Smart Maintenance Task Manager

MINING

CMMS for Mining: Usage-Based Maintenance for Mobile Fleets and Fixed Plant

Smart Maintenance Task Manager gives mine maintenance teams per-unit control of a mobile fleet — every haul truck, excavator, loader, and drill is its own asset carrying its own hour, kilometre, and tonnage meters, with service intervals that fire when the counter says so, not when the calendar does. Usage-based maintenance is optional — your Admin switches it on.

CONTEXT

Why Maintenance Discipline Matters in Mining

Mining equipment does not wear by the calendar. A haul truck that ran 400 hours this month needs service sooner than one that ran 150, and a fleet-wide average hides exactly the unit that is about to fail. Smart Maintenance Task Manager models every machine as its own asset with its own meters, so service intervals follow actual use: once a unit has a few readings, planners see a projected next-due date computed from how fast it is really running, and a counter that has not been read for too long is flagged as stale before it can mislead a schedule. Counters are read on scheduled reading rounds — one job walks the technician through up to 60 counters in walking order, and the app asks for an answer for every counter before the round can be submitted: a value, a confirmation that the machine stood idle, or a reason it could not be read. Readings are recorded on the phone at the machine, with no signal, and sync when the crew is back in range.

Mining technician checking a phone beside a haul truck while an excavator loads another truck in an open-pit mine
CAPABILITIES

What Smart Maintenance Task Manager Does for Mining Operations

  • Per-unit asset register for haul trucks, excavators, loaders, drills, dozers, and graders
  • Service intervals by running hours, kilometres, or tonnage — with staggered rules per unit (usage-based maintenance is optional — your Admin switches it on)
  • Meter readings recorded in the field, offline — on a scheduled reading round, or added to any other task at the machine
  • Projected next-due date for each rule once a machine has a few readings, computed from its actual usage rate
  • A calendar backstop per rule — every 250 hours or at the latest after 90 days, whichever comes first
  • Scheduled reading rounds that walk a technician through up to 60 counters in order
  • Lock-out/tag-out reminder screen the technician must confirm before tasks on task points flagged as lock-out required

Every completed task records who did it, when, any readings taken, and photos where you require them, and the task history (without photos) exports to CSV per machine. On task points flagged as lock-out required, the technician must confirm a lock-out/tag-out reminder screen before the task opens; this confirmation is a prompt on the phone, not a stored record.

How it runs in your facility

In a Mining facility, Smart Maintenance Task Manager runs on two layers: a web dashboard for the maintenance manager and supervisors, and a mobile app on iOS/Android tablets and phones for the technicians on the floor.

NFC tags or QR labels on machines and task points let technicians open the right tasks with a tap or a scan — no typing, no searching. Technicians can work through their tasks, readings and photos even when the production area has no Wi-Fi, and the app syncs to the central dashboard the moment the device reconnects.

Setup typically takes about 2–3 weeks for a site with around 100 assets. Multi-site rollouts scale from the same configuration.

EXAMPLE SCENARIO

Servicing a Haul Truck Fleet by Running Hours Instead of the Calendar

Open-pit mine · 40 haul trucks · 12 excavators and loaders · 14 technicians · 2 shifts

Illustrative scenario, composed from common maintenance challenges. Company size, roles and figures are representative, not from an identified customer.

The Situation

An open-pit mine services its haul trucks, excavators and loaders by the calendar. Some trucks run twice the hours of others, so the calendar services the quiet units too early and the hardest-working ones too late. Hour-meter readings are written on paper at the pit, where there is no signal, and typed into a spreadsheet days later — if at all.

“Our 250-hour service was booked by date. One truck ran close to 400 hours in a month and went far past its interval before anyone compared the meter with the plan — the readings were on a clipboard in the workshop.”
— Maintenance Planner

