FS 343529 SCR-339867-07 Marshalls Premier Mortars PODPOC Format
Marshalls Stone
Marshalls Premier Mortars POD/POC Format
CALIDUS ePOD
20th June 2017 - 1.1
Reference: FS 343529 SCR-339867-07
Contents
Functional Overview
Client Requirement
SCR-339867-07 Marshalls Premier Mortars 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 Premier Mortars.
- 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.
The original Premier Mortars format allowed for Comments to be seen from the driver. It has been agreed that this will be modified to remove the 'Comments' label and driver comments from the format - it is not required on an electronic POD format.
Solution Overview
A Premier Mortars 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:
Premier Mortars POD Format
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 Premier Mortars POD/POC format only - the Landscape format will be specified separately.
There will certainly be less than 10 products to a job, most commonly a maximum of 6, ensuring that there will only be a single page for this report.
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 343516 SCR-339867-06 Unmanned Location Process
- FS 343365 SCR-339867-01 Additional Premier Data Import
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 is for the products are as follows:
<FORM NAME="Product Details" REQUIRED="Y">
<FIELD ID="SITE_CONE_READING">
<TEXT>Site Cone Reading</TEXT>
<FORMAT>DDL</FORMAT>
<REQUIRED>Y</REQUIRED>
<ACTION>N</ACTION>
<ITEMS>
<ITEM CODE="12" DEFAULT="N" PHOTO_COUNT="0">12 or below</ITEM>
<ITEM CODE="13" DEFAULT="N" PHOTO_COUNT="0">13</ITEM>
<ITEM CODE="14" DEFAULT="N" PHOTO_COUNT="0">14</ITEM>
<ITEM CODE="15" DEFAULT="N" PHOTO_COUNT="0">15</ITEM>
<ITEM CODE="16" DEFAULT="N" PHOTO_COUNT="0">16</ITEM>
<ITEM CODE="17" DEFAULT="N" PHOTO_COUNT="0">17</ITEM>
<ITEM CODE="18" DEFAULT="N" PHOTO_COUNT="0">18 or above</ITEM>
</ITEMS>
</FIELD>
</FORM>
Functional Description
Marshalls Premier Mortars POD/POC Format
A Marshalls Premier POD/POC note will be defined, using the Configurable POD format process within CALIDUS ePOD
The format created will have description "Marshalls Premier Mortars" 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, to be displayed on every page:
| Report Item | Data Fields | Description |
|---|---|---|
| CE Logo | Fixed image embedded in the page header as Base64-encoded image. | |
| "DELIVERY NOTE" | EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying "COLLECTION NOTE" if the job is a collection. |
| Logo | EPOD_JOB_GROUPS.EPL_LOGO | The logo taken from the Job Group. If not present, this will default to the logo from the site. |
| Depot Address | EPOD_SITE_CUSTOMER | Taken from a customer record linked to the site. |
| "Customer Name" | EPOD_CUSTOMER.EPL_CUSTOMER_NAME | the customer name. |
| "Account Number" | EPOD_CUSTOMER.EPL_CUSTOMER_CODE | the customer code. |
| "Deliver To" (Label) | EPOD_JOB.EPL_JOB_TYPE | "Deliver To" or Collect From, based on the job type. |
| "Deliver To" (Data) | EPOD_JOB_ADDRESS | the job address if present, otherwise the customer address. Including the contact name and telephone. |
| "Sales Order" | EPOD_JOB.EPL_JOB_CODE | the Marshalls order number, in Job Code. |
| "Trip" | [EPOD_JOB.EPL_LOAD_ID] | the Load ID. |
| "Loading Point" | EPOD_JOB.EPL_LOAD_LOCATION | from the new import data. |
| "Vehicle Reg" | EPOD_VEHICLE.EPL_VEHICLE_REG | the vehicle that completed the trip. |
| "Date" | EPOD_JOB.EPL_END_ACTUAL_DATE | the actual end date |
| "Sales Contact" | EPOD_JOB.EPL_SALES_CONTACT | the contact that took the order. |
| "Telephone" | EPOD_JOB.EPL_SALES_TEL | the phone number of the sales contact. |
| "Cust Ref" | EPOD_JOB.EPL_CUST_REF | the customer's reference. |
| "Special Instructions" | EPOD_JOB.EPL_JOB_INSTRUCTION | any special instructions provided. |
| "Mortar: EN998-2..." | fixed text. |
Product Details, 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 |
|---|---|---|
| "Item" | EPOD_PRODUCT.EPL_PRODUCT_CODE | The product code. |
| "Description" | EPOD_PRODUCT.EPL_DESCRIPTION EPOD_PRODUCT.EPL_REASON_CODE |
The product description. If there is a reason code assigned to the product, the reason for the change or cancellation will be provided as a second line under the product description. |
| "Qty Despatched" | EPOD_PRODUCT.EPL_PRODUCT_QTY_PLANNED | The planned quantity of the product being delivered. |
| "Qty Delivered" | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL | The actual quantity of the product delivered, as confirmed by the driver. |
| (Blank Column) | EPOD_PRODUCT.EPL_ITEM_TYPE | the unit type. |
| "Hopper" | EPOD_PRODUCT.EPL_POSITION | the hopper for the product, entered in AX and sent to C-ePOD in a new field. |
| "Depot" | EPOD_PRODUCT.EPL_DEPOT_TEST | the depot cone test for the product, entered in AX and sent to C-ePOD in a new field. |
| "Site" | EPOD_PRODUCT.EPL_UDF.SITE_CONE_READING | the site cone test for the product, entered by the driver. |
Page Footer, to be shown on all pages:
| Report Item | Data Fields | Description |
|---|---|---|
| "Driver Signature for Out of Hours" | EPOD_JOB.EPL_ENG_SIGNATURE | Note: Signature image changed based on Unmanned Location process, specified elsewhere. If the driver signature is present, it will be displayed here.
|
| "Customer Name" | EPOD_JOB.EPL_CUST_SIGNATORY | the entered customer signatory, if present. |
| "Signature" | EPOD_JOB.EPL_JOB_SIGNATURE | Note: Signature image changed based on Unmanned Location process, specified elsewhere. The customer signature if present.
|
| "Date Loaded:" | EPOD_JOB.EPL_COL_DATE | from the new data received on the job. |
| "Time Loaded:" | EPOD_JOB.EPL_COL_TIME | from the new data received on the job. |
| "Delivery Date:" | EPOD_JOB.EPL_END_PLANNED_DATE | the actual planned date. |
| "Delivery Time:" | EPOD_JOB.EPL_END_PLANNED_TIME | Either the planned time or "AM"/"PM", if sent in the service level. |
| "Time on Site:" | EPOD_JOB.EPL_ARRIVAL_TIME | the start (arrival) time of the job in C-ePOD. |
| "Time Off Site:" | EPOD_JOB.EPL_END_ACTUAL_TIME | the end time of the job in C-ePOD. |
| "Waiting Time:" | See above | the start (arrival) time minus the end time in minutes. |
| 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.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | Marshalls Premier Mortars POD/POC Format | Call Number(s): 343529 SCR-339867-07 |
| Test Script / Scenario Description | Testing the new Marshalls Premier Mortars 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 Premier Mortars and run the report. | The report is displayed as expected. Specifically, check that the Waiting time is calculated and displayed correctly, that the dates are present and formatted as required, that the new data from the import is displayed correctly, and that the Product UDF data entered |
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 | 2.00 | 750 | £1,500.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 | 3.25 | £2,437.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 |
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 | _____________________________ |
