01
co.met, since 2023
Gateway administration sits on the BTC platform. co.met states more than 20,000 intelligent measuring systems, on ISO 27001 processes and BSI TR-03109. The clerk who asks for a value may not be the administrator of that fleet.
For the metering desk, not the gateway administrator
A meter data gateway the assistant may query, and may not administer.
A meter data gateway is the smart-meter gateway an administrator already runs, plus the meter-data hub beside it. co.met has used the BTC platform for gateway administration since 2023, for more than 20,000 intelligent measuring systems. BTC describes web services and file exchange. Reading a stored value is not administering the gateway, and it is not a firmware rollout.
Two products, one brand family
The gateway manager is not the meter-data manager. BTC sells both. co.met runs gateway administration on the BTC platform and describes the meter-data manager as the hub that captures, prepares and forwards values. An agent that uses the administrator login to answer a value question is an administrator.
Who actually runs it
A meter data gateway is often not inside the Stadtwerk
02
GWAdriga, as operator
In February 2020 Netze Duisburg put gateway administration with GWAdriga, as business-process outsourcing on the BTC gateway manager, and used the BTC meter-data manager as a cloud service. The operator and the utility are not the same login.
03
Robotron is a neighbour, not this API
The public Robotron surface in this repository is ecount and esales: a forecast web service, an R interface, market formats. No gateway-administration endpoint is in that record. Do not point a gateway question at the ecount chatbot.
Where the value sits
From the gateway to a question that is only a read
BTC says the gateway manager exchanges data with existing systems through standard web services and file transfer, including common ERP systems. The PDF does not publish the operation list. The blueprint does not invent one.
01
Gateway
Administration, monitoring, and firmware. This layer is the certified administrator. It is not a tool.
02
Meter-data hub
Capture, preparation, forwarding. This is the series a billing or energy-data system may already receive. A read starts here, if the asking party is allowed to see it.
03
Billing
The bill is a different system. A meter value and a billed quantity are allowed to differ. The answer names which one it read.
Checked 8 October 2026
Which meter data gateway question has a documented shape
| Question | Where it lives | Agent |
|---|---|---|
| What value was forwarded? | BTC meter-data manager, as co.met describes that hub | Read, as the party who may see it |
| Who administers the fleet? | co.met or GWAdriga on BTC, not the billing clerk | Name the operator. Do not log in as them |
| How does it reach ERP? | BTC: standard web services and files. Paths not published | Confirm on the installation |
| What does ecount know? | Robotron energy data, a different product | A different question |
| Wake the gateway or roll firmware | Gateway manager | No tool |
What a metering team learns the hard way
- TR-03109 is the administrator frame. BTC names the Digitalisierungsgesetz and TR-03109 for gateway administration. An assistant does not inherit that role because it can read a number.
- 20,000 systems is the co.met fleet. The figure is the service provider stock. It is not a volume your tenant contains, and it is not a market share.
- The SQL chatbot is the wrong door. The Robotron chatbot sits on ecount and esales. A gateway question asked there will be answered from the wrong schema, if it is answered at all.
Policy, not a call against a gateway.
allow: read_forwarded_value
deny: administer_gateway | firmware | wake | use_gwa_login
say: which hub, and the timestamp on the valueA missing timestamp is a failed answer. A gateway-administrator token is a failed design.
When the metering portal is enough
If the person already has the meter-data screen, they do not need an agent to read one value. Build the read when that value is being copied into billing or into a Monday sheet. The offer around that read is utility data analytics. The billing neighbour is the utility billing integration.
From the value to the system of record
- Utility data analytics — the series, without a write-back
- Utility billing integration — Schleupen, Wilken, kVASy, IS-U, WinEV
- Robotron — ecount and esales, not a gateway admin API
What the metering lead will ask
What is a safe first question for a meter data gateway?
What value did this metering point last hand to the meter-data manager, and when. That is a read of a series the hub already stores. It is not a command to the gateway.
Is co.met the same system as the utility's billing?
No. co.met is a gateway-administration service on BTC, under ISO 27001 processes and BSI TR-03109. The bill is still in Schleupen, Wilken, kVASy or whichever billing system the utility runs. The two can disagree if the answer hides which one it read.
Can the assistant administer the gateway if the API allows it?
No. BTC's gateway manager exists to administer gateways, including firmware. That right belongs to the certified administrator. The tool list we sign does not include it.
What does it cost to see whether this meter value is readable?
A two-week Readiness Blueprint at €4,900 net. We name the metering platform, the party who may see the value, and we stop if the only credential is a gateway-administrator login. A production read is usually a pilot from €15,000.
Next step
Name the meter value the desk already looks up
Two weeks. We separate the value from the gateway login before anything is called a tool.