Prove the Control Logic Against the Test Plan
Control functional testing checks whether new switchgear control circuits behave as the approved project documents require. Rather than treating a control diagram as proof of operation, the test plan defines the expected sequence, the conditions that permit or block each action, and the indications associated with those states. The intent is to find mismatches among design, wiring, devices, and operating logic while they can be addressed within the project process.
Testing scope depends on the assembly and its specified functions. A plan may cover local controls, remote commands, status points, alarms, and permissive or blocking logic, but none should be assumed standard for every lineup. The project team should agree which functions are included, what constitutes a pass, how exceptions are recorded, and who reviews results. Qualified electrical professionals should evaluate requirements and applicable standards for the particular design.
Start With Approved Documents and Operating Intent
Useful inputs include the latest approved one-line diagram, elementary and wiring diagrams, control schematic, equipment schedule, sequence of operation, I/O list, and the test plan. Include approved revisions and identify documents that remain under review; otherwise, a test may validate an obsolete arrangement. Device descriptions and terminal plans help connect the intended logic to the installed control components and wiring.
The operating narrative should make normal and abnormal states understandable. Confirm which source, breaker, tie, or other device combinations are intended, what conditions must exist before an action, and what happens when a command is unavailable or a condition changes. The design team should resolve unclear or conflicting instructions before testing, rather than having a tester infer the intended behavior. Project-specific ratings, control power, and device selections also require review against the application.
Define Sequences, Permissives, and Interlocks
A sequence describes the expected order and conditions for operations; an interlock prevents an action when a specified condition is not satisfied. The test plan should translate each requirement into observable steps: establish a defined initial condition, apply a command or simulated input, and compare the resulting device state and indication with the expected result. Include both permitted actions and intentionally blocked actions where those cases are part of the approved scope.
Interlock design choices are application-specific. Confirm whether logic is electrical, mechanical, or coordinated, and identify which devices and control circuits participate. Do not assume that a familiar arrangement or a prior project’s operating philosophy applies. Any required bypass, selector position, manual mode, or loss-of-control-power response should be documented with its intended behavior and approval path. Testing must follow the approved plan and safe procedures; it is not a reason to operate energized equipment without qualified authorization.
Check Indications and External Interfaces
Indications let operators and connected systems distinguish command, position, availability, alarm, and fault conditions. For each point in scope, confirm the source contact or signal, normal state, description, destination terminal, and expected presentation. A correct breaker response can still be accompanied by an incorrect status point, so tests should compare physical or simulated device state with local indication and the documented remote interface.
Coordinate control functional testing with the project’s protection, metering, supervisory-control, and communications requirements where those interfaces are included. Confirm responsibility for external signals, interface wiring, test equipment, protocol configuration, and point-to-point checks. Identify signals that will be simulated versus connected to external equipment, and agree how unavailable interfaces are handled. These decisions prevent an incomplete boundary between the switchgear package and other project systems from being mistaken for a verified end-to-end function.
Plan Test Conditions, Evidence, and Exceptions
A useful test plan names each function, required initial state, test action, expected response, acceptance criterion, and record to retain. It should identify the test configuration, the control power and inputs needed, and any temporary simulation or isolation measures permitted by the approved procedure. Test steps should be repeatable and traceable to document revisions, so reviewers can determine exactly what was verified.
Record results contemporaneously, including pass, fail, not tested, and any approved limitation. For a discrepancy, capture the observed behavior, the requirement it conflicts with, affected documents or interfaces, and disposition responsibility. Corrective work may require drawing updates or retesting related steps; closure should be documented rather than inferred from a component change. The project should establish who accepts test records and how unresolved items affect release, shipment, or later integration activities.
Coordinate Testing With Equipment Design and Procurement
Control testing is most effective when its scope is considered during design and procurement, not added after control details are fixed. Confirm that the proposed assembly’s devices, auxiliary contacts, control circuits, terminal access, and interface provisions align with the approved functional requirements. Custom assemblies can be developed to project specifications, but the sequence, signals, and interface boundaries must be sufficiently defined for design review and a meaningful test plan.
For new switchgear, coordinate control test milestones with drawing approval, design changes, production planning, and required customer review. Ask how revisions after approval are tracked and which functions need witness points or submitted evidence, if any are required by the project. Manufacturing in the USA, all-American components, nationwide shipping, and an aim for short lead times may inform procurement discussions; actual schedule depends on the project. UL 891 applies only to suitable switchboard assemblies, not automatically to every switchgear design.
Turn Findings Into Clear Project Decisions
Before requesting a proposal or finalizing a specification, provide the operating narrative, latest control documents, I/O and interface lists, required sequence scenarios, and preferred test evidence format. Identify who will approve logic, resolve exceptions, and accept records. Ask the manufacturer to clarify what control functions are included in the offered assembly and test scope, what inputs must be supplied by others, and what assumptions remain open. This gives the team a concrete basis for comparing scope without presuming a standard test capability.
After review, close decisions on operating modes, interlock intent, indication naming, external-system boundaries, simulated inputs, acceptance criteria, and revision control. Confirm applicable standards and design requirements with qualified electrical professionals and relevant authorities; applicability depends on the equipment and project. The resulting approved test plan should link each requirement to a test step and recorded outcome. That traceability gives designers, procurement teams, and reviewers a practical way to judge whether control functions were verified as specified.
Project specification checklist
Use this checklist to organize the details for a project-specific review. Final ratings, applicable standards and equipment selections depend on the approved design.
| Item | What to confirm |
|---|---|
| Functional basis | Confirm approved sequence of operation, control diagrams, revisions, and test-plan acceptance criteria. |
| Interlock scope | Identify participating devices, permissives, blocked actions, operating modes, and approved exceptions. |
| Indication points | Define each local or remote status, alarm, source signal, normal state, and destination interface. |
| Test conditions | Document initial states, simulated inputs, control-power requirements, and permitted test configuration. |
| Records and disposition | Agree on result format, discrepancy ownership, retest expectations, and approval of open items. |
| Applicable requirements | Verify equipment-specific ratings, standards, and any listing expectations for the actual assembly and project. |