 Note: This change requires integration with another system, so up to 1 day has been added to the specification and testing time to allow for this. If the specification time increases beyond this time allowed due to additional work required during this stage, the estimate will be increased to cover the actual time taken.
Assumptions:
- Jobs will be sent to Partnerlink and through to CALIDUS ePOD using the existing JobShare interfaces.
- Pallets for these Pallet Networks will be labelled with their own network's pallet labels, and not Partnerlink labels, like PalletForce.
- The new partners will accept updates into their Transport systems from CALIDUS EPOD in the standard OBS format - the pallet network system will be updated separately.
- The Consignment will already exist within the ForTec ForTrack system, ready for updating with POD information from CALIDUS ePOD.
- Wyvern Cargo will be assigned a Partner Code by Partnerlink, which will be provided to OBS Logistics prior to implementation of this change.
Note: This process is dependent on multiple reason codes for pallet networks change, specified in EST 318572 PART Job Group Level Clausing - No Duplicates. The work for this change must be completed before or as part of this change.
 Warning: At this time, OBS Logistics have not yet received a list of reason codes in use for the ForTrack system, so it is not yet known whether these reason codes used by ForTrack will cause any contention to the reason codes already in use in the system. If they do, further work will be required to the Reason Codes mechanism to allow a decoding of custom reason codes.
Process:
- The new partner Wyvern Cargo will be set up with a new partner code within CALIDUS ePOD, will be configured for their use following the standard configuration. This partner will be configured for export to the TMS system in use.
- ForTrack-specific reason codes will be set up as required by the ForTec ForTrack system.
- New Wyvern Cargo Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.
- When planned, these jobs will be sent to CALIDUS ePOD through the existing interface in use for the existing partners, and will be identified with a new Job Group e.g. FORTRACK. Note: This will require change to the sending process from the TMS system to accommodate this new job group.
- The jobs will be completed like any other normal delivery.
- When jobs are completed, the existing AutoExport functionality will update the Partner (identified through the Partner Code) using a flat-file export of the job details in OBS Logistics' XML format, as it does with each existing partner.
- The AutoExport process will also export the files to ForTec ForTrack system, identified through the Job's Group and the configuration attached to it.
- The AutoExport functionality will store the success or failure of the export, along with any of the returned reasons from the export.
The Admin Export Configuration screen will be changed to allow the parameters for the new ForTrack extract to be specified against it.
The CALIDUS ePOD system will be modified to store the GPS co-ordinates against the job at certain times:
- At Start Job
- At Arrive Job
- At Complete job
These will be included in the information sent to the ForTrack system.
The new ForTrack Export process will work as follows:
If a job is marked as successfully completed, the following files will be created for the job:
- A Delivery file will be created, showing the status of all the pallets, confirming the delivery.
- A Signature file will be created, containing the signature for the job.
If a job is marked as cancelled (i.e. not delivered), a FailedDelivery file will be created for the job, showing the reason the job failed, and listing all pallets for that job.
The files will then be named appropriately and uniquely and sent via FTP to the ForTrack system. The result of the sending process will be stored in the Audit tables within CALIDUS ePOD. Messages that process in error will be marked as such, so that they may be identified and reprocessed manually if required. |
