EST 346014 Pallex TWINE Update - Revision history

Anw: v0.3 - Amended estimate

2017-10-03T14:50:11Z

v0.3 - Amended estimate

← Older revision		Revision as of 16:50, 3 October 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=Pallex TWINE Update		\|Supimix_Client_Reference=Pallex TWINE Update
	\|Supimix_Number=346014		\|Supimix_Number=346014
	\|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 38:		Line 38:
	If the job being sent to the Pall-Ex TWINE webservice is a collection, there are slightly different messages sent in this case, substituting "POC" for "POD" the tag names.		If the job being sent to the Pall-Ex TWINE webservice is a collection, there are slightly different messages sent in this case, substituting "POC" for "POD" the tag names.
	\|Requirements_Days=0		\|Requirements_Days=0
	\|Estimation_Days=0.5		\|Estimation_Days=0
	\|Functional_Specification_Days=0.5		\|Functional_Specification_Days=0
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0
	\|Development_Days=1.5		\|Development_Days=3.5
	\|Testing_and_Release_Days=0.5		\|Testing_and_Release_Days=0
	\|Implementation_Days=0~~.25~~		\|Implementation_Days=0
	\|Project_Management_Days=0~~.25~~		\|Project_Management_Days=0
	\|Year=2017		\|Year=2017
	\|Free_Of_Charge=N		\|Free_Of_Charge=N
	}}		}}

Anw: v0.2 - Additional details

2017-10-02T13:51:32Z

v0.2 - Additional details

← Older revision		Revision as of 15:51, 2 October 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=Pallex TWINE Update		\|Supimix_Client_Reference=Pallex TWINE Update
	\|Supimix_Number=346014		\|Supimix_Number=346014
	\|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=
Line 38:		Line 38:
	If the job being sent to the Pall-Ex TWINE webservice is a collection, there are slightly different messages sent in this case, substituting "POC" for "POD" the tag names.		If the job being sent to the Pall-Ex TWINE webservice is a collection, there are slightly different messages sent in this case, substituting "POC" for "POD" the tag names.
	\|Requirements_Days=0		\|Requirements_Days=0
	\|Estimation_Days=0.25		\|Estimation_Days=0.5
	\|Functional_Specification_Days=0.5		\|Functional_Specification_Days=0.5
	\|Technical_Specification_Days=0		\|Technical_Specification_Days=0

Anw: v0.1 - Initial Draft.

2017-10-02T13:38:44Z

v0.1 - Initial Draft.

New page

{{Template:Estimate
|Supimix_Client_Code=PART
|Supimix_Project_Code=DEV
|Supimix_Site_Code=PART
|Supimix_Client_Reference=Pallex TWINE Update
|Supimix_Number=346014
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_Priority=3
|Date_(DD/MM/YY)=02/10/17
|Clients_Customer=Pall-Ex
|System_Version_being_changed=3.X/4.X
|Client_Request=Request from Chris Holland of Pall-Ex 18 September 2017 13:14:

Part of the discussions we were going to have this week was regarding enhancements we have made to our driver hand-held applications and core TWINE system, and how we can integrate with 3rd party TMS providers such as yourselves in a little more detail.

Our TWINE system, now has the ability to receive additional status information during the delivery/collection lifecycle, and each status has a GPS positioner that we can use to identify the location of the driver at that point in time.

Can you please review the attached documents, (TWINE_Webservices 3.2 DSC) and advise if it is possible for your system to send this information to us, and if so what the development timescale would be to do so.
|OBS_Solution=The new TWINE interface specification has added new webservice methods that allow the notification of GPS latitude and longitude with the messages.

In all cases, the new messages are identical in content with the exception of the new GPS tags.

{{Note}} The provided specifications in Word and PDF format are slightly different: the PDF does not contain definitions of the new webservice methods, just the old non-GPS methods. The Word document has only the ''...WithGPS'' definitions. It is noted that the following solution has been validated with Chris Holland of Pall-Ex.

The C-ePOD Export Pall-Ex TWINE interface processes will be changed to use these replacement messages, as follows:
* The GPS coordinates of the Job Update message will be extracted and stored, so that they can be used on the subsequent messages to the Pall-Ex TWINE system. If the GPS coordinates are blank or not found, these stored values will be blank.
* A message of type ''addEpodConsignmentWithGPS'' is sent per job updated, adding tags GPSLAT and GPSLON, populated from the stored coordinates.
* A message of type ''addMpodImageWithGPS'' is sent per job updated, adding tags GPSLAT and GPSLON, populated from the stored coordinates.
* A message of type ''addEpodPalletWithGPS'' is sent per pallet per job updated, adding tags GPSLAT and GPSLON, populated from the stored coordinates.

The new GPS tags will always be sent, even if the stored GPS coordinate values are blank.

If the job being sent to the Pall-Ex TWINE webservice is a collection, there are slightly different messages sent in this case, substituting "POC" for "POD" the tag names.
|Requirements_Days=0
|Estimation_Days=0.25
|Functional_Specification_Days=0.5
|Technical_Specification_Days=0
|Development_Days=1.5
|Testing_and_Release_Days=0.5
|Implementation_Days=0.25
|Project_Management_Days=0.25
|Year=2017
|Free_Of_Charge=N
}}