What is Integrated Operations in Mining?

Every mine has departments. Geology, drill and blast, load and haul, processing, maintenance, logistics. Each has its own manager, its own KPIs, its own spreadsheets. Each optimises for its own numbers. And in doing so, each quietly undermines the operation next door.

Integrated Operations is the philosophy, and increasingly the infrastructure, that says: stop optimising pieces. Optimise the whole system, from pit to port, as a single connected operation. It sounds obvious. Getting there is anything but.

Why Mining Needs This Now

The easy ore is gone. Global copper grades have dropped from around 1.5% in 1990 to below 0.6% at most major producers today. Gold grades across most active open pits sit at 1 to 2 g/t, down from 4 to 7 g/t a century ago. According to S&P Global’s 2026 Mine Cost Outlook, total cash cost per tonne of ore treated rose 27.8% between 2021 and 2024, from US$23.64 to US$30.21. Copper mining stripping ratios are climbing again, back up to an estimated 1.80:1 in 2025 after bottoming at 1.47:1 four years earlier.

These are structural headwinds, not cyclical ones. When grades decline and costs rise simultaneously, squeezing another 2% out of truck utilisation or shaving a minute off shovel hang time is not going to close the gap. The gains left on the table are not within departments. They are between them.

That is the core argument for Integrated Operations. Individual unit improvements have largely been captured. The remaining value sits in the interfaces: between geology and blasting, between blasting and comminution, between the pit schedule and the process plant feed. Capturing that value requires breaking down the walls that separate these functions and running the mine as one interdependent system.

What Integrated Operations Actually Means

At its core, IO is straightforward: every decision should account for its impact on the total value chain, not just the immediate function. The mine geologist, the drill and blast engineer, the dispatcher, the plant metallurgist, and the logistics coordinator should all be working from the same data, toward the same plan, measured against the same outcome.

In practice, that rarely happens. Traditional mining structures create the opposite. Consider a common scenario that plays out at operations worldwide:

A mine manager, measured on extraction cost per tonne, minimises explosive consumption to keep drill and blast costs low. The resulting coarse fragmentation looks fine in the pit. Trucks load easily, the faces are stable. But downstream, the SAG mill chokes on oversize material. Throughput drops. The processing manager cranks up grinding energy to compensate, burning power and liner wear to fix a problem that was created two steps back in the value chain.

Nobody did anything wrong by their own KPIs. The mine manager hit cost targets. The plant manager dealt with what arrived. But the operation as a whole left money on the table. Potentially a lot of it.

IO breaks this cycle by making the value chain visible end-to-end. When the blast engineer can see the real-time impact of fragmentation on mill throughput, and when both are measured against total cost per ounce rather than departmental budgets, behaviour changes. The blast might cost more. The total operation costs less.

Mine-to-Mill: Where IO Delivers the Biggest Wins

If you want to see Integrated Operations in action, Mine-to-Mill is the textbook example. It connects what happens in the blast pattern directly to what happens inside the SAG mill, and the financial results are hard to argue with.

The concept centres on the “fines envelope.” Comminution (crushing and grinding) routinely consumes 30 to 40% of a mine’s total site energy. That is more than haulage, more than ventilation. The energy required to grind rock drops dramatically when the feed arriving at the mill is already closer to the target size distribution. By designing blast patterns to produce finer fragmentation, you shift the energy expenditure from the mill (expensive, electrically intensive) to the pit (relatively cheap, using bulk explosives).

The numbers are compelling. Mill operating cost savings from improved fragmentation run 7 to 10 times greater than the additional blast cost. You spend an extra dollar on explosives and save seven to ten in the mill.

Morila: The Case That Proved It

The Morila Gold Mine in Mali, operated by Randgold Resources, ran one of the most thoroughly documented pit-to-plant optimisation programs in the industry. The team redesigned blast parameters specifically to increase fine material generation, then deployed digital online size analysis systems to monitor and control feed size in real time.

