NEW AMERICAN-MADE POWER DISTRIBUTIONSERVING DALLAS – FORT WORTH
Installed electrical panels and conduit in an equipment room
NEW EQUIPMENT FOR DALLAS–FORT WORTH

Fail-Safe Control Philosophy and Assumptions

Define fail-safe control behavior for switchgear by documenting source states, hardwired logic, communications failures, assumptions, and review needs.

MADE IN USAAmerican components
UL 891Switchboard assemblies
SHORT LEAD TIMESConfirm your project schedule
BUILT FOR YOUR PROJECT

Power distribution, with purpose.

A fail-safe control philosophy states what electrical distribution equipment should do when a source, control circuit, sensor, or communications link becomes unavailable or unreliable. It is not a universal setting or a promise that every failure will leave equipment energized. The safe response depends on the one-line design, operating intent, connected loads, and hazards of both action and inaction. Documenting those assumptions before switchgear is built gives the owner, designer, and manufacturer a common basis for reviewing controls.

Start with defined source and operating states

Describe each source by its role and observable conditions, rather than using “normal” and “emergency” as the whole control philosophy. Relevant inputs may include source-voltage sensing, breaker or switch position, a generator-ready contact, and an owner-defined permissive. Specify what constitutes a valid source, how long an abnormal condition must persist before action, and whether restoration requires stable voltage or operator confirmation. Distinguish a source that is electrically available from one that is authorized to carry the load.

State the allowed operating modes, such as normal, alternate-source operation, isolated, test, and manual control, and define which devices may operate in each. A transfer sequence that is appropriate for one load may be unacceptable for another. For example, a design may permit open-transition transfer but prohibit paralleling sources. The control narrative must make that boundary explicit, including what happens if a breaker fails to reach its commanded position or a source becomes unacceptable during transfer.

Treat hardwired logic as a deliberate design choice

Hardwired controls can provide direct interlocking or permissive paths independent of a supervisory network, but the phrase “hardwired” alone does not establish a safe failure response. Drawings should show the actual contact states, control-power source, protective devices, terminal points, and the conditions required to issue each command. Review whether a broken conductor, loss of control power, welded contact, or failed sensing relay would block operation, create a false permissive, or leave an existing state unchanged.

Choose the default behavior deliberately. De-energize-to-trip logic may be suitable for some protective or permissive functions, yet it can also cause unwanted interruption if a control conductor opens. Conversely, a circuit that retains a command after control-power loss may preserve service but delay a needed transition. The acceptable tradeoff depends on the equipment function and hazard analysis. Qualified design professionals should confirm the circuit architecture, protection coordination, settings, and work practices for the specific installation.

Illustrative close-up of copper busbars in a motor control panel
Illustrative industry photograph · ToT89 / Wikimedia Commons · resized · CC BY-SA 4.0

Define communication loss without confusing it with source loss

A communications interface may carry status, alarms, metering, remote commands, or control permissives. Specify which functions use the network and which remain local or hardwired. For each interface, identify the protocol and responsibility boundary, expected data points, command authority, and behavior on stale data, timeout, bad quality, or loss of link. A supervisory display that stops updating is not proof that the electrical source itself has failed.

Decide whether a communication failure should inhibit remote operation, preserve the last approved operating state, or initiate a separately defined local response. These options have different consequences: blocking remote commands can reduce the chance of action on uncertain data, while preserving local automatic control can maintain a transfer function independent of the network. Avoid allowing a network command to defeat a required electrical or mechanical interlock. The owner’s controls integrator and equipment designer should resolve interface ownership, testing responsibility, and how alarms distinguish communication trouble from equipment trouble.

Assemble the source data and test the assumptions

A useful design review begins with the current one-line diagram, equipment schedule, source and load information, protection and control schematics, and the intended sequence of operation. Supply nominal system voltage and frequency, grounding arrangement, source characteristics, breaker or switch functions, control-power details, fault-current information, and required interrupting or short-circuit ratings as applicable. Identify load priorities, motor or process restart constraints, generator limitations, and any no-parallel or no-break requirements. Ratings and component availability must be confirmed for the particular order.

Also provide interface documents that can change the control outcome: generator or UPS contacts, building-management or SCADA point lists, network-loss requirements, alarm destinations, and owner standards. A concise assumptions register should identify who supplies each signal, its normal and failed state, and who approves changes. For a new custom switchgear quote, purchasers should supply these documents along with the desired equipment scope, physical and connection constraints, applicable standards, and requested US-origin or component requirements. The manufacturer can review the proposed assembly scope; project-specific code interpretation and final control decisions remain with qualified professionals.

Compare responses with a hypothetical decision

Consider a hypothetical facility with a utility source, a standby generator, and an automatic transfer function. The owner wants local transfer logic to remain available if the supervisory network fails, but does not want remote commands issued on stale status. A documented choice could allow local source sensing and approved hardwired permissives to govern automatic transfer, while inhibiting remote transfer commands during a communications alarm and annunciating the alarm locally. This is an example for engineering review, not a recommendation for a particular installation.

Other options might inhibit all automatic transfers when communications are lost or permit both automatic and remote operation to continue. The first may avoid acting on uncertain supervisory data but can leave the load dependent on operator response; the second can preserve continuity but requires confidence that local control and interlocks remain effective. The decision should test cases such as a failed source-voltage signal, loss of control power, an unsuccessful breaker operation, and communications returning with outdated commands. A hazard and operating review determines which consequences are acceptable.

Preserve the decision in drawings and records

Capture the approved philosophy in a sequence of operation, control schematic, interconnection and terminal drawings, device and signal schedule, and interface responsibility matrix. Record source-state definitions, timers, permissives, lockouts, reset behavior, manual-mode authority, alarm meanings, and the response to each defined failure. Where a feature is not included, mark it as excluded rather than leaving the reader to infer that it exists. Use revision control so a later change to a generator contact or network point does not silently alter the intended failure behavior.

The conclusion is limited to the information reviewed and the equipment scope defined for that project. Field wiring, protective-device coordination, equipment ratings, applicable codes, standards, and owner requirements can change the result; final settings, commissioning tests, safe work practices, and code interpretation belong to qualified professionals. A manufacturer serving Dallas–Fort Worth and shipping nationwide can use a complete control narrative to evaluate a new custom assembly and work toward a shorter lead time, but schedule, component availability, UL 891 applicability for low-voltage switchboards, and any US-origin requirements must be confirmed for the specific order.

PROJECT CONSIDERATIONS

Specifications & planning

Review the details that matter for your application. Final specifications and availability should be confirmed for your project.

Controls: specifications and planning considerations
Evaluation factorWhat to define
Source stateSensing method, valid range, delay, and restoration criteria
Control-power failureExpected effect on permissives, commands, and existing state
Communications lossAffected functions, local fallback, alarm, and command inhibition
Approval recordSequence, schematics, interface ownership, and revision status
READY TO DISCUSS YOUR PROJECT?Let's build what's next.
Call (951) 403-5738
LET'S GET TO WORK

Power your next project
with confidence.

Talk through your switchgear and power distribution needs with our team.

Call (951) 403-5738
Request a Quote