Undispatch No Longer Undispatches Excess Activities Beyond Dispatch Horizon

(Doc ID 2260626.1)

Last updated on MAY 05, 2017

Applies to:

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

Symptoms

Undispatch does not work as desired

In the most recent release of MWM (2.2.0.3.2), the undispatch functionality has changed. Most notably, it no longer undispatches excess dispatches from the MDT. Excess dispatches are dispatches in excess of the drip horizon on the shift.

The new undispatch is actually a cost based reassign function. Meaning the assignment is only removed from the MDT if the assignment is also removed from the shift. This is very different than undispatch that only delete the assignment from the MDT, but not necessary from the shift.

As a result of this change, shifts are accruing excess dispatches. Some shifts have all assignments dispatched when only a few assignments should be dispatched. The only way to prevent accruing excess dispatches is to lock the sequence on thee shift. This is not desirable from crew that work same day activities and have very dynamic shifts.

It is fine that there is a new cost control to limit reassignments to different shifts, but is not a direct replacement for undispatch. We would llike to get the old undispatch function restored. There is no business requirement for the new undispatch (reassign) function, but there is a business requirement for a conventional undispatch function (remove assignment from MDT only). Conventional undispatch is very simple and is not cost based. If an dispatched assignment is pushed out of the drip horizion, delete the assignment from the MDT only.

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