Direct answer
A bankable BESS begins with the operating use case. Power, duration, duty cycle, degradation, grid services, controls, thermal and fire strategy, warranties and acceptance testing must be engineered as one system.
Decision framework
- Start with duty cycle, not container count
This stage makes assumptions, responsibilities, acceptance measures and the next decision gate explicit.
- Separate cell, BMS, PCS and EMS responsibilities
This stage makes assumptions, responsibilities, acceptance measures and the next decision gate explicit.
- Model degradation and augmentation
This stage makes assumptions, responsibilities, acceptance measures and the next decision gate explicit.
- Define fire and emergency philosophy early
This stage makes assumptions, responsibilities, acceptance measures and the next decision gate explicit.
- Write performance and acceptance tests before procurement
This stage makes assumptions, responsibilities, acceptance measures and the next decision gate explicit.
Questions the project owner should ask
- Which critical interfaces are excluded from the scope?
- Which assumptions are verified and which remain open?
- How will performance and acceptance be tested?
- Who owns change, data, configuration and lifecycle responsibility?
Frequently asked questions
Why should this be addressed early?
Because late system decisions can become more expensive changes during procurement, permitting, construction and commissioning.
The right next step
Define the need through outcome, site, grid, process, timing and risk—not an equipment list. Definova uses the first conversation to clarify critical interfaces and the required decision path.
Start a project conversation ↗