Transmission of the daily balancing area aggregate time series from ÜNB to NB — NB view
The ÜNB forms the BG-SZR (category C) daily and transmits it to the NB. The BG-SZR (category C) is formed on the basis of the ¼ h values transmitted by the MSB and the master data provided by the NB for all market locations with ÜNB aggregation responsibility. As the status per ¼ h, the BG-SZR (category C) always shows the worst status of any of the individual values in the same ¼ h.
Process flow from the perspective of the NB
Process steps
BG-SZR (category C)
NB ÜNBCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message from ÜNB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read meter
GET /getCounterBasic
- Read market location
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
Process information
Wording of the consolidated version, profile ch. 15.4.1, p. 213.
Preconditions
- The MaBiS-ZP is activated at the recipient by the ÜNB.
- The master data for creating the BG-SZR (category C) is available to the ÜNB.
- The required values from the MSB of the individual market locations are available to ÜNB by 11:00 for the previous day.
Results
The grid operator can use the transmitted BG-SZR (category C) for further processes.
Further requirements
The ÜNB must also be able to form an aggregate if not all meter reading values of all market locations are available. This must then be indicated with a status for the respective ¼ h.
First message
ÜNB sends “BG-SZR (category C)” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The NB has received the required BG-SZR (category C) from the ÜNB on a daily basis.
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 — ÜNB · market role UENB
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
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: 1