FS 343978 SCR-339867-08 Marshalls Landscape PODPOC Format
Marshalls Stone
Marshalls Landscape POD/POC Format
CALIDUS ePOD
5th July 2017 - 2.0
Reference: FS 343978 SCR-339867-08
Contents
Functional Overview
Client Requirement
SCR-339867-08 Marshalls Landscape POD/POC Format
Once jobs are completed, then will be confirmed with the C-ePOD server. After this confirmation, a POD/POC report may be produced.
These completion documents should show despatched and delivered quantity and should show all product lines on the order, whether they are cancelled or not.
Note: There are two POD/POC formats:
- One for Landscape.
- One for all other business units.
The original format contains a barcode for manual uploading of PODs into OnBase, when the documents are scanned. As the documents will no longer be scanned but electronically uploaded by C-ePOD, it has been agreed that this barcode will be removed.
Solution Overview
A Marshalls Landscape POD/POC format is required. The format of the POD note has been prototyped to show capability. The format has been provided and the prototype is shown below:
Scope
Changes will be made to latest version of CALIDUS ePOD only, and will require an update to all application components and full system and user acceptance testing.
Note: This specification covers the Marshalls Landscape POD/POC format only - the Premier Mortars format will be specified separately.
The definition of what data maps to which fields on the POD depends on the mapping of the interface of jobs into . As part of Import changes specified elsewhere, additional data will be received against the jobs so that it can be placed on the POD note.
All photos taken by the driver during the execution of the job (i.e. at cancellation of product, change quantity of product, job photos) will be displayed in the C-ePOD Admin system for the administrative users to view. Note: It is confirmed that photos taken with a job will not be added to the POD at any time (i.e. not for viewing, emailing or sending the report to OnBase). However, a subsequent change has been requested (but not yet confirmed) where these photos may be exported as a separate PDF to OnBase. Should this be required, the changes will be specified there.
This development is dependent on the following Marshalls changes:
- FS 343964 SCR-339876-02 Additional Landscape Data Import
- FS 343529 SCR-339867-07 Marshalls Premier Mortars PODPOC Format
These changes are referenced in Appendix B.
Set-up
Pre-requisites
Menu Structure
Data
The format attached to the job group is the format that will be produced from the Admin console and displayed for customers when requested through CALIDUS Portal.
UDF configuration for the Landscape site must be set as follows:
<FORM NAME="Returns" REQUIRED="Y"> <FIELD ID="UNLOAD_PALLETS"> <TEXT>Pallets Unloaded</TEXT> <FORMAT>N</FORMAT> <REQUIRED>Y</REQUIRED> <ACTION>N</ACTION> </FIELD> </FORM>
This can be configured through the Admin UDF Configuration screen:
Functional Description
Marshalls Landscape POD/POC Format
A Marshalls Landscape POD/POC note will be defined, using the Configurable POD format process within CALIDUS ePOD
The format created will have description "Marshalls Landscape" and will added to the list of POD/POC formats that can be selected from the Site and Job Group screens.
The format is populated as follows:
Page Header, expected to be displayed on every page:
Report Item | Data Fields | Description |
---|---|---|
Logo | EPOD_JOB_GROUPS.EPL_LOGO | It is expected that this will be the logo taken from the Job Group. If not present, this will default to the logo from the site. |
"Sales Order No:" | EPOD_JOB.EPL_JOB_CODE | The Marshalls order number, in Job Code. |
"Journey No / Drop No:" | EPOD_JOB.EPL_LOAD_ID + " / " + EPOD_JOB.EPL_SEQUENCE | The Load ID and Sequence. |
"DELIVERY NOTE" | EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying "COLLECTION NOTE" if the job is a collection. |
"RECEIPT NOTE TO BE RETURNED TO" | EPOD_SITE_CUSTOMER | Taken from a customer record linked to the site. Comprising Name, Address Line 1 to 5 and Post Code. |
"CUSTOMER" | EPOD_CUSTOMER | The customer (invoice) address. Comprising Name, Address Line 1 to 5, Post Code and the telephone. |
"DELIVERY ADDRESS" | EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying "COLLECTION ADDRESS" if the job is a collection. |
"DELIVERY ADDRESS" | EPOD_JOB_ADDRESS | The job address if present, otherwise the customer address. Comprising Name, Address Line 1 to 5, Post Code and the telephone. Font in red. |
"Journey No / Drop:" | EPOD_JOB.EPL_LOAD_ID + " / " + EPOD_JOB.EPL_SEQUENCE | The Load ID and Sequence. |
"Order Number" | EPOD_JOB.EPL_JOB_CODE | The Marshalls order number, in Job Code. |
"Del Date" | EPOD_JOB.EPL_START_PLANNED_DATE | The planned Start date. |
"Del Time" | EPOD_JOB.EPL_START_PLANNED_TIME + " - " + EPOD_JOB.EPL_END_PLANNED_TIME | The planned start time and end time. |
"Customer Req" | EPOD_JOB.EPL_CUST_REF | The customer's reference. |
"Customer Account" | EPOD_JOB.EPL_CUSTOMER_CODE | The customer code. |
"Haulier" | EPOD_JOB.EPL_HAULIER | From the new data received on the job. |
"Registration" | EPOD_VEHICLE.EPL_VEHICLE_REG | The vehicle that completed the trip. |
"Transport Group" | EPL_TRANSPORT_GROUP | From the new data received on the job. |
"Driver's Helpline" | Fixed text. |
Initial header, displayed on the first page only:
Report Item | Data Fields | Description |
---|---|---|
EPOD_JOB.EPL_JOB_INSTRUCTION | Any special instructions provided. |
Product Details, expected to be shown on every page, expected to show up to 12 products per page. Note: This section should show all product lines on the order, whether they are cancelled or not.
Report Item | Data Fields | Description |
---|---|---|
"Pick Code" | EPOD_PRODUCT.EPL_PRODUCT_CODE | The product code. |
"Quantity" | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL | The actual delivered quantity. |
(Blank Column) | EPOD_PRODUCT.EPL_UNIT_TYPE | The unit type (UOM) as sent, for example, m2, num, plt, ton. |
"Pack Size" | EPOD_PRODUCT.EPL_PRODUCT_QTY_CASE | The case quantity. |
"Item" | EPOD_PRODUCT.EPL_DESCRIPTION + " " + EPOD_PRODUCT.EPL_DESCRIPTION_LONG |
The item description, plus the long description. |
"Total Packs" | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL / EPOD_PRODUCT.EPL_PRODUCT_QTY_CASE | The delivered quantity integer divided by the case quantity. |
"Loose Items" | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL % EPOD_PRODUCT.EPL_PRODUCT_QTY_CASE | The remainder of the delivered quantity from the above calculation (the delivered quantity mod by the case quantity). |
"Tonnes" | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL * EPOD_PRODUCT.EPL_PRODUCT_WEIGHT | The delivered quantity multiplied by the unit weight. |
A total line will be produced, showing the totals of:
- "Total Packs" - sub-totalled from the "Total Packs" column.
- "Loose Items" - sub-totalled from the "Loose Items" column.
- "Tonnes" - sub-totalled from the "Tonnes" column.
Footer, expected to be shown on the last page only:
Report Item | Data Fields | Description |
---|---|---|
"I have received the materials listed" | Fixed text. | |
"Print Name" | EPOD_JOB.EPL_CUST_SIGNATORY | Customer signatory as entered by the driver. |
"Vehicle Reg" | EPOD_VEHICLE.EPL_VEHICLE_REG | The vehicle that completed the load. |
"Number of Pallets Unloaded" | EPOD_JOB.EPL_UDF_JOBDETS.UNLOAD_PALLETS | As entered by the driver. |
"Signature" | EPOD_JOB.EPL_JOB_SIGNATURE | The customer signature. |
"Delivery Date:" | EPOD_JOB.EPL_END_ACTUAL_DATE | The actual delivery date. |
CE Logo | Fixed image embedded in the page header as Base64-encoded image. | |
All other footer text | Fixed text. |
Note: It is expected that the POC format would be similar to the POD format (usually replacing "Deliver" with "Collect" and other similar words).
Note: The configurable report format requires several changes to perform as required for this format:
- The replaceDataTags method is modified so that Calculations are not formatted.
- If a date or a time is null or the field does not exist, then the time should return as 0.
- When a date is formatted (in EPOD_UTILS), the format should be assumed to be CALIDUS format when reading, then formatted into the required format parameter.
These changes should be completed as part of the Premier Mortars POD/POC report, specified as part of change 343529 SCR-339867-07 Marshalls Premier Mortars PODPOC Format.
Appendix A: TEST PLAN
Test Script / Scenario Reference | Marshalls Landscape POD/POC Format | Call Number(s): 343978 SCR-339867-08 |
Test Script / Scenario Description | Testing the new Marshalls Landscape POD/POC report format | PASS / ISSUES / FAIL |
Menu Access | Administration/Jobs/Report | |
Pre-requisites | A system configured as Marshalls. | Tested By: |
Test Objective | To test that the report is produced in the required format. | Date: |
Step | Action | Result | Remarks | P/F |
1 | Admin System | |||
Ensure that there are jobs complete with all requisite data (from import and from processing). | ||||
1.01 | In the jobs screen, find a completed job for Landscape and run the report. | The report is displayed as expected. |
Appendix B: Quote & Document References
Cost Details | ||||
Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
Requirements | 0.00 | 0.00 | 750 | £0.00 |
Change Request Evaluation | 0.00 | 0.00 | 750 | £0.00 |
Functional Specification | 0.75 | 0.50 | 750 | £375.00 |
Technical Specification | 0.00 | 0.00 | 750 | £0.00 |
Development | 2.50 | 1.00 | 750 | £750.00 |
Testing and Release | 0.25 | 0.25 | 750 | £187.50 |
Implementation | 0.25 | 0.25 | 750 | £187.50 |
Project Management | 0.25 | 0.25 | 750 | £187.50 |
TOTAL | 4.00 | 2.25 | £1,687.50 |
Estimate excludes training, release to live and go live support. |
B.1 References
Ref No | Document Title & ID | Version | Date |
1 | REQ 339867 Marshalls Premier Mortars Solution Design | 1.3 | 25/05/2017 |
2 | FS 343964 SCR-339876-02 Additional Landscape Data Import | 1.0 | 28/05/2017 |
3 | FS 343529 SCR-339867-07 Marshalls Premier Mortars PODPOC Format | 1.1 | 20/06/2017 |
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
Matt Turner | OBSL Account Manager | _____________________________ |
Simon Martin | Customer Representative | _____________________________ |
Debbie Linley | Customer Representative | _____________________________ |