EST 333427 PART TPN - Pallet Network Interface

STATEMENT OF WORK CHANGE REQUEST ESTIMATE

Client	PART	Project	DEV	Site	PART
Client Reference	TPN-HATH-SWAIN	Aptean Reference	333427	Estimate Version	1.0
Prepared By	A N Walker			Estimate Date	18/02/2016
Invoice Reference				Priority	3
Customer	Hathaways/Swains			System Version	3.X

Client Request

Patnerlink Partners David Hathaway and R Swain & Sons require an interface to update the POD Delivery details from CALIDUS ePOD into The Pallet Network (TPN).

Aptean Solution

Assumptions: Jobs will be sent to Partnerlink and through to CALIDUS ePOD using the existing JobShare interfaces. It is expected that pallets for TPN will be labelled with their own network's pallet labels. It is expected that pallets 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. Partners completing jobs for TPN will accept updates into their Transport systems from CALIDUS EPOD in the standard OBS format - the TPN Connect system will be updated separately. This will require a modification to identify consignments as being completed for TPN when jobs are interfaced from the external Transport systems. The Consignment will already exist within the TPN Connect application, ready for updating with POD information from CALIDUS ePOD. Any new partners will be assigned a Partner Code by Partnerlink, which will be provided to OBS Logistics prior to implementation of this change. Note: There are no reason codes required on the interface to TPN Connect for failed deliveries. Process: Any new partners will be set up with a new partner code within CALIDUS ePOD, will be configured for their use following the standard configuration. These will be configured for export to the TMS system in use. An export configuration for TPN will be created and linked to the TPN job code. New 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. TPN. Note: This will require change to the sending process from the TMS system to accommodate this new job group. The Consignment number will also be provided. The Partnerlink Pallet IDs will be generated as now. The TPN pallet IDs will be generated as an ascending numeric sequence from 1. 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 with each existing partner. The AutoExport process will also export the files to TPN Connect application, 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 TPN extract to be specified against it. The new TPN Export process will work as follows: A message will be sent to the TPN Connect application, by connecting through the AddPOD method of their existing ThirdPartyServices webservice. One message sent per pallet on the consignment, to update a pallet and consignment with delivery, signatory and signature information. Pallets that are not marked as delivered will still have a message sent, but with the Delivered flag set to false. The pallet ID used for this update will be the TPN pallet ID generated on receipt of the order (the numeric seuqence) and the consignment will be set from that provided on the order. The response will be captured by the process and handled for success or failure - the exact format of this response will be identified at functional specification stage, and is expected to identify success or failure.

Warning:

Unknown costs for client/year (PART/2016)

Cost Details
Activity	Hours	Rate per hour (£)	Cost (£ Exc. VAT)
Requirements	0.00	0.00	£0.00
Change Request Evaluation	0.25	0.00	£0.00
Functional Specification	1.00	0.00	£0.00
Technical Specification	1.00	0.00	£0.00
Development	4.50	0.00	£0.00
Testing and Release	0.75	0.00	£0.00
Implementation	0.25	0.00	£0.00
Project Management	0.25	0.00	£0.00
TOTAL	8.00		£0.00

Estimate excludes training, release to live and go live support.

Copyright © Aptean 2016. This estimate has an expiry date of 30 days from the specified Estimate Date. The information contained herein is supplied without liability for errors or omissions.