During development, progress is measured through visible milestones: design completion, equipment delivery, energization, integrated systems testing, commissioning and handover. Another transition deserves the same attention. It is the point at which the operations organization can take ownership of the facility.

That is operational readiness.

Commissioning proves the systems. Operations has to live with them.

What commissioning answers

Commissioning asks whether the plant performs to design intent.

  • Does the generator start when required?
  • Does the UPS transfer correctly?
  • Does the cooling system respond to a changing load?
  • Do alarms reach the monitoring platform?
  • Do systems perform according to design intent?

Those tests matter. They do not answer whether the site can be run at 2:00 a.m. after the project team has left.

What operational readiness asks

Operational readiness asks a different set of questions.

  • What happens when an alarm occurs at 2:00 a.m.?
  • Does the operator know what it means?
  • Is there an approved procedure, and does it describe the configuration that was actually installed?
  • Who is authorized to act?
  • What conditions require escalation?
  • Are known deficiencies visible to the operating team?
  • Has the team demonstrated that it can respond?

A system can pass a commissioning test while the organization around that system is still incomplete.

The same gap is already on the public calendar. Commissioning is a watch item on Highly Credible projects. This note does not claim that any named site is unready. Public pages do not publish internal procedures or CMMS evidence. They do show that the operating question now sits next to commissioning, not after a later buildout. That calendar is in the operational readiness challenge.

Handover is not a document transfer

Data centre handover produces a large information set:

  • drawings and equipment schedules
  • commissioning records
  • OEM manuals
  • training materials
  • asset registers
  • warranty information
  • open item lists
  • operating procedures

All of these are necessary. Possession of them does not create operating capability. The useful question is whether that information has been turned into something the operations team can use under real conditions.

A technically correct emergency operating procedure has limited value if operators have never practiced it. A CMMS populated with equipment records has limited value if maintenance requirements, spares and vendor support are incomplete. A BMS may display thousands of points correctly and still present alarms in a way that leaves the operator guessing during an incident.

Operational readiness is whether the facility, the controls, the procedures and the people work together.

The readiness test

Before a facility enters steady-state operations, these areas should be tested as one system.

1. Plant status

Operations should know exactly what it is inheriting: completed systems, outstanding deficiencies, temporary configurations, commissioning exceptions and accepted risks. The operating organization should meet those facts at handover, not discover them afterwards.

2. Procedures

SOPs, MOPs and EOPs should describe the facility that was built, not the design that existed months earlier. Critical procedures should be reviewed with the people expected to execute them. Where the consequence is material, they should be demonstrated.

3. Controls and monitoring

BMS, EPMS and the rest of the operational technology need to give operators information they can interpret and act on. Alarm priorities, escalation, remote access, overrides and dependencies should be understood before the facility enters normal operation.

4. Maintenance readiness

An asset list is not a maintenance programme. Preventive maintenance requirements, vendor relationships, critical spares, maintenance windows and equipment history should be in place before the facility depends on them.

5. People and competency

Training attendance is not competency. Operators responsible for critical systems should be able to show that they understand those systems, the procedures that govern them and the consequences of their actions. Labour supply for the Alberta buildout is a separate evidence set, in what boards should watch in Alberta’s data-centre talent market. Workforce competency assesses demonstrated capability. It is not a certification programme.

6. Governance

Change control, incident management, access control, vendor management, escalation and risk acceptance should already be functioning. A newly commissioned facility starts to change almost immediately. Without that governance, design intent and operating reality diverge from the first week.

Connected operational technology

Modern data centres depend on connected operational technology. BMS, EPMS, PLCs, intelligent power equipment, cooling controls and vendor-supported systems tie the physical plant to digital control.

Readiness then includes a further set of questions.

  • Who can remotely access critical systems?
  • How are vendors controlled?
  • What happens when a critical OT component cannot be patched immediately?
  • Do network segmentation and access rules match how the plant has to be operated?
  • Can the operations team tell a cyber event, a controls fault and an equipment failure apart?

These are operational questions. The consequences appear in the physical facility.

Why independent assurance matters

Project teams are accountable for finishing the project. Commissioning teams are accountable for proving the systems. Operations is accountable for availability after both have left. Each brief is legitimate. They do not test the same thing.

Operations assurance examines the transition between them: handover evidence, live controls and demonstrated crew competency. The aim is evidence that the facility, its controls, its procedures and its people are collectively ready to operate. It is not a second commissioning checklist, and it does not replace the commissioning authority, the engineer or owner acceptance.

That evidence matters most where the operating organization is being built alongside the plant: a new platform, or an operator expanding faster than its procedures.

The question before service

As a project approaches service, one question is whether the facility has been commissioned. The other is whether the operations team could safely run it tomorrow if the project team disappeared.

If that second answer is still unclear, the facility may be technically complete. The operating work is not finished.

DC Intel provides independent data centre intelligence and operational assurance from project development through live operations. For operational readiness, handover assurance or critical infrastructure operations, contact us.