New electrical distribution equipment, built around your projectServing Georgia
Three gray electrical switchgear cabinets on pallets, with a door swung open.

Testing

Switchgear Operational Sequence Testing

Operational sequence testing checks whether switchgear controls respond as the approved narrative intends—not just whether individual components operate. For Georgia engineers, contractors, and facilities teams, defining normal, alternate, and failure-state scenarios before testing helps surface ambiguities, align procurement with control requirements, and deliver useful records for commissioning and operations.

Made in USAUL 891 switchboard assemblies — low voltage onlyAccelerated lead times — confirm availability
Project-specific

Define the application and requirements.

Built in the USA

Discuss equipment and assembly options.

Schedule-aware

Confirm lead times for your order.

Start with the approved control narrative

A meaningful sequence test needs a controlled reference. The approved narrative should identify the normal source arrangement, permitted alternate configurations, transfer conditions, operator actions, alarms, and return-to-normal behavior. It should also state which conditions block a transfer or require a manual reset. If drawings, relay settings, and written sequences conflict, the test team should resolve the discrepancy with the responsible engineer before treating any interpretation as a pass criterion.

For a new assembly, provide the latest approved one-line diagram, elementary control diagrams, device and alarm lists, interlock descriptions, and sequence revisions with the quote request. Identify the switchboard or switchgear sections included, sources and tie devices involved, control power assumptions, and interfaces to external equipment. This lets the manufacturer determine a practical test scope and identify information gaps before they affect build documentation or schedule.

Define normal operation in observable steps

The normal-state scenario should describe the expected initial condition and each commanded or automatic action. Depending on the approved design, test points may include source availability indications, breaker or switch status, permissive checks, interlocks, control power, alarms, and the final lineup. Record what initiates each step, what indication confirms it, and what delay or condition must occur before the next action. Avoid assuming a particular transfer scheme where the project narrative has not specified one.

Agree on how results will be observed and recorded. A test sheet can map each narrative statement to an input, expected logic response, output, and observed indication, with room for pass, discrepancy, and disposition. Where a control circuit interfaces with customer-furnished relays, remote supervisory controls, or site wiring, identify the boundary clearly. Factory testing can verify the supplied assembly and agreed interfaces; it cannot establish behavior of equipment or wiring outside the test scope.

Exercise alternate states and transitions

Alternate operation is more than confirming that a second source can be selected. Test the conditions that permit or prevent the transition, the intended device sequence, required interlocks, annunciation, and the resulting configuration. Where the approved narrative includes manual transfer, automatic transfer, or a return sequence, treat each as a distinct scenario. Confirm whether the sequence is open transition, closed transition, or another arrangement only from approved project documents, since the control behavior and acceptance criteria depend on that choice.

Ask the engineer to define test conditions for source loss and restoration, unavailable controls, and any required operator intervention. If a scenario depends on external status contacts or simulated utility conditions, decide how those signals will be represented and who approves the method. Procurement teams should confirm that the quoted control scope includes the specified devices, wiring, logic, and documentation needed for the agreed scenarios rather than relying on a general statement that the equipment is tested.

Challenge failure states without guessing

Failure-state testing checks whether the sequence stops, alarms, or moves to an approved fallback when an expected condition is absent or abnormal. Examples may include a source not available, a breaker failing to reach the commanded position, control power loss, an interlock blocking operation, or conflicting status indications. These are scenario examples, not assumptions about a particular installation. The approved narrative must define the expected response, including whether the system holds its existing state, permits a manual action, or requires investigation and reset.

Testing should use an agreed method that controls risk and preserves equipment settings. Simulated inputs or test switches may be appropriate when specified, but the method, boundaries, and restoration checks must be reviewed by qualified personnel. Do not create live fault conditions or bypass protective functions simply to demonstrate a sequence. Record the stimulus, expected response, actual response, and any corrective action, then repeat affected steps after approved changes.

Set acceptance and procurement criteria

Before release, settle who approves the narrative, who witnesses testing, what constitutes a discrepancy, and how deviations are resolved. Specify whether the test is factory functional testing, a witnessed procedure, or part of a broader site commissioning plan. These are different scopes. The project team should also determine whether sequence changes after approval require revised drawings, settings, test procedures, and schedule review. A clearly bounded acceptance plan prevents an operational sequence test from being mistaken for a complete system study or site acceptance test.

For a quote, share the approved narrative and revision, relevant diagrams, source and tie arrangement, control-device schedule, required operating modes, failure cases, external interface assumptions, witness requirements, and preferred record format. Include project milestones and delivery destination in Georgia. We build new switchgear and switchboard assemblies in the United States, with custom configurations, American-made components, short lead-time planning, and nationwide shipping; exact scope, component availability, test arrangements, and timeline are confirmed for each order.

Make the handoff usable

A useful handoff gives commissioning and facilities personnel a traceable account of what was tested and under which approved revision. Provide the completed procedure, observed results, identified exceptions and dispositions, and any drawings or control documents revised during the process. Clearly distinguish factory observations from site checks still required, especially for utility signals, external controls, field wiring, and interfaces not present during factory testing. The responsible engineer and authority having jurisdiction determine applicable project acceptance and installation requirements.

Before requesting pricing, assemble the current control narrative, diagrams, desired normal and alternate modes, failure responses, interface boundaries, witness expectations, and Georgia delivery schedule. Ask the manufacturer to identify any assumptions or exclusions in the proposed test scope. Resolve those points with the project engineer before approval so the sequence can be tested against one agreed reference and the final records can support a clear commissioning handoff.

Planning reference

Project specifications

Specifications are confirmed for each order
ScopeRequested by quote
VoltageBased on project requirements
CurrentSpecified to order
ListingDependent on the applicable assembly. UL 891 applies to applicable low-voltage switchboard assemblies, not medium- or high-voltage equipment.
Request a Quote