For municipal utilities and energy suppliers
A utility source system is the billing, meter, grid or trading application a municipal utility already runs. Pexon builds the interface, the MCP tool list, the analytics read and the assistant question on that system. The signed list is read-only. A control-room archive is not a switch. A market message is not a nomination.
What we build
Checked 8 October 2026
| Desk | Systems we will open | What stays in the product |
|---|---|---|
| Billing and customer | Schleupen.CS, Wilken ENER:GY, kVASy, WinEV, msu.energie, powercloud, SAP IS-U | Posting the bill, and any AS4 send |
| Energy data and meters | Robotron ecount and esales, BelVis, SOPTIM, BTC AMM | Gateway administration and a forecast the vendor already sells |
| Grid, archive only | PSIcontrol, PSIprins, Spectrum Power 5, HIGH-LEIT | Setpoints, switching, and the command half of a programming interface |
| Network and field | Smallworld, CAIGOS, Lovion | Moving a house connection, or treating a 24-hour extract as live |
| Market and trading | Connect+ RAIDA, ION Allegro, Endur | Sending the XML, the nomination, or the schedule |
SAP S/4HANA FI/CO and PM/EAM sit beside billing in the same landscape. A contract question does not go to the finance tool list. The SAP connector on this site is not an IS-U catalogue.
Three boundaries
01
PSI documents a web service and a SQL archive for people who are not operating the grid, and it says those office users must not interfere with network operations. The SCADA programming interface can also issue commands. The command is not a tool.
02
BTC describes web services and file exchange for the gateway manager and the meter-data manager. co.met runs that platform as a gateway administrator under BSI TR-03109. Reading a value is not administering the gateway.
03
RAIDA has accepted redispatch messages since 28 June 2021, by email, SFTP or REST. Schleupen has an AS4 connect API. Both can send. Neither send is on the list we sign.
Unknown until the installation is open
The list your IT signs. The allow line is filled from that product. The deny line does not change.
allow: read_contract | read_series | read_archive | read_message_status
deny: post_bill | switch | setpoint | wake_gateway | send_market_message
run_as: the person who askedA capability on the vendor side is not a permission on ours.
When the vendor assistant is the right buy
If the question never leaves Schleupen, Wilken or Robotron, start with MAIA, GY:PT or the Robotron SQL chatbot and stop. Build ours when the same question has to cross two systems, or when the vendor assistant can write and the desk must not. The analytics read, when the series is the question, starts at utility data analytics.
The one the question already lives in. A contract question starts in Schleupen, Wilken, kVASy, WinEV, msu.energie, powercloud or IS-U. A series question starts in ecount, BelVis or SOPTIM. A switching question does not start at all.
No. The utility source system stays the system of record. We add a named read. We do not install a second billing suite, a second SCADA, or a second trading book.
Not on the list we sign. AS4, RAIDA, a PSIcontrol command and a HIGH-LEIT setpoint are real operations. They stay with the person who already has that right.
A two-week Readiness Blueprint at €4,900 net. We name the system, the release and one question, and we test that two users do not see each other's records. A production connector is usually a pilot from €15,000.
Next step
Two weeks. Bring a test user who is not an administrator, and the release you actually run. We say whether a documented read exists.