BESS availability and O&M: measuring the risk to revenue
Compare technical, contractual and service availability for a BESS, with a synthetic event log, lost-contribution cases and an O&M fee-credit calculation.
Jurisdiction: Ukraine. Sources reviewed . Periodic review required. Next scheduled editorial review: . Material rule changes require earlier review.
A battery availability percentage does not establish how much income an investor will lose during an outage or recover from a service provider. The percentage depends on the measurement boundary, denominator, derating rules and exclusions. The financial result also depends on when the event occurs, the service the battery could have delivered and the remedy actually available.
For an operating Ukrainian BESS acquisition, reconcile three records: the technical event log, the contract calculation and the cash consequence. This article addresses continuing operation after handover. Equipment acceptance and initial market qualification are separate workstreams. Ukrainian legal sources were checked through Mitralex on 31 October 2026; all numerical examples below are synthetic.
Define the capability before measuring its availability
Specify the reference import/export MW, usable AC MWh, measurement point and operating conditions. A plant can be electrically energised while unable to deliver its contracted duration, receive dispatch instructions or maintain the required state of charge. Distinguish equipment capability from the complete service obligation.
The PNNL/Sandia performance protocol treats storage performance in relation to applications and distinguishes availability from power, energy and warranty information. It is useful terminology, not a Ukrainian mandatory contract form. The calculations below use explicitly defined teaching conventions rather than claim compliance with that protocol.
Ask whether the quoted KPI is binary uptime, equivalent availability adjusted for derating, availability during nominated hours, or a contract-specific score. Identify whether planned maintenance, grid outages, communications failures, temperature limits and owner instructions are excluded, counted as available, or removed from the denominator. A percentage without those definitions cannot be compared across suppliers.
Build a log that explains each unavailable interval
Retain timestamp/time zone, affected MW/MWh, alarm, meter/EMS record, cause, responsible party, work order and restoration evidence. Split overlapping events into intervals before assigning lost capability. Keep the original log and a documented rule for the principal cause; do not charge one interval to both an OEM fault and a communications outage without defining how they interact.
For an invented 10 MW / 20 MWh usable-AC battery, consider a 30-day, 720-hour month. The events below do not overlap. Assume energy readiness and other service conditions are satisfied whenever the table counts service capability; real logs must demonstrate them separately.
Table — scroll horizontally if needed
| Event | Hours | Technical capability, MW | Capability for the assumed service, MW |
|---|---|---|---|
| Planned maintenance | 6 | 0 | 0 |
| Equipment fault | 12 | 0 | 0 |
| Partial derating | 24 | 5 | 5 |
| Grid outage | 8 | 10 | 0 |
| Lost dispatch communications | 10 | 10 | 0 |
| Other hours | 660 | 10 | 10 |
Under a binary technical convention, only the 18 fully unavailable equipment/maintenance hours are lost: (720 − 18) / 720 = 97.50%. This treats the derated unit as "up" and conceals the missing 5 MW.
Equivalent technical loss is 6 + 12 + 24 × (1 − 5/10) = 30 full-power-equivalent hours. Technical availability is therefore 95.83%. An owner-facing service measure also includes the eight grid hours and ten communications hours: (720 − 30 − 8 − 10) / 720 = 93.33%. These are different measurements of the same events, not conflicting descriptions of the log.
Suppose the illustrative O&M contract measures physical capability and excludes the six maintenance hours and eight grid hours from its denominator. Its denominator is 706 hours; its included loss is 12 + 24 × 0.5 = 24 equivalent hours. The score is (706 − 24) / 706 = 96.60%. Dispatch communications are outside that assumed physical-capability KPI. The commercial service gap remains visible in the owner's log even though that KPI does not address it.
Price the timing of the outage
Two outages with identical duration can have different consequences. Assume a twelve-hour equipment fault prevents a technically feasible, pre-defined set of earning opportunities. In scenario A, four affected hours would each have contributed EUR 700 and eight EUR 100: lost contribution is EUR 3,600. In scenario B, all twelve hours would have contributed EUR 100: EUR 1,200. The difference is EUR 2,400 with identical technical downtime.
Those contribution inputs are invented and already net of charging and relevant variable costs, before fixed costs. They are not Ukrainian market prices or a perfect-hindsight trading strategy. In a real replay, preserve the information available before dispatch, feasible charging/SoC, service commitments and excluded alternative uses. A lost gross sales figure overstates the cash loss if it ignores purchases and variable costs avoided during the outage.
Distinguish foregone operating contribution, a contractual claim, accounting recognition and cash collection. A modelled EUR 3,600 opportunity does not itself create a EUR 3,600 receivable from the O&M provider. It also does not quantify every other loss in the synthetic month.
Calculate the remedy under its own definition
Assume solely for teaching that the monthly O&M fee is EUR 10,000, the target is 99%, and the agreed fee credit is EUR 200 for each percentage point below target, prorated, capped at 10% of that fee. Using the unrounded contractual score of 96.6005666%, the credit is (99 − 96.6005666) × 200 = EUR 479.89, below the EUR 1,000 cap. These terms are not a market benchmark or statutory formula. A fee credit applied to a later invoice is not immediate cash compensation.
Legal classification matters. Civil Code article 549 defines contractual penalties; an English label such as "service credit" does not decide the treatment of a Ukrainian clause. Article 624 addresses the relationship between penalties and damages, including alternative contractual arrangements. Review the actual remedy, liability exclusions and applicable mandatory rules rather than assume every cap or label has the same effect.
Article 623 places proof of the amount of damages on the creditor and addresses foregone income. Preserve causation, the feasible earning opportunity, mitigation and the claim procedure with counsel. Under article 617, relief from liability requires the stated grounds to be proved. A broad event label does not settle causation for a particular breach or the allocation of responsibility between operator, OEM and service provider.
Test the service chain before accepting a guarantee
Table — scroll horizontally if needed
| Service point | Evidence to inspect | Acquisition consequence |
|---|---|---|
| Detection and response | Alarm coverage, staffed hours, response clock | Fast acknowledgement may leave restoration open-ended |
| Diagnosis and repair | Remote access, on-site competence, escalation and completion terms | Time to restoration drives the continuing shortfall |
| Parts and logistics | Owned/reserved stock, compatibility, delivery and customs assumptions | A warranty replacement can arrive after a valuable operating period |
| OEM / PCS / EMS interfaces | Coordinated responsibility and software/access rights | Providers may each exclude the other's fault |
| Evidence and claims | Owner data access, notices, retention, calculation and dispute process | Missing records can weaken recovery |
| Handover and change of control | Assignment/consent, licences for software, historic claims | A share sale does not establish every service right continues |
Price retained service obligations, unpaid fees, disputed claims, reserve funding and expected intervention separately. Verify safe maintenance and emergency arrangements with qualified engineers; an availability improvement never justifies bypassing required protections. Run a downside with slower restoration and delayed or unsuccessful claim recovery. A guarantee supports the investment case only within its defined capability, responsibility and collectible remedy.
Use the BESS EPC and acceptance guide, lifecycle and warranty framework and net-revenue and liquidity example. Discuss your mandate with the availability evidence, service scope and downside funding your team requires.