Compressed-Air Reliability-Centred Maintenance Engineering

COMPRESSED-AIR RELIABILITY-CENTRED MAINTENANCE ENGINEERING

Legacy route: /rental-air/portable/. Commercial state remains RENTAL FLEET / EVIDENCE PENDING with Rental Application Engineer + Operations Reviewer review. That identity remains separately preserved and is not overwritten.

Provisional new-series slug: /compressed-air-engineering/reliability-centred-maintenance/ | Primary CTA: Build My Compressed-Air RCM Programme

Maintenance should protect required functions — not simply service equipment because the calendar says so

The central question is not 'How often do we service this machine?' but 'What function must remain available, how can it fail, what evidence can detect or prevent that failure, and what maintenance action is technically justified?'

RCM does not eliminate preventive maintenance, OEM requirements or statutory inspection. It organises them around function, failure consequence, failure mode, detectability, task effectiveness and evidence. Exact service intervals, lubricant requirements, clearances, test limits and safety procedures remain equipment- and project-specific.

1 — Required Function

RCM Foundation: govern required function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

2 — Functional Performance Standard

RCM Foundation: govern functional performance standard from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

3 — Functional Failure

RCM Foundation: govern functional failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

4 — Asset Boundary

RCM Foundation: govern asset boundary from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

5 — System Boundary

RCM Foundation: govern system boundary from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

6 — Process Consequence

RCM Foundation: govern process consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

7 — Criticality Input

RCM Foundation: govern criticality input from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

8 — Operating Context

RCM Foundation: govern operating context from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

9 — Duty Cycle

RCM Foundation: govern duty cycle from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

10 — Environment

RCM Foundation: govern environment from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

11 — Maintenance History

RCM Foundation: govern maintenance history from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

12 — Failure History

RCM Foundation: govern failure history from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

13 — Configuration History

RCM Foundation: govern configuration history from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

14 — Oem Requirement

RCM Foundation: govern OEM requirement from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

15 — Statutory/Specialist Boundary

RCM Foundation: govern statutory/specialist boundary from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

16 — Failure Mode

Failure Mode Engineering: govern failure mode from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

17 — Failure Mechanism

Failure Mode Engineering: govern failure mechanism from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

18 — Failure Cause

Failure Mode Engineering: govern failure cause from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

19 — Failure Effect

Failure Mode Engineering: govern failure effect from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

20 — Local Effect

Failure Mode Engineering: govern local effect from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

21 — System Effect

Failure Mode Engineering: govern system effect from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

22 — Process Effect

Failure Mode Engineering: govern process effect from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

23 — Hidden Failure

Failure Mode Engineering: govern hidden failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

24 — Evident Failure

Failure Mode Engineering: govern evident failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

25 — Degradation Failure

Failure Mode Engineering: govern degradation failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

26 — Sudden Failure

Failure Mode Engineering: govern sudden failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

27 — Common-Mode Failure

Failure Mode Engineering: govern common-mode failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

28 — Maintenance-Induced Failure

Failure Mode Engineering: govern maintenance-induced failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

29 — Human-Factor Failure

Failure Mode Engineering: govern human-factor failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

30 — Obsolescence Failure

Failure Mode Engineering: govern obsolescence failure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

31 — Safety Consequence

Consequence Logic: govern safety consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

32 — Quality Consequence

Consequence Logic: govern quality consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

33 — Production Consequence

Consequence Logic: govern production consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

34 — Environmental Consequence

Consequence Logic: govern environmental consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

35 — Equipment Consequence

Consequence Logic: govern equipment consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

36 — Energy Consequence

Consequence Logic: govern energy consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

37 — Maintenance Consequence

Consequence Logic: govern maintenance consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

38 — Hidden-Function Consequence

Consequence Logic: govern hidden-function consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

39 — Standby Consequence

Consequence Logic: govern standby consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

