EST 377534 PART EPOD New Palletforce Interface

STATEMENT OF WORK CHANGE REQUEST ESTIMATE

Client	PART	Project	DEV	Site	PART
Client Reference	DEV	Aptean Reference	377534	Estimate Version	0.1
Prepared By	A N Walker			Estimate Date	28/08/2020
Invoice Reference				Priority	3
Customer	Palletforce			System Version	4.5.x

Client Request

As a network, Palletforce put enormous effort into collecting more than 100,000 tracking events each day and every consignment is made up of over 50 individual pieces of data. To further enhance their tracking capabilities and customer experience, they have improved their ePOD tracking integrations by creating a new ePOD and Tracking API, as well as allowing current processes to receive additional tracking data. Last year, Palletforce invested £2m in a new state of the art ePOD hardware and software. A number of Palletforce members (including Partnerlink partners) take advantage of the flexibility of using their own technology to integrate with Alliance, however over time the number of compulsory tracking events has diminished in comparison to tracking events that their newly-revamped ePOD solution offers. With this in mind, from 27th November 2020 the following tracking events will become mandatory for every consignment delivered in Alliance: Scanned onto Delivery Vehicle (DELV) En Route (DONR) Arrived at Delivery Location (ARDL) Proof of Delivery (POD) and all equivalent statuses indicating end of consignment. In addition to the above, the following tracking and data will also become mandatory to provide: Proof of Collection (POC) confirmation for collections performed on behalf of other members. Delivery order and total number of Palletforce deliveries on the route. These changes will provide a universal and consistent service for all customers, ensuring that every customer receives the same high-quality tracking data, whilst providing members with the flexibility of using their own ePOD and scanning technology. This will further enhance Palletforce's current services such as consignment notifications, and provide them with a platform to develop even better consignment tracking that will enhance their customer experience, reduce queries and provide a solid foundation for future development around real-time tracking.

Aptean Solution

Scope: The Scanned onto Delivery Vehicle event (DELV) will not sent by CALIDUS ePOD, as the partners do not use loading tasks within this application. This status event is required by Palletforce. This will be achieved through the partners' TMS solutions or through the use or Palletforce-provided scanners. This is not part of the development to CALIDUS systems indicated as part of this solution. If the partners want this functionality to be included through CALIDUS ePOD, this will require additional assessment and development. This is not included in this estimate. The new Palletforce interface requires that the message identify the address type, Commercial or Retail. This information is not provided to CALIDUS ePOD from the partners' TMS systems. As such, the interface below will be identifying each address type as "U" - Unknown, which is currently acceptable to Palletforce. However, in the future, further development may be required, both to the partners' TMS solutions (to pass this data to C-ePOD) and to C-ePOD (to receive and store this data. The time for this is not included in this estimate. The details of this Palletforce test system have not yet been provided or assessed. Once provided, this may affect this estimate. At this time, it is not expected that this will affect the estimate in a significant way. The old Palletforce method of interfacing is being decommissioned and will no longer be available after a changeover period. Solution: The C-ePOD Admin screen will not require modification, as the screen already supports the Palletforce (PALLET) interface type, which will now be configured as a SOAP webservice. There are no expected modifications to the data being passed to the partners' TMS solutions for Palletforce jobs, nor to the data being passed to C-ePOD for those jobs. There are no expected modifications to the configuration of the job processes to support this new interface, for example process changes for the driver, or reason code changes for Palletforce jobs. Jobs will be received into the C-ePOD system in the same way that they are now, with no changes to how these are processed by this interface. The existing Palletforce export will be modified to change from the existing FTP file-based (CSV/PNG) interface to sending the files directly to a webservice endpoint provided by Palletforce. The interface will send all required information to the Palletforce systems at certain events: DONR - En Route. The status is used when the job is a delivery and the job has been set to In Progress i.e. the driver has started this job. ARDL - Arrived at Delivery Location. The status is used when the job is a delivery and the job has been updated with an arrival date and time. Proof of Delivery (POD) and all equivalent statuses indicating end of consignment, including: POD - POD Received. The status is used when the job is a delivery, the container (pallet) status is "C" - complete, with no notes or reason code. PODE - POD Received with Exception. The status is used when the job is a delivery, container status is "C" - complete by also contains notes and/or a reason code (i.e. claused). DMGD - Delivered Damaged. The status is used when the job is a delivery, container status is "X" - cancelled with reason code i.e. pallet has not been delivered. POC - POC Received. The status is used when the job is a collection. ABRT - Delivery aborted. The status is used when the whole job has been cancelled. At each trigger point, an event status update will be sent to the Palletforce system, detailing the information required for that status update. All sites (i.e. partners) within Partnerlink will be assigned a unique Access Key, that uniquely identifies the partner to Palletforce. This replaces the existing mechanism of using Palletforce Depot codes. Unique tracking codes will be provided for the Palletforce jobs, which will be used to identify the consignments in the new interface. Latitude and longitude will be provided on the status update message, if the applications knows of it. Each status update message will include the drop number and total drops on the trip. For end-of-job statuses as listed above, the signatory and signature will also be included. Where exceptions are indicated, the system will provide details (i.e. the notes and reason code descriptions) in notes against the consignment. The system will audit the messages sent and will audit the response from the Palletforce webservice, to indicate whether the update was successful or has failed. Additional time has been added to this estimate to account for data set-up of the new interface on behalf of the customers, both for the test and production environments. Additional testing time has been added to test this fully with the test Palletforce system. The details of this Palletforce test system have not yet been provided or assessed.

Cost Details
Activity	No. of Days	Rate per Day (£)	Cost (£ Exc. VAT)
Requirements	0.00	850	£0.00
Change Request Evaluation	2.00	850	£1,700.00
Functional Specification	1.50	850	£1,275.00
Technical Specification	0.00	850	£0.00
Development	6.00	850	£5,100.00
Testing and Release	3.00	850	£2,550.00
Implementation	3.00	850	£2,550.00
Project Management	3.00	850	£2,550.00
TOTAL	18.50		£15,725.00

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

Copyright © Aptean 2020. 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.