Energy Systems · Battery Storage Site Readiness
Site readiness is the evidence that a battery project can be connected, permitted, built, operated, maintained and supported at the proposed location. It is not a box checked by a single site visit.
For: Owners, facilities, engineering, energy, safety, IT, finance and procurement teams deciding whether a commercial BESS can proceed to firm design or tender.
Key decisions on this page
Define the operating objective
Readiness cannot be assessed until required power, usable energy, services, export, islanding and resilience behavior are clear.
Resolve critical interfaces early
Physical layout, utility, electrical, fire-code, controls and emergency-response pathways can become schedule and budget blockers.
Convert unknowns into controlled conditions
Every unresolved item needs an owner, due date, evidence requirement and commercial treatment before proposals are called firm.
Quick answer: what does “site ready” mean?
A site is ready for the next project stage when the team has sufficient verified information to define the system, obtain comparable proposals, understand material risks and identify a credible path through utility, code, permitting, construction, commissioning and operation. Readiness is not the same as final design or regulatory approval.
Start with the operating service and system boundary in the commercial BESS explainer. This page owns the evidence register for data, physical, electrical, interconnection, safety, controls, operations and procurement readiness.
1. Define the operating objective and boundaries
| Question | Evidence | Readiness result |
|---|---|---|
| What services are required? | Load, tariff, renewable, outage or program analysis | Named objectives and priorities |
| What rating is needed? | Required AC power, usable energy, duration and response at stated life stage | Common performance boundary |
| Will the system export or island? | Utility discussion, one-line concept and operating modes | Interconnection and protection pathway identified |
| Which loads are involved? | Meter and load boundary, critical-load list and operating schedules | No hidden load or meter assumption |
| How will services conflict? | State-of-charge reserve and dispatch-priority policy | Controls requirement is testable |
A project described only as “a 1 MWh battery” is not sufficiently defined. State whether the value is gross or usable, where it is measured, which power rating applies and what capability is required at the end of the warranty or analysis period.
2. Establish the data baseline
Collect interval load and generation data at a granularity suitable for the intended service. Identify missing periods, meter changes, unusual operations, planned loads and seasonal effects. Verify current tariff components, demand windows, ratchets, export treatment and any program rules with the serving utility or supplier.
Poor data can produce a battery that is too small to deliver the service, too large to earn an acceptable return, or controlled against a peak that does not affect the bill. Document data quality, estimation and the period used in the model.
3. Test the physical site
| Domain | Questions | Potential blocker |
|---|---|---|
| Footprint and access | Clearances, maintenance access, crane/replacement route, emergency approach and future expansion | No safe installation or replacement route |
| Ground and structure | Foundation, bearing, rooftop loading, seismic, wind, snow and settlement | Unverified structural capacity or unsuitable ground |
| Environmental exposure | Flood, drainage, wildfire, heat, cold, corrosion, dust and water | Hazard exposure outside product/design basis |
| Adjacency | Occupied buildings, property lines, public access, critical equipment and ignition sources | Layout cannot meet adopted requirements or insurer expectations |
| Site operations | Traffic, loading, noise, lighting, security and construction phasing | Installation or emergency access conflicts with operations |
Photographs and a conceptual layout are useful, but readiness requires dimensions, elevations, access constraints and ownership boundaries. The layout should reserve space for transformer, switchgear, power-conversion equipment, detection, network equipment and future augmentation where required.
4. Review the electrical system
- Current single-line diagram and verified utility service, transformer, switchgear, bus and feeder ratings.
- Connection point, voltage, phase, cable route, isolation, metering and protection concept.
- Available fault current, protection coordination, grounding, harmonics and arc-flash implications.
- Interaction with solar, generators, UPS, EV charging, building controls and demand-management systems.
- Space and ownership for new transformer, switchgear, disconnects, transfer equipment or critical-load distribution.
- Existing equipment condition, planned replacement and outage windows required for construction.
A spare breaker position or an arithmetic difference between service rating and peak load is not a complete capacity study.
5. Start utility and interconnection work early
DOE’s distributed-energy interconnection checklist organizes questions by the utility process. A BESS application may require studies, protection settings, telemetry, operating limits, witness tests, agreements and upgrades. Requirements depend on size, export, islanding, voltage, utility and jurisdiction.
A zero-export control may change the review but does not automatically eliminate it. Confirm how export limitation is enforced, what happens when communications or the controller fails, whether reverse power can occur during transients and which party owns testing and ongoing compliance.
| Item | Required record | Commercial treatment if unresolved |
|---|---|---|
| Application pathway | Utility contact, process, data request and current status | Named pre-award condition and schedule risk |
| Capacity and upgrades | Utility response or study scope | Allowance with clear ownership; not “by utility” without evidence |
| Protection and controls | Concept, required functions and settings authority | Technical gate before final design |
| Metering and telemetry | Data, communication and testing requirements | Included scope and recurring cost |
| Agreement and operating limits | Export, dispatch, maintenance and notice obligations | Contract and operating-plan requirement |
6. Confirm code, permit and safety pathway
Identify the authority having jurisdiction and the adopted building, fire and electrical codes. Confirm product listing, thermal-runaway and propagation evidence, hazard analysis, separation, access, detection, ventilation or explosion control, suppression, water, signage, emergency procedures and responder coordination as applicable.
UL 9540, UL 9540A and NFPA 855 may be part of the US compliance framework, but the project team must verify the adopted editions and local amendments. The test configuration must be compared with the proposed cell, module, rack, enclosure, spacing, protection and software configuration. A certificate title alone is not sufficient evidence.
7. Define controls, communications and cybersecurity
| Requirement | Evidence | Failure condition |
|---|---|---|
| Control priorities | Written hierarchy for cost, resilience, solar, generator and utility commands | Conflicting services have no deterministic priority |
| Communications loss | Local fallback, safe state and recovery test | System depends on cloud or external signal without safe fallback |
| Access and identity | Roles, authentication, remote access and credential ownership | Vendor retains uncontrolled access or owner lacks credentials |
| Data and time | Meters, timestamps, retention, event history, export and API | Performance cannot be reproduced or audited |
| Lifecycle security | Inventory, logging, updates, vulnerability process, backups and end-of-support | No owner for patch, incident or recovery actions |
Because controls interact with physical electrical equipment, security decisions must preserve safe and reliable operation. Apply OT security principles, not only generic office-IT controls.
8. Prepare operations, maintenance and emergency response
- Named asset owner, operator, maintainer, network contact and emergency contacts.
- Inspection, preventive maintenance, alarm response, fault escalation and service response times.
- Access to diagnostic data, manuals, spares and qualified technicians.
- Emergency shutdown, isolation, re-entry, damaged-equipment and stranded-energy procedures.
- Training for site staff and coordination with emergency responders.
- Warranty reporting, performance review, software support and configuration change control.
- Decommissioning, transport, recycling or disposal and site-restoration responsibility.
9. Convert readiness findings into procurement information
The request for proposals should include verified drawings, load data, operating requirements, utility status, code assumptions, owner standards, site constraints, owner-furnished items and acceptance tests. Unknowns should appear in a controlled register rather than being hidden inside vendor assumptions.
| Status | Meaning | Permitted next action |
|---|---|---|
| Confirmed | Current evidence supports the requirement | Use as bid information and verify during design |
| Conditional | A credible path exists but evidence or approval remains | Proceed only with named condition, owner, due date and cost treatment |
| Unresolved | Material information is missing or conflicting | Do not treat related price or schedule as firm |
| Blocking | No credible path currently supports the requirement | Redesign, relocate, change service or stop the project stage |
Readiness failure conditions
Do not release a firm tender or investment estimate when:
These conditions materially undermine comparability or deliverability.
- The service, rating, connection point or operating modes remain undefined.
- Load, tariff or generation data is too incomplete for the claimed value stream.
- Physical layout, structural basis, access or environmental exposure has not been tested.
- Utility process, major upgrades or export/islanding requirements are unknown.
- The adopted code path and configuration-specific safety evidence are not identified.
- Control priorities, communications-loss behavior or cybersecurity ownership are unclear.
- Emergency response, maintenance, replacement access or end-of-life responsibility is absent.
- Unknowns have no owner, due date, evidence requirement or commercial treatment.
Limitations
This readiness guide does not certify a site, approve electrical design, determine compliance or guarantee utility capacity. Qualified engineering, fire-protection, code, structural, civil, cybersecurity, insurance and legal review may be required.
Use the readiness record in the next decision
Proceed only when the related pages use the same verified boundary.
Confirm the system boundary
Check components, ratings, control, safety and acceptance terms.
Update the project budget
Replace allowances with site, utility and safety evidence.
Issue comparable requirements
Carry confirmed facts, conditions and tests into proposal evaluation.
Record pass/fail gates and unresolved evidence in the Technology Evaluation Scorecard, and carry vendor scope differences into the Universal Vendor Comparison Worksheet. The wider Energy Storage hub keeps the site decision connected to the intended service, while the Technology Procurement Process carries confirmed and conditional findings into tender and acceptance.
Sources and evidence
Primary and authoritative references used for this page are listed below. Recheck current versions, local codes, tariffs and program terms before a live project decision.
- Distributed Energy Interconnection Checklist — U.S. Department of Energy Federal Energy Management Program
- Battery Energy Storage System Procurement Checklist — U.S. Department of Energy Federal Energy Management Program
- Lithium-ion Battery Storage Technical Specifications — U.S. Department of Energy Federal Energy Management Program
- On-Site Energy Storage Decision Guide — U.S. Department of Energy Better Buildings
- UL 9540A Test Method for Battery Energy Storage Systems — UL Solutions
- Energy Storage System Testing and Certification — UL Solutions
- NFPA 855 Standard Development — National Fire Protection Association
- SP 800-82 Rev. 3: Guide to Operational Technology Security — National Institute of Standards and Technology
- Project Control authority: approved page map, complete page criteria and page-rules addendum — Future Green Technology
Reviewed and updated 29 June 2026. Recheck when utility processes, adopted codes, safety evidence, site conditions, operating objectives, control architecture or emergency guidance changes. Organizational author: Future Green Technology, published by Zenith Star Media.