GroupReserve
Package: PowerOperationsOpenAPIModels · Source: Operations/Service/GroupReserve.json
A reserve product met by a group of individual reserves. The group requirement is additional to each member’s own requirement, and a device contributing to a member reserve also counts toward the group. Membership is carried by ServiceAssociation rows, not by a field here.
Properties
| Property | Type | Required | Unit | Description |
|---|---|---|---|---|
id | integer | yes | — | Unique integer identifier for this component. |
name | string | yes | — | Name of the component. Components of the same type (e.g., PowerLoad) must have unique names, but components of different types (e.g., PowerLoad and ACBus) can have the same name. |
available | boolean | yes | — | Indicator of whether the component is connected and online (true) or disconnected, offline, or down (false). Unavailable components are excluded during simulations. |
requirement | number | yes | MW | The value of required reserves. Units: MW. |
variable | CostCurve | — | — | Operating reserve demand curve for the group, either static or time-series-backed. A group carrying a curve is elastic: its requirement is priced by the curve rather than enforced. Time series values are carried via time_series_associations in the sidecar, never inline. Omit when the group has no demand curve. |
reserve_direction | string (ReserveDirection) | yes | — | Whether the reserve is an upward, downward, or symmetric reserve product. |