# 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 \nSystem diagram: Wiederherstellung der Anschlussnutzung (Entsperren) auf Anweisung des LF — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_ENTSPERRAUFTRAG\n\nAPI\n\n1. Entsperrauftrag\n\n\nNB\n\nAS4\n17117\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort auf\nEntsperrauftrag\n\n\nNB\n\nAS4\n19116, 19117\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Ergebnis des\nEntsperrauftrags\n\n\nNB\n\nAS4\n21039\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Wiederherstellung der Anschlussnutzung (Entsperren) auf Anweisung des LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\nÜNB\n\n\nSTART_ENTSPERRAUFTRAG\nTrigger event\n\n1. Entsperrauftrag\nAS4 · PI 17117\n\nUpdate transaction\nUpdate process data\n\n2. Antwort auf Entsperrauftrag\nAS4 · PI 19116, 19117 · E_0497\nE_0497 — Entsperrauftrag prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Information über Entsperrauftrag\nAS4 · PI 21040\n\n4. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_0499\nE_0499 — Prüfen, ob Entsperrauftrag erfolgreich\n\nCreate transaction\nCreate process data\n\n5. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_0499\nE_0499 — Prüfen, ob Entsperrauftrag erfolgreich\n\n6. Ergebnis des Entsperrauftrags\nAS4 · PI 21039 · E_0499\nE_0499 — Prüfen, ob Entsperrauftrag erfolgreich\n"} titel="LF" /> ## Process steps ### Reconnection order
**Check identifiers** - [17117](/en/schnittstellen/202604/pruefi/ORDERS/PI_17117) — Reconnection order · AS4
**Flow**
  1. **Prozessauslöser** [`START_ENTSPERRAUFTRAG`](/en/api/202604/ausloeser-lf/start-entsperrauftrag) \",\n \"lokationsId\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ENTSPERRAUFTRAG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to reconnection order
**Check identifiers** - [19116](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19116) — Confirmation of disconnection/reconnection order · AS4 - [19117](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19117) — Rejection of disconnection/reconnection order · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `19116`, `19117` → [E_0497](/en/referenz/202604/ebd/E_0497) · NB · Check reconnection order
  2. **APERAK checks** - `19116`, `19117` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Information on the reconnection order This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21040](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21040) — Reconnection order info · AS4
### Result of the reconnection order
**Check identifiers** - [21039](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `21039` → [E_0499](/en/referenz/202604/ebd/E_0499) · NB · Check whether the reconnection order was successful
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `21039` → `Z10` — APERAK check: Is location known ?
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Result of the reconnection order This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21039](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Response per decision tree** - `21039` → [E_0499](/en/referenz/202604/ebd/E_0499) · NB · Check whether the reconnection order was successful
### Result of the reconnection order This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [21039](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21039) — Order status (disconnect) · AS4
**Response per decision tree** - `21039` → [E_0499](/en/referenz/202604/ebd/E_0499) · NB · Check whether the reconnection order was successful
Decision trees of this process | EBD | Name | |---|---| | [E_0497](/referenz/202604/ebd/E_0497) | Check reconnection order | | [E_0499](/referenz/202604/ebd/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.
  1. ### 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](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)“. It is therefore a consuming market location. - The costs of the reconnection are charged to the LF as part of the disconnection.
  2. ### Results The grid connection use via the affected market location is possible again.
  3. ### 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](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-lf)”.
  4. ### 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](/en/prozessdoku/202604/LF/GPKE-Teil2-unterbrechung-der-anschlussnutzung-sperren-auf-anweisung-des-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](/en/prozessdoku/202604/LF/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf)”. A successful cancellation of a reconnection order ends the use case described here.
  5. ### Trigger **Runs beforehand:** [Cancellation of the interruption and restoration of grid connection use on the instruction of the LF](/en/prozessdoku/202604/LF/GPKE-Teil2-stornieren-der-unterbrechung-und-wiederherstellung-der-anschlussnutzung-auf-anweisung-des-lf) — these processes name the one shown here in their result.
  6. ### First message The party involved on this page is itself the sender of: „Reconnection order“ to **NB** (step 1).
  7. ### 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. - [View NB](/en/prozessdoku/202604/NB/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf) — NB - [View MSB](/en/prozessdoku/202604/MSB/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf) — MSB - [View ÜNB](/en/prozessdoku/202604/UENB/GPKE-Teil2-wiederherstellung-der-anschlussnutzung-entsperren-auf-anweisung-des-lf) — ÜNB · market role UENB *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](#schritt-2)