REQ 305796 Partnerlink EPOD Solution: Difference between revisions

From Calidus HUB
VisualWikitext
(v0.1 - Initial Creation)
 
(Added Import section details)
Line 32: Line 32:
== Scope and Limitations ==
== Scope and Limitations ==
This document is based on the documentation provided by {{#var:ClientName}}, as referred to in the appendices, as well as information gleaned from site visits and workshops with {{#var:ClientName}}.
This document is based on the documentation provided by {{#var:ClientName}}, as referred to in the appendices, as well as information gleaned from site visits and workshops with {{#var:ClientName}}.
<!-- ANY scope or limitations, bulleted. -->
<!-- ANY scope or limitations, bulleted. -->
*The changes will be made in the latest version of the {{#var:System}} system.
*The changes will be made in the latest version of the {{#var:System}} system.
<!-- ANY other systems? e.g. does this link to TTM, WMS, 414, 770, etc? -->
{{ #vardefine: SCR | 0 }}
{{ #vardefine: SCR | 0 }}
<!-- NEW PAGE -->  
<!-- NEW PAGE -->  
= Client Requirements =
= Client Requirements =
Listed below are the proposed processes that will be followed by the operatives using {{#var:System}}. Also shown are the changes required for this to be achieved.  
Listed below are the proposed processes that will be followed by the operatives using {{#var:System}}. Also shown are the changes required for this to be achieved.  


== General Changes ==
== General Changes ==
Line 55: Line 51:
|Definition=Change "Container" to "Pallet" on the device
|Definition=Change "Container" to "Pallet" on the device
}}
}}


== Importing Data ==
== Importing Data ==
Line 64: Line 58:
* Stirling
* Stirling
The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system:
The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system:
* {{warning}} list new items here
Some of the above are additional items, and the system will be modified to accept these new items.


A basic list of all the fields in the interface for Load (Manifest) and Job follows. A full spreadsheet of all the import flows and fields containing all the limitations on length and defaulted values is provided separately and issued to all TMS suppliers.
 
'''EPOD_LOAD'''
<table border="1" width="100%"><tr>
<td bgcolor="silver" width="15%">Name</td><td bgcolor="silver" width="35%">Description</td><td bgcolor="silver" width="15%">External Field</td><td bgcolor="silver" width="35%">Notes</td></tr><tr>
<td>EPL_SITE_ID</td><td>EPL_SITE_ID: Unique reference of the site that the Load belongs to.</td><td>Partner Code</td><td>Partner Code of the partner executing the load.</td></tr><tr>
<td>EPL_LOAD_ID</td><td>EPL_LOAD_ID: Unique reference of the Load.</td><td>Manifest_No</td><td>The manifest number or Consolidated Manifest No</td></tr><tr>
<td>EPL_LOAD_START_PLANNED_DATE</td><td>&nbsp;</td><td>&nbsp;</td><td>These times will be defaulted by the EPOD system to the earliest and latest dates and times against the jobs provided, unless this information can be provided by the TMS</td></tr><tr>
<td>EPL_LOAD_START_PLANNED_TIME</td><td>&nbsp;</td><td>&nbsp;</td><td>No times will be provided for jobs. Therefore ETA will only start to be shown after the first job is started.</td></tr><tr>
<td>EPL_LOAD_END_PLANNED_DATE</td><td>&nbsp;</td><td>&nbsp;</td><td>As above</td></tr><tr>
<td>EPL_LOAD_END_PLANNED_TIME</td><td>&nbsp;</td><td>&nbsp;</td><td>As above</td></tr><tr>
<td>EPL_LOAD_DISTANCE_PLANNED</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr><tr>
<td>EPL_USER_ID</td><td>To be used if a user is predefined as assigned to complete this LOAD.</td><td>Driver Code</td><td>User to whom load assigned</td></tr><tr>
<td>'''EPL_VEHICLE_ID'''</td><td>To be used if a vehicle is predefined as assigned to complete this LOAD.</td><td>Vehicle</td><td>&nbsp;</td></tr><tr>
<td>'''EPL_TRAILER_ID'''</td><td>To be used if the vehicle above is a Tractor unit, and requires a trailer ID. This can be left blank to have this entered by the driver on demand.</td><td>?</td><td>Provided if the vehicle requires a trailer ID and one is known. Otherwise left blank.</td></tr><tr>
<td>EPOD_JOBS</td><td>EPOD_JOBS contains a series of EPOD_JOB objects.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
</table>
 
'''EPOD_JOB'''
<table border="1" width="100%"><tr>
<td bgcolor="silver" width="15%">Name</td><td bgcolor="silver" width="35%">Description</td><td bgcolor="silver" width="15%">External Field</td><td bgcolor="silver" width="35%">Notes</td></tr>
<tr><td>EPL_SITE_ID</td><td>Unique Reference for the Site that the Job belongs to</td><td>partner code</td><td>Expected at this time to be one of "L01" to "L04"</td></tr>
<tr><td>EPL_LOAD_ID</td><td>Unique Reference for the Load that the Job belongs to. If not provided, defaulted from the enclosing EPOD_LOAD</td><td>Manifest_No</td><td>From the load record.</td></tr>
<tr><td>EPL_JOB_ID</td><td>Unique reference for the job. If not provided, this will be generated by EPOD</td><td>&nbsp;</td><td>Omitted - generated by EPOD</td></tr>
<tr><td>EPL_JOB_CODE</td><td>External reference for the Job. This element can be used to link a collection and delivery together under the same reference. So, if an order is being collected at A and delivered at B, there are 2 jobs, each with a unique Job ID, but with the same Job Code. Optionally, EPOD will keep the Delivery leg of a linked job updated with the information captured from the collection.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_JOB_TYPE</td><td>D=Delivery, C=Collection, S=Service</td><td>"C" or "D"</td><td>&nbsp;</td></tr>
<tr><td>EPL_JOB_GROUP</td><td>&nbsp;</td><td>partner code</td><td>&nbsp;</td></tr>
<tr><td>EPL_CUST_REF</td><td>Customer's Order Reference</td><td>Ref2</td><td>&nbsp;</td></tr>
<tr><td>EPL_JOB_INSTRUCTION</td><td>Instructions for the Driver</td><td>Notes1+Notes2</td><td>&nbsp;</td></tr>
<tr><td>EPL_OFFICE_INSTRUCTION</td><td>Instructions for Admin staff</td><td>Notes3+Notes4</td><td>&nbsp;</td></tr>
<tr><td>EPL_START_PLANNED_DATE</td><td>&nbsp;</td><td>Del_Date</td><td>If winroute in use, this can be provided.</td></tr>
<tr><td>EPL_START_PLANNED_TIME</td><td>&nbsp;</td><td>Time</td><td>May be defaulted to a time based on SLA. May be omitted.</td></tr>
<tr><td>EPL_END_PLANNED_DATE</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_END_PLANNED_TIME</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_DISTANCE_PLANNED</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPOD_CUSTOMER</td><td>This tag may be used to specify a Customer separately. If this is used, and the address and contact information on the job below is different, the EPOD system will create a Job Address specifically for this job, whilst maintaining the Customer information separately, as an Invoice address.<br />Note that this will happen if the Customer has been created previously either through another Job, another Customer Tag in a Job or a Customer Tag alone.</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_CUSTOMER_CODE</td><td>Customer Code from external system. If not provided, one will be generated from EPL_CUSTOMER_NAME</td><td>account_code</td><td>&nbsp;</td></tr>
<tr><td>EPL_CUSTOMER_NAME</td><td>The Name of the customer</td><td>Del_Name</td><td>For collections, these values would be the Collection values, i.e. Col_Name, Col_post, etc.</td></tr>
<tr><td>EPL_ADDRESS_1</td><td>&nbsp;</td><td>Del_addr1</td><td>etc</td></tr>
<tr><td>EPL_ADDRESS_2</td><td>&nbsp;</td><td>Del_addr2</td><td>&nbsp;</td></tr>
<tr><td>EPL_ADDRESS_3</td><td>&nbsp;</td><td>Del_addr3</td><td>&nbsp;</td></tr>
<tr><td>EPL_ADDRESS_4</td><td>&nbsp;</td><td>Del_addr4</td><td>&nbsp;</td></tr>
<tr><td>EPL_ADDRESS_5</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_POSTCODE</td><td>&nbsp;</td><td>Del_post</td><td>Col_post</td></tr>
<tr><td>EPL_CONTACT</td><td>Contact on site for the job. Can be changed at Job completion.</td><td>""</td><td>This field is always to be sent blank, to force the users to enter a contact on the PDA client.</td></tr>
<tr><td>EPL_TELEPHONE</td><td>The Customer's Contact Telephone number</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_EMAIL</td><td>Contact Email address. Can be used to automatically send Job Completion documents to the customer.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_OWNER_NAME</td><td>Can be used as a display field for documentation</td><td>(owning) partner code</td><td>Need to set this as the partner that owns the job (i.e. a JobShare job) rather than the partner who is executing the job.</td></tr>
<tr><td>EPL_SO_NUMBER</td><td>Sales Order Reference.</td><td>Ref3</td><td>&nbsp;</td></tr>
<tr><td>EPL_ORDER_DATE</td><td>Date Order created - defaulted to Now()</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_SALES_CONTACT</td><td>The operative who took the order. Can be used as a display field for documentation</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_SERVICE_LEVEL</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>'''EPL_SEQUENCE'''</td><td>The sequence in which the jobs are to be completed. If this is not provided, the system will allocate the jobs in the sequence in which they were provided in this interface i.e. first is "0001", second is "0002", etc.</td><td>&nbsp;</td><td>This is to be set by the TMS or defaulted by EPOD</td></tr>
<tr><td>'''EPL_TRAILER_ID'''</td><td>To be used if the vehicle being used to fulfil the job is a Tractor unit, and requires a trailer ID. This can be left blank to have this entered by the driver on demand.</td><td>&nbsp;</td><td>May be sent, if the vehicle requires a trailer ID and this is known at the time that the job is sent.</td></tr>
<tr><td>EPOD_CONTAINERS</td><td>Contains a series of EPOD_CONTAINER objects</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPOD_PRODUCTS</td><td>Contains a series of EPOD_PRODUCT objects</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPOD_SERVICE</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
</table>
 
'''EPOD_CONTAINER'''
<table border="1" width="100%"><tr>
<td bgcolor="silver" width="15%">Name</td><td bgcolor="silver" width="35%">Description</td><td bgcolor="silver" width="15%">External Field</td><td bgcolor="silver" width="35%">Notes</td></tr>
<tr><td>EPL_SITE_ID</td><td>&nbsp;</td><td>Partner Code</td><td>Defaulted</td></tr>
<tr><td>EPL_JOB_ID</td><td>&nbsp;</td><td>&nbsp;</td><td>From Job record</td></tr>
<tr><td>EPL_CONTAINER_ID</td><td>EPL_CONTAINER_ID: The unique identifier for a container.</td><td>Label_ID</td><td>Actually from the tracking id (an id for each pallet to be delivered).</td></tr>
<tr><td>EPL_SEQUENCE</td><td>The sequence in which the containers should be unloaded.</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_CONTAINER_PACKAGE_CODE</td><td>Container Type Code</td><td>EF/EH/EQ/SF/SH/SQ</td><td>Not required</td></tr>
<tr><td>EPL_CONTAINER_PACKAGE_DESC</td><td>Container Type Description</td><td>EURO FULL, etc</td><td>Not required</td></tr>
<tr><td>EPL_GROSS_WEIGHT</td><td>Gross weight of the container</td><td>Kilos</td><td>Not required, but may be useful?</td></tr>
<tr><td>EPL_DESCRIPTION_LONG</td><td>Long description of the container</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_CODE_1</td><td>Additional code field used for any purpose</td><td>Spaces</td><td>Number of spaces taken on the vehicle. Required for documentation.</td></tr>
<tr><td>EPL_CODE_2</td><td>Additional code field used for any purpose</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPL_CODE_3</td><td>Additional code field used for any purpose</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>EPOD_PRODUCTS</td><td>EPOD_PRODUCTS contains a series of EPOD_PRODUCT objects associated to the container.</td><td>&nbsp;</td><td>Not used</td></tr>
</table>
 
Notes:
* Jobs with planned start dates and times should be sent through on the message.
* Jobs without planned start dates and times, but with a service level agreement against them i.e. AM or PM deliveries, should have the time defaulted appropriately. For example:
** AM - set to 11:59
** PM - set to 16:59
* Jobs without any planned start times or service level agreements should leave the time unset (i.e. blank).
* The jobs should be sent through in the order in which they should be completed. The Sequence field should be sent with a numeric padded value as described in the description.
* Loads and the contained jobs will be sent as one message. Multiple loads can be built into one XML message structure.
* XSDs for validating the XML structure will be provided.
* At this time, it is unknown whether this is a complete list of changes. This document will be modified and re-issued if required.
 
Items above in '''bold''' are additional items, and the system will be modified to accept these new items.
 
{{Note}} It is not deemed necessary at this time to map interfaces from the TMSs for Standing Data, as it was agreed that this would be maintained separately and manually within {{#var:System}}. Those flows are:
* Vehicles
* Reason Codes (used when cancelling jobs or pallets)
* Users (Drivers)
* Customers
The system will be configured to automatically create the Vehicles and Users with very basic information based off the received values in the Load and Job messages. Customers will be created as part of the information received through the Job messages.
 
== Logging In ==
== Logging In ==


Revision as of 17:41, 30 January 2013





Aptean Logo.png







Partnerlink

Partnerlink ePOD Solution

CALIDUS ePOD

30th January 2013 - 0.1
Reference: REQ 305796











































Introduction

This document is the Partnerlink ePOD Solution document.

Objective

The primary purpose of this document is to document the requirements gathered from Partnerlink, at meetings held in the Kinghts of Old offices on 22-24th January, 2012

This document has been written in a manner such that it can be approved by non-technical representatives of Partnerlink 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 the documentation provided by Partnerlink, as referred to in the appendices, as well as information gleaned from site visits and workshops with Partnerlink.

  • The changes will be made in the latest version of the CALIDUS ePOD system.

Client Requirements

Listed below are the proposed processes that will be followed by the operatives using CALIDUS ePOD. Also shown are the changes required for this to be achieved.

General Changes

A number of changes have been requested to the general styling of all areas of the system - the details are shown here:

  • SCR SCR-305796-1: Ensure that the correct Partnerlink logo is displayed on the device.
  • SCR SCR-305796-2: Change "Container" to "Pallet" on the device

Importing Data

Note Note: CALIDUS ePOD will be accepting data imports from 3 systems initially:

  • Vigo
  • Mandata
  • Stirling

The exact formats of the data uploads from the various systems are still being decided. However, there is a requirement that certain data items are passed into the system:

A basic list of all the fields in the interface for Load (Manifest) and Job follows. A full spreadsheet of all the import flows and fields containing all the limitations on length and defaulted values is provided separately and issued to all TMS suppliers.

EPOD_LOAD

NameDescriptionExternal FieldNotes
EPL_SITE_IDEPL_SITE_ID: Unique reference of the site that the Load belongs to.Partner CodePartner Code of the partner executing the load.
EPL_LOAD_IDEPL_LOAD_ID: Unique reference of the Load.Manifest_NoThe manifest number or Consolidated Manifest No
EPL_LOAD_START_PLANNED_DATE  These times will be defaulted by the EPOD system to the earliest and latest dates and times against the jobs provided, unless this information can be provided by the TMS
EPL_LOAD_START_PLANNED_TIME  No times will be provided for jobs. Therefore ETA will only start to be shown after the first job is started.
EPL_LOAD_END_PLANNED_DATE  As above
EPL_LOAD_END_PLANNED_TIME  As above
EPL_LOAD_DISTANCE_PLANNED  N/A
EPL_USER_IDTo be used if a user is predefined as assigned to complete this LOAD.Driver CodeUser to whom load assigned
EPL_VEHICLE_IDTo be used if a vehicle is predefined as assigned to complete this LOAD.Vehicle 
EPL_TRAILER_IDTo be used if the vehicle above is a Tractor unit, and requires a trailer ID. This can be left blank to have this entered by the driver on demand.?Provided if the vehicle requires a trailer ID and one is known. Otherwise left blank.
EPOD_JOBSEPOD_JOBS contains a series of EPOD_JOB objects.  

EPOD_JOB

NameDescriptionExternal FieldNotes
EPL_SITE_IDUnique Reference for the Site that the Job belongs topartner codeExpected at this time to be one of "L01" to "L04"
EPL_LOAD_IDUnique Reference for the Load that the Job belongs to. If not provided, defaulted from the enclosing EPOD_LOADManifest_NoFrom the load record.
EPL_JOB_IDUnique reference for the job. If not provided, this will be generated by EPOD Omitted - generated by EPOD
EPL_JOB_CODEExternal reference for the Job. This element can be used to link a collection and delivery together under the same reference. So, if an order is being collected at A and delivered at B, there are 2 jobs, each with a unique Job ID, but with the same Job Code. Optionally, EPOD will keep the Delivery leg of a linked job updated with the information captured from the collection.  
EPL_JOB_TYPED=Delivery, C=Collection, S=Service"C" or "D" 
EPL_JOB_GROUP partner code 
EPL_CUST_REFCustomer's Order ReferenceRef2 
EPL_JOB_INSTRUCTIONInstructions for the DriverNotes1+Notes2 
EPL_OFFICE_INSTRUCTIONInstructions for Admin staffNotes3+Notes4 
EPL_START_PLANNED_DATE Del_DateIf winroute in use, this can be provided.
EPL_START_PLANNED_TIME TimeMay be defaulted to a time based on SLA. May be omitted.
EPL_END_PLANNED_DATE  N/A
EPL_END_PLANNED_TIME  N/A
EPL_DISTANCE_PLANNED  N/A
EPOD_CUSTOMERThis tag may be used to specify a Customer separately. If this is used, and the address and contact information on the job below is different, the EPOD system will create a Job Address specifically for this job, whilst maintaining the Customer information separately, as an Invoice address.
Note that this will happen if the Customer has been created previously either through another Job, another Customer Tag in a Job or a Customer Tag alone.		 N/A
EPL_CUSTOMER_CODECustomer Code from external system. If not provided, one will be generated from EPL_CUSTOMER_NAMEaccount_code 
EPL_CUSTOMER_NAMEThe Name of the customerDel_NameFor collections, these values would be the Collection values, i.e. Col_Name, Col_post, etc.
EPL_ADDRESS_1 Del_addr1etc
EPL_ADDRESS_2 Del_addr2 
EPL_ADDRESS_3 Del_addr3 
EPL_ADDRESS_4 Del_addr4 
EPL_ADDRESS_5  N/A
EPL_POSTCODE Del_postCol_post
EPL_CONTACTContact on site for the job. Can be changed at Job completion.""This field is always to be sent blank, to force the users to enter a contact on the PDA client.
EPL_TELEPHONEThe Customer's Contact Telephone number  
EPL_EMAILContact Email address. Can be used to automatically send Job Completion documents to the customer.  
EPL_OWNER_NAMECan be used as a display field for documentation(owning) partner codeNeed to set this as the partner that owns the job (i.e. a JobShare job) rather than the partner who is executing the job.
EPL_SO_NUMBERSales Order Reference.Ref3 
EPL_ORDER_DATEDate Order created - defaulted to Now()  
EPL_SALES_CONTACTThe operative who took the order. Can be used as a display field for documentation N/A
EPL_SERVICE_LEVEL  N/A
EPL_SEQUENCEThe sequence in which the jobs are to be completed. If this is not provided, the system will allocate the jobs in the sequence in which they were provided in this interface i.e. first is "0001", second is "0002", etc. This is to be set by the TMS or defaulted by EPOD
EPL_TRAILER_IDTo be used if the vehicle being used to fulfil the job is a Tractor unit, and requires a trailer ID. This can be left blank to have this entered by the driver on demand. May be sent, if the vehicle requires a trailer ID and this is known at the time that the job is sent.
EPOD_CONTAINERSContains a series of EPOD_CONTAINER objects  
EPOD_PRODUCTSContains a series of EPOD_PRODUCT objects N/A
EPOD_SERVICE  N/A

EPOD_CONTAINER

NameDescriptionExternal FieldNotes
EPL_SITE_ID Partner CodeDefaulted
EPL_JOB_ID  From Job record
EPL_CONTAINER_IDEPL_CONTAINER_ID: The unique identifier for a container.Label_IDActually from the tracking id (an id for each pallet to be delivered).
EPL_SEQUENCEThe sequence in which the containers should be unloaded.  
EPL_CONTAINER_PACKAGE_CODEContainer Type CodeEF/EH/EQ/SF/SH/SQNot required
EPL_CONTAINER_PACKAGE_DESCContainer Type DescriptionEURO FULL, etcNot required
EPL_GROSS_WEIGHTGross weight of the containerKilosNot required, but may be useful?
EPL_DESCRIPTION_LONGLong description of the container  
EPL_CODE_1Additional code field used for any purposeSpacesNumber of spaces taken on the vehicle. Required for documentation.
EPL_CODE_2Additional code field used for any purpose  
EPL_CODE_3Additional code field used for any purpose  
EPOD_PRODUCTSEPOD_PRODUCTS contains a series of EPOD_PRODUCT objects associated to the container. Not used

Notes:

  • Jobs with planned start dates and times should be sent through on the message.
  • Jobs without planned start dates and times, but with a service level agreement against them i.e. AM or PM deliveries, should have the time defaulted appropriately. For example:
    • AM - set to 11:59
    • PM - set to 16:59
  • Jobs without any planned start times or service level agreements should leave the time unset (i.e. blank).
  • The jobs should be sent through in the order in which they should be completed. The Sequence field should be sent with a numeric padded value as described in the description.
  • Loads and the contained jobs will be sent as one message. Multiple loads can be built into one XML message structure.
  • XSDs for validating the XML structure will be provided.
  • At this time, it is unknown whether this is a complete list of changes. This document will be modified and re-issued if required.

Items above in bold are additional items, and the system will be modified to accept these new items.

Note Note: It is not deemed necessary at this time to map interfaces from the TMSs for Standing Data, as it was agreed that this would be maintained separately and manually within CALIDUS ePOD. Those flows are:

  • Vehicles
  • Reason Codes (used when cancelling jobs or pallets)
  • Users (Drivers)
  • Customers

The system will be configured to automatically create the Vehicles and Users with very basic information based off the received values in the Load and Job messages. Customers will be created as part of the information received through the Job messages.

Logging In

Vehicle Checks

Job List

SCR SCR-305796-3: Layout changes to the Job List screen
SCR SCR-305796-4: Allow force updating of a Load from the Job List screen
SCR SCR-305796-5: Resequence Jobs


Job Details

SCR SCR-305796-6: Remove facility to Cancel a Job
SCR SCR-305796-7: Force viewing of Special Instructions on Starting Job
SCR SCR-305796-8: Allow force updating of a Job while in progress


Delivery

SCR SCR-305796-9: Allow back-out of a job after Arrival

Collection

Warning Warning: Collection with no containers - allow Notes entry at all times.

Job Confirmation

SCR SCR-305796-10: Allow Customer to Clause delivery items

Completion of a Load (Manifest)

Job Completion Documents

SCR SCR-305796-11: Create POD Formats (Generic and Palletforce)

Exporting Data

SCR SCR-305796-12: Automatically email on cancellation of a job only

Note Note: CALIDUS ePOD will be sending data exports to 4 systems initially, with up to 3 being informed of completion at any one time:

  • Vigo
  • Mandata
  • Stirling
  • Palletforce

The exact formats and methodologies of the data exports from the various systems are still being decided. However, there is a requirement that certain data items are passed out of the system:

  • Warning Warning: list new items here

Some of the above are additional items, and the system will be modified to accept these new items.

Additionally, the system will be required to export the POD/POC documents automatically in TIFF format. This will also be required for the Palletforce system.

SCR SCR-305796-13: Export POD document as TIFF through the existing Partnerlink processes.
SCR SCR-305796-14: Export POD document as TIFF to Palletforce system

The system will also be required to act as a data source for the CALIDUS TTM system. This will require all imported data and all updated and completed data to be exported. This will be through the existing ePOD-TTM interface, as described elsewhere.

However, there will also be amendments to this interface to allow for the specific functionality described in this document, namely:

  • Resequencing
  • Order In Progress (to recalculate ETAs)
  • Order Arrived
  • Warning Warning: any others?

Additional modifications will be made to TTM to allow it to access the POD document through a link. These are specified elsewhere.

SCR SCR-305796-15: Changes to ePOD-TTM interface

Out of Scope Changes

This section details functionality requested to be added to the process above, that is not within the scope of the project.

= Trailer IDs

SCR SCR-305796-16: Trailer ID changes


Appendix A: Table of SCRs and Ballpark Estimates

SCR#SystemAreaDescriptionEstimate (Days)Notes
1 System Affected Area Affected Description of change  First argument to "number_format" must be a number.  Any notes, numerically listed


Notes:

  1. Any high level ballpark estimates for development are based on the basic information provided and are subject to detailed design and creation of an SCR.
  2. <Further notes, referenced in the notes column of the grid above>


Appendix B: Document References

B.1 References

Ref NoDocument Title & IDVersionDate
1Reference10.101/01/2011


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


Phil Harding
OBS Project Manager		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=REQ_305796_Partnerlink_EPOD_Solution&oldid=986’