Restoration of grid connection use at start of supply — View NB
For a disconnected market location, the NB triggers the restoration of the grid connection use. The NB informs, where applicable, the MSB and, where applicable, the ÜNB about the result of the reconnection order.
Process flow from the perspective of the NB
Process steps
Information on the reconnection order
NB MSBSTART_AUFTRAGSSTATUSSTART_WIEDERHERST_LBCheck identifiers
- 21040 — Reconnection order info · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_STATUSMITTEILUNG_BASIS
- Read market location
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
Result of the reconnection order
NB MSBSTART_AUFTRAGSSTATUSSTART_WIEDERHERST_LBCheck identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_STATUSMITTEILUNG_BASIS
- Read market location
Message to MSB · AS4
Response per decision tree
21039→ E_0487 · NB · Check whether the reconnection order was successful
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
Result of the reconnection order
NB ÜNBSTART_AUFTRAGSSTATUSSTART_WIEDERHERST_LBCheck identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_STATUSMITTEILUNG_BASIS
- Read market location
Message to ÜNB · AS4
Response per decision tree
21039→ E_0487 · NB · Check whether the reconnection order was successful
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_0487 | Check whether the reconnection order was successful |
Process information
Wording of the consolidated version, profile ch. 3.5.4.1, p. 114.
Preconditions
- In the case of the assignment of LFN to the market location within the use case “Start of supply”, NB determines that the registration relates to a disconnected market location.
- 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.
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.
- The parties involved clarify the further procedure bilaterally.
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
If the reconnection of the market location is carried out with the involvement of the MSB, these steps take place bilaterally outside this process standardisation.
Trigger
Runs beforehand: Start of supply — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Information on reconnection order“ to MSB (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.
These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button.
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.