Diagnostic check 01Available after safety acknowledgement.
Australian mining maintenance software
The shift ends.
The fault context stays.
Carry one operational record from the machine through fault finding, handover and reliability review.
- Maintainer first
- Console oversight
- Named handovers
The operating gap
Mining maintenance loses too much at the seams.
The work order records what was done. The diagnostic reasoning and next shift context often remain in calls, messages, photos and one person's head.
Without continuity
The next crew rebuilds the fault from fragments.
Each transfer strips away a little more context until the same checks are repeated and the asset history says less than the work that actually happened.
- ObservationWhat the maintainer saw, heard, tested and ruled out
- Safe workThe hazards, controls, checks and evidence around the task
- OwnershipWho has the job, what is blocked and what happens next
- HistoryWhat changed on the asset and what the result proved
With FaultPilotThe known context moves with the work.
The next owner can see what was found, what was checked and what still needs a decision.
One fault. One thread.
Start at the machine. Keep the whole shift in the picture.
The maintainer captures the work while it is happening. The Console carries the same record into assignment, handover, asset history and leadership review.
02 Operations Console
CONSOLEFP-1001 · HT-214Intermittent loss of drive under load
0 of 5- Current owner
- Priya N.
- Safety boundary
- Acknowledgement required
- Handover
- Sam O. · Pending
- Record
- FP-1001 · HT-214
- Field owner
- Priya N.
- Next responsibility
- Sam O. · Pending
Follow the complete record from field intake to supervisory review.
System boundary
Keep planned work in the CMMS. Carry field context through FaultPilot.
FaultPilot captures what happens at the machine, carries it across the shift, then returns a structured record to the maintenance workflow.
Planned work stays where it is.
Work orders, asset registers and commercial records remain in the customer's established systems.
Field evidence stays attached to the fault.
- Fault and asset context
- Safety, checks and findings
- Organisation enabled knowledge
- Evidence, handover and outcome
Close the information gap.
Supported exports and scoped integration return the evidence needed for close out, review and reliability work.
Deployment
Start with one crew. Earn the rollout.
A paid operating test at one site. One crew, one workflow and agreed success criteria.
- 01
Scope
Agree one site, one fleet, one crew and the supported operating workflow.
- 02
Configure
Set up the organisation, fleet information and the technical information enabled for the pilot.
- 03
Operate
Run the 30-day pilot against the baseline and success criteria agreed at kickoff.
Built around the handover
What was seen. What was checked. What comes next.
FaultPilot keeps those details with the fault, so the incoming maintainer can review the agreed record and continue from the last recorded point.
The operating principleKeep the fault, evidence, decisions and next action together.
Why FaultPilot exists Start with the real workflow
Bring the fault path you want to fix.
We will map where context is being lost, define the operating boundary and tell you plainly whether FaultPilot fits the site.
Scope a 30-day pilot