Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View NB
The LF sends
- a cancellation of the order for the disconnection (case a) or
- a cancellation of the order for the reconnection (case b) of a market location, so that
- grid connection use at the market location remains possible (successful cancellation of case a) or
- the market location remains disconnected (successful cancellation of case b). If the MSB was already involved, it must be informed as well.
Process flow from the perspective of the NB
Process steps
Cancellation
NB LFZ33E_0468 Check cancellationCheck identifiers
- 39000 — Cancellation of disconnection/reconnection order · AS4
Flow
Message from LF · AS4
APERAK checks
39000→Z33
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
Load data for the check
- Read market location
GET /getMarketLocationBasic
- Read market location
Decision tree
39000→ E_0468 — Check cancellation
Response to cancellation
NB LFCheck identifiers
Flow
Message to LF · AS4
Response per decision tree
19128,19129→ E_0468 · NB · Check cancellation
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
Forwarding of the cancellation
NB MSBCheck identifiers
- 39001 — Forwarding of the cancellation · AS4
Flow
Message to MSB · AS4
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_0468 | Check cancellation |
Process information
Wording of the consolidated version, profile ch. 3.5.3.1, pp. 111–112.
Preconditions
- The affected market location is assigned to LF.
- In accordance with the grid usage contract (supplier framework agreement) concluded between LF and NB, the LF has instructed the NB to have the grid connection use at the named market location of the AN supplied by the LF
- to interrupt (case a: use case „Interruption of grid connection use (disconnect) at the instruction of the LF“) or
- to reconnect (case b: use case „Restoration of grid connection use (reconnect) at the instruction of the LF“).
- It is therefore a consuming market location.
- The reason for the disconnection order or reconnection order no longer applies, e.g. because the customer has settled the claim of the LF or the LF has accepted the AN's objection.
- The interruption of the grid connection use (case a) or restoration of the grid connection use (case b) via the affected market location has not yet taken place.
Results
- The grid connection use via the affected market location is still possible (successful cancellation of case a: disconnection order was successfully canceled), or
- the market location remains disconnected (successful cancellation of case b: the reconnection order was cancelled successfully).
Error case
Result in the error case
- If the cancellation of case a is unsuccessful:
- In order to lift the disconnection of the market location, LF starts the use case “Restoration of grid connection use (reconnect) on the instruction of LF” (case b).
- If the cancellation of case b is unsuccessful:
- For the disconnection of the market location, LF starts the use case „Interruption of grid connection use (disconnect) on the instruction of LF“ (case a).
- If the cancellation of case a is unsuccessful:
Further requirements
- The cancellation of an order can be carried out by the LF at any time, irrespective of the status at the NB, as long as the disconnection order or reconnection order from the NB has not yet been executed at the AN.
- If a disconnection order is successfully cancelled, the use case “Interruption of grid connection use (disconnect) on the instruction of the LF” is continued with the SD step "ref Billing of another service" in order to bill any services incurred up to that point.
First message
LF sends “Cancellation” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The LF cancels an order for the disconnection or reconnection of a market location before it has been carried out by the NB.
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.
Notes on this page
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.
The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created.
Applies to: 1