Sandvik Equipment Data: Underground Maintenance Guide

By Riley Quinn on October 13, 2026

sandvik-equipment-data-for-underground-maintenance

Sandvik equipment data can help underground maintenance teams connect operating hours, machine events and utilization trends with service decisions. But a dashboard reading alone does not tell a technician what to repair. The useful step is turning verified OEM information into inspections, preventive maintenance plans and documented work orders.

UNDERGROUND MINING · MAINTENANCE PLANNING

Turn Sandvik equipment data into maintenance decisions.

Make better use of machine hours, event histories and equipment condition signals—without losing the repair context behind each underground asset.

OEM DATA → MAINTENANCE REVIEW → DOCUMENTED ACTION
UNDERGROUND EQUIPMENT · EXAMPLEIllustrative
OPERATING HOURS5,280 hEVENTS TO REVIEW2 flagged
Operating hoursEvent contextMaintenance history
THE PRACTICAL QUESTION

Which machine signals should change the maintenance plan?

OEM portals can surface valuable operating information, but available fields depend on the equipment model, installed hardware, connectivity, subscriptions and user permissions. A maintenance manager needs to distinguish an interesting reading from a signal that warrants inspection.

Start with the asset's operating context, then check whether the information is reliable enough to support a maintenance decision. If a loader shows recurring hydraulic events, for example, verify the event description and operating conditions before creating a diagnostic task. Book a demo to discuss how HVI can document the resulting maintenance work.

EQUIPMENT VIEW

Different machines, different maintenance signals

Build equipment-specific review routines instead of treating every underground machine as an identical telemetry source.

⛏

Underground drills

Review operating hours, drilling activity, repeated event codes and service instructions relevant to the installed system.

Focus: wear and system checks
▰

Loaders (LHD)

Compare duty cycle, hours and hydraulic or powertrain-related events with technician findings and prior repairs.

Focus: high-duty components
▤

Underground trucks

Use hours and utilization trends to plan service windows while checking braking, cooling and driveline inspection records.

Focus: haulage readiness
⚙

Other mobile equipment

Confirm the actual available fields and OEM maintenance guidance before adopting a common reporting template.

Focus: model-specific context
SIGNAL → ACTION

How to convert equipment data into a maintenance task

Data becomes valuable when it changes a decision and the team can trace that decision to a completed repair.

1
◷

Collect

Review OEM hours, alerts and available utilization data.

2
⌕

Validate

Check machine ID, timestamp, severity and operating context.

3
▣

Plan

Choose inspection, scheduled PM or diagnostic action.

4
⚒

Execute

Record work, labor, parts and technician findings.

5
✓

Review

Confirm repair outcome and recurring event trends.

Example: An underground loader reaches its planned service-hour threshold. The planner checks the OEM reading, verifies the asset and interval, schedules the work and records the completed service. The hour reading informs the decision; the maintenance record documents the action.
DATA QUALITY

Five checks before relying on an OEM report

✓

Asset identity: Match the OEM machine identifier to the correct fleet asset.

✓

Freshness: Check when data was last transmitted, especially underground.

✓

Units: Confirm engine hours, operating hours and other counters are interpreted correctly.

✓

Event meaning: Use OEM documentation and technician judgment rather than assuming every alert means failure.

✓

Record trail: Keep a clear link between reviewed signals and resulting inspections or repairs.

MAINTENANCE REVIEW · EXAMPLE
MachineUnderground Loader · LHD-07
Operating hours5,280 h
Recent eventHydraulic system alert
Review OEM event description and confirm condition before assigning work
OEM signal→Inspection→Work order
Illustrative workflow, not a live Sandvik feed or HVI integration screen.
TURN FINDINGS INTO ACTION

Keep the maintenance history behind every machine.

Use HVI to organize inspections, planned maintenance, work orders and service records alongside the OEM data your team reviews.

SYSTEM BOUNDARIES

Where Sandvik's data and HVI's maintenance records fit

The distinction matters: access to OEM telemetry does not automatically mean it is synchronized with a maintenance platform.

OEM INFORMATION

My Sandvik and machine reports

Depending on the product and equipment configuration, review available machine hours, utilization, events and condition information.

Machine dataOEM contextEvent history
MANUAL REVIEW / VALIDATED DATA PROCESS→Confirm export, access and integration options with the relevant providers.
MAINTENANCE EXECUTION

HVI maintenance records

Document inspections, preventive maintenance, work orders, repair history and relevant service activity for the fleet asset.

PM plansInspectionsWork orders

HVI is not represented here as having a verified native My Sandvik integration, automatic telemetry ingestion or automated fault-code diagnosis. Any integration should be evaluated for your equipment, access rights and technical requirements.

MAINTENANCE PLANNING

Use data to improve three everyday decisions

01WHEN

Schedule the right service window

Compare verified operating hours, OEM service guidance and upcoming production requirements. Avoid scheduling solely from a stale meter reading.

HVI fit: preventive maintenance schedules
02WHAT

Investigate recurring machine events

Look for repeated symptoms across shifts, then assign an inspection or diagnostic task that captures the technician's actual findings.

HVI fit: inspections and work orders
03WHY

Review the cost of repeat repairs

Compare equipment maintenance history, parts consumption and work performed to understand where reliability problems persist.

HVI fit: repair and maintenance history
ROLL-OUT CHECKLIST

A practical four-week pilot for one underground fleet

Start small: prove that the data improves a maintenance decision before expanding the reporting effort.

WEEK 1

Map the fleet

List machines, OEM portal access, equipment identifiers and available fields.

WEEK 2

Verify the readings

Check data freshness, meter differences and alert interpretation.

WEEK 3

Run a review routine

Turn a small set of verified findings into planned inspections or repairs.

WEEK 4

Measure outcomes

Review overdue PM, repeat defects and work-order completion—not just dashboard activity.

DISCUSS YOUR DATA WORKFLOW

Build a clearer path from machine insight to completed maintenance.

See how HVI can support your underground equipment records and service planning. Ask about the capabilities relevant to your fleet before assuming an OEM integration.

FREQUENTLY ASKED QUESTIONS

Sandvik equipment data and underground maintenance

What Sandvik equipment data is most useful for maintenance planning?
Verified operating hours, equipment events, utilization patterns and available condition information can support service scheduling and technical reviews. The fields available depend on the machine, installed systems and OEM product access.
Can HVI automatically import My Sandvik telemetry?
A native automatic connection should not be assumed. Confirm current integration availability and technical requirements with HVI and Sandvik. HVI can support the inspections, PM schedules and maintenance records that follow your team's review of equipment information.
Can fault codes alone determine which repair is needed?
No. Event codes and alerts are starting points for diagnosis. Qualified technicians should consult OEM guidance, verify operating conditions and inspect the equipment before determining the corrective action.
How can operating hours improve underground preventive maintenance?
Accurate hour readings help teams identify service intervals and plan maintenance around production. Use the correct hour counter and OEM maintenance recommendations, then document the completed work and next service requirements.
What should be recorded after a telemetry-triggered inspection?
Record the machine identifier, observation date, relevant alert or hour reading, technician findings, work performed, parts used and any follow-up action. These records help teams distinguish repeat problems from isolated events.

Share This Story, Choose Your Platform!

Start Free Trial Book a Demo