By AGILE Consulting Engineers, Solar PV and Battery Energy Storage Systems (BESS) specialists.
Most battery energy storage system (BESS) projects that run into trouble weren’t undone by exotic technical problems. They were undone by ordinary, well-documented mistakes made early, often at concept or preliminary design, that only became visible once construction or connection approval was already underway. The pattern repeats often enough across projects that it’s worth naming the mistakes directly rather than describing best practice in the abstract.
Table of Contents
- Sizing Around Nameplate Capacity Instead of Use Case
- Treating Grid Connection as an Afterthought
- Underestimating Protection and Control Complexity
- Skipping Site-Specific Investigation
- Treating Fire Safety as a Late-Stage Add-On
- Inconsistent Documentation Across Design Disciplines
- Skipping Independent Review on Complex Projects
- What to Do Next
- FAQ
Sizing Around Nameplate Capacity Instead of Use Case
It’s common for a BESS project to start with a target capacity in kilowatt-hours before the use case has been properly defined, often based on budget, available space, or a round number that sounds reasonable. The trouble is that power and energy requirements for demand reduction, backup resilience, solar export management, and frequency control ancillary services (FCAS) participation are genuinely different problems, and a system sized without reference to actual interval load data or a clearly prioritised use case tends to under-deliver on whichever objective mattered most to the business case. Working backward from a capacity figure instead of forward from a defined use case is one of the more expensive mistakes to unwind once equipment has already been ordered.
Treating Grid Connection as an Afterthought
Grid connection requirements, particularly for larger or standalone systems, can materially affect system design, site layout and even commercial viability. Projects that finalise equipment selection and layout before engaging with the distribution network service provider (DNSP) risk discovering late that export or import limits, interface protection requirements, or fault level constraints require a redesign. AGILE’s guide to DNSP grid connection design requirements for solar and BESS systems sets out what a connection-ready design actually needs to account for, and engaging with these requirements early, even informally, tends to save far more time than it costs.
Underestimating Protection and Control Complexity
Because a battery can both import and export power and often needs to coordinate with existing site protection and control systems, protection design for a BESS is rarely a simple extension of standard electrical installation practice. Anti-islanding, fault ride-through behaviour and coordination with existing switchboard protection all need deliberate design attention, and projects that treat the battery’s control system as a self-contained black box supplied by the equipment vendor often find that its default behaviour doesn’t actually match the site’s protection philosophy or the DNSP’s requirements. Resolving this after equipment has been selected is considerably harder than designing for it from the outset.
Skipping Site-Specific Investigation
Ground conditions, existing infrastructure capacity, and site access constraints all affect what’s actually buildable, and assuming a standard design will transfer directly onto a new site without site-specific investigation is a recurring source of cost overrun. Civil and foundation design in particular depends on actual site conditions rather than generic assumptions. Structural and civil issues discovered during construction are typically far more disruptive and costly to resolve than the same issues identified during design, when there’s still flexibility in layout and equipment selection.
Treating Fire Safety as a Late-Stage Add-On
Fire safety requirements for a BESS, covering separation distances, enclosure construction and emergency response planning, are sometimes treated as a compliance step to be addressed once the general layout is already fixed. This gets the sequence backward. Separation distances and enclosure requirements can directly affect how much space a system needs and where it can be sited relative to buildings and boundaries, which means fire safety needs to inform the layout, not be checked against it after the fact. Projects that leave fire engineering input until late in design frequently need to revisit decisions that were otherwise settled.
Inconsistent Documentation Across Design Disciplines
On more complex projects involving electrical, civil, control and structural design working in parallel, it’s common for documentation to drift out of alignment, a single line diagram that doesn’t match the switchboard schedule, or a control philosophy document that references equipment that changed after the electrical design was finalised. These inconsistencies are a frequent trigger for requests for further information from DNSPs, councils and certifiers, adding delay that’s entirely avoidable with better document control during design. A coordinated design process, where disciplines are cross-checked against each other rather than developed in isolation, is one of the more reliable ways to avoid this.
Skipping Independent Review on Complex Projects
For larger or more complex projects, particularly those delivered through an engineering, procurement and construction (EPC) contractor, skipping independent technical review of the design can leave an asset owner without their own line of sight into whether the design actually meets their requirements and relevant standards. AGILE’s article on why independent engineering review matters for solar and BESS projects covers this in more detail, and it’s a particularly relevant safeguard where the same party responsible for construction is also responsible for the design, since that arrangement removes a natural check that an independent reviewer would otherwise provide.
What to Do Next
Most of the mistakes above share a common thread: they’re decisions made early, under time or budget pressure, without the technical input that would have surfaced the issue before it became expensive to fix. Bringing engineering rigour into a project from concept through to detailed design, rather than treating it as a late-stage compliance exercise, is the basis of AGILE’s BESS engineering service.
FAQ
What’s the single most common mistake in early-stage BESS design?
Sizing the system around a target capacity figure before the use case, whether that’s demand reduction, backup resilience or market participation, has been clearly defined and supported by actual interval load data. This tends to produce a system that doesn’t fully deliver on the objective the business case was built around.
Why does grid connection need to be considered so early in design?
Because export and import limits, protection requirements and fault level constraints set by the distribution network service provider can directly affect system sizing, layout and equipment selection. Finalising a design before understanding these requirements risks a costly redesign later in the project.
Can protection design just be left to the equipment vendor’s default settings?
Not reliably. Default settings from an equipment vendor may not match a specific site’s existing protection philosophy or the relevant DNSP’s requirements, and anti-islanding and fault ride-through behaviour typically need to be deliberately coordinated with the rest of the site’s protection system.
How much does site-specific investigation actually matter for a standard-looking project?
It matters more than it appears to on paper. Ground conditions, existing switchboard capacity and access constraints vary significantly between sites even for similarly sized systems, and issues discovered during construction are typically far more expensive to resolve than the same issues identified during design.
When should fire safety be factored into the design process?
As early as the concept or preliminary layout stage, since separation distances and enclosure requirements can directly affect site layout and available space, rather than being treated as a compliance check applied to a layout that’s already been finalised.
Is independent engineering review necessary if a reputable EPC contractor is delivering the project?
It’s a useful safeguard, particularly on larger or more complex projects, because it gives the asset owner an independent line of sight into whether the design meets their requirements and relevant standards, which is especially valuable when the same party is responsible for both design and construction.
