Power distribution, with purpose.
A utility distribution protection interface is the point where a switchboard or other distribution assembly must work with the utility’s protective devices, operating practices, and communications—not just carry load. A sound review starts with verified system data and clear responsibility for settings and approvals. This guide outlines the inputs and decisions a purchaser should assemble before requesting a new equipment quote.
Define the boundary before selecting equipment
Start by marking the ownership and protection boundary on a one-line diagram. Identify the utility service point, metering arrangement, service disconnect, bus sections, feeders, tie breakers, and any customer-owned generation or alternate source. The drawing should show which devices can interrupt each source of fault current and whether a transfer scheme can connect sources in an unusual operating state. This prevents a common coordination gap: reviewing the normal utility-fed arrangement while overlooking a generator-fed or closed-tie condition.
State the system nominal voltage and the required equipment maximum voltage as separate specification items. Also identify phase, frequency, grounding method, continuous current, and the available fault current at the point where the assembly connects. A nominal system voltage does not, by itself, establish the equipment rating. Short-circuit ratings and interrupting capabilities must suit the actual system and configuration, and the applicable standards must be confirmed for the specific order. Low-voltage switchboards may be specified as UL 891 assemblies where applicable; UL 891 is not a general listing for medium-voltage gear.
Gather relay and fault-study inputs
For each utility or customer protective device that affects coordination, request the device type, current-transformer ratios, sensing inputs, existing settings or approved setting ranges, trip outputs, and time-current curves. Clarify whether settings are fixed, utility-controlled, or subject to review before energization. Relay functions, zones of protection, trip-circuit supervision, lockout behavior, and breaker failure logic can all affect how the interface is built and tested. Do not assume that a relay model or function is available in a proposed assembly until its compatibility and procurement are confirmed.
Obtain the latest utility fault-current data, including the method and point of reference, and ask whether minimum and maximum source conditions are available. The review may also need transformer impedance, conductor data, motor contribution, generation behavior, and alternate-feed conditions. These inputs affect interrupting duty, bus bracing, protective-device selection, and coordination margins. If values are preliminary, identify them as such and have the responsible engineer determine whether a conservative assumption is appropriate; a guessed fault level is not a substitute for utility confirmation.

Treat communications as a protection interface
Document what information must cross the switchgear boundary and why. A utility may require status, alarms, metering, remote trip, or permissive signals, while the customer may need relay events or breaker position at a supervisory system. Specify the intended protocol, physical medium, point list, time synchronization method, and who supplies gateways, network switches, fiber, and control power. Where communications participate in tripping or interlocking, define the fail-safe state and the behavior during loss of channel, power, or remote control.
Separate protection-critical functions from monitoring and convenience signals. A communications link used only for indication has different reliability and review implications from one that enables a transfer, blocks a trip, or sends a direct transfer trip. The utility and customer controls teams should confirm interface diagrams, contact conventions, signal voltage, isolation, and cybersecurity or access requirements before design release. Protocol support, relay options, and component availability are order-specific; a stated communications requirement should not be taken as confirmation that a particular device or configuration is offered.
Coordinate stakeholders and approval boundaries
The purchaser should identify who owns each decision: the serving utility, facility electrical engineer, protection engineer, controls integrator, equipment manufacturer, and commissioning or testing provider. The utility may determine service rules, metering, acceptable relaying, and permission to connect. The engineer of record should establish the protection basis and evaluate coordination. The manufacturer can use approved drawings and specifications to develop the new assembly, but should not be presumed to set utility relay values, approve a protection study, or authorize service.
Set formal review gates for the one-line diagram, relay and communications interface, equipment submittals, and final settings documentation. Record who resolves comments and who has authority to approve deviations. A purchase order should not silently replace utility requirements or an engineer’s stamped design. Likewise, equipment acceptance does not itself mean that the utility has approved the connection or that field settings have been validated. Confirm the required inspections, testing scope, and turnover documents with the parties responsible for those activities.
Use a scenario to expose missing assumptions
Consider a hypothetical commercial facility in the Dallas–Fort Worth area adding a second utility-fed bus section and a standby generator. The initial request describes the service voltage, main-breaker current, and generator size, but leaves the tie-breaker operating scheme and utility maximum fault current unresolved. That is not enough to settle breaker duties or protection interfaces. The review should ask whether the tie can close with both sources present, whether a transfer is open-transition or closed-transition, and which authority approves any parallel operation.
In that example, the team would also need the generator subtransient data, transformer impedances, relay and breaker information, and communications requirements for any transfer permissive or trip signal. If the utility has not supplied fault data or an approved protection interface, those items should remain explicit engineering hold points rather than being filled in by assumption. The scenario is illustrative only, not a completed project or a claim about a particular utility’s requirements. Regional service practices vary, so the serving utility must confirm its own criteria.
Prepare a quote package and compare tradeoffs
For a useful quote request, provide the current one-line and site-specific specifications, verified service data, fault-study basis, protection and communications requirements, operating sequence, required drawings, and known utility comments. Include the requested enclosure and environmental conditions, access and cable-entry constraints, metering provisions, and any required documentation or witness testing. Identify assumptions, unresolved inputs, requested delivery timing, and the project decision-maker. This helps evaluate a custom new assembly against the actual interface rather than a generic equipment description.
Selection tradeoffs may include integrated controls versus separate interface panels, a simpler hardwired scheme versus networked monitoring, and a compact arrangement versus service access and future expansion. Each option affects engineering effort, component availability, testing, and coordination responsibility. The manufacturer builds and supplies new equipment using American components as applicable and can make shorter lead time a goal, but availability, US-origin requirements, ratings, standards, and timing must be confirmed for the order. Any proposed configuration remains subject to engineering review and utility approval.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Information to confirm |
|---|---|
| Fault duty | Utility source data, reference point, and operating cases |
| Protection | Relay functions, CT ratios, curves, settings authority, and trip logic |
| Communications | Protocol, signal list, media, control power, and failure behavior |
| Approval boundary | Utility criteria, engineer review, and documented approval owners |
