FS 313761 AUNZ-026 LFS AUNZ POD POC Format
LFS
LFS AUNZ POD/POC Format
CALIDUS ePOD
24th February 2014 - 0.2
Reference: FS 313761 AUNZ-026
Contents
Functional Overview
Client Requirement
Proof of Delivery and Proof of Collection documents are required for Delivery and customer collection Jobs only.
There are two ways the Proof of delivery document can be issued to the customer:
- 1) If a customer email is available on the contact section of the Location stored in the CTMS system, an automatic POD document can be sent to the customer at the completion of the job. It is understood that PDF format is required. There is also the option to send the EPOD document to a central email address for LFS.
- 2) The Proof of Delivery / Proof of Collection documents will be available for the customer to view on-line through the web portal.
LFS have provides OBS with the format of the POD document, seen in Appendix A
Further comments provided by the customer:
- The shipping Temp and the Commodity are as per the fields that are on the CTMS for Order Temp and Commodity. These are in specs AUNZ-001,AUNZ-002 and AUNZ-003.
- The delivery comments should be any notes that have been keyed in by the driver
- The POC is the same format, just changing delivery to collection.
- The watermark they want on the Signature is seen in Appendix A. This is related to the PDA changes in AUNZ-013. The text is slightly different than what has been provided previously. This must show on the POD and POC note too.
Solution Overview
The report will be produced in CALIDUS ePOD to the specifications provided - several further items of data not currently stored by the system will be passed in from CALIDUS TMS and will be used to populate the report.
The report may be viewed through direct access through the Report button in the Jobs screens in CALIDUS ePOD or through remote access from CALIDUS Portal.
The format has been prototyped and is as follows:
Scope
- This functionality will be developed in the latest version of CALIDUS ePOD only.
- CALIDUS TMS requirements are mentioned only by reference in this solution - see elsewhere for specification of the changes to that system.
Note: Best efforts will be made to match the produced format to the sample provided, but differences in production and presentation (i.e. Browser, Email, etc) may result in some small differences.
Set-up
Pre-requisites
- A working CALIDUS ePOD system.
- A working CALIDUS TMS system, accessible to the CALIDUS ePOD system.
CALIDUS TMS Interface Changes
Note: No change are required to the existing CALIDUS ePOD interface formats, as the new data will be passed in using existing fields in the interface. For clarity, this information is as follows:
- Order Date - EPL_ORDER_DATE
- Shipping Temp - EPL_CONTAINER_PACKAGE_CODE
- Commodity - EPL_DESCRIPTION_LONG
Menu Structure
None
Data
A Job Group record should be created for the business. The settings should include:
- Driver Signature requirements
- POD and POC format set to "LFS (AU/NZ)"
Functional Description
Admin Changes
The Job Group and Site screens (job_group.aspx and site_header.aspx respectively) will be modified to allow the system to be configured for the new LFS report, by adding this as an option to the DDLs in the editing pop-up forms, for both POD and POC format. Additionally, the grid will be modified to display this correctly if selected. The name on the list will be 'LFS (AU/NZ)', pointing to the new report below, LFS_AUNZ.aspx.
POD/POC Format
Note: This format has been prototyped and is available on request for the developer to base the final formats.
The format created here should follow the standardised pagination code used in other formats.
The format will be created as LFS_AUNZ.aspx.
The fields will be mapped as follows when this is a delivery job. Note that all fields come from EPOD_JOB unless specified differently:
- Customer - EPL_CUSTOMER_NAME of EPL_CUSTOMER.
- Customer Reference - EPL_CUST_REF
- Order Date - EPL_ORDER_DATE, formatted as a long date format, plus day name.
- Origin - EPL_NAME/EPL_ADDRESS_LINE_1/2/3/4/5/EPL_POST_CODE of EPL_JOB_ADDRESS for job type "C".
- Destination - EPL_NAME/EPL_ADDRESS_LINE_1/2/3/4/5/EPL_POSTCODE of EPL_JOB_ADDRESS for job type "D".
- Delivery Instructions - EPL_JOB_INSTRUCTION
- Details - This information will come from the Containers sent to CALIDUS ePOD. Regardless of whether this is a collection or delivery, the information is taken from the EPOD_CONTAINERS table. The information will be concatenated on EPL_CONTAINER_PACKAGE_CODE and EPL_DESCRIPTION_LONG (the shipping temp and commodity code respectively) - this will be referred to as the group from this point onwards. There will be a maximum of 6 detail lines in this format, not including the title.
- Items - The number of containers of this matching EPL_CONTAINER_PACKAGE_CODE ND and EPL_DESCRIPTION_LONG.
- Shipping Temp - EPL_CONTAINER_PACKAGE_CODE of the group
- Commodity - EPL_DESCRIPTION_LONG of the group
- Weight - The sum of all EPL_WEIGHT fields on all records in this group
- Dimensions - EPL_CODE_1 of any of the records of this group
- Delivery Date - EPL_END_ACTUAL_DATE
- Delivery Time - EPL_END_ACTUAL_TIME
- Received By - EPL_SIGNATORY
- Delivery Comments
- Signature - the image of the customer signature from EPL_JOB_SIGNATURE. This will overlay a background containing the fixed text "ORDER RECEIVED IN FULL AND GOOD CONDITION".
All other elements on the report shall be fixed text and formatting.
For collection jobs, the following modifications will be made:
- Replace the word "Delivery" with the word "Collection" in all labels.
Note: When producing this format as PDF through WkHtmlToPDF, this format should have no borders.
Appendix A: Report Format Examples
Sample POD Note
Sample Watermark
Appendix B: Quote & Document References
| Cost Details | ||||
| Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | 0 | £0.00 |
| Change Request Evaluation | 0.00 | 0.00 | 0 | £0.00 |
| Functional Specification | 0.00 | 0.75 | 0 | £0.00 |
| Technical Specification | 0.00 | 0.00 | 0 | £0.00 |
| Development | 0.00 | 1.75 | 0 | £0.00 |
| Testing and Release | 0.00 | 0.25 | 0 | £0.00 |
| Implementation | 0.00 | 0.25 | 0 | £0.00 |
| Project Management | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | 0 | £First argument to "number_format" must be a number. |
| TOTAL | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | £First argument to "number_format" must be a number. | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 |
B.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. |
B.3 Authorised By
Matt Tipping | Project Manager | _____________________________ |
____________________(PRINT) | Client Representative | _____________________________ |
