Define the facility context before specifying points
Data center electrical distribution connects utility sources, generators or other backup sources, transfer equipment, distribution paths, and loads that support information technology and facility operations. Cooling and other mechanical systems can also represent significant electrical demand. The exact arrangement varies by project, so instrumentation and communications requirements should follow the engineered one-line diagram, operating sequences, and redundancy strategy—not a generic list of features.
Start by identifying which equipment operators need to observe, what decisions they must make, and which events require an alarm or record. A system intended to support capacity planning may need different information from one focused on source status or troubleshooting. Define operating modes, normal and abnormal conditions, and planned expansion phases with the owner, electrical engineer, controls team, and equipment suppliers.
Build a usable point list
A point list translates operational needs into equipment-specific requirements. It may identify measurements such as current, voltage, power, or energy where the selected design and metering devices support them. Status points could include breaker position, source availability, or an equipment alarm. Confirm each proposed point against the actual equipment configuration; do not assume every switchgear assembly provides every value or signal as standard.
For each point, specify its name, purpose, source device, units or state, expected destination, and whether it is required for monitoring, alarming, trending, or another defined function. State which values need local indication and which must be communicated to a supervisory system. Agree on naming conventions and alarm priorities early. Clear definitions reduce ambiguity during submittal review, controls programming, commissioning, and later maintenance.
Coordinate sources, capacity, and operating sequences
Source coordination is central to a data center specification. Document how normal and backup sources are expected to interact, which equipment indicates their status, and what operating sequences the responsible engineer has designed. Identify the status or measurement information needed to understand a transition or an unavailable source. Transfer and protection functions must be specified and engineered for the project; communications monitoring should not be treated as a substitute for those functions.
Capacity phasing also affects instrumentation. A facility may be built or expanded in stages, but future points, network capacity, metering provisions, and space or interface requirements should be identified only where the project design calls for them. Clarify which phase supplies each item and which assumptions remain provisional. This helps avoid treating an anticipated future configuration as an approved present requirement or assuming later expansion will be plug-and-play.
Specify protocols and network boundaries
List the required communications protocol, physical interface, connection location, and intended receiving system, then have the responsible controls and network teams confirm compatibility. Specify whether the equipment supplier provides a communications card, gateway, meter, or other interface, and who configures, addresses, tests, and documents it. A protocol name alone does not settle integration: supported data points, mapping, scaling, and behavior during loss of communication also require agreement.
Define cybersecurity boundaries with the owner’s network and security stakeholders. Establish which party approves network connections, access methods, segmentation, credentials, and change control under the project’s policies. Avoid assuming that a switchgear communications port is a complete cybersecurity solution or that it should connect directly to an enterprise network. Network architecture and controls implementation remain project-specific responsibilities.
Make maintainability part of the interface
Readable labels, consistent point names, accessible documentation, and clear alarm descriptions help qualified personnel understand what the system is reporting. Consider how operators will distinguish a device alarm from a communications failure, stale value, or normal change of state. Specify the records and configuration information the project requires at handover, including approved point mapping and interface details, and assign responsibility for keeping them current after changes.
Keep monitoring interfaces distinct from the electrical functions they observe. The design team should identify which indications are informational and which functions are implemented through engineered protection, control, or transfer equipment. Installation, testing, and maintenance belong to qualified personnel following applicable safety procedures. Project commissioning should follow the approved scope and procedures, with equipment-specific capabilities and test responsibilities confirmed before procurement.
Coordinate the service entrance and supplier scope
Service-entrance switchgear is one possible interface in a facility’s distribution arrangement, not a universal requirement or a complete description of the data center system. If it is in scope, provide the supplier with the relevant one-line, source information, equipment schedule, required metering and status points, communications interface, and project-defined ratings. The engineer must determine the design and applicable requirements for the specific installation.
Before requesting a proposal, distinguish equipment supplied by the manufacturer from owner-furnished devices, controls contractor work, network configuration, field wiring, and commissioning tasks. Ask who supplies each component, who connects it, and who verifies the resulting data path. Submit the protocol and point list with the equipment specification, and identify open decisions rather than leaving suppliers to infer control-system requirements.
Prepare a coordinated purchasing package
Useful purchasing information includes the approved one-line diagram, equipment schedules, source and load assumptions, project phases, operating sequence, point list, protocol and interface requirements, and named integration responsibilities. Include the applicable standards and listing requirements as determined for the actual equipment and design; do not assume a requirement applies to every assembly. Ask the engineer and owner to review these documents together before release.
South Carolina Switchgear Builders manufactures new switchgear and switchboards to specification, builds in the United States using all-American components, and ships nationwide. Configuration, availability, applicable listing, ratings, testing, delivery timing, and interface capabilities must be confirmed against the project requirements and supplied equipment; lead times depend on the order. A coordinated package lets the manufacturer assess the requested equipment while the project team retains clear responsibility for system design and integration.