Compressed-Air Maintenance Planning, Work-Order & Shutdown Coordination Engineering

COMPRESSED-AIR MAINTENANCE PLANNING, WORK-ORDER & SHUTDOWN COORDINATION ENGINEERING

The expanded benchmark library informs maintenance/service topic breadth.

Its safeguard prohibits installation-compliance claims without current manufacturer instructions, site engineering, competent electrical/mechanical work and applicable local-code review. That legacy identity remains separately preserved.

Provisional new-series slug: /compressed-air-engineering/maintenance-planning-work-order-shutdown-coordination/ | CTA: Build My Compressor Maintenance Work Plan

Maintenance quality is decided before the machine stops: in the scope, parts, evidence, isolation, sequence, responsibility and restart plan

A technically correct maintenance task can still fail if the wrong asset is scoped, parts are missing, access is blocked, stored energy is not controlled, production dependencies are unknown, measurements are not captured, configuration is lost or restart acceptance is undefined.

The page therefore treats every material intervention as a controlled lifecycle event: identify the need, define scope, plan resources and outage, isolate safely, preserve as-found evidence, execute against approved technical data, control deviations, recommission, verify function and close the record without losing unresolved risk.

1 — Asset Identity

Maintenance Planning Foundation: govern asset identity as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

2 — Maintenance Trigger

Maintenance Planning Foundation: govern maintenance trigger as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

3 — Work Type

Maintenance Planning Foundation: govern work type as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

4 — Criticality

Maintenance Planning Foundation: govern criticality as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

5 — Scope Owner

Maintenance Planning Foundation: govern scope owner as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

6 — Technical Owner

Maintenance Planning Foundation: govern technical owner as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

7 — Operations Owner

Maintenance Planning Foundation: govern operations owner as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

8 — Planned Date

Maintenance Planning Foundation: govern planned date as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

9 — Outage Window

Maintenance Planning Foundation: govern outage window as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

10 — Production Dependency

Maintenance Planning Foundation: govern production dependency as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

11 — Redundancy State

Maintenance Planning Foundation: govern redundancy state as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

12 — Temporary-Air Need

Maintenance Planning Foundation: govern temporary-air need as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

13 — Technical Data Source

Maintenance Planning Foundation: govern technical data source as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

14 — Acceptance Criteria

Maintenance Planning Foundation: govern acceptance criteria as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

15 — Revision Control

Maintenance Planning Foundation: govern revision control as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

16 — Work-Order Id

Work-Order Architecture: govern work-order ID as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

17 — Problem Statement

Work-Order Architecture: govern problem statement as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

18 — Requested Work

Work-Order Architecture: govern requested work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

19 — Asset Hierarchy

Work-Order Architecture: govern asset hierarchy as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

20 — Priority

Work-Order Architecture: govern priority as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

21 — Failure Code Boundary

Work-Order Architecture: govern failure code boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

22 — Task List

Work-Order Architecture: govern task list as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

23 — Parts List

Work-Order Architecture: govern parts list as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

24 — Tools/Test Equipment

Work-Order Architecture: govern tools/test equipment as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

25 — Labour/Skill Requirement

Work-Order Architecture: govern labour/skill requirement as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

26 — Permit Requirement

Work-Order Architecture: govern permit requirement as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

27 — Isolation Requirement

Work-Order Architecture: govern isolation requirement as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

28 — Evidence Requirement

Work-Order Architecture: govern evidence requirement as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

29 — Completion Criteria

Work-Order Architecture: govern completion criteria as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

30 — Closeout Owner

Work-Order Architecture: govern closeout owner as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

31 — Routine Maintenance

Scope Definition: govern routine maintenance as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

32 — Condition-Based Work

Scope Definition: govern condition-based work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

33 — Corrective Repair

Scope Definition: govern corrective repair as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

34 — Diagnostic Investigation

Scope Definition: govern diagnostic investigation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

35 — Overhaul Boundary

Scope Definition: govern overhaul boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

36 — Inspection

Scope Definition: govern inspection as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

37 — Calibration/Verification

Scope Definition: govern calibration/verification as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

38 — Cleaning

Scope Definition: govern cleaning as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

39 — Configuration Change

Scope Definition: govern configuration change as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

40 — Piping Work

Scope Definition: govern piping work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

41 — Electrical Work

Scope Definition: govern electrical work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

42 — Treatment Work

Scope Definition: govern treatment work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

43 — Temporary Modification

Scope Definition: govern temporary modification as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

44 — Deferred Work

Scope Definition: govern deferred work as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

45 — Scope Exclusion

Scope Definition: govern scope exclusion as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

46 — Parts Availability

Pre-Shutdown Readiness: govern parts availability as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

47 — Part Applicability

Pre-Shutdown Readiness: govern part applicability as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

48 — Consumables

Pre-Shutdown Readiness: govern consumables as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

49 — Special Tools

Pre-Shutdown Readiness: govern special tools as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

50 — Lifting Plan Boundary

Pre-Shutdown Readiness: govern lifting plan boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

51 — Access/Scaffold Boundary

