What this is
What does PM optimization actually decide?
What does PM optimization actually decide?
It decides, task by task, whether a preventive maintenance check is still earning its place — based on how often it actually finds a defect, whether it addresses a real failure mode, and whether it duplicates coverage sitting elsewhere. The output is a recommendation per task: keep, extend, shorten, convert to condition-based, merge or delete.
How is this different from a reliability centred maintenance study?
An RCM study builds the maintenance strategy from scratch, working through failure modes to decide what kind of task, if any, should exist. A PM optimization review starts from tasks that already exist and uses their performance data — find rate, cost, duplication — to tune or remove them. It's maintenance of the maintenance plan, not a first-principles redesign.
Why does a low find rate justify removing a task rather than keeping it as a precaution?
A task that inspects for a failure mode that rarely or never occurs is consuming planner and technician hours that could go toward tasks with a demonstrated find rate, or toward addressing failures this task isn't catching. Under SAE JA1011's logic, a preventive task only earns its place if it is technically feasible and worth doing against the failure it targets.
Scope
When is a pm optimization review required?
This review tunes an existing PM plan using performance data. It is not where a maintenance strategy gets built from scratch, and it is not where a single failure gets investigated — those happen in the templates this one draws its task history from.
Use this template when
- A defined review period has closed and the PM plan's performance over it needs assessing
- A new record is needed; each one gets its own ID in the form PMO-2026-000
- You are running the Reliability and Predictive Maintenance programme and this yearly review is one of its scheduled steps
- A task's find rate, cost or duplication has been flagged as worth checking outside the normal annual cycle
- A linked record needs this one to exist, such as a PM plan update citing the review that justified an interval change
Do not use it for
- Reliability Centred Maintenance Study, which builds the maintenance strategy for a failure mode from first principles, rather than tuning a task that already exists.
- Equipment FMEA, which identifies failure modes and their severity ahead of deciding what task, if any, should address them.
- MTBF Review, which reports the asset-level failure rate this review draws on as one of its inputs, but doesn't touch task frequency itself.
- Equipment Failure Report, which records one failure event, not a task's performance across a review period.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process
Compliance mapping
Which SAE JA1011 requirements does this satisfy?
SAE JA1011 sets out what a maintenance task has to demonstrate to remain justified once a failure mode is understood; the fields below map to the parts of that logic this review applies to existing PM tasks.
| Clause | Requirement | Where it lands |
|---|---|---|
| SAE JA1011 §5.4 — proactive task applicability and effectiveness | A task must be shown to actually detect or prevent the failure mode it targets, not merely exist against it on paper. | Task review |
| SAE JA1011 §5.5 — default actions where no proactive task is effective | Where a task shows no find rate and no real failure mode behind it, the review must consider deletion or a default action rather than leaving it unexamined. | Task review |
| SAE JA1011 §5.1 — functions and functional failures as the basis for task selection | Each task is checked against whether it addresses a real, defined failure mode before its frequency is tuned. | Task review |
| SAE JA1011 §5.3 — failure consequences drive task priority | The recommendation should reflect the consequence of the failure the task targets, not the find rate in isolation. | Task review |
| Site PM governance procedure | Every recommended change is checked against the related RCM study or MTBF review that justifies it before the PM plan is updated. | Related records |
| Site PM governance procedure | The net effect of the review — hours released, tasks changed, plan updated — is quantified before the record closes. | Result |
What it does not cover
- A task recommended for deletion with no check on the failure consequence behind it, which risks removing the one check standing between normal running and a severe, low-frequency failure.
- Find rate reported with no reference to whether the task addresses a real failure mode, which conflates a task that's simply misdirected with one that's genuinely no longer needed.
- Tasks reviewed with no PM Plan Updated confirmation, which leaves the recommendation stranded as a paper exercise that never reaches the working plan.
- Duplicated tasks left in place because no one cross-checked coverage elsewhere, which keeps paying labour twice for the same inspection.
- A recommendation to convert to condition-based monitoring with no owner or instrument identified, which leaves the change unimplementable however sound the logic behind it.
Global
PM Optimization Review requirements by country
SAE JA1011 itself isn't a legal instrument, but the industries that lean on formal RCM logic hardest, and the regulatory backdrop around removing a preventive task, differ enough by region to change how cautiously this review should be run.
SAE JA1011 and SAE JA1012
The template's own basis standard and its companion guidance
JA1011 sets the minimum criteria a process must meet to be called RCM; JA1012 provides the explanatory detail most US reliability teams cite when defending a task deletion or interval change to an auditor.
MSG-3 maintenance steering group logic, alongside JA1011
A parallel, sector-specific RCM logic that overlaps but isn't identical
Where the asset sits in an aviation, rail or nuclear context, task justification may need to satisfy a sector-specific standard as well as, or instead of, JA1011.
EN 13306 and EN 60300 series
The terminology and process framework many EU sites expect this review to align to
EN 60300 covers dependability programme management broadly; aligning task categories to it avoids a mismatch with a European site's existing reliability documentation.
How to complete it
How to complete a pm optimization review, step by step
The numeric fields — times performed, defects found, cost per year — are just counting. The defensibility of the review rests on four judgement calls a reliability engineer has to make deliberately for each task.
Check the failure consequence first. A rare, high-consequence failure can justify keeping a task at a persistently low find rate, provided no cheaper check exists — deletion should follow from consequence and feasibility, not find rate alone.
A task can run reliably, cost little, and still be pointless if it was never checking for the failure mode that's actually occurring. Answer this against current failure data, not the original justification from years ago.
A recommendation to extend, shorten or delete a task means nothing until the PM plan itself is updated. Treat PM Plan Updated as the review's actual close condition, not a formality after the recommendation is written down.
Task Duplicated Elsewhere is easy to mark 'No' from habit. Cross-check against the live PM plan and any condition-monitoring routes, since duplication tends to accumulate exactly where nobody expects it.
What auditors find
Most common pm optimization review findings
The failure modes that repeat across PM optimization reviews sit less in the arithmetic and more in what gets skipped before a recommendation is accepted.
| Finding | Clause | What fixes it |
|---|---|---|
| A task deleted on a zero find rate with no check on failure consequence | SAE JA1011 §5.3 | Require Task Addresses A Real Failure Mode and a documented consequence check before Delete can be selected. |
| Recommendations recorded but PM Plan Updated left at No | Site PM governance procedure | Block record closure until PM Plan Updated is confirmed Yes, or an explicit delay reason is captured. |
| Task Duplicated Elsewhere answered from memory rather than a plan cross-check | Site PM governance procedure | Require the duplicate task's reference whenever Task Duplicated Elsewhere is Yes, forcing an actual lookup. |
| Condition-based conversion recommended with no instrument or owner assigned | SAE JA1011 §5.4 | Make New Frequency 'Condition based' require a linked instrument or route reference before acceptance. |
| Find rate calculated over too short a sample to mean anything | SAE JA1011 §5.4 | Set a minimum Times Performed In Period below which the find rate is flagged low-confidence rather than acted on. |
| Hours released and estimated saving left blank despite tasks deleted or extended | Site PM governance procedure | Require Hours Released Per Year and Estimated Annual Saving wherever Tasks Deleted or Extended exceeds zero. |
Case in point
Case in point: the weekly check nobody dared delete
A weekly visual inspection on a filling line's guarding had run for six years with a find rate of zero — not one defect logged in over three hundred checks. Every annual review noted the number and recommended 'keep as is', because removing a safety-adjacent task felt like the wrong call on paper.
A planner finally traced the task's origin and found it duplicated a daily operator pre-start check on the same guarding, introduced two years after the weekly task was written. The weekly check wasn't protecting anything the daily one didn't already catch — pure duplicated labour, renewed every year because nobody had checked Task Duplicated Elsewhere against the current plan rather than memory.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- MNT-052
- Archetype
- Review
- Record ID
- PMO-2026-000
- Scoring
- Task value rating
- Direction
- High is good
- Singleton
- No
- Basis
- SAE JA1011
- Links
- Links PM Plan, Failure records
- Tags
- Reliability, Optimisation
- Sections
- 4
- Fields
- 43
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
12 fieldsReview ID*
Auto sequence. Format PMO-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Both Directions
Optimisation means removing tasks that never find anything as well as adding frequency where failures are being missed. Most programmes only ever add.
Period Reviewed*
Scope*
Reviewed By*
Task review
Repeats12 fieldsTask Description*
Current Frequency*
Times Performed In Period*
Times A Defect Was Found*
Find Rate Percent*
A task finding nothing in fifty attempts is a candidate for extension or removal.
Failures Despite This Task
Task Addresses A Real Failure Mode*
- Yes3 pts
- Partly1 pt
- No0 pts
Task Duplicated Elsewhere*
- No3 pts
- Yes0 pts
Task Cost Per Year
Recommendation*
Keep as is, extend interval, shorten interval, change to condition based, merge or delete.
- Keep as is3 pts
- Extend interval3 pts
- Shorten interval2 pts
- Change to condition based4 pts
- Merge2 pts
- Delete3 pts
- Add verification checks3 pts
- Replace instrument1 pt
New Frequency
Justification
Related records
2 fieldsRCM Study ID
The study that proposed the interval change.
Links to MNT-050 Study ID
MTBF Review ID
The measured intervals behind the change.
Links to MNT-051 Review ID
Result
17 fieldsTasks Reviewed*
Tasks Deleted*
Tasks Extended*
Tasks Shortened*
Tasks Added*
Tasks Changed To Condition Based*
Hours Released Per Year
Estimated Annual Saving
PM Plan Updated*
- Yes3 pts
- No0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Reliability*
Signature*
Planner*
Second Signature*
MNT-052 · record IDs look like PMO-2026-000 · Links PM Plan, Failure records
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Tuning a PM plan from performance data is straightforward arithmetic. What slips is checking a low find rate against failure consequence before deleting a task, and making sure a recommendation reaches the live plan rather than staying a line on last year's review.
Holds the PM optimization review library against the live PM plan, flags any recommendation where PM Plan Updated is still No, and keeps task history connected across review cycles.
Checks any recommended deletion or interval extension against the failure consequence behind the task, so a safety-adjacent check doesn't get removed on find rate alone.
Rolls hours released and estimated annual saving into the operations view, turning the review's task-level detail into a resourcing number leadership can act on.
Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
PM Optimization Review definitions and key terms
- Find rate
- The proportion of times a preventive task actually detects a defect, out of the total times it's performed — the core evidence for whether a task's frequency or existence is justified.
- Proactive task
- A scheduled maintenance action intended to prevent or detect a failure before it occurs, as opposed to a default action taken only after failure.
- Condition-based task
- A check triggered by a measured condition trend rather than a fixed calendar interval, typically used where a failure mode develops with a detectable warning period.
- Default action
- The fallback strategy — run to failure, redesign, or a scheduled discard — applied when no proactive task is technically feasible or worth doing for a given failure mode.
- Task duplication
- Two or more scheduled checks covering the same failure mode on the same asset, usually accumulated as tasks are added over time without cross-checking existing coverage.
FAQ
Frequently asked questions about pm optimization review
What is the PM optimization review template based on?+
It is built against SAE JA1011, the standard that defines what a process must demonstrate — functions, failure modes, consequences, task effectiveness — to be called reliability centred maintenance rather than an informal maintenance review.
What sections does the PM optimization review contain?+
Four sections: Header, Task review, Related records, Result. Together they hold 43 fields, 29 of which are required, with the task review section repeating for each task assessed.
How often is a PM optimization review raised?+
Yearly by default, plus any trigger event such as a task's find rate or cost being flagged outside the normal cycle. Each record gets an ID in the form PMO-2026-000 so it can be traced and referenced from other records.
Why does the review work in both directions — adding and removing tasks?+
Most PM programmes only ever add tasks as new failure modes are found, and rarely remove ones that stop earning their place. This review is built to catch both: tasks with no measurable find rate as candidates for extension or deletion, and failure modes still slipping through as candidates for new or more frequent checks.
What happens to a task with a low find rate but a severe failure mode behind it?+
It isn't automatically deleted. The review checks Task Addresses A Real Failure Mode and the consequence of that failure first — a rare but severe failure mode can justify keeping a task even at a persistently low find rate.
Can the PM optimization review template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust the recommendation categories to match how their own planning function actually works.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Reliability and Predictive Maintenance
Root Cause Analysis
Finds out why something happened rather than who was involved
Equipment Failure Report
Records that an asset has failed and stopped or degraded production
Failure Mode Record
Records how an asset failed, using standard failure mode codes rather than free text
Repair Record
Records what was actually done to fix the asset, including parts replaced and settings changed
Temporary Repair Record
Records a repair that is not permanent, with an expiry date and a plan for the proper fix
Repeat Failure Review
Reviews an asset that has failed the same way more than once
More in Reliability
Equipment FMEA
Works through how an asset could fail, what the effect would be and how likely it is to be detected
Reliability Centred Maintenance Study
Decides the right maintenance strategy for each failure mode, from run to failure through to condition monitoring
MTBF Review
Reviews mean time between failures for an asset or asset class over a period
Root Cause Failure Analysis Trigger
Decides whether a failure warrants a full investigation, based on cost, safety and repeat history
Spares Criticality Review
Decides which spare parts must be held on site based on lead time and asset criticality
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- SAE JA1011 — Evaluation Criteria for RCM Processes
- SAE JA1012 — Guide to the RCM Standard
- EN 60300 — Dependability management
- ISO 14224 — Collection and exchange of reliability data for equipment
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.