Use the operational pages to monitor task execution and audit direct future scheduling runs directly in the Daily Plan. To ensure work orders are assigned correctly and to quickly identify scheduling errors, review the real-time processing states and historical archives.
Prerequisites
You must have access to the Daily Plan interface.
Monitor direct future scheduling activities
To monitor the current view of work order operations handled by direct future scheduling without opening individual archives:
-
Navigate to the Daily Plan operation bar.
-
Open the Direct Future Scheduling Activities page.
-
To identify specific activities, filter the list by last processing state, creation date, processing date, WO code, external WO code, Expected Work Start Date, Expected Work End Date, WO Type, Service Type, Request Type, or Facility Type.
-
Review the current processing states:
|
State |
Meaning |
|
TO_BE_PROCESSED |
Waiting to be processed by the task. |
|
IN_PROGRESS |
Currently being processed. |
|
PROCESSED_OK |
Successfully processed. |
|
PROCESSED_KO |
Could not be assigned or processed successfully. |
Note: A PROCESSED_KO state does not necessarily indicate a technical issue. It can also mean the task ran correctly but no feasible technician was available under the configured constraints.
Review the archive
To review the execution history and audit past processing runs:
-
Navigate to the Daily Plan > Direct Future Scheduling tab.
-
Click Archive.
-
In the Processing List (which displays one row per processing run), review the execution runs:
|
Column |
Description |
|
Operation Center |
Operation Center the run was executed for. |
|
Scheduling Model |
Model used for the run. |
|
Last processing status |
Status of the run. |
|
Expected Processing Date |
Expected date of the run. |
|
Horizon Start Date |
Scheduling start of the period. |
|
Horizon End Date |
Scheduling end of the period. |
|
Processing Start Date |
Start of the processing run. |
|
Processing End Date |
End of the processing run. |
|
WO Assigned |
Number of WOs assigned. |
|
WO not Assigned |
Number of WOs not assigned. |
|
Error Description |
Error from the process execution. |
Note: Use this list to spot runs with many exclusions, failed assignments, or reprocessing activity.
Verify activity outcomes
To verify the outcome of a specific run and confirm which technician received the activity:
-
In the Archive, select a row from the Processing List.
-
In the detail panel, navigate to the Direct Future Scheduling Activities tab.
-
Review the work orders considered in that run:
|
Column |
Description |
|
WO Operation Id |
Internal Work Order Operation code. |
|
WO Operation |
Specific WO and operation code. |
|
Horizon Start Date |
Admissible scheduling horizon start for the activity. |
|
Horizon End Date |
Admissible scheduling horizon end for the activity. |
|
Scheduling Start Date |
Start date/time of the scheduling. |
|
Scheduling End Date |
End date/time of the scheduling. |
|
Foreman |
Foreman of the team. |
|
Processing Attempt status |
Status of the assignment. |
|
Creation Date |
Creation date of the Work Order. |
|
Last Processing Date |
Last processing date of the Work Order. |
|
Processing Counter |
Number of times the WO was processed. |
|
Last Processing Error |
Error message, if available. |
Analyze scheduling logs
To view a granular, step-by-step technical trace of the scheduling engine's execution:
-
In the Archive Processing List, locate the target run.
-
Click the ⋯ menu for that row.
-
Select Scheduling Log.
Note: This log is pre-filtered to the selected run and is intended for IT or support users. It displays data initialization, the valid resource list per day (with exclusions and reasons), loaded scheduled activities, VRP daemon selection, time-slot configuration, and assignment results or error traces.