A finished build is not yet a working system.
A building can be physically complete while its ventilation controls are wrong. A railway asset can be installed while one interface still misreads state. A data centre can contain all the hardware and still fail its power-transfer test. A school programme can have curriculum, staff and classrooms and still be unready for the first cohort.
Commissioning is the transition that turns completed installation into demonstrated operational capability. It verifies that components work individually, interfaces work together, controls respond correctly, operators understand the system, documentation matches reality and the whole arrangement performs under the conditions it was designed to face.
This is a specialist branch beneath How Engineering Works. Engineering spans need, requirements, design, verification, operation and retirement. Commissioning occupies the critical boundary between built and ready to operate.
Construction Completion Is Not Functional Completion
Physical completion answers questions such as: Was the equipment installed? Are the cables connected? Are the pipes in place? Is the software deployed?
Commissioning asks a different class of questions:
- Does the installed system behave according to the requirement?
- Do sensors report believable values?
- Do interlocks block unsafe transitions?
- Do alarms reach the right receiver?
- Can one subsystem hand state to the next?
- Does failover actually transfer function?
- Can operators recognise abnormal conditions and recover?
The difference is the difference between presence and capability.
Commissioning Begins Before the End
Good commissioning is designed early. Requirements should specify what must be demonstrated, what evidence counts, which operating states must be tested and who has authority to accept the result.
If commissioning is treated as a final inspection after every design decision has already hardened, difficult defects become expensive discoveries rather than manageable design questions.
The strongest programmes therefore connect commissioning criteria to requirements, interface contracts and verification plans from the start.
Component Test → Subsystem Test → Integrated Test
Commissioning usually builds confidence in layers.
- Component checks: confirm individual equipment, sensors, actuators or software services are installed and functional.
- Subsystem checks: confirm a bounded system performs its internal job.
- Interface checks: prove state, signals, custody and control cross boundaries correctly.
- Integrated testing: operate several subsystems together under realistic conditions.
- Performance demonstration: show the end-to-end system meets the required outcome.
This hierarchy matters because a collection of passing component tests does not prove integrated behaviour. Failure often lives at the handoff.
See How Interface Contracts Work and How Cross-System Handoffs Work.
Cold Test and Live Test Are Different
A system can pass isolated simulation and still fail under real load.
Commissioning therefore distinguishes safe pre-live tests from tests under actual operating conditions. Pumps are run with real flow. backup power is transferred under realistic load. signalling logic is exercised with operational sequences. digital services are tested with realistic traffic and dependency behaviour.
Live testing must be controlled because the test itself can create risk. Commissioning is not permission to “try everything”; it is a governed evidence programme.
The Acceptance Criteria Must Be Explicit
A commissioning test should not end with “looks okay.”
The pass condition may specify flow, pressure, temperature, accuracy, response time, stopping distance, failover time, alarm propagation, energy use, error rate or another measurable requirement.
Where judgment is required, the judging authority and evidence should still be explicit. Acceptance is a state transition; it should have a guard condition.
This connects commissioning directly to How State Validation Works.
Defects Become a Managed Punch List
Commissioning rarely produces a perfectly clean first run. Findings are logged, classified and routed.
- critical defect: blocks safe or essential operation;
- major defect: important requirement not met;
- minor defect: limited issue with controlled workaround;
- documentation defect: physical system and recorded system disagree;
- optimisation item: capability works but can be tuned later.
The classification prevents cosmetic completion from hiding operational unreadiness.
Documentation Is Part of the Product
A commissioned system should leave behind an operational representation of itself.
Drawings, configuration, asset identifiers, test records, maintenance instructions, control narratives, alarm lists, spare parts, training materials and known limitations should match the system that actually exists.
If the documentation describes the design while the field contains several undocumented changes, the system begins its operational life with built-in state drift.
Operators Must Be Commissioned Too
Capability does not reside only in equipment.
Operators need to know normal states, alarms, limits, safe manual actions, degraded modes, escalation routes and restart conditions. Maintenance teams need access, spares and diagnostic procedures. Management needs ownership and service thresholds.
A technically perfect asset can fail operationally if the people receiving it were treated as an afterthought.
Worked Example: Building Systems
A new building has chillers, pumps, air-handling units, sensors and a building-management system. Installation completion proves the equipment exists. Commissioning proves that temperatures are measured correctly, control loops maintain conditions, alarms appear, pumps sequence properly, energy meters reconcile and backup states work.
The building becomes operational when the integrated environmental system, not merely the individual machines, is verified.
Worked Example: MRT Asset
A new rail subsystem must fit into power, signalling, communications, train operations, maintenance and safety procedures already in service.
Commissioning therefore tests more than the new hardware. It verifies interfaces with the existing railway and the behaviour of the complete route under normal and abnormal scenarios.
The specialist railway estate remains under How MRT Works | It’s Mathematics.
Worked Example: Digital Platform
A new service has passed unit and integration tests. Production commissioning still asks whether secrets, permissions, monitoring, backups, scaling, failover, alerts, support ownership and rollback are ready.
The deployment may be technically successful while production capability is not yet commissioned.
A Careful Analogy: Education Programme
A new curriculum can be “finished” on paper while teacher preparation, assessment, materials, timetable and student support remain untested together.
A commissioning analogy asks whether the whole programme can produce the intended learner experience under real school conditions before scale-up. It is an analogy, not a claim that education should be reduced to engineering acceptance testing.
Commissioning Ends With Handover, Not Abandonment
The final handover should transfer:
- accepted operating state;
- open defects and limitations;
- documentation and configuration;
- spares and tools;
- training evidence;
- warranty and supplier responsibilities;
- baseline performance measurements.
That baseline becomes the reference for later maintenance, reliability and lifecycle decisions.
A Commissioning Checklist
- Trace commissioning tests back to requirements.
- Verify component installation and calibration.
- Test subsystem behaviour.
- Test interfaces and integrated sequences.
- Test abnormal and failover states safely.
- Measure performance against explicit acceptance criteria.
- Close or govern defects.
- Align documentation with as-built reality.
- Train operators and maintainers.
- Transfer a verified baseline into operation.
The CivDJ Rotation
- Forward: completed build → test → integrated demonstration → accepted capability → operational handover.
- Backward: start from the receiver’s required service and ask which commissioning evidence proves every necessary subsystem and handoff.
- Rotate: compare designer, contractor, operator, maintainer, safety owner and end-user views of “ready.”
Commissioning is the moment construction stops being a promise and becomes evidence that the system can actually carry its intended job.
Continue through How Engineering Works, How State Validation Works and the master How X Works hub. Next: ramp-up — what happens after first operation when capability exists, but stable full performance has not yet been earned.