EST 341168 PalletLine Integration - Revision history

Anw: v2.0 - Issued with discount

2017-03-21T14:00:32Z

v2.0 - Issued with discount

← Older revision		Revision as of 16:00, 21 March 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=HATH-PALLETLINE		\|Supimix_Client_Reference=HATH-PALLETLINE
	\|Supimix_Number=341168		\|Supimix_Number=341168
	\|The_version_of_the_document=1.1		\|The_version_of_the_document=2.0
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=

Anw: v1.1 - Added discount percentage

2017-03-21T13:47:14Z

v1.1 - Added discount percentage

← Older revision		Revision as of 15:47, 21 March 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=HATH-PALLETLINE		\|Supimix_Client_Reference=HATH-PALLETLINE
	\|Supimix_Number=341168		\|Supimix_Number=341168
	\|The_version_of_the_document=1.0		\|The_version_of_the_document=1.1
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=
Line 60:		Line 60:
	\|Year=2017		\|Year=2017
	\|Free_Of_Charge=N		\|Free_Of_Charge=N
			\|DiscountPerc=50
			\|DiscountText=Hathaways Discount
	}}		}}

Anw: v1.0 - Issue

2017-03-15T10:46:12Z

v1.0 - Issue

← Older revision		Revision as of 12:46, 15 March 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=HATH-PALLETLINE		\|Supimix_Client_Reference=HATH-PALLETLINE
	\|Supimix_Number=341168		\|Supimix_Number=341168
	\|The_version_of_the_document=0.3		\|The_version_of_the_document=1.0
	\|Your_Name=A N Walker		\|Your_Name=A N Walker
	\|Supimix_PO_Reference=		\|Supimix_PO_Reference=
Line 21:		Line 21:

	The process will be as follows:		The process will be as follows:
	* Palletline-specific reason codes will be set up within ''CALIDUS'' ePOD, conforming to the list of delivery codes used by Palletline. These reason codes will be exclusive ~~tot he~~ Palletline job group, and the Palletline job group will be configured so that only those codes can be used on Palletline jobs.		* Palletline-specific reason codes will be set up within ''CALIDUS'' ePOD, conforming to the list of delivery codes used by Palletline. These reason codes will be exclusive to the Palletline job group, and the Palletline job group will be configured so that only those codes can be used on Palletline jobs.
	* New Palletline Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.		* New Palletline 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. PLINE. The Pallet Depot will be set to the Palletline depot code provided to the carrier, in Hathaway's case, this is "053". The Pallet Consignment will be sent in as the Palletline ID. {{Note}} This will require change to the sending process from the TMS system to accommodate these new values for every partner that wishes to join the Palletline network.		* 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. PLINE. The Pallet Depot will be set to the Palletline depot code provided to the carrier, in Hathaway's case, this is "053". The Pallet Consignment will be sent in as the Palletline ID. {{Note}} This will require change to the sending process from the TMS system to accommodate these new values for every partner that wishes to join the Palletline network.

Anw: v0.3 - After review by JMM.

2017-03-10T11:07:21Z

v0.3 - After review by JMM.

← Older revision		Revision as of 13:07, 10 March 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=HATH-PALLETLINE		\|Supimix_Client_Reference=HATH-PALLETLINE
	\|Supimix_Number=341168		\|Supimix_Number=341168
	\|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 12:		Line 12:
	\|Clients_Customer=David Hathaway		\|Clients_Customer=David Hathaway
	\|System_Version_being_changed=3.X		\|System_Version_being_changed=3.X
	\|Client_Request=Andy Ward at David Hathaway Transport ~~advises: We have agreed to join~~ the Palletline network and ~~start on~~ the ~~6th March 2017. One of the things we'll need~~ to ~~set up is our epod devices sending the pod information back~~ to Palletline's Contrado system~~. Do you have any experience of transferring files into Contrado? Note: We have previously looked at Palletline via 3rd party (sterling) for AKW Global~~.		\|Client_Request=Andy Ward advises that David Hathaway Transport are joining the Palletline network and require the POD debrief information to be sent from Calidus ePOD to Palletline's Contrado system.
	\|OBS_Solution=		\|OBS_Solution=
	Assumptions:		Assumptions:

Anw: v0.2 - Added development of the mobile device application

2017-03-09T13:15:38Z

v0.2 - Added development of the mobile device application

← Older revision		Revision as of 15:15, 9 March 2017
Line 5:		Line 5:
	\|Supimix_Client_Reference=HATH-PALLETLINE		\|Supimix_Client_Reference=HATH-PALLETLINE
	\|Supimix_Number=341168		\|Supimix_Number=341168
	\|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 20:		Line 20:
	* The Consignment will already exist within the Palletline Contrado system, ready for updating with POD information from ''CALIDUS'' ePOD.		* The Consignment will already exist within the Palletline Contrado system, ready for updating with POD information from ''CALIDUS'' ePOD.

	~~Process~~:		The process will be as follows:
	* Palletline-specific reason codes will be set up within ''CALIDUS'' ePOD, conforming to the list of delivery codes used by Palletline. These reason codes will be exclusive tot he Palletline job group, and the Palletline job group will be configured so that only those codes can be used on Palletline jobs.		* Palletline-specific reason codes will be set up within ''CALIDUS'' ePOD, conforming to the list of delivery codes used by Palletline. These reason codes will be exclusive tot he Palletline job group, and the Palletline job group will be configured so that only those codes can be used on Palletline jobs.
	* New Palletline Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.		* New Palletline Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.