The results: mill throughput lifted from a baseline of 365 tonnes per hour (January–April 2002) to an average of 399 tph over the following 20 months, a 10% improvement achieved without touching the plant. In the mine’s second full year of production (2002), total cash costs dropped to US$74 per ounce and annual output exceeded one million ounces. That exceptional year was amplified by a zone of unusually high-grade ore (head grades peaked at 943 g/t), so the economics reflected both the optimisation and the geology.

By 2003, with grades normalised, production settled at 794,000 ounces and cash costs at US$108 per ounce. The throughput gains, however, persisted. The Morila case has been widely cited in AusIMM and academic literature ever since, and for good reason: the 10% throughput improvement was a direct, repeatable result of integrating blast design with mill performance.

More recent examples tell a similar story. A North American metals operation reported a 15% lift in mill throughput and US$58 million in added value over a single year by increasing the minus-half-inch fines fraction by up to 10%.

Beyond Morila: Why Every Mine Should Pay Attention

Mine-to-Mill is not a technique reserved for gold operations or billion-dollar brownfield optimisations. Any operation with a comminution circuit (which is most hard-rock mines) can benefit. The principles are the same whether you are processing copper, iron ore, or nickel laterite:

1. Characterise the geological domains and their breakage properties
2. Design blast patterns that produce fragmentation aligned to the downstream circuit
3. Monitor feed size in real time, not after the fact
4. Close the loop: adjust blasting based on mill performance data, not just pit conditions

The barrier is rarely technical. It is organisational. Mine-to-Mill requires the drill and blast team and the processing team to share data, agree on targets, and accept that one department’s costs may rise so the other’s can fall further. That is an IO problem, not an engineering one.

The Financial Case for IO

The specific numbers vary by commodity, scale, and maturity, but the target ranges cited across industry literature are remarkably consistent:

Metric	Target Improvement	How It Is Achieved
Overall productivity	5 to 10% increase	Real-time short-interval control, reduced idle time, centralised coordination
Total operating costs	10 to 15% reduction	Centralised workforce management, predictive maintenance, optimised logistics
Mill throughput	10 to 30% increase	Optimised blast fragmentation, proactive ore blending, stabilised feed rates
Grinding energy costs	10 to 20% reduction	Improved feed size distribution reducing specific energy in SAG and ball mills

These are conservative, broadly applicable targets for IO specifically. McKinsey’s February 2025 mining operational excellence report found that outperforming mines reduced unit costs at a compound annual rate of 3 to 6%, and one operation increased output 25% within a year with no additional capital, reaching 40% above its starting point after two years. Those larger gains reflect comprehensive operational excellence programs that include IO alongside other levers, but IO is typically the backbone.

The important distinction: these are whole-system gains. No single department captures them. If your reporting structure only measures departmental KPIs, IO gains will be invisible, or worse, will look like cost increases in the departments that spend more (like drill and blast) while the savings appear elsewhere (like processing). This is why IO requires integrated KPIs and collective accountability, not just integrated data.

The IOC: Central Nervous System of the Mine

The physical manifestation of Integrated Operations is the Integrated Operations Centre, or IOC. In remote operations, these become IROCs (Integrated Remote Operations Centres), typically located hundreds or thousands of kilometres from the mine itself.

An IOC is not a control room with more screens. It is the facility where cross-functional teams sit together, share real-time data from across the value chain, and make coordinated decisions. Geology, dispatch, processing, maintenance, and logistics operating from the same room, looking at the same dashboards, working the same shift plan.

The value of an IOC comes from the integration it enables, not the building it sits in. When a shift supervisor can walk into the control room, stand beside the controller, look at the same screen, and resolve an issue face-to-face in thirty seconds, that is integration working. When the drill and blast engineer and the plant metallurgist share a coffee break and notice something in each other’s data that neither would have caught alone. That is the kind of incidental collaboration that drives real operational improvement.

This is why experienced practitioners, including Ray Ballantyne in his AusIMM Bulletin series on mine control, argue strongly that the default location for an IOC should be on-site. Proximity to operations preserves the human interaction, the shared context, and the trust between field teams and control room staff that integrated decision-making depends on.

Remote Operations: A Deliberate Choice, Not the Default

