Skip to main content

Apio EMS

Apio EMS is the control layer for plants with distributed energy resources. It holds a physical model of the plant, computes a quarter-hourly dispatch plan for every asset under its operating and market constraints, and executes that plan on site — including when the link to the cloud is down.

Cloud and Edge

A brain in the cloud, a reflex on the plant

Forecast

Reference profiles for consumption and generation, split by working, holiday and pre-holiday days, continuously updated from measured data.

Optimize

The optimal dispatch plan of the day, quarter-hour by quarter-hour, for every asset — within all physical and contractual constraints.

Execute

EMS Edge reads the meters and drives the assets in closed loop, checking that every command was actually applied.

Keep Running

If connectivity is lost the plant keeps following the plan it already received, with a configurable fallback behaviour and a defined safe state.

Plant Model

A full-fidelity model of the plant

The plant is described once, in a graphical configurator: connection point, storage, generation, CHP units and modulable loads, with the electrical links between them. Each asset carries its technical parameters — capacity, power limits, efficiencies, ramp rates, operating costs, usage windows — and each physical quantity is bound to the device that measures it.

The optimizer, the monitoring views and the market interface all read from this model, so a change to the plant is a change in one place. Assets can declare a fallback profile, which keeps the plan computable when a meter goes missing, and configuration is updated without interrupting operation.

Optimization

Dispatch under physical and contractual constraints

The optimizer computes a plan for every asset over the day at 15-minute resolution. Constraints are hard: withdrawal and injection limits at the connection point; capacity, power and round-trip efficiency of storage; technical minimums, ramp rates and marginal costs of generators; energy requirements and time windows of modulable processes.

Objectives are configurable and can be combined:

  • Self-consumption of on-site generation
  • Arbitrage against energy prices
  • Peak shaving on withdrawn power
  • Load shifting into lower-cost bands
  • Battery degradation, priced into the objective so a cycle is taken only when the return covers it
Every plan is stored with the inputs it was computed from, and can be reproduced — the requirement for settlement and audit.

Flexibility and Markets

Commitments are constraints, not intentions

Apio EMS computes the flexibility envelope of the plant — how far it can move up and down, hour by hour — which is exactly the information needed to offer capacity on the markets.

Market commitments are handled as obligations the plan must honour, and delivery is measured: adherence and deviation are visible, which is the basis for settlement reporting and for avoiding penalties. Capacity can be reserved for expected activations, with explicit visibility on what holding that margin costs.

Compatibility with different market schemes (scheduling, dispatching services, local flexibility) is a matter of configuration, not new development.

Monitoring and KPIs

Plan versus reality, on one plant or a hundred

A real-time plant view shows power at the connection point, state of charge and the contribution of each asset. Synthetic indicators cover energy withdrawn and injected, self-consumption share, withdrawal peak and plan adherence.

The plan/actual comparison makes it immediately clear when something is not going as expected, and the fleet view aggregates the same indicators for operators running multiple sites.

Made for Developers

Easy-to-use well documented APIs

  • Feature-complete JSON REST API
  • Up-to-date OpenAPI specifications
  • Multi-tenant by design, natively integrated with the Apio IoT Platform
Read the documentation