Scheduling > Dispatch Console > Server-Side Configuration Options > Configuration Settings > Jeopardy Computation and Work Order Dependency
Jeopardy Computation and Work Order Dependency
The following are the settings related to jeopardy computation and work order dependency.
Setting Id
Setting Type
Default Value
Setting Name and Details
SET001
Global
0
Name: Scheduling frequency of running the 'In Jeopardy' condition computation job
Details: This setting is used to control the time interval in minutes for running the jeopardy condition computation job. Setting a value of '0' would disable the jeopardy condition computation.
SET002
Global
False
Name: Enable technician status update consideration for Jeopardy computation
Details: This setting is used to control whether timely technician updates should be considered for Jeopardy computation.
SET003
Global
30
Name: Threshold for Work Order to be in Jeopardy caused by delayed technician updates
Details: This is the threshold value (in minutes) for marking an scheduled/resourced Work Order as 'In Jeopardy' and surfacing it for Dispatcher's attention, when an expected Technician status update is not done on time.
SET004
Global
1440
Name: Threshold for Unresourced Work Order to be 'In Jeopardy' of being fulfilled
Details: This is the threshold value (in minutes) for marking an unresourced Work Order as 'In Jeopardy' and surfacing it for Dispatcher's attention. For example, with default value (1440 minutes) if the Work Order is still Unresourced with a day left for fulfillment deadline, it will be marked as 'In Jeopardy'.
SET005
Global
False
Name: Enable work order dependency validation in Dispatch Console
Details: Enable work order dependency validation when creating events from Dispatch console. If set to True and Dependency management has been defined for the work order, then time and resource dependency violations if any will be reported while creating events for the work order.
* 
These settings are used in Jeopardy Computation.
Was this helpful?