Control cabinet FAT checklist for repeatable acceptance tests

A repeatable control cabinet FAT checklist connects every requirement to a defined test, an acceptance limit and retained evidence. Agree those items before testing starts. Record actual results, not just ticks, and keep failed tests visible through correction and retesting.

A factory acceptance test proves the agreed cabinet scope under documented conditions. It does not replace machine safety validation, site commissioning or enclosure rating evidence. Separate those responsibilities before approving the test plan.

Agree the test boundary

Start with a controlled specification, drawing set and list of supplied equipment. Identify which functions can be demonstrated with the cabinet alone. Mark anything requiring field equipment as deferred, with a defined site acceptance test.

Use the machine control cabinet specification to establish the requirements before writing acceptance procedures. A FAT should verify that specification, not introduce undocumented requirements during testing.

Your test plan should establish:

• [ ] Cabinet identification, drawing revisions, bill of materials revision and applicable project standards.
• [ ] Software versions, approved parameter files and the configuration to be released.
• [ ] Incoming supply characteristics and the simulated or connected field interfaces.
• [ ] Tests included, tests excluded and the reason for each exclusion.
• [ ] Required approvals, witness points and the document review period.
• [ ] Evidence format, deviation handling and release authority.
• [ ] Site tests needed after installation, including functions that cannot be proven at the factory.

Separate design approval, electrical verification, functional testing and safety validation. Passing one does not establish that the others are complete.

Give every requirement a test record

Assign each requirement a unique reference. Connect it to a procedure with explicit initial conditions, actions, expected results and evidence requirements.

Avoid instructions such as “check operation” or “verify wiring.” State the terminal, signal, operating state and expected response. Another test execution should produce comparable evidence without relying on undocumented assumptions.

Use a record structure like this:

A photograph can prove a label exists. It cannot prove terminal tightness, protective bonding continuity or a functional response.

• [ ] Define acceptance limits before execution.
• [ ] Record the source of each limit: project specification, component instructions or applicable verification procedure.
• [ ] Document why a test is not applicable; do not leave an empty result.
• [ ] Keep original failures when recording later successful retests.

Finish the de-energized inspection first

Isolate all energy sources, apply the approved lockout procedure and verify absence of voltage before internal inspection. Include separate supplies and stored energy in that procedure.

Check the finished cabinet against its approved drawings, not an earlier layout export. Keep enclosure construction checks separate from circuit checks so omissions remain visible.

• [ ] Match component identification and ratings to the approved bill of materials.
• [ ] Verify conductor identification, terminal assignments, separation and routing against the drawings.
• [ ] Record tightening verification using the component manufacturer's method and specified torque where applicable.
• [ ] Inspect protective bonding connections, door bonding and the equipment grounding conductor termination.
• [ ] Confirm clearances, conductor bending space and access to serviceable components.
• [ ] Inspect gasket seating, latch engagement, door alignment and cable-entry sealing.
• [ ] Check cutout dimensions, fitted accessories and unused-opening closures against the approved enclosure design.
• [ ] Remove swarf, loose hardware and temporary assembly materials.

Use the enclosure grounding and bonding guide for the bonding fundamentals. Visual inspection alone does not establish the electrical performance of a protective bonding circuit.

A routine FAT also does not establish a water-ingress rating. Do not add an improvised hose test to the electrical test sequence.

Control electrical verification and energization

Electrical verification needs a project-specific procedure based on the applicable standards, circuit design and component instructions. There is no universal insulation-test voltage or continuity limit suitable for every populated cabinet.

• [ ] Identify required protective bonding, insulation and other electrical verification tests.
• [ ] Record the specified test conditions, acceptance limits and instrument suitability.
• [ ] Confirm instruments have the required calibration status and measurement capability.
• [ ] Protect or isolate sensitive electronics as required by the approved procedure.
• [ ] Record actual measurements, test locations and any excluded circuits.
• [ ] Restore disconnected circuits and verify restoration before functional testing.

Do not apply test voltages to connected electronics unless their instructions explicitly allow the selected test.

Authorize energization only after the required inspections and electrical checks pass. Use a controlled test area, appropriate protective measures and a defined shutdown method. Hazardous field loads must remain isolated unless their operation forms part of an approved, controlled test.

Confirm supply voltages and control power against the design before proceeding. Stop testing when an unexpected condition appears; do not continue merely to finish the checklist.

Test I/O from the documented interface

An I/O test should prove the intended signal path, not merely show that a software tag changes. Record where the stimulus enters and where the response is observed.

A simulator connected at the field terminal can exercise terminal wiring and input processing. A value entered directly into software does not prove that same path.

