Report
powercloud
Hansen describes more than 30 standard reports in Power BI or Amazon QuickSight. That is a reporting source. It is not an API, and there is no tenant database to query.
For the desk that re-exports the same series every Monday
Utility data analytics that reads the series and does not steer the grid.
Utility data analytics reads the series a municipal utility already stores: a billing quantity, a meter value, an energy-data file, or a grid archive. Pexon does not build a second control system. The assistant answers a question a person at a desk is already allowed to ask. Setpoints, switching and market sends stay in the source system.
The series is already in a system. The export is the problem.
Utility data analytics starts from a file someone already pulls: a powercloud report, a BelVis CSV, a Spectrum HIS export, a HIGH-LEIT Excel report. The assistant is not a new database of the grid. It is a question against that copy, with the time of the copy attached.
PSI says office users of PSIcontrol may see the archive and must not interfere with network operations. That sentence is the product boundary. An analytics tool that can also send a setpoint has crossed it.
What we will not call analytics
A chart is not a permission
- A shared database login with a prompt in front of it. The Robotron schema is unpublished, so an outside SQL tool cannot be reviewed against a contract.
- Tailing every BelVis file the job wrote. The person at the desk is looking at one series, not the whole drop.
- A forecast hit rate. Robotron sells machine-learning forecasts. The source we have does not publish an accuracy figure, so this page does not invent one.
- A write-back of a corrected value into the control system or the billing system.
Three copies, three clocks
Where utility data analytics actually reads
Archive
PSIcontrol and PSIprins
PSIcontrol stores history in SQL and offers it to external clients through a browser and a web service. PSIprins 9, announced 30 June 2025, exports operational time series from OT into IT. The export is the read.
File
BelVis and HIGH-LEIT
BelVis exchanges CSV with Wilken ENER:GY in both directions. HIGH-LEIT evaluates archives in the system and in Excel reports. A file the job wrote is a real interface. It is also wider than the one series a person is looking at.
Checked 8 October 2026
Which utility data analytics question has a documented read
| Question | Where the series sits | Agent |
|---|---|---|
| What did this point record last hour? | PSIcontrol archive, Spectrum HIS export, HIGH-LEIT archive | Read the copy. Do not switch |
| What is the billing quantity for this market location? | Schleupen SLP interface where CS 3.0 has it. Elsewhere, unknown until the installation is open | Read. Do not bill |
| What did the meter send? | BTC meter-data manager, as co.met describes that hub | Read the value. Do not administer the gateway |
| What does the vendor forecast say? | The Robotron forecast product | Use theirs. Do not quote a hit rate they did not publish |
| Write the corrected value back | A command or a posting | No tool |
What surprises a team that already trusts the export
- The HIS screen is not an API. Siemens trains operators to retrieve Spectrum Power 5 history in HISWebUI and to export it. The course names additional interfaces. It does not publish a path.
- The office client is a privilege. PSI ships a browser and a Java client so management can see the grid without operating it. An agent on that client inherits the same limit.
- Two clocks disagree on purpose. A BelVis file and an ENER:GY bill are neighbours. An answer that omits which side it read will contradict the bill.
Policy, not a live call. The series name is filled from the installation.
allow: read_report | read_archive_series | read_meter_value
deny: write_archive | setpoint | post_bill | send_market_message
as_of: the timestamp on the copy, or the answer says the copy time is unknownAn omitted timestamp is a failed answer, not a live value.
When the Monday export is enough
If one person runs one report inside powercloud or HISWebUI, leave it there. Build the read when the same series is being pasted into a second system. The system of record stays on the utility source system page. A control-room question that is only the archive is the grid control archive.
From the series to the system
- Utility source system — interface, MCP, analytics and the assistant question
- powercloud — reports, not a database
- SOPTIM — the catalogue behind the customer login
What the analyst will ask
What is utility data analytics if we already have reports?
The same series, asked as a question, under that person's login. powercloud already has more than 30 standard reports. A PSIcontrol archive already has a web service for office users. We do not replace those. We name which one the assistant may call.
Will you train a forecast on our meter data?
Not in the first use case. Robotron already sells a machine-learning forecast, and this page does not quote a hit rate because the source we have does not contain one. The blueprint reads the series the installation already keeps.
Can the analytics job write a corrected value back?
No. PSIprins 9 can export operational time series from OT into IT. That export is a copy. Correcting the archive, switching, or sending a market message stays in the source system.
What does utility data analytics cost to start?
A two-week Readiness Blueprint at €4,900 net. We name the system, the series and the one question, and we test the read with two users. A production connector is usually a pilot from €15,000.
Next step
Bring the series the team already exports by hand
Two weeks. We say which documented read can replace that export, and which question has no read yet.