REQ 354402 ABC POD and POC Layout and Mapping
From Calidus HUB
Anchor Bay Construction
POD and POC Layout and Mapping
CALIDUS ePOD
22nd March 2019 - 1.0
Reference: REQ 354402
Contents
Overview
This document describes the proposed layout and field mapping for the POD / POC (Proof of Delivery / Collection) document to be developed for Anchor Bay Construction. This document has been written in a manner such that it can be approved by non-technical representatives of Anchor Bay Construction 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 information provided by Anchor Bay Construction in emails and points clarified and confirmed in subsequent emails.
- The changes will be made in the latest version of the CALIDUS ePOD system.
POC and POD Layouts
This section shows the proposed layout of the POD (Proof of Delivery) and POC (Proof of Collection) document, with annotated notes for clarification.
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 document is on the following pages.
- POD Document is the delivery note
- POC Document is the collection note
POD Document
POC Document
POD and POC Mapping
These notes refer to the annotated layouts on the previous pages.
POD Mapping
Upper Heading Section
| Item | Sourced from |
| Company Name & Address | ePOD Admin: This is user-maintained as customer details with a customer code of "ABC" (matching the site code for the system), including the VAT number, phone, fax and email of the main address. |
| Document title | Fixed text: "Delivery Note" |
| Logo | ePOD Admin: This is maintained by uploading the logo image into the Job Group in ePOD. (Note: a new sub-company Forsite will come on board in the near future; this will use these same POD and POC layouts but will run as a separate site, which will allow it to have a different company name & address and logo on the documents) |
Lower Heading Section
| Item | Sourced from |
| Delivery Address | Imported EPOD_JOB (multiple fields): EPL_CUSTOMER_CODE, EPL_CUSTOMER_NAME, EPL_ADDRESS_1, EPL_ADDRESS_2, EPL_ADDRESS_3, EPL_ADDRESS_4, EPL_ADDRESS_5, EPL_POSTCODE |
| Invoice Address | Imported: EPOD_JOB: EPOD_CUSTOMER (contains multiple fields) |
| Date | ePOD Mobile: the date that the delivery job was completed (Actual Date) |
| Page | Page number |
| Shipment No | Imported: EPOD_JOB: EPL_JOB_CODE. This is the Anchor Bay Construction job number which must be unique for each job. |
| Customer No | Imported: EPL_CUSTOMER_CODE. This is the Anchor Bay internal reference code for the customer. |
| PO Number | Imported: EPL_CUST_REF. This is the customer’s order number. |
| Salesperson | Imported: EPL_SALES_CONTACT. This is the Anchor Bay sales person name or ID. |
Delivery Detail Section
| Item | Sourced from |
| Qty Shipped | Imported: EPOD_PRODUCT: EPL_PRODUCT_QTY_PLANNED. The quantity despatched. |
| Item Number | Imported: EPOD_PRODUCT: EPL_PRODUCT_CODE. The product identifier. |
| Description | Imported: EPOD_PRODUCT: EPL_DESCRIPTION. |
| Unit of Measure | Imported: EPOD_PRODUCT: EPL_UNIT_TYPE. |
| Qty Delivered | ePOD Mobile: the quantity confirmed as delivered by the driver. |
| Total Weight | Imported: Calculated as EPOD_PRODUCT: EPL_PRODUCT_WEIGHT multiplied by Qty Delivered. Note that this reflects the actual quantity confirmed by the driver, not the quantity shipped. |
| Short Reason | ePOD Mobile: The reason code the driver entered when shorting or cancelling an item on the delivery. Reason codes are user-maintained in ePOD Admin. |
| Qty to Follow | Imported: Calculated as EPOD_PRODUCT: EPL_QTY_ORDERED minus EPOD_PRODUCT: EPL_PRODUCT_QTY_PLANNED. Note that this reflects the quantity backordered at time of shipping and not any shortages or cancellations on delivery. |
Footing Section
| Item | Sourced from |
| Customer Signature | ePOD Mobile: Customer signature. The name can be imported in EPOD_JOB: EPL_CONTACT and changed at sign-off. The Company / badge number will be captured as a user-defined field (UDF) on the customer signature screen. |
| Terms And Conditions | ePOD Admin: Maintained on the Job Groups screen in the Terms & Conditions tab. |
| Tot Weight | Calculated: Sum of Total Weight for all delivered items. Note that, if the delivery note runs to 2 or more pages, this will only be printed on the last page. |
POC Mapping
Upper Heading Section
| Item | Sourced from |
| Company Name & Address | (See POD Mapping above) |
| Document title | Fixed text: "Collection Note" |
| Logo | (See POD Mapping above) |
Lower Heading Section
| Item | Sourced from |
| Collection Address | Imported EPOD_JOB (multiple fields): EPL_CUSTOMER_CODE, EPL_CUSTOMER_NAME, EPL_ADDRESS_1, EPL_ADDRESS_2, EPL_ADDRESS_3, EPL_ADDRESS_4, EPL_ADDRESS_5, EPL_POSTCODE, EPL_TELEPHONE |
| Notes | Imported: EPOD_JOB: EPL_JOB_INSTRUCTIONS. (Note that the driver also sees these job instructions on the mobile device when starting the job). |
| Date | ePOD Mobile: the date that the collection job was completed (Actual Date) |
| Page | Page number |
| Cust Return No | Imported: EPOD_JOB: EPL_JOB_CODE. This is the Anchor Bay Construction collection reference, which must be unique for each job. |
| Customer No | (See POD Mapping above) |
| Relates to Shipment No | Imported: EPL_CUST_REF. This is the customer’s order number. |
Delivery Detail
| Item | Sourced from |
| Item Number | Imported: EPOD_PRODUCT: EPL_PRODUCT_CODE. The product identifier. |
| Description | Imported: EPOD_PRODUCT: EPL_DESCRIPTION. |
| Unit of Measure | Imported: EPOD_PRODUCT: EPL_UNIT_TYPE. |
| Qty Collected | ePOD Mobile: the quantity confirmed as delivered by the driver. |
Footing
| Item | Sourced from |
| Driver Signature | ePOD Mobile: Driver signature. The name will be pre-displayed as the driver’s name from ePOD Admin. |
| Customer Signature | ePOD Mobile: Customer signature. The name can be imported in EPOD_JOB: EPL_CONTACT and changed at sign-off. The Company will be captured as a user-defined field (UDF) on the customer signature screen. |
| Terms And Conditions | ePOD Admin: Maintained on the Job Groups screen in the Terms & Conditions tab. |
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 | _____________________________ |
