A battery can support several potential services, but each creates an operating claim on the same equipment. A model that adds separate revenue lines may overlook conflicts in timing or state of readiness. Before accepting the combined business case, an owner should establish which obligation takes priority and what happens when competing requests cannot all be fulfilled.
Put the services on one calendar
Identify when each proposed service requires power, stored energy or reserved capability. Use a common representation of the actual equipment and operating limits, assessed by qualified specialists. IEA flexibility analysis discusses the wider system role of storage, generation and demand. That does not establish that one asset can deliver every service simultaneously. In a hypothetical site, preserving energy for a later obligation could conflict with an immediate commercial request. The model should show that interaction instead of valuing both services as if each had exclusive access to the installation.
Give the controller a hierarchy
The dispatch rules should explain who may request action, which commitments prevail and how unavailable capacity is communicated. Supplier control systems and third-party platforms need compatible authority arrangements. An owner should understand what happens if communications fail or instructions conflict, with qualified design and operating procedures determining the response. A contract promising flexibility is incomplete if nobody has established which organisation controls the equipment at the relevant moment. The commercial hierarchy must therefore survive in the operating configuration rather than remain only in a financial-model assumption.
Price the opportunity cost
A reserved service can prevent another use even when no visible discharge occurs. Assess that foregone opportunity alongside the payment and obligations for the reservation. Review penalties, settlement and exceptions under the actual contracts with appropriate advice. DOE's storage material describes different functions, but the project must establish its own combination. A hypothetical higher-paying activity may be less attractive once its effect on another commitment is included. The comparison should use the same operational sequence rather than separately optimising every revenue line and adding the results together.
Verify the combined operating case
Test representative conflicts before relying on the full revenue stack, and keep a record of assumptions and priorities. Review the arrangement when services or counterparties change. Actual data should distinguish available capability, reserved capability and delivered service so managers can interpret missed opportunities or obligations. This does not require publishing sensitive control details. It requires a business case that can be reconciled with a workable operating policy, allowing investors to see which revenues can coexist, which depend on uncertain opportunities and which alternatives must be chosen between at particular times. When contracts expire on different dates, the model should show how the remaining obligations can be served after the original combined arrangement changes.
