Data Centre Contractor Management

Start with operational objectives

A maintenance system should preserve required asset function while controlling the operational exposure created by the work itself. Frequency alone is not a strategy; the task, failure mode and consequence must be connected.

• Define the function that must be preserved
• Identify credible failure modes and indicators
• Set tasks against condition, usage, time or statutory need
• Review effectiveness using findings and repeat defects

Plan the work against real constraints

The plan should combine asset criticality, manufacturer information, operating experience and site constraints. Package work into windows only after checking interactions with concurrent activities and degraded states.

Every planned activity needs an approved procedure, a competent team, verified isolation boundaries and an agreed return-to-service test.

Practical example

Annual UPS maintenance on a 2N system is planned as two separate windows so that only one system is unavailable at a time, with load transfer verified before each intervention and no concurrent work permitted on the remaining path.

Control execution and feedback

Good maintenance records capture more than completion. Findings, measurements, defects, temporary conditions and follow-up actions should return to planning and risk review.

• Define acceptance criteria before work begins
• Coordinate permits, access, spares and specialist support
• Verify restoration and alarm status
• Track findings to closure with named ownership

Frequently asked questions

How often should critical equipment be maintained?

Frequency should follow the failure modes being managed, manufacturer requirements, operating conditions and statutory obligations — not a single generic interval applied to every asset.

Does maintenance create risk as well as reduce it?

Yes. Work on live infrastructure temporarily reduces redundancy, so planning must consider the exposure during the activity as well as the benefit of the task.