# Transmission of the energy and power values measured so far — NB view ## Process flow from the perspective of the NB \nSystem diagram: Übermittlung der bisher gemessenen Arbeits- und Leistungswerte — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nTriggered by incoming\nmessage: 17103\n\nProcess trigger received\n\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\n1. Bisher gemessene\nArbeits- und Leistungswerte\n\n\nLF\n\nAS4\n13009\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung der bisher gemessenen Arbeits- und Leistungswerte — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n1. Bisher gemessene Arbeits- und Leistungswerte\nAS4 · PI 13009\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Energy and demand values measured so far
**Check identifiers** - [13009](/en/schnittstellen/202604/pruefi/MSCONS/PI_13009) — Energy quantity (gas) · AS4
**Flow**
  1. **Triggered by incoming message** - [17103](/schnittstellen/202604/pruefi/ORDERS/PI_17103) The MACO APP sends this message itself, as a follow-up process after this incoming message. In addition, the backend can trigger this step with an event — the next item.
  2. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202604/ausloeser-nb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  3. Message to **LF** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Energy and power values measured to date“ to **LF** (step 1).
## 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 LF](/en/prozessdoku/202604/LF/geli-gas-2-0-ubermittlung-der-bisher-gemessenen-arbeits-und-leistungswerte) — LF *The source provides no use case profile for this process — objective, precondition and result are not recorded there.* *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.* :::caution{title="Step sequence reconstructed"} For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification. :::