Operational readiness as an asset management discipline

Operational readiness is the asset management discipline that decides how a new asset behaves in its first decade, and it is almost never owned by the people who will live with the consequences. Capital projects deliver a constructed plant, a substation, a fleet, a building, or a digital control system. Operations and maintenance then inherit the running cost of every decision taken during design and construction. The handover between those two worlds is where most of the long-run value of an asset is either secured or quietly lost. Industry studies put the early ramp-up loss on poorly handed-over capital projects at up to 30 per cent of anticipated benefit. The pattern is consistent across refining, power, water, transport and large industrial estates. It is rarely a construction failure. It is an asset management failure dressed up as a commissioning problem.

Project teams measure success at mechanical completion. Asset managers measure it three to five years later, when the asset has either stabilised at design throughput or quietly entered a long period of unplanned work, costly retrofits and missing documentation. Operational readiness is the bridge between those two definitions of success.

What operational readiness actually covers

There is a tendency to confuse operational readiness with commissioning. They are not the same. Commissioning proves that the plant can be started and run safely. Operational readiness proves that the receiving organisation is ready to own the asset across its life. The two run in parallel through the late stages of a capital project, but they answer different questions.

A working definition: operational readiness is the structured assurance that all required operational deliverables (people, processes, data, documentation, spares, contracts, systems and competencies) are complete, tested and accepted before the asset is declared ready for sustained operation. ISO 55001 frames acquisition and commissioning as a controlled lifecycle stage with specified inputs and accepted outputs, not as a finance-led milestone.

The remit usually splits into four domains:

Asset information and data. Tag lists, asset hierarchies, attributes, drawings, manuals, vendor data books, spare parts catalogues, and the digital twin or equivalent loaded into the EAM.
Maintenance strategy and work management. Criticality, failure modes, preventive maintenance programmes, job plans, inspection regimes, and the routines that will exist on day one inside the work management system.
Operating procedures and competence. Standard operating procedures, isolation regimes, permit-to-work integration, training plans, and the assessed competence of the people who will run and maintain the asset.
Sustaining commercials. Spares holding, vendor support contracts, warranty management, calibration regimes, and the service agreements that follow the asset into operation.

Programmes that try to cover only the first domain (the data) and treat the rest as someone else’s problem are the ones that surface twelve months later with a working system of record and an unworkable maintenance backlog.

Why so many handovers fail

The patterns are well documented and depressingly consistent.

Project schedules optimise for the construction milestone, not the operational one. Contractual incentives stop at mechanical completion, and anything that does not block start-up tends to be deferred. Asset information is exactly the kind of deliverable that does not block start-up.

The receiving organisation is rarely staffed early enough to validate what is being handed over. Operations teams are stood up close to commissioning, by which point the data, the maintenance plan and the spare parts strategy have already been set. Acceptance becomes a paperwork exercise rather than a technical one.

The information specification is missing or inconsistent. Without a single, contracted asset information specification, every EPC, vendor and sub-contractor delivers data in the shape that suits them, and the owner reconciles formats for years. CFIHOS, the Capital Facilities Information Handover Specification (layered over ISO 15926), exists precisely so process industry owners do not pay for that reconciliation. Outside the process industries the equivalents are less mature, but the principle is the same.

The maintenance strategy is left as a post-handover exercise. New assets arrive with a vendor-recommended schedule, often generic and conservative, uploaded into the EAM without challenge. Within a year the PM queue is flooded, the wrong work is being done frequently, and the right work is being missed. A PM design that does not flood the work order queue cannot be retrofitted easily once the bad routines are live.

The shape of a credible programme

A defensible operational readiness programme has the same backbone whether the asset is a CCGT, a wastewater works, a depot, an airport baggage system, or a data centre.

A single, contractual asset information specification

Write it once, embed it in every EPC and vendor contract, and govern it from the owner side. The specification covers what asset records will exist, what attributes are mandatory, how tagging works, what documents must accompany each asset class, and how the data will be delivered (format, structure, frequency of progressive handover, acceptance criteria). For process industries, CFIHOS is the natural reference. For other sectors, build the equivalent against ISO 55001 lifecycle requirements and the receiving EAM data model.

Maintenance strategy built before commissioning, not after

Criticality assessment, failure mode analysis and PM design are operational readiness deliverables, not steady-state activities to start in year two. The receiving organisation should walk into go-live with a defensible maintenance strategy already loaded against asset classes, ready to be refined by real failure data. Programmes that already use criticality assessment that changes behaviour find this step natural. Programmes that do not, default to vendor-recommended schedules and spend years undoing the consequences.

Progressive, staged handover with formal acceptance

Treat handover as a series of accepted milestones rather than a single event at start-up. Tag lists transfer first, then hierarchies, then attributes and documents, then maintenance strategy, then spares and contracts. Each stage is checked against the specification, accepted by a named owner-side authority and tracked. The progressive approach surfaces problems while the project still has the contractual leverage to fix them. A single big-bang handover at the gate surfaces them when no one is paid to care.

An owner-side team with the authority to refuse acceptance

If the operations and asset management organisation cannot refuse acceptance of incomplete or non-compliant deliverables, none of the rest matters. The team needs the headcount, the technical authority and the executive sponsorship to push back on the project. Without that, every contested item is conceded to keep the schedule, and the asset enters operation with debts the owner will pay for years.

A measurable handover scorecard

A short, public scorecard makes operational readiness governable. Useful measures include the percentage of tagged assets with complete attribute sets, the percentage of asset classes with an accepted maintenance strategy, the percentage of critical spares stocked and contracted, the number of unaccepted deliverables outstanding at each milestone, and the number of post-handover changes already in flight. Boards understand scorecards. They tend not to understand handover narratives.

A short diagnostic

Asset leaders facing an imminent handover, or a recent one that has not stabilised, can score their position quickly. Five honest answers usually predict the next twelve months better than the formal readiness review.

Is there a single, contractually binding asset information specification, applied to every EPC and vendor on the programme?
Has criticality and maintenance strategy been completed for every asset class before commissioning, or is it scheduled for “after go-live”?
Is the receiving operations and asset management team staffed, trained and on site early enough to validate deliverables, not just receive them?
Are handover deliverables accepted at named, staged milestones, with the authority to refuse incomplete items?
Is there a published scorecard that a sponsor can read in two minutes and act on?

Where the answers are weak, the cost of strengthening them is small relative to the cost of an asset that never settles. Programmes that take this seriously typically formalise the operating model alongside the platform, rather than treating operational readiness as a workstream that only the project team can see.

The bottom line

Operational readiness is the unfashionable end of asset management. It does not generate transformation slides and rarely shows up in vendor demonstrations. It does, however, decide whether a new asset performs from day one or spends a decade being quietly retrofitted by the people who inherited it. Experienced operators put it near the top of every best practice list, for good reason.