EST 324098 ForTrack Interface - Revision history

Anw: v0.3 - Modified cost

2018-08-07T07:36:17Z

v0.3 - Modified cost

← Older revision		Revision as of 09:36, 7 August 2018
Line 5:		Line 5:
	\|Supimix_Client_Reference=		\|Supimix_Client_Reference=
	\|Supimix_Number=324098		\|Supimix_Number=324098
	\|The_version_of_the_document=0.2		\|The_version_of_the_document=0.3
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=
Line 70:		Line 70:
	\|Requirements_Days=0		\|Requirements_Days=0
	\|Estimation_Days=2.5		\|Estimation_Days=2.5
	\|Functional_Specification_Days=1.00		\|Functional_Specification_Days=1.25
	\|Technical_Specification_Days=0.00		\|Technical_Specification_Days=0.00
	\|Development_Days=4.50		\|Development_Days=5.00
	\|Testing_and_Release_Days=0.75		\|Testing_and_Release_Days=1.00
	\|Implementation_Days=0.5		\|Implementation_Days=0.5
	\|Project_Management_Days=0.25		\|Project_Management_Days=0.25

Anw: v0.2 - Re-estimated for Swains

2018-08-07T07:33:56Z

v0.2 - Re-estimated for Swains

← Older revision		Revision as of 09:33, 7 August 2018
Line 5:		Line 5:
	\|Supimix_Client_Reference=		\|Supimix_Client_Reference=
	\|Supimix_Number=324098		\|Supimix_Number=324098
	\|The_version_of_the_document=0.1		\|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)=24/03/~~2015~~		\|Date_(DD/MM/YY)=7/08/2018
	\|Clients_Customer=~~Wyvern Cargo~~		\|Clients_Customer=Swains
	\|System_Version_being_changed=1.X		\|System_Version_being_changed=4.X
	\|Client_Request=		\|Client_Request=A working interface to Fortec.
	~~Wyvern Cargo will be rolling out ''CALIDUS'' ePOD to their fleet and will need to send ePOD information/confirmation on deliver completion through~~ to ~~ForTec's ForTrack system~~.
	\|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 ~~estimate~~ will be increased to cover the actual time taken.		{{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~~, like PalletForce~~.		* Pallets for these Pallet Networks will be labelled with their own network's pallet labels, and not Partnerlink labels.
	* 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 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.		* The Consignment will already exist within the ForTec ForTrack2 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 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.

	{{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:'''
	Process:		* A FORTRACK job group will be configured, following the same process as the other job groups in the system, configured the same way.
	* 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 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 ~~ForTrack~~ system.		* Swains Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.
	* ~~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 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 ~~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.		* 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.		* 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 ~~ForTrack~~ system, identified through the Job's Group and the configuration attached to it.		* 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 ~~export~~, along with any of the returned reasons from the export.		* 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, ~~the following files will be created for the job:~~		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:
	* A Delivery file will be created, showing the status of all the pallets, confirming the delivery.		* The Consignee Code
	* ~~A Signature file will be created~~, ~~containing the~~ signature for the job.		* 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.

	~~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~~.		Package numbers will be generated from the Consignment Number provided, plus a unique 3-digit numerical count.

	~~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~~.		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=1		\|Estimation_Days=2.5
	\|Functional_Specification_Days=1.75		\|Functional_Specification_Days=1.00
	\|Technical_Specification_Days=1.25		\|Technical_Specification_Days=0.00
	\|Development_Days=6.25		\|Development_Days=4.50
	\|Testing_and_Release_Days=1.25		\|Testing_and_Release_Days=0.75
	\|Implementation_Days=1		\|Implementation_Days=0.5
	\|Project_Management_Days=0.75		\|Project_Management_Days=0.25
	\|Year=~~2015~~		\|Year=2018
	\|Free_Of_Charge=N		\|Free_Of_Charge=N
	}}		}}

Anw: v0.1 - Initial creation for review

2015-03-24T10:18:02Z

v0.1 - Initial creation for review

New page

{{Template:Estimate
|Supimix_Client_Code=PART
|Supimix_Project_Code=DEV
|Supimix_Site_Code=PART
|Supimix_Client_Reference= 
|Supimix_Number=324098
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_Priority=3
|Date_(DD/MM/YY)=24/03/2015
|Clients_Customer=Wyvern Cargo
|System_Version_being_changed=1.X
|Client_Request=
Wyvern Cargo will be rolling out ''CALIDUS'' ePOD to their fleet and will need to send ePOD information/confirmation on deliver completion through to ForTec's ForTrack system.
|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 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.

|Requirements_Days=0
|Estimation_Days=1
|Functional_Specification_Days=1.75
|Technical_Specification_Days=1.25
|Development_Days=6.25
|Testing_and_Release_Days=1.25
|Implementation_Days=1
|Project_Management_Days=0.75
|Year=2015
|Free_Of_Charge=N
}}