Power distribution, with purpose.
Factory functional testing checks whether specified switchgear control functions respond as intended before equipment ships. The test plan should begin with approved drawings, control logic and clearly defined pass criteria—not assumptions about how a system will operate in the field. For buyers, a useful plan identifies which source states and control sequences will be simulated, which interfaces will be represented, what evidence will be recorded, and what remains for site commissioning. Proposed testing scope and capabilities must be confirmed for the specific order.
Define the source states and test boundaries
A source-state simulation represents the electrical conditions relevant to a control sequence without treating a factory functional test as a live-system demonstration. Depending on the approved design, test conditions may include normal source available, alternate source available, a source unavailable indication, or both sources unavailable. The specification should identify how each condition is represented, such as through control-circuit inputs or approved test interfaces, and whether indications are simulated or measured. It should also state which devices and assemblies are included in the test boundary.
This distinction matters for automatic transfer schemes, tie-breaker logic, generator interfaces and other arrangements where equipment behavior depends on external signals. A factory test can confirm the documented response to a simulated input; it cannot establish that an upstream protective device, generator controller, building automation system or field wiring will provide the correct signal. Buyers should identify those external dependencies and decide whether the factory scope will check only the switchgear-side interface or include defined interface testing using supplied devices or test equipment.
Translate the sequence into observable checks
The control narrative should describe each permitted state, transition and expected indication in language that can be turned into a test script. For example, a sequence may specify which source has priority, what conditions permit transfer, whether a delay applies, and what prevents a transfer or retransfer. The test plan should pair each input condition with an expected output or state, including breaker commands, status points, alarms and operator indications where included in the design. Ambiguous terms such as “automatic operation” are not sufficient pass criteria by themselves.
Interlocks deserve particular attention because they constrain actions rather than simply announce status. The approved logic and drawings should make clear which mechanical, electrical or control interlocks apply, what conditions block an operation, and how a blocked action is represented. Testing can confirm the response of the provided control scheme under specified simulated conditions, but it should not imply that every possible fault or misuse has been tested. The parties should agree on the test cases, exclusions and acceptance criteria before build completion to avoid disputes over unlisted behaviors.

Specify alarms, interfaces and failure indications
Alarm testing is most useful when each alarm has a defined source, destination and expected presentation. The project documents should identify whether the test covers local lights or displays, audible devices, relay contacts, network points, or a combination. They should also clarify signal names, normal and abnormal states, latching or reset behavior, and any time delay that affects an indication. A point-to-point check at the factory may verify a control-circuit response, while communication with a site network or third-party controller may require equipment, configuration files or access that are not part of the switchgear build.
Designers and purchasers should decide how unavailable, contradictory or out-of-range signals are represented in the test plan. A simulated source-loss input, for instance, can verify a programmed response but does not prove that the actual sensing device is correctly selected, installed or adjusted in the field. Interface boundaries should identify responsibility for furnished devices, wiring terminations, protocol mapping and final integration. When an interface is excluded, the record should say so plainly rather than allowing a factory test report to be mistaken for validation of the complete power system.
Agree on witness points and test records
A witness point is a planned opportunity for the purchaser or designated representative to observe an agreed test activity. The purchase specification should identify which tests are witnessed, which are reviewed from records, how much notice is required, and what happens if a witness cannot attend. Witnessing is not a substitute for defined acceptance criteria, and it does not automatically mean the witness approves items outside the stated scope. Whether witness testing can be supported, and its schedule and documentation, must be confirmed for the order.
Useful records connect each test case to a drawing revision, control narrative or approved sequence, identify the simulated inputs and observed outputs, and document results, exceptions and retests. Buyers should decide whether they need a signed checklist, marked-up sequence, alarm-point record or other deliverable, and in what format. Record detail affects preparation and review time; a concise functional checklist may suit a straightforward scheme, while complex source logic can require more traceability. Open deviations should be resolved or explicitly carried forward with an owner and disposition before shipment.
Separate factory function from field commissioning
Factory testing evaluates the equipment and control functions within the agreed factory test boundary under represented conditions. Field commissioning takes place after installation and addresses site-specific connections, settings, grounding, coordination with upstream and downstream equipment, and integration with external systems. A factory simulation does not verify shipping condition, installation quality, site wiring, actual source behavior, protective-device coordination or the complete end-to-end sequence at the installed location. Those activities require a separate commissioning scope by appropriately qualified personnel.
For projects in Dallas–Fort Worth or elsewhere, the same boundary question applies: what can be demonstrated before shipment, and what depends on the site? Owners should coordinate factory records with the commissioning plan so tests are complementary rather than assumed to be interchangeable. A clear handoff can identify factory-verified logic, field-only checks, required site signals and any settings that must be finalized after installation. No one should interpret a functional test record as authorization to operate or work on energized equipment.
Supply the information needed to quote the scope
A practical quote request includes the one-line diagram, control schematics or sequence narrative, equipment scope, source and breaker arrangement, interface list, required alarms, and applicable specifications. Include the preferred test boundary, expected record format, witness requirements, and any customer-furnished controllers or communication devices. If documents are preliminary, identify their revision and what remains unresolved. These inputs help establish whether the requested scenarios can be represented with the proposed design and what engineering coordination, fixtures or external interfaces may be needed.
Testing scope can affect engineering effort, schedule and the readiness date for review, so buyers should state which behaviors are mandatory and which are optional or subject to later definition. Custom-built equipment and shorter lead time as a goal do not remove the need for approved inputs or guarantee a test date. For a project requiring UL 891 low-voltage switchboard assemblies, identify that requirement in the procurement documents; it does not apply as a general listing for medium-voltage switchgear. Ratings, components, standards and U.S.-origin requirements must be confirmed for the specific order, along with the proposed functional-test capability.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Decision to document |
|---|---|
| Source-state simulation | Inputs represented and test boundary |
| Control sequence | Expected transitions, outputs and pass criteria |
| Alarms and interfaces | Points included, destinations and exclusions |
| Witness and records | Attendance, notice, report format and retests |
