267282: Difference between revisions
Middletong (talk | contribs) (New page: =267282 - JB-7TYD7F/ Stop Consolidation for Microlise = Copyright OBS Logistics © 2010 The information contained herein is the property of OBS Logistics and is supplied without liabilit...) |
Middletong (talk | contribs) No edit summary |
||
Line 106: | Line 106: | ||
|} | |} | ||
Back to [[CONPRD Release - 24/02/2010]] |
Latest revision as of 17:12, 2 March 2010
267282 - JB-7TYD7F/ Stop Consolidation for Microlise
Copyright OBS Logistics © 2010
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
Different customers deliveries for same delivery point on same trip result in 1 stop per order in load plan , this impacts on Microlise.
When multiple customer orders exist on one trip to the same delivery point , if the delivery windows do not overlap then MTS will treat them as separate deliveries , so Microlise will see them as 3 stops.
Approach: - Apply new logic on MTS to consolidate orders into one stop where the consecutive orders are for the same destination and apply the logic of 30 mins plus 2 mins per lift to calculate the window. - There are possible knock on effects where we might be requested to deliver at 8am 9am and 10am for the 3 customers, but we would show a potential early delivery for the last 2 and Damian was concerned we could get penalised for this. There are however benefits in that MTS planning will no longer build in extra time as the plan will mirror reality and the driver can be utilised more on MTS (MTS logic applies 30 mins per stop plus 2 mins per lift and across multiple stops this could remove an hour?)
Solution
A new system parameter will control the slot consolidation functionality:
TRM_CONSOLIDATE_STOPS
Set to Y will turn on the functionality N or Null will preserve existing functionality.
If the above parameter is set to Y a further check against a new flag on Group Names will be made if this is also set to Y then orders on consecutive stops will be consolidated regardless of whether the time windows of those orders overlap or not.
The new flag on Group Name Maintenance will be to the right of Description in the screen shot below, it will be labelled Consol Stops:
If two orders are being delivered at a location on consecutive stops on a trip, with time windows that do not overlap, should one of the orders not belong to a group which has Consol Stops turned on then the stops will NOT be consolidated.
If stops are consolidated then standard MTS functionality will apply when calculating stop times i.e. MTS will still use current set up in the Load Rates tab of Resource Maintenance or the system defaults of 30 mins and 0.5mins per RPE if no load/unload is set up for the location.
Scope
This change will be applied to system version 10.6.
SET-UP
Data
New System registry TRM_CONSOLIDATE_STOPS will be added.
FUNCTIONAL DESCRIPTION
A new system registry called TRM_CONSOLIDATE_STOPS will be added that will control the new functionality detailed below.
If the system registry is set to ‘Y’ then the further checks will be made, if the registry is ‘N’ or null the existing functionality will be used.
A new flag will be added to the Group Name Maintenance tab, this will indicate whether orders belonging to that group should be included in consolidation of stops.
A new column will be added to the table OMS_SCHED_GROUP to store this flag.
When adding orders to a trip if two orders are being delivered to the stop, but the time windows do not overlap, the order will be consolidated. This is based on the registry being set and the orders belonging to a group which has the consolidate stops flag set.
If an order belongs to a group that does not have the consolidate stops flag set, it will not be included in the consolidation.
When stops are consolidated existing MTS functionality will still apply for calculating stops times etc.
REFERENCES
Not Applicable
DOCUMENT HISTORY
Initial version | ||||
Reviewed and Issued |
AUTHORISED BY
Matt Crisford | Development Manager | |
Peter Greer | TMSCC MTS Product Manager |
Back to CONPRD Release - 24/02/2010