Interruption of grid connection use (disconnect) at the instruction of LF — View NB
In accordance with the grid usage contract (supplier framework contract) concluded between the LF and the NB, the LF instructs the NB to interrupt the grid connection use at the named market location of the AN supplied by the LF. The number of disconnection attempts per disconnection order depends on the general terms and conditions of the NB. The LF announces the disconnection to the AN. The NB checks whether the necessary preconditions for a disconnection are met and carries the disconnection out if they are. If the MSB has not granted the NB general consent to carry out the disconnection/reconnection, the MSB is asked. The NB informs the LF, where applicable the MSB and where applicable the ÜNB about the disconnection result.
Process flow from the perspective of the NB
Process steps
Disconnection order
NB LFZ10E_0470 Check disconnection order1911619117Check identifiers
- 17115 — Disconnection order · AS4
Flow
Message from LF · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic
- Read market location
APERAK checks
17115→Z10
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 location bundle
GET /getLocationBundleBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read price sheet
GET /getPriceSheetBasic
- Read location bundle
Decision tree
17115→ E_0470 — Check disconnection order
Trigger follow-up process
- 19116 — Confirmation of disconnection/reconnection order
- 19117 — Rejection of disconnection/reconnection order
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to disconnection order
NB LF17115Check identifiers
Flow
Triggered by incoming message
- 17115 — Disconnection order
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF · AS4
Response per decision tree
19116,19117→ E_0470 · NB · Check disconnection order
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
Request
NB MSBCheck identifiers
- 17116 — Request disconnection · AS4
Flow
Prozessauslöser
START_ANFRAGE_SPERRUNGThe backend triggers this step with this event.
Message to MSB · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend once the message has been created.
- Transaction created — Create process data
Response to request
NB MSBZ33Check identifiers
Flow
Message from MSB · AS4
Response per decision tree
19118,19119→ E_0488 · MSB · Check request
APERAK checks
19118,19119→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
Result of the disconnection order
NB LFSTART_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 LF · 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 disconnection 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_0472 · NB · Check whether the disconnection 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 disconnection 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_0472 · NB · Check whether the disconnection 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_0470 | Check disconnection order |
| E_0472 | Check whether the disconnection order was successful |
| E_0488 | Check request |
| E_0501 | Check rejection, perform clearing if necessary |
Process information
Wording of the consolidated version, profile ch. 3.5.1.1, pp. 103–104.
Preconditions
- This is a consuming market location. If the consuming market location is electrically connected to one or more generating market locations in such a way that the interruption of grid connection use also affects this generating market location or these generating market locations, this UC is nevertheless applicable.
- The market location to be disconnected is assigned to LF.
- The market location is not already disconnected.
- The market location to be disconnected is in the low voltage level.
- The metering point operation is carried out at all metering locations of the market location to be disconnected by the same MSB; i.e. the MSB of the market location is the MSB of the metering location(s).
Results
- The market location is disconnected.
- Billing can be carried out via the use case „Billing of another service". The costs of the reconnection are also charged to the LF that ordered the successful disconnection of the market location.
Error case
Result in the error case
- The grid connection use via the affected market location is still possible.
- The disconnection order was ended without success (reasons: e.g. market location cannot be identified on site, access to the market location not possible, passive refusal of access or active refusal of access). Note: costs incurred up to that point due to an unsuccessful interruption can be settled via the use case “Billing of another service"."
- If required, the LF can restart the use case „Interruption of the grid connection use (disconnect) on instruction of the LF“, where applicable with the involvement of a bailiff.
Error cases
- This is a generating market location or a tranche.
- The market location to be disconnected is not in the low voltage level.
- The MSB of the market location is not the MSB of the metering locations.
Further requirements
- A disconnection of a market location is not equivalent to a decommissioning. In the event of a disconnection, MSB must continue to fulfil its obligations, in particular the transmission of values to the authorized parties. This means that MSB transmits or applies the disconnection meter reading or "zero consumption substitute values" for the period of the disconnection.
- A disconnected market location remains part of the balancing.
- If the disconnection of the market location is carried out with the participation of MSB, these steps take place bilaterally outside this process standardization.
- The cancellation of a disconnection order is described in the use case „Cancellation of the interruption and restoration of the grid connection use on the instruction of the LF“. If a disconnection order is successfully canceled, the use case „Interruption of the grid connection use (disconnect) on the instruction of the LF“ described here continues with the SD step "ref Billing of another service" so that the services incurred up to that point can be billed.
- After an active refusal of access, no further disconnection attempt is made within a disconnection order.
- The disconnection of a market location involving a bailiff must always be ordered separately.
- If the affected market location is not in the low voltage grid and/or MSB of the market location is not at the same time MSB of all metering locations of the market location, communication takes place NON-EDIFACT.
- Note: If the consuming market location is electrically connected to one or more generating market locations in such a way that the interruption of the grid connection use also affects these generating market location(s), the disconnection order of LF for the consuming market location is not to be rejected on the grounds that this prevents the feed-in of the generated electricity quantities into the grid.
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
LF sends “Disconnection order” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The grid connection use via the affected market location is no longer possible.
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.