FS 325466 SCR-HEW-007 Extract of data from EPOD
Hewicks Haulage
Extract of data from EPOD
CALIDUS EPOD
8th April 2015 - 2.0
Reference: FS 325466 SCR-HEW-007
Contents
Functional Overview
Client Requirement
CSV exports will need to be generated from the EPOD system.
Existing Reports Samples
Solution Overview
Currently different reports are created for each individual customer. One generic report will be designed which contains all data that is needed. The relevant information for each customer can then be manually manipulated on the spreadsheet. Note: There is no Charging or Invoice functionality within CALIDUS EPOD, therefore no charge information can be extracted for the jobs.
The following parameters will need to available to filter the data required to generate the reports
- Date Range
- Customer Code
- Collection or Delivery customer
The existing Reports screen will be modified to include a drop-down list of all available reports. The current report will be labelled 'Service Report' a new report will be added: 'Transport Report'. When a report is selected, the relevant parameters will be displayed for it. This report will prompt for the Location and Date Range. The report will, when run, extract the data to/from that location, obtaining the information from any jobs linked to the jobs selected by the transport reference (the Job Code). The report will print the data as required above, with all columns consolidated from the three reports into one data extract. This report will open directly in Microsoft Excel and may then be further formatted and modified. It is not expected that the data will be formatted in any way other than to highlight a title for the report, showing the location and the date range selected.
Fields available in the report will be:
- Weighbridge Ticket - Recorded on PDA by driver
- Arrival date/time - Actual arrival Arrival Date/Time from the Collection job
- Collected Date/Time - Actual End or Arrival Date/Time from the Collection job (NOTE - The arrival date and time and the collected date and time will be used to manually calculate the demurrage)
- Collected Weight - Weight recorded by driver UDF details
- Delivered Weight - Weight keyed in by driver on collection
- Haulage Cost - EPOD does not support costs or invoicing - not included
- Rate/Rate Charged - EPOD does not support costs or invoicing - not included
- Order No - Job Code of the collection or delivery job
- Delivery Customer - Customer Name from the Delivery Job
- Delivery Place - Full delivery address
- Fixing Code - Will be keyed in as the customer reference at order entry
- Price T - EPOD does not support costs or invoicing - not included.
- Delivery Date/Time - Actual End or Arrival Date/Time from the Delivery job.
- Collection Point - Full collection address
- Product Collected - Product Code and/or Description from product(s) on the collection job
- McCain Ticket Number - Recorded weighbridge number by driver
- Customer Ticket Number - Recorded weighbridge number by driver
- (Customer) Weight - from Product UDF on the Delivery job
Scope
The changes will be made to the latest version of the CALIDUS EPOD system.
Set-up
Pre-requisites
A valid CALIDUS EPOD system is required.
Menu Structure
None
Data
None
Functional Description
Admin Reports
The existing CALIDUS EPOD Admin Reports screen will be modified to include a drop-down list of all available reports. The current report will be labelled 'Service Report'. A new report will be added labelled as 'Transport Report'.
Reports Selection
When a report is selected, the relevant parameters will be displayed for it, and any parameters for any previously-selected reports will be hidden.
The existing Service report will continue to prompt for Date From, Date To and Job Group.
Service Report parameters
The new Transport report will prompt for the following:
- Date From - a pop-up date picker will be displayed to select the date, defaulting to and indicating the current date. This entry is required and cannot extend to more than 28 days of data selected.
- Date To - a pop-up date picker will be displayed to select the date, defaulting to and indicating the current date. This entry is required and cannot extend to more than 28 days of data selected.
- Customer - The customer. The customers should be presented in a list, allowing the user to see and select a single customer, matching the text entered. A partial match of any part of the customer name should display the customer and allow it to be selected. This is required entry.
- Collect or Delivery - Whether the customer selected is the Collection customer or the Delivery customer. This will be presented as a a list, allowing the user to select one of the two values. This is required entry and will default to "Collect".
The screen will validate all entered values that they are populated where required and entered correctly.
Transport Report parameters
The screen will allow two actions through the following buttons:
- Clear - to clear the parameters entered.
- Create Excel Spreadsheet - to run the report and generate the Excel spreadsheet.
When run, the browser will open the report in the manner configured against it (i.e. saving the file locally, opening in Microsoft Excel if installed, opening in the Web Browser directly) - this is controlled by the Browser and not the CALIDUS EPOD Admin application. The report will be named "transportReport.xls"
The report will be in two sections:
- Header - this will display the parameters entered
- Report - the selected records, with header columns.
If no records are selected, the header columns and report parameters will still be displayed.
The data will be reported with the following headings and values, in this sequence:
- Collection ID - The Ticket Number (Job ID) of the Collection job.
- Collection Customer - The Customer Name of the Collection Customer
- Collection Address - Address Line 1-4 and Postcode of the Job address on the Collection job, if present, otherwise the same values from the Collection Customer.
- Collection Arrival Date - Arrival Date from the Collection Job
- Collection Arrival Time - Arrival Time from the Collection Job
- Collection End Date - Actual End Date from the Collection Job
- Collection End Time - Actual End Date from the Collection Job
- Collection Weighbridge - Weighbridge Number from the Collection Job, if present.
- Collected Weight - Product Quantity entered against the Collection job.
- Product Collected - Description of the Product from the Collection job.
- Job Code - The Job Code from the Delivery Job
- Order No - The Customer Reference from the Collection Job
- Reference - The S/O Reference from the Collection Job. This will contain the Fixing Code.
- Delivery ID - The Ticket Number (Job ID) of the Delivery job.
- Delivery Customer - The Customer Name of the Delivery Customer
- Delivery Address - Address Line 1-4 and Postcode of the Job address on the Delivery job, if present, otherwise the same values from the Delivery Customer.
- Delivery Date - Actual End Date from the Delivery Job
- Delivery Time - Actual End Time from the Delivery Job
- Delivery Weighbridge - Weighbridge Number from the Delivery Job, if present.
- Delivered Weight - Product Quantity entered against the Delivery job.
- Product Delivered - Description of the Product from the Delivery job.
Example Output format
The data from the report will depend on the selection criteria:
- Collection Job (required if selecting by Collection customer, optional if selecting by Delivery customer)
- Collection Job Products (if Collection exists)
- Collection Job Address (optionally)
- Collection Customer
- Delivery Job (required if selecting by Delivery customer, optional if selecting by Collection customer)
- Delivery Job Products (if Delivery exists)
- Delivery Job Address (optionally)
- Delivery Customer
Appendix A: Quote & Document References
| Cost Details | ||||
| Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | 750 | £0.00 |
| Change Request Evaluation | 0.00 | 0.00 | 750 | £0.00 |
| Functional Specification | 0.75 | 0.90 | 750 | £675.00 |
| Technical Specification | 0.75 | 0.75 | 750 | £562.50 |
| Development | 3.25 | 3.25 | 750 | £2,437.50 |
| Testing and Release | 0.75 | 0.75 | 750 | £562.50 |
| Implementation | 0.00 | 0.00 | 750 | £0.00 |
| Project Management | 0.00 | 0.00 | 750 | £0.00 |
| TOTAL | 5.50 | 5.65 | £4,237.50 | |
| Estimate excludes training, release to live and go live support. |
A.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | 322793 - REQ-Hewicks Haulage | 3.0 | 12/03/2015 |
A.2 Glossary
| Term | Definition |
|---|---|
| EPOD | Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD. |
| CALIDUS eSERV | The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system. |
| PDA | The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android. |
| DAL | Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it. |
| GPS | Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device. |
| GPRS, 3G, HSDPA, Data Service | All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet. |
A.3 Authorised By
Matt Tipping | OBS Logistics Representative | _____________________________ |
Christopher Hewick | Hewicks Haulage Representative | _____________________________ |
Carl Brinkley | Hewicks Haulage Representative | _____________________________ |
