Two questions decide whether operational readiness gets funded properly on a capital project: when does it need to start, and what will it cost? The timing question has a precise answer. The cost question mostly gets answered badly, with vendor claims that, in the proposals we have reviewed, differ by an order of magnitude with no published basis behind any of them. This article answers both the way we scope real programs: the timing counted back from first production, the factors that actually drive cost, how credible pricing is structured, and the honest arithmetic of what skipping the work costs instead.
HolisticAM (Holistic Asset Management) is an Australian reliability engineering and asset management consultancy that delivers operational readiness on mining and heavy-industry capital projects in Australia and West Africa. What follows is the method we use, not a rate sheet; you will find no invented benchmark figures here, and the article explains why.
Key takeaways: Operational readiness should start at project sanction, because the readiness horizons for maintenance strategy, spares, systems and people are measured in months and years, not weeks. Cost is driven by scope breadth, asset count, project type and data quality, not by a flat percentage anyone can quote you. Credible pricing is staged, with a fixed-scope first step, so commitment follows evidence.
In This Guide
When operational readiness should start: at sanction
The call to start operational readiness belongs at project sanction, not during construction or commissioning. That is not a consultant’s preference; it is arithmetic that runs backwards from first production.
A readiness program has deliverables with long lead times. Maintenance strategy built from failure modes on critical equipment wants to begin while the design is still settling, because that is when it can still influence equipment selection, access and monitoring provisions. Spares with long procurement lead times must be identified early enough to be on site before they are needed. CMMS master data takes months to build and load properly. People need to be recruited and trained before handover, not after. Our operational readiness checklist sets out 27 checkpoints across the nine readiness streams, each with a required-by horizon; the earliest sit around two years before first production, and the checkpoints roll forward through 18, 12 and 6-month horizons from there.
The deeper reason for starting early is that the biggest cost decisions are made before operations ever sees the plant. NASA’s Systems Engineering Handbook estimates that during design only about 15% of costs have been spent, but the design itself commits about 75% of life-cycle costs (NASA SEH section 2.5). Operational readiness started at sanction gets a voice while that 75% is still being committed. Started during commissioning, it inherits every decision already locked in.
Starting late does not usually change what the work costs to do. It changes what it costs to catch up: compressed timelines, premium freight on spares, training squeezed into commissioning chaos, and readiness gaps discovered by breakdown instead of by gate review. The pattern differs again for greenfield builds, brownfield expansions and restarts, but the direction never does: later means more expensive, in ways that rarely appear on the readiness budget line.
What actually drives the cost of operational readiness
Anyone quoting an operational readiness price without asking the following questions is guessing. These are the drivers we scope against:
- Scope breadth. A full program spans nine streams, from maintenance strategy through spares, systems, people and licence requirements (the operational readiness framework explains them). A program covering only the streams your project team cannot already carry costs correspondingly less than a full nine-stream build; the question is which streams are genuinely covered.
- Asset count and criticality profile. The maintenance-strategy stream scales with the number of asset lines and how many warrant deep analysis. A concentrator with dozens of asset lines is a different program from a single processing train.
- Project type. Greenfield programs build everything from nothing. Brownfield expansions integrate with live systems and standards. Restarts inherit stale data and unknown asset condition that must be assessed before anything can be trusted. Same streams, different effort profiles.
- Data starting point. Whether OEM manuals, drawings and equipment lists exist, in what state, and how much master data must be created versus validated. Poor incoming data is the single most common source of scope growth.
- Delivery model. What your owner’s team and EPCM carry versus what the readiness partner delivers, and how much of the work is coaching your people versus producing deliverables for them.
- Timeline. A program that starts at sanction spreads its cost across the project’s life. The same scope compressed into the final months costs more and delivers less.
Two projects with the same nameplate capacity can legitimately land far apart on readiness cost because of these factors. That is why published benchmark figures for operational readiness diverge so wildly, and why we decline to add another one.
| Cost driver | What moves the cost |
|---|---|
| Scope breadth | How many of the nine streams the program must carry |
| Asset count and criticality | How many asset lines exist, and how many earn deep strategy work |
| Project type | Greenfield builds from nothing; brownfield integrates; restarts must first prove what can be trusted |
| Data starting point | Whether manuals, drawings and master data exist, and in what state |
| Delivery model | The split between owner’s team, EPCM and readiness partner; coaching versus producing |
| Timeline | Runway from sanction spreads cost; compression concentrates it and adds recovery work |
How credible operational readiness pricing is structured
You cannot price a program properly before the gaps are known, and any vendor who does is pricing their risk into your fee. The structure that protects both sides:
- A fixed-scope, fixed-fee first step. A diagnostic that assesses readiness against every stream, produces the gap register and roadmap, and prices the program from evidence. Bounded cost, defined deliverable, no open-ended commitment. That is exactly what our operational readiness assessment is for.
- Staged delivery aligned to project gates. The program is scoped and costed in phases that match the project schedule, so each stage’s spend is approved against the previous stage’s evidence, and the readiness budget appears in the project budget as defined packages rather than one opaque number.
- Scope boundaries in writing. What is included, what the owner’s team carries, what the EPCM carries, and what is explicitly excluded. Most readiness cost disputes are boundary disputes that were never written down.
- Deliverables the site keeps. Strategy, plans, data and trained people that remain when the engagement ends. A readiness program’s cost should be judged against what is left behind, not the daily rate that produced it.
If you take one test away: ask any prospective readiness partner what their fixed first step costs and what it delivers. A clear answer to that question predicts the rest of the engagement.
The other side of the ledger: what skipping it costs
The cost of operational readiness is visible and budgetable. The cost of its absence arrives disguised as operations: a first year run reactively, emergency spares bought at premium prices and freight, unplanned downtime through ramp-up when every lost tonne is hardest to win back, and a maintenance team building its strategy while firefighting the assets it was never prepared for. Our guide to what operational readiness is describes the pattern in full; on the projects where we are brought in late, the recovery work is reliably harder to buy than the readiness would have been.
That comparison, not any benchmark percentage, is the honest business case. Price the readiness program from a scoped diagnostic, price the reactive-first-year scenario from your own project’s production value, and the decision usually makes itself.
Scoping a readiness program with HolisticAM
HolisticAM delivers operational readiness across Australian and West African mining and heavy industry, from single-stream support through full nine-stream programs. Every engagement starts the same way: a fixed-scope, fixed-fee operational readiness assessment that maps your project’s gaps and prices the program from evidence. If you want a quick self-assessment first, the free readiness scorecard takes a few minutes and shows where you stand.
Frequently asked questions
How much does operational readiness cost?
There is no credible flat answer, and published figures diverge wildly because the honest answer depends on scope breadth (how many of the nine readiness streams), asset count and criticality, project type (greenfield, brownfield or restart), and the state of your incoming data. Credible pricing starts with a fixed-scope, fixed-fee diagnostic that maps the gaps, then prices the program in stages from that evidence rather than quoting a number before the gaps are known.
What drives the cost of an operational readiness program?
Six factors dominate: how many readiness streams are in scope, the number and criticality of asset lines, project type (a restart’s stale data costs more to trust than a greenfield’s clean sheet), the quality of incoming OEM and engineering data, the split of work between the owner’s team, the EPCM and the readiness partner, and how much runway the program has. Two same-sized projects can legitimately land far apart across these factors.
Is operational readiness worth the cost on a smaller project?
The streams still apply; the depth scales. A smaller project needs the same questions answered about maintenance strategy, spares, systems and people, but proportionate effort per stream and fewer assets analysed deeply. The scoping logic is identical: run a bounded diagnostic, find which streams are genuinely covered already, and spend only where the gaps are. Skipping readiness entirely costs a small project the same reactive first year it costs a large one, at a scale it is often less able to absorb.
Why do operational readiness cost estimates differ so much between providers?
Because they are usually pricing different things without saying so: different stream coverage, different depth of maintenance-strategy analysis, different assumptions about who builds the CMMS data, and different amounts of risk priced into a premature fixed number. The fix is structural, not comparative: get every proposal restated against the same scoped gap register from a diagnostic, with boundaries in writing, and the spread collapses.
What does it cost to skip operational readiness?
The bill arrives as operations rather than as a budget line: a reactive first year, emergency spares at premium prices, unplanned downtime through ramp-up when lost production is hardest to recover, and a maintenance strategy built under fire after handover. Pricing that scenario against your own project’s production value, next to a scoped readiness program priced from a diagnostic, is the honest version of the business case.