COMPRESSED-AIR BREAKDOWN DIAGNOSTICS, FAULT TRIAGE & RECOVERY ENGINEERING
It also requires diagnostic conclusions to state evidence, tests and unresolved uncertainty. These controls are expanded here without inventing diagnosis-time or first-time-fix guarantees.
Provisional new-series slug: /compressed-air-engineering/breakdown-diagnostics-fault-triage-recovery/ | CTA: Diagnose My Compressor Breakdown
The first job in a breakdown is not to reset the alarm. it is to make the condition safe and preserve the evidence that explains why the machine stopped
The objective is safe restoration of required service while preserving fault chronology, distinguishing symptoms from mechanisms, testing competing causes and verifying that corrective work actually restored the compressor system.
A compressor trip can originate outside the compressor. Supply voltage, cooling water, room ventilation, downstream pressure, blocked treatment, closed valves, failed drains, sequencing, sensor error or process demand can create package symptoms. The diagnostic boundary therefore expands from the alarmed component to the complete compressed-air utility when evidence requires it.
1 — Asset Identity
Breakdown Triage Foundation: govern asset identity as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
2 — Breakdown Timestamp
Breakdown Triage Foundation: govern breakdown timestamp as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
3 — Operating State
Breakdown Triage Foundation: govern operating state as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
4 — Production Consequence
Breakdown Triage Foundation: govern production consequence as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
5 — Criticality
Breakdown Triage Foundation: govern criticality as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
6 — Safety Condition
Breakdown Triage Foundation: govern safety condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
7 — Fault Code
Breakdown Triage Foundation: govern fault code as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
8 — Alarm Chronology
Breakdown Triage Foundation: govern alarm chronology as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
9 — Operator Observation
Breakdown Triage Foundation: govern operator observation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
10 — Recent Maintenance
Breakdown Triage Foundation: govern recent maintenance as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
11 — Recent Configuration Change
Breakdown Triage Foundation: govern recent configuration change as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
12 — Recent Process Change
Breakdown Triage Foundation: govern recent process change as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
13 — Environmental Condition
Breakdown Triage Foundation: govern environmental condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
14 — Diagnostic Owner
Breakdown Triage Foundation: govern diagnostic owner as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
15 — Revision Control
Breakdown Triage Foundation: govern revision control as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
16 — Abnormal Noise
Stabilise & Make Safe: govern abnormal noise as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
17 — Abnormal Heat
Stabilise & Make Safe: govern abnormal heat as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
18 — Air Leak
Stabilise & Make Safe: govern air leak as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
19 — Oil/Fluid Leak
Stabilise & Make Safe: govern oil/fluid leak as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
20 — Electrical Smell/Smoke Boundary
Stabilise & Make Safe: govern electrical smell/smoke boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
21 — Pressure Hazard
Stabilise & Make Safe: govern pressure hazard as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
22 — Stored Pressure
Stabilise & Make Safe: govern stored pressure as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
23 — Rotating Hazard
Stabilise & Make Safe: govern rotating hazard as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
24 — Hot Surface
Stabilise & Make Safe: govern hot surface as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
25 — Cooling-Water Leak
Stabilise & Make Safe: govern cooling-water leak as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
26 — Structural Damage
Stabilise & Make Safe: govern structural damage as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
27 — Remote-Start Risk
Stabilise & Make Safe: govern remote-start risk as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
28 — Isolation Need
Stabilise & Make Safe: govern isolation need as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
29 — Secondary-Damage Risk
Stabilise & Make Safe: govern secondary-damage risk as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
30 — Safe-State Confirmation
Stabilise & Make Safe: govern safe-state confirmation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
31 — Controller Fault History
Evidence Preservation: govern controller fault history as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
32 — Vsd Fault History
Evidence Preservation: govern VSD fault history as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
33 — Sequencer History
Evidence Preservation: govern sequencer history as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
34 — Event Timestamp
Evidence Preservation: govern event timestamp as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
35 — Pressure Trend
Evidence Preservation: govern pressure trend as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
36 — Temperature Trend
Evidence Preservation: govern temperature trend as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
37 — Current/Power Trend
Evidence Preservation: govern current/power trend as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
38 — Speed/Load Trend
Evidence Preservation: govern speed/load trend as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
39 — Oil Level
Evidence Preservation: govern oil level as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
40 — Oil Condition
Evidence Preservation: govern oil condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
41 — Vibration Evidence
Evidence Preservation: govern vibration evidence as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
42 — Photos/Video
Evidence Preservation: govern photos/video as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
43 — Failed-Part Condition
Evidence Preservation: govern failed-part condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
44 — Operator Statement
Evidence Preservation: govern operator statement as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
45 — Data Export
Evidence Preservation: govern data export as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
46 — Incoming Voltage
Power & Electrical Fault Chain: govern incoming voltage as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
47 — Phase Condition
Power & Electrical Fault Chain: govern phase condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
48 — Protection Trip
Power & Electrical Fault Chain: govern protection trip as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
49 — Fuse/Breaker Boundary
Power & Electrical Fault Chain: govern fuse/breaker boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
50 — Starter/Contactor
Power & Electrical Fault Chain: govern starter/contactor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
51 — Vsd Input
Power & Electrical Fault Chain: govern VSD input as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
52 — Vsd Fault
Power & Electrical Fault Chain: govern VSD fault as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
53 — Motor Current
Power & Electrical Fault Chain: govern motor current as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
54 — Motor Temperature
Power & Electrical Fault Chain: govern motor temperature as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
55 — Motor Insulation Boundary
Power & Electrical Fault Chain: govern motor insulation boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
56 — Terminal Condition
Power & Electrical Fault Chain: govern terminal condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
57 — Control Power
Power & Electrical Fault Chain: govern control power as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
58 — Earthing Boundary
Power & Electrical Fault Chain: govern earthing boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
59 — Generator Supply Boundary
Power & Electrical Fault Chain: govern generator supply boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
60 — Electrical Specialist Escalation
Power & Electrical Fault Chain: govern electrical specialist escalation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
61 — Controller State
Controls & Instrument Fault Chain: govern controller state as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
62 — Pressure Sensor
Controls & Instrument Fault Chain: govern pressure sensor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
63 — Temperature Sensor
Controls & Instrument Fault Chain: govern temperature sensor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
64 — Flow Sensor Boundary
Controls & Instrument Fault Chain: govern flow sensor boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
65 — Dp Sensor
Controls & Instrument Fault Chain: govern DP sensor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
66 — Dew-Point Sensor
Controls & Instrument Fault Chain: govern dew-point sensor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
67 — I/O State
Controls & Instrument Fault Chain: govern I/O state as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
68 — Interlock
Controls & Instrument Fault Chain: govern interlock as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
69 — Permissive
Controls & Instrument Fault Chain: govern permissive as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
70 — Local/Remote Mode
Controls & Instrument Fault Chain: govern local/remote mode as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
71 — Setpoint
Controls & Instrument Fault Chain: govern setpoint as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
72 — Configuration
Controls & Instrument Fault Chain: govern configuration as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
73 — Communication Link
Controls & Instrument Fault Chain: govern communication link as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
74 — Stale/Bad Data
Controls & Instrument Fault Chain: govern stale/bad data as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
75 — Sensor Plausibility
Controls & Instrument Fault Chain: govern sensor plausibility as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
76 — Ambient Temperature
Cooling & Thermal Fault Chain: govern ambient temperature as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
77 — Intake Temperature
Cooling & Thermal Fault Chain: govern intake temperature as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
78 — Room Ventilation
Cooling & Thermal Fault Chain: govern room ventilation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
79 — Recirculation
Cooling & Thermal Fault Chain: govern recirculation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
80 — Cooler Condition
Cooling & Thermal Fault Chain: govern cooler condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
81 — Fan Condition
Cooling & Thermal Fault Chain: govern fan condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
82 — Cooling-Water Flow
Cooling & Thermal Fault Chain: govern cooling-water flow as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
83 — Cooling-Water Temperature
Cooling & Thermal Fault Chain: govern cooling-water temperature as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
84 — Thermostatic/Bypass Boundary
Cooling & Thermal Fault Chain: govern thermostatic/bypass boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
85 — Lubricant/Coolant Level
Cooling & Thermal Fault Chain: govern lubricant/coolant level as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
86 — Filter Restriction
Cooling & Thermal Fault Chain: govern filter restriction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
87 — High-Pressure Duty
Cooling & Thermal Fault Chain: govern high-pressure duty as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
88 — Thermal Sensor
Cooling & Thermal Fault Chain: govern thermal sensor as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
89 — Temperature Trend
Cooling & Thermal Fault Chain: govern temperature trend as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
91 — Lubricant Identity
Lubrication & Separation Fault Chain: govern lubricant identity as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
92 — Oil Level
Lubrication & Separation Fault Chain: govern oil level as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
93 — Oil Pressure Boundary
Lubrication & Separation Fault Chain: govern oil pressure boundary as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
94 — Oil-Filter Condition
Lubrication & Separation Fault Chain: govern oil-filter condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
95 — Fluid Degradation
Lubrication & Separation Fault Chain: govern fluid degradation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
96 — Water Contamination
Lubrication & Separation Fault Chain: govern water contamination as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
97 — Separator Dp
Lubrication & Separation Fault Chain: govern separator DP as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
98 — Oil Carryover
Lubrication & Separation Fault Chain: govern oil carryover as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
99 — Scavenge Line
Lubrication & Separation Fault Chain: govern scavenge line as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
100 — Minimum-Pressure Valve
Lubrication & Separation Fault Chain: govern minimum-pressure valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
101 — Foaming
Lubrication & Separation Fault Chain: govern foaming as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
102 — Leakage
Lubrication & Separation Fault Chain: govern leakage as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
103 — Oil-Analysis Evidence
Lubrication & Separation Fault Chain: govern oil-analysis evidence as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
104 — Recent Oil Service
Lubrication & Separation Fault Chain: govern recent oil service as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
106 — Airend Vibration
Airend & Mechanical Fault Chain: govern airend vibration as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
107 — Bearing Condition
Airend & Mechanical Fault Chain: govern bearing condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
108 — Abnormal Noise
Airend & Mechanical Fault Chain: govern abnormal noise as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
109 — Rotor-Contact Suspicion
Airend & Mechanical Fault Chain: govern rotor-contact suspicion as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
110 — Coupling Condition
Airend & Mechanical Fault Chain: govern coupling condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
111 — Belt Condition
Airend & Mechanical Fault Chain: govern belt condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
112 — Gear Condition
Airend & Mechanical Fault Chain: govern gear condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
113 — Alignment
Airend & Mechanical Fault Chain: govern alignment as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
114 — Soft Foot
Airend & Mechanical Fault Chain: govern soft foot as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
115 — Foundation
Airend & Mechanical Fault Chain: govern foundation as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
116 — Motor Bearing
Airend & Mechanical Fault Chain: govern motor bearing as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
117 — Mechanical Drag
Airend & Mechanical Fault Chain: govern mechanical drag as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
118 — Wear Debris
Airend & Mechanical Fault Chain: govern wear debris as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
119 — Recent Overhaul
Airend & Mechanical Fault Chain: govern recent overhaul as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
121 — Intake Filter
Air Path / Valve / Pressure Fault Chain: govern intake filter as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
122 — Inlet Restriction
Air Path / Valve / Pressure Fault Chain: govern inlet restriction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
123 — Inlet Valve
Air Path / Valve / Pressure Fault Chain: govern inlet valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
124 — Minimum-Pressure Valve
Air Path / Valve / Pressure Fault Chain: govern minimum-pressure valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
125 — Blowdown Valve
Air Path / Valve / Pressure Fault Chain: govern blowdown valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
126 — Check Valve
Air Path / Valve / Pressure Fault Chain: govern check valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
127 — Discharge Valve
Air Path / Valve / Pressure Fault Chain: govern discharge valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
128 — Separator Restriction
Air Path / Valve / Pressure Fault Chain: govern separator restriction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
129 — Aftercooler Restriction
Air Path / Valve / Pressure Fault Chain: govern aftercooler restriction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
130 — Dryer/Filter Dp
Air Path / Valve / Pressure Fault Chain: govern dryer/filter DP as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
131 — Receiver Pressure
Air Path / Valve / Pressure Fault Chain: govern receiver pressure as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
132 — Distribution Valve
Air Path / Valve / Pressure Fault Chain: govern distribution valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
133 — Network Pressure Loss
Air Path / Valve / Pressure Fault Chain: govern network pressure loss as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
134 — Process Demand
Air Path / Valve / Pressure Fault Chain: govern process demand as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
135 — Closed/Incorrect Valve
Air Path / Valve / Pressure Fault Chain: govern closed/incorrect valve as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
136 — Aftercooler
Treatment & Downstream Fault Chain: govern aftercooler as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
137 — Separator/Drain
Treatment & Downstream Fault Chain: govern separator/drain as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
138 — Refrigerated Dryer
Treatment & Downstream Fault Chain: govern refrigerated dryer as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
139 — Adsorption Dryer
Treatment & Downstream Fault Chain: govern adsorption dryer as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
140 — Prefilter
Treatment & Downstream Fault Chain: govern prefilter as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
141 — Afterfilter
Treatment & Downstream Fault Chain: govern afterfilter as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
142 — Condensate Drain
Treatment & Downstream Fault Chain: govern condensate drain as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
143 — Pdp Condition
Treatment & Downstream Fault Chain: govern PDP condition as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
144 — Filter Dp
Treatment & Downstream Fault Chain: govern filter DP as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
145 — Treatment Bypass
Treatment & Downstream Fault Chain: govern treatment bypass as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
146 — Receiver
Treatment & Downstream Fault Chain: govern receiver as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
147 — Distribution Contamination
Treatment & Downstream Fault Chain: govern distribution contamination as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
148 — Point-Of-Use Restriction
Treatment & Downstream Fault Chain: govern point-of-use restriction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
149 — Critical-User Pressure
Treatment & Downstream Fault Chain: govern critical-user pressure as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
150 — Downstream Process Interaction
Treatment & Downstream Fault Chain: govern downstream process interaction as part of a hypothesis-driven breakdown investigation. Record exact asset and operating state, symptom, alarm/event chronology, measurement or inspection evidence, applicable manufacturer limit or reference, test performed, result, confidence and unresolved uncertainty. Do not clear evidence or replace parts merely because a fault code names a component. Where a test carries electrical, pressure, rotating, thermal or other hazard, use the site's competent-person and isolation controls.
151 — Premium Breakdown Diagnostic Register
Field | Controlled record | Purpose |
|---|---|---|
Incident | ID/date/time | Traceability |
Asset | Tag/model/serial | Identity |
State | Load/speed/pressure/process | Context |
Fault | Code/alarm/symptom | Trigger |
Chronology | Events before/after trip | Evidence |
Safety state | Hazards/isolation | Control |
Measurements | Pressure/temp/current/etc. | Evidence |
Hypotheses | Competing causes | Reasoning |
Tests | Method/result | Discrimination |
Finding | Confirmed/probable/unresolved | Conclusion |
Repair | Action/part/configuration | Response |
As-left | Controlled-load behaviour | Verification |
Residual risk | Open uncertainty | Transparency |
Follow-up | RCA/monitoring/work order | Closure |
Revision | Reviewer/date | History |
152 — Fault Triage Matrix
Symptom / trip | First questions | Evidence path |
|---|---|---|
Will not start | Power? permissive? emergency stop? pressure state? controller? | Supply/control/I-O/event history |
Trips on start | Electrical overload? mechanical drag? configuration? | Current/VSD/mechanical evidence |
High temperature trip | Cooling? ambient? load? fluid? sensor? | |
Low pressure / low capacity | Demand? intake? valve? speed? leakage? airend? | Flow/pressure/intake/control evidence |
High separator DP | Flow? element? sensor? fluid deposits? | |
Oil carryover | Separator? scavenge? level? fluid? pressure? | |
High vibration | Motor? coupling? airend? foundation? | |
Dryer quality failure | Overload? PDP sensor? drains? regeneration? | |
Repeated breaker/VSD trip | Supply? motor? load? drive? | |
System pressure collapse | Compressor fault? valve/header? demand surge? | Plant pressure/flow/sequencing evidence |
153 — Fault Code Is a Starting Point, Not Root Cause
A fault code identifies what the controller detected, not necessarily why the condition developed. Preserve context and test the physical/electrical chain before assigning cause.
154 — Repeated Resetting Destroys Diagnostic Value
Repeated resets can overwrite logs, alter operating state, heat/cool components or create secondary damage. Capture evidence first unless immediate safety action requires otherwise.
155 — Parts Swapping Is Not Diagnosis
Replacing a sensor, valve, filter or controller without a tested hypothesis can temporarily change symptoms while the real cause remains.
156 — Recovery vs Permanent Correction
A controlled temporary restoration can be appropriate where risk is understood, but it must be labelled temporary with limitations, monitoring, owner and permanent corrective action.
157 — Verify Under Controlled Load
After repair, confirm relevant protection, pressure, temperature, vibration, controls, treatment and operating behaviour at an agreed representative condition; a machine that merely starts is not fully verified.
158 — Technical / Breakdown Verification Gate
Verify safety, chronology, measurements, hypotheses, tests, repair, as-left behaviour and unresolved uncertainty. No diagnosis-time, response-time or first-time-fix guarantee is invented.
160 — AEO / Engineering FAQ Layer
Answer what to preserve after a compressor trip, why alarms should not be repeatedly reset, how high-temperature/low-pressure/vibration/VSD faults are triaged, and how a repair is verified.