BESS Container Factory Acceptance Test: Documents and Functional Checks

A factory acceptance test (FAT) is the pre-shipment quality gate for a Battery Energy Storage Container: Smart Energy Control for Real-Time Grid Response. It verifies that the containerized system matches its approved design documents, component specifications, and contractual acceptance criteria before it leaves the factory floor.

This guide explains what a BESS container FAT covers, which documents you should review, which functional checks matter by subsystem, and how to turn test results into an auditable shipment-release decision. It is written for project owners, EPCs, integrators, procurement teams, and commissioning engineers who need to witness or approve a container before transport.

Why a Factory Acceptance Test Is a Critical Pre-Shipment Gate

A FAT is performed in a controlled factory environment, before transport, site installation, and grid interconnection add complexity. It is the last practical opportunity to catch assembly errors, integration faults, and configuration mistakes while correction is still inexpensive.

A well-executed FAT can detect:

• reversed polarity or loose terminations;
• incorrect module or rack configuration;
• BMS alarm settings that do not match the approved alarm matrix;
• communication mismatches between the BMS, EMS, and PCS;
• protection relay logic that does not trip at the expected threshold;
• HVAC, fire-detection, or emergency-stop interlocks that fail to respond.

Each finding is recorded with evidence, so both the supplier and the buyer share the same picture of the system’s as-built condition. That record becomes the baseline for later site acceptance testing and commissioning.

BESS FAT vs SAT vs Commissioning: Where Factory Testing Ends

FAT is often confused with site acceptance testing and commissioning. They are separate phases with different objectives.

Phase	Location	What It Verifies
Factory acceptance test (FAT)	Factory	As-built configuration, subsystem function, and integration against approved design documents before shipment
Site acceptance test (SAT)	Project site	Transport integrity, installation workmanship, site wiring, grid connection, and local operating conditions after delivery
Commissioning	Project site	Energization, coordinated system operation, control modes, and readiness for commercial or project-specific operation

FAT does not verify transport damage, site cabling, grid conditions, installation clearances, or local interconnection approval. Those checks belong to SAT and commissioning. When the container reaches the site, the SAT team should compare its results against the FAT baseline. The bess container commissioning checklist outlines the site-level steps that follow delivery.

Documents to Assemble Before the FAT Begins

A FAT is only as credible as its document package. Without an approved procedure and reference documents, test results are difficult to evaluate and easy to dispute.

The following documents should be reviewed and approved before testing starts:

Document	Why It Is Needed
Approved FAT procedure	Defines the test sequence, instruments, tolerances, and pass/fail criteria for every check
Contractual technical specification	Establishes the performance and design requirements the system must meet
Single-line diagram	Shows how the battery, PCS, switchgear, transformers, and loads are connected
As-built drawings	Confirms layout, mechanical assembly, grounding, cable routing, and communication architecture
Battery datasheets	Provides nominal voltage, Ah capacity, energy in kWh, current limits, and temperature limits
BMS, EMS, and PCS datasheets	Defines operating ranges, protection settings, communication interfaces, and control modes
Calibration certificates	Proves the test instruments used to record measured values are accurate
Software and firmware version records	Ensures the tested configuration matches the configuration that will be shipped
Component test reports and certificates	Supports model-specific compliance claims, but only where the certificate applies to the exact component or system
Prior inspection and nonconformance reports	Confirms that open issues from earlier inspections have been resolved

The FAT procedure itself must be version-controlled and approved by both the supplier and the buyer before the test date. If the procedure is changed during testing, the change, the reason, and the approving party should be recorded.

FAT Roles: Who Witnesses and Who Approves

A FAT produces a binding acceptance record, so roles should be defined before the test begins.

Role	Responsibility	Authority
Owner or asset operator	Defines acceptance requirements and commercial expectations	Holds final shipment-release decision unless delegated by contract
EPC or integrator	Coordinates the test schedule, reviews evidence, and manages the punch list	Recommends acceptance or hold based on evidence
Supplier test engineer	Executes the approved FAT procedure and records measured results	Operates the system and captures evidence
Independent witness	Provides impartial verification of test results and report quality	Reports findings without operational authority

The contract should state who may stop a test, who may accept a deviation, and who signs the final FAT report. When these details are left open, a disputed test result can delay shipment and create commercial conflict.

If you are evaluating suppliers, the quality of the proposed FAT procedure and document package is a meaningful selection criterion. A bess container supplier that treats FAT as a formality rather than a controlled verification step may be transferring risk to your project.

