REQ 305796 Partnerlink EPOD Solution
Partnerlink
Partnerlink ePOD Solution
CALIDUS ePOD
30th January 2013 - 0.1
Reference: REQ 305796
Contents
Introduction
This document is the Partnerlink ePOD Solution document.
Objective
The primary purpose of this document is to document the requirements gathered from Partnerlink, at meetings held in the Kinghts of Old offices on 22-24th January, 2012
This document has been written in a manner such that it can be approved by non-technical representatives of Partnerlink whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.
Scope and Limitations
This document is based on the documentation provided by Partnerlink, as referred to in the appendices, as well as information gleaned from site visits and workshops with Partnerlink.
- The changes will be made in the latest version of the CALIDUS ePOD system.
Client Requirements
Listed below are the proposed processes that will be followed by the operatives using CALIDUS ePOD. Also shown are the changes required for this to be achieved.
General Changes
A number of changes have been requested to the general styling of all areas of the system - the details are shown here:
SCR-305796-1: Ensure that the correct Partnerlink logo is displayed on the device. SCR-305796-2: Change "Container" to "Pallet" on the device
Importing Data
Note: CALIDUS ePOD will be accepting data imports from 3 systems initially:
- Vigo
- Mandata
- Stirling
The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system:
Warning: list new items here
Some of the above are additional items, and the system will be modified to accept these new items.
Logging In
Vehicle Checks
Job List
| SCR-305796-3: | Layout changes to the Job List screen |
| SCR-305796-4: | Allow force updating of a Load from the Job List screen |
| SCR-305796-5: | Resequence Jobs |
Job Details
| SCR-305796-6: | Remove facility to Cancel a Job |
| SCR-305796-7: | Force viewing of Special Instructions on Starting Job |
| SCR-305796-8: | Allow force updating of a Job while in progress |
Delivery
| SCR-305796-9: | Allow back-out of a job after Arrival |
Collection
Warning: Collection with no containers - allow Notes entry at all times.
Job Confirmation
| SCR-305796-10: | Allow Customer to Clause delivery items |
Completion of a Load (Manifest)
Job Completion Documents
| SCR-305796-11: | Create POD Formats (Generic and Palletforce) |
Exporting Data
| SCR-305796-12: | Automatically email on cancellation of a job only |
Note: CALIDUS ePOD will be sending data exports to 4 systems initially, with up to 3 being informed of completion at any one time:
- Vigo
- Mandata
- Stirling
- Palletforce
The exact formats and methodologies of the data exports from the various systems are still being decided. However, there is a requirement that certain data items are passed out of the system:
- Warning: list new items here
Some of the above are additional items, and the system will be modified to accept these new items.
Additionally, the system will be required to export the POD/POC documents automatically in TIFF format. This will also be required for the Palletforce system.
| SCR-305796-13: | Export POD document as TIFF through the existing Partnerlink processes. |
| SCR-305796-14: | Export POD document as TIFF to Palletforce system |
The system will also be required to act as a data source for the CALIDUS TTM system. This will require all imported data and all updated and completed data to be exported. This will be through the existing ePOD-TTM interface, as described elsewhere.
However, there will also be amendments to this interface to allow for the specific functionality described in this document, namely:
- Resequencing
- Order In Progress (to recalculate ETAs)
- Order Arrived
- Warning: any others?
Additional modifications will be made to TTM to allow it to access the POD document through a link. These are specified elsewhere.
| SCR-305796-15: | Changes to ePOD-TTM interface |
Out of Scope Changes
This section details functionality requested to be added to the process above, that is not within the scope of the project.
= Trailer IDs
| SCR-305796-16: | Trailer ID changes |
Appendix A: Table of SCRs and Ballpark Estimates
| SCR# | System | Area | Description | Estimate (Days) | Notes |
| 1 | System Affected | Area Affected | Description of change | First argument to "number_format" must be a number. | Any notes, numerically listed |
Notes:
- Any high level ballpark estimates for development are based on the basic information provided and are subject to detailed design and creation of an SCR.
- <Further notes, referenced in the notes column of the grid above>
Appendix B: Document References
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | Reference1 | 0.1 | 01/01/2011 |
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
Phil Harding | OBS Project Manager | _____________________________ |
