Make Monitoring Reflect Data Center Operations
Data center power monitoring is useful only when its measurements support real operating decisions. New data center switchgear can provide visibility into incoming power, distribution sections, or selected feeders, but the right measurement points depend on the one-line diagram and how operators manage capacity, maintenance, and abnormal conditions. A facility may need to distinguish utility supply, generator or alternate-source paths, and loads serving different spaces or systems; those boundaries must be confirmed for the project rather than presumed.
Start by identifying who will use the data and what they need to answer: Is a source available? Which distribution path is carrying load? Has a value crossed an operating threshold? These questions shape instrument selection, alarm priorities, and the information presented to monitoring systems. Monitoring is not a substitute for protective functions or operating procedures. Qualified electrical professionals should review the design, intended use, and applicable requirements before equipment is specified.
Select Measurements Around Decisions
Metering choices can include voltage, current, power, energy, frequency, demand, or power-quality information, subject to the selected devices and system design. Not every measurement is needed at every point. Define whether operators need phase-level detail, aggregate values, directional information, or energy readings for a particular boundary. Confirm expected system configuration, measurement accuracy needs, current-sensing approach, and the available space and wiring provisions with the switchgear designer.
A useful metering schedule names each point, its purpose, required values, units, and intended audience. It should also clarify whether readings are for live operations, trend analysis, reporting, or another purpose. Avoid treating meter data as a guaranteed billing or compliance basis unless the design and relevant requirements support that use. The project team should verify instrument compatibility with the electrical system and confirm that measurement points align with the facility’s one-line and naming conventions.
Define Alarm Meaning and Response
Alarms should distinguish conditions that require immediate operator attention from advisory information and routine status changes. For each alarm, specify the monitored condition, threshold or logic source, priority, delay or persistence behavior if needed, and the intended response. Examples may include a measurement beyond a project-defined limit, device communication loss, or a change in equipment status; which conditions are available depends on selected components and design.
Agree on alarm ownership and presentation before procurement. Operators need clear point names, meaningful text, and a defined route to the system where alarms are reviewed. Confirm how alarm acknowledgment, event timestamps, state changes, and restoration are handled by the receiving platform. Thresholds should be established by the responsible engineering and operations teams using project requirements, not copied without review. Alarm design should complement protection and facility procedures, not imply that monitoring equipment independently makes a system safe.
Plan Communications and Interfaces
Document the intended communications path from meters and other selected devices to the facility monitoring or supervisory platform. Confirm protocols, network boundaries, interface hardware, point counts, addressing responsibilities, and who supplies or configures each element. Compatibility cannot be assumed from a protocol name alone: the project should verify supported data points, required data formats, timing, and any gateway or integration needs across the actual equipment and software.
Network and control-system coordination matters as much as device selection. Identify whether the switchgear package is expected to provide communications connections only or additional configured points, and establish the division of work with the controls integrator and owner. Review cybersecurity and access requirements with the facility’s responsible team, including approved connection methods and account or configuration procedures. These decisions affect drawings, wiring, device schedules, and procurement, so resolve them early enough to avoid late interface changes.
Coordinate Design, Testing, and Data Use
Provide the switchgear supplier with current one-line diagrams, equipment schedules, monitoring point lists, preferred naming conventions, interface documents, and relevant network requirements. Also identify the facility’s operating objectives, expected source arrangements, data destinations, and responsibility boundaries among the owner, engineer, equipment supplier, and integrator. The manufacturer builds new equipment in the USA using all-American components and can develop custom assemblies to specification; project-specific requirements and applicable standards must be reviewed before the design is finalized.
During design review, reconcile metering locations and alarm points against drawings and the receiving system’s point list. Define commissioning checks appropriate to the project, such as verifying displayed values, point names, status changes, alarm routing, communications, and time alignment. Agree on test methods and acceptance responsibility in advance; no particular interface, listing, or test scope should be assumed. Where UL 891 applies to a suitable switchboard assembly, confirm that applicability for the specific design rather than extending it to all switchgear.
Turn Requirements Into a Procurement Package
Before requesting a quotation for new switchgear, assemble the one-line, preliminary equipment schedule, monitoring and alarm matrix, communications requirements, and interface responsibility list. Mark requirements as mandatory, preferred, or unresolved, and identify the person authorized to settle open points. Include operational data needs such as units, naming, timestamp expectations, retention destination, and required reporting outputs where known. This gives the manufacturer a practical basis to review the design and identify questions instead of relying on assumptions.
For an Austin or Central Texas project, coordinate drawing reviews, delivery planning, receiving constraints, and the integrator’s schedule with the project team; equipment can ship nationwide, but timing is determined by the project. Ask for confirmation of proposed metering devices, available data points, alarm behavior, communications interfaces, applicable standards, and any exclusions. Then route the submittals through the qualified engineer and relevant authorities. A documented interface and acceptance plan is the clearest next step toward monitoring that operators can interpret and use.
Project specification checklist
Use this checklist to organize the details for a project-specific review. Final ratings, applicable standards and equipment selections depend on the approved design.
| Item | What to confirm |
|---|---|
| Metering schedule | Confirm measurement locations, required values, units, intended use, and measurement accuracy needs. |
| Alarm matrix | Define monitored conditions, priorities, thresholds or logic, routing, and expected operator response. |
| Communications interface | Verify protocols, supported points, network boundaries, addressing, gateways, and integration responsibilities. |
| Operational data conventions | Establish point names, timestamps, event handling, data destination, and reporting or retention needs. |
| Design and acceptance review | Reconcile one-line diagrams and interface documents; agree on project-appropriate checks and acceptance ownership. |