It’s Not Greenfield. It’s Not Brownfield. It’s Complicated.
The Operational Readiness Challenge.
Not every project is neatly greenfield or brownfield.
A pure greenfield project is usually about building a new operation from the ground up – new assets, new systems, new people, new procedures and new ways of working.
A pure brownfield project is usually about modifying or improving an existing operation – often while keeping production, safety, compliance and business continuity intact.
But many projects sit somewhere in the middle.
These are blended greenfield/brownfield projects – where something new is being introduced into an existing operating environment.
The challenge is that these projects are often managed as if they fit neatly into one category, when the real readiness risk sits in the overlap between new capability and existing operations.
That could be:
- Autonomous equipment added to an existing mining fleet
- Advanced process control layered over existing plant equipment
- New flotation, filtration or ore sorting circuit tied into a live process plant
- Solar, battery or microgrid system connected to existing site power infrastructure
- New underground mine feeding an established processing plant; or a
- New production line added to an existing manufacturing facility.
This is where Operational Readiness becomes more complex: the project is not starting with a blank sheet, but it also cannot rely entirely on existing systems, procedures and capability.
Why blended projects are different
In a greenfield project, the focus is often on building the full operating capability before start-up: organisation structure, recruitment, training, operating procedures, maintenance strategies, spares, systems, asset data and commissioning support. EnterpriseIS’ OR Framework treats these as connected readiness elements that need to be planned across the project lifecycle, not as separate workstreams to be picked up later.
In a brownfield project, the focus is usually on safely implementing change within a live operating environment – managing tie-ins, shutdown windows, existing procedures, system updates, operational constraints and workforce impacts.
A blended project has to do both.
That is the part that often gets underestimated.
A simple example: new technology in an existing operation
Introducing new technology into an existing plant might look like a straightforward brownfield change on the surface: install the equipment, integrate the software and manage the shutdown or tie-in.
But from an Operational Readiness perspective, it can have a strong greenfield component.
The equipment or software may be new. The operating philosophy may change. Existing procedures may no longer be fit for purpose. Operators may need to work differently. Maintainers may need new skills. Asset data, spares, maintenance plans, cyber controls, reporting and troubleshooting processes may all need to be created or updated.
At the same time, the change has to integrate with the existing operation.
That means the new capability still has to work within existing production targets, permit systems, isolations, control rooms, maintenance systems, safety processes, shift structures and business routines.
So the question is not simply, “Is the new technology ready?”
The better question is:
“Is the whole operation ready to absorb, operate, maintain and sustain the change?”
What needs to be done differently?
Blended projects need a more deliberate OR approach, starting with a simple question: what can be adopted, what needs to be modified, and what must be developed from scratch?
- Adopt what already exists
If existing procedures, maintenance tactics, training material or systems are still fit for purpose, then just adopt them. - Modify what partly fits
If existing material is close but not quite right, adapt it for the new equipment, technology, risks or operating context.
- Develop what is genuinely new
Where the project introduces new capability, new risks or new ways of working, build what is genuinely missing from scratch: procedures, training, asset data, maintenance plans, spares and support systems.
This “adopt, modify or develop” approach is reflected in EnterpriseIS’ OR execution methodology. This avoids two common mistakes: rebuilding everything unnecessarily, or assuming existing systems are good enough when they’re not.
Why recognising the difference matters
If a blended project is treated as purely greenfield, the team may miss the real-world constraints of the existing operation. If it is treated as purely brownfield, the team may underestimate the new capability that needs to be built. Either way, the risk usually appears late – during commissioning, handover, ramp-up or early operations.
That can lead to slow start-up, operational disruption, poor handover, unclear ownership, incomplete training, missing spares, unreliable asset data and avoidable pressure on the operations team – all of which can result in lost production, lost revenue and avoidable cost.
Operational Readiness is about closing those gaps before they become start-up problems. EnterpriseIS’ framework reinforces that successful start-up depends not only on the physical asset being delivered, but also on the people, systems and processes being ready to operate and maintain that asset.
Final Thoughts
Blended greenfield/brownfield projects are becoming more common, especially as organisations modernise existing operations with new technology, automation, renewable energy systems, processing capability and infrastructure.
The physical project may be new.
The operating environment may already exist.
But the readiness challenge sits in the integration between the two.
For project teams, the practical takeaway is simple: do not classify the project once and move on. Test each readiness element against the real operating context, then decide what can be adopted, what must be modified and what needs to be built.
Recognising blended elements early allows the project and operations teams to focus effort where it matters most: making sure the new capability can be safely, reliably and sustainably absorbed into the business from day one.