Jeopardy Work Orders
A work order gets into In Jeopardy state if there are issues with the Work Order field values that impact the scheduling. For example:
• A work order is scheduled without any exception. However, due to real world situation such as technician not acknowledging the schedule in time, technician not arrived on time to the work order site, and so on, the work order gets into jeopardy state over time
• A work order may be in an exception state such as Unresourced, Unscheduled – Bad Data and have Constraint Violations, which get into jeopardy state over time. To know more about the exceptions, refer to the above section.
The jeopardy state of the work order is captured in Work Order field In Jeopardy. A scheduled job does
dynamic computation of work orders getting into jeopardy state and sets this field to True.
When a work order gets into a jeopardy state, it can cause some work orders scheduled for the same technician subsequently to go into jeopardy state. Such subsequent work orders, which cannot be fulfilled by the same technician within 24 business hours, will also be marked as In Jeopardy.
If the scheduled job that does jeopardy computation finds a work order to be no longer in jeopardy state, the subsequent work orders will be removed from jeopardy state if
jeopardy condition is not met.