OfflineReserve

Package: PowerOperationsOpenAPIModels · Source: Operations/Service/OfflineReserve.json

A non-spinning reserve product from devices not currently synchronized with the system but able to come online quickly after an unexpected contingency. Upward only, so unlike OnlineReserve there is no reserve direction. The procurement requirement is static unless a requirement time series is attached, in which case requirement is the scaling factor.

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.
time_frame	number	yes	min	The saturation time frame to provide reserve contribution. Units: min.
requirement	number	—	MW	The value of required reserves. Units: MW.
variable	CostCurve	—	—	Operating reserve demand curve, either static or time-series-backed. Time series values are carried via time_series_associations in the sidecar, never inline. Omit when the reserve has no demand curve.
sustained_time	number	—	min	The time reserve contribution must be sustained at a specified level. Units: min.
max_output_fraction	number	—	—	The maximum fraction of each device’s output that can be assigned to the service.
max_participation_factor	number	—	—	The maximum portion [0, 1.0] of the reserve that can be contributed per device.
deployed_fraction	number	—	—	Fraction of service procurement that is assumed to be actually deployed. Most commonly, this is assumed to be either 0.0 or 1.0.