# Transmission of a definition of NB by NB — LF view All LF and MSB always receive the current - Metering time definitions of NB or - Switching time definitions of NB or - Power curve definitions of NB. If a definition of NB changes, it is transmitted to LF and MSB. ## Process flow from the perspective of the LF \nSystem diagram: Übermittlung einer Definition des NB durch den NB — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Definition des NB\n\nNB\n\nAS4\n25005, 25008, 25009\n\nLoad data for the incoming\ncheck\n\n\n3 read APIs called\n\nAPI\nlisted at the step\n\nAPERAK check: Z10\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nreferenzAufAnfragenachricht = null\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nreferenzAufAnfragenachricht != null\n"} gesamt={"\nSequence diagram: Übermittlung einer Definition des NB durch den NB — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\nMSB\n\n\n1. Definition des NB\nAS4 · PI 25005, 25008, 25009\n\nCreate transaction\nCreate process data · referenzAufAnfragenachricht = null\n\nUpdate transaction\nUpdate process data · referenzAufAnfragenachricht != null\n\n2. Definition des NB\nAS4 · PI 25009, 25005, 25008\n"} titel="LF" /> ## Process steps ### Definition of the NB
**Check identifiers** - [25005](/en/schnittstellen/202610/pruefi/UTILTS/PI_25005) — Transmission of a rolled-out metering time period definition · AS4 - [25008](/en/schnittstellen/202610/pruefi/UTILTS/PI_25008) — Transmission of a rolled-out switching time definition · AS4 - [25009](/en/schnittstellen/202610/pruefi/UTILTS/PI_25009) — Transmission of a rolled-out power curve definition · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Load data for the incoming check** - [Read metering time period definition ](/en/api/202610/backend-lesen/getdefinitioncounting#zaehlzeitdefinition-lesen) `GET /getDefinitionCounting` Try it - [Read switching time definition](/en/api/202610/backend-lesen/getdefinitionswitch#schaltzeitdefinition-lesen) `GET /getDefinitionSwitch` Try it - [Read power curve definition](/en/api/202610/backend-lesen/getdefinitionperformance#leistungskurvendefinition-lesen) `GET /getDefinitionPerformance` Try it
  3. **APERAK checks** - `25005`, `25008`, `25009` → `Z10` — APERAK check: Is location known ?
  4. **Write endpoint** - `referenzAufAnfragenachricht = null` → Transaction created — [Create process data](/en/api/202610/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.
  5. **Write endpoint** - `referenzAufAnfragenachricht != null` → Transaction updated — [Update process data](/en/api/202610/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.
### Definition of the NB This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [25009](/en/schnittstellen/202610/pruefi/UTILTS/PI_25009) — Transmission of a rolled-out power curve definition · AS4 - [25005](/en/schnittstellen/202610/pruefi/UTILTS/PI_25005) — Transmission of a rolled-out metering time period definition · AS4 - [25008](/en/schnittstellen/202610/pruefi/UTILTS/PI_25008) — Transmission of a rolled-out switching time definition · AS4
## Process information Wording of the consolidated version, profile ch. 1.2.3.1, pp. 13–14.
  1. ### Preconditions - The - Overview of the metering time period definition of the NB or - Overview of the switching time definitions of the NB or - Overview of the power curve definitions of the NB is available to the LF and MSB.
  2. ### Results - The LF can trace a definition assigned to a location (e.g. the LF can trace a metering time period definition of the NB assigned to a market location). - The MSB can set up a configuration for a location for which a definition is required. - In the case of the order placement of a configuration for which a definition is required: - The LF can carry out the use case „[Order placement of a configuration from the LF to NB](/en/prozessdoku/202610/LF/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-nb)“ (e.g. for ordering a configuration for which a metering time period definition of the NB is required). - The NB can carry out the use case „Order placement of a configuration from the NB or LF to MSB“ (e.g. for ordering a configuration for which a metering time period definition of the NB is required).
  3. ### Further requirements - The NB transmits definitions with the highest version number for each time period. - For a time period, the definition with the highest version number is valid. - On first transmission, all definitions used are to be sent in their respective valid version. This also applies when they are rolled out for the following years for the first time. - The definition of the NB must always be specified for a complete calendar year. In the case of corrections, only the corrected definition for the entire calendar year is to be sent. - In the case of the metering time period definition of NB: - A metering time period definition of NB must also be transmitted by NB to the final customer in his role as LF if the final customer assumes the role of LF within the grid usage settlement, insofar as these provisions are applicable to him accordingly. - If a metering time period definition of NB is communicated to MSB as part of the minimum parameters in the use case “[Start of metering point operation](/en/prozessdoku/202610/LF/WiM-Teil1-beginn-messstellenbetrieb)” (WiM part 1) that MSB has not received in advance via the use case “Transmission of a definition of NB by NB”, the energy must be recorded in one register at the metering location(s) and the associated market location for the metering time period usage purpose “grid usage”.
  4. ### Trigger - A definition already transmitted has changed or - a definition has been newly added to the corresponding overview or - the NB has created definitions for the following year. **Runs beforehand:** [Complaint about a definition of the NB from LF to NB](/en/prozessdoku/202610/LF/GPKE-Teil3-reklamation-einer-definition-des-nb-vom-lf-an-nb), [Complaint about a definition of the NB from MSB to NB](/en/prozessdoku/202610/MSB/GPKE-Teil3-reklamation-einer-definition-des-nb-vom-msb-an-nb), [Transmission of the overview of the definitions of the NB by the NB](/en/prozessdoku/202610/LF/GPKE-Teil3-uebermittlung-der-uebersicht-der-definitionen-des-nb-durch-den-nb) — these processes name the one shown here in their result.
  5. ### First message **NB** sends “Definition of the NB” (step 1). From here on, it is the turn of the party involved on this page.
  6. ### Objective The LF and MSB know the - Metering time definitions of NB or - Switching time definitions of NB or - Power curve definitions of NB
## 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/202610/NB/GPKE-Teil3-uebermittlung-einer-definition-des-nb-durch-den-nb) — NB - [View MSB](/en/prozessdoku/202610/MSB/GPKE-Teil3-uebermittlung-einer-definition-des-nb-durch-den-nb) — MSB *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.*