Define What the Test Must Prove
A useful functional test begins with an approved control narrative, elementary diagrams, and an I/O or point list. These documents establish expected behavior for each command and indication. The test should verify those defined behaviors, not substitute an informal demonstration for design review or commissioning.
Decide whether the scope covers factory wiring and device operation, an integrated control scheme, or both. Identify acceptance criteria, witness requirements, records, and any customer procedures. The responsible engineer should resolve ambiguous logic and confirm that test steps match the current drawing revision.
Match Scenarios to the Equipment Configuration
The test plan depends on the supplied assembly: breaker arrangement, control power, local or remote controls, protective relays, metering, and communications interfaces all affect what can be exercised. Confirm which devices and functions are included in the new equipment and which depend on customer-furnished systems.
For low-voltage assemblies, distinguish a UL 891 switchboard from UL 1558 low-voltage switchgear when defining construction and operating arrangements. Medium-voltage equipment requires its own applicable design and test scope. Neither control testing nor a functional checklist changes the equipment’s standard or establishes a listing.
Exercise Interlocks and Permissives
Write scenarios for permitted and blocked operations. For example, verify that a closing command is accepted only when the specified permissives are satisfied, and that an intended mechanical or electrical interlock prevents an incompatible operation. Document the control states that create each result rather than relying on assumptions.
Where drawout devices, transfer schemes, grounding provisions, or source interlocks are involved, confirm the actual design and safe test method first. Some conditions may require simulated inputs or a controlled setup. Confirm test boundaries, bypass controls, and restoration steps with the responsible engineer before execution.
Verify Status Indications and Feedback
Check that local indicators, mimic displays, remote contacts, and communication points correspond to the intended device state. Scenarios can include open, closed, tripped, test, connected, or not-available indications where those states exist in the supplied configuration. Record both the initiating action and observed feedback.
Define signal polarity, contact form, naming, and destination for each point, especially when the customer’s PLC, SCADA, or building system is involved. A lamp check alone does not prove an end-to-end signal path. State whether external interfaces are simulated, connected, or excluded from factory testing.
Test Trip Commands and Protective Logic
Separate a control-system trip command from primary fault interruption. A functional scenario may verify that a relay output or remote command operates the intended trip circuit and produces the specified status change. It does not, by itself, demonstrate interrupting capacity or prove protective coordination.
Identify the relay model, settings source, trip-circuit arrangement, control voltage, and test method needed for the scope. Confirm whether test switches, secondary injection, or simulated inputs are specified. Protection settings and coordination remain subject to review by the responsible engineer and applicable project requirements.
Prove Sequences in Their Intended Order
For automatic or manual transfer, load-shedding, or restart sequences, list each initiating condition, delay, permissive, command, and expected final state. Test normal transitions as well as defined failure responses, such as a source not becoming available or a commanded device failing to change state.
Sequence timing and behavior must follow approved logic, not generic assumptions about facility operation. Confirm which timers are adjustable, whether external source signals are simulated, and what constitutes a pass. If multiple controllers or relays coordinate actions, specify their interface and revision-controlled logic.
Set Safe, Repeatable Test Conditions
Factory functional checks should use controlled conditions that do not expose personnel or equipment to unintended energization. Determine whether control power is applied, primary circuits remain isolated, and any outputs are safely contained. The approved procedure should identify hazards, responsible personnel, test instruments, and stop conditions.
Some functions cannot be fully proven without site devices, utility signals, or connected loads. Mark those as customer-site or commissioning checks rather than implying they were completed at the factory. Coordinate boundaries with the contractor, utility, and authority having jurisdiction when their systems or approvals are involved.
Specify Scope for a Manufacturing Quote
For a useful quote, provide the one-line diagram, control schematics, sequence narrative, device and relay schedules, required standards, and current revisions. Include the equipment type, voltage class, breaker arrangement, control voltage, communication interfaces, and any customer-furnished devices that affect functional scenarios.
Also state requested witness points, documentation format, acceptance criteria, test exclusions, and whether integrated external systems must be represented. The U.S. manufacturer can review these requirements for custom fabrication and nationwide shipment of new equipment; final design details should be checked by the responsible engineer and, where applicable, the utility and AHJ.