Power distribution, with purpose.
Hardwired switchgear interlocks use electrical circuits and mechanical blocking features to prevent specified operations unless required conditions are met. Their value depends on precise source-state definitions, documented permissives, and tests tied to the actual one-line diagram and operating sequence—not on an assumed guarantee that an interlock will prevent every unsafe action.
Define the operating sequence before selecting interlocks
Start with the switching actions the design must permit or inhibit. A two-source arrangement, for example, may allow a tie breaker to close only when a particular source breaker is open, or it may require a different sequence when automatic transfer is included. State whether sources can operate in parallel, whether transfer is open-transition only, and how bypass, maintenance, or emergency operating modes change the rules. “Prevent paralleling” is not a complete requirement until the permitted states and exceptions are explicit.
The purchaser should provide the current one-line diagram, breaker and disconnect schedules, intended operating sequence, source and tie relationships, and any control schematics or protection narratives that establish relevant states. Identify who has authority to select operating modes and whether local and remote controls must follow identical permissives. These inputs let engineering evaluate the requested logic and identify conflicts; they do not substitute for approval by the responsible design professional or facility authority.
Separate electrical permissives from mechanical blocking
An electrical interlock commonly uses auxiliary contacts, control relays, and wiring to allow or inhibit a control command. A permissive may depend on a breaker’s open indication, a disconnect position, a control-power condition, or another defined input. The specification should say which contact state represents each condition, how the signal is supervised, and what the control circuit does if an input is missing or contradictory. A pilot light or status point can report a state, but indication alone does not establish an interlock.
Mechanical interlocks physically constrain selected operations and may provide a different layer of protection where the equipment arrangement supports it. They can limit flexibility, add operating steps, and depend on compatible devices and enclosure geometry. Electrical logic can accommodate more conditional sequences, but its behavior relies on wiring, control power, contact integrity, and correct interpretation of indications. Whether either method—or a combination—is appropriate must be reviewed against the actual equipment and applicable project requirements.

Make source states and abnormal conditions explicit
A breaker position is not necessarily proof that a source is available, isolated, or safe for a requested operation. Specify the states the logic uses, such as breaker open or closed, drawout position where applicable, source-present indication, control-power healthy, and any approved mode selection. Define whether voltage sensing or protection-relay status participates in a permissive, who supplies those signals, and what happens when status is unavailable. Do not treat a single auxiliary contact as conclusive evidence of every electrical condition.
Review failure scenarios as requirements to evaluate and test, not as outcomes the manufacturer can promise in advance. Consider loss of control power, a failed or misadjusted auxiliary contact, broken wiring, conflicting indications, a stuck relay, an unintended mode selection, and a manual operation that bypasses normal control. Decide which conditions should block operation, which should alarm, and what fallback is acceptable. Fail-safe behavior is not one universal design rule; blocking a command can itself have operational consequences that the project team must assess.
Specify interfaces, ownership, and design records
Interlocks often cross equipment boundaries. Identify whether signals come from another switchboard section, a utility source, a generator controller, a transfer scheme, or a protection relay supplied by another party. For each interface, document the signal name, normal and abnormal states, contact form or approved interface method, control-voltage basis, terminal responsibility, and party responsible for wiring and verification. Coordinate remote commands and supervisory controls so that software, external contacts, and local hardwired logic do not impose incompatible sequences.
Useful project outputs may include an interlock matrix or truth table, revised elementary and connection diagrams, terminal plans, device and contact schedules, and a sequence narrative showing allowed and blocked operations. Record assumptions, exclusions, and unresolved interface points on those documents. For a custom build, the purchaser should identify drawing review and approval responsibilities, required revisions, and the information needed from other equipment suppliers. The specific documents and engineering scope should be confirmed before quotation.
Turn the logic into project-specific acceptance tests
A test plan should trace each required permissive and prohibited operation to a stated expected result. Define which input combinations will be simulated, how local and remote commands will be checked, what indications or alarms must appear, and how abnormal or contradictory inputs will be represented. Include relevant operating modes and control-power-loss behavior. The scope should state whether testing is limited to shop verification of the supplied assembly or also requires coordinated testing with external equipment at the project site.
Test boundaries matter: a switchboard test cannot by itself verify an external relay, field wiring, source-sensing device, generator controller, or complete facility transfer sequence unless those items are included and available for the test. Agree on test records, witness requirements, exception handling, and responsibility for final system validation. Requirements and acceptance criteria should be reviewed by the project engineer and confirmed for the ordered configuration rather than inferred from a generic interlock description.
Prepare a quote request with configuration details
For a useful quotation, submit the one-line diagram, equipment lineup and breaker information, control voltage, desired operating sequences, interlock matrix if available, interface points, applicable project specifications, and expected drawing and test deliverables. Note whether the request involves new low-voltage switchboard equipment, replacement sections, or integration with equipment supplied by others. Ratings, short-circuit requirements, components, standards, and any U.S.-origin requirements must be reviewed and confirmed for the particular order.
A manufacturer serving Dallas–Fort Worth and shipping nationwide can review a documented application for a custom new-equipment build; service area does not imply a local factory or installation scope. UL 891 applies to low-voltage switchboards, not to medium-voltage switchgear generally, and applicability or listed status must be verified for the specific assembly. Lead time may be a planning goal, not a guarantee, because approved drawings, component availability, and scope affect schedule. Confirm capabilities, responsibilities, and requirements before release.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | What to define for engineering review |
|---|---|
| Source-state logic | Required and conflicting states for each switching command |
| Interlock method | Electrical, mechanical, or combined approach; subject to equipment review |
| Interfaces | Signal ownership, normal state, control basis, and wiring boundary |
| Acceptance evidence | Project-specific test cases, records, and witness expectations |
