|
|
|
The following figure shows the power limit module (ic-pwlm) that reuses the data-point concept from the ic-data module. The ic-pwlm module also reuses the device and state concepts from SAREF, extending the `saref:State` class with additional states needed by the InterConnect pilots for the power limit use case, namely `ic-pwlm:PowerLimitState` and `ic-pwlm:FailsafeState`.
|
|
|
|
The following diagram shows the power limit module (ic-pwlm) that reuses the data-point concept from the ic-data module. The ic-pwlm module also reuses the device and state concepts from SAREF, extending the `saref:State` class with additional states needed by the InterConnect pilots for the power limit use case, namely `ic-pwlm:PowerLimitState` and `ic-pwlm:FailsafeState`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A power limit (`ic-pwlm:PowerLimit`) is defined as the maximum value for power consumption and/or production that must not be exceeded by e.g. a (group of) device(s), a building, or also a district. The value of a power limit is expressed using a `ic-data:DataPoint` (see Section 4.2. Optionally, the limit may come with a time period of validity based on duration (`time:Duration`). This is e.g. used for grid congestion management. Additional constraints may apply, such as that premises may be subject to a contractual limitation to power consumed and/or produced. This is shown in Figure 10 using the `ic-pwlm:isBoundTo` relation between a device and its contractual power limit (`ic-pwlm:ContractualPowerLimit`). Moreover, a device may have nominal power consumption and/or production values (`ic-pwlm:NominalPowerLimit`) that are defined by the manufacturer and must not be exceeded, so that the power limit must stay within these constraints. A device must acknowledge (ACK) a received power limit. Figure 9 further shows that a power limit is associated with a state (`ic-pwlm:PowerLimitState`), meaning that a power limit may be toggled active or inactive.
|
|
|
|
A power limit (`ic-pwlm:PowerLimit`) is defined as the maximum value for power consumption and/or production that must not be exceeded by e.g. a (group of) device(s), a building, or also a district. The value of a power limit is expressed using a `ic-data:DataPoint`. Optionally, the limit may come with a time period of validity based on duration (`time:Duration`). This is e.g. used for grid congestion management. Additional constraints may apply, such as that premises may be subject to a contractual limitation to power consumed and/or produced. Moreover, a device may have nominal power consumption and/or production values (`ic-pwlm:NominalPowerLimit`) that are defined by the manufacturer and must not be exceeded, so that the power limit must stay within these constraints. A device must acknowledge (ACK) a received power limit. A power limit is associated with a state (`ic-pwlm:PowerLimitState`), meaning that a power limit may be toggled active or inactive.
|
|
|
|
|
|
|
|
In case the communication between a device and the energy manager is interrupted, fail-safe values apply (`ic-pwlm:FailsafePowerLimit`) and the device enters fail-safe state until the communication is re-established.
|
|
|
|
|
|
|
|
For all values, the passive sign convention is used, i.e., positive power values apply to consumption and negative values apply to production. However, since this convention can lead to misinterpretations when exchanging data, we recommend to explicitly set for a certain power value whether it is production or consumption by using one the two additional instances `ic-data:production` and `ic-data:consumption` that we have defined as `rdf:type` of the `ic-data:Usage` class.
|
|
|
|
|
|
|
|
For all values, the passive sign convention is used, i.e., positive power values apply to consumption and negative values apply to production. However, since this convention can lead to misinterpretations when exchanging data, we recommend to explicitly set for a certain power value whether it is production or consumption by using one the two additional instances `ic-data:production` and `ic-data:consumption` that we have defined as `rdf:type` of the `ic-data:Usage` class. |
|
|
\ No newline at end of file |
