DH-142 Updating an energy community
Event description
A DSO updates the energy community information.
Parties
DSO
Datahub
Supplier
Third Party
Time limits
Effective time of the update |
|---|
The energy community update has to be reported at least 7 days and maximum 90 days before the date when the changes take effect. |
Event processing in Datahub
Step | Description |
The community’s participation in energy community calculations | The energy community and the member accounting points are taken into community calculations from the start of occurrence of the community. |
Energy community information for member accounting points | If members are added to or removed from the community, the energy community information is updated in the accounting point information of those members (the community information is either added or removed accordingly). |
Information storage
Origin of information | Information stored |
Information reported by the party | All reported information is stored in Datahub. |
Information processed by Datahub | Information on the participation of the community and its member accounting points in energy community calculations. |
Energy community information for the community’s member accounting points. |
Return of information
Party | Description | Message |
|---|---|---|
DSO | Notification of a successful or rejected update of energy community. |
Relaying of information
Party | Description | Message |
|---|---|---|
Supplier | The updated accounting point information is reported to the suppliers associated with the community’s accounting points at the effective time of the update as specified. | |
Third party | The updated accounting point information is reported to third parties associated with the accounting points at the effective time of the update as specified with consideration to the parties’ rights to information on the reported start of occurrence. |
Significant errors and consequences
Error | Consequence |
|---|---|
Wrong accounting points are linked to the energy community | The calculations are based on wrong accounting point information. |
Event cancellation
Information can be corrected by updating the community information or by terminating the energy community.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The energy community must be valid on the update date notified in Datahub. | EC.ECY.105 |
|
The energy community belongs to the reporting distribution system operator. | EC.ECY.107 |
|
The surplus calculation method cannot be changed with an update event. | EC.ECY.108 |
|
The accounting point to be reported to the energy community is recorded in Datahub and is valid on the agreement start date. | EC.MPT.115 |
|
The member consumption accounting point reported to the energy community is not in the ‘Removed from use’ status or ‘Deleted’ on the date the community enters into force. | EC.MPT.167 |
|
All accounting points in the energy community are part of the same metering grid area. | EC.ECM.101 |
|
The metering grid area must be recorded in the system and belong to the reporting distribution system operator. | EC.MPT.168 |
|
The member accounting points reported for the energy community cannot already be part of another energy community. | EC.ECM.100 |
|
The member accounting points reported for the energy community cannot be in the community twice. | EC.ECY.109 |
|
The energy community has at least two member consumption accounting points. | EC.ECM.102 |
|
The energy community has at least one member small-scale production accounting point. | EC.ECM.102 |
|
One accounting point, the sub-type of which is not ‘Virtual’, must be reported as the energy community’s surplus production accounting point. | EC.ECM.103 |
|
If a small-scale production accounting point reported as an energy community member has a related accounting point, that related accounting point cannot be part of another energy community. | EC.ECM.105 |
|
If the energy community’s surplus calculation method is SMA, the sub-type of no member accounting point reported to any community may be ‘Virtual’. | EC.ECY.110 |
|
If the surplus calculation method of the reported energy community is SMB, the reported member consumption accounting point must have a related small-scale production accounting point, which must also be reported as a member of the same energy community. (The distribution system operator must, if necessary, create an accounting point of sub-type ‘Virtual’ using event DH-121 before creating an energy community.) | EC.MPT.169 |
|
The shares of the member accounting points in the community must add up to 100%. | EC.ECM.104 |
|
The share of a single member accounting point cannot be 100%. | EC.CPF.043 |
|
|
|
|
Please observe that the list is not complete. | ||