What is due in the coming weeks: the due-date calendar
The Maintenance → Due dates page shows the due dates of maintenance tasks in one place: on a weekly or monthly grid, or as a “next 30 / 90 days” list. On the same page you see what is overdue and — for runtime-based tasks — when the next maintenance can be estimated. The page is read-only: you change nothing here.
Before you start
Section titled “Before you start”- Permission: cmms:view (view maintenance). Without it the page sends you — with a work-order permission — to the work orders, otherwise to the diary.
- Prerequisite: the Maintenance module is on. With the module off the page says so: “The Maintenance module is not enabled”.
- What is shown: maintenance tasks. Operational (diary) tasks do not appear here — they go to the shift diary and do not generate work orders.
- Open Maintenance → Due dates. By default the Month view opens on the current month.
- Pick a view from the button row: Week, Month, Next 30 days or Next 90 days. On the week and month grids you page with Previous, Today and Next; the two lists count forward from today.
- Narrow the content with the filter bar: Site (only if you have access to more than one site), Plant and Equipment type. Choosing a main type includes the subtypes below it. Clear filters brings every item back.
- To get the due dates of one technical location, use the “Due dates in the calendar” link on that location’s page under Maintenance: it shows the items of the location and the locations below it, in the Next 90 days list. Under the filter bar you then see “Functional location (with subtree): …”, with a Clear filters link next to it.
- Click an item to go to the work order, or to the task’s technical location.
What you see on the items
Section titled “What you see on the items”- Planned — a coming occurrence of a calendar-based task. There is no work order for it yet; the system creates it in the first generation run from the due date on.
- Work order — an open preventive work order on its due date, with its status. This covers work orders generated from a task as well as preventive work orders created by hand.
- Overdue — marked in red. The Overdue (N) card gathers these separately and does not depend on the selected period: when you page forward on the grid, overdue items do not disappear.
- “Open work order: …” — the task already has an open work order; the link takes you there.
“Due — the work order is created in the next generation run”
Section titled ““Due — the work order is created in the next generation run””This is not an error. The system generates PM work orders from the calendar tasks every 6 hours. If a task’s due date has passed but its work order has not been created yet, the item shows as overdue with this note, and it gets its work order in the next run.
No double entries
Section titled “No double entries”If a task has an open work order for the same day, only the work order appears in the calendar and the “planned” item is left out. The task’s other days carry the “Open work order: …” mark.
Runtime-based tasks
Section titled “Runtime-based tasks”A runtime-based task has no calendar date: its work order is created when the equipment reaches the runtime threshold. They therefore sit on a separate card (“Runtime-based tasks”). Each row shows the interval (“every N running hours”) and the running hours left (“N running hours left”).
The card states that the date is only an estimate. The estimated day (“estimated: …”) is computed from the average daily runtime of the latest readings, counting from the day of the last reading; next to it you see the assumed rate (“≈ N running hours/day”) and the last reading day. The average uses the readings of the last 180 days, from the stretch after the last correction or meter replacement — values before a correction may have been on another scale (see Correct a runtime reading and meter replacement).
When there is no date, the row also says why:
| Message | What it means |
|---|---|
| Threshold reached (and “Threshold reached — the work order is created in the next generation run.”) | The equipment has reached the end of the interval; a work order is created in the next run. |
| “No date estimate: too few readings, or the machine did not run.” | There are not enough readings for a trend (at least two, at least a day apart), or the runtime did not grow. |
| “No baseline yet — the next generation run sets it; not due until then.” | On the task’s first run the system records the starting runtime. |
| “No runtime reading — no work order is generated.” | No runtime reading has ever been recorded on the equipment. |
If it worked
Section titled “If it worked”On the grid or list your tasks sit on their due dates, overdue ones on the Overdue card, and runtime-based ones on their own card — with an estimated day or a stated reason.
Common problems
Section titled “Common problems”- I do not see the task. A task appears when it has a next due date (calendar-based task) or a runtime interval, is not archived, its strategy is not archived, and it is not an operational type. A task with an ad hoc or continuous frequency gets a single due day and does not repeat.
- “The list is too long — not every item is shown.” The calendar shows at most 3000 items per query. Narrow it down by site, plant or equipment type.
- “Today” differs from my own clock. What counts as “overdue” is decided per site, from the current day in the site’s time zone.
Related
Section titled “Related”How well the due dates were actually met is shown by the article PM compliance report and export.