286986
DHL C-TMS
Change to Dates & Times to Microlise
FUNCTIONAL SPECIFICATION - 10.6
23/05/2012 - 1.0
Reference: 286986 OB-8EYLAJ
Functional Overview
Client Requirement
Change Request Summary:
Change to dates and times sent to Microlise via interface.
Change Request Details:
The business requires a change to the times that are sent over to Microlise from C-TMS. Currently the times being sent to Microlise are the planned arrive and depart times held against the trip stop (in this case they are populated by Paragon, but would normally be derived from C-TMS itself). These planned in and out times are not however always correct as they only reflect roughly 40 mins per stop. Each Dunelm store has a delivery window (some 1 hour most 2 hours). So sometimes Microlise is displaying that we are arriving late (arriving after the planned time from Paragon), however, we may arrive during the two hour window.For example: store window is 09:00 to 11:00. Vehicle is planned to arrive at 09:30 and depart at 10:15. Vehicle actually arrives at 10:05. According to Microlise, this is classed as a late, however, because we have arrived before 11:00 from a KPI reporting perspective we are actually on time.Can the planned arrived and depart numbers be changed on the interface to be the store delivery windows, possibly reporting the windows held against the slots within the C-TMS Locations table?
Benefits identified as a result of the change:
Far more accurate KPI reporting.
Solution
Currently, when sending trip information to MICROLISE, the planned arrive and depart times held against each stop as scheduled by Paragon are sent. These schedule times are uploaded into Microlise in the journeySchedule import message. In Microlise, the actual arrival and departure times are compared with these planned times to establish if the driver was on time or late.
Rather than send the planned arrive and depart times from the stop as planned and scheduled by Paragon (or C-TMS if planned manually), C-TMS will send the delivery slot times for the store delivery location. In the Location maintenance screen, there is a tab for setting slot times against the store location. Each slot is linked to a day of the week, based on the numbers 1 to 7. To link the delivery stop to a slot, the delivery date will be converted to a numeric day of the week. The location id of the store and the day of the week will be used to retrieve the relevant slot times.
The current process for sending Trip information to MICROLISE will be changed to send the store slot times rather than the planned stop times. The code changes will be controlled by the value of a new system parameter SET_MICROLISE_SLOTS. If this parameter is set to Y, the slot times will be retrieved and sent to MICROLISE, if this parameter is set to N, the planned stop arrive and depart times will be sent to MICROLISE (current functionality)
The slot times will only be selected where the stop type is ‘DL’. If null is returned for the slot times then the planned arrive and depart times at the stop will be used by default.
Scope
This change will be applied to system version 10.6.
Set-up
Pre-requisites
The new system parameter ‘SET_MICROLISE_SLOTS’ must be setup.
Menu Structure
‘Unchanged’
Data
The new system parameter ‘SET_MICROLISE_SLOTS’ must be set.
Functional Description
The outbound EDI message to Microlise will be changed to include the delivery window of the slot instead of the planed arrival and departure times of the trip stop.
The files with the name format ‘TMS_MIC_{OWNING_DEPOT}_TRP_{SYSTIME}’ will include this change dependent on the system parameter ‘SET_MICROLISE_SLOTS’: if the system parameter is set to ‘Y’ and a delivery window of the slot can be found then those times will be used in preference to the planned arrival and departure times of the trip stop.
The file generated in procedure ‘INT_XML_MIC.PROCESS_XML_OUTBOUND_MIC’ will be changed so that the procedures ‘INT_XML_MIC.GEN_STOP_DET’ and ‘INT_XML_MIC.GEN_STOP_DET_CONSOL’ obtain the times based on the system parameter.
The date/time format of ‘YYYY-MM-DDTHH24:MI:SS’ will be retained.
The slot delivery window will be obtained for stop types of ‘DL’ (i.e. ‘Delivery’) from the orders being delivered at the trip stop; the ID of the scheduled slot usage (on table ‘SCH_SLOT_USAGE’ for the OMS reference) for the orders may be used to obtain the delivery window of the slot.
The delivery window of the slot is stored as follows:
| Tag | Table | Column |
| <STOP_PLANNED_ARRIVAL_DATE> | GEO_SLOT | DELIVER_WINDOW_START |
| <STOP_PLANNED_DEPARTURE_DATE> | GEO_SLOT | DELIVER_WINDOW_END |
The day offset should also be considered by adding to the usual delivery window:
| Table | Column |
| GEO_SLOT | DWS_DAY_OFFSET |
| GEO_SLOT | DWE_DAY_OFFSET |
These values are stored in the ‘Slots’ tab page of the ‘Locations’ maintenance screen in C-TMS where the destination of the order is the principal location and the source of the order is the secondary location.
NB it is expected that DHL will maintain the slot information in C-TMS, via the locations maintenance form or via standard C-TMS slot Import functionality.
Table Updates Required
The new system parameter may be created using the following script:
INSERT INTO ADM_SYSTEM_PARAM
(PARAM_NAME,VALUE,DATA_TYPE,MAX_LENGTH,DISPLAYED,USER_MODIFIABLE,DESCRIPTION,CREATED_BY,CREATED_DATE,UPDATED_BY,UPDATED_DATE,CONFIG_BY,CONFIG_BY_VALUE)
VALUES
('SET_MICROLISE_SLOTS','Y','S',1,'Y','Y','Determines if the delivery slot times are sent to Microlise instead of the planned delivery times.','OBS',SYSDATE,'OBS',SYSDATE,'SYSTEM','NONE');
/
References
| EST-286986 OB-8EYLAJ Change to dates & times to Microlise v1.0.doc | |||
Glossary
| C-TMS | Calidus TMS |
Document History
| Initial version | ||||
| Reviewed | ||||
| Issued | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
