The Schedule Summary Report provides a high-level view of the status of scheduled dispatches.
- This report is to highlight all PM work that was scheduled to be done in that time frame, plus the current work (even if it was completed after the designated timeframe that was SUPPOSED to be done in the designated timeframe).
Metrics
- On Time: includes 1. dispatches that were completed on time within the time frame in the filter and 2. open dispatches (not completed) with a due date in the future.
- Past Due: Includes 1. dispatches that were completed after the due date within the time frame in the filter and 2. open dispatches with a due date in the past.
- On Time/Past Due Total: Includes all dispatches that were completed within the time frame in the filter and all open dispatches. Essentially, this is a sum of the On Time dispatches and Past Due dispatches.
- On-time percentage: "On Time" / "On Time/Past Due Total"
- Open: Dispatches that were launched within the time frame and are due within the time frame and have not been completed.
- Completed: Dispatches that were launched within the time frame and were completed within the time frame.
- Missed Complete: Count of Dispatches that were Missed, or Skipped. If a Scheduled PM is not completed within it's time frame (e.g. Daily PM isn't completed one day), the system will create a Dispatch as Closed to count a missed occurrence. These Dispatches will be counted as Missed Complete. Missed Complete Dispatches are only counted one time - they are not included in the "Completed" count.
- Open/Complete/Missed Total: All Dispatches that were launched within the time frame in the filter. Essentially, this is a sum of the Open Completed, and Missed Completed dispatches.
-
Completion Percentage: "Completed" / "Open/Complete/Missed Total"
Helpful Tips
- Cycle Based schedules will show up on this report after they have been scheduled. Only schedules with a due date or a completion date show up on this report.
- The PM dispatches must be from the scheduler (have an associated event schedule machine id).
Example:
For the example date range of 12/1/25-12/31/25, for a dispatch to be counted in Open or Missed:
- First: The earlier of completed/due must be between 12/1-12/31
- Second: The reported date must be on or after 12/1 (reported >= start)
So a dispatch with:
- Reported: 11/15
- Due: 12/15
- Completed: 12/20
Would:
-
Pass the main date filter (due date 12/15 is in range)
-
NOT be counted in Open/Completed/Missed (reported 11/15 is before 12/1)
-
Still be counted in On Time/Past Due calculations. The reported date is the additional gating factor for Open and Missed categories
Further Breakdown of column headers:
- On Time:
- If completed: completed <= due
- If not completed: now <= due (currently on time)
- Includes ALL dispatches meeting this criteria within the filtered date range
- Past Due:
- If completed: completed > due AND not marked as missed
- If not completed: now > due AND not marked as missed
- Includes ALL dispatches meeting this criteria within the filtered date range
- Open:
- Dispatch was reported (created) on or after the start date
- Not completed
- Not marked as missed
- Completed:
- Dispatch was reported (created) on or after the start date
- Has been completed
- Not marked as missed
- Missed:
- Dispatch was reported (created) on or after the start date
- Has been completed
- Marked as missed in the occurrence table
The main difference:
- On Time/Past Due: Include ALL dispatches in the date range regardless of when they were reported.
- Open/Completed/Missed: Only include dispatches that were reported during or after the start date (d.reported >= start)
This means a dispatch that was created before your date range but completed within it would count toward On Time/Past Due but NOT toward Open/Complete/Missed totals.
See Also