40 — Recovery Consequence

Consequence Logic: govern recovery consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

41 — Financial Consequence

Consequence Logic: govern financial consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

42 — Customer Consequence

Consequence Logic: govern customer consequence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

43 — Criticality Tier Link

Consequence Logic: govern criticality tier link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

44 — Interruption Tolerance

Consequence Logic: govern interruption tolerance from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

45 — Residual-Risk Owner

Consequence Logic: govern residual-risk owner from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

46 — Scheduled Restoration

Task Selection: govern scheduled restoration from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

47 — Scheduled Replacement

Task Selection: govern scheduled replacement from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

48 — Condition-Based Task

Task Selection: govern condition-based task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

49 — Failure-Finding Task

Task Selection: govern failure-finding task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

50 — Lubrication Task

Task Selection: govern lubrication task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

51 — Inspection Task

Task Selection: govern inspection task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

52 — Cleaning Task

Task Selection: govern cleaning task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

53 — Calibration/Verification Task

Task Selection: govern calibration/verification task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

54 — Functional Test

Task Selection: govern functional test from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

55 — Proof Test

Task Selection: govern proof test from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

56 — Run-To-Failure Decision

Task Selection: govern run-to-failure decision from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

57 — Redesign Trigger

Task Selection: govern redesign trigger from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

58 — Spare-Parts Action

Task Selection: govern spare-parts action from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

59 — Operator Care Task

Task Selection: govern operator care task from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

60 — No-Effective-Task Escalation

Task Selection: govern no-effective-task escalation from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

61 — Vibration Monitoring

Condition Monitoring: govern vibration monitoring from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

62 — Temperature Trending

Condition Monitoring: govern temperature trending from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

63 — Differential-Pressure Trending

Condition Monitoring: govern differential-pressure trending from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

64 — Lubricant/Oil Analysis

Condition Monitoring: govern lubricant/oil analysis from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

65 — Motor Electrical Condition

Condition Monitoring: govern motor electrical condition from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

66 — Bearing Condition

Condition Monitoring: govern bearing condition from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

67 — Cooler Performance

Condition Monitoring: govern cooler performance from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

68 — Airend Performance

Condition Monitoring: govern airend performance from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

69 — Separator Restriction

Condition Monitoring: govern separator restriction from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

70 — Filter Restriction

Condition Monitoring: govern filter restriction from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

71 — Dryer Performance

Condition Monitoring: govern dryer performance from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

72 — Dew-Point Trend

Condition Monitoring: govern dew-point trend from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

73 — Drain Condition

Condition Monitoring: govern drain condition from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

74 — Sensor Drift

Condition Monitoring: govern sensor drift from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

75 — Control-State Anomaly

Condition Monitoring: govern control-state anomaly from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

76 — Airend Function

Compressor Package RCM: govern airend function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

77 — Motor Function

Compressor Package RCM: govern motor function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

78 — Coupling/Belt Function

Compressor Package RCM: govern coupling/belt function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

79 — Lubrication Function

Compressor Package RCM: govern lubrication function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

80 — Separator Function

Compressor Package RCM: govern separator function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

81 — Cooler Function

Compressor Package RCM: govern cooler function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

82 — Fan/Pump Function

Compressor Package RCM: govern fan/pump function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

83 — Inlet Filtration

Compressor Package RCM: govern inlet filtration from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

84 — Minimum-Pressure/Check Valve

Compressor Package RCM: govern minimum-pressure/check valve from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

85 — Blowdown Function

Compressor Package RCM: govern blowdown function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

86 — Controller Function

Compressor Package RCM: govern controller function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

87 — Vsd/Starter Function

Compressor Package RCM: govern VSD/starter function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

88 — Package Sensors

Compressor Package RCM: govern package sensors from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

89 — Safety/Protection Devices

Compressor Package RCM: govern safety/protection devices from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

90 — Enclosure/Ventilation Interface

