A property management company can have meters on every asset, a BMS with full engineering system coverage, and even IoT sensors in every room and still have no clear picture of where energy is being wasted or why this month’s costs are higher than last month’s. The data exists. But it is scattered, incomparable across systems, and unavailable at the moment it is needed.
An energy efficiency dashboard is not simply a visual for an investor presentation. It is an operational tool that converts fragmented consumption data into concrete signals for decision-making. And, like any tool, it can be built well or built poorly.
Industry EUI Benchmarks: A Reference Point for Your Portfolio
Before building a dashboard, it is useful to understand where your portfolio stands relative to industry norms. EUI (Energy Use Intensity) is the most universal metric for cross-asset comparison.
| Building Type | Average EUI (kWh/m²/year) | Efficient Level | Source |
|---|---|---|---|
| Office building | 180–250 | < 120 | ENERGY STAR, CBECS |
| Shopping center | 300–450 | < 220 | ENERGY STAR |
| Residential complex (multifamily) | 120–180 | < 90 | EU Energy Performance Directive |
| Hotel | 280–420 | < 200 | CBRE Energy Benchmarking |
| Warehouse / logistics | 80–130 | < 60 | ENERGY STAR |
| Hospital / medical facility | 550–750 | < 400 | ASHRAE |
If your property’s EUI exceeds the average for its building type, that is not cause for alarm, but it is a clear signal that a dashboard is needed now, not “at some point.”
What Is Wrong With Typical Dashboards
Before discussing how to build, it is worth understanding why most existing solutions fail to perform as expected.
- Too much data, too little context. A dashboard displaying 40 charts simultaneously does not support decision-making — it moves the problem from one spreadsheet to another. Without prioritization and context, a manager does not know where to look first.
- No benchmarks. The figure “18,500 kWh for the month” means nothing without comparison against last month, against a similar asset in the portfolio, against the industry standard for that building type.
- Data updated once a month. A monthly refresh turns a dashboard into a reporting tool rather than a management tool. By the time a manager sees an anomaly, it has already cost money.
- No link between consumption and context. A spike in energy use could be caused by unusually cold weather, a 300-person event, or a failing chiller. Without contextual data weather, occupancy, calendar it is impossible to tell one from another.
Key Metrics: What the Dashboard Should Measure
Before designing a dashboard, it is essential to determine which metrics actually drive operational decisions.
| Metric | What It Measures | Why It Matters | Data Source | Update Frequency |
|---|---|---|---|---|
| EUI (Energy Use Intensity) | kWh/m² per year | Enables cross-asset comparison and benchmarking against industry norms | Meters, BMS | Monthly |
| System-level consumption share | % of total for HVAC, lighting, elevators | Identifies where optimization potential lies | BMS, sub-metering | Hourly |
| Peak load | kW during peak hours | Supports tariff zone management and cost reduction | Meters, tariff APIs | Real-time |
| Baseline deviation | % deviation from norm for a given day type / season | Signals anomalies and potential equipment faults | BMS + weather data | Real-time |
| Carbon intensity | kg CO₂/m² | Required for ESG reporting and EU Taxonomy compliance | Meters + emissions API | Monthly |
| Cost per unit | $ per m² or per tenant | Connects consumption to financial performance | Financial systems + meters | Monthly |
Dashboard Architecture: Three Levels
An effective energy efficiency dashboard is built on the principle of “from general to specific” — answering different questions depending on the level of detail required.
Level 1. Portfolio overview. A single screen with key KPIs across all assets: EUI ranking, budget deviation, properties with anomalous consumption this week. The goal: understand in 30 seconds where the problem is and where to look next.
Level 2. Asset dashboard. A detailed view of a specific property: consumption trends by system, year-over-year comparison, correlation with weather and occupancy, equipment status. The goal: understand the cause of the deviation.
Level 3. System / zone drill-down. Granular view of a specific engineering system or building zone: hourly HVAC consumption charts, floor-level temperature profiles, readings from individual meters. The goal: localize the problem and define a technical brief for the service team.
Data Sources and Integrations
A dashboard does not exist in isolation — it aggregates data from multiple systems, and the quality of integrations determines the quality of analytics.
Primary sources:
- Meters and sub-metering: the foundational data collection point for electricity, gas, and water consumption across assets and systems.
- BMS (Building Management System): real-time operational data from engineering systems.
- IoT sensors: micro-zone data on temperature, occupancy, and air quality.
- External APIs: weather data (to contextualize consumption), tariff schedules (for real-time cost calculation).
- Financial systems: to link consumption figures to budgets and operating costs.
A critical requirement: data must update in real time or with minimal delay — within 15 minutes for operational decisions, within 1 hour for analytical use.
Want to understand which dashboard architecture fits your portfolio or product? ORIL Innovation offers free consultations for teams working in Smart Buildings and energy efficiency. We help clarify the right technology approach, solution architecture, and practical first steps toward implementation. → Book a Free Consultation
What to Consider When Designing: A Checklist
- End users and their use cases are defined (property manager, portfolio director, ESG officer — each has different needs)
- A core set of metrics is agreed upon — no more than 7–10 per level
- Update frequency is defined for each data source
- Automated alerts are configured for deviations beyond a set threshold from the baseline
- Cross-asset benchmarking capability is in place
- A mobile version is available for managers working on-site
- The dashboard is integrated with the maintenance request system — so an anomaly immediately converts into a task
Where to Start If You Have No Dashboard Yet
The most common mistake is waiting until “everything is ready” before building: all systems integrated, all sensors installed, all metrics agreed upon. In practice, that moment never arrives.
A minimum viable starting point — available right now:
- Weeks 1–2. Collect what you already have. Export data from existing meters for the past 12 months. Even an Excel file from your electricity provider is a baseline. Calculate EUI for each property and compare against the industry benchmarks in the table above.
- Weeks 3–4. Identify one priority metric. Do not try to measure everything at once. Choose the single metric with the greatest impact on operating costs — typically either peak load or HVAC consumption share. Set up weekly monitoring for that indicator.
- Month 2. Launch an MVP dashboard. A minimum viable dashboard is 5–7 metrics, automatic daily data refresh, and one level of detail — the portfolio overview. Even Google Looker Studio connected to Google Sheets delivers this level of functionality without complex development.
- Month 3+. Add integrations iteratively. Connect new data sources as infrastructure readiness allows: BMS → IoT sensors → weather APIs → financial systems. Each new integration enriches the analytical context — but none of them is a precondition for getting started.
Common Mistakes When Building
- “We’ll do everything at once.” A dashboard with 50 metrics and 20 integrations that takes 8 months to build — and is already partially outdated by the time it launches. The right approach: an MVP with 5–7 core metrics and one level of detail, launched in 6–8 weeks and improved iteratively.
- Ignoring UX. A dashboard that is difficult to use does not get used. Design must start with interviews with actual users not with a technical specification for data integrations.
- No alerts. A dashboard that requires a manager to actively log in to spot a problem is a passive tool. An active alert system transforms it from an information screen into an operational assistant.
An energy efficiency dashboard is not a one-time project — it is a product that evolves alongside the team’s needs. The best examples in the industry started with simple consumption monitoring and gradually grew into full-scale operational analytics platforms with predictive capabilities. The key is to start with a specific operational need — not with the ambition to build “the best dashboard possible.”
More PropTech & energy efficiency
Subscribe to the blog and listen to the Innovation Blueprint podcast — practical insights at the intersection of AI, IoT and real estate.
Working on building performance or energy data?
ORIL works with real estate companies on Smart Building platforms, IoT integrations, building analytics and custom software development.
Explore Smart Buildings & IoT →Talk to a technology expert →