Activities Being Despatched Out Of Sequence In v220.127.116.11
(Doc ID 2466855.1)
Last updated on NOVEMBER 01, 2018
Applies to:Oracle Real-Time Scheduler - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.3]
Information in this document applies to any platform.
On : 126.96.36.199.0 version, System Related Issues
Activities Being dispatched out of sequence
We drip feed our Engineers one activity at a time. However as new activities enter the schedule, ORS schedules them before already dispatched activities and will then immediately dispatch the new activity.
This causes confusion for the Engineer. His mobile device now contains two or more activities at different addresses with no information about the sequence of action.
The workaround is to call the Planning team incurring cost and taking additional time to resolve. The additional dispatched activities restrict the ability of ORS to respond to events which seriously impacts the efficiency of the schedule. Our contractual Response times are between 2 and 8 hours which requires ORS to replan frequently which it cannot do once an activity is dispatched.
We have defined parameters to lock the sequence of activities as it was done in ORS v1. There is also the drip horizon set to 1 and we dispatch upon completion. It appears as though the lock sequence parameter is being ignored.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!