01 · Send
The agent submits the schedule
A schedule toward the transmission operator is EDIFACT or ESS over AS4. A tool that can send one will send one.
Energy data management sits next to billing. The agent may read a schedule and may not send it.
Energy data management for schedules and metered load sits in KISTERS BelVis, Robotron ecount or SOPTIM, beside the billing contract rather than inside it. Pexon lets an agent read a schedule status under the caller's login. Sending a schedule to a transmission operator stays a job inside that system.
Three ways an energy-data agent causes a nomination
02 · SQL
The chatbot writes SQL on ecount
Robotron's own SQL chatbot sits on a schema that is not published. Copying that pattern from outside is a shared database login with a prompt in front.
03 · File
The CSV drop is treated as an API
BelVis exchanges CSV with Wilken ENER:GY in both directions. A folder is not a permission model.
Two jobs that share a CSV and nothing else
Who may look, and who may send
The desk may read
- Schedule status, once that installation shows a read
- A meter series under the caller's own login
- The CSV BelVis already exchanges with ENER:GY, as a file the job wrote
The desk still sends
- A nomination toward the transmission operator
- AS4, MSCONS, UTILMD or ESS out of the EDM job
- SQL against ecount from outside Robotron's own chatbot
Use cases
Read, forecast, send: only one of those is yours to automate
| Job | System that holds it | Agent |
|---|---|---|
| Was this schedule accepted? | BelVis, Robotron ecount, or SOPTIM | Read the status, once a read path exists on that installation |
| What did this meter series do yesterday? | The EDM time series, not the billing contract | Read the series under the caller's login. Do not invent a BelVis endpoint |
| Forecast the load for tomorrow | Robotron documents its own machine-learning forecast | Not this server. No accuracy figure is published for us to repeat |
| Send the schedule | AS4, MSCONS, UTILMD, ESS, inside the EDM job | No tool. The person who may nominate keeps that job |
VU-ARGE on BelVis, read 6 October 2026. Robotron and SOPTIM surfaces are the connector records in this repository. KISTERS and SOPTIM both declined the PwC February 2020 ERP survey; BelVis is not an ERP.
One desk, not three products
What each system has actually published
File
KISTERS BelVis
VU-ARGE calls it widespread German energy data management for electricity and gas, and integrates it to Wilken ENER:GY with CSV in both directions. No public query API. A folder is not a permission model.
Product
Robotron ecount
Oracle or PostgreSQL, schema unpublished. A web service for external forecast models, an R interface, and market formats BDEW, AS4, MSCONS, UTILMD. The vendor forecast and the SQL chatbot stay Robotron's. No accuracy figure is published.
Mapping
SOPTIM
DataHub maps Excel, XML, CSV, REST or SOAP by time, event, API call or a file on S3 or SFTP. Schedules leave as EDIFACT or ESS. Elements APIs sit behind a customer login, so the pilot reads that catalogue on the tenant.
A forecast product, or a file share, and why the read sits between them
Robotron already sells the clever half. The connector record names machine-learning consumption forecasts, anomaly detection on scheduler jobs, and an SQL chatbot for ecount and esales. Using that chatbot, or prompting a model to imitate it against Oracle or PostgreSQL, skips the only control a municipal utility can actually audit: which person asked, and which named read ran. The schema is not published, so an outside SQL tool cannot even be reviewed against a contract.
KISTERS BelVis is the system VU-ARGE calls widespread for electricity and gas, and the one they integrate to Wilken with CSV in both directions. That is a real interface. It is also a drop. An agent that tails the drop sees every file the job wrote, which is a wider set than the person at the desk is looking at. SOPTIM's DataHub is the more explicit version of the same idea: Excel, XML, CSV, REST or SOAP, fired by a clock, an event, an API call or a file landing on S3 or SFTP. The API documentation itself sits behind a customer login, so a pilot starts by reading that catalogue on your tenant, not by guessing paths.
PwC in February 2020 put Robotron's energy-market platform in the large-installation chart and did not get a BelVis or SOPTIM questionnaire, because both vendors declined. Absence from that ERP study is not absence from a Stadtwerk. A 300-person utility that trades or nominates has one of these desks beside Schleupen, Wilken or kVASy. It does not have all three, and the agent should be built for the one that is installed.
Status in, nomination out of reach
01
Identify the desk
BelVis, ecount or SOPTIM. The billing system is a neighbour. The CSV into ENER:GY is the proof they are neighbours, not the proof they are one database.
02
Find the read that is already supported
On SOPTIM that is whatever Elements documents behind the customer login, or a DataHub mapping you already run. On Robotron the public note is a web service for external forecast models and an R interface, not a general query API. On BelVis we have the CSV, and nothing more published.
03
Bind it to the caller
If the only path is a technical database user, stop. The SQL chatbot is Robotron's product on Robotron's terms. It is not a pattern to copy.
04
Leave the send where it is
Market formats stay inside the EDM job. The agent reports status. It does not nominate.
- AS4
- MSCONS
- no send
The pilot stops when any of these is true
- The only path is a database login. Robotron's schema is unpublished. An outside SQL tool cannot be reviewed against a contract.
- The read is a folder. BelVis CSV in both directions is a real interface. Tailing the drop sees every file the job wrote, which is wider than the person at the desk.
- The tool can nominate. Market formats stay inside the EDM job. Status is a read. Sending the schedule is not.
The desk will notice these before the model does
- A forecast without a published error is not a number. Robotron offers machine-learning forecasts. This page does not quote a hit rate, because the source we have does not contain one.
- Two directions of CSV means the billing system can be stale too. VU-ARGE's BelVis link to ENER:GY is bilateral and file-based. An agent that reads only one side will disagree with the bill.
- Declining a 2020 ERP survey is not a small vendor. KISTERS and SOPTIM are absent from PwC's respondent list on purpose. Treat them as unsurveyed, not as rare.
The tool that is refused
The allow line is conditional. It appears only after the installation shows a read. The deny line is unconditional.
allow_if_documented: schedule_status, meter_series
deny_always: send_schedule, raw_sql
source: belvis | ecount | soptimraw_sql is how a shared database login disguises itself as an assistant. It is refused even when Robotron's own chatbot does something similar inside their product.
One installation
A 300-person utility has one of these desks. Not BelVis and ecount and SOPTIM at once. The agent is built for the system that is installed, beside Schleupen, Wilken or kVASy, and it still may not send the schedule.
Robotron connectorWhen the vendor forecast is the right buy
If the question is the load for tomorrow, the Robotron forecast is the product that exists, and an agent that re-implements it is a second model with no published error bar. Build the read when someone is copying a schedule status into a mail. The Robotron integration and the SOPTIM integration are those reads. The contract they get matched to is the billing system.
The series has a meter, and the meter has a customer
- Network assets: where the meter is on the map — Smallworld and Lovion, and the copy the crew already carries
- Billing: the contract the series is billed against — Schleupen, Wilken, kVASy, IS-U, WinEV
- Robotron integration — why the SQL chatbot is not the connector
What the scheduling desk will ask
Which system holds the schedule at a municipal utility?
Not the billing contract. VU-ARGE describes KISTERS BelVis as a widespread energy-data system for electricity and gas, with a CSV exchange both ways into Wilken ENER:GY. Robotron calls ecount the market-leading German energy data management system. SOPTIM Elements is the other desk, for portfolio, balancing group and schedules. A 300-person utility has one of these, sometimes two, and not all three.
Can the agent send a schedule to the transmission operator?
No. Schedules leave as EDIFACT or ESS, over AS4, from inside BelVis, ecount or SOPTIM. An agent may read whether a schedule was accepted. The send stays a job the EDM system already runs, under the person who is allowed to nominate.
Is Robotron's SQL chatbot the integration?
It is Robotron's own assistant on the ecount and esales database. The schema is not published. A prompt that asks the model to write SQL against that database is the same shape as handing over a shared account. We do not build that. A named read, under the caller's login, is the shape that survives an audit.
What does scoping one energy-data question cost?
A two-week Readiness Blueprint at €4,900 net. Bring the system name and the release. We confirm whether the read path is a documented API, a CSV drop or an unpublished schema, and we price the pilot from €15,000 only after that.
What if we do not want to operate the connector?
We can operate it in your environment. Monitoring starts at €3,000 per month. If the only interface is a CSV folder that your EDM team already watches, an agent on that folder is a second reader of a file share, and we will say so before building.
Next step
Name the one series someone re-exports every morning
Two weeks. We look at whether that series is a documented read, a CSV drop, or a database nobody is allowed to hand to a model.