Compressor Package RCM: govern enclosure/ventilation interface from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

91 — Refrigerated Dryer Function

Treatment & Storage RCM: govern refrigerated dryer function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

92 — Adsorption Dryer Function

Treatment & Storage RCM: govern adsorption dryer function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

93 — Dryer Valves

Treatment & Storage RCM: govern dryer valves from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

94 — Dryer Refrigeration Circuit

Treatment & Storage RCM: govern dryer refrigeration circuit from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

95 — Dryer Regeneration System

Treatment & Storage RCM: govern dryer regeneration system from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

96 — Prefilter Function

Treatment & Storage RCM: govern prefilter function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

97 — Afterfilter Function

Treatment & Storage RCM: govern afterfilter function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

98 — Activated-Carbon Stage

Treatment & Storage RCM: govern activated-carbon stage from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

99 — Automatic Drains

Treatment & Storage RCM: govern automatic drains from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

100 — Condensate Treatment

Treatment & Storage RCM: govern condensate treatment from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

101 — Receiver Storage Function

Treatment & Storage RCM: govern receiver storage function from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

102 — Receiver Drain

Treatment & Storage RCM: govern receiver drain from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

103 — Receiver Instruments

Treatment & Storage RCM: govern receiver instruments from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

104 — Isolation/Bypass Valves

Treatment & Storage RCM: govern isolation/bypass valves from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

105 — Quality Monitoring

Treatment & Storage RCM: govern quality monitoring from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

106 — Main Header Integrity

Distribution & Utility RCM: govern main header integrity from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

107 — Branch Integrity

Distribution & Utility RCM: govern branch integrity from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

108 — Flexible Connection

Distribution & Utility RCM: govern flexible connection from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

109 — Couplings

Distribution & Utility RCM: govern couplings from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

110 — Supports

Distribution & Utility RCM: govern supports from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

111 — Isolation Valves

Distribution & Utility RCM: govern isolation valves from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

112 — Pressure Regulators

Distribution & Utility RCM: govern pressure regulators from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

113 — Point-Of-Use Filters

Distribution & Utility RCM: govern point-of-use filters from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

114 — Local Receivers

Distribution & Utility RCM: govern local receivers from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

115 — Critical Hoses

Distribution & Utility RCM: govern critical hoses from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

116 — Cooling-Water System

Distribution & Utility RCM: govern cooling-water system from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

117 — Room Ventilation

Distribution & Utility RCM: govern room ventilation from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

118 — Electrical Feeder Interface

Distribution & Utility RCM: govern electrical feeder interface from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

119 — Emergency-Air Connection

Distribution & Utility RCM: govern emergency-air connection from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

120 — Metering Infrastructure

Distribution & Utility RCM: govern metering infrastructure from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

121 — Job Plan

Planning & Execution: govern job plan from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

122 — Work Scope

Planning & Execution: govern work scope from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

123 — Permit/Isolation Interface

Planning & Execution: govern permit/isolation interface from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

124 — Required Competence

Planning & Execution: govern required competence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

125 — Parts/Tools Readiness

Planning & Execution: govern parts/tools readiness from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

126 — Pre-Work Baseline

Planning & Execution: govern pre-work baseline from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

127 — As-Found Evidence

Planning & Execution: govern as-found evidence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

128 — Defect Classification

Planning & Execution: govern defect classification from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

129 — Work Execution

Planning & Execution: govern work execution from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

130 — As-Left Evidence

Planning & Execution: govern as-left evidence from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

131 — Functional Verification

Planning & Execution: govern functional verification from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

132 — Performance Verification

Planning & Execution: govern performance verification from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

133 — Configuration Update

Planning & Execution: govern configuration update from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

134 — Handover

Planning & Execution: govern handover from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

135 — Post-Maintenance Monitoring

Planning & Execution: govern post-maintenance monitoring from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

136 — Rcm Register Owner

RCM Governance: govern RCM register owner from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

