The PM compliance report and export

The Maintenance → PM compliance page (titled Work order and PM compliance) shows, for a period, how many of the preventive work orders that fell due were done on time, how many were late, and how many were missed. Next to it you see the ratio of corrective to preventive work orders. The page is read-only; the figures are computed from the work orders when you open it.

Before you start

• Permission: cmms:view (view maintenance). The export needs the same permission.
• Prerequisite: the Maintenance module is on.
• What the report looks at: the preventive work orders whose due date falls in the period — generated ones and preventive ones created by hand alike.

Steps

1. Open Maintenance → PM compliance. By default the last 90 days are shown, up to and including today.
2. Set the period in From and To and click Apply. A period can be at most two years, and the start cannot be after the end; otherwise you see: “Invalid period (at most two years, the start cannot be after the end).”
3. You can narrow it to a site (if you have access to more than one) and a plant. The plant is the work order’s own plant — the same one the work-order list shows.
4. Read the summary, then the Preventive work orders due list below it.
5. Save the list with Export (CSV) or Export (Excel).

What the classifications mean

Every preventive work order that fell due lands in exactly one category:

Category	When
On time	Done (technically completed or closed) on the due day or before.
Late	Done, but after the due day.
Missed	Not done yet, and the due day has passed.
Cancelled / rejected	The work order was cancelled or rejected — it was not carried out.
Pending (not yet due)	Open, and the due day has not passed — today counts as pending.

The completion day is the day of technical completion (or, failing that, of closing), in the site’s time zone.

The PM compliance percentage

PM compliance = done on time ÷ evaluable due items. An evaluable item is On time, Late, Missed and Cancelled / rejected together — the count is shown under the figure (“done on time / evaluable due items (N)”). Pending items do not count (neither good nor bad): it is not decided yet.

With nothing evaluable: “no data”, not 0

If not a single due item in the period is evaluable, the figure reads “no data”. That is not 0 %: it would mean nothing was achieved, when there is simply nothing to measure yet.

If a work order is in a “done” status but carries no completion timestamp (bad legacy data), the report does not count it as done on time — the claim cannot be proven.

The corrective share

The Corrective share is the share of corrective work orders among those created in the period (excluding cancelled and rejected ones). The counts appear under the figure: “N corrective · M preventive work orders created in the period”. The creation day is also taken in the site’s time zone. With no work orders, this too reads “no data”.

What the report does not see: skipped cycles

The system generates PM work orders every 6 hours. After a longer outage it creates a single work order and jumps to the next future due date — no work order is created for the skipped cycles. The report counts work orders, so it cannot see them. The page says so. If a figure looks too good after an outage, this is one possible reason.

The list and the export

• The summary covers the whole period. On screen the list shows the first 500 rows; if there are more you see: “The list shows the first N rows; the summary covers the whole period. The full list is in the export.”
• The export gives the report’s scope (period, site, plant) at row level. Its columns: Due, Number, Title, Site, Plant, Location, Status, Done, Classification. The file name has the form operex-pm-teljesites-<start>_<end>.
• CSV or Excel. The Excel file’s first sheet is the summary (“Summary”: the period, PM compliance, the category counts and the corrective share), the second sheet holds the rows (“PM compliance”).
• At most 20,000 rows go into one file. If the scope has more, the last row of the file says so: “The file contains the first N rows — narrow the period or the scope.” In that case narrow down and export in parts. The Excel summary still covers the whole period.

If it worked

The page shows the period, the PM compliance percentage (or “no data”), the counts of the five categories and the corrective share, with the list of work orders and their classification below; the export file’s rows say the same.

Common problems

• “No preventive work order is due in this period.” No preventive work order has a due date in the period. Widen the period or remove the filter.
• Compliance is high, but I know there was an outage. See above: skipped cycles have no work order, so the report cannot see them.
• A work order is “Pending”, although it should have been done today. Today does not count as overdue yet; from tomorrow it becomes “Missed” if it was not done by then.

Related

The next due dates are shown by the article What is due in the coming weeks: the due-date calendar. The gates and policy of the work order are covered in Configure the maintenance policy.