DH-812 Customer authorization notification – third party
Event description
A third party registered in Datahub reports an authorization issued by a customer to Datahub.
Parties
Third party
Datahub
Time limits
Effective time of the update |
|---|
The start time cannot be in the past or further than 90 days into the future. |
The maximum validity of the authorization is:
|
Information storage
Origin of information | Information stored |
Information reported by the party | A new authorization is created based on the reported information. If an authorization already exists for the same party, customer, accounting point and purpose, the new authorization will overwrite the previously reported one. If the reported authorization involves multiple customers, Datahub stores the authorization information separately for each customer and accounting point pair. |
Return of information
Party | Description | Message |
|---|---|---|
Third party | Notification of successful or rejected notification. |
Significant errors and consequences
Error | Consequence |
|---|---|
The authorization is reported for the wrong accounting point. | The party receives information it is not entitled to. The party must cancel the authorization and delete the information that it has already retrieved from Datahub. |
A party reports an authorizations without actually having been issued an authorization by a customer. | The party is criminally liable for its actions in cases of abuse. |
Event cancellation
If the start date is in the future, the cancellation can be done by an update that sets the end date to be the same as the start date. A valid authorization cannot be cancelled, but it can be terminated on the current date.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The accounting point is recorded in Datahub. | EC.MPT.115 |
|
The accounting point must not have the status ‘Removed from use’ or ‘Deleted’. | EC.MPT.120 |
|
If the type of authorization is contract tendering as a service (the customer has a contract for the metering point) or energy reporting, all reported customers must have a sales or network contract for the metering point for the entire duration of the reported authorization. | EC.AGR.403 |
|
The maximum validity of an energy-reporting-type authorization is 30 days. | EC.AGR.404 |
|
A third party (DH-812) registered in the Datahub can report an authorization for the following purposes:
| EC.AGR.405 EC.AGR.408 |
|
The start time cannot be in the past or further than 90 days into the future. | EC.AGR.406 |
|
The request must specify at least one customer. | EC.AGR.407 |
|
If the type of authorization is ‘Invitation to tender’ (customer does not have an agreement for the accounting point), none of the reported customers may hold a sales or grid agreement at the accounting point for the entire reported authorization period. | EC.AGR.411 |
|
The maximum duration of the authorization is 30 days. | EC.AGR.412 |
|
The authorizing organization must be active for the entirety of the authorization period. | EC.AGR.418 |
|
The authorization period cannot overlap with more than one existing authorization period if they have the same authorization reason and customer. | EC.AGR.419 |
|
The termination date conforms to the rules. | EC.AGR.421 |
|
An authorization cannot be notified in a situation in which the accounting point already has, during the reported period, an unconfirmed grid agreement for another customer awaiting confirmation from the distribution system operator. | EC.CAA.434 |
|
The customer must be recorded in Datahub. | EC.CUS.113 |
|
All reported customers must have different customer identifiers. | EC.CUS.114 |
|
The reported customers are business customers. | EC.CUS.135 |
|
The customer cannot be flagged as confidential for the reported authorization period. | EC.CUS.139 |
|
Please observe that the list is not complete. | ||