FS 305796 EPOD Vigo Interface: Difference between revisions

From Calidus HUB
VisualWikitext
(v0.2 - Ready for customer review)
 
(v0.3 - amendments following supplier discussions)
Line 4: Line 4:
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|EPOD Vigo Interface}}
{{#vardefine:Doc_Title|EPOD Vigo Interface}}
{{#vardefine:Version|0.2}}
{{#vardefine:Version|0.3}}
{{#vardefine:Date|25th January 2013}}
{{#vardefine:Date|18th February 2013}}
{{#vardefine:Reference|305796}}
{{#vardefine:Reference|305796}}
{{#vardefine:Year|2013}}
{{#vardefine:Year|2013}}
Line 33: Line 33:


== Solution Overview  ==
== Solution Overview  ==
The existing ''CALIDUS'' EPOD Interface format and transport mechanism will be used, both for exporting and importing of data.
A new interface to and from ''CALIDUS'' EPOD will be created. This will be heavily based around the existing JobShare interface.


The summary of the solution requirements are:
The summary of the solution requirements are:
* Standing Data (Vehicles, Users, Reason Codes, Job Groups, Sites) will be manually set up within ''CALIDUS'' ePOD - no automated drip-feed of this data will be entered into.
* Standing Data (Vehicles, Users, Reason Codes, Job Groups, Sites) will be manually set up within ''CALIDUS'' ePOD - no automated drip-feed of this data will be entered into.
* Sending of data to and receiving data from ''CALIDUS'' ePOD will be through the standard ePOD XML formats provided.
* Sending of data to ''CALIDUS'' ePOD will be through a new Partnerlink CSV format.
* The mechanism of sending and receiving data will be through Web Services
* Receiving data from ''CALIDUS'' ePOD will be through the OBS XML format.
* The mechanism of sending and receiving data will be through Flat File transfer via FTP.
* The sending of data to ''CALIDUS'' ePOD will be through a manual option within the Vigo system ("Send to ePOD").
* The sending of data to ''CALIDUS'' ePOD will be through a manual option within the Vigo system ("Send to ePOD").
* The Vigo system must merge of Delivery and Collection manifests into a single Consolidated Manifest when sending data.
* The Vigo system must merge of Delivery and Collection manifests into a single Consolidated Manifest when sending data.
* The Vigo system must sort the data by Type (Deliveries first, then Collections), the planned start time, if available, or sequence to be completed, as required by the customer (Partnerlink).
* The Vigo system must sort the data by Type (Deliveries first, then Collections), the planned start time, if available, or sequence to be completed, as required by the customer (Partnerlink).
* Once manifests have been sent to ''CALIDUS'' ePOD, any amendments to the manifests sent will be automatically re-exported, up to the point of completion of the job and manifest.
* Amendments to the manifests sent will not be automatically re-exported to ''CALIDUS'' ePOD - all amendments will be manually resent on demand by the user through the mechanism above.
* ''CALIDUS'' ePOD exporting of completed or cancelled jobs will be through a timed process, expected to be every 5 minutes.
* ''CALIDUS'' ePOD exporting of completed or cancelled jobs will be through a timed process, expected to be every 5 minutes.
Out of scope of this document:
Out of scope of this document:
Line 49: Line 50:
This will require the Vigo system to be modified as follows:
This will require the Vigo system to be modified as follows:
* Consolidate manifests that are assigned to the same user and vehicle onto a new Consolidated Manifest ID.
* Consolidate manifests that are assigned to the same user and vehicle onto a new Consolidated Manifest ID.
* Trigger the export of the Loads and Jobs at the request of a user, and automatically after this request whenever the manifest or job information changes, up to the point of completion of the job and manifest.
* Convert the information into an agreed CSV format (described here).
* Convert the information into an agreed XML format (described here).
* FTP or copy the file containing the CSV-formatted payload to an agreed folder.
* Connect to the ''CALIDUS'' EPOD Import web service and send the XML data as the payload to a SOAP request.
* Create a process for importing data back into the Vigo TMS from an XML flat file in the OBS XML format.
* Process the acknowledgement response effectively.
* Create a web service for importing data back into the Vigo TMS when complete.
* Process the payload provided by a SOAP request from ''CALIDUS'' EPOD (when jobs are completed or cancelled).
* Acknowledge the success or failure through the response format provided.


== Scope  ==
== Scope  ==
Line 68: Line 65:
* Users (Drivers)
* Users (Drivers)
* Customers
* 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.


A number of actions are outstanding from this meeting regarding the production of this interface specification, as follows:
A number of actions are outstanding from this meeting regarding the production of this interface specification, as follows:
* Partnerlink to send a screenshot of the main Vigo screen, so that it can be used in the specification for when the user will select to send the selected manifests to ePOD.
* Partnerlink to provide a list of existing Partner Codes in use.
* Partnerlink to provide a list of existing Partner Codes in use.
* Partnerlink to provide a document of the standard Reason Codes in use.
* Partnerlink to provide a document of the standard Reason Codes in use.
Line 81: Line 76:
== Pre-requisites  ==
== Pre-requisites  ==
* A working Vigo TMS and ''CALIDUS'' EPOD system must be in place.
* A working Vigo TMS and ''CALIDUS'' EPOD system must be in place.
* The two systems must be able to connect to the web services created, either through an internet or LAN connection.
* The two systems must be able to connect via FTP, either through an internet or LAN connection.


== Menu Structure  ==
== Menu Structure  ==
Line 99: Line 94:


[[File:FS-305796-Vigo-01.PNG|border]]
[[File:FS-305796-Vigo-01.PNG|border]]
{{Note}} If, at any point up to completion of a specific job or completion of the manifest, modifications are made to the manifests that have been sent to CALIDUS EPOD or the jobs contained within those manifests, they will be automatically resent with all details at the point that modifications are made.


== Creating the Messages ==
== Creating the Messages ==
Line 115: Line 108:
== Message Content ==
== Message Content ==


A basic list if 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.
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.


'''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>Del_Date</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>Time</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>Del_Date</td><td>As above</td></tr><tr>
<td>EPL_LOAD_END_PLANNED_TIME</td><td>&nbsp;</td><td>Time</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>
<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>
<td bgcolor="silver" width="5%">#</td><td bgcolor="silver" width="15%">Field Name</td><td bgcolor="silver" width="5%">Type</td><td bgcolor="silver" width="10%">Max Length</td><td bgcolor="silver" width="15%">Mapped Field</td><td bgcolor="silver" width="50%">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>AA: To provide a list. Expected at this time to be one of "L01" to "L04"</td></tr>
<tr><td>1</td><td>Requestor</td><td>C</td><td>3</td><td>(owning) partner code</td><td>Owning Partner - the partner that owns the JobShare job (if present), else the Delivery or Collection Partner, depending on Job Type</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. This may also be the Consolidated manifest number</td></tr>
<tr><td>2</td><td>Reference 1</td><td>C</td><td>7</td><td>Ref1</td><td>&nbsp;</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>3</td><td>Reference 2</td><td>C</td><td>16</td><td>Ref2</td><td>&nbsp;</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>Ref1</td><td>&nbsp;</td></tr>
<tr><td>4</td><td>Reference 3</td><td>C</td><td>16</td><td>Ref3</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>5</td><td>PartnerJobID</td><td>C</td><td>14</td><td>tracking_code</td><td>Is used to form the pallet ID of the pallets to be delivered (this field plus 2-digit count from 01 to Total Pallets)</td></tr>
<tr><td>EPL_JOB_GROUP</td><td>&nbsp;</td><td>partner code</td><td>&nbsp;</td></tr>
<tr><td>6</td><td>Job Date</td><td>C</td><td>8</td><td>&nbsp;</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>7</td><td>Collection Name</td><td>C</td><td>30</td><td>col_name</td><td>Collection details - required for POD note (Consignor address)</td></tr>
<tr><td>EPL_JOB_INSTRUCTION</td><td>Instructions for the Driver</td><td>Notes1+Notes2</td><td>&nbsp;</td></tr>
<tr><td>8</td><td>Collection Address 1</td><td>C</td><td>30</td><td>col_addr1</td><td>Collection details - required for POD note (Consignor address)</td></tr>
<tr><td>EPL_OFFICE_INSTRUCTION</td><td>Instructions for Admin staff</td><td>Notes3+Notes4</td><td>&nbsp;</td></tr>
<tr><td>9</td><td>Collection Address 2</td><td>C</td><td>30</td><td>col_addr2</td><td>Collection details - required for POD note (Consignor address)</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>10</td><td>Collection Address 3</td><td>C</td><td>30</td><td>col_addr3</td><td>Collection details - required for POD note (Consignor address)</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>11</td><td>Collection Address 4</td><td>C</td><td>30</td><td>col_addr4</td><td>Collection details - required for POD note (Consignor address)</td></tr>
<tr><td>EPL_END_PLANNED_DATE</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>12</td><td>Collection Postcode</td><td>C</td><td>10</td><td>col_post</td><td>Collection details - required for POD note (Consignor address)</td></tr>
<tr><td>EPL_END_PLANNED_TIME</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>13</td><td>Collection Contact</td><td>C</td><td>30</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_DISTANCE_PLANNED</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>14</td><td>Collection Phone Number</td><td>C</td><td>16</td><td>&nbsp;</td><td>Collection details - required for POD note (Consignor address)</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>15</td><td>Collecting Partner</td><td>C</td><td>3</td><td>partner code</td><td>Partner code of the partner executing the job (if it's a collection job type)</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>16</td><td>Collection Date</td><td>C</td><td>8</td><td>col_date</td><td>Planned Start Date</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>17</td><td>Collection Time</td><td>C</td><td>5</td><td>time</td><td>Planned Start Time</td></tr>
<tr><td>EPL_ADDRESS_1</td><td>&nbsp;</td><td>Del_addr1</td><td>etc</td></tr>
<tr><td>18</td><td>Delivery Name</td><td>C</td><td>30</td><td>del_name</td><td>Customer or Job Address</td></tr>
<tr><td>EPL_ADDRESS_2</td><td>&nbsp;</td><td>Del_addr2</td><td>&nbsp;</td></tr>
<tr><td>19</td><td>Delivery Address 1</td><td>C</td><td>30</td><td>del_addr1</td><td>Customer or Job Address</td></tr>
<tr><td>EPL_ADDRESS_3</td><td>&nbsp;</td><td>Del_addr3</td><td>&nbsp;</td></tr>
<tr><td>20</td><td>Delivery Address 2</td><td>C</td><td>30</td><td>del_addr2</td><td>Customer or Job Address</td></tr>
<tr><td>EPL_ADDRESS_4</td><td>&nbsp;</td><td>Del_addr4</td><td>&nbsp;</td></tr>
<tr><td>21</td><td>Delivery Address 3</td><td>C</td><td>30</td><td>del_addr3</td><td>Customer or Job Address</td></tr>
<tr><td>EPL_ADDRESS_5</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>22</td><td>Delivery Address 4</td><td>C</td><td>30</td><td>del_addr4</td><td>Customer or Job Address</td></tr>
<tr><td>EPL_POSTCODE</td><td>&nbsp;</td><td>Del_post</td><td>Col_post</td></tr>
<tr><td>23</td><td>Delivery Postcode</td><td>C</td><td>10</td><td>del_post</td><td>Customer or Job Address</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>24</td><td>Delivery Contact</td><td>C</td><td>30</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>25</td><td>Delivery Phone Number</td><td>C</td><td>16</td><td>phone</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>26</td><td>Delivery Partner</td><td>C</td><td>3</td><td>Partner Code</td><td>Partner code of the partner executing the job (if it's a delivery job type)</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>27</td><td>Delivery Date</td><td>C</td><td>8</td><td>del date</td><td>Planned Start Date</td></tr>
<tr><td>EPL_SO_NUMBER</td><td>Sales Order Reference.</td><td>Ref3</td><td>&nbsp;</td></tr>
<tr><td>28</td><td>Delivery Time</td><td>C</td><td>5</td><td>time</td><td>Planned Start Time</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>29</td><td>Number of Full Pallets</td><td>N</td><td>&nbsp;</td><td>full</td><td>Added to form Total Pallets</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>30</td><td>Number of Half Pallets</td><td>N</td><td>&nbsp;</td><td>half</td><td>Added to form Total Pallets</td></tr>
<tr><td>EPL_SERVICE_LEVEL</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>31</td><td>Number of Quarter Pallets</td><td>N</td><td>&nbsp;</td><td>qtr</td><td>Added to form Total Pallets</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>32</td><td>Number of OverSize Pallets</td><td>N</td><td>&nbsp;</td><td>osize</td><td>Added to form Total Pallets</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>33</td><td>Weight in Kilos</td><td>N</td><td>&nbsp;</td><td>kilos</td><td>Divided by Total Pallets to create a Weight per pallet</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>34</td><td>Manifest Notes 1</td><td>C</td><td>48</td><td>notes1</td><td>Job Instructions</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>35</td><td>Manifest Notes 1</td><td>C</td><td>48</td><td>notes2</td><td>Job Instructions</td></tr>
<tr><td>EPOD_SERVICE</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>36</td><td>Manifest Notes 1</td><td>C</td><td>48</td><td>notes3</td><td>Office Instructions</td></tr>
</table>
<tr><td>37</td><td>Manifest Notes 1</td><td>C</td><td>48</td><td>notes4</td><td>Office Instructions</td></tr>
 
<tr><td>38</td><td>Service</td><td>C</td><td>2</td><td>service</td><td>Service Level</td></tr>
'''EPOD_CONTAINER'''
<tr><td>39</td><td>Surcharges</td><td>C</td><td>16</td><td>surcharges</td><td>&nbsp;</td></tr>
<table border="1" width="100%"><tr>
<tr><td>40</td><td>Pallet Spaces</td><td>N</td><td>&nbsp;</td><td>spaces</td><td>&nbsp;</td></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>41</td><td>Number of Chep pallets</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_SITE_ID</td><td>&nbsp;</td><td>Partner Code</td><td>Defaulted</td></tr>
<tr><td>42</td><td>Hazardous</td><td>C</td><td>1</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_JOB_ID</td><td>&nbsp;</td><td>&nbsp;</td><td>From Job record</td></tr>
<tr><td>43</td><td>ADR Number</td><td>N</td><td>5.2</td><td>&nbsp;</td><td>N/A</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>44</td><td>Packing Group</td><td>C</td><td>10</td><td>&nbsp;</td><td>N/A</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>45</td><td>Category</td><td>C</td><td>10</td><td>&nbsp;</td><td>N/A</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>46</td><td>Product name</td><td>C</td><td>10</td><td>&nbsp;</td><td>N/A</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>47</td><td>UN Number</td><td>C</td><td>10</td><td>&nbsp;</td><td>N/A</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>48</td><td>24 Hour Phone Number</td><td>C</td><td>10</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>EPL_DESCRIPTION_LONG</td><td>Long description of the container</td><td>&nbsp;</td><td>&nbsp;</td></tr>
<tr><td>49</td><td>Number of Packs</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</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>50</td><td>Number of Litres</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</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>51</td><td>Weight in Kilos</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</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>52</td><td>Value 1</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</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>
<tr><td>53</td><td>Value 2</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>54</td><td>Value 3</td><td>N</td><td>&nbsp;</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>55</td><td>Spare Text 1</td><td>C</td><td>6</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>56</td><td>Job Bar Code</td><td>C</td><td>16</td><td>&nbsp;</td><td>N/A</td></tr>
<tr><td>57</td><td>Manifest Number</td><td>C</td><td>20</td><td>manifest_no</td><td>Load ID</td></tr>
<tr><td>58</td><td>Account Code</td><td>C</td><td>12</td><td>&nbsp;</td><td>required - unknown what this is.</td></tr>
<tr><td>59</td><td>Trailer Number</td><td>C</td><td>10</td><td>trailer</td><td>Trailer ID</td></tr>
<tr><td>*</td><td>Driver ID</td><td>C</td><td>10</td><td>&nbsp;</td><td>Driver to whom the job has been assigned</td></tr>
<tr><td>*</td><td>Vehicle ID</td><td>C</td><td>10</td><td>vehicle</td><td>&nbsp;</td></tr>
<tr><td>*</td><td>Job Type</td><td>C</td><td>2</td><td>&nbsp;</td><td>Identifying Collection "C" or Delivery "D"</td></tr>
<tr><td>*</td><td>PF Depot</td><td>C</td><td>3</td><td>&nbsp;</td><td>Palletforce depot code</td></tr>
<tr><td>*</td><td>PF Tracking Number</td><td>C</td><td>13</td><td>&nbsp;</td><td>Palletforce tracking number</td></tr>
</table>
</table>


Line 198: Line 185:
** PM - set to 16:59
** PM - set to 16:59
* Jobs without any planned start times or service level agreements should leave the time unset (i.e. blank).
* 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.
* The jobs should be sent through in the order in which they should be completed on the manifest.  
* 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.
A sample of a single load with multiple jobs is shown below:
<pre>
<EPOD_IMPORT EPL_SITE_ID="L03" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
  <EPOD_LOADS>
    <EPOD_LOAD>
      <EPL_SITE_ID>L03</EPL_SITE_ID>
      <EPL_LOAD_ID>258309</EPL_LOAD_ID>
      <EPL_LOAD_START_PLANNED_DATE>20121112</EPL_LOAD_START_PLANNED_DATE>
      <EPL_LOAD_START_PLANNED_TIME>09450000</EPL_LOAD_START_PLANNED_TIME>
      <EPL_LOAD_END_PLANNED_DATE>20121112</EPL_LOAD_END_PLANNED_DATE>
      <EPL_LOAD_END_PLANNED_TIME>09450000</EPL_LOAD_END_PLANNED_TIME>
      <EPL_USER_ID>pda</EPL_USER_ID>
      <EPL_VEHICLE_ID>33218</EPL_VEHICLE_ID>
      <EPL_TRAILER_ID></EPL_TRAILER_ID>
      <EPOD_JOBS>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0948464</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>L03</EPL_JOB_GROUP>
          <EPL_CUST_REF>0001903931</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>DEL 12/11 @ 0945 HRS REF CARL 2046517  WMD122</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME>09450000</EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>MAWDSLEY BROOKS &amp; CO LTD</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>UNIT 1, HAINGE PARK</EPL_ADDRESS_1>
          <EPL_ADDRESS_2>HAINGE ROAD</EPL_ADDRESS_2>
          <EPL_ADDRESS_3></EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>B69 2NY</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>GA026183/003</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0001</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094846401</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>120</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0945951</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>06/12/026963</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>3 PLTS  DEL. MON 12TH  ASAP  OPEN 8AM-4PM  2@ 120X100X210 1@120X100X150</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>SVEN MANUFACTURING</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>21</EPL_ADDRESS_1>
          <EPL_ADDRESS_2>FIRST AVENUE,PENSNETT TRADING</EPL_ADDRESS_2>
          <EPL_ADDRESS_3>KINGSWINFORD</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>DY6 7TU</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>POR TRLR B92CXR</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0002</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094595101</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>186</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094595102</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>186</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094595103</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>186</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0945953</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>06/12/026964</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>2 PLTS  DEL. ASAP MON 12TH OPEN 8AM-4PM 1@ 120X100X220  1@ 120X100X115</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>SVEN MANUFACTURING</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>21</EPL_ADDRESS_1>
          <EPL_ADDRESS_2>FIRST AVENUE,PENSNETT TRADING</EPL_ADDRESS_2>
          <EPL_ADDRESS_3>KINGSWINFORD</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>DY6 7TU</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>POR TRLR B92CXR</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0003</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094595301</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>205</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094595302</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>205</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0948551</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>1533960</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION> 49 BOX 2 PLT DEL 12/11 T/L  MW/LDS KIDD</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>CHURCH OF JESUS CHRIST LDS</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>6-8 BIRMINGHAM RD</EPL_ADDRESS_1>
          <EPL_ADDRESS_2></EPL_ADDRESS_2>
          <EPL_ADDRESS_3>KIDDERMINSTER</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>DY10 2BX</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>1030685</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0004</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094855101</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>451</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094855102</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>451</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>SE51237</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>14658843</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>DEL 12/11 </EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>MUSIC GROUP RESEARCH UK LTD</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>COPPICE TRADING ESTATE</EPL_ADDRESS_1>
          <EPL_ADDRESS_2></EPL_ADDRESS_2>
          <EPL_ADDRESS_3>KIDDERMINSTER</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>DY11 7HJ</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>750068</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0005</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063555015123701</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>228</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063555015123702</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>228</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063555015123703</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>228</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063555015123704</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>228</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0949219</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>222665</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>*T/LIFT DO NOT DOUBLE STACK* DEL 12/11 *ALL PAGES OF POD'S TO BE SIGNED &amp; RETURNED**</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>WILTS ELECTRICAL</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>UNIT 31</EPL_ADDRESS_1>
          <EPL_ADDRESS_2>KELVIN WAY</EPL_ADDRESS_2>
          <EPL_ADDRESS_3>WEST BROMWICH</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>B70 7TP</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>220772</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0006</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094921901</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>520</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>0948545</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>1551547</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION> 2 BOX 1 MIX DEL 12/11 REF: JAMES RODRIGUEZ  CC1134/0028/JR</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>CHURCH OF JESUS CHRIST LDS</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>6-8 BIRMINGHAM RD</EPL_ADDRESS_1>
          <EPL_ADDRESS_2></EPL_ADDRESS_2>
          <EPL_ADDRESS_3>KIDDERMINSTER</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>DY10 2BX</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER>1030685</EPL_SO_NUMBER>
          <EPL_SEQUENCE>0007</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063000094854501</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>36</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
        <EPOD_JOB>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_LOAD_ID>258309</EPL_LOAD_ID>
          <EPL_JOB_CODE>DA51425</EPL_JOB_CODE>
          <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
          <EPL_JOB_GROUP>KOO</EPL_JOB_GROUP>
          <EPL_CUST_REF>17685222</EPL_CUST_REF>
          <EPL_JOB_INSTRUCTION>8028816379/816370/816373/816376 PALLETS: 1  ITEMS: 7  TAILLIFT</EPL_JOB_INSTRUCTION>
          <EPL_START_PLANNED_DATE>20121112</EPL_START_PLANNED_DATE>
          <EPL_START_PLANNED_TIME></EPL_START_PLANNED_TIME>
          <EPL_CUSTOMER_NAME>NORTON CANES BUILDERS MERCHANT</EPL_CUSTOMER_NAME>
          <EPL_ADDRESS_1>WALLSALL ROAD, NORTON CANES</EPL_ADDRESS_1>
          <EPL_ADDRESS_2></EPL_ADDRESS_2>
          <EPL_ADDRESS_3>CANNOCK</EPL_ADDRESS_3>
          <EPL_ADDRESS_4></EPL_ADDRESS_4>
          <EPL_POSTCODE>WS11 9NS</EPL_POSTCODE>
          <EPL_CONTACT></EPL_CONTACT>
          <EPL_SO_NUMBER></EPL_SO_NUMBER>
          <EPL_SEQUENCE>0008</EPL_SEQUENCE>
          <EPL_TRAILER_ID></EPL_TRAILER_ID>
          <EPOD_CONTAINERS>
            <EPOD_CONTAINER>
              <EPL_SITE_ID>L03</EPL_SITE_ID>
              <EPL_CONTAINER_ID>063555015142501</EPL_CONTAINER_ID>
              <EPL_CONTAINER_PACKAGE_CODE>PALL</EPL_CONTAINER_PACKAGE_CODE>
              <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
              <EPL_GROSS_WEIGHT>207</EPL_GROSS_WEIGHT>
              <EPL_DESCRIPTION_LONG>Pallet</EPL_DESCRIPTION_LONG>
              <EPL_CODE_1>1</EPL_CODE_1>
            </EPOD_CONTAINER>
          </EPOD_CONTAINERS>
        </EPOD_JOB>
      </EPOD_JOBS>
    </EPOD_LOAD>
  </EPOD_LOADS>
</EPOD_IMPORT>
</pre>


== Sending Mechanism ==
== Sending Mechanism ==
The system provides web services for importing data.
The files can be
There are two mechanisms:
* Sent by the Vigo TMS via FTP to an FTP service hosted by OBS
* Passing the data as a string, through Web Service EPOD_dataservice.asmx
* Pulled by ''CALIDUS'' ePOD via FTP from an FTP service hosted by Vigo
* Passing the data as an XML object, through EPOD_dataservice2.asmx
* Copied by ''CALIDUS'' ePOD from a shared folder on the Vigo TMS
The IP or web address of the ''CALIDUS'' EPOD server is not mapped into the Partnerlink network at this time, so the exact URL is unknown. This will be confirmed at a later date, for testing purposes.
* Copied by ''CALIDUS'' ePOD from a shared folder on the ''CALIDUS'' ePOD system.
 
For each data service, data can be sent via multiple methods, as shown below:
* '''EPOD_dataservice.asmx'''
SOAP 1.1
 
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.
<pre>
POST /webservices/dataservice/EPOD_dataservice.asmx HTTP/1.1
Host: www.calidus-web.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "ePOD_DataService/EPOD_XML_IMPORT"
 
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <EPOD_XML_IMPORT xmlns="ePOD_DataService">
      <IMPORT>string</IMPORT>
    </EPOD_XML_IMPORT>
  </soap:Body>
</soap:Envelope>
 
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <EPOD_XML_IMPORTResponse xmlns="ePOD_DataService">
      <EPOD_XML_IMPORTResult>string</EPOD_XML_IMPORTResult>
    </EPOD_XML_IMPORTResponse>
  </soap:Body>
</soap:Envelope>
</pre>
SOAP 1.2
 
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.
<pre>
POST /webservices/dataservice/EPOD_dataservice.asmx HTTP/1.1
Host: www.calidus-web.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <EPOD_XML_IMPORT xmlns="ePOD_DataService">
      <IMPORT>string</IMPORT>
    </EPOD_XML_IMPORT>
  </soap12:Body>
</soap12:Envelope>
 
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <EPOD_XML_IMPORTResponse xmlns="ePOD_DataService">
      <EPOD_XML_IMPORTResult>string</EPOD_XML_IMPORTResult>
    </EPOD_XML_IMPORTResponse>
  </soap12:Body>
</soap12:Envelope>
</pre>
HTTP GET
 
The following is a sample HTTP GET request and response. The placeholders shown need to be replaced with actual values.
<pre>
GET /webservices/dataservice/EPOD_dataservice.asmx/EPOD_XML_IMPORT?IMPORT=string HTTP/1.1
Host: www.calidus-web.com
 
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<string xmlns="ePOD_DataService">string</string>
</pre>
HTTP POST
 
The following is a sample HTTP POST request and response. The placeholders shown need to be replaced with actual values.
<pre>
POST /webservices/dataservice/EPOD_dataservice.asmx/EPOD_XML_IMPORT HTTP/1.1
Host: www.calidus-web.com
Content-Type: application/x-www-form-urlencoded
Content-Length: length
 
IMPORT=string
 
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<string xmlns="ePOD_DataService">string</string>
</pre>
 
*'''EPOD_dataservice2.asmx'''
SOAP 1.1
 
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.
<pre>
POST /webservices/dataservice/EPOD_dataservice2.asmx HTTP/1.1
Host: www.calidus-web.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "ePOD_DataService/EPOD_XML_IMPORT"
 
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <EPOD_XML_IMPORT xmlns="ePOD_DataService">
      <IMPORT>xml</IMPORT>
    </EPOD_XML_IMPORT>
  </soap:Body>
</soap:Envelope>
 
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <EPOD_XML_IMPORTResponse xmlns="ePOD_DataService">
      <EPOD_XML_IMPORTResult>xml</EPOD_XML_IMPORTResult>
    </EPOD_XML_IMPORTResponse>
  </soap:Body>
</soap:Envelope>
</pre>
 
SOAP 1.2
 
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.
<pre>
POST /webservices/dataservice/EPOD_dataservice2.asmx HTTP/1.1
Host: www.calidus-web.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
 
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <EPOD_XML_IMPORT xmlns="ePOD_DataService">
      <IMPORT>xml</IMPORT>
    </EPOD_XML_IMPORT>
  </soap12:Body>
</soap12:Envelope>
 
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length


<?xml version="1.0" encoding="utf-8"?>
Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <EPOD_XML_IMPORTResponse xmlns="ePOD_DataService">
      <EPOD_XML_IMPORTResult>xml</EPOD_XML_IMPORTResult>
    </EPOD_XML_IMPORTResponse>
  </soap12:Body>
</soap12:Envelope>
</pre>


== Processing Responses ==
The files to be picked up will be named as follows:
The response data is an XML file (either string data or an XML object), as shown in the calling methods above. The result is governed by a schema, in the same way that the import files are. All XSD schemas will be provided to you.
* <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.csv
where
* <SENDER> is the system sending the file - expected to be "vigo"
* <RECEIVER> is the system receiving the file - expected to be "epod"
* <OPERATING_PARTNER> is the operating partner code, i.e. L02, L03, etc.
* <DATE> is the date in YYYYMMDD format
* <TIME> is the time in HHMMSSNN format
* <SEQ> is a unique counting sequence for each file created in a run.


The import processor will validate the entire file to the import schema. If this fails, the file will be rejected - all errors found will be exported in the response file.
No responses to the files shall be given - the receiving system (''CALIDUS'' ePOD in this case) will maintain an audit trail to be examined by the user on event of failure.


If the pre-process is successful, each record will then be attempted to be loaded. If any of these fail for any reason, the discovered error will be reported in the response file.
Each manifest should be sent in a separate file, to minimise disruption if a single file fails.


If the loading of all records proceeds without an issue, the acknowledged response will be sent.
The entire content of the file will fail if there is a problem with any content.
 
{{Note}} It is not recommended to attempt to resend files unless the errors have been investigated and resolved. This is the responsibility of the sending system or the users of that system to do this.
 
{{Note}} It is recommended that this XML Response fragment is stored for later auditing of potential issues.
 
{{Note}} The Result and Error tags will not be checked for content, only structure. Therefore these tags can contain any informative data that the producing system deems adequate for identifying issues.
 
An example of an Success and Failure response to an import into ''CALIDUS'' EPOD are shown below:
<pre>
<EPOD_IMPORT_RESPONSE RESULT="NAK">
    <ERRORS>
        <ERROR error="The element 'EPOD_LOAD' has invalid child element 'EPL_SITE_IDX'. List of possible elements expected: 'EPL_SITE_ID'." exception="System.Xml.Schema.XmlSchemaValidationException: The element 'EPOD_LOAD' has invalid child element 'EPL_SITE_IDX'. List of possible elements expected: 'EPL_SITE_ID'."/>
    </ERRORS>
</EPOD_IMPORT_RESPONSE>
</pre>
<pre>
<EPOD_IMPORT_RESPONSE RESULT="ACK">
    <RESULTS>
        <RESULT>
            <ID>Load: LOAD001</ID>
            <STATUS>Status: Load updated and at status C</STATUS>
        </RESULT>
        <RESULT>
            <ID>Job: JOB001</ID>
            <STATUS>Status: Job updated and at status P</STATUS>
        </RESULT>
        <RESULT>
            <ID>EPOD_CUSTOMER: Cust001</ID>
            <STATUS>Status: EPOD_CUSTOMER Updated</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB001-01</ID>
            <STATUS>Status: Container created on Job: JOB001</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB001-02</ID>
            <STATUS>Status: Container created on Job: JOB001</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB001-03</ID>
            <STATUS>Status: Container created on Job: JOB001</STATUS>
        </RESULT>
        <RESULT>
            <ID>Job: JOB002</ID>
            <STATUS>Status: Job updated and at status X</STATUS>
        </RESULT>
        <RESULT>
            <ID>EPOD_CUSTOMER: Cust001</ID>
            <STATUS>Status: EPOD_CUSTOMER Updated</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB002-01</ID>
            <STATUS>Status: Container created on Job: JOB002</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB002-02</ID>
            <STATUS>Status: Container created on Job: JOB002</STATUS>
        </RESULT>
        <RESULT>
            <ID>Container: JOB002-03</ID>
            <STATUS>Status: Container created on Job: JOB002</STATUS>
        </RESULT>
    </RESULTS>
</EPOD_IMPORT_RESPONSE>
</pre>


== Importing into ''CALIDUS'' EPOD ==
== Importing into ''CALIDUS'' EPOD ==
Line 806: Line 216:


The import into ''CALIDUS'' EPOD will be modified as follows:
The import into ''CALIDUS'' EPOD will be modified as follows:
* Vehicle ID will be created in advance on the load
* Vehicle ID will be created in advance
* If the vehicle does not exist, one will be created with basic information
* If the vehicle does not exist, one will be created with basic information
* The Vehicle data will be modified to hold whether this vehicle is a tractor.
* The Vehicle data will be modified to hold whether this vehicle is a tractor.
Line 1,003: Line 413:


== ''CALIDUS'' EPOD Export Mechanism ==
== ''CALIDUS'' EPOD Export Mechanism ==
The system will be configured to send to a web service, requiring a string (rather than an XML object) input.  
The files can be
*    Sent by the Vigo TMS via FTP to an FTP service hosted by OBS
*    Pulled by ''CALIDUS'' ePOD via FTP from an FTP service hosted by Vigo
*    Copied by ''CALIDUS'' ePOD from a shared folder on the Vigo TMS
*    Copied by ''CALIDUS'' ePOD from a shared folder on the ''CALIDUS'' ePOD system.
 
Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).
 
The files to be picked up will be named as follows:
 
*    <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_<TIME>_<SEQ>.csv
 
where


The identity of the web service will be defined by the Vigo team as part of this development.
*    <SENDER> is the system sending the file - expected to be "epod"
*    <RECEIVER> is the system receiving the file - expected to be "vigo"
*    <OPERATING_PARTNER> is the operating partner code, i.e. L02, L03, etc.
*    <DATE> is the date in YYYYMMDD format
*    <TIME> is the time in HHMMSSNN format
*    <SEQ> is a unique counting sequence for each file created in a run.  


Each job will be sent independently, resulting in a single call to the external web service to add this job.
No responses to the files shall be given - the receiving system (Vigo TMS in this case) will maintain an audit trail to be examined by the user on event of failure.


When the file is received and processed by the web service, the system expects the web service to respond in the format, as shown in previous sections. The exact same format and structure should be used as described here. The content may be as detailed as required by the Vigo system.
Each job will be sent in a separate file, to minimise disruption if a single file fails.
<!-- MEDIA LANDSCAPE NO -->  
<!-- MEDIA LANDSCAPE NO -->  
{{Doc_Appendix
{{Doc_Appendix
Line 1,015: Line 442:
|Estimate=N
|Estimate=N
|Glossary=EPOD
|Glossary=EPOD
|Ref1=EPOD Import Mapping v0.3.xlsx
|Ref1=JobShare Mapping v0.2.xlsx
|RefV1=0.3
|RefV1=0.2
|RefDate1=25/01/2013
|RefDate1=18/02/2013
|Ref2=EPOD Export Mapping v0.5.xlsx
|Ref2=EPOD Export Mapping v0.5.xlsx
|RefV2=0.5
|RefV2=0.5

Revision as of 14:07, 18 February 2013





Aptean Logo.png







PartnerLink

EPOD Vigo Interface

CALIDUS EPOD

18th February 2013 - 0.3
Reference: FS 305796











































Functional Overview

The document is intended to describe the exact requirements for the Vigo TMS system interfacing to and from the CALIDUS EPOD system.

Client Requirement

The requirements were captured from the Partnerlink staff on 18/01/2013, at the Kettering operation.

  • The Vigo system will send messages to the CALIDUS EPOD system to define Loads and Trips to be completed.
  • The CALIDUS EPOD system will inform the Vigo system that the jobs are completed or cancelled.

Note Note: There is also a requirement to interface an image of the generated POD document to all TMS systems being used by the PartnerLink partners. This will be covered in a separate document, as this will make use of the existing image upload processing available in the TMS systems.

Solution Overview

A new interface to and from CALIDUS EPOD will be created. This will be heavily based around the existing JobShare interface.

The summary of the solution requirements are:

  • Standing Data (Vehicles, Users, Reason Codes, Job Groups, Sites) will be manually set up within CALIDUS ePOD - no automated drip-feed of this data will be entered into.
  • Sending of data to CALIDUS ePOD will be through a new Partnerlink CSV format.
  • Receiving data from CALIDUS ePOD will be through the OBS XML format.
  • The mechanism of sending and receiving data will be through Flat File transfer via FTP.
  • The sending of data to CALIDUS ePOD will be through a manual option within the Vigo system ("Send to ePOD").
  • The Vigo system must merge of Delivery and Collection manifests into a single Consolidated Manifest when sending data.
  • The Vigo system must sort the data by Type (Deliveries first, then Collections), the planned start time, if available, or sequence to be completed, as required by the customer (Partnerlink).
  • Amendments to the manifests sent will not be automatically re-exported to CALIDUS ePOD - all amendments will be manually resent on demand by the user through the mechanism above.
  • CALIDUS ePOD exporting of completed or cancelled jobs will be through a timed process, expected to be every 5 minutes.

Out of scope of this document:

  • CALIDUS ePOD will be modified to export the POD/POC documents through the standard JobShare Image Upload system.

This will require the Vigo system to be modified as follows:

  • Consolidate manifests that are assigned to the same user and vehicle onto a new Consolidated Manifest ID.
  • Convert the information into an agreed CSV format (described here).
  • FTP or copy the file containing the CSV-formatted payload to an agreed folder.
  • Create a process for importing data back into the Vigo TMS from an XML flat file in the OBS XML format.

Scope

Note Note: There are modifications being made to the CALIDUS EPOD system, both for product enhancement and specifically for the Partnerlink customer that are driving changes into both the import and export functionality described here. Some have not yet been finalised. All known modifications to the schemas have been added to this document. Should any further requirements be known after this document is issued, this document will be revised and reissued at that time.

Note Note: Future modifications may be made to the exporting of data from CALIDUS EPOD to the Vigo system. When modifications of this nature are made, a new validation schema (XSD) for the XML payload will be issued. The modifications to the Vigo system to import this data should be made in such a way that this new XSD can be replaced into the system without program modifications in the future.

Note Note: It is not deemed necessary at this time to map interfaces from Vigo 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

A number of actions are outstanding from this meeting regarding the production of this interface specification, as follows:

  • Partnerlink to provide a list of existing Partner Codes in use.
  • Partnerlink to provide a document of the standard Reason Codes in use.
  • Partnerlink to update the spreadsheets (provided to map the import to and Export from ePOD) to indicate Vigo Table and Field Names, for inclusion in this document.

Until these actions are completed, the document will remain in draft form, unless authorised by the customer.

Set-up

Pre-requisites

  • A working Vigo TMS and CALIDUS EPOD system must be in place.
  • The two systems must be able to connect via FTP, either through an internet or LAN connection.

Menu Structure

None

Data

As described below.


Functional Description

Vigo Export

The export to the CALIDUS EPOD system will be made at the request of the Vigo user - the user will select an option from the screen which will send all selected manifests through to the CALIDUS EPOD system.

The following is a screen-shot of where this functionality is expected to be added.

FS-305796-Vigo-01.PNG

Creating the Messages

Should any manifests be available for sending at any time, and there are manifests for the same date that are allocated to the same driver, vehicle and trailer, Vigo will generate a Consolidated Manifest ID and assign this to the manifests that are linked. This will be a unique manifest number in itself, although does not have to be generated in the same format.

The purpose of this is so that some operations will link two manifests together, a set of deliveries, and a set of collections. As the customer requires these tasks to be executed by the same driver and interleave the collections among the deliveries if possible, they must be collected onto the same manifest.

This Consolidated Manifest number should be used to identify the Load for CALIDUS EPOD.

When manifests are consolidated in this way, the sorting of the data should be preserved, but the Delivery manifest jobs placed first on the consolidated manifest.

This functionality should be enabled through configuration within the Vigo system.

Message Content

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.

#Field NameTypeMax LengthMapped FieldNotes
1RequestorC3(owning) partner codeOwning Partner - the partner that owns the JobShare job (if present), else the Delivery or Collection Partner, depending on Job Type
2Reference 1C7Ref1 
3Reference 2C16Ref2 
4Reference 3C16Ref3 
5PartnerJobIDC14tracking_codeIs used to form the pallet ID of the pallets to be delivered (this field plus 2-digit count from 01 to Total Pallets)
6Job DateC8  
7Collection NameC30col_nameCollection details - required for POD note (Consignor address)
8Collection Address 1C30col_addr1Collection details - required for POD note (Consignor address)
9Collection Address 2C30col_addr2Collection details - required for POD note (Consignor address)
10Collection Address 3C30col_addr3Collection details - required for POD note (Consignor address)
11Collection Address 4C30col_addr4Collection details - required for POD note (Consignor address)
12Collection PostcodeC10col_postCollection details - required for POD note (Consignor address)
13Collection ContactC30""This field is always to be sent blank, to force the users to enter a contact on the PDA client.
14Collection Phone NumberC16 Collection details - required for POD note (Consignor address)
15Collecting PartnerC3partner codePartner code of the partner executing the job (if it's a collection job type)
16Collection DateC8col_datePlanned Start Date
17Collection TimeC5timePlanned Start Time
18Delivery NameC30del_nameCustomer or Job Address
19Delivery Address 1C30del_addr1Customer or Job Address
20Delivery Address 2C30del_addr2Customer or Job Address
21Delivery Address 3C30del_addr3Customer or Job Address
22Delivery Address 4C30del_addr4Customer or Job Address
23Delivery PostcodeC10del_postCustomer or Job Address
24Delivery ContactC30""This field is always to be sent blank, to force the users to enter a contact on the PDA client.
25Delivery Phone NumberC16phone 
26Delivery PartnerC3Partner CodePartner code of the partner executing the job (if it's a delivery job type)
27Delivery DateC8del datePlanned Start Date
28Delivery TimeC5timePlanned Start Time
29Number of Full PalletsN fullAdded to form Total Pallets
30Number of Half PalletsN halfAdded to form Total Pallets
31Number of Quarter PalletsN qtrAdded to form Total Pallets
32Number of OverSize PalletsN osizeAdded to form Total Pallets
33Weight in KilosN kilosDivided by Total Pallets to create a Weight per pallet
34Manifest Notes 1C48notes1Job Instructions
35Manifest Notes 1C48notes2Job Instructions
36Manifest Notes 1C48notes3Office Instructions
37Manifest Notes 1C48notes4Office Instructions
38ServiceC2serviceService Level
39SurchargesC16surcharges 
40Pallet SpacesN spaces 
41Number of Chep palletsN  N/A
42HazardousC1 N/A
43ADR NumberN5.2 N/A
44Packing GroupC10 N/A
45CategoryC10 N/A
46Product nameC10 N/A
47UN NumberC10 N/A
4824 Hour Phone NumberC10 N/A
49Number of PacksN  N/A
50Number of LitresN  N/A
51Weight in KilosN  N/A
52Value 1N  N/A
53Value 2N  N/A
54Value 3N  N/A
55Spare Text 1C6 N/A
56Job Bar CodeC16 N/A
57Manifest NumberC20manifest_noLoad ID
58Account CodeC12 required - unknown what this is.
59Trailer NumberC10trailerTrailer ID
*Driver IDC10 Driver to whom the job has been assigned
*Vehicle IDC10vehicle 
*Job TypeC2 Identifying Collection "C" or Delivery "D"
*PF DepotC3 Palletforce depot code
*PF Tracking NumberC13 Palletforce tracking number

Notes:

  • The Vigo Table and Field names have been provided by the Partnerlink team.
  • 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 on the manifest.

Sending Mechanism

The files can be

  • Sent by the Vigo TMS via FTP to an FTP service hosted by OBS
  • Pulled by CALIDUS ePOD via FTP from an FTP service hosted by Vigo
  • Copied by CALIDUS ePOD from a shared folder on the Vigo TMS
  • Copied by CALIDUS ePOD from a shared folder on the CALIDUS ePOD system.

Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).

The files to be picked up will be named as follows:

  • <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_

where

  • <SENDER> is the system sending the file - expected to be "vigo"
  • <RECEIVER> is the system receiving the file - expected to be "epod"
  • <OPERATING_PARTNER> is the operating partner code, i.e. L02, L03, etc.
  • <DATE> is the date in YYYYMMDD format
  • <SEQ> is a unique counting sequence for each file created in a run.

No responses to the files shall be given - the receiving system (CALIDUS ePOD in this case) will maintain an audit trail to be examined by the user on event of failure.

Each manifest should be sent in a separate file, to minimise disruption if a single file fails.

The entire content of the file will fail if there is a problem with any content.

Importing into CALIDUS EPOD

Note Note: This information is specified in detail in another document, but the bulleted information is listed here for completeness.

The import into CALIDUS EPOD will be modified as follows:

  • Vehicle ID will be created in advance
  • If the vehicle does not exist, one will be created with basic information
  • The Vehicle data will be modified to hold whether this vehicle is a tractor.
  • If vehicles are created through the import and a trailer ID is identified against the vehicle, the vehicle will be marked as a tractor, requiring Trailer entry.
  • The Load and Jobs data will be modified to hold the trailer ID against them.

CALIDUS EPOD Export Process

A process runs on a timed schedule within the CALIDUS EPOD application, to pick up any jobs that have been completed and export them to external systems.

The system be configured to ensure that updates are sent.

The exporting of this data will be modified to include:

  • Entered Trailer ID (at Job level).
  • Clause information (per pallet)

Note Note: Trailer ID and Clause modifications are out of scope of the existing solution being provided, but have been added here so that the systems can be prepared to handle this functionality when it becomes available.

CALIDUS EPOD Export Message Content

A basic list if all the fields in the interface for Job follows. A full spreadsheet of all the export flows and fields containing all the limitations on length and defaulted values is provided separately.

EPOD_JOB

NameDescriptionExternal FieldNotes
EPL_SITE_IDUnique Reference for the Site that the Job belongs topartner codeThis will be the Partner ID
EPL_JOB_IDUnique reference for the job. If not provided on Import, this will be generated by EPOD N/A
EPL_LOAD_IDUnique Reference for the Load that the Job belongs to. If not provided, defaulted from the enclosing EPOD_LOADManifest_NoAs Sent
EPL_JOB_TYPED=Delivery, C=Collection, S=Service"D" or "C"As Sent
EPL_JOB_GROUP partner codeThis will be the Partner ID
EPL_JOB_INSTRUCTIONInstructions for the DriverNotes1+Notes2As Sent
EPL_JOB_SIGNATUREThe signature taken from the customer when the job was completed. This is in the form of a Base64-encrypted Jpeg file x
EPL_REASON_CODEIf a job has been cancelled, the reason code entered by the user is held here. x
EPL_LINKED_REASONIf the job is a delivery, and a collection of the same load with the same EPL_JOB_CODE is cancelled, this delivery will be cancelled, and this field will be set to "Y" N/A
EPL_STATUSC- complete, X cancelled x
EPL_CUSTOMER_CODECustomer Code from external system. If not provided, one will be generated from EPL_CUSTOMER_NAMEAccount_CodeAs Sent
EPL_PHOTO_IDIf cancelled, a photo may have been taken by the user. If so, this field is populated with a unique ID. x
EPL_PHOTOThe photo taken for the exception. This is in the form of a Base64-encrypted Jpeg file x
EPL_ENG_SIGNATUREThe signature taken from the driver/engineer when the job was completed, if required. This is in the form of a Base64-encrypted Jpeg file x
EPL_SEQUENCEThe sequence of the job. This could be the sequence sent on Import, a pre-defined sequence (if one was not provided) or a user-changed value (if enabled)  
EPL_START_PLANNED_DATE Del_DateAs Sent
EPL_START_PLANNED_TIME TimeAs Sent
EPL_END_PLANNED_DATE Del_DateAs Sent
EPL_END_PLANNED_TIME TimeAs Sent
EPL_START_ACTUAL_DATEThe date the user actually chose to start the job. Format: YYYYMMDD x
EPL_START_ACTUAL_TIMEThe time the user actually chose to start the job. Format HHMMSSNN x
EPL_ARRIVED_DATE_TIMEThe date the user indicated they arrived at the destination. Format: YYYYMMDD x
EPL_ARRIVED_DATE_TIMEThe time the user indicated they arrived at the destination. Format HHMMSSNN x
EPL_END_ACTUAL_DATEThe date the user completed or cancelled the job. Format: YYYYMMDD x
EPL_END_ACTUAL_TIMEThe time the user completed or cancelled the job. Format HHMMSSNN x
EPL_DISTANCE_PLANNED  N/A
EPL_DISTANCE_ACTUAL  N/A
EPL_DRIVING_TIME  N/A
EPL_CUSTOMER_NAMEThe Name of the customerDel_NameAs Sent
EPL_JOB_ADDRESSA flag indicating whether this is a default Customer Address or a specific address for this job alone. N/A
EPL_ADDRESS_1 Del_addr1As Sent
EPL_ADDRESS_2 Del_addr2As Sent
EPL_ADDRESS_3 Del_addr3As Sent
EPL_ADDRESS_4 Del_addr4As Sent
EPL_ADDRESS_5  N/A
EPL_POSTCODE Del_postAs Sent
EPL_CONTACT Del_postAs Sent
EPL_TELEPHONE  As Sent
EPL_EMAIL  As Sent
EPL_INVOICED  N/A
EPL_CUST_SIGNATORYThe name of the customer signatory on the job. x
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.Ref1As Sent
EPL_CUST_REFCustomer's Order ReferenceRef2As Sent
EPL_OFFICE_INSTRUCTIONInstructions for Admin staffNotes3+Notes4As Sent
EPL_SIGNED_UNCHECKEDAn indication whether the customer signed for the goods without checking them first. Note that this field can be used for any check-box entry, as this is configurable. x
EPL_SO_NUMBERSales Order Reference.Ref3As Sent
EPL_TNCSAn XML fragment, displaying the Terms and Conditions agreed to by the customer when signing for the goods. This can also include up to 3 configurable check-boxes that the user may check. x
EPL_ORDER_DATEDate Order created - defaulted to the date the order was received if not provided N/A
EPL_SALES_CONTACTThe operative who took the order. Can be used as a display field for documentation N/A
EPL_USER_NOTESOptional Notes entered by the driver while completing the job. x
EPL_OWNER_NAME (owning) partner codeNeed to set this as partner owning job.
EPL_SERVICE_LEVEL  N/A
EPL_TRAILER_IDTo be used if the vehicle being used to fulfil the job is a Tractor unit, and a trailer ID has been entered by the user. x
EPL_LAST_CHANGED_DATE  N/A
EPL_LAST_CHANGED_TIME  N/A
EPOD_CONTAINERSContains a series of EPOD_CONTAINER objects, detailing all the deliverable items on this load. If there are loose products, there will also be a container with ID '000000000' holding these products. A collection of pallets that were part of the job, plus the status.
EPOD_SERVICEIf the job is a Service, this object holds all the service-related information. In that case, no containers or products will be specified against the job. N/A

EPOD_CONTAINER

NameDescriptionExternal FieldNotes
EPL_JOB_IDUnique reference for the job. If not provided on Import, this will be generated by EPOD  
EPL_CONTAINER_IDEPL_CONTAINER_ID: The unique identifier for a cotainer.Label_IDActually from the tracking id (an id for each pallet to be delivered).
EPL_SEQUENCEA sequence for the containers to be shown on the user's device. As Sent
EPL_CONTAINER_PACKAGE_CODE EF/EH/EQ/SF/SH/SQAs Sent
EPL_CONTAINER_PACKAGE_DESC EURO FULL, etcAs Sent
EPL_REASON_CODEIf a job has been cancelled, the reason code entered by the user is held here. x
EPL_LINKED_REASONIf the job is a delivery, and a collection of this container on the same load with the same EPL_JOB_CODE is cancelled, this container will be cancelled, and this field will be set to "Y" x
EPL_STATUSEPL_STATUS: Status of the current Container. C-Completed, X-Cancelled. x
EPL_PHOTO_IDIf cancelled, or received with a clause, a photo may have been taken by the user. If so, this field is populated with a unique ID. x
EPL_PHOTOThe photo taken for the exception. This is in the form of a Base64-encrypted Jpeg file x
EPL_CUST_COMMENTSOptional entry by the user, indicating whether the customer has identified an issue with the received item (a claused receipt). If present, the customer may have requested an image, which would be contained in EPL_PHOTO.  
EPL_DESCRIPTION_LONG  As Sent
EPL_CODE_1Multi-purpose fieldSpacesAs Sent
EPL_CODE_2Multi-purpose field As Sent
EPL_CODE_3Multi-purpose field As Sent
EPL_LAST_CHANGED_DATE  N/A
EPL_LAST_CHANGED_TIME  N/A
EPOD_PRODUCTSContains a series of EPOD_PRODUCTS objects, detailing the products within the container, or loose products N/A

Note Note: Fields identified with an 'x' are expected to be stored within the Vigo system. Neither the Partnerlink nor OBS teams know which fields are in use within Vigo to store this data, but this must be stored by the application.

Note Note: Regarding Signature and Photo data formats in this message: This data is stored and transmitted as a text string, Base64-encrypted. This data can be decoded and saved as binary data once received if required.

A sample of a single job with a single pallet is shown below: 

<EPOD_EXPORT_JOB>
  <EPOD_JOBS>
    <EPOD_JOB>
      <EPL_SITE_ID>L03</EPL_SITE_ID>
      <EPL_JOB_ID>0000000001</EPL_JOB_ID>
      <EPL_LOAD_ID>000000000002</EPL_LOAD_ID>
      <EPL_JOB_TYPE>D</EPL_JOB_TYPE>
      <EPL_JOB_GROUP>L03</EPL_JOB_GROUP>
      <EPL_JOB_INSTRUCTION>Very Fragile Parcel..Please handle with Care</EPL_JOB_INSTRUCTION>
      <EPL_JOB_SIGNATURE>R0lGODlh4AB4APcA...NKdJTY4EBAA7</EPL_JOB_SIGNATURE>
      <EPL_REASON_CODE></EPL_REASON_CODE>
      <EPL_LINKED_REASON>N</EPL_LINKED_REASON>
      <EPL_STATUS>C</EPL_STATUS>
      <EPL_CUSTOMER_CODE>OBS</EPL_CUSTOMER_CODE>
      <EPL_PHOTO_ID></EPL_PHOTO_ID>
      <EPL_ENG_SIGNATURE></EPL_ENG_SIGNATURE>
      <EPL_SEQUENCE>1</EPL_SEQUENCE>
      <EPL_START_PLANNED_DATE>20111108</EPL_START_PLANNED_DATE>
      <EPL_START_PLANNED_TIME>12000000</EPL_START_PLANNED_TIME>
      <EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
      <EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
      <EPL_START_ACTUAL_DATE>20111108</EPL_START_ACTUAL_DATE>
      <EPL_START_ACTUAL_TIME>10490000</EPL_START_ACTUAL_TIME>
      <EPL_END_ACTUAL_DATE>20111108</EPL_END_ACTUAL_DATE>
      <EPL_END_ACTUAL_TIME>10520000</EPL_END_ACTUAL_TIME>
      <EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
      <EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
      <EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
      <EPL_CUSTOMER_NAME>OBS Logistics</EPL_CUSTOMER_NAME>
      <EPL_JOB_ADDRESS>N</EPL_JOB_ADDRESS>
      <EPL_ADDRESS_1>Southern Gateway</EPL_ADDRESS_1>
      <EPL_ADDRESS_2>Speke Boulevard</EPL_ADDRESS_2>
      <EPL_ADDRESS_3>Liverpool</EPL_ADDRESS_3>
      <EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
      <EPL_ADDRESS_5></EPL_ADDRESS_5>
      <EPL_POSTCODE>L24 9HZ</EPL_POSTCODE>
      <EPL_CONTACT>Xavier Wai</EPL_CONTACT>
      <EPL_TELEPHONE>01514480331</EPL_TELEPHONE>
      <EPL_EMAIL>[email protected]</EPL_EMAIL>
      <EPL_INVOICED></EPL_INVOICED>
      <EPL_CUST_SIGNATORY></EPL_CUST_SIGNATORY>
      <EPL_JOB_CODE>L03</EPL_JOB_CODE>
      <EPL_CUST_REF></EPL_CUST_REF>
      <EPL_OFFICE_INSTRUCTION></EPL_OFFICE_INSTRUCTION>
      <EPL_SIGNED_UNCHECKED></EPL_SIGNED_UNCHECKED>
      <EPL_SO_NUMBER></EPL_SO_NUMBER>
      <EPL_TNCS></EPL_TNCS>
      <EPL_ORDER_DATE>0</EPL_ORDER_DATE>
      <EPL_SALES_CONTACT></EPL_SALES_CONTACT>
      <EPL_USER_NOTES></EPL_USER_NOTES>
      <EPL_OWNER_NAME></EPL_OWNER_NAME>
      <EPL_SERVICE_LEVEL></EPL_SERVICE_LEVEL>
      <EPL_TRAILER_ID></EPL_TRAILER_ID>
      <EPL_LAST_CHANGED_DATE>20120314</EPL_LAST_CHANGED_DATE>
      <EPL_LAST_CHANGED_TIME>9420098</EPL_LAST_CHANGED_TIME>
      <EPOD_CONTAINERS>
        <EPOD_CONTAINER>
          <EPL_SITE_ID>L03</EPL_SITE_ID>
          <EPL_JOB_ID>0000000001</EPL_JOB_ID>
          <EPL_CONTAINER_ID>000000000000001</EPL_CONTAINER_ID>
          <EPL_SEQUENCE>0</EPL_SEQUENCE>
          <EPL_CONTAINER_PACKAGE_CODE>XX</EPL_CONTAINER_PACKAGE_CODE>
          <EPL_CONTAINER_PACKAGE_DESC>Pallet</EPL_CONTAINER_PACKAGE_DESC>
          <EPL_REASON_CODE></EPL_REASON_CODE>
          <EPL_LINKED_REASON></EPL_LINKED_REASON>
          <EPL_STATUS>C</EPL_STATUS>
          <EPL_PHOTO_ID></EPL_PHOTO_ID>
          <EPL_CUST_COMMENTS></EPL_CUST_COMMENTS>
          <EPL_GROSS_WEIGHT>120</EPL_GROSS_WEIGHT>
          <EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
          <EPL_CODE_1>1</EPL_CODE_1>
          <EPL_CODE_2></EPL_CODE_2>
          <EPL_CODE_3></EPL_CODE_3>
          <EPL_LAST_CHANGED_DATE>20120614</EPL_LAST_CHANGED_DATE>
          <EPL_LAST_CHANGED_TIME>16362322</EPL_LAST_CHANGED_TIME>
        </EPOD_CONTAINER>
      </EPOD_CONTAINERS>
      <EPOD_SERVICES></EPOD_SERVICES>
    </EPOD_JOB>
  </EPOD_JOBS>
</EPOD_EXPORT_JOB>

Note Note: The signature has been shortened for the purposes of this document.

CALIDUS EPOD Export Mechanism

The files can be

  • Sent by the Vigo TMS via FTP to an FTP service hosted by OBS
  • Pulled by CALIDUS ePOD via FTP from an FTP service hosted by Vigo
  • Copied by CALIDUS ePOD from a shared folder on the Vigo TMS
  • Copied by CALIDUS ePOD from a shared folder on the CALIDUS ePOD system.

Regardless of the mechanism chosen above, the final destination folder should contain only completed files in the agreed naming convention, not files being built. The files should be built and copied under a temporary naming convention, before renaming to csv file (i.e. .tmp files).

The files to be picked up will be named as follows:

  • <SENDER>_<RECEIVER>_<OPERATING_PARTNER>_<DATE>_

where

  • <SENDER> is the system sending the file - expected to be "epod"
  • <RECEIVER> is the system receiving the file - expected to be "vigo"
  • <OPERATING_PARTNER> is the operating partner code, i.e. L02, L03, etc.
  • <DATE> is the date in YYYYMMDD format
  • <SEQ> is a unique counting sequence for each file created in a run.

No responses to the files shall be given - the receiving system (Vigo TMS in this case) will maintain an audit trail to be examined by the user on event of failure.

Each job will be sent in a separate file, to minimise disruption if a single file fails.

Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
1JobShare Mapping v0.2.xlsx0.218/02/2013
2EPOD Export Mapping v0.5.xlsx0.525/01/2013
3EPOD XSD.zipN/A25/01/2013


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_305796_EPOD_Vigo_Interface&oldid=1017’