Quick lead-in for owners
You want a clear map of engineering support before signing contracts. Ask battery energy storage system manufacturers for their documentation and track record. Ask also about battery energy storage system certification and whether systems passed UL 9540A thermal runaway testing. Keep questions short. Expect straight answers.
What exactly will the engineer deliver?
Get a list. Be firm about format and dates. Typical deliverables:- Single line diagrams, panel schedules, and cable schedules.- Site layout, civil and structural drawings with load cases.- Protection and control settings, relays, and interlocks.- Testing plans: FAT, SAT, commissioning checklists.- O&M and spare-part lists, firmware and software versions.Ask who signs each deliverable. If the engineer won’t commit, that’s a risk.
Who owns which risks?
Split responsibilities in writing. Common risk points:- Performance guarantees vs. testing conditions.- Thermal events and fire-suppression integration.- Grid-interconnection compliance and protection coordination.- Delays from long-lead components.Make liability simple: if vendor supplies a sub-system, they own its factory acceptance and defect fixes until handover.
How is safety and compliance handled?
Ask for evidence early. Require test reports, third-party inspection records, and a certification path for the full system. Confirm the plan for abnormal events and evacuation zones. If certification requires follow-up testing, get timelines and funding responsibility in the contract.
Controls, data and cybersecurity—who does what?
Clarify scope for BMS, SCADA and communications:- Protocols supported (e.g., modbus, opcua) and firmware control.- Data retention, telemetry ownership and access rights.- Cybersecurity measures, patching, and responsibility for incidents.If the engineer cannot show a testing plan for control logic and cybersecurity, you’re likely to find errors at commissioning.
What testing and acceptance criteria matter?
Demand detailed acceptance tests and pass/fail criteria:- FAT at vendor site and witnessed by your engineer.- SAT on site with environmental and grid-variance scenarios.- Performance tests that match real operating conditions, not ideal ones.Write the acceptance criteria into payment milestones. Ambiguous criteria lead to disputes and extra cost.
Experience and references you should check
Ask for projects of similar scale and grid conditions. Request:- Final as-built drawings and commissioning reports.- Names you can call: owner, commissioning lead, operator.- Lessons learned or change orders from past projects.I’ve reviewed many proposals where references exposed gaps the paperwork hid. Real projects reveal how teams handle problems.
Common mistakes and how to avoid them
Watch these faults and do this instead:- Missing geotech or wrong foundation loads → confirm structural scope early.- Cable and busbar under-sizing → require final ampacity reports.- No coordinated fire suppression plan → integrate fire engineers in design phase.- Undefined software ownership → document who controls releases and backups.Address these in the contract and the design review to stop scope creep.
Checklist of direct questions to ask now
Use these in meetings:- Who is the lead engineer and who will be onsite for commissioning?- Can I see FAT and SAT templates and past reports?- What certifications and third-party testing are included?- Who pays for retesting and change orders caused by design errors?- Who owns control logic and firmware updates after handover?- What spare parts and training are part of the handover package?
Wrap-up: what good engineering support looks like
Good engineering support is clear, accountable, and documented. It names deliverables, assigns risks, and ties payments to measurable tests. Compare proposals on those bases. Practical partners publish scope examples and testing paths you can audit, and firms like Dunext are among those that make their processes visible so you can compare apples to apples and avoid surprises.