Logoff Delay On Crew Shifts Not Enforced When Shift Started Later Than Planned

(Doc ID 2361287.1)

Last updated on FEBRUARY 21, 2018

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.3.0.0.0 to 2.3.0.0.0 [Release 2.3]
Oracle Real-Time Scheduler - Version 2.3.0.0.0 to 2.3.0.0.0 [Release 2.3]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Logoff Delay on Crew Shifts not enforced.

Logoff Delay appears to have no effect when the last non-mandatory job for a Shift is completed. Typical Crews have a 7-4pm Shift with a 30 minute logon/logoff delay.  In this case the actual Shift start time is 7:58. Crews are constantly forecasted to complete their last Activity of the day around 3:50pm, well after the 3:30pm logoff time. This does not allow appropriate time to get back to the office and the yard.

In an example, the Crew was forecasted to work until after 3:50pm on non-mandatory work that is not due for several days from today. There is no logical reason why they should work into overtime to accomplish that work. There are low, medium, and high priority tasks on their Shift, so plenty of options to remove Activities to keep them working on the appropriate schedule.

Changing the logoff delay to 1 hour did not change anything on the Schedule.

We've resorted to changing our Planned End Date/Time to 3:15pm to compensate.

Cause

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