Why AEYS
Why teams choose AEYS
Energy data, ISO 50001 evidence, and reporting — one operating system, not a folder of workbooks.
- ISO 50001
- ÖEK / SEU
- Connector Hub
- EnRC + WMAPE
- Company energy report
Most energy programmes stall in the gap between the standard and the plant. Policy is written, meters exist, and yet EnPIs, baselines, and SEU lists live in files that age the moment they are exported.
AEYS is the energy management system platform that keeps that loop in one place: programme intake, organizational units, Connector Hub mappings, ÖEK / SEU analysis, normalization models, and the company energy report your accreditor and board can read.
- 80%
- Cumulative share rule for numbering SEUs
- 3
- Audiences, one evidence pack
- EnRC
- Expected consumption, not a flat baseline
- Upload
- Train before a historian exists
How AEYS holds the EnMS together
Designed for the EnMS, not around it
ISO 50001 is the spine of AEYS: energy review, significant energy uses, EnPIs, energy baselines, documented information, and management review inputs. Programme intake captures scope and the energy team; units and energy sources give operational control a place to live; the company energy report is written against TS EN ISO 50001:2018, not a generic PDF template.
Plant data, mapped once
Connector Hub connects site or enterprise databases. Canonical mappings bind timestamp, consumption, and relevant variables per unit and energy carrier so training and predict do not re-ask which column is the clock. Uploaded files still work for the first model; the hub is the path for data that has to arrive every month.
SEUs you can show an auditor
ÖEK analysis rolls process and sub-process totals to TEP and TJ, applies a priority matrix, and uses the 80% cumulative-share threshold to number significant energy uses. Each selected SEU can be tied to a unit, an energy source, and a trained model — so the list in the report matches what operations actually run.
Expected consumption, not a flat baseline
mf-python models turn relevant variables into energy reference consumption (EnRC). Actual-versus-predicted tables, WMAPE bands, and SEU narratives feed the company energy report. CUSUM, efficiency and intensity indices, and specific energy consumption sit next to the model so operators and reviewers share one picture of performance.
One evidence pack, three audiences
Operators see units, mappings, and predict overflow. Customer programme owners see intake, documented information, and reports. Linked accreditors review the same programme without owning the plant database. That split is how AEYS stays useful after certification week is over.
Frequently asked
Does AEYS replace an ISO 50001 consultant?
No. AEYS holds the EnMS data, models, and documented information so consultants and accreditors review a living system instead of a snapshot. Programme intake can notify the linked accreditor when the team needs support.
Do we need a historian on day one?
No. Models can be trained from uploaded files. Connector Hub and canonical mappings are the path for recurring operational data once the first SEUs are agreed.
How does this help with CSRD or CBAM?
Energy-carrier totals in TEP/TJ are the usual activity data for Scope 1 and 2. AEYS does not replace a full ISO 14064 inventory, but it stops energy figures from being rebuilt in a year-end spreadsheet for ESRS E1 or installation-level CBAM packs.
See it against your plant
Share a site, a carrier, and where the energy review lives today. We will map it onto the AEYS loop.