Power distribution, with purpose.
Protection and control engineering turns operating requirements into decisions the switchgear can make—and signals operators can understand. For a new switchgear order, relay functions, control power, interlocks, and functional sequences should be defined together, then checked against the one-line diagram, equipment ratings, and site interfaces. These services and deliverables should be treated as proposed until the manufacturer confirms its capabilities and the project team approves the scope.
Start with protection intent and system data
Relay selection begins with the protection objective, not a preferred catalog model. The design team needs the one-line diagram, system nominal voltage, available fault-current information, grounding method, transformer and motor data where applicable, and the upstream and downstream protective-device details. Those inputs help establish which faults must be detected, which equipment should be isolated, and where coordination with other devices matters. System nominal voltage is not the same as an equipment maximum rating; both the switchgear rating and its short-circuit capability require confirmation for the specific order.
A purchaser should identify required protection functions, preferred relay families if specified, communications protocols, metering needs, event records, and any owner standards. Settings are not safely inferred from a generic application description: they depend on the actual system study and approved operating criteria. If those studies are not complete, the quote and design review should mark assumptions and identify who will provide or approve final settings. This reduces the risk of designing around provisional fault levels or conflicting coordination expectations.
Define control power and operating boundaries
Control power determines whether relays, trip and close circuits, indication, communications, and auxiliary devices can perform their assigned functions. Specify the source and nominal control voltage, AC or DC characteristics, grounding or isolation expectations, and whether a station battery, control transformer, or other source is intended. The design also needs to account for voltage variation, circuit protection, and what remains available during loss of normal power. Component availability and the final circuit arrangement must be confirmed for the particular build.
Control interfaces extend beyond the switchgear lineup. Identify hardwired status and command points, remote I/O, supervisory control connections, terminal requirements, cable entry and routing constraints, and the party responsible for field wiring. Clarify whether remote commands are permitted, what local controls take precedence, and which signals must be fail-safe or alarmed. A point list and interface drawing provide a concrete review basis; vague language such as “SCADA ready” does not define the signals, protocol, or responsibility split.

Make interlocks explicit and reviewable
Interlocks prevent an operation when a stated condition is not satisfied, but their purpose and boundaries must be clear. Specify mechanical, electrical, key-operated, or logic-based interlocking as applicable, including the devices involved and the prohibited operating combinations. For example, a transfer arrangement may require defined source and tie-breaker conditions, while a drawout device may have position-dependent permissives. Such examples are illustrative only; the actual design requires engineering review against the equipment configuration and operating philosophy.
Review interlocks for both safety and maintainability. An interlock that is too permissive can allow an unintended state, while one that is too restrictive can block an authorized operating or maintenance sequence. The project team should confirm whether bypasses are allowed, how they are controlled and indicated, and what happens after loss of control power or communications. Drawings should show the logic and device references clearly enough for the owner to verify that the intended operating boundary is preserved.
Translate operating intent into functional sequences
A functional sequence describes what the equipment should do in normal operation, during a fault, and when an operator requests a change of state. Define initiating conditions, permissives, expected breaker or contactor actions, alarms, time delays, and the response to failed or missing feedback. State whether automatic retransfer, load shedding, or other automatic action is required, prohibited, or outside the switchgear scope. These decisions affect relay logic, wiring, operator indications, and test planning, so they belong in a reviewed sequence rather than being left to interpretation during assembly.
Sequence documents should distinguish command, status, and trip functions, and identify the source of each input. Include expected behavior for simultaneous commands, stale or invalid communications, device disagreement, and restoration after control-power interruption where relevant. The owner’s operating personnel and protection engineer should review the sequence for practical usability and system coordination. A sequence approved for one system configuration should not be assumed to apply unchanged after a revision to the one-line diagram or control philosophy.
Set deliverables, inspection handoffs, and approval gates
A proposed engineering package may include relay and control schematics, elementary diagrams, terminal plans, point lists, device schedules, logic or sequence documents, and a settings record when included in scope. The exact deliverables must be agreed for the order; their availability should not be presented as a verified in-house capability before confirmation. For low-voltage switchboards, UL 891 may apply to the assembly when applicable and confirmed for the specific order. It is not a general listing for medium-voltage switchgear, and ratings, standards, and any U.S.-origin requirements must be reviewed product by product.
Inspection and test handoffs should connect approved documents to observable results. The project plan can identify drawing-review release, wiring checks, point-to-point verification, functional demonstrations, and the records required before shipment, subject to the agreed scope and equipment. The purchaser’s approval role is essential: review drawings, resolve comments, approve operating sequences and interface assignments, and provide final settings or designate their responsible engineer. Approval should not be treated as a substitute for the manufacturer’s checks or for site-specific commissioning by qualified personnel.
Prepare a quote package that limits assumptions
For a useful quote, provide the latest one-line diagram, equipment schedule, system and fault data available, protection philosophy, control-power source, operating sequence, and applicable owner specifications. Include relay preferences, communication requirements, I/O lists, wiring and terminal conventions, environmental conditions, and the required drawing and test submittals. Flag unresolved items rather than silently treating them as settled. The manufacturer can then identify the information needed to confirm component selection, engineering scope, assembly details, and a shorter lead time as a goal rather than a guarantee.
Customers in Dallas–Fort Worth and elsewhere can use the same document-led review process; service to a region does not establish a local manufacturing facility or project history. The manufacturer builds and supplies new equipment, with custom builds and American components subject to order-specific confirmation. Before release, align the final diagrams, ratings, settings responsibilities, standards, and inspection plan. That shared approval record helps keep protection intent, control wiring, and the delivered configuration tied to the same accepted design.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Decision to document |
|---|---|
| Protection basis | System data, fault study status, required functions, and settings responsibility |
| Control power | Source, nominal voltage, circuit needs, and behavior during source loss |
| Operating logic | Interlock boundaries, permissives, sequence, alarms, and failure response |
| Project handoff | Drawing approvals, agreed inspection records, and purchaser sign-off points |
