Managing Disabled Stops

Stops (or activities in the Siebel application) can convert to a disabled state in Oracle Real-Time Scheduler 1.0 when the scheduler cannot incorporate them into the schedule because of data inconsistencies. This result can occur for one of the following reasons:

• The time window on the stop is in the past.

• There are no field service engineers with the skills required to perform the job.

The dispatcher must monitor disabled stops and try to fix data inconsistencies so that such stops can be scheduled. If the dispatcher cannot fix a disabled stop, then the dispatcher must update the status to Inactive, and update the Warn Text field in Oracle Real-Time Scheduler 1.0 with suitable comments.

Inactive stops are automatically synchronized with the Siebel application. The corresponding Siebel activity is updated to Unscheduled, and the Error Reason field is populated with comments in the Warn Text field.