How to Read a BESS Factory Acceptance Test (FAT) Protocol Before Shipment
Key Takeaway
A BESS FAT protocol is the buyer’s last structured chance to prove the shipped SKU matches the PO—before ocean freight and SAT rework. Read it for pass/fail criteria, witness rights, and document deliverables; do not waive electrical, thermal, and BMS tests to save a week at the factory.
Table of Contents
Why Buyers Regret Waiving FAT
C&I battery orders often slip schedule at the port, not at the factory. Buyers waive or dilute Factory Acceptance Test (FAT) to hit a vessel date, then discover at Site Acceptance Test (SAT) that PCS grid-code settings were wrong, BMS alarm maps do not match SCADA, or thermal derate points differ from the datasheet. Rework on site costs more than a disciplined FAT week—especially when cranes, outages, and insurer hold points are involved.
The FAT protocol is a contract document. If a test is not listed with explicit pass/fail limits, the OEM can claim “industry practice” while you hold a failed SAT. Read the protocol before shipment authorization, not as a PDF archive after COD.
Align FAT with export compliance: certificate packs and UN38.3 shipping configuration are separate but must match the same BOM—see UN38.3 and CE export compliance for BESS. For lead-time and MOQ context on repeat orders, see C&I BESS lead time and MOQ export guide.
What a C&I BESS FAT Protocol Contains
A complete FAT protocol typically includes:
- Unit under test — serial numbers, firmware, cell/pack revision
- Test equipment calibration — meters, loads, environmental chambers
- Procedure steps — preconditioning, charge/discharge profiles, soak times
- Acceptance criteria — numeric limits, not “normal operation”
- Roles — OEM tester, buyer witness, third party if any
- Non-conformance process — retest, repair, deviation approval
- Deliverables — signed report, waveforms, photos, data logs
FAT proves the factory-built assembly. It does not replace civil works, grid interconnection, or full-system SAT—but it should catch defects that are expensive to fix after export.
Electrical and PCS Tests
Electrical FAT items should map to your PO kW/kWh and grid-code profile.
| Test area | What to verify | Weak protocol signal |
|---|---|---|
| Insulation / dielectric | DC and AC isolation per OEM procedure | “Visual inspection only” |
| Charge / discharge | Specified C-rate, energy throughput vs nameplate | No energy balance calculation |
| Efficiency round-trip | Documented at reference power/temperature | Marketing brochure value cited without test |
| PCS grid functions | Power factor, ramp rates, fault ride-through if in scope | “As per default firmware” |
| Ground fault and RCD | Trip thresholds and reset behavior | Omitted for “container only” FAT |
Require waveform captures or data logs for trips and ramp tests. “Pass” without artifacts is not auditable for warranty disputes.
Thermal and Environmental Checks
Thermal FAT validates that HVAC or liquid loops control cell temperatures under load. At minimum, confirm:
- Sensor placement matches BMS map
- Fans or pumps start at defined thresholds
- Derate or alarm triggers at high-temperature setpoints
- Cold-start behavior if shipping to freeze-prone regions (environmental chamber or OEM-defined low-temperature start test)
- Leak checks on liquid-cooled skids if applicable
Factory ambient may not match site climate. FAT should still prove control logic responds; SAT proves performance in real weather. For system-level C&I context, see the complete guide to C&I energy storage solutions in 2026.
BMS, EMS, and Protection Logic
BMS FAT is where alarm maps and interlocks are validated before SCADA integration.
Non-negotiable BMS checks
- SOC/SOH calibration method and error band
- Cell voltage and temperature alarm and fault thresholds
- Contactor or breaker open commands on fault injection (where safe)
- Communication to EMS/SCADA—Modbus, CAN, or IEC 61850 as specified
- Firmware and parameter file version recorded in FAT report
Fire detection interface
If fire panels are factory-wired, FAT should include detection loop continuity and alarm routing to EMS. If fire is site-installed, state the boundary clearly—do not assume SAT will cover factory wiring errors.
Document Pack Tied to FAT
FAT pass should trigger delivery of a dossier aligned to the shipped serials:
| Document | FAT linkage |
|---|---|
| Signed FAT report | Serial numbers, dates, witness signatures |
| As-built single-line and BOM | Must match unit under test |
| Certificate pack (IEC, CE, UL as applicable) | SKU and revision mapped—not generic folder |
| O&M manual and spare parts list | Version tied to firmware in FAT |
| Warranty conditions | Throughput and temperature limits referenced in tests |
| Shipping SOC and UN38.3 packing photos | Same pack revision as FAT unit |
Payment milestones tied to “FAT pass” should define pass as signed report plus document pack, not a verbal OK from sales.
Witness, Remote, and Retest Rules
Negotiate before PO:
- Witness rights — on-site, remote video, or review-only
- Notice period — days of advance scheduling
- Retest cost — who pays if failure is OEM responsibility
- Deviation process — written acceptance for partial waivers
- Shipment hold — no release until NCR closed or deviation signed
Remote witness works when live data streams and raw logs are shared in real time. PDF summaries days later are not equivalent.
Boundaries: When FAT Scope Differs
FAT scope legitimately narrows or shifts when:
- PCS is shipped separately and FAT covers battery skid only—define interface tests
- Repeat SKU with prior witness FAT—buyer may accept sample FAT plus spot checks if the PO states that sampling plan
- Container is too large for full-power load at factory—partial load with SAT completion clause
- Grid-code scripts cannot run without utility simulator—require simulator or defer with written SAT obligation
Boundaries must be written. “We always do FAT” marketing language without a protocol is not scope.
Request a BESS FAT Review Checklist
Share your draft FAT protocol or PO test section. Weltrus can help align acceptance criteria with C&I project risk—before you authorize shipment.
Frequently Asked Questions
What is a BESS factory acceptance test (FAT)?
A documented factory test program on the production or representative unit before shipment, with pass/fail criteria against the PO spec.
Should buyers witness BESS FAT in person?
For high-value or first-of-kind SKUs, yes—or use qualified remote witness. Define retest and delay rules in the contract.
What FAT tests are non-negotiable for C&I BESS?
Insulation, charge/discharge at specified C-rate, protection trips, thermal response, BMS/EMS mapping, and locked firmware records.
How does FAT relate to UN38.3 and export paperwork?
FAT proves performance; transport and certification docs prove legal shipment configuration. Both must reference the same pack SKU and revision.
Can FAT failures delay shipment without penalty to the buyer?
Only if the contract ties shipment to pass and assigns rework time to the OEM. Otherwise delay costs sit in ambiguous “force majeure” gaps.
