Commissioning, readiness and operational readiness: what is the difference
The three terms appear together in almost every project plan and rarely mean the same thing. The confusion costs accountability — and capability.
Commissioning, readiness and operational readiness are used as synonyms in many project documents. They are not. Each term describes a different object, with a different owner and a different completion criterion.
Commissioning
Commissioning verifies that installed systems work as specified. It is a technical process executed on the asset: equipment testing, integrated tests, instrument verification, control tuning, interlock checking.
The completion criterion is objective: the system passed the specified test or it did not. The owner is the commissioning team, supported by the vendor and engineering.
Readiness
Readiness verifies that the organisation is prepared to operate what has been commissioned. It is an organisational process, not one about the asset: competence available on every shift, procedures in use, critical spares in stock, support contracts in force, management systems live from day one.
The completion criterion is not a single test, and that is where the confusion starts. Readiness is verified by evidence: a competence matrix with demonstrated coverage, a procedure tested in the field, a critical spares list with confirmed availability.
Operational readiness
Operational readiness is the resulting state. It is neither a process nor a checklist: it is the condition in which the operation can sustain the capability required by the business case, within the design envelope, with the resources it has.
A plant can be commissioned and not ready. It can be ready in process and asset and not ready in competence. It can have every checklist signed and still fail to hold stable throughput in month three.
Why the distinction matters
When the three terms blur, the completion of one is used as the completion of another. Commissioning ends, the readiness checklist is signed on the same documents, and operational readiness is declared without anyone having verified actual capability.
The consequence is familiar: a technically successful and economically disappointing start-up. The asset works; the operation does not capture the value the project promised.
Separating the terms is not a semantic exercise. It is what allows accountability to be assigned, acceptance criteria to be defined and, above all, the gap to be measured before it turns into lost production.