FS 304709 Partnerlink POD Format

From Calidus HUB
Revision as of 10:44, 22 August 2013 by Anw (talk | contribs) (Added and updated images)





Aptean Logo.png







PartnerLink

Partnerlink POD Format

CALIDUS ePOD

19th August 2013 - 0.1
Reference: FS 304709











































Functional Overview

Client Requirement

Produce a POD format that is based closely on the following format. Ensure that the pallets delivered are shown on the report.

FS 304709 4.PNG

Solution Overview

A POD report format will be produced.

This format will be configurable against the Partners.

Scope

  • These changes will be made in the latest version of the CALIDUS ePOD system.
  • It is noted that this change will be split into two phases.
    • Phase 1 will include all except the Consignee address and Collection Date.
    • Phase 2 will complete the delivery.

Set-up

Pre-requisites

Menu Structure

None

Data

Functional Description

Database Changes

DAL Changes

Partnerlink File Import Changes

POD Report Format

Fields on the POD report:

  • Partnerlink Logo - removed if this is a Palletforce job (EPL_JOB_GROUP = "PALLET")
  • Customer - EPL_CUSTOMER_CODE
  • Consignment Details - EPL_JOB_CODE
  • Consignor - the address of the consignor (collection address). For Phase 1, this will be labelled as "By" and will show the Site address (operating partner).
    • Company - EPL_CUSTOMER_NAME of EPL_CUSTOMER
    • Address - EPL_ADDRESS_LINE_1/2/3/4/5 of EPL_CUSTOMER
    • Postcode - EPL_POST_CODE of EPL_CUSTOMER
    • Phone - EPL_PHONE_NO of EPL_CUSTOMER
  • Deliver To - the delivery address.
    • Company - EPL_CUSTOMER_NAME of EPL_CUSTOMER
    • Address - EPL_ADDRESS_LINE_1/2/3/4/5 of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
    • Postcode - EPL_POST_CODE of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
    • Phone - EPL_PHONE_NO of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
  • Driver - EPL_DRIVER_NAME of EPOD_DRIVER
  • Vehicle - EPL_VEHICLE_REG of EPOD_VEHICLE
  • Track Num - EPL_EXT_REF
  • Trailer Number - EPL_TRAILER_ID
  • Col Date - New field - excluded in phase 1
  • Manifest Title - removed
  • Manifest Number - EPL_LOAD_ID
  • Del Date - EPL_START_PLANNED_DATE
  • Service - EPL_SERVICE
  • Del Time - EPL_START_PLANNED_TIME
  • Conditions - Hard-coded
  • Customer Ref - EPL_CUST_REF
  • Customer Ref2 - EPL_SO_REF
  • Barcode - removed
  • Consignment Instructions - EPL_JOB_INSTRUCTION
  • Total Packs - Calculated from number of the job's container records (not including loose products)
  • Total Weight - subtotalled from EPL_GROSS_WEIGHT of the job's container records (not including loose products)
  • Cubic - removed
  • Consignee Signature - EPL_SIGNATURE
  • Printed Name - EPL_SIGNATORY
  • Date - EPL_END_ACTUAL_DATE
  • Arrival Time - EPL_ARRIVAL_TIME
  • Departure Time - EPL_END_ACTUAL_TIME

Note Note: All fields are from EPOD_JOB unless otherwise specified.

The customer also required that the status of the pallets delivered should be shown on the note. Due to this, and the slight changes to the content of the note shown above, the note has been redesigned as a A4 document, where the existing format (slightly modified for space) is the header of the document, followed by a list of pallets, their status and and descriptive text associated to them, as in the prototype shown.

FS 304709 2.PNG

  • Item - EPL_CONTAINER_ID
  • Status - EPL_STATUS (translated)
  • Notes - EPL_USER_NOTES (if claused) else EPL_REASON_CODE and EPL_DESCRIPTION of EPOD_REASON_CODE

Note Note: All fields are from EPOD_CONTAINER unless otherwise specified. Developer Notes:

  • As there is a possibility that the number of containers will exceed that allowable on a page, the format should be written as a paginated document. The style of this should be copied from previous examples (e.g. ALS.aspx.cs).
  • 30 lines should be allowed per page.
  • The Container list should be recognised as the Detail portion of the document, the rest seen as the header.
  • The header should be shown on each page, ensuring that the signature is shown at all times.


Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
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


Andrew Allison
Client Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_304709_Partnerlink_POD_Format&oldid=1165’