A battery energy storage system (BESS) long-term service agreement (LTSA) should cover the whole system, not just the battery. At minimum it should define the equipment inside scope, the availability or performance commitment and how it is measured, the preventive maintenance calendar, corrective response times, remote monitoring and diagnostics, warranty administration, spare parts, capacity maintenance, the records and reports the owner receives, and what happens at renewal, transfer or exit. Anything left undefined becomes the owner's cost.
Why LTSA scope decides what an asset actually earns
A BESS only earns revenue when it is available to charge and discharge on schedule. Availability depends on far more than cells: thermal management, HVAC, fire detection and suppression, power conversion, controls and communications, switchgear, and the energy management system all have to work together. An agreement written around the battery enclosure alone can be fully honored while the asset sits unavailable because a chiller, a communications link or a fire panel is out of service and nobody is contractually responsible for it.
The same gap shows up in warranty. Most battery warranties are conditional on documented operating conditions and maintenance being performed on schedule and evidenced. If nobody owns the record, a valid claim can fail on paperwork rather than on the merits. Scope, evidence and warranty recovery are the same problem seen from three angles.
The ten areas an LTSA should define
1. Equipment boundary
List the systems inside scope by name: battery enclosures and modules, battery management system, power conversion, transformers and switchgear inside the fence, thermal management and HVAC, fire detection and suppression, controls, communications and the energy management system, plus site infrastructure such as fencing, lighting and access. State explicitly what is excluded and who is responsible for it instead. A one-line reference to "the BESS" is not a boundary.
2. Availability or performance commitment, and its measurement
If the agreement carries an availability figure, it should say how availability is calculated, over what period, from which data source, and which outages are excluded — planned maintenance, force majeure, grid or curtailment events, owner-caused delays and parts lead time. Two agreements quoting the same percentage can differ by weeks of usable time once exclusions are applied. Where the commitment is capacity or round-trip efficiency rather than availability, the test method and the measurement interval matter just as much.
3. Preventive maintenance scope and calendar
The agreement should carry a named scope per visit and a frequency, not a promise of "annual service". Typical BESS preventive maintenance includes visual and thermal inspection, torque verification on electrical connections, insulation-resistance testing, cooling-system service and leak checks, filter replacement, fire-system inspection, firmware review, state-of-charge checks and module balancing, and functional testing of protection and communications. Ask which of these are included, which are quoted separately, and what evidence is returned after each visit.
4. Corrective maintenance and response times
Define fault severity tiers, the response clock for each tier, and where that clock starts — alarm receipt, owner notification, or arrival on site. Distinguish remote response from mobilization, and state travel and after-hours terms. Round-the-clock coverage should only appear in the agreement where the service commitment behind it is confirmed in writing for that specific site.
5. Remote monitoring, diagnostics and alerting
Remote monitoring shortens diagnosis and prevents avoidable site visits, but it is not automatic. It depends on site integration, controls configuration and Modbus mapping being completed and maintained, and on user accounts, permissions and modules being configured. The agreement should state what is monitored, which alerts are automated, who receives them, and what reporting cadence the owner gets. Renewance delivers this through the Renewance Monitoring Center, with automated alerts and periodic performance reporting.
6. Warranty administration
Name the party that prepares claims, holds the evidence, tracks claim status and manages OEM correspondence. Owners frequently assume the service provider does this and discover otherwise at the first failed claim. Ask how claim validity is checked before submission, and how the maintenance evidence a warranty depends on is captured and retained. This is what warranty management in RenewanceConnect is built to digitize: claim preparation, validity checking and workflow tracking.
7. Spare parts, consumables and obsolescence
Establish which spares are held, where, by whom, and who owns the stock. Agree replenishment terms and lead-time expectations for long-lead items such as modules, power-conversion components and transformers. Then agree what happens when a part is no longer manufactured or the original supplier exits the market — obsolescence is the most common cause of an unplanned outage becoming a multi-month one.
8. Capacity maintenance and augmentation
Cells degrade. If the offtake or tariff assumes a capacity level over time, the agreement should state whether capacity testing is included, on what schedule, using which method, and whether augmentation or module replacement is inside scope, optional, or excluded. Where augmentation is excluded, say who is expected to plan and fund it, and how the service provider will coordinate with that work.
9. Records, reporting and data ownership
The owner should receive an asset hierarchy, a document repository, completed maintenance records with evidence, fault history, and approved periodic reports. Two clauses are routinely missing and routinely expensive: who owns the operating and maintenance data, and what the owner receives in a usable, structured format if the agreement ends. A service history that cannot be exported is a switching cost, and it weakens both warranty position and resale value.
10. Compliance, safety and exit
Confirm who maintains regulatory records and retention obligations, who owns the emergency response plan and coordinates with the local fire authority, and how incidents are reported and investigated. Then define the end: renewal mechanism, assignment on sale of the asset, termination rights, and a structured handover of records, spares and access at exit. Where the asset is approaching retirement, the agreement should say how service coordinates with decommissioning and end-of-life work rather than stopping at the last invoice.
A responsibility matrix beats a scope paragraph
The fastest way to expose a gap is to list every recurring task and name one accountable party per row before signing. A short version:
| Task | Questions to settle |
| Alarm monitoring and triage | Who watches, on what hours, and who is notified |
| Preventive maintenance visits | Scope per visit, frequency, evidence returned |
| Corrective response | Severity tiers, response clock, mobilization terms |
| Firmware and controls changes | Who approves, who applies, how it is recorded |
| Warranty claims | Who prepares, who holds evidence, who tracks status |
| Spares ownership | Who stocks, who funds, replenishment lead times |
| Capacity testing | Included or extra, method, schedule |
| Compliance records | Who maintains, retention period, audit access |
| Emergency response plan | Owner, review cycle, fire-authority coordination |
| Data and record handover | Format, timing, ownership at exit |
Five questions to ask before signing
- Which systems inside the fence are not in scope, and who is responsible for them?
- Show the availability calculation with every exclusion applied — what does last year's data produce?
- What evidence do I receive after each visit, and is it enough to support a warranty claim?
- Who prepares and tracks warranty claims, and what is the recovery record?
- If I terminate, what records, spares and access do I get back, in what format, and by when?
How Renewance approaches whole-system service
Renewance is an independent lifecycle service provider, not an OEM, so scope is written around the whole system and the owner's obligations rather than around one manufacturer's equipment. RenewanceServices covers preventive and corrective maintenance, remote support, fault response, diagnostics, firmware work, balancing and whole-system coordination, and connects to commissioning at the start of life and to end-of-life services at retirement. RenewanceConnect holds the asset hierarchy, document repository, maintenance records, fault workflows, warranty claims and compliance obligations, so the operating record stays with the owner.
As of September 2026, Renewance supports more than 150 sites across 30 states and works with more than 125 customers and partners.
If you are reviewing an LTSA now, or comparing an OEM offer against an independent one, the scope checklist in this article is the fastest place to start.
Frequently asked questions
What is the difference between an LTSA and a standard O&M contract?
An O&M contract typically buys defined activity — a set number of visits with a set scope. An LTSA is a multi-year commitment that usually adds performance or availability terms, warranty and spares arrangements, and obligations that extend across the asset's operating life. The label matters less than the scope and measurement clauses inside it.
How long is a typical BESS LTSA?
Terms commonly align to the battery warranty period or the offtake agreement, often five to twenty years, frequently structured in renewable blocks. What matters is whether pricing, scope and performance terms are fixed, indexed or renegotiated at each block, and what triggers a reopener.
Can an independent provider service an OEM-supplied system?
Often yes, but check the warranty terms first. Some warranties require OEM-authorized work or OEM-approved procedures for specific tasks. Confirm which activities are restricted, and have the service provider document how it coordinates with the OEM so warranty coverage is preserved.
Who is responsible if a fault is caused by a communications or controls failure?
That depends entirely on the equipment boundary and on whether controls, communications and the energy management system are named in scope. It is one of the most common unallocated risks in BESS service agreements, and it is worth resolving in writing before signature.
Talk through your agreement with us
Most scope gaps are cheap to fix before signature and expensive to fix after a fault. If you are drafting, renewing or comparing an LTSA, send us the scope and responsibility sections and we will walk them against the ten areas above, flag what is unallocated, and tell you which questions to put back to the provider. No charge, no obligation, and we will say so plainly if the agreement already covers you.
Send us your scope sections for review — tell us a little about the system and where you are in the process, and the Renewance team will come back to you.
Sources
- Renewance service scope and RenewanceConnect capability descriptions, Renewance Solutions, September 2026.
- Renewance operating figures, company-confirmed as of September 2026.
This article is general information about service-agreement scope and is not legal, engineering or regulatory advice. Contract terms, warranty conditions and applicable codes and standards vary by manufacturer, jurisdiction and project. Have your own qualified legal and engineering advisers review any agreement before signature.