Example of Scheduling Behavior With Auto-dispatch Funtionality And Auto Dispatch Time Horizon

(Doc ID 2261706.1)

Last updated on MAY 09, 2017

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.2.0 and later
Information in this document applies to any platform.


(Q1) How to auto-dispatch the "appointment" assignment as soon as the crew logs in?
(Q2) Why did it only dispatch one assignment at a time even though drip mode was set to ALL?
(Q3) Where can I find the ETA in the front-end and back-end?
(Q4) How to calculate the ETA?

(Q5) Re-phrase the question with an example:

If the Auto Dispatch Time Horizon were set to 1hr then then activity would be dispatched 1hr before the crew needed to get moving towards the activity.
Using Chi's earlier example of 30 min travel and a 12:00 appointment. The activity would now be dispatched at 10:30 rather than 11:30.

Question: 10:30 - 11:30 is idle time. 11:30 - 12:00 is the travel time.
Can work be scheduled between 10:30 and 11:30 or that is considered as idle time and no work can be scheduled during this time?


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