Gubernix / Underground mining

From underground faults to verified software fixes.

Capture diagnostic evidence from drill rigs and loaders, even when the connection drops. Give engineering the context to investigate recurring faults, then roll out approved software changes and verify the result machine by machine.

Follow a recurring fault

Illustrative workflow

Diagnostics · Authorized software changes · Machine control stays yours

Both articulated booms, drill feed rails and low-profile carrier of an unbranded underground drill rig
One recurring fault. An evidence trail. An approved change.Your machine control and safety boundaries stay yours.

01 · Customer ownership

Your equipment. Your authority to change it.

Gubernix works around one approved gateway application—not around the ownership of your machine.

Your equipment andoperating systemsMachine controlSafety systemsAutomationExisting fleet / service toolsCapture and buffer evidenceDeliver data to authorized teamsStage approved releasesVerify outcomes

KD’s ownership model

Gubernix · scoped gateway application

Capture the agreed events, selected signals and installed version. Buffer locally when site connectivity drops; disclose source gaps.

Integration, assessed together.

Generic equipment and interfaces · no named deployment claims
Onboard compute target
Gateway hardware, operating system and application isolation
Telemetry / event interface
Available event logs, selected signals and read permissions
Site connectivity
Coverage, outages, gateway and controlled transfer path
Software owner
OEM or supplier authorized to review, test and sign
Maintenance window
Compatible machine group and agreed installation conditions
Evidence destination
Authorized engineering team and existing service / fleet tools

Integration with existing tools is a path to assess with the customer, not a pre-confirmed connector. Named Sandvik integrations, deployments or results appear only after scope and publication permission are confirmed.

02 · Follow one underground equipment issue

Illustrative data

A fault on shift. Context for engineering. A change you can verify.

Evidence back to engineering

Underground loader

Approved gateway app
Local evidence buffer

Site network

Site link / gateway
Controlled transfer

Engineering workstation

Authorized evidence destination
OEM / software owner

Approved changes out to equipment

Diagnostic application only · owner approved · signed

10:12:00 · original event time

A recurring diagnostic fault during the shift.

LD-07 triggers diagnostic D-042. The approved gateway application captures the event, selected pressure and temperature signals, and diagnostic application v2.3. Machine control and safety systems stay outside its scope.

Capturing evidence

Field event to usable evidence

20 s transfer

Illustrative data
Connected transfer
20 s
Device offline
18 min
Reconnect catch-up
40 s

2 missing source records · transfer not yet complete
Gap: 10:12:08–10:12:09 · never silently filled

Release approval to verified installation

3 targets · awaiting approved rollout

Approval 13:50 · window 14:00–14:30 · compatible diagnostic application v2.4 · all times Illustrative data

MachineInstalled version reportedApplication health reportedState
LD-07Not reportedNot reportedAwaiting verification
LD-12Not reportedNot reportedAwaiting verification
LD-19OfflineNot reportedNot reportedAwaiting verification

All figures are Illustrative data, not measured performance or a customer result. Replace with measured results when an approved customer case is available.

03 · Make the meeting concrete

Bring one machine model and one recurring field issue.

We’ll cover what can be captured, where the data should go, who can approve a change and what can be measured in a pilot.

A practical pilot discussion

  • Map the available events, signals and gaps
  • Agree the authorized evidence destination
  • Confirm the software owner and release boundary
  • Measure evidence latency, completeness and verified outcomes

Optional supporting material
Client video and downloadable technical brief: awaiting approved material. No unapproved references are shown.

Outside this demo’s scope: machine control changes, safety-system updates and autonomous-control authorization. Any wider integration must be assessed separately.