ORS v1 Not Offering Expected Slots Due To Conflicting Shift Update Processing By Slot Generator
Last updated on AUGUST 08, 2017
Applies to:Oracle Real-Time Scheduler - Version 10.3 and later
Information in this document applies to any platform.
ORS not able to offer slots for certain Shifts.
In this example, at 12:19 on the 28th of June order 175555555x1 was taken and this was initially scheduled to Van 5-20170630-1.
At 12:21 the order was moved by the primary scheduler to shift Van 6-20170630-1, when more orders were taken. Within 15 seconds the slot generators where updated with the move to Van 6, this update failed for order 175555555x1 and 17666666x1 since shift Van 6-20170630-1 was missing from the slot generators. This meant that the two stops were left in position 5 and 6 on shift Van 5-20170630-1. As a result these two stop in the slot generators were 173 and 152 minutes late and with over two hours of overtime. There was spare capacity within the shift such that it could be optimised to arrive on time without overtime, but this is functionality that the slot generators do not perform.
When a slot request is performed that includes the affected store for the 30th of June the slot generators always return slots on van Van 5-20170630-1, since in calculating the cost of including the new stop the shift is optimised and so returning a very large negative cost (removal of stop late, overtime and lifespan cost). The host system then filtered out these large negative costs before being returned to the customer. No other slots are returned that overlap this shift and so no slots are returned for the store for the 30th.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms