ONTOLOXIA EMS · The operational layer for distributed energy

Energy. Under control.

One operational layer for solar PV, battery storage, meters, loads and technical infrastructure — from a single site to a distributed portfolio.

  • Monitoring
  • Data
  • Maintenance
  • Control

One operational model

One system. The complete operational picture.

ONTOLOXIA EMS brings live telemetry, history, alarms, documentation and operational processes into one environment.

01

Monitor

Generation, consumption, power flows, connectivity quality and active alarms.

02

Record

Measurements, events, alarms and command results with source timestamps and data quality.

03

Act

Respond, report, maintain and control within the approved integration scope.

One signal journey

From energy. To decision.

Scroll to see how ONTOLOXIA turns distributed signals into one operational picture.

  1. 01Source
  2. 02Edge
  3. 03Connectivity
  4. 04Central platform
  5. 05Data layer
  6. 06Decision

Scroll through the six stages of the signal journey.

01SourceEMIT

It starts with a signal.

An inverter, battery, meter, charger or HVAC system each speaks its own language. ONTOLOXIA starts with what the device actually exposes.

  • P · E
  • SoC
  • Status · alarm

02EdgeBUFFER

Data is handled at the site first.

An industrial edge node acquires device data and aligns timestamps, units and data quality — close to the installation.

  • Acquisition
  • Validation
  • Data quality

03ConnectivitySYNCHRONIZE

Connectivity can drop. Data does not have to.

Edge acquisition continues. When the secure channel returns, the missing history is synchronised in the right order.

  • Local buffer
  • Store-and-forward
  • TLS · VPN

04Central platformMERGE

Many sites. One operational picture.

Signals from across the portfolio meet in the central platform — on-premise or hybrid — without losing their source identity.

  • On-premise
  • Portfolio
  • Source identity

05Data layerNORMALIZE

Different sources. Shared meaning.

ONTOLOXIA normalises data and connects it with history, alarms, assets and audit.

  • active_power
  • state_of_charge
  • quality

06DecisionRESOLVE

Context becomes action.

Operators see the state, maintenance sees the cause, and owners stay in control. Monitoring becomes a documented decision.

  • Alarm
  • Task
  • Action · audit

View DEMOcoming soon

Key benefits

A complete picture without giving up control.

ONTOLOXIA connects technical information with operational responsibility — from signal to documented action.

01

One operational context

From portfolio to site, device and individual signal — without switching tools.

02

Data remains under control

Edge maintains data acquisition, while data can remain in the owner’s infrastructure.

03

Alarms lead to action

The alarm, device, documentation, maintenance task and audit trail remain connected.

Interoperability

Open interfaces. Control with safeguards.

ONTOLOXIA separates vendor protocols from the common data model. Different registers, topics and API fields can represent the same operational concepts.

Protocols and APIs

The meaning and availability of data come from the protocol and device documentation.

Modbus RTU / TCPMQTTOPC UAM-BusREST API

Transport and signals

A transport layer alone does not define the meaning of data or whether writing is supported.

RS485EthernetHTTPS / TLSI/O
ONTOLOXIA EMS common data modelONTOLOXIA EMS

Scalability

The same platform — built for different scales.

From a single site to a centrally managed fleet, with independent configuration and data continuity at every location.

01

Single site

A local server or compact installation, one site hierarchy and a complete path for further expansion.

02

Multiple sites

Edge nodes at each site, the owner’s central server, and shared reports, alarms, roles and portfolio oversight.

03

Portfolio + external O&M

Local operational continuity and controlled access to selected central services and partner processes.

04

Scale and HA/DR requirements

Individually sized infrastructure, redundancy, identity integration and extended security policies.

For one site and the entire portfolio.

Site count, hierarchy, devices, signals, dashboards, alarms and retention are defined in the deployment profile.

01

Public sector

Government offices, schools, public facilities and distributed assets that need shared oversight and reporting.

02

Industry and logistics

Plants, halls, logistics centres and technical infrastructure focused on availability and cost control.

03

Retail and real estate

Commercial property portfolios, multi-meter sites and installations that connect energy with asset maintenance.

04

Solar PV and battery storage

Residential and industrial installations where energy performance depends on a shared view of PV, BESS and loads.

05

EPC, O&M and integrators

Portfolio operators, delivery partners and maintenance teams that need one context for data and service work.

Product and deployment

Let’s define the right deployment profile for your infrastructure.

We start with devices, interfaces, site count, retention, network architecture and operational responsibilities. This defines the realistic integration scope.

Go to contact details