Energy Systems · Battery Storage Procurement
Battery proposals become comparable only after ratings, duty, scope, safety evidence, controls, life-cycle cost and contract obligations are placed on one common basis.
For: Owners, energy teams, engineers, finance, procurement, safety, IT and legal stakeholders evaluating commercial BESS offers.
Key decisions on this page
Use gates before scores
Safety, code, interconnection, technical capacity, cybersecurity and commercial viability should not be traded away by a weighted total.
Normalize performance and scope
The same MW and MWh label can hide different usable energy, degradation, auxiliaries, site work, controls and warranty rights.
Convert claims into obligations
Material promises should become evidence, acceptance tests, guarantees, remedies or clearly disclosed assumptions.
Quick answer: why battery proposals are difficult to compare
Vendors may use different AC/DC boundaries, gross and usable energy, beginning- and end-of-life ratings, duration, efficiency tests, availability exclusions, augmentation assumptions and project scope. One offer may be turnkey while another excludes utility, transformer, civil, fire-safety or controls work. Comparing headline price or nameplate capacity can therefore reward the least complete proposal.
Use the site-readiness record as the common project input and the cost guide as the common commercial boundary. This page owns the evaluation and procurement process.
1. Issue one basis of design and comparison
- Operating objectives, service priorities and measurable outcomes.
- Site drawings, connection point, load and tariff data, utility status and operating constraints.
- Required AC power, usable energy, duration, response and life-stage boundary.
- Applicable codes, owner standards, safety evidence and cybersecurity requirements.
- Scope schedule, owner-furnished items, interfaces and required optional prices.
- Commercial instructions, contract form, schedule, evidence format and acceptance tests.
Require each bidder to return a compliance matrix, exception register and assumptions schedule. Silence should not be interpreted as compliance.
2. Apply mandatory gates before weighted scoring
| Gate | Minimum evidence | Failure result |
|---|---|---|
| Identity and configuration | Named cell, module, rack, enclosure, power conversion, firmware and certification basis | Proposal cannot be matched to evidence |
| Performance fit | Required AC power and usable energy across duty, temperature and life stage | Service cannot be delivered |
| Safety and code path | Configuration-specific listing/testing, hazard information and adopted-code response | Safety or permitting path is not credible |
| Interconnection | Compatible functions, protection, export/islanding approach and utility pathway | Project cannot connect as proposed |
| Cybersecurity and data | Access, remote support, logging, updates, owner credentials and export rights | Owner cannot govern or recover the asset |
| Commercial viability | Complete scope, price basis, warranty, support and financially credible delivery party | Risk cannot be allocated or funded |
A weighted score may help distinguish proposals that pass the gates. It should not cure a failed requirement that makes the project unsafe, noncompliant, undeliverable or operationally unusable.
3. Normalize ratings and performance
| Item | Required normalized statement | Evidence or test |
|---|---|---|
| Power | Continuous AC charge/discharge at point of connection; overload separately | Datasheet, model and acceptance test |
| Energy | Gross and usable energy at beginning and end of warranty | Guarantee, degradation curve and test method |
| Duration | Usable AC energy divided by required AC power under stated conditions | Calculated on common boundary |
| Efficiency | Round-trip efficiency including defined auxiliaries and meters | Test conditions and correction method |
| Availability | Formula, exclusions, planned maintenance and remedy | Contract definition and reporting method |
| Throughput | Equivalent full-cycle method, annual/lifetime allowance and operating limits | Warranty schedule tied to duty |
| Response | Command-to-output performance and sustained requirement | Controls and site test |
| Auxiliary load | HVAC, controls and standby consumption by operating state | Measured or guaranteed values |
Do not compare a beginning-of-life usable-energy figure with an end-of-warranty guarantee. Do not compare DC battery energy with AC-delivered energy. Require all proposals to show the conversion from their native rating to the common procurement boundary.
4. Compare duty cycle and warranty together
A warranty is valuable only if it permits the planned operation. Compare depth of discharge, state-of-charge window, charge/discharge rate, temperature, throughput, operating hours, services and calendar term. Identify owner obligations, data needed for a claim and exclusions created by control changes, grid events or maintenance.
| Question | Why it matters | Required commercial response |
|---|---|---|
| What capacity is guaranteed and where measured? | Determines actual service at the site | End-of-term value, method, tolerance and remedy |
| What duty is permitted? | Controls whether the economic model is warrantable | Throughput/cycle and operating-envelope schedule |
| Is augmentation included? | Shifts future capital and outage risk | Quantity, timing, labor, controls, testing and disposal scope |
| How is availability calculated? | Changes revenue and service confidence | Formula, exclusions, reporting and liquidated remedy |
| Who proves a defect? | Can make a nominal guarantee impractical | Data access, investigation process, cost and timeline |
| What survives vendor change or insolvency? | Affects long-term operability | Escrow, licenses, parts, documentation and transition rights |
5. Normalize the complete project scope
Create a responsibility matrix covering engineering, studies, permits, utility coordination, equipment, transformer, switchgear, civil work, communications, cybersecurity, safety systems, installation, commissioning, operations, software, spares and decommissioning. Each item should be included, excluded, owner-furnished or optional—not left as “by others” without a named party.
The DOE procurement checklist and technical specification are useful starting prompts, but they are customizable federal resources. They must be adapted to the project, jurisdiction, owner requirements and procurement route rather than copied as universal contract language.
6. Review safety evidence for the proposed configuration
| Evidence | Check | Do not assume |
|---|---|---|
| System certification/listing | Exact model, ratings and configuration match | A similar product certificate covers the offer |
| UL 9540A or other propagation evidence | Cell, module, unit, installation level, spacing and observed hazards | A test is a universal pass/fail safety certificate |
| Hazard and mitigation documents | Detection, ventilation, explosion/fire strategy and emergency actions align | Vendor narrative replaces code and fire-protection review |
| Installation drawings | Separation, access, protection, water, drainage and responder approach match assumptions | A compact layout is automatically permit-ready |
| Change control | Substitutions and firmware/configuration changes preserve evidence basis | Post-award changes are immaterial |
7. Test controls, data and economic claims
Require a transparent explanation of dispatch logic, input data, forecast horizon, constraints, state-of-charge reserve and fallback behavior. Re-run vendor savings or revenue results using the same load, tariff, degradation, availability, efficiency and value-stream rules. A result that cannot be reproduced from inputs and logic should not be scored as proven value.
Test communications loss, bad meter data, delayed signals, conflicting commands and recovery. Confirm owner access to raw meter and event data, settings, credentials, configuration history and export. Apply OT security requirements to remote access, software updates and incident recovery.
8. Compare delivery and commercial risk
| Area | Questions | Decision evidence |
|---|---|---|
| Price | Validity, currency, tax, tariffs, escalation, contingency and optional work | Normalized cost schedule and assumptions |
| Schedule | Long-lead items, utility dependencies, permits, milestones and delay responsibility | Integrated schedule and critical-path ownership |
| Payment | Deposits, milestones, security, retention and acceptance linkage | Cash-flow and protection aligned with delivered value |
| Performance | Capacity, efficiency, availability, response and service guarantees | Measurable definitions and remedies |
| Support | Maintenance, spares, remote service, technician coverage and response | Service-level schedule and evidence of capability |
| Liability and insurance | Caps, exclusions, indemnity, cyber and property coverage | Legal and insurance review |
| Change and exit | Substitution, software licensing, data portability, termination and insolvency | Owner can operate, transition and recover the asset |
9. Define acceptance before award
- Document and design-review milestones before manufacture and construction.
- Factory tests appropriate to the integrated equipment and controls.
- Site tests for protection, alarms, emergency stop, communications and fail-safe behavior.
- Installed power, usable-energy, efficiency, response and control-mode tests at the agreed boundary.
- Integration tests with solar, generator, building load, utility or market interfaces.
- Training, credentials, as-built drawings, settings, manuals, spare-parts and emergency records.
- Punch-list, provisional acceptance, final acceptance, warranty start and remedy process.
Acceptance should create a baseline for future warranty and performance reporting. If the test method is not specified before award, the owner may have little leverage when parties disagree after installation.
10. Use a transparent scoring and decision record
| Category | Example evidence | Scoring caution |
|---|---|---|
| Technical fit | Normalized performance, integration and controls | Do not reward unverified optional capability |
| Safety and deliverability | Configuration evidence, permit path, site and utility response | A gate may still remain conditional rather than scored |
| Whole-life cost | Normalized capital, operating, augmentation, downtime and exit | Keep uncertain revenue separate from committed cost |
| Delivery capability | Team, schedule, supply chain, references and quality controls | Past projects must be comparable and verified |
| Operations and support | Maintenance, data, diagnostics, spares and service levels | A low service price may transfer workload to the owner |
| Commercial terms | Guarantees, remedies, liability, change and exit | Legal risk is not fully represented by a numeric score |
Use the Comparison Methodology, Universal Vendor Comparison Worksheet, Technology Evaluation Scorecard and TCO Worksheet. Preserve the evidence, exceptions, clarification answers, score changes and reasons for the final decision.
Hard rejection conditions
Reject or hold a proposal where:
Clarification may resolve some items, but the evaluation record must not conceal them.
- Identity or configuration cannot be matched to certification, testing and warranty evidence.
- Required AC power or usable energy is not demonstrated at the agreed life-stage boundary.
- The offered duty conflicts with warranty limits or degradation assumptions.
- Major site, utility, safety, integration or commissioning scope is excluded without ownership and price.
- Savings or revenue cannot be reproduced from common data and assumptions.
- Owner lacks operational data, credentials, configuration records or transition rights.
- Acceptance tests, guarantees or remedies are undefined.
- Material exceptions remain hidden in marketing material or inconsistent attachments.
Limitations
This guide supports a structured evaluation; it does not approve a vendor, contract, design, safety case or investment. Qualified technical, fire-protection, cybersecurity, insurance, legal, financial and procurement review is required for a live project.
Prepare the evidence before final award
Use the sibling pages to close unresolved technical and commercial assumptions.
Check the system terms
Return to components, ratings, degradation, controls and acceptance boundaries.
Verify site inputs
Resolve utility, layout, electrical, code and operating conditions.
Recalculate whole-life cost
Use one cost boundary and the same performance assumptions.
The wider Technology Procurement Process explains governance, market engagement, contract award, implementation and closeout beyond this technology-specific comparison.
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.
- 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
- Distributed Energy Interconnection Checklist — 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
- Handbook 135: Life-Cycle Costing Manual for the Federal Energy Management Program — 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 technical specifications, safety standards, market evidence, warranties, utility requirements, cybersecurity guidance or procurement authority changes. Organizational author: Future Green Technology, published by Zenith Star Media.