137 — Asset Hierarchy

RCM Governance: govern asset hierarchy from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

138 — Failure Coding

RCM Governance: govern failure coding from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

139 — Task Library

RCM Governance: govern task library from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

140 — Interval Basis

RCM Governance: govern interval basis from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

141 — Condition Trigger

RCM Governance: govern condition trigger from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

142 — Backlog Priority

RCM Governance: govern backlog priority from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

143 — Deferral Governance

RCM Governance: govern deferral governance from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

144 — Critical-Spares Link

RCM Governance: govern critical-spares link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

145 — Training Link

RCM Governance: govern training link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

146 — Sop Link

RCM Governance: govern SOP link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

147 — Fmea Link

RCM Governance: govern FMEA link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

148 — Incident-Learning Link

RCM Governance: govern incident-learning link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

149 — Change-Management Link

RCM Governance: govern change-management link from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

150 — Rcm Review Cycle

RCM Governance: govern RCM review cycle from the required compressed-air function and its consequence. Record the asset/system boundary, operating context, credible failure mode, evidence source, task or monitoring method, responsible role, acceptance/trigger criterion and post-task verification. Preserve exact OEM, statutory, pressure-system, electrical and safety requirements where applicable. If a task cannot demonstrably prevent, detect or reveal the relevant failure, do not retain it merely because it is traditional; document the gap and evaluate redesign, proof testing, spares or run-to-failure only within approved risk governance.

151 — Premium RCM Decision Register

152 — RCM Task-Selection Matrix

153 — Technical / RCM Verification Gate

Required functions and performance standards are explicit.

Functional failures are separated from component symptoms.

Failure modes are credible for the actual operating context.

OEM/statutory requirements remain preserved.

Preventive tasks have a defined failure-control purpose.

Condition-based tasks use measurable degradation and actionable lead time.

Hidden standby/protective functions have failure-finding where justified.

Intervals/triggers have an evidence basis rather than arbitrary harmonisation.

Run-to-failure decisions are explicit and consequence controlled.

Repeat failures trigger RCA/redesign rather than endless repetitive PM.

As-found/as-left evidence is preserved for critical work.

Intrusive maintenance is followed by appropriate functional/performance verification.

Configuration and documentation are updated after maintenance changes.

What is reliability-centred maintenance for air compressors?

A structured method that starts with required functions and failure consequences, then selects maintenance, monitoring, proof testing, spares or redesign that actually controls credible failure modes.

Is RCM the same as preventive maintenance?

No. Preventive maintenance is one possible RCM response; RCM can also use condition-based tasks, failure-finding, redesign or controlled run-to-failure.

How does compressor criticality affect maintenance?

Higher-consequence functions can justify stronger monitoring, proof testing, spares, backlog escalation and recovery planning.

When should condition-based maintenance be used?

When a credible degradation parameter can be measured with enough warning to take effective action before functional failure.

What is a hidden failure?

A failure that is not evident during normal operation, such as an unavailable standby or protective function that may only be discovered when demanded.

Should every compressor receive the same maintenance interval?

No. Preserve exact OEM/site requirements, but operating context, condition, criticality and evidence can require different governance.

What is failure-finding maintenance?

A controlled test used to reveal whether a hidden standby, protective or backup function is actually available.

When is run-to-failure acceptable?

Only where consequence, recovery, spares and risk governance support it and no more effective proactive task is justified.

Why preserve as-found and as-left data?

It shows whether the maintenance task addressed the actual condition and establishes a new baseline.

What should happen after repeat failures?

Escalate to root-cause analysis, FMEA or redesign instead of simply repeating the same maintenance.

Can AI create an RCM programme?

AI can organise histories and suggest candidate failure modes, but equipment-specific tasks, limits, intervals and risk decisions require verified evidence and competent review.

How does RCM connect to spare parts?

Failure consequence, detectability, lead time and recovery strategy determine which spares are truly critical.