Skip to main content

Platform Capabilities

This page maps the Energyworx platform's capabilities at a business level and links each one to its detailed documentation. Data follows the same journey in every deployment: it is ingested from files, APIs, meters or market hubs; modelled onto datasources, channels and tags; processed by flows and rules (validation, estimation, calculation); and used — searched, aggregated, visualized, exported, or delivered to downstream systems.

Data ingestion & integration

Multi-source, multi-format ingestion of measurement data, master data and market messages: file upload (CSV, Excel, XML, JSON), an inbound REST API with synchronous validation feedback, scheduled outbound REST polling, direct meter reading via MODBUS, and SOAP market hub messaging. Pluggable Market Adapters normalise any inbound format, and Transformation Configurations map the parsed output onto the data model.

Data Ingestion · Market Adapter · Transformation Configuration

Datasource & metadata registry

A versioned, append-only registry of everything that produces data — meters, sensors, market profiles — modelled as datasources with timeseries channels, classifiers, and tags that track slowly changing dimensions (contracts, locations, market parties) with full validity timelines.

Data Model overview · Datasources · Tags

Full-text and structured search over the datasource registry — by identifier, tag properties and classifiers — with near-real-time indexing, plus an Advanced Search interface for ad-hoc queries across the platform's data.

Datasource Search

Flow orchestration & rules engine

Composable data-processing pipelines ("flows") built from sequences of Python rules, with conditional branching via decision trees, flow chaining, multi-message correlation via the Collective Trigger, and scheduled execution. Business logic changes without waiting for a platform release.

Flow Orchestration Overview · Flow Design · Rules

Anomaly detection & automated actions

Rules detect data anomalies and automatically act on them: annotation thresholds create tasks for human follow-up, flows chain corrective processing, and notifications go out by email — the full path from detection to action.

Anomaly Detection and Alerting · Task Management

Timeseries aggregation & virtual datasources

Aggregate timeseries across whole populations of datasources selected by tag-based filters, with timeline-aware membership: when its aggregation is triggered (typically on a schedule), a Virtual Datasource aggregates every datasource matching its filter, for exactly the period each one matches.

Virtual Datasources

Machine learning inference

Deploy trained models (XGBoost, scikit-learn) to the platform and query them from rules for in-flow inference — anomaly detection, forecasting, estimation — at processing scale.

Machine Learning

Dashboards & reporting

Build dashboards in the platform with configurable widgets (charts, tables, statistics, lists) powered by eQL, the Energyworx Query Language, over timeseries, flow and audit data — for both current-state monitoring and historical analysis.

Dashboards · eQL

Process monitoring & alerting

Track every process instance end-to-end — from file arrival through transformation, storage and flow execution — with KPIs per process, and alerts (including email notification) when metrics cross configured thresholds.

Process Monitoring

Multi-tenancy, identity & access management

Namespaces provide isolated tenant environments with their own datasources, flows and configuration. Access is governed by role-based permission groups, and sign-in federates with your identity provider (Microsoft Entra, SAML) including automatic group-to-permission mapping.

Multi-Tenancy and Namespaces · IAM and Permissions

Public APIs

Everything the platform does is reachable over documented REST APIs — datasources, timeseries, flows, tasks and identity — for customer and partner integration.

Automated API Access · API v2 · API v1.5

Solution modules

Business use cases built on these capabilities — such as Meter Reads Processing (VEE) and Billing Determinants Calculation — are productised solution modules, documented separately under Solutions.