The two terms get used interchangeably on projects, in tenders, and in most of what is written about them. We have caught the habit in our own guides. The interchange is not harmless. Projects have funded a “readiness” scope, received a maintenance build, and discovered at handover that nobody had planned the statutory appointments, the operating budget, or the ramp-up assumptions. The scope gap was hiding inside a vocabulary gap.
Here is the precise line between the two, what each one covers, and how to tell which one your project has actually bought.
Quick Links
The short answer
Maintenance readiness prepares the asset to be maintained: strategy, asset register, CMMS data, spares, work management. Operational readiness prepares the whole organisation to operate. It contains maintenance readiness, plus the people, operating model, statutory, financial and stakeholder streams. A project can pass maintenance readiness and still be unable to legally, financially or organisationally run the plant. If your scope only says “maintenance readiness”, the rest is unowned.
Maintenance readiness vs operational readiness at a glance
| Maintenance readiness | Operational readiness | |
|---|---|---|
| Question it answers | Can we maintain this asset from day one? | Can we run this operation from day one? |
| Scope | The asset and its maintenance system | The organisation: people, processes, systems, asset, compliance, finance, community |
| Relationship | A subset, roughly a third of the full readiness scope | The whole. Nine streams, of which the asset streams are three |
| Core deliverables | Criticality, maintenance strategy, asset register and hierarchy, CMMS master data, PMs, spares and materials, work management | All of that, plus operating model, org structure and recruitment, ramp-up plan, statutory registers and appointments, operating budget, stakeholder commitments |
| Typical owner | Maintenance manager and the maintenance management function | A named operational readiness lead, reporting to the operator |
| Must start by | 24 months before first ore, because vendor data requirements go into the EPC and OEM purchase orders | 24 to 30 months before first ore |
| Risk if it is all you do | A maintainable plant nobody is organised, authorised or funded to operate | None. Done properly it includes the other |
What maintenance readiness covers
Maintenance readiness is the asset half of the job, and it is the half with the longest lead times. Done properly it means:
- Criticality assessment across the major equipment, so effort follows consequence.
- Maintenance strategy built from the design, asset by asset, before the equipment arrives, using full FMECA or RCM on the critical assets.
- Asset register and hierarchy built from design drawings and equipment lists, structured for the CMMS.
- CMMS master data loaded and tested, with work orders generating correctly before start-up.
- Spares and materials. Critical spares analysed with a method you could defend, long-lead spares ordered against their lead times, a materials catalogue written to a standard.
- Work management. The process designed end to end, from notification to close-out, so the team runs a planned operation.
That list is concrete because it has to be. On a recent iron-ore plant, working from the design drawings while construction ran, HolisticAM built 353 planned routine tasks across 23 asset lines, packaged as nine SAP-ready deliverable types, in a 12-week pre-commissioning programme, loaded and CMMS-ready before start-up. That is what “maintenance ready” looks like as evidence rather than intent.
Maintenance readiness also owns the deadline nobody can move: vendor data requirements (data books, manuals, spares lists) must be written into the EPC and OEM purchase orders before those contracts are executed, around 24 months before first ore. Miss that window and the maintenance data gets purchased back later at the contractor’s price.
What operational readiness adds
Operational readiness contains all of the above, and then covers the six things a maintenance-ready plant can still be missing. Each is a stream in its own right, set out in the operational readiness framework:
- A readiness organisation. A named lead, a costed plan with its own budget and schedule, review gates with named approvers.
- People. The operations and maintenance org structure drawn to position level, recruitment sequenced against construction milestones, key technical appointments confirmed.
- An operating model and a ramp-up plan. What your team does versus contractors, and a production ramp-up curve whose assumptions are written down and defensible.
- Statutory and HSE readiness. Registers established and populated, operating approvals tracked separately from construction approvals, statutory position holders appointed before the first work is done. Construction approvals do not authorise operation.
- Finance and commercial readiness. A year-one operating budget built bottom-up from the maintenance plan, operating contracts assessed against design intent, the asset established in the financial system.
- Stakeholder and community readiness. A live engagement plan, confirmed social-licence conditions, a grievance mechanism that runs through construction into operations.
Maintenance readiness covers three of the nine readiness streams. The other six decide whether the maintainable plant is allowed, staffed and funded to run.
None of that is maintenance work. All of it decides whether the maintainable plant is allowed to run, staffed to run, and funded to run. The full breakdown, 27 checkpoints across the nine streams each carrying the date it must be complete before first ore, is published in our operational readiness checklist.
The two failure modes the confusion creates
Maintenance-ready, operationally blind. The project bought a maintenance build and called it readiness. The CMMS is loaded and the spares are on the shelf, and yet the statutory position holders are not appointed, the operating budget was scaled from someone else’s benchmark, and the ramp-up curve is a line on a slide with no assumptions behind it. The plant can be maintained. It cannot yet be legally or commercially operated.
Operationally planned, maintenance-hollow. The reverse, and just as common: a readiness framework that reads well (governance, gates, a glossy plan) sitting on top of an empty CMMS. A readiness plan is only worth the maintenance system built underneath it. When the first breakdown arrives and there is no work order to raise, the plan was never real.
Both failures trace to the same root: the terms were treated as synonyms, so one half of the scope was never owned. NASA’s Systems Engineering Handbook gives the reason neither half can be recovered cheaply later: design decisions commit about 75% of life-cycle cost while only about 15% has been spent. Readiness scope missed at design is bought back at a premium, in the worst year to be paying premiums.
Who owns maintenance readiness vs operational readiness?
- Operational readiness is owned by a named readiness lead who answers to the operator, not to the construction contract. The whole nine-stream scope reports through them.
- Maintenance readiness is owned inside that structure by the maintenance function, which is why the maintenance manager’s start date matters so much. An appointment made at commissioning inherits decisions that should have been theirs.
- The EPCM question comes up on every project: can the build contractor deliver readiness? An EPCM assessing readiness is grading its own construction, and a readiness plan handed across a scope seam rarely survives first ore. The full argument is in who should deliver operational readiness: specialist vs EPCM vs advisory.
Which one does your project need?
A greenfield build: the full operational readiness scope, started 24 to 30 months before first ore. Maintenance readiness alone leaves six streams unowned.
A brownfield expansion: operational readiness with the emphasis shifted. The statutory registers and CMMS exist, so the work is integration, and the ramp-up must not drag down the running plant. The maintenance-readiness streams still need their own build for the new circuit.
An operating site fixing a weak maintenance foundation: maintenance readiness on its own is legitimate here, being the asset streams rebuilt for a plant that is already running. That is maintenance management work rather than a readiness project.
Where the readiness effort actually lands differs sharply between these project types, and the trap in each is different. That comparison is set out in greenfield vs brownfield vs restart.
Not sure which you have bought? Score the project. The free readiness scorecard runs all nine streams in about five minutes and bands the result against your first ore date. If only the asset streams score well, you have a maintenance build, not readiness.
Find out which one you have actually bought
Pull your readiness scope and count the streams it covers. Three streams is a maintenance build. Nine is operational readiness. The free readiness scorecard does the counting for you, scored against your first ore date, and shows which streams are weakest on screen.
Frequently asked questions
Is maintenance readiness part of operational readiness?
Yes. Maintenance readiness covers the asset streams (maintenance strategy, asset register, CMMS data, spares, work management) which are roughly a third of a complete operational readiness scope. Operational readiness adds the organisational, people, statutory, financial and stakeholder streams that decide whether the maintainable plant is actually allowed, staffed and funded to run.
Can a project be maintenance ready but not operationally ready?
Easily, and it is one of the most common readiness failures. The CMMS is loaded and spares are on the shelf, but no statutory appointments are confirmed, the operating budget is unbuilt, and the ramp-up assumptions were never written down. The plant can be maintained but not yet operated.
Who is responsible for maintenance readiness on a project?
The maintenance function, typically the incoming maintenance manager, working inside the operational readiness structure under a named readiness lead who answers to the operator. If that appointment has not been made 12 months before first ore, the decisions get made by whoever is nearest, and inherited by whoever arrives.
How long does maintenance readiness take before first ore?
The long-lead items start about 24 months out, because vendor data requirements have to be in the EPC and OEM purchase orders before they are executed. Criticality, strategy, the asset register and spares analysis run from about 18 months, and the loaded, tested CMMS is a 6-months-out proof point. A maintenance readiness plan should fix these dates against the contract schedule rather than a generic countdown. A capable crew can compress the build, and a 12-week pre-commissioning CMMS build is achievable, but only if the contracts and data standards were set early.
Does an EPCM contractor deliver maintenance readiness or operational readiness?
EPCMs commonly deliver parts of maintenance readiness (registers, data, sometimes strategy) because those flow from documents they control. Full operational readiness is harder for a build contractor to own credibly: an EPCM assessing readiness is grading its own construction, and the organisational, statutory and financial streams sit with the operator. Most projects that get this right keep readiness accountability with an independent party answering to the operator.