The maintenance record that lives in two places at once
A mid-tier operation buys a maintenance management platform, rolls it out with good intentions, and six months later discovers the maintenance foreman still keeps his real notes in a paper logbook "because the tablet is slow to use in the pit." The system looks fully adopted from the office. The actual data driving repair decisions never made it in. The platform did exactly what it was built to do; the rollout simply never solved for the person actually holding the spanner.
Mining operations and the suppliers pitching them are regularly sold individual products in isolation, a fleet platform here, a safety monitoring tool there, a new planning suite pitched at last year’s Mining Indaba. Evaluating each pitch on its own is exactly how an operation ends up with five overlapping tools, three of which cannot exchange data, and a maintenance team quietly running its real records somewhere else entirely.
This article does not rank or recommend specific products. It maps the categories that exist, what job each one actually does, and the practical questions that matter more than a feature list, so operators and marketers share an honest vocabulary before a demo happens, not during one.
The five categories, and how they usually fail
| Category | Core job | Typical failure mode |
|---|---|---|
| Fleet / dispatch | Optimise asset utilisation and haul cycle efficiency | Rich data exists; nobody changes a dispatch decision because of it |
| Maintenance management | Improve uptime and reduce unplanned downtime | Real records kept in a parallel paper system nobody retires |
| Safety / fatigue monitoring | Reduce risk from fatigue, PPE gaps and hazardous behaviour | Alerts fire into an inbox nobody is assigned to check |
| Planning / geology | Align the mine plan with actual extraction and grade control | The plan-versus-actual gap surfaces too late to correct |
| Reporting / data integration | Turn operational data into decisions across departments | A polished dashboard; decisions still made from memory |
Fleet and dispatch: mature technology, immature rollouts
Fleet and dispatch software routes trucks, loaders and other mobile equipment to maximise utilisation and cut idle time. It is one of the most mature categories in mining technology, with established vendors and provable returns under the right conditions.
The usual failure is not a bad vendor choice, it is rich utilisation data that never changes a dispatcher’s actual call, because the workflow around the tool was never redesigned to use it. See our dedicated fleet management technology guide for a deeper look at evaluating ruggedness, offline behaviour and integration in this specific category.
Maintenance management lives or dies on what actually gets logged
Maintenance systems track asset history, schedule preventive work, and increasingly pull in predictive signals from condition monitoring, the promise is fewer unplanned failures and better parts planning. The risk sits entirely in data discipline: a system is only as good as what gets logged against it consistently, shift after shift, by people under time pressure.
Operations that let a parallel paper or spreadsheet record persist "because the app is slow in the field" have quietly undermined the whole investment. The dashboard looks complete. The data feeding it is not.
A scenario: the safety alert nobody was assigned to read
An operation installs a fatigue-monitoring system across its haul fleet, and it works exactly as specified, flagging genuine fatigue events in near real time. Six months in, an audit finds the alerts were routing to a shared email inbox that three different people believed was someone else’s responsibility to monitor. Every alert had technically been delivered. Not one had reliably been acted on.
The system passed every technical acceptance test at procurement. It failed the only test that actually mattered operationally, because nobody had assigned clear, individual ownership of the response before go-live. This is a change management gap, not a software gap, and it is depressingly common across all five categories described here, the newest, most capable tool in the world still needs a named person accountable for what it flags.
Evaluation questions worth more than any feature list
- How does this behave with intermittent or no connectivity on site?
- What does integration with our existing fleet, ERP or safety systems actually require?
- Who owns the data if we switch vendors, is it portable?
- What does onboarding and change management support actually include, beyond initial training?
- What is the realistic support response time for a system that fails on night shift?
Safety, fatigue and planning: only as good as the response behind them
Camera-based fatigue detection, PPE compliance monitoring and proximity detection have genuinely improved risk visibility across the sector. Their value depends entirely on whether the operation has a defined process for what happens when the system flags an event, a fatigue alert routed to an unmonitored inbox achieves nothing beyond a compliance checkbox.
Planning and geology software addresses the gap between the mine plan and actual grade control before it becomes an expensive surprise. Integration with fleet and maintenance data (so planning reflects real equipment availability rather than theoretical capacity) usually matters more than the modelling sophistication of any single tool.
A frequently underestimated cost in both categories is training effort at site level, particularly where staff turnover is high or several languages are spoken on the floor. Software procured centrally but never properly embedded at site level tends to produce compliance-only usage rather than a real change in behaviour.
A realistic evaluation sequence
- Map your current tools by categoryInclude spreadsheets and manual processes, not just licensed software.
- Find the real integration gapsWhere does data get re-entered by hand, or not connect at all, between systems that should talk?
- Name the decision, not the featureFor any new tool, state the specific decision it should change and who makes it.
- Stress-test offline behaviourMost SA sites have connectivity constraints, test this before evaluating dashboards.
- Plan change management before rolloutAdoption fails on workflow resistance more often than on software capability.
The hard part of mining software is never the demo. It is integration, offline reality, and whether the people on site actually change what they do because of it.
Nexus industrial technology principle
Point solution vs integrated platform, the trade-off operators actually face
| Approach | Advantage | Cost |
|---|---|---|
| Best-of-breed point solutions per category | Often the strongest individual tool in each category; easier to swap one out later | Integration between systems becomes your problem to solve and maintain, not the vendor’s |
| Single integrated platform across categories | Data flows between fleet, maintenance and safety without custom integration work | Individual modules are sometimes weaker than a dedicated specialist tool in that one category |
| Phased integration of existing point tools | Avoids a disruptive rip-and-replace of systems already working reasonably well | Slower to realise full cross-category value; requires sustained integration effort over time |
Reporting: the category that exposes every gap underneath it
Reporting and data integration tools sit slightly apart because their value depends entirely on the quality of the systems feeding them. A dashboard built on top of disconnected fleet, maintenance and safety data can only ever show a partial, polished-looking picture.
Strengthen data quality and integration in the underlying systems first. Investing in reporting before that work is done tends to produce an expensive visualisation layer that restates known problems without helping solve any of them.
What suppliers should actually put on their websites
Vendors selling into mining should name which of the five jobs their product does, how it integrates with adjacent categories, and how it behaves offline (directly, on the capability page) instead of leading with generic "smart mining" claims that give an operator nothing to evaluate against.
This kind of operational literacy builds more credibility with a technical buyer than a glossy feature page, and it shortens the evaluation cycle by answering questions procurement and operations were going to ask anyway.
Vendor lock-in is a real cost, even when the software works well
A system that has run for several years accumulates institutional value in its data, historical patterns, tuned configurations, staff who have learned its quirks. That accumulated value is exactly what makes switching expensive, even when a better or cheaper alternative genuinely exists on the market. Vendors know this, and pricing on a long-standing contract sometimes drifts upward over time in ways that would never survive a fresh competitive tender.
Negotiate data portability and export rights into the contract at the start, while you still have real negotiating power as a prospective customer, rather than discovering the terms years later when you actually want to leave. This is a procurement discipline question as much as a technology one, and it belongs in the same conversation as price and feature comparison from day one.
Budget for the whole system, not the licence line item
A common mistake across all five categories: pricing only the software licence and treating implementation, integration, training and change management as a rounding error. In practice these supporting costs frequently exceed the licence cost in the first year or two, particularly for maintenance and safety categories where site-level adoption is the harder problem to solve.
Build the business case around the total cost of a properly adopted system (including the internal time your own team spends on data cleanup and training) not just the number on the vendor’s quote.
What to do next
Use the category map and evaluation checklist above before your next vendor demo, it works just as well for building an internal business case.
Read our fleet management technology guide for a deeper look at that specific category, and our mining suppliers lead generation guide if you are marketing into this sector.
Talk to Nexus if you want help clarifying how your mining technology capability is communicated online.