Pre-Shutdown Readiness: govern access/scaffold boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

52 — Contractor Readiness

Pre-Shutdown Readiness: govern contractor readiness as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

53 — Technical Drawings

Pre-Shutdown Readiness: govern technical drawings as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

54 — Manuals/Procedures

Pre-Shutdown Readiness: govern manuals/procedures as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

55 — Permits

Pre-Shutdown Readiness: govern permits as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

56 — Production Clearance

Pre-Shutdown Readiness: govern production clearance as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

57 — Temporary-Air Plan

Pre-Shutdown Readiness: govern temporary-air plan as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

58 — Waste Handling

Pre-Shutdown Readiness: govern waste handling as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

59 — Weather/Site Constraint

Pre-Shutdown Readiness: govern weather/site constraint as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

60 — Go/No-Go Review

Pre-Shutdown Readiness: govern go/no-go review as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

61 — Electrical Isolation

Isolation & Stored Energy: govern electrical isolation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

62 — Pneumatic Isolation

Isolation & Stored Energy: govern pneumatic isolation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

63 — Stored Pressure

Isolation & Stored Energy: govern stored pressure as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

64 — Mechanical Energy

Isolation & Stored Energy: govern mechanical energy as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

65 — Thermal Energy

Isolation & Stored Energy: govern thermal energy as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

66 — Gravity/Load Boundary

Isolation & Stored Energy: govern gravity/load boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

67 — Cooling-Water Isolation

Isolation & Stored Energy: govern cooling-water isolation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

68 — Control-Energy Boundary

Isolation & Stored Energy: govern control-energy boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

69 — Remote-Start Prevention

Isolation & Stored Energy: govern remote-start prevention as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

70 — Multiple-Feed Boundary

Isolation & Stored Energy: govern multiple-feed boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

71 — Bleed/Depressurise

Isolation & Stored Energy: govern bleed/depressurise as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

72 — Zero-Energy Verification

Isolation & Stored Energy: govern zero-energy verification as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

73 — Lock/Tag Governance

Isolation & Stored Energy: govern lock/tag governance as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

74 — Permit Boundary

Isolation & Stored Energy: govern permit boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

75 — Isolation Handback

Isolation & Stored Energy: govern isolation handback as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

76 — Load Transfer

Shutdown Sequence Engineering: govern load transfer as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

77 — Standby Start

Shutdown Sequence Engineering: govern standby start as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

78 — Production Notification

Shutdown Sequence Engineering: govern production notification as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

79 — Controlled Unload

Shutdown Sequence Engineering: govern controlled unload as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

80 — Cool-Down Boundary

Shutdown Sequence Engineering: govern cool-down boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

81 — Stop Sequence

Shutdown Sequence Engineering: govern stop sequence as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

82 — Isolation Sequence

Shutdown Sequence Engineering: govern isolation sequence as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

83 — Depressurisation

Shutdown Sequence Engineering: govern depressurisation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

84 — Drainage

Shutdown Sequence Engineering: govern drainage as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

85 — Configuration Capture

Shutdown Sequence Engineering: govern configuration capture as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

86 — As-Found Measurements

Shutdown Sequence Engineering: govern as-found measurements as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

87 — Disassembly Start

Shutdown Sequence Engineering: govern disassembly start as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

88 — Parallel-Work Coordination

Shutdown Sequence Engineering: govern parallel-work coordination as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

89 — Critical-Path Task

Shutdown Sequence Engineering: govern critical-path task as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

90 — Schedule Control

Shutdown Sequence Engineering: govern schedule control as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

91 — Exact Part Identity

Parts & Materials Governance: govern exact part identity as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

92 — Supersession Boundary

Parts & Materials Governance: govern supersession boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

93 — Applicability

Parts & Materials Governance: govern applicability as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

94 — Quantity

Parts & Materials Governance: govern quantity as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

95 — Kit Completeness

Parts & Materials Governance: govern kit completeness as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

96 — Lubricant Identity

Parts & Materials Governance: govern lubricant identity as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

97 — Seal/Gasket Material

Parts & Materials Governance: govern seal/gasket material as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

98 — Filter/Separator Element

Parts & Materials Governance: govern filter/separator element as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

99 — Bearing Boundary

Parts & Materials Governance: govern bearing boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

100 — Fastener Boundary

Parts & Materials Governance: govern fastener boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

101 — Electrical Component

Parts & Materials Governance: govern electrical component as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

102 — Sensor/Instrument

Parts & Materials Governance: govern sensor/instrument as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

103 — Storage Condition

Parts & Materials Governance: govern storage condition as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

104 — Traceability

Parts & Materials Governance: govern traceability as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

105 — Unused/Removed Parts Control

Parts & Materials Governance: govern unused/removed parts control as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

106 — Approved Procedure

Execution & Quality Control: govern approved procedure as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

107 — Technician Competence Boundary

Execution & Quality Control: govern technician competence boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

108 — Cleanliness

Execution & Quality Control: govern cleanliness as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

109 — Measurement Method

Execution & Quality Control: govern measurement method as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

110 — Torque/Data Boundary

