EST 337049 Hathaways Europa Interface

From Calidus HUB
Revision as of 16:57, 13 September 2016 by Anw (talk | contribs) (Minor format changes)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Aptean Logo.png
STATEMENT OF WORK
CHANGE REQUEST ESTIMATE
ClientPARTProjectDEVSitePART
Client ReferenceHATH-EUROPAAptean Reference337049Estimate Version0.1
Prepared ByA N WalkerEstimate Date13/09/16
Invoice Reference Priority3
CustomerALLSystem Version3.3.X


Client Request
Mark Middleton at Europa requests an interface between C-ePOD and Europa.

An update back to Europa is required, as well as maintaining the update back into ManPack3 for Hathaways.

OBSL have provided the interface documentation and this format is acceptable.

Note Note: Europa consignments are being sent across to C-ePOD currently as 'L02' Hathaways owned and executed jobs.


Aptean Solution
Note Note: If data is to be back to Europa as well as to ManPack3, CALIDUS ePOD will need to have the Europa Jobs created with a EUROPA job group, to differentiate their processing and split it out to send it back to Europa. This will involve some changes to be made on C-ePOD and also for Mandata to send through Europa messages differently on the interface, setting the Tracking System (column 65 in the Job Share interface format) to "EUROPA".


The EUROPA Job Group may then be configured to require a data export in the C-ePOD XML format to a destination folder or external system through file transfer or FTP. The files will be named as per the normal processing.


C-ePOD will require modification to recognise this Tracking System on import.

It is expected that a tracking number will not be provided in column 64 of the Job Share import. The Container (Pallet) ID generated will then be the Partner Job ID plus a 3-digit counter for each pallet to be generated.

Note Note: If a Tracking Number is provided, the system will generate pallet IDs in the following format:

"506" + pfDepot (column 63) + serviceLevel (column 38) + PfTrackingNo (column 64) + a 2-digit counter for each pallet to be generated.

Note Note: If any other format of pallet ID is required for Europa pallets, this must be identified before sign-off of this estimate, as this will incur additional development. It is assumed that this is not required.


The EUROPA job group will be configured with a C-ePOD 'JOB' XML type export. It is expected that this will either be FILE or FTP transfer type, with details to be provided. It is expected that all EUROPA jobs will be exported to a single folder.

Note Note: If sub-folders are required based on the job data rather than the configuration, additional development will be required.


The Export process will be modified to identify the EUROPA job group and export configuration. This will export the C-ePOD Job XML to the destination as specified in the configuration.

Note Note: It is not expected that any changes are required to the naming convention of these files. If this is required, additional development will be required.


Note Note: The export of data from C-ePOD has been extended for multiple additional systems (i.e. the pallet network tracking exports) far beyond it's initial design. As such, the export process has at times reached its maximum capacity in the current form. As part of change 337120, the export process will have many efficiency changes put into it to improve the speed of processing. It is required that this efficiency change is completed before the changes here are implemented.


Warning 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 0.25 0.00 £0.00
Technical Specification 0.00 0.00 £0.00
Development 1.50 0.00 £0.00
Testing and Release 0.50 0.00 £0.00
Implementation 0.00 0.00 £0.00
Project Management 0.00 0.00 £0.00
 
TOTAL 2.50   £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.