About Jeopardy Computation
Jeopardy Computation includes the following:
• The settings under module Dispatch Management and submodule Exception Management control how a work order is computed to be in jeopardy, resulting in its In Jeopardy field being set to True. These settings are listed as follows:
◦ SET001 enables jeopardy computation when set to a value greater than 0.
◦ SET002 determines if missed timely updates from technician will make the work order to be considered as In Jeopardy, if the delay is greater than the threshold set by
SET003.
◦ SET003 specifies the maximum allowed delay in updates from technicians after which the work order is marked as In Jeopardy, if
SET002 is True.
◦ SET004 specifies the minimum time required before the fulfillment deadline, falling short of which the work order is marked as In Jeopardy.
• Scheduler:
Execute the following method in Developer Console to create scheduler for jeopardy computation:
SVMXC.WSCH_Jeopardy_Manager_Scheduler Jeosch = new SVMXC.WSCH_Jeopardy_Manager_Scheduler(); Jeosch.startJeopardyPushScheduler();
When you enable jeopardy computation using the settings described above, Work Order field In Jeopardy is set to True automatically, by the scheduled job that does jeopardy computation. This computation applies to work orders scheduled by Schedule Optimization, either through Optimized Batch or through Real Time Optimization dispatch processes.