Subsystem Functional Checks

The FAT should test each subsystem against the approved procedure, not through ad hoc observation. Every check must produce an auditable record: a measured value, screenshot, log, event record, or photograph.

Enclosure, Mechanical, and Visual Inspection

The physical container is the foundation for every other system. Mechanical defects discovered after shipment are expensive to correct.

Check:

• container nameplate and identification against the bill of materials;
• doors, locks, seals, hinges, and access panels;
• enclosure integrity, including the specified IP rating if it is part of the contract;
• cable routing, termination quality, labeling, and general workmanship;
• grounding and bonding points;
• lifting points, tie-downs, and shipping fixtures;
• corrosion, paint damage, and assembly defects.

Each finding should be photographed and recorded against the as-built drawing.

Battery Racks, Modules, and BMS Checks

The battery subsystem stores the energy that the container is designed to deliver. The BMS protects it from electrical and thermal faults.

Verify:

• module and rack positions match the approved layout;
• module and rack voltage readings are within the expected range;
• temperature sensors are installed and reporting correctly;
• state of charge and state of health values are available if the BMS provides them and the contract requires them;
• cell or module balancing is operating within the manufacturer’s specification;
• BMS alarms respond correctly to over-voltage, under-voltage, over-current, over-temperature, and low-temperature conditions;
• BMS communication to the EMS and PCS is stable;
• manual service disconnects operate and isolate as intended.

The BMS alarm responses must match the approved alarm matrix. A BMS that reports the correct alarm through the wrong communication path is a functional failure, not a minor discrepancy.

PCS, Inverter, Switchgear, and Protection Checks

The power conversion system controls how the battery charges and discharges and how the container interacts with the AC side of the project.

Verify:

• PCS or inverter identity, firmware version, and rated values match the approved datasheet;
• DC-side and AC-side voltage and current readings are within tolerance;
• charge and discharge commands execute correctly, at reduced current or rated current as permitted by the procedure;
• active power and reactive power behavior is correct where the test allows;
• breakers trip manually, remotely, and under protection-command conditions;
• protection relay settings and interlock logic match the approved settings;
• insulation resistance and grounding checks pass before energization;
• polarity is correct at every DC connection.

Protection checks are particularly important because a relay that is set incorrectly may not be discovered again until the system is under stress on site.

EMS, SCADA, and Communication Checks

The energy management system, SCADA interface, and communication links determine whether the container can be operated remotely as part of the wider project.

Verify:

• EMS point lists and operating modes match the approved design;
• setpoint changes and schedule execution are correct;
• local and remote control modes behave as expected;
• SCADA or platform communication delivers status points, alarms, and event logs with accurate timestamps;
• loss-of-communication behavior follows the specified default state;
• command signals produce the correct device response.

Communication checks should be performed point by point, not sampled. A single incorrect register mapping can cause a system to respond to the wrong command in normal operation.

HVAC, Fire Protection, Alarms, and Emergency-Stop Checks

Thermal management and fire safety protect both the equipment and the people who will work near the container.

Verify:

• HVAC operation in heating and cooling modes, including setpoints, sensor readings, and alarms;
• ventilation dampers and their interlocks;
• smoke, heat, or gas detection as designed for the project;
• fire-suppression control panel, manual release, automatic release, agent pressure, and alarm outputs;
• emergency stop activation from local and remote locations, including the resulting shutdown of the PCS, BMS contactors, and HVAC interlocks;
• the complete alarm matrix: every alarm condition produces the correct notification and system action.

E-stop testing must follow the approved procedure to avoid damaging equipment. The purpose is to confirm a controlled shutdown, not to stress the system unnecessarily.

Integrated Container-Level Functional Tests

Individual subsystem checks are necessary but not sufficient. The container must also prove that all systems work together as one coordinated unit.

Representative integrated tests include:

1. Transition from standby to charge mode and charge to discharge mode at a controlled rate.
2. Change an operating setpoint through the EMS and confirm the PCS responds.
3. Validate SOC-based control logic, including charge and discharge limits at defined SOC thresholds.
4. Confirm interlocks between HVAC, the fire panel, the E-stop, and the power path.
5. Simulate a fault or command a shutdown, then confirm restart and recovery behavior.
6. Apply a load step if the contract and test procedure require it.

Integrated tests expose issues that component-level checks cannot: for example, a BMS that protects the battery correctly but conflicts with the EMS during a mode transition, or a fire panel that interrupts power when it should only raise an alarm.

