Power distribution, with purpose.
Breaker control circuits turn operating intent and protective action into defined electrical signals, then report what the breaker actually did. A useful control schematic makes the path from open or close command to breaker response clear, including permissives, trip-circuit supervision, position contacts, selector switches, and alarms. For new switchgear, these details should be settled alongside the one-line diagram and protection requirements, not left as assumptions during assembly.
Trace open and close commands from source to breaker
A control drawing should show where control power originates, how it is protected, and how it reaches each operating coil. An open command may come from a local pushbutton, a remote control system, a protective relay, or more than one of these sources. A close command commonly passes through a different set of conditions, such as a local/remote selector, anti-pumping logic, and required permissive contacts. The schematic should identify terminal points and distinguish command wiring from the breaker’s internal wiring and field connections.
The purchaser should specify the intended control-power source and voltage, the command sources, and whether close operation must be blocked under particular conditions. A design decision is whether control power is supplied by the switchgear or by the site, and how loss of that supply is to be indicated. DC and AC control systems have different component and supervision considerations; neither should be assumed from the nominal system voltage. Coil ratings, fuse or circuit-breaker selection, and available control power must be confirmed for the specific order.
Design trip paths for protection and dependable operation
The trip circuit connects protective action to the breaker’s opening mechanism. A schematic should make clear which relays or external inputs can initiate a trip, whether more than one trip coil or trip path is required, and how the circuit is isolated and protected. Where trip-circuit supervision is specified, its alarm logic should reflect what the circuit can actually detect; an indication of control-power availability alone does not necessarily prove that every trip-path component is functional.
Coordination with the protection engineer is essential where a breaker serves multiple trip sources, lockout functions, or interlocks. Specify required trip behavior, reset expectations, and whether an alarm or event indication is needed when a trip occurs. Avoid treating a generic control diagram as proof of a particular protection scheme. Relay functions, breaker accessories, short-circuit ratings, and the interfaces to upstream or downstream equipment all require project-specific review.

Make breaker status and indications unambiguous
Status indications should be tied to defined breaker auxiliary contacts rather than inferred solely from the presence or absence of a command. Open and closed indications may use separate contacts, while spring-charged, ready-to-close, or mechanism trouble points can provide additional operating context when the selected breaker supports them. The drawing should state contact designations and terminal references so that panel lamps, remote input points, and wiring schedules agree.
A purchaser should identify which indications are needed locally and which must be sent to a supervisory control system, relay, or building automation interface. Contact form, quantity, voltage, current, isolation, and whether contacts are spare or assigned affect the design. It is also important to define signal behavior during control-power loss and how alarms are reset or latched. The final point list and schematic should use the same names as the project’s control-system documentation.
Set local and remote authority deliberately
A local/remote selector determines which command source is enabled, but the exact authority arrangement is a project choice. A simple selector may block remote commands in local mode, while other schemes preserve protective trips regardless of selector position. The schematic should show these relationships explicitly, including any lockout, test, or maintenance position and the status contact that reports the selected mode. Protection trips should not be unintentionally disabled by a control-source selection.
The tradeoff is between straightforward operation and the additional wiring, contacts, and logic needed for permissives or command arbitration. Specify who may issue commands, whether remote close is allowed after a trip, and whether a local close requires a separate reset or ready condition. For a Dallas–Fort Worth facility or a site elsewhere, remote operating conventions and control-system interfaces should be confirmed with the owner; serving a region does not establish the site’s operating philosophy.
Define alarms, interlocks, and interface boundaries
Alarm indications are most useful when each one names a condition the control circuit can reliably detect. Examples for engineering review include control-power failure, trip-circuit trouble, breaker disagreement, or a failure to reach the commanded state within a specified interval. Each point needs an agreed source, normally energized or normally de-energized behavior where relevant, and a destination such as a local annunciator or remote input. Avoid combining unrelated conditions into one alarm if operators need to distinguish their causes.
Interlocks may depend on breaker position, equipment configuration, or external process signals. The control schematic should identify which contacts are provided within the assembly and which must arrive as field inputs, along with terminal blocks and responsibility for the external wiring. This page describes design considerations, not a promise that a particular logic package or interface is included. Confirm scope, applicable standards, component availability, and any required U.S.-origin content for the specific project.
Provide quote inputs and verify drawing deliverables
For a useful quote, provide the one-line diagram, breaker type and application, control-power source and voltage, desired open and close command sources, selector philosophy, required trip sources, and the list of local and remote indications. Include relay and control-system interface details, preferred terminal conventions, applicable project specifications, and any required sequence or permissive descriptions. Identify whether the scope is a new low-voltage switchboard, medium-voltage equipment, or another assembly; ratings and standards differ by equipment class.
Expected engineering records may include control schematics, elementary diagrams, connection diagrams, terminal plans, and a point list, subject to the agreed scope and review process. Purchasers should check that drawing revisions, wire and terminal references, and signal names align with the project documents before release. Custom new-equipment builds and American components may be considered where suitable; shorter lead time is a goal, not a guarantee. UL 891 applies to low-voltage switchboards when applicable, not medium-voltage breaker control equipment, and ratings and compliance must be confirmed for each order.
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 |
|---|---|
| Control power | Source, voltage, protection, and loss-of-power indication |
| Command authority | Local and remote sources, selector behavior, and close permissives |
| Protection and status | Trip sources, auxiliary contacts, alarms, and required remote points |
| Documentation | Schematic, terminal plan, point list, and review responsibility |
