Energy Data Management Module
What the module does
The Energy Data Management (EDM) module turns the Energyworx platform into a ready-made meter data management system for the meter-to-cash process. Master data and meter data arrive from your head-end and back-office systems; the module validates, completes and stores the data, keeps your teams informed through dashboards and task boards, and delivers billing determinants, aggregates and device commands to the systems that need them. Everything runs automatically on the platform's flow engine, and exceptions become tasks for your operators instead of silent data problems.
Processes
| Process | What it automates | Package |
|---|---|---|
| Master Data Processing | Creates and updates meters, metering points, network areas and contracts from IEC 61968-9 (CIM) messages, and acknowledges every message | master_data |
| Meter Events Processing | Stores meter events, keeps the switched-off status of metering points current and turns critical events into tasks | device_control |
| Meter Reads Processing - VEE | Validates, estimates and edits meter readings so that every read has a known quality | vee |
| Device Control Transactions | Sends connect and disconnect commands and on-demand read requests to the head-end system | device_control |
| Aggregations and Calculations | Aggregates validated data per energy community and per network area and calculates self-consumption | energy_communities, network_aggregations |
| Billing Determinants Calculation | Calculates totals, time-of-use splits, peak demand and register reads for a billing period and sends them to the billing system | billing |
Billing Settlement and Prepayment are on the roadmap.
What every process has in common
- Standard message formats. Master data, meter events and device commands use the IEC 61968-9 Common Information Model (CIM) message types, and meter reads use a ready-made mapping of the standard meter readings message. Formats specific to your market or head-end are added through market adapters and transformation configurations without changing the process itself.
- Quality you can see. Every read carries a quality status (measured, estimated, disturbed or missing) and, when it was estimated, the method that produced it. Validation findings are stored as annotations on the data, where anyone can inspect them.
- Exceptions become tasks. Critical validation errors, critical meter events and invalid contract data create tasks on dedicated task boards, so follow-up is tracked instead of hoped for.
- Dashboards included. Each process ships with console dashboards that answer the operational questions: which meters are orphaned or silent, how many datasources completed VEE today, which billing calculations failed.
- Tested. Each package ships with unit tests and automated acceptance scenarios that run end to end against a live environment, so an upgrade or a customisation can be verified the same way Energyworx verifies a release.
- Adaptable by configuration. Thresholds, tolerances, schedules, time zones, tariff definitions, which events count as critical and where messages are sent are configuration, not code. Behaviour specific to your market or organisation is layered on top as your own rules and flows and survives package updates.
Getting the packages
The EDM processes are delivered as the separately licensed standard-packages: pre-built, tested sets of flows, rules, transformation configurations, market adapters, dashboards and task boards that are installed into a namespace and adapted where needed. The Packages section covers access, installation and updates.