On this page
- In short
- Reconstruct the Failure History Before Optimising the Strategy
- Compare the Failure History with the Existing Strategy
- Failure Events Are Only Part of the Operating History
- Optimisation May Lead to Different Maintenance Decisions
- Dirty CMMS Data Can Still Contain Valuable Reliability Evidence
- Improve the Data Being Created in the CMMS
- A Practical Workflow from Work Orders to PM Decisions
- Connecting Maintenance Strategy with Operating Evidence
- Key questions
In short
A mature maintenance program can have thousands of completed work orders and still have surprisingly little usable failure history. Yet this historical data still contains valuable evidence about asset failures, their effects and consequences, and the corrective actions taken in response. The challenge is to structure that information so it can be used confidently in maintenance strategy and PM optimisation decisions.
Related platform modules
A mature maintenance program can have thousands of completed work orders and still have surprisingly little usable failure history.
Over time, CMMS records can become inconsistent, incomplete or difficult to interpret, this is what many maintenance teams are increasingly referring to as dirty or fragmented data. The same failure may be described differently by different technicians, work may be recorded against different levels of the asset location hierarchy, and failure information may be buried in free-text notes.
In many CMMS environments, failure coding presents another limitation. Failure codes may not exist at all, or they may be defined too generically to support consistent adoption and meaningful reliability analysis.
Yet this historical data still contains valuable evidence about asset failures, their effects and consequences, and the corrective actions taken in response. The challenge is to structure that information so it can be used confidently in maintenance strategy and PM optimisation decisions.
Reconstruct the Failure History Before Optimising the Strategy
A work order does not necessarily represent a failure event.
It may document an inspection, planned replacement, condition finding, follow-up activity or routine maintenance. A single work order may also contain evidence of multiple failure modes, while another may contain too little information to determine what happened with reasonable confidence.
Using raw work-order counts as failure counts can therefore distort the apparent behaviour of an asset.
A more useful analysis places each relevant work order within the asset’s operating context and structures the available failure information by asset and maintainable item. Within Nexaan, a failure mode is represented by:
Component + failure mechanism + cause
Dates, labour, costs and other supporting maintenance information can also be considered alongside the failure information.
This is where Nexaan Work Order Analyser supports the process. Historical work-order descriptions, technician notes and associated maintenance data can be classified against a controlled taxonomy, allowing records written in different ways to be analysed within a consistent structure.
The quality of the underlying evidence remains visible throughout the process. Records that can be classified confidently can contribute accordingly, while ambiguous or incomplete records can be identified rather than forced into a category simply to produce a cleaner dataset.
Compare the Failure History with the Existing Strategy
Once historical records have been structured, they become much more useful for reviewing the maintenance strategy.
Engineers can compare the failure modes observed in operation with the tasks intended to manage them and identify gaps between the strategy and actual asset behaviour.
A recurring failure mode may have no corresponding PM task. An existing task may have a weak relationship with the failure mode it is intended to manage. Several maintenance activities may address the same failure, while a single task may manage multiple failure modes. An appropriate task may also be performed at an interval that no longer reflects operating experience.
The analysis may also show that changing an interval would have little effect because the existing task does not adequately address the failure mode observed in operation.
These findings provide a stronger basis for optimisation than reviewing PM frequencies or maintenance workload in isolation. They allow engineers to examine the relationship between the original maintenance strategy and the evidence accumulated through operation.
Failure Events Are Only Part of the Operating History
Consider a population of ten similar assets observed over the same period. Two experience a confirmed failure while eight operate through the observation period without one.
Using only the two failures discards information contained in the operating history of the remaining assets.
Those non-failure observations contribute to understanding how the asset population has performed over time and can be considered as suspension data points when evaluating maintenance intervals.
Nexaan's PM Optimisation uses confirmed failures and suspension history against a selected reliability target. This allows the observed operating history to be evaluated in relation to the selected reliability target rather than basing an interval decision solely on the timing of recorded failures.
The resulting recommendation can then be considered alongside cost and risk before an engineer approves a change to the maintenance task within the Reliability Centred Maintenance (RCM) process in Nexaan’s Asset Strategy module.
Optimisation May Lead to Different Maintenance Decisions
PM optimisation is often associated with extending intervals and reducing maintenance workload, but the evidence may support several different outcomes.
An interval may be unnecessarily conservative and suitable for extension. Another may expose the asset to an unacceptable level of failure risk and require the maintenance task to be performed more frequently.
In other cases, the analysis may indicate that the task itself should be reconsidered. This may occur where the existing task has a weak relationship with the failure mode, or where failures have not been evident or recorded in the available operating history. The review may also support reconsidering the maintenance task type, including a change from Preventive Maintenance (PM) to Condition Based Maintenance (CBM) or Run to Failure (RTF).
The appropriate decision depends on the observed failure behaviour, desired reliability, consequence of failure, cost and operational context.
For this reason, Nexaan PM Optimisation presents the basis for an interval recommendation for engineering review rather than automatically changing the maintenance strategy. Engineers can review the supporting reliability, cost and risk information before approving a governed, timestamped change.
This retains engineering accountability while reducing the analytical effort required to reach the decision.
Dirty CMMS Data Can Still Contain Valuable Reliability Evidence
Many organisations delay deeper analysis because their CMMS history is inconsistent or incomplete. A full data-cleaning exercise can become a significant project, particularly across years of work orders, coding conventions and asset structures.
Historical records do not all carry the same analytical value. Some contain enough information to identify a failure mode confidently, while others remain partial or ambiguous. Maintaining that distinction is more useful than forcing every record into a standard classification.
Automated work-order analysis can structure and classify this history at scale, allowing engineers to focus on the records and decisions that require engineering judgement.
Improve the Data Being Created in the CMMS
Historical analysis can also reveal where maintenance execution is producing weak reliability data.
If recurring failures are consistently hidden inside free-text notes, recorded at the wrong hierarchy level or assigned generic failure codes, those patterns can inform improvements to future data capture.
Nexaan's Catalog Profile converts asset-type-specific failure modes from the RCM analysis into CMMS-ready failure codes. These codes retain their relationship with the underlying failure mode and the maintenance task associated with detecting or managing it.
As these structures are carried into the CMMS, future maintenance history becomes easier to interpret and compare.
This creates a practical reliability feedback loop:
- Defined failure modes
- CMMS execution
- structured failure history
- maintenance strategy review
- approved strategy changes
- failure information recorded back into the asset’s RCM analysis
- improved execution data
Historical records contribute evidence for current decisions, while improvements to failure coding and asset context increase the quality of evidence available for future reviews.
A Practical Workflow from Work Orders to PM Decisions
For organisations looking to use historical CMMS data in PM optimisation, the process can be approached in nine stages.
- 1
Establish the engineering context
Confirm the relevant asset hierarchy, maintainable items, equipment classifications and failure-mode structure.
- 2
Bring together the existing strategy and operating history
Combine current PM tasks and frequencies with relevant work orders, technician notes, dates, labour, cost and maintenance history.
- 3
Structure the historical records
Map work-order information into consistent asset, component and failure contexts so that records written differently can be analysed together.
- 4
Establish the usable failure evidence
Differentiate confirmed failures from inspections, planned work, routine maintenance, ambiguous records and other events that should not automatically be treated as failures.
- 5
Include suspension history
Consider the wider operating history alongside confirmed failures when assessing asset performance.
- 6
Compare observed failures with the existing strategy
Review whether existing PM tasks address the failure modes occurring in service and identify missing, duplicated or ineffective maintenance activities.
- 7
Evaluate the maintenance interval
Assess the existing interval using the required reliability target together with relevant cost and risk considerations.
- 8
Review and approve the decision
Allow the responsible engineer to review the evidence and recommendation before approving a governed change to the maintenance strategy.
- 9
Record the failure information back into the RCM analysis
Record relevant failure events, effects, consequences and supporting information back into the asset’s RCM analysis within the Asset Strategy module, against the relevant failure mode, for future reference and knowledge.
Applying this process consistently across a large historical dataset is difficult to sustain manually. Automated classification and analysis can reduce that effort while preserving engineering review at the points where judgement is required.
Connecting Maintenance Strategy with Operating Evidence
Asset-intensive organisations generally already have the core information required for this process distributed across their engineering systems.
RCM and FMEA work defines failure modes and maintenance strategies. The CMMS manages execution and accumulates operational history. Reliability teams review performance and determine where strategies need to change.
The opportunity is to connect these activities so that operational evidence can feed back into maintenance strategy decisions more systematically.
Within Nexaan, Work Order Analyser structures historical maintenance records into usable failure evidence. PM Optimisation evaluates confirmed failures and suspension history against reliability targets, cost and risk. Catalog Profile carries governed failure information into CMMS-ready structures so that future maintenance history can be captured more consistently.
The resulting feedback loop allows operational evidence from the CMMS to inform maintenance strategy reviews, while approved strategy changes improve how future maintenance and failure information is captured.
For teams with years of accumulated maintenance history, this creates a practical way to extract more engineering value from existing data and use it to support maintenance decisions that can be reviewed and explained.
Key questions
Is a work order the same as a failure?
A work order does not necessarily represent a failure event.
Does preventive maintenance optimisation always mean extending intervals?
PM optimisation is often associated with extending intervals and reducing maintenance workload, but the evidence may support several different outcomes.
How does PM Optimisation use failure and suspension history?
Nexaan's PM Optimisation uses confirmed failures and suspension history against a selected reliability target. This allows the observed operating history to be evaluated in relation to the selected reliability target rather than basing an interval decision solely on the timing of recorded failures.
When should a preventive maintenance task change to condition based maintenance or run to failure?
The appropriate decision depends on the observed failure behaviour, desired reliability, consequence of failure, cost and operational context.
Does PM Optimisation change the maintenance strategy automatically?
For this reason, Nexaan PM Optimisation presents the basis for an interval recommendation for engineering review rather than automatically changing the maintenance strategy. Engineers can review the supporting reliability, cost and risk information before approving a governed, timestamped change.
