The problem it solves
SCADA systems collect thousands of values a minute, but most organisations still produce monthly reports by hand: export, paste, format, check, email. It takes days, mistakes creep in, and it all happens again next month.
Regulatory and ESG reporting raises the stakes. Water quality compliance, energy consumption and carbon figures each need a defensible number from a traceable source, not a spreadsheet that’s been edited six times.
How it works
-
Define what’s reported
We agree the reports that matter (production, consumption, quality, alarms, runtimes) and the station, zone or tenant each one is broken down by.
-
Build the templates
Report templates pull directly from the SCADA database: tabular and graphical, with filters, statistics and comparisons across periods, such as this month against the same month last year.
-
Schedule and publish
Reports are generated automatically on time- or event-based triggers (daily, monthly, annually or when an alarm occurs) and published through the SCADA web server, so managers read them in a browser.
-
Feed other systems
Meter data can flow into billing systems compatible with the SCADA database, and selected values can be published over MQTT to analytics or ESG platforms.
System architecture
How the layers connect, from the people using the system down to the equipment in the field.
- Managers and finance in a browser
- Regulators
- Billing and ESG platforms
- SCADA web server
- Scheduled reports
- MQTT to analytics
- Time- and event-based reports
- Statistics and filters
- Period-on-period comparison
- Historical values
- Alarms and events from every station
- RTUs, PLCs and meters already reporting into SCADA
What the capability includes
- Station-based daily, monthly and annual reports
- Time- and event-triggered report generation
- Tabular and graphical layouts with filters
- Statistical summaries and period-on-period comparison
- Report access through the SCADA web server
- Billing integration from meter data
