Give Your Energy Data
A Location
Energy monitoring without spatial context is just numbers. Kernopy EMS ties consumption to the exact floor, zone, and asset it came from — using the spatial model you've already built in Kernopy Spaces.
Spatial Hierarchy Activated by EMS
Portfolio
All sites
Site
Campus
Building
Structure
Floor
Energy view
Zone
Meter bound
Asset
Device param
Floor, Zone, and Asset levels are energy-aware when EMS is enabled.
The Problem
Your Energy Bill Knows.
Your Software Doesn't.
You can see total consumption. You can't see where it's coming from — and that gap costs you every month.
No Spatial Context
Energy dashboards show site totals. Waste hides at the floor and zone level, invisible until it's already in the bill.
Duplicate Zone Setup
Every EMS tool forces you to redefine your building hierarchy even when you've already modelled it elsewhere.
Shared Asset Confusion
A central chiller serves multiple floors. Most systems count it once per floor and then wonder why the numbers don't add up.
Alerts Without Location
Threshold breaches fire with a meter ID. Your team spends 20 minutes locating the problem before they can act on it.
Platform Modules
Your Space Tree Is Your Energy Topology.
EMS reads the hierarchy you've built in Spaces directly. No zone re-configuration. No parallel data model. Meters bind to Space nodes — and that's it.
Spatial consumption rollup
Consumption aggregates up your Space tree automatically — from individual asset to zone to floor to building to portfolio. Every level always in sync.
Shared asset apportionment
Central chillers, UPS units, and shared infrastructure live at their owner Space node. EMS apportions consumption to served zones without double-counting in rollups.
Location-aware anomaly alerts
Every threshold breach resolves to a named Space node — not a meter ID. Your team knows exactly which floor or zone to look at, immediately.
Baseline & deviation tracking
Set energy baselines per zone, per shift, or per production cycle. Track performance over time and surface deviations as they occur — not in the monthly report.
Asset-level parameter binding
Energy assets bind directly to device parameters already registered in Kernopy IoT Core. One asset can aggregate parameters from multiple gateways across the same zone.
Portfolio & ESG reporting
Aggregate consumption across all sites in a single view. Generate sustainability reports, track against ESG targets, and benchmark properties against each other.
EMS ships with every Spaces deployment
No separate module activation. No zone re-configuration. When you set up a Spaces hierarchy, EMS is already reading it. Your Space tree is your energy topology from day one.
How It Fits In
A Structured Model,
Not A Parallel One.
EMS doesn't introduce new concepts. It adds energy context to the spatial model that already exists.
Space UUID = Zone ID
The EMS query engine accepts Space UUIDs directly as zone identifiers. There is no translation layer, no zone mapping table.
Single source of truth
If a zone boundary changes in Spaces, EMS reflects it immediately. IoT Core, alerts, and all apps stay consistent — one write, consistent state.
No rip-and-replace
Meters and devices connect through Kernopy Edge. Raw telemetry flows into IoT Core and into the canonical device registry without migration.
Works with Foundry
For manufacturing deployments, EMS runs alongside Foundry — sharing the same Edge infrastructure with no duplicate device registration.
Every Scale. Every Sector.
Where Kernopy EMS Operates.
From a single commercial building to a multi-site industrial portfolio — EMS scales to the hierarchy you've built.
Commercial Real Estate
Floor-level consumption per tenant. Portfolio-wide visibility from one dashboard.
Manufacturing
Production-normalised energy per zone. Shift-based deviation tracking. OEE-linked consumption.
Data Centres
PUE monitoring per zone. Cooling vs. IT load breakdown. Continuous anomaly detection.
Healthcare
Department-level energy tracking. HVAC and equipment monitoring across large campuses.
Logistics
Warehouse zone monitoring. Cold chain energy tracking. Loading bay idle detection.
Energy & Utilities
Sub-station and distribution-level monitoring. Consumption rollup across large sites.
The Ecosystem
Your Operation, Finally Organised.
Kernopy EMS is built on Kernopy Spaces, which runs on Kernopy IoT Core. No rip-and-replace. No data migration. No parallel systems.
Kernopy Edge
Meters connect through Edge. Protocol translation (Modbus TCP / OPC-UA / MQTT), local compute, offline resilience.
IoT Core
Canonical device registry. Sub-second telemetry ingestion. TimescaleDB storage for all parameter history.
Spaces + EMS
Hierarchy modelled once. EMS reads the Space tree directly. Zero re-configuration required — Space UUID is zone ID.
Kernopy Foundry
Runs alongside EMS in manufacturing deployments. Shared Edge infra and IoT Core, no duplicate device registration.
A Living Energy Model.
Not a Static Dashboard.
Experience spatial energy intelligence. See exactly where consumption comes from and act on it.