• [ ] Reconcile the I/O schedule with terminal drawings and software addresses.
• [ ] Verify each discrete input in both states, including indication and configured logic behavior.
• [ ] Verify discrete outputs with an approved test load or isolated indication method appropriate to the output.
• [ ] Check analog channel type, polarity, range, scaling and engineering units.
• [ ] Test defined responses to missing or invalid signals where supported by the design.
• [ ] Record channels that need field-device testing during commissioning.

For example, a 4–20 mA input scaled from 0–100 units should nominally indicate 0, 50 and 100 units at 4, 12 and 20 mA. The acceptance tolerance must account for the approved accuracy requirement and measurement uncertainty; those three nominal values are not themselves a tolerance.

Keep safety-related circuits within their approved validation procedure. Standard I/O simulation is not evidence that a safety function meets its required performance.

Prove sequences and abnormal responses

Write functional tests around operating states and transitions. Include the initial state, commanded action, expected outputs, indications and permitted timing.

Test normal operation first, then the approved abnormal conditions. Do not invent fault-injection methods that could damage equipment or create hazardous motion.

• [ ] Demonstrate startup, normal operation and controlled shutdown within the agreed cabinet scope.
• [ ] Check mode selection, command priority and prevention of incompatible commands.
• [ ] Verify alarms, acknowledgement behavior and alarm history against the specification.
• [ ] Check approved responses to loss and restoration of power or communications.
• [ ] Verify restart behavior without allowing unintended hazardous operation.
• [ ] Confirm retained settings, access permissions and configuration backup procedures.
• [ ] Record functions deferred because the required field equipment is absent.

Safety-function testing requires an approved validation plan and controlled conditions. Never defeat a safety function to obtain a passing production sequence.

If a test fixture or simulator is used, identify it in the evidence. Record its limitations so simulated acceptance is not mistaken for a complete machine test.

Record the conditions behind thermal results

A short energized demonstration does not prove cooling performance at full load. Record heat-producing equipment, loading, ambient temperature, door position and cooling configuration whenever temperature is an acceptance item.

• [ ] Define the representative load and the required operating duration or stabilization criterion.
• [ ] Keep doors closed when the intended operation requires a sealed cabinet.
• [ ] Record measurement locations and instrument identification.
• [ ] Compare local component temperatures with the applicable limits and derating requirements.
• [ ] Identify thermal tests deferred until realistic site loading is available.

Use the control cabinet temperature limits procedure to establish what needs measurement. A passing air-temperature reading at one location does not establish acceptable temperatures everywhere inside.

Keep transport verification separate as well. Enclosure transport testing addresses movement-related faults that can occur after factory acceptance.

Close deviations before releasing the cabinet

Run the complete procedure internally before the formal acceptance event. Resolve ambiguous instructions and missing evidence during this preparation, rather than changing acceptance criteria while a test is running.

• [ ] Give each discrepancy a unique reference and affected requirement.
• [ ] Record the observed condition, correction and disposition.
• [ ] Identify related tests affected by wiring, hardware or software changes.
• [ ] Retest the failed requirement and affected functions after correction.
• [ ] Reconcile final drawings, software backups and parameter files with the tested cabinet.
• [ ] Remove temporary test connections and verify the final configuration.
• [ ] Record unresolved items and obtain explicit release authorization where acceptance permits them.

Do not convert a failed test into “not applicable” to close the record. Preserve the failure, correction and successful retest as a traceable sequence.

The release package should contain the approved procedure, completed results, evidence index, deviation log and final configuration references. It should also identify every outstanding site test.

What to send with a quote request

Include FAT requirements in the quote scope, especially when acceptance depends on documentation, fixtures or witnessed testing. Do not assume an enclosure fabrication order includes a wired cabinet, programming or functional acceptance testing.

The control cabinet layout quote scope helps separate layout work, fabrication and other deliverables.

Send these requirements with the request:

• [ ] Enclosure dimensions, material, environmental conditions and required enclosure rating.
• [ ] Approved layout, cutouts, cable entries, mounting details and fitted accessories.
• [ ] Applicable listing or approval requirements, stated separately from FAT acceptance.
• [ ] Required inspections, measurements, evidence formats and document revisions.
• [ ] The boundary between enclosure supply, panel assembly, programming and testing.
• [ ] Acceptance hold points and the process for approving deviations.

We build custom enclosures to the approved specification. Their ratings are manufacturer ratings for the specified design; the enclosures are not UL listed. A completed FAT does not change that status.

Enclosures for this job

Catalog sizes that suit the job this article answers, picked from its subject; open one for its full specifications.

Questions