Line 30:		Line 30:
	* 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 export, along with any of the returned reasons from the export.

			The development required will be as follows:

			The mobile device application will be modified to capture the signature in vector format as well as the standard mechanism of an image format. The application will be configured to store this and use it for the Palletline export process.

	The Admin Export Configuration screen will be changed to allow Palletline export types to be configured in it.		The Admin Export Configuration screen will be changed to allow Palletline export types to be configured in it.


	The Partnerlink Import process will be modified to identify the Palletline job group (e.g. "PLINE"). This will then generate Pallet Ids in the normal way.		The Partnerlink Import process will be modified to identify the Palletline job group (e.g. "PLINE"). This will then generate Pallet Ids in the normal way.

Anw: v0.1 - Initial Draft

2017-03-09T12:10:49Z

v0.1 - Initial Draft

New page

{{Template:Estimate
|Supimix_Client_Code=PART
|Supimix_Project_Code=DEV
|Supimix_Site_Code=.
|Supimix_Client_Reference=HATH-PALLETLINE
|Supimix_Number=341168
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_Priority=3
|Date_(DD/MM/YY)=09/03/17
|Clients_Customer=David Hathaway
|System_Version_being_changed=3.X
|Client_Request=Andy Ward at David Hathaway Transport advises: We have agreed to join the Palletline network and start on the 6th March 2017. One of the things we'll need to set up is our epod devices sending the pod information back to Palletline's Contrado system. Do you have any experience of transferring files into Contrado? Note: We have previously looked at Palletline via 3rd party (sterling) for AKW Global.
|OBS_Solution=
Assumptions:
* Jobs will be sent to Partnerlink and through to ''CALIDUS'' ePOD using the existing JobShare interfaces.
* Pallets for the Palletline pallet network will be labelled with their own network's pallet labels, and not Partnerlink labels. It is expected that pallet IDs will be created by ''CALIDUS'' ePOD in the normal way, identifying the individual pallets by assigning each pallet a unique ID, counting from the 1 to the total number of pallets.
* Palletline's Contrado system will be updated separately to the partner's TMS systems. This will require a modification to identify consignments as being completed for Palletline.
* The Consignment will already exist within the Palletline Contrado system, ready for updating with POD information from ''CALIDUS'' ePOD.

Process:
* Palletline-specific reason codes will be set up within ''CALIDUS'' ePOD, conforming to the list of delivery codes used by Palletline. These reason codes will be exclusive tot he Palletline job group, and the Palletline job group will be configured so that only those codes can be used on Palletline jobs.
* New Palletline 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. PLINE. The Pallet Depot will be set to the Palletline depot code provided to the carrier, in Hathaway's case, this is "053". The Pallet Consignment will be sent in as the Palletline ID. {{Note}} This will require change to the sending process from the TMS system to accommodate these new values for every partner that wishes to join the Palletline network.
* {{Note}} The Palletline ID is noted to be field 4 in the Palletline manifest download file.
* The jobs will be completed like any other normal delivery.
* When jobs are completed, the existing AutoExport functionality will update the Partners (identified through their Partner Codes) using a flat-file export of the job details in OBS Logistics' XML format, as it does now.
* The AutoExport process will also export the files to Palletline Contrado 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 Palletline export types to be configured in it.

The Partnerlink Import process will be modified to identify the Palletline job group (e.g. "PLINE"). This will then generate Pallet Ids in the normal way.

The ''CALIDUS'' ePOD AutoExport function will be modified to recognise jobs with the Palletline job group and export a file in the Palletline format.

This format will identify the pallets delivered and any reason codes against them, including claused and cancelled pallets. This will also identify the signatory and signature (if delivered), the GPS coordinates (if available) and the status (POD Uploaded for pallets that were delivered, the selected reason code for clauses and cancellations).

The format will be in XML and will be named following the conventions specified by Palletline. A single file will be created per job completed or cancelled.

{{Note}} It is as yet undecided what mechanism will be used to send this file to Palletline. It will however be one of the following:
* Create the file locally to the ''CALIDUS'' ePOD server and host an FTP service so that Palletline can pick up the file.
* Create the file and send immediately through FTP to the Palletline FTP server.
The process should support either case as standard.

|Requirements_Days=0
|Estimation_Days=1.50
|Functional_Specification_Days=1.50
|Technical_Specification_Days=0
|Development_Days=7
|Testing_and_Release_Days=1.25
|Implementation_Days=0.25
|Project_Management_Days=0.50
|Year=2017
|Free_Of_Charge=N
}}