Some operations have moved their IOCs off-site entirely, creating Integrated Remote Operations Centres located hundreds or thousands of kilometres from the mine. The Australian iron ore sector has been the global leader here, but understanding why these specific operations went remote is more instructive than the fact that they did.

BHP, Rio Tinto, and Fortescue each operate multiple Pilbara mines that feed shared rail corridors and shared port facilities. Their customers, predominantly Asian steel mills, place orders specifying tight tolerances on iron percentage, contaminant levels (phosphorus, silica, alumina), moisture content, and lump-to-fines ratios. Meeting those specifications requires blending ore from different mines in real time, coordinating train scheduling across over a thousand kilometres of rail, and managing port stockyard composition to hit the target blend for each individual shipload.

That is an integration problem that genuinely cannot be solved from any single mine site. No individual operation has visibility of what the other mines are producing, what is already on the rail network, or what blend the next vessel requires. The IROC is the only location where the full picture converges: production rates, grade profiles, rail logistics, and port blending all on the same screen, managed by the same team.

BHP has operated this way from Perth’s CBD since 2012. Rio Tinto runs its operations from Perth Airport, including the autonomous AutoHaul rail network. Fortescue’s Hive in East Perth manages 200 autonomous haul trucks and the full pit-to-port supply chain.

Roy Hill represents a different model. It is a single mine, a single rail line, and a single port, but it has still centralised the full value stream into a remote operations centre at Perth Airport. The integration problem is simpler (one connected operation rather than a multi-mine network), but the benefits of co-locating mine control, rail, port, and shipping functions in one facility still hold.

The business case changes significantly for geographically isolated mines with no shared logistics or product blending requirements. A company operating three separate gold or copper mines with independent logistics chains can still benefit from a centralised hub: standardised systems and processes, shared specialist resources, common analytics platforms, and consistent maintenance practices across sites. But that is standardisation and resource sharing, not operational integration. It is a valid justification, but a different one, and it does not carry the same weight as the multi-mine blending case.

The point is that remote should be a deliberate strategic decision driven by a specific integration need, not adopted simply because the bandwidth exists. Removing the control function from site introduces real costs: the loss of face-to-face interaction, degradation of controllers’ understanding of physical site conditions, and erosion of trust between remote staff and field teams. These are solvable problems, but they require structured mitigation and should not be underestimated. The question of where to locate an IROC, and the trade-offs involved, is explored in the third article of this series.

In 2017, the World Economic Forum estimated that digitalisation and integration across mining, minerals, and metals could deliver over US$425 billion in combined industry, customer, and environmental value over a decade, including US$190 billion in direct value for mining companies. Those gains come from integration itself, regardless of whether the IOC sits on-site or in a capital city.

The design, human factors, and staffing of IOCs, whether on-site or remote, is covered in the next article in this series.

One Truth, One System: The Newmont ONE Story

If the financial case for IO is about what you gain, the Newmont story is about what you have to tear down first.

Under the “One Newmont Enterprise” initiative, Newmont Australia set out to standardise Mine Control systems across its underground operations at Jundee, Pajingo, and Tanami. What they found was a case study in how silos grow unchecked.

Each site had built its own non-standard, localised control system. Terminology varied: one site called them “boggers,” another called them “loaders.” Some sites recorded truck loads from the original stope rather than the actual drawpoint, a simplification that made local grade control easier but severely distorted regional productivity data.

The maintenance codes were the most telling example. Across the three sites, operators used over 200 distinct breakdown categories. When the standardisation team analysed the data, they found that just 15 of those 200 categories accounted for 90% of all downtime. The system was rationalised to 22 major categories. Simpler for operators, cleaner for analysts, and infinitely more useful for cross-site comparison.

The team did not mandate these changes from head office. They presented the data, demonstrated the inefficiencies, and let the site teams see the problem for themselves. As Ray Ballantyne documented in his AusIMM publications on the project, the approach was deliberate: educate and influence rather than dictate. Build collective consensus. Let the people who own the process own the solution.

That philosophy, getting buy-in through evidence rather than authority, is the template for IO change management across the industry.

