Skip to main content

Diagnostic intelligence

The next maintainer should not start fault finding from scratch.

Trace prepares an advisory fault diagnosis workflow from the report, machine context, prior work and technical information enabled by the organisation.

Context into action

Search the maintenance memory before building the next checks.

FaultPilot brings the machine, symptom and relevant organisational information together, ranks what is useful and prepares a reviewable work structure a maintainer can execute and record.

CONCEPTUAL INFORMATION FLOW

Turn available context into a reviewable work structure.

Advisory only. The maintainer remains responsible for every decision.

AVAILABLE CONTEXTFault reportMachine historyPrior workEnabled information
DIAGNOSTIC PATH01Understand02Find03Rank04Structure
MAINTAINER WORK PACKSafety boundaryImmediate checksOrdered workVerification
Template demonstrationNo AI generation representedNo governed source retrieval represented
Operational context

Fault report

Asset, symptom, operating context, fault codes, photos and work already tried.

Machine context

Model, fleet detail, recent faults, common codes and recurring fault signals.

Prior work

Relevant checks, findings, confirmed causes, repairs, parts and time to fix.

Enabled information

Technical procedures and organisational knowledge made available for the relevant work.

Trace
  1. Understand the query
  2. Search by meaning and terms
  3. Rank the useful evidence
  4. Build structured field work
Maintainer work pack
  1. 01Safe starting conditions
  2. 02Immediate checks and likely causes
  3. 03Ordered diagnostic steps with tools and parts context
  4. 04Verification, escalation and handover ready next actions

Safety in the workflow

Put the hazard and its control beside the diagnostic work.

Task specific hazards remain paired with their controls. General site safety is kept visibly separate, and the maintainer still works under the site's procedures, permits, isolations and judgement.

Task specific controlDrive system inspection
Hazard
Unexpected movement or stored mechanical energy
Control
Confirm isolation and verify zero energy before inspection
Gate
Safety acknowledgement required before work begins
General site safety remains a separate operating requirement.

Visible source states

The crew can see what the workflow is built from.

The interface states whether the workflow uses authorised information, a reduced information set or a configured template before the maintainer acts.

01

Grounded

Relevant enabled information supports the work and its source coverage can be shown.

02

Reduced sources

Useful context exists, but the available source coverage is thinner than the preferred operating state.

03

Template

A clearly marked baseline workflow is used without implying governed retrieval or generated evidence.

Field executionSee how the work pack becomes the repair record.Asset memorySee how the record remains searchable from the console.Field noteRead why source state must stay visible.

Diagnostic intelligence remains advisory. Maintainers remain responsible for site procedures, safe isolation, verification and escalation. Retrieval and document availability depend on the organisation's enabled information and access controls.

Technical evaluationReview the permitted information sources, access boundary, fallback states and evidence required for your operating scope.

Discuss the information boundary