|
|
| Line 23: |
Line 23: |
| = Introduction = | | = Introduction = |
| <!-- The introduction will detail the initial requirements supplied by the client --> | | <!-- The introduction will detail the initial requirements supplied by the client --> |
| This document is the {{#var:Doc_Title}}. | | This document is the {{#var:Doc_Title}}. This defines the changes to the POD report required by the customer |
|
| |
|
| {{ #vardefine: SCR | 0 }} | | {{ #vardefine: SCR | 0 }} |
| Line 37: |
Line 37: |
| * Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future. | | * Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future. |
|
| |
|
| | [[File:JBG POD page 1.jpg|border|600px]] |
|
| |
|
| | | [[File:JBG POD page 2.jpg|border|600px]] |
| | |
|
| |
|
|
| |
|
Revision as of 18:16, 2 January 2019
JB Global
JB Global POD Note Changes
CALIDUS ePOD
21st December 2018 - 0.1
Reference: REQ 354567
Introduction
This document is the JB Global POD Note Changes. This defines the changes to the POD report required by the customer
Client Requirements
I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.
Points confirmed:
- Print images on a following page as with the current delivery note.
- ePOD has no telephone number 3 so will be blank.
- Print the name and signature side by side to allow more vertical room for the signature.
- If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
- Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
Appendix A: Document References
A.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | | | |
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
Barry Preece |
OBS Project Manager | _____________________________ |
