Epiroc Certiq is being retired, and if you run drill rigs or loaders, your telematics just moved to Fleet+ on MyEpiroc. That's the moment to ask a bigger question than "where's my dashboard now?" — what actually happens to all that machine data once it lands. Certiq, and now Fleet+, tell you what the equipment is doing: hours, fault codes, service due. But a flagged fault isn't a work order on a tech's phone or a service recorded against that serial. The value is the bridge. Book a demo to see that bridge wired up.
Turn Epiroc Machine Data Into a Maintenance Plan
The OEM platform reports what the rig is doing. A CMMS decides what to do about it. Here's what that handoff looks like when it's wired together.
Fleet+ is a strong monitoring layer — it tells you, in near real time, what your Epiroc fleet is doing. What it doesn't do is close the loop. Below is exactly where that gap sits, what Epiroc machine data looks like once it becomes a maintenance plan, and the four-stage path a single flagged fault travels from signal to signed-off repair.
3things Fleet+ tells you — none of them is a completed repair
Think about what you actually get off an Epiroc rig today. Three streams of truth, all accurate, all live. And a gap at the end of each one where the work is supposed to happen. That gap is where downtime hides.
Fleet+ says: this rig has run 8,460 hours.
Gap It won't open the 8,500-hour service, reserve the filter, or tell a tech. Someone has to watch the number.
Fleet+ says: fault code active on the hydraulics.
Gap It won't become a prioritized work order, pull the part, or capture the fix against the serial. The code sits in a feed.
Fleet+ says: where the machine is and whether it's running.
Gap It won't tie that status to parts on hand, labor hours, or cost per operating hour. Visibility isn't a maintenance record.
None of this is a knock on Fleet+ — monitoring is doing its job. The point is that monitoring ends where maintenance begins. A CMMS like HVI picks up at exactly those three gaps and turns each signal into a scheduled, assigned, recorded action. Book a demo to see each gap closed on your own rigs
The handoffevery Epiroc signal, mapped to the maintenance action it should trigger
This is the whole idea on one screen. Left column is what Fleet+ sends. Right column is what HVI does with it the moment it arrives — automatically, against the right machine, with the work recorded.
Exact Fleet+ data fields and export options are still settling as Epiroc completes the Certiq migration — confirm what's available for your account with your Epiroc representative. Whatever the OEM exposes, OEM telematics integration is where HVI picks it up and turns it into recorded maintenance. Start free and map your first signal
4stages a flagged fault travels — from Epiroc signal to signed-off repair
Here's one hydraulic fault code, start to finish, once Epiroc data and HVI are connected. Each stage is automatic or one tap — no one re-keying a code from a dashboard into a maintenance system by hand.
-
1Fleet+ flags the fault0 min
Epiroc telematics logs an active hydraulic fault code on the rig and streams it with the machine's hours and location.
-
2HVI opens the work orderautomatic
The signal maps to a prioritized work order against that exact serial, with the fault, the hours and prior history attached.
-
3Tech sees it on mobileon shift
The assigned tech gets it on the phone underground, pulls the reserved part from inventory, and does the repair.
-
4Fix logged to the serialclosed
Parts, labor and time are recorded against the machine. Cost-per-operating-hour updates, and a repeating code is now visible as a trend.
Without the bridge, that same fault is a line in a feed someone may or may not check, re-typed into a spreadsheet if you're lucky, and never tied back to the machine's cost history. With it, the fault manages itself. Book a demo to watch a fault flow end to end
What you run it forthe maintenance jobs Epiroc data drives once it's in a CMMS
Monitoring tells you. A connected CMMS does. These are the day-to-day jobs that Epiroc machine data starts driving the moment it stops living only in the OEM dashboard.
Meter-based PM
Operating hours trigger service schedules automatically — no manual hour-reading, no overdue intervals slipping past.
Fault-to-work-order
A fault code becomes an assigned, prioritized job on a tech's phone — not a notification nobody owns.
Parts & inventory
The right part is reserved against the right machine before the tech arrives, and stock draws down as jobs close.
Cost per hour
Every logged repair feeds true cost-per-operating-hour by machine — the number that tells you when to rebuild or retire.
Chronic-fault tracking
Repeating codes on the same serial surface as a trend, so you fix the root cause instead of the symptom twice.
Audit-ready history
A complete, timestamped maintenance record per machine — ready for safety audits, warranty claims and resale.
Every one of these runs off data your Epiroc fleet is already producing — the difference is whether it sits in a dashboard or drives the work. Book a demo to see these jobs running on your machines
Before you migratethe Certiq-to-Fleet+ checklist that keeps your maintenance intact
A platform migration is the moment maintenance history quietly gets lost — subscriptions move, logins change, and the record of what you did to each machine falls through the cracks. Run this list before and during your Certiq-to-Fleet+ switch so nothing resets to zero.
Do this once and the next OEM platform change — whatever it's called — becomes a non-event for your maintenance team. Start free and get your Epiroc fleet's records in one place
From a maintenance manager who made the switch
Certiq told us the hours and the faults. It was good at that. But the fault would ping, and then it lived in someone's head until a machine stopped. We were re-typing codes into a spreadsheet every morning.
Once we ran Epiroc data into HVI, the fault opens the work order itself and the part's already reserved. The thing I didn't expect was cost-per-hour by machine — we found two rigs that were quietly costing us double, and we'd never have seen it in the OEM dashboard alone.
Frequently asked questions
Is Epiroc Certiq being discontinued?
Yes. Epiroc has retired Certiq and transitioned to Fleet+ as its fleet-monitoring solution, accessed through MyEpiroc. Existing Certiq subscribers are directed to contact their nearest Epiroc customer center to migrate. Fleet+ is positioned as the successor with an improved interface and expanded insights. Because the migration is still rolling out, exact data fields, access levels and export options can vary by account and region — confirm the specifics for your fleet with your Epiroc representative. What doesn't change is the underlying need: whatever the OEM platform is called, the machine data it produces (operating hours, fault codes, service information) only reduces downtime once it drives scheduled, recorded maintenance in a system built for that. That's the role a CMMS plays alongside Fleet+.
What's the difference between Epiroc Fleet+ and a CMMS like HVI?
They solve two different halves of the same problem. Fleet+ is a monitoring and telematics layer — it gathers and communicates what your Epiroc equipment is doing in near real time: hours, faults, location, status. A CMMS (Computerized Maintenance Management System) like HVI is the action layer — it takes those signals and runs the maintenance: opening meter-based preventive-maintenance schedules from operating hours, turning fault codes into assigned work orders, reserving the right parts, and logging every repair against the machine so you build a true cost and service history. Monitoring tells you a service is due or a fault is active; the CMMS makes sure the work actually gets scheduled, assigned, done and recorded. Used together, Fleet+ is the eyes and HVI is the hands — the OEM platform sees the condition, and the CMMS closes the loop on it.
Can HVI use data from Epiroc telematics?
Yes — HVI is built to sit on top of OEM telematics rather than replace it. Through OEM and GPS/telematics integration, operating hours can drive preventive-maintenance scheduling automatically, and fault signals can trigger work orders without anyone manually re-keying a code from the OEM dashboard into the maintenance system. Because Epiroc's Fleet+ platform is still completing its transition from Certiq, the exact integration method and available fields should be confirmed with both your Epiroc representative and the HVI team for your specific account. The important principle holds regardless of the connection detail: the goal is that a milestone or fault in the OEM platform becomes a scheduled, assigned, recorded maintenance action — so the data stops being a dashboard you watch and starts being work that happens on its own.
Why not just use the OEM dashboard for maintenance?
Because a monitoring dashboard and a maintenance system are different tools with different jobs. The OEM dashboard is excellent at showing condition — it will tell you a rig has hit 8,500 hours or thrown a fault. What it generally won't do is open the service, reserve the filter, route the job to a specific tech, draw down inventory, and log the completed repair against the serial so your cost-per-hour updates. It also only covers one brand's equipment; most real fleets are mixed, and you don't want maintenance history split across three or four OEM portals plus a spreadsheet. A CMMS consolidates all of that into one maintenance record per machine, across every brand, and turns the OEM's signals into completed, documented work. The dashboard is where you look; the CMMS is where the work lives and stays, even when the OEM platform changes names.
What happens to my maintenance history when Certiq is retired?
This is exactly why it pays to keep your maintenance records in a CMMS rather than inside the OEM platform. Telematics history and settings tied to Certiq move with Epiroc's migration to Fleet+, and you should confirm with your Epiroc representative what carries over for your account. But your maintenance history — the work orders, parts used, labor, costs and service records per machine — belongs in your maintenance system, not the monitoring layer. When that history lives in HVI, an OEM platform change doesn't touch it: your preventive-maintenance schedules, repair logs and cost-per-hour figures stay put, and you simply re-point the telematics feed from Certiq to Fleet+. The lesson most fleets take from a migration like this one is to keep the record of what you did to each machine independent of whichever dashboard is showing you what the machine is doing.
Turn your Epiroc machine data into maintenance that runs itself
HVI connects to your telematics, drives preventive maintenance from operating hours, turns fault codes into assigned work orders, and keeps one complete service and cost record per machine — across every brand you run, not just Epiroc.
