Diagnostic check 01Available after safety acknowledgement.
How it works
One operating thread, viewed from the field and the Console.
The Maintainer application creates the record at the machine. The Console coordinates people, continuity and review without rebuilding that record.
The maintenance lifecycle
Each stage adds evidence. None of it resets the story.
FaultPilot does not replace the maintenance system of record. It keeps the field operating context useful as work moves between people, shifts and review.
- Fault intakeTie the problem to the machine.
Asset, symptom, codes, photos and operating context start one attributed record.
- Safe workPut hazards and safeguards beside the job.
Task specific hazards, paired controls and the safety gate sit before diagnostic action.
- Field recordRecord the work as it happens.
Checks, findings, photos, parts, readings and verification stay with the job.
- Job delegationPut the right work with the right crew.
Supervisors offer, assign and reassign work with asset, attention and ownership visible.
- HandoverMove responsibility cleanly.
Work completed, blockers and the exact next action move to a named person.
- Asset historyLet the machine retain what crews learned.
Faults, work, findings, parts and repair outcomes become one explorable history.
- ReliabilityTurn recorded history into reliability work.
Repeat faults, asset patterns and supported reports remain connected to the source record.
Maintainer application
Build the record while the machine and the context are still together.
Structured intake leads into a visible safety boundary, then controlled work. The current FP-1001 demonstration remains at 0 of 5 with safety unacknowledged.
MAINTAINER APPLICATION
One field record carried through the work.
FP-1001 · HT-214 · Template workflow
Three stages. One attributed field record.
Capture the faultTie the symptom to the asset while the operating context is still fresh.
Hold the safety boundaryThe 5-step template remains locked at 0 of 5.
Pass the known contextThe named recipient reviews the finding, evidence and next action.
Conditional diagnostic knowledge
Bring forward useful context only when the authorised information supports it.
The diagnostic path changes with the information and capabilities authorised for the site. The FP-1001 demonstration below states the exact mode being shown.
CONCEPTUAL INFORMATION FLOW
Turn available context into a reviewable work structure.
Advisory only. The maintainer remains responsible for every decision.
DIAGNOSTIC PATH01Understand02Find03Rank04Structure
Operations console
Coordinate the operation from the same attributed record.
The Console starts after the field record exists. It brings open work, crew context, attention, handovers, assets and supported review into one operating view with drill back to source records.
CONSOLEFP-1001 · HT-214Intermittent loss of drive under load
0 of 5- Current owner
- Priya N.
- Safety boundary
- Acknowledgement required
- Handover
- Sam O. · Pending
Continuity
Move responsibility with the finding and next action intact.
Job handovers and supervisor shift handovers keep different responsibilities clear.
CONTINUITY MODEL
Two handover records. Two accountable review paths.
Job ownership and shift responsibility move differently. Both retain the source fault and its latest useful context.
Maintainer to named maintainer
- Source
- FP-1001 · HT-214
- From and to
- Priya N. to Sam O.
- Carries
- Finding, evidence, blocker and next action
- Review
- Accept or decline in the Maintainer application
Outgoing supervisor to incoming supervisor
- Scope
- Selected jobs and shift operating context
- Recipient
- Named next shift supervisor
- Carries
- Ownership, safety boundaries and next actions
- Review
- Draft, review, publish and acknowledge
Asset memory and reliability
Trace reliability review back to the recorded work.
Asset history, selected review scopes and exports remain connected to the recorded maintenance activity.
ASSET MEMORY AND REVIEW
The measure never outruns the maintenance record.
FaultPilot keeps the source work explorable, then limits reliability review to the authorised inputs that actually exist.
HT-214
Selected record · FP-1001- 01
Fault openedFP-1001 linked to HT-214
- 02
Field context recordedFinding, note and evidence stay attributable
- 03
Handover preparedPriya N. to Sam O.
Selected authorised scope
- Scope
- Selected authorised recordsOrganisation, site, crew, person or asset
- Source
- Recorded maintenance inputsFaults, work, handovers and valid measures
- Boundary
- Only supported resultsIncomplete inputs remain clearly marked as No data
- Output
- Drill back or exportSource job, asset history, CSV or scoped PDF
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.
Bring the current fault, job delegation and handover workflow. We will map it against a bounded 30-day operating test.
Scope a 30-day pilot