Max Compatibility Distance And Speed Profile Not Working As Expected
(Doc ID 2511152.1)
Last updated on DECEMBER 21, 2020
Applies to:Oracle Real-Time Scheduler - Version 22.214.171.124.0 and later
Oracle Utilities Mobile Workforce Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
We have a user reporting that activity scheduling is not in respect to Scheduling Configuration parameters.
Example: We have an activity which is schedule behind the crew who is out of range for them and showing Calculated Travel Distance 125.57 Km. They have cost Profile defined as well but this seems to be not working at moment.
Basically we have an issue with the Max Compatibility distance defined on the Scheduler Configuration, the activity is scheduled behind an engineer with calculated travel distance is 125.57 km, but on the Scheduler Configuration level, Max compatibility distance is defined as 100Km.
That means it is not respecting the Max compatibility distance defined on Scheduler Configuration level.
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