Data centers: connect digital demand with physical resilience.

Data centers include enterprise facilities, colocation sites, cloud and hyperscale operations, and smaller edge locations closer to users or equipment. IBM’s overview distinguishes these models and the different divisions of responsibility between infrastructure providers and customers.

For an OT discussion, establish who owns the building systems, who operates the IT equipment and who approves changes. A whole-site view and a tenant’s view may cover different assets. The first useful boundary is therefore both physical and organisational: the equipment involved and the people able to act on its condition.

The electrical path can include utility supplies, switchgear, uninterruptible power supplies, backup generation and distribution equipment serving IT racks. Cooling may involve air-handling units, chillers, pumps, heat rejection equipment or liquid cooling circuits, depending on the facility design. These systems support servers, storage and networking equipment.

The U.S. DOE design guide treats IT conditions, air management, cooling and electrical systems as related parts of facility efficiency. For a practical overview, map which power and cooling assets serve each area, where measurements are taken, and which systems share a dependency.

Computing work changes over time, while the facility supplies power and removes heat within its design and operating constraints. Daily work includes monitoring, inspection, maintenance, incident response and the controlled introduction of equipment or capacity changes. The relevant operating record should show what configuration was active during the period being reviewed.

Map that cycle from a capacity request or planned maintenance task through assessment, implementation and verification. Identify the information exchanged between IT, facilities and service teams. A change in one area should be understood by the people responsible for the connected assets before it becomes an unexplained event in another system.

The major challenges include maintaining service through equipment problems, accommodating changing load, managing constrained power or cooling capacity, and understanding energy use. Australian government guidance recommends assessing where power is consumed and whether cooling capacity matches the IT load; it also highlights the effect of poor airflow.

A facility-wide average can hide a local question. Ask whether a temperature change belongs to a particular rack area, a workload shift or a maintenance condition. Compare efficiency figures over a defined boundary and operating period. A useful review should consider the service being supported as well as the resources consumed.

Building and equipment controls already observe and regulate parts of the facility. A broader OT approach connects their measurements, operating states and event histories with the relevant asset and maintenance context. This can support a shared view of capacity, equipment condition and developing exceptions.

Define how an observation becomes an action: who checks the condition, who coordinates with other teams and who authorises a change. Preserve the distinction between monitoring and switching or control authority. Clear timestamps, known data quality and visible gaps help avoid treating an old or incomplete reading as the present state of the facility.

Choose a hall, room or group of racks and map its electrical and cooling support. Review the equipment status, measurements and maintenance records already available. Include IT and facilities colleagues so the physical boundary matches the service responsibilities.

Agree a useful first outcome, such as a clearer explanation of recurring alarms or a better-informed maintenance discussion. Evaluate whether the necessary context can be assembled reliably before expanding across the site. Data Center Insights provides deeper reading on power and cooling, and on operational continuity, while this overview keeps the connected facility in focus.