Specific Problems

  • Services were booked by date, while the trucks wore at very different rates
  • Hour-meter readings lived on paper and reached the plan days late, or never
  • No signal in the pit, so nothing could be recorded at the machine
  • Nobody noticed when a machine’s meter had not been read for weeks

How It Would Work

Setup

  • Every haul truck, excavator and loader entered as its own asset with its own hour meter; the trucks also carry an odometer
  • Usage-based maintenance switched on by the Admin, and service rules tied to the meters — every 250 running hours, or at the latest after 90 days, whichever comes first
  • Scheduled reading rounds that list the counters in walking order — up to 60 on one round — assigned and tracked like any other task

Daily Workflow

1 The technician walks the reading round on the phone, counter by counter, with the last reading of each shown as a hint
2 Every counter gets an answer before the round can be submitted: a value, “unchanged” for an idle machine, or a reason it could not be read — with no signal, synced when the crew is back in range
3 Once a truck has a few readings, the planner sees its projected next-due date, computed from how fast it is really running; the service appears on the calendar when that date is within 30 days
4 The moment a reading reaches the interval, the service is due today, whatever the estimate said

Catching Gaps

  • A meter that goes longer than its stale-after tolerance (7 days unless you change it) without a reading is named in a digest to the people who plan and assign the work
  • Reading rounds that went by unanswered are listed once a day in a missed-readings digest
  • Every completed service records who did it, when and the readings taken, and the history (without photos) exports to CSV per machine

The Result

Service timing
Per machine
Follows each unit’s own hours
Meter readings
At the machine
Recorded offline, synced later
Unread meters
Flagged
Stale-meter digest to planners
Service history
Complete
Who, when and readings, per machine

Illustrative scenario based on common industry challenges.

FREQUENTLY ASKED

Mining Questions

Each unit is its own asset with its own meters and its own service rules. A fleet of forty haul trucks is forty assets, each with an hour meter and an odometer, and each with its own projected next-due date once it has a few readings. A fleet-wide average hides the unit that is about to fail; per-unit records show it.

Yes. A maintenance rule can be tied to a meter — "service every 250 running hours" — and the service gets a date projected from that machine's own usage once it has a few readings, appearing on the calendar when that date is within 30 days; the moment a reading reaches the interval it is due today, whatever the estimate said. Add a calendar backstop — "or at the latest after 90 days, whichever comes first" — so a machine that stands idle still gets serviced. Running hours, distance, cycles, and custom units are all supported, and calendar-based schedules remain available for anything that does wear by time. Usage-based maintenance is optional — your Admin switches it on.

Reading rounds work with no signal. The technician walks the round on the phone — each counter in turn, with the last reading shown as a hint — or adds a reading to any other job at that machine, and everything syncs when the device is back in range, like other tasks and photos.

Yes. A machine can carry a tonnage meter alongside its hour meter and odometer, and a service rule can be tied to any of them. Each meter drives its own rules, so a loader can be serviced by hours for the engine and by tonnage for the bucket and linkage. Service rules on meters need usage-based maintenance, which your Admin switches on.

Each meter has a stale-after tolerance (7 days unless you change it). When a meter goes longer than that without a reading, it is named in a digest to the people who plan and assign the work — with how often technicians could not read it, and why — and then at most weekly while it stays quiet, so a projection built on an old reading is caught before it misleads a schedule. Readings are collected by scheduled reading rounds: a task that lists up to 60 counters in walking order, assigned and tracked like any other task, and the app asks for an answer for every counter on it (a value, "unchanged" for an idle machine, or a reason it could not be read). Rounds that went by unanswered, or that closed without a reading, are listed once a day in a missed-readings digest. A reading recorded during any other job at that machine closes a single-counter reading task that was due for it, so nobody is sent to the same display twice. Both digests need usage-based maintenance switched on.

Your facility. Your workflows. Book a 30-minute demo.

We will show you how Smart Maintenance Task Manager fits the specific maintenance pattern of a Mining facility your size, with no commitment.

Book a Free Demo →