Emergency Activities Not Subject to Auto Dispatch Stability Period Parameter (Doc ID 2010853.1)

Last updated on MAY 21, 2015

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.1.0.5 to 2.2.0.2.0 [Release 2.1 to 2.2]
Information in this document applies to any platform.

Symptoms


Emergency Activities are not subject to the Auto Dispatch Stability Period parameter

The Auto Dispatch Stability Period (default value 60 seconds) is designed to prevent MWM from dispatching a newly created activity to the first shift that it finds. It has been determined that Emergency Activities are not being impacted by this stability period parameters. Instead, Emergencies are going to the first available Crew, even if the distance to travel is much longer.

In some instance,it is far better to wait a couple of minutes and dispatch an emergency to the most optimal crew than to the first compatible crew that MWM finds. The Auto Dispatch Stability Period should be applied to all activities.

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