The most expensive assumption in operational readiness is that it comes in one flavour. A greenfield build, a brownfield expansion and a restart from care and maintenance all end the same way, with a plant that must run at design intent from day one, but they start from three different places. A readiness program built for the wrong one fails politely, on schedule, at handover.
The framework does not change. The nine readiness streams apply to all three, and the checklist still gets scored against first production. What changes is which streams dominate, where the data comes from, and what kills you if you get it wrong.
Quick Links
The short answer
A greenfield build creates everything from the design drawings, and the readiness risk is starting too late. A brownfield expansion inherits live systems and a running plant, so the risk is integration and a ramp-up that drags the existing operation down. A restart looks like brownfield but behaves like greenfield with worse data: the plant exists, and almost nothing recorded about it can be trusted until it is re-verified.
The three starting points at a glance
| Dimension | Greenfield | Brownfield expansion | Restart from care and maintenance |
|---|---|---|---|
| What exists at day zero | Drawings and contracts | A running plant, live systems, a crew | A dormant plant and a paper history |
| Where the data comes from | Built new, from design and OEM data | Extended from live systems, after checking their debts | Re-verified in the field, because the records describe a plant that may no longer exist |
| Hardest streams | Organisation, systems, vendor data | Operating model, ramp-up, integration | Asset integrity, criticality, statutory re-validation |
| Timeline driver | First ore, 24 to 30 months out | Tie-in and shutdown windows | Commercial restart window, usually compressed |
| The killer risk | Readiness deferred to commissioning | New circuit drags the live plant below plan | “Switch-on” thinking, treating a restart as a resume |
Greenfield: everything is built, nothing is inherited
Greenfield is operational readiness at full scope. There is no register to extend, no crew to redeploy, no systems to integrate. Every stream starts from the design drawings. That is why the readiness clock starts 24 to 30 months before first ore, and why the earliest deadlines are contractual: vendor data requirements written into EPC and OEM purchase orders before they are executed, tagging and hierarchy standards agreed before drawings multiply.
The dominant streams early are organisational readiness and systems: the readiness program itself, then the data architecture everything else loads into. The classic greenfield failure is sequencing, with readiness treated as a commissioning-phase activity and discovered to be a design-phase activity two years too late.
It is also the scenario with the deepest proof behind our approach. We have authored the operational readiness plan and built the maintenance system for a West African greenfield gold plant, and written the readiness standard a major greenfield project is being delivered under, aligned to ISO 55001 through the framework.
Brownfield: the plant you are not building is the one at risk
A brownfield expansion inherits what greenfield must create: statutory registers, a working CMMS, experienced people. That inheritance is the trap. “We already have the systems” quietly becomes “we do not need a readiness program”, and the new circuit then inherits every debt the existing systems carry, including the register that drifted, the master data nobody cleansed, and the maintenance strategy that was inherited rather than built.
The streams that dominate are the ones greenfield finds easiest. The operating model must absorb a new circuit without doubling the organisation. The ramp-up plan carries a constraint greenfield never faces: the expansion must reach nameplate without dragging the running operation below plan, with tie-ins scheduled into real shutdown windows and commissioning staffed without stripping the operating crew. We have delivered exactly that readiness scope on a live-plant expansion, where the tie-in had to pay for itself without costing the base plant a tonne.
Brownfield readiness is smaller than greenfield in build volume and harder in integration. Score it honestly before assuming the inheritance covers you. The readiness scorecard treats an expansion the same way it treats a new build: evidence, not history.
Restart: greenfield’s scope hiding under brownfield’s roof
The restart from care and maintenance is the least written-about scenario and the most deceptive. The plant is standing, the drawings exist, the CMMS still holds ten thousand records, and everything about it whispers brownfield. It behaves like greenfield.
Years of dormancy do three things to readiness. Asset integrity becomes an open question. Seals, linings, instruments and electrical systems degrade in ways a care-and-maintenance regime slows but does not stop, so criticality and integrity assessment come first, because the plant must be re-understood before it can be re-run. The data describes a plant that no longer exists. Strategies, spares levels and master data reflect the operation as it was, not as corrosion, cannibalisation and modification have left it. The licence and the people are gone. Statutory appointments lapsed, approvals need re-validation, and the workforce that knew the plant’s habits dispersed years ago.
That is why our restart work looks the way it does. At a recommissioned nickel concentrator in Kambalda, Western Australia, we were engaged to support the operational readiness project bringing the plant back to production after a period of care and maintenance, providing specialist reliability engineering to review, assess and report on asset criticality and asset integrity before the restart leaned on either.
The commercial pressure makes it worse. Restarts get sanctioned when a price window opens, so the readiness runway is usually the shortest of the three exactly when the unknowns are largest. A restart scored on its paper history will pass. The same restart scored on evidence usually does not, and the gap between those two scores is the project risk, quantified.
One framework, three emphases
The scenarios do not need three frameworks. They need one framework applied with open eyes about where the weight falls:
| Scenario | Streams that surge | Streams that flex down |
|---|---|---|
| Greenfield | Organisational readiness, systems and technology, people and capability | Nothing. Full scope, longest runway |
| Brownfield | Operating model and processes (the ramp-up), supply chain and logistics (the integration) | HSE and finance streams largely extend what exists |
| Restart | Asset management and maintenance readiness (integrity), HSE risk and regulatory compliance (re-validation), people and capability (the rebuild) | Systems and technology exist, but every record must earn back trust |
If the distinction between the asset streams and the rest of the scope is new territory, maintenance readiness vs operational readiness draws that line in full.
Match the readiness program to the project you actually have
Whichever starting point you are at, the sequence is the same: find out where you stand, on evidence. The free readiness scorecard scores all nine streams against your first production date in about five minutes, whether greenfield, expansion or restart. When the score says the gap is real, that is what our operational readiness consultants close.
Frequently asked questions
Is operational readiness different for brownfield projects?
The framework is the same; the emphasis inverts. Brownfield inherits registers, systems and people, so the build volume is smaller, but integration risk is larger. The operating model must absorb the new circuit, tie-ins must land in real shutdown windows, and the ramp-up must not pull the running plant below plan. The inherited systems also carry inherited debts, which the readiness program must surface rather than assume away.
What makes restarting a plant from care and maintenance harder than greenfield?
Greenfield builds from a truth it creates; a restart must first discover the truth. Dormant years degrade asset integrity, the historical data describes the plant as it was rather than as it is, statutory appointments and approvals have lapsed, and the workforce that knew the plant is gone. Restart readiness therefore starts with criticality and integrity re-verification, and usually on the shortest runway of the three, because restarts are sanctioned when a price window opens.
Can you trust the old CMMS data when restarting a plant?
Treat it as a hypothesis, not a record. The register, strategies and spares levels reflect the operation before dormancy, modification and cannibalisation. Field re-verification decides what survives: walk the plant against the register, re-run criticality on the plant that exists, and rebuild strategy and spares from what the verification finds rather than what the archive remembers.
Who should own operational readiness on a brownfield expansion?
The same answer as any readiness program, a named lead answering to the operator, with one addition: the operations manager of the running plant must sit inside the governance rather than outside it. The expansion’s biggest risk is borne by the existing operation, so the person accountable for the base plant’s performance needs a gate-level voice in readiness decisions.
Do the nine readiness streams apply to all three project types?
Yes. Every stream exists in every scenario; what changes is weight and sequence. Greenfield runs all nine at full scope from the design. Brownfield leans on operating model, ramp-up and integration while extending inherited statutory and financial structures. A restart front-loads asset integrity, criticality and statutory re-validation before the rest of the scope can be trusted.