Restoration of grid connection use (reconnect) at the instruction of LF — View LF
In accordance with the grid usage contract (supplier framework contract) concluded between the LF and the NB, the LF instructs the NB to restore the grid connection use at the named market location of the AN supplied by the LF without delay. The NB checks the conditions on site on the day of the reconnection and, where necessary, makes several attempts to restore the grid connection use. The NB informs the LF, where applicable the MSB and where applicable the ÜNB about the result of the reconnection order.
Process flow from the perspective of the LF
Process steps
Reconnection order
LF NBCheck identifiers
- 17117 — Reconnection order · AS4
Flow
Prozessauslöser
START_ENTSPERRAUFTRAGThe backend triggers this step with this event.
Message to NB · 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
Response to reconnection order
LF NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19116,19117→ E_0497 · NB · Check reconnection order
APERAK checks
19116,19117→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
3 Information on the reconnection order
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21040 — Reconnection order info · AS4
Result of the reconnection order
LF NBZ10Z17Z18Check identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Message from NB · AS4
Response per decision tree
21039→ E_0499 · NB · Check whether the reconnection order was successful
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
21039→Z10— APERAK check: Is location known ?21039→Z1721039→Z18
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0497 | Check reconnection order |
| E_0499 | Check whether the reconnection order was successful |
Process information
Wording of the consolidated version, profile ch. 3.5.2.1, pp. 109–110.
Preconditions
- The disconnected market location is assigned to LF.
- The grid connection use is interrupted by means of the use case „Interruption of the grid connection use (disconnect) on the instruction of the LF“. It is therefore a consuming market location.
- The costs of the reconnection are charged to the LF as part of the disconnection.
Results
The grid connection use via the affected market location is possible again.
Error case
Result in the error case
- The grid connection use via the affected market location is still not possible.
- LF and NB clarify the further procedure bilaterally; if necessary, the LF restarts the use case “Restoration of the grid connection use (reconnect) at the instruction of the LF”.
Error cases
The grid connection use is not interrupted by means of the use case “Interruption of the grid connection use (disconnect) at the instruction of the LF”.
Further requirements
- The restoration of grid connection use at a start of supply is carried out via the use case "Restoration of grid connection use at start of supply".
- The extent to which MSB participates in carrying out the reconnection depends on whether MSB has granted NB general consent to carry out the disconnection/reconnection and, if such consent has not been granted, on the content of the consent from process step 4 “Response to request” of the use case “Interruption of grid connection use (disconnect) on the instruction of LF”. If the reconnection of the market location is carried out with the participation of MSB, these steps take place bilaterally outside this process standardisation.
- Cancellations of a reconnection order are presented in the use case “Cancelling the interruption and restoration of grid connection use on the instruction of LF”. A successful cancellation of a reconnection order ends the use case described here.
Trigger
Runs beforehand: Cancellation of the interruption and restoration of grid connection use on the instruction of the LF — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Reconnection order“ to NB (step 1).
Objective
The grid connection use via the affected market location is possible again.
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 own role was already involved in this process, so the transaction already exists.
Applies to: 2
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: 4