EST 324098 ForTrack Interface: Difference between revisions
From Calidus HUB
(v0.1 - Initial creation for review) |
(v0.2 - Re-estimated for Swains) |
||
| Line 5: | Line 5: | ||
|Supimix_Client_Reference= | |Supimix_Client_Reference= | ||
|Supimix_Number=324098 | |Supimix_Number=324098 | ||
|The_version_of_the_document=0. | |The_version_of_the_document=0.2 | ||
|Your_Name=A N Walker | |Your_Name=A N Walker | ||
|Supimix_PO_Reference= | |Supimix_PO_Reference= | ||
|Supimix_Priority=3 | |Supimix_Priority=3 | ||
|Date_(DD/MM/YY)= | |Date_(DD/MM/YY)=7/08/2018 | ||
|Clients_Customer= | |Clients_Customer=Swains | ||
|System_Version_being_changed= | |System_Version_being_changed=4.X | ||
|Client_Request= | |Client_Request=A working interface to Fortec. | ||
|OBS_Solution= | |OBS_Solution= | ||
{{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 | {{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 cost will be increased to cover the actual time taken. | ||
Assumptions: | '''Assumptions:''' | ||
* Jobs will be sent to Partnerlink and through to ''CALIDUS'' ePOD using the existing JobShare interfaces. | * 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 | * Pallets for these Pallet Networks will be labelled with their own network's pallet labels, and not Partnerlink labels. | ||
* The | * The 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 | * The Consignment will already exist within the ForTec ForTrack2 system, ready for updating with POD information from ''CALIDUS'' ePOD. | ||
{{ | {{Warning}} At this time, OBS Logistics is still expecting additional information regarding the interface to Fortec's ForTrack2 system. At this time, it is believed that the update will follow the process as laid out in this estimate. If details come to light at a later stage that affect this, the estimate or functional specification will be reissued with additional costs identified. | ||
'''Process:''' | |||
Process: | * A FORTRACK job group will be configured, following the same process as the other job groups in the system, configured the same way. | ||
* ForTrack-specific reason codes will be set up as required by the ForTec ForTrack2 system. These will be set up as specific to job group FORTRACK and will be the only reason codes that may be selected when completing jobs of that group. | |||
* ForTrack-specific reason codes will be set up as required by the ForTec | * Swains 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 FORTRACK. {{Note}} This will require change to the sending process from the TMS system to accommodate this new job group, and the consignment number will also be sent - Swain's TMS provider will be required to make these changes. | ||
* 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 | |||
* The jobs will be completed like any other normal delivery. | * 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 | * 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 partner. | ||
* The AutoExport process will also export the files to ForTec | * The AutoExport process will also export the files to ForTec ForTrack2 system, identified through the Job's Group and the configuration attached to it. | ||
* The AutoExport functionality will store the success or failure of the | * The AutoExport functionality will store the success or failure of the exports, along with any of the returned reasons from the export. | ||
| Line 53: | Line 49: | ||
The new ForTrack Export process will work as follows: | The new ForTrack Export process will work as follows: | ||
If a job is marked as successfully completed, | If a job is marked as successfully completed, a delivery file will be created, showing the status of all the pallets, confirming the delivery. This will include: | ||
* The Consignee Code | |||
* | * The Trip Number | ||
* The Delivery details, consisting of: | |||
** The package number | |||
** The latitude and longitude when delivered (if available) | |||
** The Consignment Number | |||
** Discrepancy Codes (if applicable) | |||
** The Date and Time | |||
* The signatory | |||
* The signature for the job. | |||
Discrepancy codes will be added only when an item has failed to be delivered - there are no specific clause codes for Fortec deliveries, although some may be added solely for internal Swains use. | |||
Package numbers will be generated from the Consignment Number provided, plus a unique 3-digit numerical count. | |||
If a job is marked as cancelled (i.e. not delivered), the same file will be created for the job, showing the reason the job failed. The reason description will be sent, from the list of Fortec reason codes. | |||
The files will then be named appropriately and uniquely and sent via FTP to the ForTrack2 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. | |||
|Requirements_Days=0 | |Requirements_Days=0 | ||
|Estimation_Days= | |Estimation_Days=2.5 | ||
|Functional_Specification_Days=1. | |Functional_Specification_Days=1.00 | ||
|Technical_Specification_Days= | |Technical_Specification_Days=0.00 | ||
|Development_Days= | |Development_Days=4.50 | ||
|Testing_and_Release_Days= | |Testing_and_Release_Days=0.75 | ||
|Implementation_Days= | |Implementation_Days=0.5 | ||
|Project_Management_Days=0. | |Project_Management_Days=0.25 | ||
|Year= | |Year=2018 | ||
|Free_Of_Charge=N | |Free_Of_Charge=N | ||
}} | }} | ||
Revision as of 09:33, 7 August 2018
 |
CHANGE REQUEST ESTIMATE |
| Client | PART | Project | DEV | Site | PART |
| Client Reference | Aptean Reference | 324098 | Estimate Version | 0.2 | |
| Prepared By | A N Walker | Estimate Date | 7/08/2018 | ||
| Invoice Reference | Priority | 3 | |||
| Customer | Swains | System Version | 4.X | ||
| Client Request |
| A working interface to Fortec. |
| Aptean Solution |
 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 cost will be increased to cover the actual time taken.
These will be included in the information sent to the ForTrack system.
If a job is marked as successfully completed, a delivery file will be created, showing the status of all the pallets, confirming the delivery. This will include:
Discrepancy codes will be added only when an item has failed to be delivered - there are no specific clause codes for Fortec deliveries, although some may be added solely for internal Swains use. Package numbers will be generated from the Consignment Number provided, plus a unique 3-digit numerical count. If a job is marked as cancelled (i.e. not delivered), the same file will be created for the job, showing the reason the job failed. The reason description will be sent, from the list of Fortec reason codes. The files will then be named appropriately and uniquely and sent via FTP to the ForTrack2 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. |
 Warning: | Unknown costs for client/year (PART/2018) |
| Cost Details | |||
| Activity | Hours | Rate per hour (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | £0.00 |
| Change Request Evaluation | 2.50 | 0.00 | £0.00 |
| Functional Specification | 1.00 | 0.00 | £0.00 |
| Technical Specification | 0.00 | 0.00 | £0.00 |
| Development | 4.50 | 0.00 | £0.00 |
| Testing and Release | 0.75 | 0.00 | £0.00 |
| Implementation | 0.50 | 0.00 | £0.00 |
| Project Management | 0.25 | 0.00 | £0.00 |
| TOTAL | 9.50 | £0.00 | |
| Estimate excludes training, release to live and go live support. |
|
Copyright © Aptean 2018. |
