Billing of grid usage — LF view
Process flow from the perspective of the LF
Process steps
ongoing meter reading values
LF NBMSCONSZ10Z18Z27Z33Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic - Read market location
GET /getMarketLocationBasic - Read meter
GET /getCounterBasic
- Read metering location
APERAK checks
13002,13006,13008→MSCONS13009→Z10— APERAK check: Is location known ?13009→Z1813009→Z2713009→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Grid usage invoice
LF NBZ10Z25Z26Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
31002,31001→Z10— APERAK check: Is location known ?31002,31001→Z2531002,31001→Z26
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Response
LF NBFlow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe backend triggers this step with this event.
Message to NB · AS4
Response per decision tree
33002→ E_3018 · Check grid usage settlement
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Notification that the original grid usage invoice was correct
LF NBZ33Check identifiers
- 29001 — Rejection of REMADV · AS4
Flow
Message from NB · AS4
Response per decision tree
29001→ E_3035 · Check of other data relevant to the billing period and/or retroactive notifications
APERAK checks
29001→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Response
LF NBFlow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe backend triggers this step with this event.
Message to NB · AS4
Response per decision tree
33002→ E_3036 · Check grid usage invoice again
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Cancellation of the original invoice
LF NBZ33Check identifiers
- 31004 — Cancellation invoice · AS4
Flow
Message from NB · AS4
APERAK checks
31004→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Response
LF NBFlow
Prozessauslöser
START_VERSAND_ANTWORT_NNAThe backend triggers this step with this event.
Message to NB · AS4
Response per decision tree
33002→ E_3038 · LF · Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required)
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_3018 | Check grid usage settlement |
| E_3035 | Check of other data relevant to the billing period and/or retroactive notifications |
| E_3036 | Check grid usage invoice again |
| E_3038 | Check whether a response to the cancellation is required (Based on electricity EBD: E_0459_Check whether a response to the cancellation is required) |
Process information
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
- View NB — NB
Notes on this page
The source provides no use case profile for this process — objective, precondition and result are not recorded there.
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.
Applies to: 6