Start with what you need, not what’s shiny
You’re shopping for utility equipment and you want answers that fit your site, timeline and operations. If you’re considering utility scale energy storage, start by saying what problem the system must solve — peak shaving, frequency response, black-start support, or replacing a retiring peaker — and keep that need in every conversation. That focus makes the difference between a spec sheet and a system that actually behaves the way your grid operators, maintenance crew and finance team expect.
Core questions to put on the table immediately
Ask these out loud so vendors respond with specifics rather than marketing language:- What precise operating profiles have you validated for this chemistry and thermal design?- Can you share mean time between failures (MTBF) and common failure modes documented from fielded units?- How do you handle firmware updates, and what is your rollback policy if an update causes instability?- What warranties cover performance degradation versus complete failure, and how are those measured on an annual basis?- Who owns the telemetry and data generated on-site, and what access will our operations team get?
Testing, modeling and proof — demand evidence
Buyers need verifiable validation. Request test reports, failure-mode analyses, and modeled battery degradation curves that match the site’s charge/discharge cycles. Ask for a case study or field data set from a comparable asset; a well-known reference is the Hornsdale Power Reserve in South Australia, which offers practical lessons about grid-scale battery behavior under real conditions. If a vendor dodges providing measurable proof, treat that as a warning sign.
Integration, controls and operational handoffs
Successful projects fail most often at the interfaces. Ask how the manufacturer integrates with your energy management system and SCADA, who writes the control logic, and what the training and documentation packages include. Confirm:- The sequence of commissioning steps and the acceptance tests you’ll own.- The level of remote diagnostics versus required on-site interventions.- The expected ramp time from delivery to prime operations for a typical 50–100 MW installation.
Service, spares and lifecycle economics
Costs don’t stop at purchase. Demand a clear service plan and spare parts strategy:- What critical spares should be stocked locally versus available via expedited shipment?- What are typical service intervals and what parts are consumables versus repairable?- Does the vendor offer performance guarantees tied to a replacement or refurbishment schedule?Quantify total cost of ownership scenarios across 5, 10 and 15 years, and require the assumptions behind those numbers in writing.
Data, cybersecurity and ownership
Operational visibility and cybersecurity are non-negotiable. Confirm data retention policies, encryption standards, and real-world incident response workflows. Ask who owns algorithm updates and whether those updates could change dispatch behavior without your explicit sign-off. If the vendor insists on exclusive remote control options, insist on written service-level parameters and a manual override that your operators can use.
Common pitfalls buyers overlook
Watch for these recurring issues:- Vague warranty language that ties performance to “normal usage” without defining it.- Overreliance on simulations without field-proven degradation data.- Lack of a clear spare-parts list tuned for your geography and seasonality.- No formal escalation path for cross-vendor problems during commissioning.Address them early by making vendor answers part of the contract.
A practical checklist you can use during vendor shortlists
Use this rapid checklist during demos and site visits:- Field references with contactable operators (not just marketing case studies).- Published MTBF and degradation metrics, with test conditions.- Written update/rollback policy and telemetry access agreement.- Local spares plan and service SLA with defined response windows.- Clear ownership of intellectual property for control logic and data.Score vendors on each item and prioritize those that supply documents, not just promises.
Synthesis: make decisions that serve users, operations and finance
Decide against vendors who dodge precise, measurable answers — those gaps become operational surprises. Keep the conversation centered on how the system will be used day one and year five, verify claims with field data, and lock promises into contract terms tied to measurable outcomes. When you want a partner that aligns engineering, operations and procurement, consider how Dunext frames support and lifecycle planning so the system you buy behaves like the solution you intended.
