A Green Dashboard Is Not a Passed SAT
A BESS Site Acceptance Test (SAT) should prove that the installed system works at the actual site, with the actual transformer, switchgear, BMS, PCS, EMS, SCADA, protection settings, and communications. Pass/fail criteria should be agreed before testing and tied to measurable requirements—not decided after commissioning by whether the system can simply charge and discharge.
I treat SAT as the point where the project stops being a collection of equipment and becomes an operating power system.
That distinction matters.
Factory Acceptance Testing can verify equipment before shipment. SAT has a different job: finding problems introduced—or exposed—by transport, installation, cabling, configuration, site interfaces, and final software integration.
I Want the Test Sheet Before Anyone Energizes the BESS
A useful SAT protocol does not say:
Test PCS — Pass
It says what "pass" means.
For example:
Command 100 kW discharge for 30 minutes. Measured AC power shall remain within the contractually agreed tolerance.
Now the technician knows what to test.
The owner knows what constitutes acceptance.
And if the result is 91 kW, nobody needs to invent a definition of "close enough" beside an energized cabinet.
NREL's commissioning guidance emphasizes establishing acceptance criteria and documenting commissioning results rather than treating commissioning as an informal startup activity. NREL
For a Ruibit/Dawnice project, I would want those criteria linked back to the approved technical specification and final equipment configuration.
SAT Starts Before the First Charge Cycle
On site, my first pass is mostly visual and documentary.
I want to confirm:
equipment model and serial numbers
shipping/installation damage
battery and PCS connections
cable identification and torque records
grounding/bonding
protection devices
HVAC or liquid-cooling system
fire detection/suppression interfaces
emergency stops
network connections
approved firmware versions
final protection settings
A commissioning engineer should also have the latest single-line diagram, approved settings, equipment manuals, FAT records, and open punch-list items.
If the physical installation no longer matches the drawing, I fix the document or the installation before pretending the SAT represents the final system.
The First Real Test Is Usually an Interface Test
A battery cabinet may work.
The PCS may work.
The EMS may work.
SAT asks whether they work together .
A typical commissioning sequence might include:
| SAT Area | Example Acceptance Evidence |
|---|---|
| BMS–PCS communication | Stable data, correct limits and alarms |
| EMS commands | Charge/discharge commands executed correctly |
| Metering | Direction, scaling and phase mapping verified |
| SCADA | Required points and alarms visible remotely |
| Cooling | Starts/stops according to control logic |
| E-stop | System reaches defined safe state |
| Protection | Correct trip/alarm behavior |
| Grid loss | Response matches approved operating mode |
The actual acceptance values must come from the project specification, manufacturer requirements, grid rules, and applicable standards.
I would not copy a generic tolerance from another BESS and call it engineering.
Charge and Discharge Tests Need a Measurement Boundary
This is where acceptance disputes begin.
Suppose the contract says:
Usable energy: 200 kWh
The SAT measures:
194 kWh
Pass or fail?
I cannot answer until I know where energy was measured.
At the battery DC terminals?
PCS AC output?
Point of common coupling?
Were HVAC and auxiliary loads included?
What were initial and final SoC?
Battery temperature?
Power level?
The U.S. DOE's BESS Evaluation Method describes performance assessment using measurable parameters such as energy capacity, efficiency, response and availability, while stressing the importance of consistent measurement boundaries and operating conditions. DOE
So before an energy-capacity test, I freeze:
measurement point
starting SoC
ending SoC
charge/discharge power
temperature range
auxiliary-load treatment
meter accuracy
Then the number means something.
I Intentionally Create Faults During SAT
Not dangerous faults.
Controlled signals and conditions the system is supposed to handle.
Depending on the agreed test scope, I may verify:
loss of BMS–PCS communication
high-temperature alarm input
HVAC fault
emergency stop
meter/SCADA communication loss
PCS trip
fire-system interface
loss of grid
The point is not to abuse the equipment.
It is to prove the control architecture knows what to do when normal operation stops.
A system that performs beautifully at 100 kW but sends no remote alarm when the cooling system fails has not completed the commissioning conversation.
The Punch List Is Part of the SAT Result
Not every defect needs to prevent commercial operation.
A missing label and a failed emergency stop are obviously not equivalent.
I normally separate findings into something like:
Critical: safety or protection problem; energization/operation cannot be accepted.
Major: required performance or functionality not achieved; closure required according to contract.
Minor: documentation, labeling, cosmetic, or non-critical issue that can be closed through an agreed punch list.
The project contract should define the actual classification and acceptance rules.
This is especially important for final payment.
If the commercial milestone says:
10% payment after SAT
then "SAT complete" must have a contractual meaning.
Otherwise commissioning becomes a negotiation instead of a test.
The Commissioning Record Should Survive the Commissioning Engineer
Six months later, an O&M technician may need to know:
Why is PCS 2 limited to 92 kW?
Was that already observed during SAT?
Which firmware was installed?
What were the original insulation readings?
Which alarm was tested?
Was the CT polarity ever corrected?
That is why I want the final SAT package to contain:
signed test sheets
raw measurement data where relevant
alarm/event records
photos
firmware/software versions
protection settings
as-built drawings
serial numbers
open and closed punch-list records
final acceptance signatures
The SAT is not finished when the technician closes the laptop.
It is finished when another engineer can reconstruct what was tested and understand why the project was accepted.
For a commercial BESS, "it works" is an observation. "It passed" should be a documented result against criteria agreed before the test began.
FAQs
1. What is a BESS Site Acceptance Test?
A BESS SAT verifies that the installed battery, PCS, BMS, EMS, SCADA, protection, cooling, metering, and site interfaces operate correctly together under actual site conditions.
2. What should be tested during BESS commissioning?
Typical tests include BMS–PCS communication, charge/discharge performance, EMS commands, metering, SCADA points, cooling, protection functions, E-stop operation, alarms, and grid-loss response , depending on project scope.
3. How should BESS SAT pass/fail criteria be defined?
Criteria should be agreed before testing and linked to measurable contractual requirements such as power, energy capacity, response, communication, protection behavior, and operating conditions.
4. Why is the measurement boundary important during a BESS capacity test?
A 200 kWh requirement means little unless the contract defines whether energy is measured at the battery DC terminals, PCS AC output, or point of connection , and how auxiliary loads and SoC limits are treated.
5. What records should be retained after SAT?
Keep signed test sheets, measurement data, alarm logs, firmware versions, protection settings, serial numbers, as-built drawings, photos, punch-list records, and final acceptance signatures .
