Mining · Production & Throughput Report

Ore Production & Throughput Reporting: From the Bench to the Mill

1 June 202611 min readPerth, Western Australia

Short answer

Ore production and throughput reporting tracks total material moved, ore tonnes, strip ratio, feed grade at the mill, and contained metal recovered - reconciled against plan at every stage from the mining bench to the concentrate. Done well, it gives operations, planning and finance one reconciled production number rather than competing figures from dispatch, grade control and the processing plant. SolveBI builds production dashboards on Microsoft Power BI and Fabric that unify dispatch systems, ROM surveys, assay data and process historians into a single, trusted daily production picture.

An open-cut mine pit showing excavator loading a haul truck with ore - the primary source of production volume data that feeds daily throughput and tonnes-moved reporting.

Why production and throughput is the number every other decision is measured against

Revenue, royalties, stripping schedules, processing plant budgets and mine-life calculations all trace back to one question: how many tonnes of ore actually came out of the ground, at what grade, and how much metal did the mill recover? In many operations these three figures live in three separate systems - the fleet dispatch system, the grade control database, and the process historian - and are reconciled once a month, weeks after the fact. By the time the shortfall appears in a report, the opportunity to recover production in that period has already passed.

Best-practice production reporting closes this loop. It reconciles dispatch tonnes, ROM pad surveys, mill feed tonnes and metallurgical recovery into one authoritative daily figure - broken down to mining area, bench and ore domain - so production engineers, grade control geologists and plant metallurgists are all working from the same number and can trace any variance back to its source the day it appears.

3–7%
Typical production recovered from faster detection of dispatch-to-mill reconciliation gaps
Same day
Target for ore-vs-waste reconciliation when dispatch, ROM survey and assay data are unified
1 figure
Ore production should mean the same thing to mine planning, operations and finance

The metrics that belong on a production and throughput dashboard

  • Total material moved (BCM and tonnes) - ore and waste separately, by fleet, area and shift
  • Strip ratio - waste BCM per ore tonne, trended against plan; the leading indicator of future mining cost
  • ROM delivery (tonnes and grade) - what was dispatched to the pad vs what the plant weighed in
  • Mill feed grade and throughput - hourly and daily, against plan, with feed source breakdown
  • Metallurgical recovery (%) - actual recovery against the geometallurgical model prediction
  • Contained metal produced - the bottom-line output that feeds revenue and royalty calculations
  • Variance to mine plan - which areas are ahead, behind, and why - attributed to grade, selectivity or mining rate

Open cut versus underground: different reporting priorities

Open-cut and underground operations share the same ultimate question - tonnes, grade and contained metal against plan - but the reporting structure differs significantly. Open-cut reporting centres on fleet productivity: BCM per operating hour, truck cycle time, shovel payload, and the strip ratio trend that drives future mining cost. Underground reporting centres on development metres and stope performance: development advance against schedule, void reconciliation, stope grade and dilution, and the drawpoint management that determines what grade the plant actually receives.

For operations running both open cut and underground simultaneously - a transition common in Australian gold and nickel operations - the dashboard must consolidate production from both mining methods into a single contained-metal figure without obscuring the different drivers behind each.

From mine block model to metal in concentrate: the reconciliation chain

A Power BI dashboard showing the mining reconciliation chain from geological block model through dispatch, ROM pad, mill feed and concentrate - with variance factors at each stage.
Ore production reporting connects four reconciliation points: geological model, dispatch, ROM pad and mill gate. Each gap has a different root cause - and a different team responsible for it.

Best-practice mine reconciliation tracks the movement of tonnes, grade and metal through four distinct stages: the geological block model prediction, what was dispatched from the pit (dispatch), what arrived at the ROM pad (survey), and what the mill weighed in at the gate. The ratio of each consecutive pair - the F-factor, GF-factor and metal factor - tells management precisely where the production prediction is breaking down. A low F-factor means either the dispatch record is wrong or tonnes are being lost in handling. A high GF-factor means the ore is above the model grade prediction - or below. Each is a different conversation, and the dashboard makes clear which one the team is having.

Forecast versus actual - attributing the variance

Spreadsheet production reporting vs unified production dashboard

AspectSpreadsheet reportingUnified production dashboard
Time to daily production figureHours of manual assembly each morningAutomated - reconciled by start of day shift
Dispatch-to-mill reconciliationMonthly, often weeks after the factDaily, with gap attributed to source
Variance attributionReconstructed retrospectivelyAttributed to grade, selectivity or mining rate at source
One figure for all stakeholdersOperations, planning and finance reconcile separatelyOne reconciled number shared across all teams
Drill-down to mining blockNot possible without raw data accessAny variance drills to the individual block or face

The Power BI and Fabric architecture behind production reporting

On a typical SolveBI deployment we land fleet dispatch data (Modular DISPATCH, Wenco, Minestar), ROM pad surveys, drill-and-blast records, grade control assay results, and process historian feeds into Microsoft Fabric, then expose a single production model through Power BI. Mine operations see the shift and daily production view; planning and grade control see the reconciliation and forecast-variance view; finance see the contained metal and royalty-calculation view - all from one dataset with consistent logic across mining areas and domains.

Common mistakes in ore production and throughput reporting

  1. Reporting tonnes without grade. A high ore-tonne week at below-plan grade is a shortfall in metal - not a good week.
  2. No dispatch-to-mill reconciliation. The gap between dispatch and weightometer disappears into a monthly variance and is never investigated.
  3. Strip ratio reported in arrears. By the time a deteriorating strip ratio appears in a monthly report, the mining sequence that caused it has already moved on.
  4. Blending invisible to the dashboard. Ore from multiple sources feeding the mill simultaneously makes grade variance unexplainable without a feed-source view.
  5. One figure for underground and open cut. Consolidating both methods without a method-level breakdown hides the drivers unique to each.

From a morning spreadsheet scramble to a reconciled ore production figure before first shift.

Book a free 30-minute consultation with a SolveBI consultant. We'll map your dispatch, grade control and plant data, agree the right reconciliation structure, and quote a phased Power BI deployment you can budget against.

Frequently Asked

Common Questions

Can it integrate with Modular DISPATCH, Wenco, and Minestar?
Yes. We connect to fleet dispatch systems via their reporting APIs or database exports and load the data into Microsoft Fabric on a scheduled or near-real-time basis. The dispatch record becomes one input to the reconciled production figure alongside ROM surveys, assay data and process historian feeds.
How do you handle the gap between dispatch tonnes and ROM pad survey tonnes?
The dispatch-to-ROM gap is calculated explicitly as part of the reconciliation chain - not hidden in a catch-all variance. We build logic that classifies the gap between what the dispatch system records and what the ROM survey confirms, so the team can see whether the difference is in the dispatch record, the survey method, or genuinely missing material.
Can the dashboard break down production by mining block, bench and domain?
Yes. Where grade control data is available at block level - and on most modern operations it is - we link dispatch records to the source block and domain so any production or grade variance can be drilled through to the specific area or geological domain driving it.
How do you handle multiple ore sources blending at the mill?
We build a feed-source model that tracks the contribution of each ROM pad or stockpile to the mill feed blend on each shift. This makes it possible to explain why the mill feed grade differs from any individual ore source - and to optimise the blend to target grade rather than discovering the variance after the fact.
How long does a first production dashboard take to deploy?
Typically four to eight weeks for a first useful version, depending on the number of source systems and the complexity of the reconciliation model. We prioritise getting a working daily production figure visible quickly, then add reconciliation depth and forecast comparison in subsequent iterations.