For commercial and industrial projects, the specific integrated scenarios may differ. A ci energy storage system with peak-shaving logic, for instance, must demonstrate that the EMS responds to site demand signals correctly during the integrated test.

Contractual Performance Tests and Acceptance Limits

A FAT does not automatically include a full capacity test, an efficiency test, or a response-time test. Whether these tests are required depends on the contract and the approved FAT procedure.

Functional checks confirm that systems operate. Performance tests confirm that they operate to a measurable standard. Common performance tests include:

• capacity test at a defined C-rate and SOC window;
• active power and reactive power capability tests;
• response-time test for grid-service commands;
• round-trip efficiency test with a defined measurement boundary.

Each performance test requires explicit acceptance limits in the contract. The test method matters as much as the result: the starting SOC, charge and discharge current, temperature, and measurement boundary all affect the outcome.

Do not assume that a generic FAT includes a full-capacity discharge test. Long-duration capacity tests take time, may be limited by the factory’s available load banks, and are sometimes deferred to site acceptance. The FAT procedure should state clearly which performance tests are included and which are not.

Also distinguish nameplate capacity from usable energy. A battery system with a nominal capacity of 1 MWh may have a usable range defined by the BMS, the inverter, and the depth-of-discharge limits in the contract. The FAT should test against the same basis that the commercial guarantee uses.

FAT Evidence, Deviations, Punch Lists, and Shipment Release

A FAT report is only as valuable as the evidence it records. Every test step should produce a result that can be reviewed later without relying on memory.

For each check, record:

• the measured value and the expected value;
• the instrument used, including its identification and calibration status;
• software and firmware versions;
• the starting and ending SOC where relevant;
• ambient temperature and test configuration;
• screenshots, event logs, trend plots, or photographs;
• the name and signature of the test engineer and witness.

Findings should be classified clearly:

Classification	Meaning
Pass	The result meets the approved acceptance criteria
Pass with note	The result is acceptable but a minor observation should be documented
Deviation	The result differs from the approved criteria, but the difference is accepted by the buyer or by a documented engineering decision
Fail	The result does not meet the approved criteria and must be corrected

Punch-list items should include a severity classification, the responsible party, the target closure date, and the evidence required to close each item.

After corrective work, the retest scope must be defined. A change to protection settings may require retesting only the affected relay logic, while a change to the battery configuration may require a broader retest. The supplier and buyer should agree on the regression scope before the retest begins.

The shipment-release decision has three possible outcomes:

1. Release: all tests pass and no open punch-list items remain.
2. Release with approved punch list: the remaining items do not affect transport safety or site installation, and closure is contractually scheduled.
3. Hold: one or more critical items must be corrected and retested before shipment.

The final FAT report should reference every attachment: measured values, logs, screenshots, signature pages, and approved deviations. This report becomes the official pre-shipment record for the project.

What a FAT Does Not Prove

A passing FAT is strong evidence that the container was correctly assembled and functionally integrated at a specific point in time. It does not guarantee everything that follows.

FAT does not prove:

• that the container will arrive undamaged after transport;
• that site wiring, grounding, and grid interconnection are correct;
• that local electrical and fire-safety inspectors will approve the installation;
• that the system meets every certification requirement unless the certificate or listing is explicitly part of the FAT scope;
• that long-term performance, battery aging, or seasonal operating extremes are already proven.

Certification and FAT are separate activities. A system-level safety listing such as UL 9540 or a transport test such as UN 38.3 may support specific claims, but those claims must be tied to the exact model, certificate, and scope. A FAT is not a substitute for any of these.

The FAT baseline is best understood as a snapshot of the system at the factory gate. Comparing that snapshot with SAT results later is the proper way to identify transport damage, installation errors, or site-related performance issues.

From FAT to SAT: Protecting the Baseline

Once the FAT report is approved and the container is released for shipment, the evidence must not sit in a project folder until commissioning starts.

The FAT baseline should be:

1. packaged into the project quality record;
2. shared with the site commissioning team before the container arrives;
3. used as the comparison reference for SAT;
4. tracked for open punch-list items that carry over to site closure;
5. matched against the site-level checks defined in the bess container commissioning checklist.

A clear handoff prevents a common project failure: FAT evidence that is never used on site, so problems that existed at the factory are rediscovered only after installation costs have been incurred.

The FAT is not the final test of the system. It is the first complete test of the container as a product. Done properly, it gives both the buyer and the supplier a shared, evidence-based starting point for everything that follows.