ISO 50001 Energy Reporting from KNX Modbus Metering
ISO 50001:2018 requires documented energy baselines, performance indicators, and measurable monitoring data. KNX buildings with Modbus sub-metering already have the measurement infrastructure in place — this guide shows how to structure that data into a compliant energy management system ready for third-party certification audit.
ISO 50001:2018 overview and EU regulatory context
ISO 50001:2018 is the international standard for energy management systems (EnMS). It applies the Plan-Do-Check-Act (PDCA) cycle to energy: organisations establish an energy policy and energy review (baseline), define energy performance indicators (EnPIs) and targets, implement action plans (energy conservation measures), and monitor results against the baseline. Annual management reviews close the PDCA loop.
In the EU regulatory context, ISO 50001 certification is increasingly relevant under the Energy Efficiency Directive (EED) recast of 2023. Large non-SME enterprises must conduct energy audits every four years, or alternatively implement and maintain an ISO 50001 certified EnMS as an equivalent compliance pathway. For commercial building owners and occupiers managing significant energy expenditure, ISO 50001 certification provides both regulatory compliance and demonstrable energy cost reduction.
ISO 50001 core requirements relevant to KNX buildings
- Energy review: 12-month baseline consumption data by boundary and sub-boundary
- Significant energy users (SEUs): equipment with highest consumption or improvement potential identified and sub-metered
- Energy performance indicators (EnPIs): measurable metrics normalised for relevant variables (area, occupancy, weather)
- Monitoring, measurement and analysis (MMA) plan: documented measurement system with meter accuracy class and calibration
- Action plan monitoring: before/after measurement evidence for each energy conservation measure (ECM)
- Internal audit: annual verification that the EnMS is implemented and maintained
Energy baseline from KNX Modbus metering
The ISO 50001 energy baseline requires 12 months of metered consumption data per energy boundary and sub-boundary. In a KNX commercial building, Carlo Gavazzi EM340 three-phase MID Class B energy meters — one per distribution board or major circuit — provide the sub-metering data. These meters communicate via Modbus RTU, read by a WAGO 750-893 Modbus/KNX gateway, and published to KNX group addresses accessible to the BMS.
Metering hierarchy for ISO 50001 boundary definition
Building boundary (import metering):
Main incomer meter (utility billing meter, MID Class A)
Sub-boundaries (KNX Modbus EM340 meters):
HVAC distribution board → 35-50% of total (typical)
Lighting distribution board → 20-30% of total
Equipment (sockets, IT) → 20-35% of total
Hot water / catering → 5-10% of total
Significant energy user (SEU) sub-metering:
HVAC compressor circuit → dedicated EM340
Server room PDU → dedicated EM340
Process equipment → dedicated EM340
Each EM340 meter publishes its active power (kW) and cumulative energy (kWh) to KNX group addresses via the WAGO gateway. The BMS logs these GAs at 15-minute intervals and retains data for five years. At the end of the baseline year, the BMS database contains the complete 12-month consumption profile for each sub-boundary and SEU circuit.
Energy performance indicators (EnPIs)
EnPIs translate raw kWh data into meaningful performance metrics that can be compared between years and between similar buildings. ISO 50001 does not mandate specific EnPIs — they must be appropriate to the organisation and relevant to the significant energy uses.
| EnPI | Formula | KNX data source | Normalises for |
|---|---|---|---|
| kWh/m²/year | Annual total kWh ÷ conditioned floor area (m²) | BMS annual total from EM340 KNX GAs | Building size |
| kWh/occupant-day | Annual kWh ÷ (occupancy days × number of occupants) | EM340 kWh + KNX presence detector occupancy hours | Occupancy intensity |
| kWh/HDD (heating) | Annual heating kWh ÷ annual heating degree days | HVAC EM340 kWh + KNX outdoor temp GA for HDD calc | Outdoor climate variation |
| HVAC kWh/m² | Annual HVAC kWh ÷ conditioned area | HVAC distribution board EM340 GA | HVAC efficiency vs area |
Weather normalisation with degree-day calculation
Year-to-year comparison of heating energy is misleading without weather normalisation: a colder winter requires more heating regardless of efficiency improvements. The degree-day method removes this variation. Heating degree days (HDD) for a given period are calculated as the sum over each day of the maximum of zero or (15.5°C minus the daily mean outdoor temperature). Days with mean temperature above 15.5°C contribute zero HDD (no heating expected).
In a KNX building, the outdoor temperature is available from a KNX weather station GA — typically a Theben RDZ 2 or Elsner P03 publishing outdoor temperature as DPT 9.001. A WAGO 750-352 CODESYS PLC reads this GA at midnight each day, calculates the daily mean, computes the day's HDD contribution, and accumulates a running monthly HDD total stored in WAGO retain memory (persists across power cycles). The monthly HDD value is published to a dedicated KNX group address (for example 5/8/0, DPT 9.002 value in degree-days) where the BMS logs it.
CODESYS degree-day calculation logic (pseudocode)
At midnight (daily task):
daily_mean_temp := average of 24 hourly outdoor temp readings
hdd_today := MAX(0, 15.5 - daily_mean_temp)
monthly_hdd_accumulator := monthly_hdd_accumulator + hdd_today
On first day of month:
Write monthly_hdd_accumulator to KNX GA 5/8/0 (DPT 9.002)
Reset monthly_hdd_accumulator := 0
BMS logs the monthly HDD value from KNX GA
Normalised heating EnPI:
normalised_heating_kWh_per_HDD := monthly_hvac_kWh / monthly_hdd
If this value falls between years: efficiency improved
If this value rises: HVAC efficiency degraded or building fabric issue
Significant energy users (SEUs)
ISO 50001 requires identifying and monitoring the equipment or systems that consume the largest proportion of energy or have the most significant improvement potential. These are designated significant energy users (SEUs) and must each have their own monitoring arrangements.
In a KNX commercial building, the typical SEUs are the HVAC compressor plant (usually 35–45% of total building energy), the server room cooling system (often 8–15%), and any process equipment specific to the tenancy. Dedicating one Carlo Gavazzi EM340 meter per SEU circuit provides the individual monitoring required. The EM340 Modbus registers for each SEU circuit are mapped to separate KNX group addresses, published to the BMS, and trended individually.
SEU identification criteria
- Consumes more than 10% of total site energy: mandatory SEU
- Significant improvement potential identified in energy review
- Subject to an energy conservation measure (ECM) action plan
- Required to demonstrate compliance with EED or building regulations energy targets
KNX metering per SEU
- Dedicated Carlo Gavazzi EM340 on SEU distribution circuit
- Modbus registers: active power (kW) and cumulative energy (kWh)
- WAGO gateway maps to dedicated KNX GA per SEU (not shared with sub-boundary GA)
- BMS trends SEU GA at 15-minute interval, 5-year retention
- Monthly SEU report: BMS trend export CSV reviewed in management review
Monitoring, measurement and analysis plan
ISO 50001 clause 9.1.1 requires a documented monitoring, measurement and analysis (MMA) plan. The MMA plan specifies for each measured energy parameter: what is measured, how it is measured (meter type and accuracy class), where it is installed (circuit ID and location), the measurement frequency, and who is responsible for analysis.
KNX Modbus metering meets the MMA requirements when the following are documented: the Carlo Gavazzi EM340 is a MID-certified Class B meter (measurement uncertainty ≤1% for active energy), the meter serial number and calibration date are recorded in the as-built documentation, and the installation location and circuit are identified in the IEC 61439 panel schedule and single-line diagram. MID certification means no periodic recalibration is required for the meter's rated lifetime under normal conditions — the MID certificate serves as the calibration record.
MMA plan documentation checklist for auditors
- Meter schedule: circuit ID, meter type (EM340), serial number, accuracy class (Class B), MID certificate number, installation date
- As-built single-line diagram: meter location on circuit clearly marked
- WAGO gateway configuration: Modbus register map showing which EM340 Modbus register maps to which KNX GA
- BMS trend configuration: GA address, logging interval (15 min), retention period (5 years) for each metered circuit
- Frequency of analysis: monthly energy review by energy manager, annual management review
KNX energy dashboard for ISO 50001 reporting
An energy dashboard on the Gira X1 or a Home Assistant instance provides the FM team and energy manager with real-time visibility of all metered boundaries. The dashboard displays current power draw per sub-boundary in kW, daily and monthly kWh totals per boundary, the current EnPI (kWh/m²) against the annual target, and the weather-normalised comparison versus the baseline year.
Automated monthly reporting via WAGO CODESYS
On first day of each month (CODESYS scheduled task):
Read EM340 cumulative kWh register for each circuit
Calculate monthly kWh = current kWh - previous month kWh
Write monthly kWh to KNX retain GA per circuit
(retain memory: persists across power cycles)
BMS logs the monthly total KNX GA value → SQL database
Monthly report: BMS Report → Energy Overview → select all
circuit GAs → date range = current month → export CSV
Energy manager reviews CSV against target EnPI values
Monthly totals pasted into ISO 50001 annual review template
Action plan monitoring and ECM verification
ISO 50001 action plans document specific energy conservation measures (ECMs) with baseline measurement, target, implementation date, responsible person, and post-implementation verification measurement. KNX metering provides the before and after data.
A practical example: the ECM is "install KNX presence sensors for HVAC setback in meeting rooms, target 15% reduction in HVAC circuit energy." The baseline is the three-month average daily kWh of the HVAC distribution board EM340 circuit before the sensors are installed. After installation and three months of operation, the BMS trend export for the same circuit shows the actual reduction. KNX presence detector GAs confirm occupancy hours changed as intended — empty rooms are now setback to 18°C rather than maintained at 21°C continuously.
Presenting ECM results to the ISO 50001 auditor: the BMS trend report (CSV exported from Desigo CC or equivalent, with timestamps) for the HVAC circuit GA before and after the ECM implementation date constitutes the measurement evidence required by ISO 50001 clause 6.3. The presence detector GA trend (occupancy hours per day) corroborates the setback strategy was active. Both reports should be retained in the EnMS document control system for the audit.
Third-party verification and certification audit
ISO 50001 certification requires a third-party audit by an accredited certification body — Lloyd's Register, Bureau Veritas, SGS, or TÜV are the main providers in Europe. The initial certification audit (Stage 1 documentation review plus Stage 2 on-site audit) verifies that the EnMS has been implemented and is effective. Surveillance audits follow annually, with full recertification every three years.
The auditor will request the measurement system documentation as part of clause 9.1.1 evidence. The KNX as-built documentation package should include: the panel meter schedule (circuit, EM340 serial number, MID certificate number, CT ratio where applicable), the WAGO Modbus register map linking each EM340 Modbus register to its KNX GA, the BMS trend configuration screenshot showing the logging interval and retention for each energy GA, and a sample 12-month CSV export showing the baseline year data.
Audit evidence package for KNX metering system
- Meter schedule: circuit ID, EM340 model and serial number, MID certificate number, accuracy class B, installation date, CT ratio if used
- As-built single-line diagram with meter locations marked (PDF, revision-controlled)
- WAGO Modbus configuration export: register map document or PDF of WAGO I/O Check configuration
- BMS trend configuration: screenshot or PDF of trend settings (GA address, 15-minute interval, 5-year retention) for each circuit
- 12-month baseline CSV: timestamped kWh records per circuit exported from BMS database for the baseline year
- ECM before/after reports: BMS trend CSV exports for each energy conservation measure verification period
Common audit finding: CT ratio not documented
Where the Carlo Gavazzi EM340 is connected to current transformers (CTs) for circuits above 100A, the CT ratio (e.g. 400:5A, ratio 80) must be set correctly in the EM340 configuration and documented in the meter schedule. Auditors regularly find that CT ratios are set but not documented — creating a measurement uncertainty gap in the MMA plan. Always include CT type, ratio, and accuracy class (Class 1 minimum for ISO 50001) in the as-built meter schedule alongside the EM340 serial number.
Need KNX panels with MID-certified metering for ISO 50001?
We build KNX panels with Carlo Gavazzi EM340 MID Class B sub-metering on every significant circuit, WAGO Modbus-to-KNX gateway pre-configured, and a complete meter schedule with serial numbers and MID certificate references — providing audit-ready documentation from day one.
Request a quote →