Execution & Quality Control: govern torque/data boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

111 — Inspection Hold Point

Execution & Quality Control: govern inspection hold point as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

112 — As-Found Evidence

Execution & Quality Control: govern as-found evidence as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

113 — As-Left Evidence

Execution & Quality Control: govern as-left evidence as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

114 — Nonconformance

Execution & Quality Control: govern nonconformance as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

115 — Scope Change

Execution & Quality Control: govern scope change as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

116 — Unexpected Damage

Execution & Quality Control: govern unexpected damage as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

117 — Specialist Escalation

Execution & Quality Control: govern specialist escalation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

118 — Workmanship Check

Execution & Quality Control: govern workmanship check as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

119 — Foreign-Material Control

Execution & Quality Control: govern foreign-material control as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

120 — Quality Release

Execution & Quality Control: govern quality release as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

121 — Isolation Removal

Recommissioning & Restart: govern isolation removal as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

122 — Guard/Panel Restoration

Recommissioning & Restart: govern guard/panel restoration as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

123 — Fluid Level

Recommissioning & Restart: govern fluid level as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

124 — Valve Lineup

Recommissioning & Restart: govern valve lineup as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

125 — Configuration Restore

Recommissioning & Restart: govern configuration restore as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

126 — Sensor Plausibility

Recommissioning & Restart: govern sensor plausibility as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

127 — Manual Rotation Boundary

Recommissioning & Restart: govern manual rotation boundary as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

128 — Initial Start

Recommissioning & Restart: govern initial start as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

129 — Leak Check

Recommissioning & Restart: govern leak check as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

130 — Temperature Stabilisation

Recommissioning & Restart: govern temperature stabilisation as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

131 — Vibration Check

Recommissioning & Restart: govern vibration check as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

132 — Pressure Control

Recommissioning & Restart: govern pressure control as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

133 — Treatment Function

Recommissioning & Restart: govern treatment function as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

134 — Alarm/Trip Review

Recommissioning & Restart: govern alarm/trip review as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

135 — Production Handback

Recommissioning & Restart: govern production handback as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

136 — Service Report

Closeout & Learning: govern service report as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

137 — Parts Used

Closeout & Learning: govern parts used as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

138 — Measurements

Closeout & Learning: govern measurements as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

139 — Photos

Closeout & Learning: govern photos as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

140 — Configuration Changes

Closeout & Learning: govern configuration changes as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

141 — Unresolved Defect

Closeout & Learning: govern unresolved defect as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

142 — Temporary Repair

Closeout & Learning: govern temporary repair as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

143 — Residual Risk

Closeout & Learning: govern residual risk as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

144 — Follow-Up Action

Closeout & Learning: govern follow-up action as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

145 — Next Due Task

Closeout & Learning: govern next due task as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

146 — Failure Code

Closeout & Learning: govern failure code as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

147 — Root-Cause Trigger

Closeout & Learning: govern root-cause trigger as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

148 — Baseline Reset

Closeout & Learning: govern baseline reset as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

149 — Document Archive

Closeout & Learning: govern document archive as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

150 — Lessons Learned

Closeout & Learning: govern lessons learned as a traceable work-management control. Record exact asset, maintenance trigger, scope, technical source, responsible owner, required isolation, parts/tools, planned outage, as-found evidence, execution result, deviation, as-left verification and residual risk. Do not convert generic maintenance practice into model-specific intervals, torque values, isolation points or acceptance limits. If scope changes after opening the machine, control the change before continuing rather than silently expanding the job.

151 — Premium Maintenance Work-Pack Register

152 — Shutdown Readiness Matrix

153 — Work Order Is an Engineering Record

A work order should preserve why the work was needed, what was found, what changed, what evidence proves completion and what remains unresolved—not merely a labour booking.

154 — Shutdown Scope Freeze & Change Control

Freeze the planned scope before outage where practical. If inspection reveals additional defects, record the new evidence, risk, parts/time impact and approval before expanding the work.

155 — Critical-Path Maintenance Engineering

Identify tasks that govern restart, specialist availability, cure/cool-down times, parts dependencies, inspections and parallel work. A shutdown schedule should expose these dependencies rather than hide them in a single duration.

156 — Temporary Air & Redundancy Coordination

Where maintenance removes critical capacity, prove standby or temporary-air duty, quality, pressure, connection, controls and mobilisation before shutdown. Do not assume rental availability.

157 — Restart Is Part of Maintenance

Maintenance is not complete when tools are removed. Recommissioning must prove fluid levels, valve line-up, configuration, guards, leaks, pressure control, temperatures, vibration, treatment and alarms as relevant.

158 — Technical / Work-Management Verification Gate

Verify exact asset, scope, technical source, parts, isolation, outage, evidence, deviations, acceptance and residual risk. No universal interval, shutdown duration, manpower norm or response-time promise is invented.

160 — AEO / Engineering FAQ Layer

Answer what a compressor maintenance work pack should contain, how shutdowns are planned, why parts/isolation/readiness matter, how temporary air is coordinated, what as-found/as-left evidence means and how restart acceptance is controlled.