Short Interval Control and Production Reporting Software Guide
6 sections · 9 min readWhat to check in mine operations and short interval control software, from shift plans and delay codes to production records that hold up at month end.
Definition
Short interval control (SIC) software breaks a mining shift into shorter intervals, sends each crew its tasks, records progress and delays as they happen, and lets supervisors move people and equipment when the plan slips. The same shift records usually become the mine's production reporting, so how they are captured, approved and corrected decides whether the monthly tonnes can be trusted.
What is Mine Operations & SIC Software?
Mine Operations and Short Interval Control (SIC) software connects the weekly mine plan to what is happening on the current shift. If the Fleet Management System (FMS) manages where the trucks go, SIC manages whether the shift is on track to meet its targets.
SIC software replaces the shift boss's whiteboard. It lets supervisors break a 12-hour shift into shorter intervals (for example, 2 to 4 hours), assign tasks to crews, follow progress in near real time and move people and equipment as soon as a delay occurs. Because it records what each crew did, it also becomes the starting point for the mine's production reporting.

Signs Your Operation Needs It
If your shift supervisors only find out about a missed production target at the end-of-shift handover, the operation is reacting rather than controlling:
Symptom
The weekly mine plan is consistently missed, but no one knows exactly why until the end of the week when the reconciliation report is run.
Reality
You lack visibility within the shift. Variances build up over the shift without anyone dealing with them.
Symptom
Shift supervisors spend the first two hours of their shift driving around to figure out the status of working places and equipment.
Reality
Your shift handover is manual and paper-based, with no single digital record of where each heading and machine stands.
Symptom
When a critical piece of equipment breaks down, it takes hours to reassign the affected crew to a backup task.
Reality
You cannot update the shift plan or tell operators about changes mid-shift.
Symptom
The tonnes in the shift reports, the truck counts and the plant feed never agree, and month end is spent explaining the gap.
Reality
Production is recorded in more than one place, edited without a trail, or counted before it has reached the status your reporting rules say it should.
Understanding the Software Landscape
SIC software ranges from digital shift logs to integrated operations hubs:
Underground SIC Platforms
Tools built around the sequential cycle of underground mining (drill, blast, muck, bolt), such as CiteOps (Commit Works), Deswik.OPS (Deswik) and GroundHog FMS Underground (GroundHog). These systems track the status of headings and the dependencies between tasks.
Open Pit Shift Management
Often integrated with the FMS or running alongside it, these tools focus on operator line-out, equipment pre-starts, and monitoring shift progress against the daily plan.
Digital Shift Logs & Handovers
Point solutions that replace paper plods and shift-boss notebooks, so that safety and operational data pass cleanly from one crew to the next.
Unified Operations Centres
Enterprise platforms that take in data from the FMS, SCADA and planning tools and show it in one place for a remote operations centre (ROC).
How to Evaluate Mine Operations & SIC Software
When evaluating SIC software, look for systems that help supervisors make fast decisions rather than adding another data-entry chore.
Critical Evaluation Dimensions
- Integration with Planning: The software must take in the short-term mine plan from your scheduling tool without manual rework. If engineers have to type the plan into the SIC tool by hand, it will not last.
- Ease of Use at the Face: The screens used by operators and supervisors underground or in the pit have to be simple. If it takes a stylus and five taps to update a task status on a rugged tablet, operators won't use it.
- Dynamic Rescheduling: When a delay is logged (for example, a jumbo breaks down), does the system help the supervisor find a suitable next task for that operator based on skills and heading availability?
- Production Records You Can Defend: Every tonne the system reports should trace back to one shift record, with a status and an edit history. See the next part of this section.
How do you make production numbers trustworthy from shift log to month end?
Record each movement of material once, at the source, with who logged it, when, where it came from and where it went. Build the monthly figure from those records instead of re-keying shift totals into a spreadsheet, and keep every correction as a new entry with a reason rather than overwriting the original. Only count material as production once it reaches the status your reporting rules define, and give every tonne one source and one reporting area, so it cannot sit in two totals.
A current case shows why it matters. In October 2026, Chile's state miner Codelco said it was investigating new evidence of over-reported copper production in 2024 and 2025 at its Ministro Hales and Salvador divisions. In Codelco's words, "the same material was recorded as production by more than one division." An earlier audit of its 2025 reporting had found that materials still needing further processing were reported as finished product. Codelco has brought in EY for an external audit (Reuters via Mining Weekly, 7 October 2026). The reports do not say which systems were involved. Both problems, double counting and counting material too early, are the kind a production reporting system can be set up to catch.
As of 12 October 2026, the MSR directory lists 14 mine operations and short interval control products from 11 vendors. In their profiles, 11 of the 14 mention shifts, 2 mention reconciliation (AVEVA Production Management and MineRP Platform) and none mention an audit trail. Profile wording is a starting point for a shortlist, not proof of capability, so put the checks below to every vendor.
What Production Reporting Should Record
- One record per movement: Source (heading, stope or bench), destination, material type, quantity, time, equipment and operator. Each record belongs to one area and one reporting entity. If two areas or two sites can both claim a load, the system should refuse the second claim, not just warn.
- Material status: Broken, hauled, stockpiled, processed and shipped are different states. Each record should carry its status, and the production report should state which statuses it counts. Material that still needs processing stays out of the finished-product figure.
- An audit trail on every change: Who changed a record, when, the old and new values and the reason. Corrections add a new entry and keep the original visible.
- Who can edit what: Operators log, supervisors approve the shift, and later changes need a named role and a reason. A closed month should only reopen with sign-off, and the reopening itself should be logged.
- Reconciliation you can see: Shift tonnes against truck counts or payload data, survey and plant feed, with the variance shown and a tolerance your team sets. A gap should be flagged in the week it appears, not discovered at month end.
- Raw records you can export: Auditors and your own analysts will want the underlying records as well as the dashboard. Check that a full export comes with the licence.
Key Performance Metrics to Track:
The right software in this category should measurably improve:
Increase in plan compliance (percentage of planned tasks actually completed).
Reduction in delay times and unscheduled downtime.
Decrease in time spent on shift handovers.
Smaller, earlier-explained gaps between shift, survey and plant figures.
Defining the ROI
The ROI of Short Interval Control comes from turning "lost time" into productive time. It typically comes from:
Reclaiming Shift-Change Losses
A digital line-out and a live view of the mine can get crews to the face sooner after shift change. Measure your own shift-change time before go-live so you can see what you get back.
Immediate Delay Mitigation
Fixing a problem in hour two of a shift stops it from costing the whole 12-hour target. Faster intervention adds directly to shift output.
Accurate Delay Accounting
By capturing exactly why a task was delayed (for example, waiting on ventilation or missing parts) as it happens, management can find recurring bottlenecks and spend capital on root causes rather than symptoms.
What can a control room rollout deliver?
Most published figures for this kind of project come from vendors, so read them as claims. One recent example is a vendor-supplied article from Micromine about two Pitram projects (Mining Weekly, 8 October 2026):
- At the Çayeli Bakır copper and zinc mine in Türkiye, Micromine says Pitram and a dedicated mine control room gave real-time visibility of people, equipment and production. It reports an average productivity increase of 18 per cent, including 39 per cent in development, 29 per cent in shotcrete and 26 per cent in rock bolting.
- At Rana Gruber's iron ore operation in Norway, the same article says the project replaced fragmented reporting with one source of operational data. A Rana Gruber mining engineer is quoted saying the team spent less time "chasing spreadsheets and checking numbers".
These are vendor-reported results, not independent measurements. Before you use a figure like this in a business case, ask the vendor for the baseline period, how productivity was defined, what else changed on site at the same time, and whether you can speak to the site. In the MSR directory, Pitram is listed under fleet management and dispatch.
The Rana Gruber example also points to a gain that is easy to miss: when supervisors and engineers stop reconciling spreadsheets by hand, that time goes back into running the mine, and the numbers are easier to defend when someone asks where they came from.
Key Questions to Ask Vendors
Show me exactly what an operator has to do on a tablet to log a 15-minute delay due to lack of water.
Tests the UX and likelihood of field adoption. Underground operators work in harsh conditions with gloves and poor lighting, so the interface must allow delay logging in under 30 seconds with large touch targets, pre-populated reason codes, and minimal typing.
How does your system handle the update loop back to the mine planning software so the engineers know the current face positions?
Tests their integration depth with tools like Deswik. A mature SIC system should push actual progress data (metres advanced, tonnes mucked) back to the short-term planning tool, so planned and actual figures can be compared without engineers re-keying data.
Does your system work completely offline, and how does it handle data conflict resolution when two tablets sync at the same time?
Tests their architecture for underground and remote environments. Underground mines often lack continuous network coverage, so the system should keep working offline and resolve sync conflicts by a fixed rule, without losing either record.
Can the system automatically trigger an alert to the maintenance team if an operator logs an equipment defect during their digital pre-start?
Tests workflow automation. A well-integrated SIC platform should route defect reports from the pre-start to the maintenance planner, with the equipment number and a priority, instead of leaving them in a shift note.
What stops the same tonnes being reported twice, by two areas, two shifts or two sites?
Tests the production record itself. Ask the vendor to show how one load is tied to one source location, one destination and one reporting area, and what happens when someone tries to enter or import that load again. A warning that can be clicked past is weaker than a record that cannot exist twice.
Show me the audit trail for a shift record that was corrected after the shift closed.
Tests whether corrections are traceable. You should see who made the change, when, the old and new values, and the reason, with the original entry kept. Ask who is allowed to edit a closed shift, and whether a closed month can be reopened and by whom.
At what point does your system count material as production, and can we set that rule ourselves?
Tests material status. Broken, hauled, stockpiled, processed and shipped material are different things. Ask whether each record carries a status, whether reports can filter on it, and whether material that still needs processing can be kept out of the finished-product figure.
Ready to compare?
See how 14 mine operations / short interval control products stack up side by side.
Compare 14 ProductsUpdated · Mining Software
Explore Other Categories
Mine Planning & Design
Compare alternatives
Geology & Resource Modelling
Compare alternatives
Simulation & Digital Twins
Compare alternatives
Drill & Blast
Compare alternatives
Fleet Management & Dispatch
Compare alternatives
Database Management
Compare alternatives
Data & Analytics
Compare alternatives
Exploration & Drilling
Compare alternatives
Environmental, ESG & Compliance
Compare alternatives
Workforce / Roster
Compare alternatives