281762

DHL C-TMS

Transport Planning

- 10.5

- 1.0

Reference: FS 281762 AS-89WCCS

Transport planning process should remain the same in terms of linking orders to trips for collection and delivery, however it should be optimised in terms of speed from a CTMS perspective and have the ability for orders to be split to support the flexibility required within CTMS and WCS for cross schedule receiving and loading. We should also pass over new data from CTMS to Paragon relating to pallet equivalent by DU type. We should also have the ability within CTMS to record pallet equivalents by DU type, by supplier. The data exported from CTMS will now also include all unplanned & closed manifested collection orders up to 7 days old and 2 weeks in advance. Delivery planning should take any SCHEDCOLL orders. DUs in QC & SINBIN should not be part of the delivery planning export to Paragon.

This development will cover a number of changes to the transport planning integration with Paragon.

The solution will be developed so that it can be delivered as two separate releases. The priority of the initial release is to address extending the planning window to include supplier manifests confirmed later than or earlier than expected based on the provided SAP in-store date. The second part of the development will address a number of enhancements to improve general use-ability and functionality of the C-TMS Paragon integration.

Note that the upload of the Paragon plan file into C-TMS that creates the trips for the traffic schedule has been reworked and released successfully into live operation. Uploading the trip plan is now taking circa 10 to 15 minutes.

Release A – The paragon interface function to export data to paragon in CSV format will be changed to include late and early confirmed supplier manifests. Two new system parameters will be introduced to allow late and early which will be set initially to 7 and 14 days respectively.

When the paragon export is run for collections, the export CSV file will be created to include all manifests with orders at UNSCHEDULED status (closed manifests) with a collection window within the -7 and +14 days parameter. The RPE and volume value will be accumulated based on all UNSCHEDULED orders to be planned on the next paragon run.

When the paragon export is run for deliveries, the export CSV file will be created to include all orders at SCHED_COLL status. Orders in QC and in SINBIN will not be exported until released from these locations, usually on the next operational day after collection planning and receipt.

After the paragon plan is completed, the import file back to C-TMS that describes the trips, stops and manifests to be collected and orders to be delivered will be processed as normal. The upload functionality in C-TMS will only process the orders if at UNSCHEDULED for collection manifest and SCHED_COLL for delivery orders. This will guard against any situation arising where a manifest is planned over more than one collection day and constituent orders split to cover part receipts of an order at item level.

Release B – The following enhancements will be developed;

Paragon requires the constraint measures for RPE (PTE) to be uploaded from C-TMS as integer values. The paragon export file format from C-TMS will be modified to include integer RPE (PTE) and volume as integers by factoring the real values by 1000. Currently, the real values are factored by 10 and rounded up.

The paragon export will be extended to send a separate field for the qty of each DU type and the respective RPE of each DU type. Within the Supplier DU configuration (static data in C-TMS), a specific RPE (PTE) ratio will be available to be input for each DU type optionally. This will allow a specific ratio to be maintained for certain suppliers for the purpose of sending a more accurate RPE (PTE) to paragon for planning. For example, supplier A always sends large cartons so rather that 0.125, a specific factor of 0.2 is set into the C-TMS for this supplier. Note that this alternative RPE will only be calculated for the purpose of the paragon interface. All other screen query, reporting and extracts from C-TMS will work with the standard system wide DU RPE ratios.

The three changes below are OBS product investment at no cost to DHL -

The interface file validation in C-TMS when uploading a paragon CSV file will be modified. If the planner has rejected a file due to, for example, missing carrier codes, the checksum of the file will not be saved for further validation. This means, under this type of circumstance, the same file can be re-uploaded once the new static data has been entered in C-TMS. Conversely, if a file is processed, with or without errors having been flagged, C-TMS will not allow the same file content to be processed again using the existing checksum duplicate validation processing. The more detailed validation checking at the next level will be unaffected.

The paragon export screen in C-TMS will be modified to allow a button to be selected to retrieve the CSV file from the C-TMS server (from the interface archive) should the planner not save or lose the file on the local PC.

The paragon import screen in C-TMS will be modified to allow all orders status NEW to be reset back to UNSCHEDULED or SCHED_COLL should the planner need to clear and reset the interface. This means reverting the NEW status to the orders original status. The NEW status is a temporary status used to protect orders from being changed in C-TMS while paragon has control.