Skip to main content
For profiled customers the network operator does not send the BKV a sum time series it could use before settlement: the BK-SZR (Kategorie A) of the SLS arrives at the earliest on the 12th Werktag after the month. What the supplier receives earlier is enough to compute it: per market location the annual consumption forecast and the load profile, and per network operator the profile values. For profiled customers the rolled-out profile is the forecast and the Ist. Cloover’s MaKo system receives those messages as supplier and forwards them, converted to BO4E JSON (one file per message), to a shared Drive folder. An Apps Script posts every new file to the bridge.

​
What is forwarded

​
The roll-out

Per Bilanzierungsgebiet and quarter hour:
The 13010 values are average power for a profile normalized to 1,000,000 kWh/a, so × 0.25 is the quarter hour’s energy. The JVP comes from the 55126; of several 55126 for one market location, the latest message valid on the day wins.
  • No 55073 for the profile: 1,000,000 kWh/a is assumed and said so in the result.
  • Normalized otherwise (1,000,000 kW, 300 kWh/K): not scaled by the JVP - counted under nicht_skalierbar.
  • No 13010 for the day: the market location is counted under fehlende_profile, never rolled out as 0.
  • A day curve that adds up to 1,000 (× 0.25): flagged - that is the shape of a temperature-dependent day curve, not an annual profile.
Temperature-dependent customers (TLS) need, in addition, the day’s temperature at the measuring point the 55126 names. In a 13011 the curve at position n adds up to n kWh per day for 1 kWh/K: the position is the temperature difference in Kelvin. The bridge stores them; rolling out TLS waits for the temperature data.

​
Endpoints

All under the report scope - the read-only report key is enough. The files hold market location IDs. They stay on the audit share (marktdaten/, ledgers marktdaten_*); every response, event and the Slack log carry counts only. The per-file event marktdaten_importiert is kept out of the Slack log; marktdaten_unbekannt (warning) is not.

​
Setting up the Drive script

scripts/drive_marktdaten.gs, run with an account that can read the folder:
  1. script.google.com → new project, paste the file; CONFIG.FOLDER_ID is the Drive folder.
  2. Project settings → Script properties: REPORT_API_KEY = the bridge’s report key.
  3. Run marktdatenSenden once and grant Drive and external-request access.
  4. Triggers → marktdatenSenden, time-driven, every hour.
The script sends every .json file (subfolders included) changed since the newest one it delivered, oldest first, at most 150 per run - a large first load spreads over a few runs. A failed call stops the run; the next one retries. allesNeuSenden starts over; the bridge ignores what it has.