TECHNICAL GUIDES / MANUFACTURER DIRECT
Control Sequence Test Planning turns an approved operating narrative into observable, documented checks before equipment testing begins. For buyers planning new switchgear, the key is to define what each control state should do, what conditions trigger a change, and what evidence counts as a pass. Switchgear Builder Virginia can build custom equipment to project requirements, with schedules and ratings confirmed by quote and review. Use the plan to align the sequence, drawings, test boundaries, witness roles, and sign-off before testing is scheduled.
Set the test basis
Start with the approved control sequence, current one-line diagram, schematics, equipment schedules, and project specifications. Record document revisions so the test team is not comparing behavior against an outdated narrative. Break the sequence into individual actions: initiating condition, expected response, timing requirement if specified, indication, and reset or next state. Identify which devices and interfaces are included, such as controls supplied with the switchgear, customer-provided signals, or connections to a building or supervisory system. Do not assume an interface, interlock, alarm, or automatic transfer function is included merely because it appears in a general example. Confirm the supplied scope and available test access against approved submittals. For applicable low-voltage switchboards, verify whether UL 891 requirements apply to the assembly; that designation does not establish a particular control sequence or prove a project-specific test has passed.
Define normal states
Write normal-operation cases as clear starting conditions and expected outcomes, not broad statements such as “system operates normally.” Specify the source or operating mode selected, the permitted control inputs, the indications expected at each relevant point, and the conditions under which the case is complete. If a project includes multiple sources or transfer logic, describe each approved state and transition separately, including any required operator action. Treat timing limits, permissives, alarms, and remote status points as values or functions to verify against the approved documents, not assumptions to fill in during testing. A useful case lets the witness observe whether the intended response occurred without relying on undocumented behavior. Where an outcome depends on external equipment or a customer system, identify the dependency and agree how it will be represented or confirmed within the defined test boundary.
Exercise failure states
List failure cases from the approved sequence and project risk review, then define the safe, expected response for each. Examples to consider, only where applicable to the design, include loss of a control-power source, unavailable or abnormal source status, a failed-to-operate indication, or a communication interruption. State the initiating condition, expected device response, alarms or status changes, any inhibited transition, and how the test ends. Distinguish a simulated input from an actual fault; the test procedure should specify an approved method and responsible party, rather than inviting improvised fault creation. Check that an abnormal condition does not cause an unintended command or obscure the status needed to assess the result. If a failure case cannot be safely or meaningfully demonstrated within the agreed boundary, document an alternative evidence method and obtain project-team approval before testing.
Plan restoration checks
A recovery case confirms more than whether normal status returns. Define how the initiating condition is cleared, whether reset or operator acknowledgment is required, which state should follow, and what indications must be checked. Where automatic return, manual retransfer, or a delayed action is specified, use the approved sequence and verified settings to define the expected result; do not assume a preferred mode. Include checks for alarms that should clear, alarms that should remain latched, and any lockout or permissive that must be deliberately reset. Record the starting condition for each recovery case so a pass can be repeated consistently. If restoration depends on an external source, communications link, or customer control, identify who provides and confirms that condition. The procedure should prevent a “pass” based only on a display returning to normal when the required control response remains unverified.
Assign witnesses and sign-off
Name the parties responsible for preparing the procedure, operating test inputs, observing equipment behavior, recording results, and approving exceptions. Depending on contract scope, these may include the manufacturer, purchaser, engineer, commissioning provider, or controls-system representative; confirm assignments rather than presuming them. The test record should identify the case, document revision, equipment or circuit under test, setup, observed result, pass or fail status, discrepancy reference, and retest outcome. Agree in advance who must witness each case and whose signature closes the record. A witness signature should document observation, not imply approval beyond that person’s assigned authority. Keep unresolved items, deferred cases, and accepted deviations visible in the closeout package. Switchgear Builder Virginia manufactures new, custom switchgear with all-American components and ships nationwide; project-specific schedules, ratings, test scope, and witness arrangements require review and confirmation.
