FS 359234 SCR-358307-8 DELG Collection Performance Report
The Delivery Group
Collection Performance Report
Functional Specification
7th August 2019 - 1.0
Reference: FS 359234 SCR-358307-8
Contents
FUNCTIONAL OVERVIEW
Client Requirement
A Collection Performance report is required.
The format of this report has been provided and is referenced in the appendices below.
Solution Overview
A new report labelled as "Collection Performance report" will be added to the list of reports that can be run from the C-ePOD Admin Reports screen.
When selected, the report will prompt for the parameters, expected to be:
- Date range, cannot be more than a month. A date lookup will be provided.
- Depot - from drop-down list, defaulting to current depot, selecting only non-warehouse depots for the list, including a first row option of "All Depots".
When the user clicks Run Report, the application will create and then open up the report. Depending on the browser settings, this could be through the browser, through download or directly in Microsoft Excel (if locally installed).
The report generated will produce several tabs:
- A Parameters sheet, showing the entered parameters and the report title.
- A Reports sheet, identical in structure and operation to the existing report.
- A Report Data sheet, identical in structure and operation to the existing report.
- An Arrivals Before Collection Time sheet, identical in structure and operation to the existing report.
- A Calculation sheet, combining the data currently reported in the existing Calculation Sheet and Data Extract OTIF sheets.
Scope
This change will be applied to the latest version of CALIDUS ePOD version 4.5.
Impact
None - this is a new implementation of CALIDUS ePOD.
CONFIGURATION SET-UP
Pre-requisites
The CALIDUS ePOD system must be implemented as described in the solution design document, referenced in the appendices.
Menu Structure
Reports/Collection Performance Report.
Data
None
Implementation Advice
As part of the release of the software changes, a Collection Report Template will be included.
FUNCTIONAL DESCRIPTION
Report Parameters
A new report labelled as "Collection Performance report" will be added to the list of reports that can be run from the C-ePOD Admin Reports screen.
When selected, the report will prompt for the parameters:
- Date range - this cannot be more than a month apart from each other. A date lookup will be provided. The dates will both default to yesterday's date.
- Depot - from drop-down list, defaulting to current depot, selecting only non-warehouse depots for the list, including a first row option of "All Depots".
When the user clicks Run Report, the application will validate the parameters. The validation will appear as a box-out on the parameter that is wrong, stating the issue.
In this case, the Date To parameter will be validated, showing that the date range must be 31 days or less.
The report will not run if there are validation errors.
When the user clicks Run Report, the application will create and then open up the report. Depending on the browser settings, this could be through the browser, through download or directly in Microsoft Excel (if locally installed).
Report Structure
The report will be named for download as follows:
Collection Performance Report-{DEPOT}-{DATEFROM}-{DATETO}.xlsx
So, running the report for all depots from 08/07/2019 - 08/07/2019, the report would be named:
Collection Performance Report-ALL-20190708-20190708.xlsx
The user can rename the report as it is saved from the browser.
The saved report will be able to be edited, filtered and saved like the sample report.
Parameters Sheet
The report will contain a Parameters sheet as the first sheet, showing the entered parameters and the report title.
The site logo from the site of the user logged in to the system will be shown in the top left corner of this page.
The report title will be fixed as "Customer Collection Performance Report".
The parameters entered by the user will be shown on the sheet:
- "Date From:" - in DD/MM/YYYY format.
- "Date To:" - in DD/MM/YYYY format.
- "Depot:" - the name of the site selected, or "All" if the user selected all depots.
The sheet will also allow entry and changing of the following parameters within the produced report itself:
- SLA Parameters - a table of minutes, description and SLA adherence text. This is used by the report data to categorise each job's SLA adherence.
- Column Parameters - which columns the report uses for the Book Time, Open Time and Close Time for the report data.
Note: The column numbers selected for each of the times will change in the final report, to reflect the columns in the new Calculation sheet.
Reports Sheet
The report will show a Reports sheet, identical in structure and operation to the existing report.
This sheet sources its information from the Report Data sheet and contains 2 pivot tables showing SLA adherence.
Report Data Sheet
The report will show a Report Data sheet, identical in structure and operation to the existing report.
Note: This sheet will not contain conditional formatting (or any manual formatting) on the data rows to highlight the Onepost jobs, nor will any - the customer has confirmed that this is not required.
The data from this sheet is sourced from the Calculation Data sheet.
Arrivals Before Collection Time Sheet
The report will show an Arrivals Before Collection Time sheet, identical in structure and operation to the existing report.
The data for this sheet is sourced from the Report Data sheet.
Calculation Sheet
The report will show a Calculation sheet, combining the data currently reported in the existing Calculation Sheet and Data Extract OTIF sheets.
C-ePOD will generate this data (with additional columns added to combine the Book, Open and Close times) in the same way that the original two sheets worked, but into one data source, as all of the data required will be held in the C-ePOD database against the jobs.
TECHNICAL NOTES
Modules Changed
| Module Name | Module Type | Notes |
|---|---|---|
| ExcelReports.aspx | WinForm | |
| ExcelReports.aspx.cs | WinForm code | |
| XLReports.cs | Server Code | |
| {Date}_{Time}-{SysVer}-359234_CollectionPerformanceReport.sql | Database Modification Script |
Table Updates
| Name | Type | Nullable | Default | Storage | Comments |
|---|---|---|---|---|---|
Developer Notes
Note: .NET's objects used to create spreadsheets cannot create pivot tables. However, it is capable of the following:
- Copying a workbook and naming it appropriately.
- Opening an existing workbook.
- Change a range that a range name applies to.
The original sample report has been modified to use named ranges for the report data, rather than cell references.
"pivotData" has been created for the pivot reports, pointing to the Report Data ranges.
This has been applied to the following Pivot reports:
- "Reports" sheet - 3 pivot reports
- "Arrivals before Collection Time" sheet.
VLOOKUPS on the Report Data sheet uses fixed ranges from Calculation Sheet - this has been changed for a named range. Similarly, also the SLA ranges have been changed. The formulas here have been improved. The named ranges are:
- calculationData
- lkupSLA
Calculation Sheet also uses VLOOKUP to determine SLA adherence through the parameters. The name has been changed to lkupSLATime.
The following is a summary of the development required to produce this report:
- Copy the template to a reasonable name.
- Update the parameter sheet with the runtime parameters.
- Create a dataset similar to a combination of the existing Calculation and Data Extract sheet data.
- Add a single formula to each row of this sheet (to calculate the SLA).
- Select this data and update the named range "calculationData".
- Select the Report Data sheet and create rows up to the amount of rows in the data sheet.
- Select this and update the "pivotData" named range.
- Save the sheet and serve it up to the customer in exactly the way that any other report is served to the customer.
For further reading on how to achieve some of the above techniques see:
https://poi.apache.org/components/spreadsheet/quick-guide.html#NamedRanges
.NET Solution
Add an empty version of the report to a new Report Templates folder. under the top-level Web App project.
This template can be sourced from the sample report referenced in the appendices.
Ensure that this file is always included in the build.
Data Modification Script
A data modification script will be required to add changes to the Excel reports capable of being run from the system, adding "Collection Performance Report" to the drop-down list name "ddlReportSelect" on EPOD_LISTS. The value will be added to EPOD_LIST_ITEMS with ListId equal to the ID of the record on EPOD_LISTS. The report will be added as value "9".
This will be named {Date}_{Time}-{SysVer}-359234_CollectionPerformanceReport.sql, with Date, Time and System version are set from the current date, time and system version respectively.
The script must be added to the EPOD_DatabaseScriptsLibrary project and set to "Copy Always" to output directory.
Admin Reports screen
In ExcelReports.aspx.cs:
Add Collection Performance report to the drop-down list of reports ddlReportSelect, as a 9th report. Label it as such in the drop-down list. Note: This will be achieved through the data modification script.
Re-utilise the Date Range code from the Service report, and the the list of depots from the PvA report. Load the ddlCPRDepot drop-down list from the depot list. The depot list should default to "All Depots" rather than the current depot (unlike the PvA report). The default "All Depots" value should be a value that cannot be entered for a site in C-ePOD, such as "*", space or null.
Add a new case "9" to the select in the CreateXLS_Click event handler. Set the parameters and call a new method CollectionPerformanceReport, storing the resulting dataset.
Create a new method here called CreateCollectionPerformanceReport, passing the dataset and the parameters. Call this only if the report type (exportTypeDDL) is "xlsx".
Exclude report "9" from the standard report processing.
In XLReports.cs:
Create a new method CollectionPerformanceReport.
Use the parameters passed in in the selection, and that the columns are in the same sequence as above. Select only Collection jobs initially, but link to the associated delivery job on the same load. Select only completed collections (i.e. EPL_STATUS = "C"). Select the collection jobs by the Actual End date being within the date range provided. If the depot selected is not the default "All Depots" option, select the site of the collection jobs for the provided depot parameter.
All EPOD_JOB data from selected jobs should be reported as well as the following:
- ROUTE NAME - EPOD_LOAD.EPL_ROUTE_CODE.
- LOCATION - EPOD_CUSTOMER.EPL_NAME from EPOD_JOB.EPL_CUSTOMER_CODE.
- COLL DEPOT - EPL_SITE_NAME of EPOD_SITE linked from EPOD_JOB.
- RTD TIME - EPL_END_ACTUAL_DATE/TIME from the linked delivery EPOD_JOB of the same EPL_JOB_CODE on the same EPL_LOAD_ID.
- COST CENTRE - APV_VALUE of EPOD_ADM_PARAMETER_VALUE where APV_PARAM_CODE is "COST_CENTRE" for EPL_CUSTOMER_CODE of EPOD_CUSTOMER linked to EPOD_JOB.
- Freq - EPL_SERVICE_LEVEL of EPOD_JOB.
- Open Time - ETW_TIME_START of EPOD_TIME_WINDOW for EPOD_JOB.
- Close Time - ETW_TIME_START of EPOD_TIME_WINDOW for EPOD_JOB.
In CreateCollectionPerformanceReport:
- Copy the template from the Report Templates area under the root folder to the new name.
- Naming convention is:
Collection Performance Report-{DEPOT}-{DATEFROM}-{DATETO}.xlsx
- So, for all depots from 08/07/2019 - 08/07/2019, the report would be named:
Collection Performance Report-ALL-20190708-20190708.xlsx
- Update the Parameters worksheet with the parameters and the logo.
- Add the data from the Data Set to the Calculation Sheet. Include in this the formulas from the existing sheet, as shown below.
- ORDER REF - EPL_JOB_CODE.
- DATE - EPL_END_ACTUAL_DATE.
- MONTH - Extracted from EPL_END_ACTUAL_DATE.
- WEEK NO - Calculated from EPL_END_ACTUAL_DATE.
- ARR AT LOC - EPL_ARRIVAL_DATE/TIME of EPOD_JOB.
- DEP FROM LOC - EPL_END_ACTUAL_DATE/TIME of EPOD_JOB.
- DUR AT LOC - calculated from the prior two fields, represented as a time (hours and minutes).
- ROUTE NAME - EPOD_LOAD.EPL_ROUTE_CODE.
- LOCATION - EPOD_CUSTOMER.EPL_NAME from EPOD_JOB.EPL_CUSTOMER_CODE.
- ORDER_REF - EPL_CUST_REF of EPOD_JOB.
- SCH COLL TIME - EPL_START_PLANNED_DATE/TIME of EPOD_JOB.
- COLL DEPOT - EPL_SITE_NAME of EPOD_SITE.
- RTD TIME - EPL_END_ACTUAL_DATE/TIME from the linked delivery EPOD_JOB of the same EPL_JOB_CODE on the same EPL_LOAD_ID.
- SLA vs Sch coll time - a formula lookup on the lkupSLATime, taken from the existing Calculation Sheet. This differs to the "SLA Vs Book Time" in that this uses the Schedule Collection time rather than the defined Book time.
- ARR V SCH TIME - EPL_START_PLANNED_DATE/TIME of EPOD_JOB minus EPL_ARRIVAL_DATE/TIME of EPOD_JOB, represented as a time (hours and minutes).
- COST CENTRE - APV_VALUE of EPOD_ADM_PARAMETER_VALUE where APV_PARAM_CODE is "COST_CENTRE" for EPL_CUSTOMER_CODE of EPOD_CUSTOMER linked to EPOD_JOB.
- Freq - EPL_SERVICE_LEVEL of EPOD_JOB.
- Lookup - a formula of COLL DEPOT, ROUTE NAME, Freq and LOCATION, delimited with a dash, as in the formula in the existing Calculation Sheet.
- Book Time - EPL_COL_DATE/TIME of EPOD_JOB.
- Open Time - ETW_TIME_START of EPOD_TIME_WINDOW for EPOD_JOB.
- Close Time - ETW_TIME_START of EPOD_TIME_WINDOW for EPOD_JOB.
- Minutes - EPL_ARRIVAL_DATE/TIME of EPOD_JOB minus EPL_COL_DATE/TIME in while minutes, rounded up.
- SLA vs Book Time - a formula lookup on the lkupSLATime, taken from the existing Calculation Sheet. This should use the defined Book time (which may the scheduled collection time or the planned collection time, depending on parameters taken from the Parameters sheet).
- Count the number of rows and update the pivotData and calculationData ranges accordingly.
- Save the workbook.
- Write the worksheet to the Response OutputStream and close the Response.
In ExcelReports.aspx:
Add a panel for the parameters for the new report, called pnlCollectionPerformance.
Add a Date From (tbCPRDateFrom) and Date To (tbCPRDateTo), both with appropriate labels sourced from the resource library, with calendar extenders, and the Date To with a validation extender to check that the two dates are not more than 31 days apart. Add javascript checking if necessary. The dates will both default to yesterday's date.
Add a drop-down list ddlCPRDepot.
The Clear button will reset the dates to today's date and the depot to "All Depots".
TEST PLAN
| Test Script / Scenario Reference | Collection Performance Report | Call Number(s): 359234 SCR-358307-8 |
| Test Script / Scenario Description | Testing the new Collection Performance report functionality. | PASS / ISSUES / FAIL |
| Menu Access | Reports | |
| Pre-requisites | Several pairs of collection and delivery jobs should have been created and completed in multiple sites (depots), along with some incomplete jobs, and completed linked delivery and collection pairs. Jobs should be planned and completed on the same day, and there should be several over multiple days. | Tested By: |
| Test Objective | To test that; the parameters select data correctly; the data selected for the report is correct; the report output is as expected. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Collection Performance Report. | |||
| 1.01 | The actions to follow | The expected result | ||
| 1.02 | Select the Collection Performance report from the drop-down list. | The correct parameters are displayed. | ||
| 1.03 | Enter a date range greater than 31 days. | A validation error will occur, and the report cannot be run. | ||
| 1.04 | Enter a date range covering all jobs in all depots. Click Run Report. | The report is produced. The default name is correct as per the specification. | ||
| 1.05 | Download the report and check it. | The Calculation Data sheet shows all data that should be selected. The calculated formulas are correct. The Report Data sheet lists all of the data correctly from the Calculation Data sheet and can be filtered as normal. The Reports sheet is populated on all three pivot charts and the data is correct and can be filtered as normal. | ||
| 1.06 | Re-run the report, with only a single depot (ensuring this will select some data). Click Run Report. | The report is produced. The default name is correct as per the specification. The data in the report is correct as before, showing only the data from the depot selected. Note: Compare the results with the previous workbook produced, by filtering the previous report just for the selected depot. | ||
| 1.07 | Re-run the report, with the same depot but with a single date where there are multiple jobs (ensuring this will select some data). Click Run Report. | The report is produced. The default name is correct as per the specification. The data in the report is correct as before, showing only the data from the depot selected and the date. Note: Compare the results with the previous workbook produced, by filtering the previous report just for the selected date. |
APPENDIX A: QUOTE & DOCUMENT HISTORY
| Cost Details | ||||
| Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | 850 | £0.00 |
| Change Request Evaluation | 0.00 | 0.00 | 850 | £0.00 |
| Functional Specification | 0.75 | 0.75 | 850 | £637.50 |
| Technical Specification | 0.00 | 0.00 | 850 | £0.00 |
| Development | 2.50 | 2.50 | 850 | £2,125.00 |
| Testing and Release | 0.50 | 0.50 | 850 | £425.00 |
| Implementation | 0.25 | 0.25 | 850 | £212.50 |
| Project Management | 0.25 | 0.25 | 850 | £212.50 |
| TOTAL | 4.25 | 4.25 | £3,612.50 | |
| Estimate excludes training, release to live and go live support. |
References
| Ref No | Document Title & ID | Version | Date |
| 1 | SDD 358307 The Delivery Group Solution Design | 0.3 | 18/07/2019 |
| 2 | File:4th July 2019 - TMS Customer Collection Performance Report v5.xlsx | 5 | 04/07/2019 |
| 3 | File:Customer Collection Performance Report TEMPLATE.xlsx | N/A | 02/08/2019 |
Glossary
| Term or Acronym | Meaning |
|---|---|
| General Definitions | |
| EPOD | Electronic Proof of Delivery. The OBSL EPOD system is CALIDUS ePOD. This also comprises the basis of the Service Completion system CALIDUS eServ. |
| Server | The portion of the CALIDUS ePOD/eServ systems that controls all the data and sends information to and receives updates from the mobile device. |
| Mobile Device; PDA | The device used by the driver to perform the jobs. Typically an Android mobile device or tablet. |
| Site | The site usually defines the depot, business or the transport group (carrier). It can be set to any value required by the customer. All transactions data (for example, loads and jobs) and standing data (for example, vehicles and uses) belong to a site. An EPOD user, on a device or in the Admin screen, can only see data for one site at a time. |
| Load | A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload. |
| Job | Also Consignment. A single task for the driver as a specific location. This could be the collection of goods or the delivery of goods. Jobs may also be Services (for example, servicing, installing or de-installing a boiler). A job is identified by a unique job ID but can also have other references held against the job (e.g. job code, SO number, customer reference and external reference). |
| Job Group | Jobs must be tagged with a Job Group. All jobs tagged with a single job group are processed in the same way. The job group has configuration associated to it to control such items as: POD/POC Report settings; Pre-Job actions (such as signing at a gatehouse); Post-Job actions (such as who signs for the item, are photos required); configurable fields required for entry for the jobs; Terms and Conditions displayed and; driver/user process (such as photos required for cancellation, comments/notes allowed). The job group can be used for any or all Sites, and the configuration against the job group can be different in each site. Job Groups can also be restricted from Admin and Remote users, so that certain users only see jobs for certain groups. |
| Container | A generic term for any object that contains the items being collected or delivered. Examples of containers are: Pallet; Package; Carton; Item; Cage. A special container "Loose Products" - see Product below. A container is identified by a container ID which is unique to this physical container. |
| Product | A product is any goods that are being collected or delivered where the product has a 'Product Code' which identifies what the product is but which does not uniquely identify each individual item. A product will also have a quantity associated with it to indicate how many items of this 'Product Code' are being collected or delivered. Products can either be processed within a 'Container' or as 'Loose Products' without a 'Container'. |
| Owner | The owner of the order that created the job. Typically this is the sales team that took the order and will be responsible for dealing with queries from the customer regarding the status. |
| Operator; Executor | The Site (depot or carrier) that is executing the load or loads that are involved in the delivery of the items. |
| Item Related Definitions | |
| Job Code | A reference associated with a job or job(s). This reference is common to connected jobs, for example this would be the same on both the collection of goods and the associated delivery of the same goods. Typically this would be the transport unique reference. |
| SO Number | A reference associated with a job which indicates the "Sales Order Number" this job is associated with. |
| Customer Reference | A reference associated with a job which has been provided by and will be recognised by the customer. |
| External Reference | A reference associated with a job which does not match any of the existing references, usually because it has been provided by an external system. |
| Pallet | An alternative for 'Container'. The term pallet is used when the operation only uses portable platforms as the container for goods. |
| Package | An alternative for 'Container'. The term package is used when the operation only uses boxes or wrapping as containers for goods. |
| Package Code | A code representing the type of 'Container'. |
| Package Desc | A description of the type of 'Container'. |
| Product Code | A code which identifies what a product is. |
| Item | A generic term for any individual item that can be collected or delivered. An item can represent a 'Container' or a 'Product'. This can also be used as an alternative for 'Container' when the operation only treats the goods as individual items, i.e. not as identifiable products. |
| Service Item | An item which will be serviced by a service job. See action 'Service'. |
| Issue Life | The time after which an item is no longer fit for purpose. |
| Pack Size; Case Quantity | A product may consist of a full quantity of items, inside a pack. The Pack Size (or Case Quantity) defines the amount of this product contained in a single pack. For example, if there are 85 items to deliver, with a pack size of 24, the number of full packs is determined to be 3 (24 * 3, or 72), with the remaining (13) being 'loose' quantity. This is displayed as "3/13" on the mobile application. |
| UOM; Item Type | Unit of Measure; The major (case) UOM. This can optionally be displayed on the mobile device when changing product quantities. |
| Product Type | A classification of the product being delivered. For example, a company may deliver 7 different mortar products and 80 different concrete slab products. The Product Types may be set to "MORTAR" and "SLABS". This may be used to attach additional configuration, changing the data required when collecting or delivering these product types. |
| Status Definitions | |
| Status | An indicator of how far through the processing a 'Job', 'Container' or 'Product' has progressed. |
| Pending | A status indicating that the processing has not yet started, but is required to be completed. |
| In Progress | A status indicating that processing has started but not yet finished. |
| Complete | A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered. |
| Complete (Amended) | A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered but that some changes or amendments have been made. This means that not everything that was planned to be collected or delivered was collected or delivered, some items may have been cancelled or some products may only have had some of the planned quantities collected or delivered. |
| Complete (Claused) | A status indicating that the processing has been finished but that a 'Clause' condition has been recorded for this item. |
| Claused | See 'Complete (Claused)' and action 'Clause'. |
| Cancelled | A status indicating that the processing of this item or job is no longer required. |
| Cancelled at Collection | A status indicating that the delivery of a container or product is no longer required because the associated collection of this container or product was cancelled. |
| Submitted | An optional status that applies only to a 'Job' and which occurs after the 'Job' has been completed. This indicates that any time and expenses information recorded for the 'Job' has been submitted back to the server and can no longer be altered. |
| Action Definitions | |
| Start | An action associated with a 'Job' meaning the driver is about to start the processing of this job or jobs. This action will mark the job(s) with a status of 'In Progress'. |
| Arrive | A conditional action associated with a 'Job' meaning the driver has arrived at the location the goods should be collected from or delivered to. |
| Continue | An action associated with a 'Job' meaning the driver has previously performed the 'Start' and/or 'Arrive' action and has exited the processing screen but is now going to continue the processing. |
| Collect | An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'. |
| Collect Claused | An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product' but with a condition under which the collection was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'. |
| Deliver | An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'. |
| Deliver Claused | An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product' but with a condition under which the delivery was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'. |
| Clause | An action associated with a specific 'Container' or a 'Product' that has already been collected or delivered meaning the collection or delivery has been accepted with a condition. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'. |
| Cancel | An action associated with a 'Job', 'Container' or 'Product' meaning the collection or delivery will not be performed for this 'Job', 'Container' or 'Product'. |
| Submit | An optional action which can conditionally be carried out after a 'Job' has been collection or delivered meaning that any/all required expense or time recording for this 'Job' has been completed and can be submitted back to the server. |
| Service | A service of a service item or items. Typically, Installation, Deinstallation or Service. The process of a service usually encompasses Pre- and Port-work checks, information gathering and diagnosis and resolution notes. Additional references (MC Refs) may also be captured. |
| Actioned | A general term describing completing a job. So, 'Actioned' may be used instead of 'Collected', 'Serviced', 'Delivered'. |
| Consolidate | The action of taking several jobs and linking them together, so they are actioned at the same time with one start, arrive and signature. |
| Deconsolidate | The action of taking a consolidation of jobs and breaking them down into the component jobs again. |
| Job Swap | The action of selecting an existing load not assigned to the user, and picking jobs to transfer onto the user's load. |
| Signature Capture | Usually the final action of a job, where the customer's name and signature are entered. |
| Other Definitions | |
| Reason Code | A code which represents the reason that a job was cancelled or an item was cancelled or claused. |
| Vehicle | The vehicle used for transporting the goods. |
| Vehicle Checks | Also Defect Checks. A series of questions representing the results of checks intended to ensure the vehicle is in an acceptable condition. |
| Metrics Entry | A series of questions to capture information either at the start or end of a 'Load'. |
| Driver | The person performing the collections or deliveries; the user of the device/application. |
| Engineer | The person performing the services; the user of the device/application. |
| Customer | The person/company the goods are being collected from or delivered to. |
| Signatory | The name of the person providing a signature. |
| T&Cs | Terms and Conditions. The T&Cs are shown when signatures are prompted for. The text of the T&Cs are defined in the system itself. |
| Transfer Load | A load select from which to swap jobs to the user's load. |
| Base | E.g. 'Return to Base'. Typically the depot from which the driver departed. |
| Unplanned Ad Hoc Collection | A collection job that is created by the driver, usually after delivering to a customer. |
| Ad Hoc Container Entry/Scanning | The process of adding containers (items) to a job that have not been pre-advised on the job. |
| Completion Report | POD, POC, Service/Work Report. |
| Load Assignment | The action of assigning a vehicle and/or a driver to a load. |
| Job Assignment | The action of putting jobs onto a load. |
| Collection/Delivery Windows; Access Windows | Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes. |
| Location/Map Terms | |
| Lat-Longs; GPS Co-ordinates, GPS Position | Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - CALIDUS ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool. |
| GPS | Global Positioning System; the satellite system used to obtain a GPS position, for use with navigation and location positioning. |
| Geocode; Reverse Geocode | Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs. |
| Geofence; Geofence Break | A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimeter on entry or exit from the location. |
Authorised By
Murray Middleton | OBS Project Manager | _____________________________ |
Stuart Mylchreest | Customer Representative | _____________________________ |
