Shifts That Get Cancelled For No Apparent Reason Corrected in MWM/ORS 220.127.116.11.7
(Doc ID 2142978.1)
Last updated on JUNE 01, 2018
Applies to:Oracle Utilities Mobile Workforce Management - Version 18.104.22.168.1 to 22.214.171.124.7 [Release 2.2]
Oracle Real-Time Scheduler - Version 126.96.36.199.1 to 188.8.131.52.7 [Release 2.2]
Information in this document applies to any platform.
Occasionally, shifts get cancelled for no apparent reason and seems to happen on the actual day. The cancellation of these shifts forces work to be redistributed among the remaining shifts causing lateness and more importantly causes those shifts to run into shifts for the following day. This in turn causes even more lateness and the whole thing can dangerously spiral.
It seems ORS no longer likes one shift for a resource ending at the same time as the next shift starting. This is a change that has occurred sometime during the 2.2 release. Therefore we needed a minute break between one shift and the next shift. Hence we set up the shift templates to end 1 minute earlier than they would normally.
1st Shift: 06:00 to 12:59
2nd Shift: 13:00 to 17:59
3rd Shift: 18:00 to 23:00
When the auto-complete process completes shifts there are occasions when a shift is completed slightly later than the planned end time. So 1st Shift may finish at 13:01.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document