Protection and controls advisory for large-load data center builds.
Guidance on the protection and controls side of data center power, from the utility service entrance through the critical bus — scheme review, coordination, SCADA and RTU architecture, and the documentation that gets a site to energization readiness.
Why data center protection is its own problem
Large-load interconnection is the fastest-growing category on the U.S. grid, and data centers are the reason. The electrical engineering is well understood; what makes these projects difficult is the combination of an extremely low tolerance for interruption with the redundancy required to deliver it.
Redundancy complicates protection. Dual utility feeds, tie breakers, UPS systems, and standby generation mean a bus can be fed from more than one direction, and which direction depends on the operating configuration at that moment. A coordination scheme that is selective in the normal configuration can lose selectivity in a maintenance or failover configuration — exactly when the facility can least afford it.
The protection question is therefore not "is this scheme selective," but "is this scheme selective in every configuration the site will actually operate in."
The utility side
A large-load service request is its own negotiation. The utility is assessing what the load does to their system at the service point: step-load and inrush behavior, protection and metering at the service entrance, and whether on-site generation or storage will ever operate in parallel with their system. Where it will, the project inherits interconnection requirements in addition to service requirements, and the two need to be answered as one coherent package rather than by two disconnected efforts.
Energization readiness
The gap that most often delays energization is documentation rather than construction: settings that do not match the drawings, drawings that do not match the field, or a utility requirement that was never explicitly closed out. Assembling that record deliberately, before the utility asks, is materially cheaper than assembling it under schedule pressure with equipment already on site.
Service entrance one-line convention.
One-line convention for a data center service entrance: main breaker (52), differential / bus relay (87), and switchgear bus configuration feeding UPS and mechanical buses, per typical utility submittal format. Reference only, not project-specific.
What we look at first
- Service entrance protection. Main device rating, interrupting duty against available fault current, and the relay functions protecting the incoming service.
- Bus differential zones. Where zone boundaries fall, and whether every fault location is inside a zone that will clear it quickly.
- Configuration coverage. Whether coordination holds under tie-closed, single-feed, and generator-supported operation as well as normal.
- Documentation state. Whether drawings, settings, and installed devices currently tell the same story.
Data center protection questions.
What makes data center power protection different from other large loads?
Two things: the tolerance for interruption is close to zero, and the redundancy that delivers that tolerance makes the protection scheme substantially more complex. A conventional industrial facility can often accept a radial service and a straightforward coordination chain. A data center's dual-path service, tie arrangements, UPS systems, and generator backup mean fault current can arrive at a bus from several directions and the coordination picture changes depending on which configuration the facility is running in.
Protection has to be selective in every one of those configurations, not just the normal one.
What does a large-load utility service request involve?
Beyond capacity, the utility is assessing what a large load does to their system: inrush and step-load behavior, the protection at the service entrance, metering arrangement, and increasingly whether on-site generation or storage will operate in parallel with their system. Where it does, the request carries interconnection requirements on top of the service requirements — see DG interconnection engineering.
Do you replace our EPC or engineer of record?
No. We work alongside them as the protection and controls specialist. The EPC or PE of record owns the design; we bring depth on the protection scheme, the coordination, the relay settings, and the utility-facing documentation. That division works well precisely because it is explicit — we define at the scope call which deliverables are ours and which route through your engineer of record.
What is involved in SCADA and RTU architecture planning?
Deciding what the protection and controls system needs to see, where those points originate, and how they get to the systems that use them. In practice that covers which relay and equipment points are monitored, how data moves from field devices to the monitoring system, what the utility requires visibility of at the service entrance, and how the architecture supports both operations and post-event analysis.
When should protection be brought into a data center build?
During preliminary design, alongside the utility service request. Protection scheme decisions constrain equipment selection — interrupting ratings, CT arrangements, relay capability, switchgear configuration — and reversing those decisions after procurement is expensive. It is also when the utility's own requirements for the service are still negotiable rather than fixed.
Related scope for large-load sites.
Building or energizing a large-load site?
Bring us in during preliminary design, while protection decisions still shape equipment selection rather than fight it.