Scheduling > Dispatch Console > Using Dispatch Console > Using Work Order Grid > Jeopardy Work Orders > About Jeopardy Conditions
About Jeopardy Conditions
The following table shows the conditions under which a work order is marked as in jeopardy. These conditions are applied in the order specified. Note that the configuration settings that have been mentioned are available under module Dispatch Management and submodule Exception Management.
Work Order State
Scenario
Work Order Status is not Closed or Canceled
AND
(Violation Status is Unscheduled – Bad Data or Unresourced
OR
Dispatch Status is New)
AND
Now > (Committed date time for scheduling – Service Duration – SET004 (Threshold for Unresourced Work Order to be 'In Jeopardy' of being fulfilled) value)
The committed date time for scheduling is identified as follows, in the order specified:
1. Work order’s Preferred End Time
2. Related case’s Preferred End Time
3. If the work order has SLA Terms, the value of the SLA field (default: Onsite Response Customer By) identified by the setting SET008 (SLA Timestamp for Work Order Scheduling, module OptiMax, submodule Dispatch Calculations)
The work order remains unscheduled.
AND
The remaining time between now and the committed date time for work order scheduling is less than the buffer defined in SET004.
Order Status is not Closed or Canceled
AND
Violation Status is blank
AND
Scheduling Status is not Null, Cancelled, En Route, Onsite, Finished Onsite, or Completed
AND
Now > (Scheduled Date Time – Driving Time + SET003 (Threshold for Work Order to be in Jeopardy caused by delayed technician updates) value)
The work order is scheduled, but the technician has not yet started driving to the work order site.
AND
It is already past the time at which the technician must have started, even after taking into account the maximum allowed delay (SET003, with SET002 set to True).
Order Status is not Closed or Canceled
AND
Violation Status is blank
AND
Scheduling Status is not Null, Cancelled, Onsite, Finished Onsite, or Completed
AND
Now > (Scheduled Date Time + SET003 (Threshold for Work Order to be in Jeopardy caused by delayed technician updates) value)
The work order is scheduled, but the technician has not yet arrived at the work order site.
AND
It is already past the time at which the technician must have arrived, even after taking into account the maximum allowed delay (SET003, with SET002 set to True).
Order Status is not Closed or Canceled
AND
Violation Status is blank
AND
Scheduling Status is not Null, Cancelled, Finished Onsite, or Completed
AND
Now > (Scheduled Date Time + Service Duration + SET003 (Threshold for Work Order to be in Jeopardy caused by delayed technician updates) value)
The work order is being serviced, but the technician has not yet finished service delivery at the work order site.
AND
It is already past the time at which the technician must have finished, even after taking into account the maximum allowed delay (SET003, with SET002 set to True).
* 
Run the following Scheduler scripts to enable the jeopardy conditions feature:
SVMXC.WSCH_Jeopardy_WOBatchApex_Scheduler jeopardySch = new SVMXC.WSCH_Jeopardy_WOBatchApex_Scheduler();jeopardySch.startJeopardyPushScheduler();
Was this helpful?