356578 REQ SOS POD and POC Layout and Mapping
Storage On Site
POD Layout and Mapping
CALIDUS ePOD
7th August 2019 - 0.1
Reference: REQ 356578
Contents
Overview
This document describes the proposed layout and field mapping for the POD (Proof of Delivery) documents to be developed for Storage On Site. This document has been written in a manner such that it can be approved by non-technical representatives of Storage On Site whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin. There are 4 delivery documents within the scope, three of these share the same layout:
- Delivery / Collection Note
- Covers the Sales Delivery Note, Hire Delivery note and Collection Note
- Transfer Note
The Sales and Hire Delivery Notes and the Collection Note have identical layouts and content except for changes to some text headings so a single delivery note will be developed for these three documents. The Transfer Note has some differences to this layout so will be developed as a separate layout.
Scope and Limitations
This document is based on information provided by Storage On Site in emails and points clarified and confirmed in subsequent emails.
- The changes will be made in the latest version of the CALIDUS ePOD system.
POD /POC Layouts
This section shows the proposed layout of the delivery documents.
POD and POC Mapping
This section describes the source of information that appears on the POD, which can come from various sources:
- Imported
- Imported into the ePOD Admin system in the job and load details sent by Anchor Bay Construction.
- ePOD Admin
- User entered and maintained in the ePOD Admin server screens.
- ePOD Mobile
- Data captured during the ePOD mobile delivery / collection process and uploaded to the ePOD Admin server.
- Fixed Text
- Text that is embedded in the POD layout. To change these in future will require OBSL to update the report layout.
POD and POC Layouts
The annotated layout for the electronic POD documents are on the following pages.
Delivery / Collection Note
Transfer Note
POD and POC Mapping
These notes refer to the layouts on the previous pages.
Delivery / Collection Note Mapping
Heading Section
Item | Sourced from |
Company Name & Address | ePOD Admin + Fixed Text: This is user-maintained as customer details with a customer code of "SOS" (i.e. matching the site code for the system). The email addresses for Sales & Hire and Accounts will come from the customer contact and email. There is no mapping for the web site so this will be fixed text. |
Document title | Fixed text: "DELIVERY NOTE", "HIRE DELIVERY NOTE" or "COLLECTION NOTE" depending on the job type (Delivery / Collection) and job group. Deliveries for Job Group "Hire" are counted as hire delivery notes. |
Logo | ePOD Admin: This is the site logo maintained by uploading the company logo image into the Site screen in ePOD. |
Document No. | ePOD Admin: This will be called the "Delivery Note No." or "Collection Note No." depending on the job type (Delivery / Collection). The number is taken from the JOB ID in ePOD (a unique number generated by ePOD for each job). |
Account No | ePOD Admin: The Customer ID |
Order No | ePOD Admin: The Customer Ref from the job, entered by the user |
Contract No | ePOD Admin: The Sales No. from the job, entered by the user |
Date | ePOD Mobile: The date when the delivery / collection was confirmed. |
Customer | The customer name & address for the customer ID on the job (i.e. invoice address) |
Delivery / Collection Address | Imported EPOD_JOB (multiple fields): The job address. This will be called "Delivered To:" or "Collected From:" depending on the job type (Delivery / Collection). |
Detail Section
Item | Sourced from |
Description | ePOD Admin: Product description (short description: max 40 characters) |
Stock No. | ePOD Admin: Product code |
Qty Shipped | ePOD Admin: The product's Planned quantity |
Qty Delivered / Collected | ePOD Mobile: the quantity confirmed as delivered / collected by the driver. |
Footing Section
Item | Sourced from |
Customer Signature | ePOD Mobile: Customer signature. The name is entered on the job in ePOD Admin and can be changed when the customer signs for the delivery / collection. |
Terms And Conditions | ePOD Admin: Maintained on the Job Groups screen in the Terms & Conditions tab. |
Transfer Note Mapping
In ePOD, a transfer involves a collection job and delivery job both linked by the same job code on a Load. The Transfer Note can include information from both jobs. The mapping of the Transfer Note is the same as the Delivery / Collection Note except for these differences:
- In the heading section, the document title is "TRANSFER NOTE"
- Instead of the Customer (Invoice) Address, the collection address is printed for the collection job (so the collection and delivery addresses are both shown)
- In the detail section the quantity collected and delivered are shown as the actual quantity confirmed for the collection job and the delivery job
- In the footer section, the driver's signature from the collection job is also printed to the left of the customer's signature from the delivery job
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 | _____________________________ |