A containerized BESS technical specification checklist should not be a list of attractive product features. It should force every bidder to connect each requirement to the offered configuration, a controlled document, a stated deviation, and an acceptance-stage record. This structure helps a buyer identify when a headline kWh figure is being offered under a different operating boundary, enclosure, interface, or warranty assumption from another proposal.
Before issuing an RFQ, ask every supplier to complete the same matrix: buyer requirement → offered configuration and revision → evidence → deviation or exclusion → FAT witness point → site responsibility → open item. Use this article with our RFQ guide for containerized solar BESS for the procurement process, and with the BESS procurement checklist for bid comparison and award controls.
Start with a specification-to-evidence matrix—not a feature list
Copy this structure into your RFQ. Do not accept “compliant,” “standard,” or “included” as a complete answer. Each response needs a model, configuration, revision, evidence reference, and any departure from the buyer requirement.
| Buyer requirement | Offered configuration and controlled revision | Evidence reference and stated conditions | Deviation, exclusion, or assumption | FAT / SAT acceptance point and owner | Open item, owner, and due date |
|---|---|---|---|---|---|
| Delivered energy and AC power | Nominal and usable energy; continuous and maximum power; duration; point of delivery; auxiliary-load treatment; SOC window | Configuration-specific data sheet, calculation basis, test conditions, ambient conditions, and derating assumptions | Any condition under which the stated energy, power, or duration does not apply | FAT evidence where applicable; site performance conditions and SAT owner defined in contract | Confirm performance-test boundary, witness role, and unresolved input data |
| Battery and power-conversion configuration | Cell and PCS model; rack arrangement; BMS limits; AC/DC ratings; overload curve; firmware/software revision | BOM, controlled drawings, data sheets, single-line diagram, and revision register | Substitutions, unconfirmed interfaces, or data not available for the offered revision | Configuration verification at FAT; site interfaces confirmed at SAT | Close configuration changes before release to manufacture |
| Container, transport, and access | Transport state; dimensions; gross mass; center of gravity; lifting points; locking/folding arrangements; service clearance | GA drawing, lifting/handling plan, transport-state drawing, and packing responsibility matrix | Route, handling, stacking, or access constraints outside the quoted scope | Factory record for transport configuration; logistics party confirms route constraints | Assign owner for outstanding route, carrier, and handling evidence |
| Site and environmental design basis | Ambient range; humidity; altitude; corrosion; dust; wind/snow/seismic inputs; noise boundary; HVAC basis | Design-basis schedule, derating curves, thermal-management basis, and stated boundary list | Conditions requiring a different enclosure, derating, civil design, or maintenance basis | Supplier states equipment basis; local EPC/engineer confirms site inputs | Close missing climate, civil, and clearance inputs before final design |
| Interfaces, protection, and controls | PCC, voltage/frequency, grounding, protection boundary, emergency-stop interface, SCADA/EMS protocol, I/O, and access rights | Single-line diagram, protection matrix, control narrative, I/O list, point list, and network architecture | Interfaces requiring owner, utility, EPC, or third-party design input | Factory I/O and logic checks; site settings and communications verified at SAT | Assign final-setting, protocol, and cybersecurity decisions |
| Evidence, tests, and handover | Applicable reports, document revisions, FAT/SAT procedure, witness points, pass criteria, manuals, and spares records | Document register with model/configuration, report number, issuer, date, revision, and applicability statement | Missing, non-applicable, representative, or configuration-mismatched evidence | Contract defines FAT release authority and SAT/site responsibilities | Track each unresolved record to a named owner and due date |
Buyer rule: a capacity, efficiency, IP rating, certificate, or test report is not comparable until its exact model/configuration, test condition, scope, and exclusions are visible. Do not allow evidence from a different cell, rack, PCS, enclosure, firmware, or fire-protection arrangement to be presented as automatic proof for the offered system.
Specify the output you need—not only a nameplate number
For a solar container or containerized BESS, a usable specification starts at the delivery point. Ask bidders to distinguish nameplate energy from usable AC energy; rated power from maximum or short-duration power; and an equipment-level figure from a site-level result. Require the starting state of charge, ambient temperature, discharge duration, auxiliary consumption, allowable depth of discharge, and any temperature or altitude derating that affect the stated output.
For PV equipment, request module model and quantity, rated power, Voc, Vmp, Isc, Imp, maximum system voltage, temperature coefficients, mounting method, and the offered warranty terms. For battery and PCS equipment, request the exact model, configuration, voltage range, power limits, protection functions, control modes, and communication interfaces. If the project needs black start, grid-forming operation, islanding strategy, or remote dispatch, write the operating scenario and acceptance evidence into the requirement rather than assuming it is included.
Make the site boundary visible before suppliers design around it
A containerized BESS technical specification checklist should make the buyer’s site assumptions explicit. Provide location, elevation, temperature range, diurnal swing, humidity and condensation risk, salt/dust exposure, flood/seismic/wind constraints, noise limit, foundation information, available access, maintenance clearance, and the interface boundary with transformers, switchgear, loads, or the grid.
Then require each bidder to state where its operating rating changes. “Suitable for outdoor use” is not a usable procurement requirement. Ask which enclosure or component carries the stated rating, what test or calculation supports it, whether HVAC or maintenance assumptions apply, and what exceptions follow if the site sits outside the stated design basis.
Require an interface package before promising connectivity
Interfaces need explicit coordination before the container arrives on site. Identify the point of common coupling, voltage and frequency, grounding scheme, transformer/switchgear boundary, metering, emergency-stop logic, fire-system interface, remote-control authority, and fault-reset sequence. Request a controlled single-line diagram, protection-function list, control narrative, communications point list, time synchronization method, network topology, and protocol version.
For a U.S. 60 Hz interconnection context, IEEE 1547-2018, including applicable amendments and project-specific utility requirements, provides a reference point for interconnection and interoperability between distributed energy resources and electric power system interfaces. It is not a universal grid rule and does not replace the local utility’s studies, settings approval, commissioning process, or permission to operate. Put the relevant utility and project requirements in the RFQ, then make the supplier identify what it can provide as equipment-side data and what still needs local engineering or approval.
Ask for evidence by configuration and by purpose
The document register is the control point that turns a specification into a comparable bid. Request each certificate, report, drawing, declaration, and test procedure with its manufacturer, model, configuration, rating, issuer, report number, date, revision, scope, and stated applicability to the offered system. Require a separate deviation log for conditions the supplier cannot meet, assumptions it made, and items it excludes.
When a project asks for a particular standard or evidence route, treat it as a project-specific evidence request. UL 9540 is UL’s Energy Storage Systems and Equipment safety standard. Whether a particular listing, certification, or report is required depends on the applicable code pathway, project specification, authority having jurisdiction, and exact offered configuration. Likewise, UL 9540A is a test-method/report context for thermal-runaway fire-propagation assessment; it is not a universal product certification.
If the equipment will travel as an international freight container, specify whether it is a transport container conversion, a non-standard module, or a fixed prefabricated enclosure. Where international container transport is part of the project, ask for the transport configuration, handling information, and any applicable CSC documentation. CSC relates to transport-container safety; it does not establish BESS electrical safety, site installation compliance, or project acceptance. Where lithium batteries are transported, ask the supplier and logistics party to identify the actual transport classification and evidence for the specific battery and transport configuration; the UN Manual of Tests and Criteria is a primary reference for the UN 38.3 test context.
Turn FAT and SAT into separate deliverables
Use FAT to verify the agreed factory configuration and records; use SAT to verify the installed system and site interfaces. Your RFQ should name the configuration and serial-number scope, software/firmware version, test steps, calibrated instruments, raw records, alarm/interlock checks, pass criteria, deviation process, witness roles, and shipment-release authority for FAT.
SAT should separately address installation condition, grounding and cables, field I/O, communications, applied protection settings, local control permissions, site environment, and the project’s performance-test boundary. Passing FAT does not prove transport condition, local construction quality, authority approval, grid permission, or long-term field performance. Keep the factory witness record, shipment-release decision, site-work scope, and final acceptance record as separate controlled decisions.
Use this pre-quote handoff
- Freeze the buyer’s load, PV, storage, site, and interface assumptions.
- Issue the same specification-to-evidence matrix to every bidder.
- Reject untraceable “compliant” answers; require a revision, evidence reference, or logged exception.
- Separate factory proof, shipment release, site work, and local approvals in the contract and evaluation matrix.
- Carry all open technical items into the selected supplier’s clarification log before award.
If you are preparing a solar container or containerized BESS RFQ, send the intended load profile, site country, required interfaces, target operating conditions, and known approval constraints through our project enquiry form. Use those inputs to structure the technical specification questions before suppliers quote.