90% Behaviour, 10% Systems

There is an aphorism that circulates through IO implementation teams: it is “90% behaviour and 10% systems.” The exact ratio is debatable. The underlying truth is not.

The technology to run an IOC exists. The communications bandwidth is available. The data platforms, real-time dashboards, fleet management systems, and autonomous equipment are all mature enough. What determines whether an IO implementation succeeds or fails is almost entirely about people.

McKinsey’s February 2025 research reinforced this, finding that operational excellence cultures are built through management practices that reinforce daily behaviours, not through technology deployments. The technology enables. The culture delivers.

What the Cultural Shift Looks Like

KPI redesign. Departmental metrics that reward local optimisation at the expense of whole-system performance have to go. If the drill and blast team is penalised for higher powder factors when those higher powder factors are saving the mill three times the cost, the KPI is working against the operation.

Collective accountability. In an IO model, the shift team owns the shift result. Not the mine department, not the plant department, not logistics independently. This requires a fundamental rethink of how performance is measured, reported, and rewarded.

A single source of truth. When geology has one dataset, dispatch has another, and the plant runs off a third, every meeting starts with an argument about whose numbers are right. IO eliminates this by establishing one centralised, transparent data repository. The shift dynamic changes from reactive finger-pointing to proactive problem-solving when everyone is looking at the same screen.

Configuration control. Once systems are standardised, they need to stay that way. Without a dedicated system administrator, configuration “drift” sets in within months. Sites revert to old habits, add local workarounds, and the single source of truth fractures into multiple versions again.

Where It Goes Wrong

The most common failure mode is not technical. It is treating the IOC as a data collection centre rather than a decision-making hub. When controllers are relegated to clerical roles (logging truck movements, recording delays, filling in spreadsheets) the IOC becomes an expensive overhead with no operational leverage. The people in the room have screens but no authority. The site teams see the IOC as an inconvenience rather than a partner.

The fix is cultural, not technological. Controllers need to be treated as operational leaders, not clerks. They need authority to influence shift decisions, status equal to field supervisors, and a career pathway that makes the role attractive to high-calibre people. Without that, the best-designed IOC in the world will underperform.

Getting Started with IO

Not every operation needs a $50 million IROC in Perth. Integrated Operations is a spectrum, and the entry point is simpler than most people think.

Start with the data. Before integrating anything, establish a single source of truth. Get geology, dispatch, and processing reading from the same dataset. This alone eliminates a surprising number of cross-departmental arguments and misallocations.

Pick one integration to prove the concept. Mine-to-Mill is the classic starting point because the value is large and measurable. But even integrating shift handover data between the pit and the plant, so the processing team knows what is coming before it arrives, creates immediate value.

Redesign one KPI. Find a metric that currently rewards departmental behaviour at the expense of the whole. Replace it with a value-chain metric and measure the impact over a quarter. That single change will reveal more about your organisation’s readiness for IO than any technology assessment.

Walk before you run. Experienced IO practitioners consistently use the phrase “get the fundamentals right first.” Standardise your data. Clean your maintenance codes. Agree on terminology. These are not exciting projects, but they are the foundation everything else builds on.

Key Takeaways

• IO is a philosophy before it is an infrastructure. The technology exists. The challenge is breaking departmental silos and aligning the entire value chain toward shared outcomes.

• Mine-to-Mill is the highest-ROI entry point. Blast fragmentation improvements that cost an extra dollar in the pit routinely save seven to ten dollars in the mill. Any hard-rock operation with a comminution circuit should be looking at this.

• Conservative IO targets (5 to 10% productivity, 10 to 15% cost reduction) represent whole-system gains. They will not show up in departmental KPIs. Integrated measurement is a prerequisite, not an afterthought.

• Start with a single source of truth. Eliminate competing datasets before attempting integrated decision-making. If departments argue about whose numbers are correct, you are not ready for an IOC.

• The cultural shift is the hard part. Technology is 10% of the solution. KPI redesign, collective accountability, controller authority, and sustained change management account for the rest. Skip these and the IOC becomes an expensive clerical hub.