KNX Energy Dashboard with ARISTO BewO: kWh Trending, Peak Demand Alerts and ISO 50001
ARISTO BewO transforms KNX sub-meter group address values into an actionable energy monitoring dashboard — with trend charts per zone, SMS alerts when peak demand thresholds are exceeded, CO2 equivalent reporting for sustainability disclosures, and ISO 50001 baseline comparison for the facilities management team.
ARISTO BewO energy monitoring module: adding data points
ARISTO BewO separates alarm management from energy monitoring — the energy module is licensed separately and must be activated. Data points are added by selecting KNX group addresses and configuring the logging interval, display name, and unit for each energy zone.
BewO energy module configuration — adding a zone data point
BewO Energy Module → Add data point: Data point name: "HVAC Total Power" Group address: 6/0/0 (linked to Intesis KNX output) DPT: DPT 13.010 (4-byte signed, kW) Unit: kW Logging interval: 15 minutes (averaging: arithmetic mean) Display: Real-time tile + trend chart Data point name: "HVAC Import kWh" Group address: 6/0/1 (energy accumulator) DPT: DPT 12.001 (4-byte unsigned, kWh) Unit: kWh Logging interval: 15 minutes (pulse counter: delta between readings) Display: Daily/weekly/monthly bar chart Repeat for each zone: Lighting: GA 6/1/0 (kW), GA 6/1/1 (kWh) Transport: GA 6/2/0 (kW), GA 6/2/1 (kWh) DHW: GA 6/3/0 (kW), GA 6/3/1 (kWh) Small power: GA 6/4/0 (kW), GA 6/4/1 (kWh) Dashboard view: BewO → Energy → Overview → Real-time kW tiles for each zone (colour coded) → Total building consumption = sum of all zones → Trend selection: last 24h, 7 days, 30 days, 12 months
Peak demand monitoring: threshold alert via SMS
Peak demand monitoring prevents breaching the contracted maximum demand with the utility supplier, which would trigger a penalty charge. ARISTO BewO monitors the total building power GA and sends an SMS when the threshold is approached.
BewO peak demand alert configuration
Alarm object: "Peak Demand Warning"
Group address: 6/9/0 (total building power, DPT 13.010 kW)
Alarm condition: Value > 80 (threshold = 80 kW = 80% of 100 kW contract)
Alarm priority: Medium
Notification:
SMS to: +44 7xxx xxx xxx (FM manager)
Message: "DEMAND WARNING: Building power [value] kW at [time].
Contract limit: 100 kW. Reduce loads immediately."
Clear condition: Value < 70 kW (10% hysteresis to prevent SMS flood)
Acknowledgement: Not required (informational, auto-clears)
Maximum demand register (for utility tariff):
Some utilities measure 30-minute maximum demand (kVA or kW)
Configure BewO energy data point for 30-minute interval max:
GA 6/9/0: log every 15 minutes → calculate 30-minute max
Export: monthly CSV for utility bill verification
Reactive power alert (kVAr penalty avoidance):
Add data point: GA 6/9/2 (total reactive power DPT 13.010 kVAr)
Alert if cos-phi < 0.90 for > 30 minutes:
→ SMS: "Low power factor [value] — capacitor bank fault?"
→ Action: check whether power factor correction capacitors
are operating (KNX binary output on PFC contactor feedback)CO2 equivalent reporting for sustainability disclosure
Carbon equivalent reporting converts electricity consumption (kWh) into kg of CO2 using the national grid emission factor. ARISTO BewO calculates CO2 equivalents by multiplying logged kWh totals by the configured emission factor — updated annually as national grids decarbonise.
| Country / year | Grid emission factor | Source | Update frequency |
|---|---|---|---|
| UK 2024 | 0.212 kgCO2/kWh | DESNZ / BEIS | Annual (July) |
| Germany 2024 | 0.380 kgCO2/kWh | UBA (Umweltbundesamt) | Annual (March) |
| EU average 2024 | 0.233 kgCO2/kWh | EEA (European Environment Agency) | Annual (Q1) |
| Latvia 2024 | 0.104 kgCO2/kWh | LETA / CSB | Annual |
| France 2024 | 0.049 kgCO2/kWh | RTE | Annual (March) |
BewO CO2 calculation configuration
BewO Energy → CO2 Settings: Emission factor: 0.212 (UK 2024, update annually in July) Calculation: Total kWh (all zones) × emission factor Display: kgCO2 per day/week/month/year trend chart Annual CO2 report (example — 500,000 kWh/year office): Total consumption: 500,000 kWh CO2 (UK 2024): 500,000 × 0.212 = 106,000 kgCO2 = 106 tCO2 CO2 (Germany 2024): 500,000 × 0.380 = 190,000 kgCO2 = 190 tCO2 5-year trend (grid decarbonisation visible): 2020: 500,000 kWh × 0.233 = 116.5 tCO2 2021: 500,000 kWh × 0.220 = 110.0 tCO2 2022: 500,000 kWh × 0.210 = 105.0 tCO2 2023: 500,000 kWh × 0.210 = 105.0 tCO2 2024: 500,000 kWh × 0.212 = 106.0 tCO2 Note: emission factor updates are not automatic — FM team must update the BewO CO2 factor annually using latest published value. BewO does not connect to external emission factor APIs.
ISO 50001 energy baseline and EnPI configuration
ISO 50001 energy management systems require an energy baseline (EnB) established from 12 months of measured data, and an Energy Performance Indicator (EnPI) that tracks improvement against the baseline over subsequent years. ARISTO BewO provides both through its reporting module.
ISO 50001 baseline and EnPI in ARISTO BewO
Step 1 — Establish energy baseline (EnB):
Period: First 12 months of operation (Year 0)
Data: Total building kWh from GA 6/9/1 (utility meter kWh)
Normalisation: Adjust for occupancy hours and HDD (if significant)
BewO: Export 12-month kWh CSV → calculate annual baseline
Store baseline value in BewO documentation field
Example baseline: 500,000 kWh (Year 0, 2024)
Step 2 — Define EnPI:
EnPI formula: Actual energy / Baseline energy × 100%
Target: < 100% = improvement against baseline
Stretch target: < 90% at Year 3 (10% reduction programme)
Step 3 — Annual EnPI calculation in BewO:
Year 1 actual: 480,000 kWh
EnPI Year 1: 480,000 / 500,000 × 100% = 96% (4% improvement)
Year 2 actual: 462,000 kWh
EnPI Year 2: 462,000 / 500,000 × 100% = 92.4% (7.6% improvement)
BewO reporting:
Annual report: total kWh per zone, EnPI vs baseline, CO2 total
PDF export → email to FM director (automated monthly summary)
ISO 50001 auditor evidence: 3-year trend showing improvementAutomated monthly energy reports for facilities management
ARISTO BewO generates and emails PDF energy reports automatically at configured intervals. Monthly reports give the FM team a consistent energy performance overview without manual data extraction.
BewO automated monthly report configuration
BewO → Reports → Scheduled Reports → Add report:
Report name: "Monthly Energy Report — [building name]"
Schedule: 1st day of each month, 08:00
Report period: Previous calendar month
Content sections:
1. Total building consumption (kWh) — bar chart monthly comparison
2. Zone breakdown (HVAC, Lighting, Transport, DHW, Small power)
— Pie chart % of total
3. Peak demand record — maximum kW during the month + timestamp
4. Power factor — average cos-phi for the month per phase
5. CO2 equivalent — total kgCO2 for the month
6. EnPI vs baseline — bar showing this month vs baseline monthly avg
7. Alarms summary — number of demand warnings, meter fault alerts
Email settings:
To: fm@building.com; energy.manager@building.com
CC: sustainability@occupier.com (if applicable)
Format: PDF attachment + inline summary table
KNX tariff integration (optional):
GA 6/9/3: current tariff rate DPT 9.001 (€/kWh, updated by occupier)
BewO cost column: kWh × tariff rate = estimated cost per zone per month
Note: tariff GA must be manually updated when utility rates changeCommissioning: data continuity and retention policy
After all energy data points are configured in BewO, commissioning verifies that 15-minute data logging runs continuously without gaps, the email reporting functions correctly, and the backup and retention policy is in place.
BewO energy commissioning verification checklist
1. Data continuity check (after 24 hours of operation): BewO → Energy → HVAC Power trend → 24-hour view → Confirm data logged every 15 minutes (96 data points per day) → No gaps in trend (gap = Modbus poll failure or BewO restart) → If gaps visible: check Modbus gateway connectivity, BewO logs 2. Value plausibility check: Compare BewO HVAC kWh for yesterday with meter front-panel Tolerance: ±2% (difference due to 15-minute averaging) If >5% difference: check DPT configuration (kW vs kWh mix-up) 3. Email report test: BewO → Reports → Send test report now Confirm PDF received at all configured email addresses Check: all 7 sections present, no #ERROR values in charts 4. Peak demand alert test: Use ETS6 Group Monitor: write 85 to GA 6/9/0 (simulate 85 kW) Confirm SMS received within 60 seconds Write 0 to GA 6/9/0 — confirm alert clears (no further SMS) 5. Backup configuration: BewO → System → Backup → NAS share \serverewO-backup Schedule: daily at 03:00 Retention: keep 30 daily backups + 12 monthly snapshots BREEAM requirement: 5-year data retention (verify storage capacity) 6. UPS test for BewO server: Simulate mains power loss (switch off BewO server UPS input) Confirm BewO continues running on battery Confirm data logging does not gap during power event
Need ARISTO BewO energy monitoring with KNX sub-metering?
We configure ARISTO BewO energy dashboards with KNX sub-meter integration, 15-minute logging, peak demand SMS alerts, ISO 50001 EnPI reporting, and automated monthly PDF reports for your FM team.
Request a quote →