At portfolio scale, energy coordination means navigating 10 or 15 separate BMS interfaces. Each has different credentials, data formats, and alarm logs, with no consolidated view. Comparing Building 4 with Building 11 means gathering data from both systems, adjusting for square footage and operating schedules, then normalizing it manually. Most facilities teams instead run buildings independently, noticing cross-building patterns only after utility bills arrive.
The Default State: Isolated Visibility
Multi-building facilities management usually starts with fragmented visibility. Every BMS operates as its own island: Siemens Desigo in three buildings, Johnson Controls Metasys in two others, and Honeywell EBI in the newest building. Interfaces, historian formats, and APIs differ, when an API exists. Comparable data then requires manual work at each system or a custom integration layer that takes months to build and maintain.
Portfolio energy questions are often answered annually, when an energy manager or consultant gathers utility bills, adjusts for square footage or degree-days, and creates a benchmarking report. The report ranks buildings, but rarely explains underperformance. The needed context, including HVAC schedules, setpoint histories, and occupancy data, is absent from the utility bill.
What Portfolio Visibility Requires
Useful portfolio energy visibility combines three data layers that most facilities operations keep separate:
First is near-real-time consumption by building, measured in 15-minute intervals or less rather than monthly bills. Sources include utility interval data through Green Button Download or a utility API in most US jurisdictions, plus building submeters. Without intervals, intra-day patterns and the operating hours driving consumption remain hidden.
Second is normalized comparison. Buildings differ in size, vintage, and use, so raw kWh is not enough. Energy use intensity, or EUI, measured in kBtu per square foot per year, supports comparison, but full-year EUI trails by 12 months. Degree-day normalized monthly EUI is more useful. The key question is whether performance this month is better or worse than expected for the building's size, occupancy type, and weather exposure.
Third is zone or system-level BMS data. Utility readings show how much energy a building used; BMS readings show which systems drove that use and how they operated. Building 7 using 14% more HVAC energy than Building 3 is notable. Its chiller plant running at 40% higher load per ton of cooling delivered points toward the cause.
Why Dashboard Farms Fall Short
The first response to fragmented visibility is often a consolidated dashboard: move BMS data into a warehouse, add visualization, and give the facilities team one browser view of all 15 buildings.
That can support monitoring, but it leaves interpretation and action to the team. One screen containing 15 buildings' BMS data can create more work: more readings, a less familiar interface, and less context for understanding each value within its building.
The useful portfolio question is not "show me all the data." It is "which buildings need attention today and why?" That calls for analysis above the dashboard, reading all 15 buildings and surfacing actionable anomalies, efficiency opportunities, or declining performance. A building running 20% above its seasonal HVAC baseline during the 10am-2pm weekday window presents a clear investigation target. The dashboard exposes the spike; analysis identifies its timing and narrows the likely causes.
What Cross-Building Views Enable
Cross-portfolio visibility changes three parts of facilities work:
First, it supports prioritization. If Building 3, Building 7, and Building 11 all exceed their baselines this quarter, but Building 11's deviation is three times larger, attention can go there first. Without a shared view, teams may review all three equally or spend time on a building performing well.
Second, it reveals patterns between buildings. Several buildings in one climate zone consuming more during the same weather event provide useful calibration. A spike limited to one building suggests an operational issue there. Seeing the portfolio together separates shared conditions from building-specific anomalies.
Third, it improves capital planning. Normalized performance lets teams rank buildings against comparable type and vintage. Bottom quartile performers may warrant a different investment priority from top quartile performers. Building that ranking from 15 separate BMS systems and monthly bills is difficult; a consolidated performance view produces it directly.
Building the View Without a Data Team
For most early-stage portfolios, a custom data platform is not the right starting point. Connecting multiple BMS platforms takes substantial work, and maintaining those connections remains an ongoing burden.
A practical route is to connect a system that normalizes BMS protocols, including BACnet, Modbus, and others, while aggregating buildings without a separate integration effort for each one. DomeSystems was built for this use. The BMS connection supporting setpoint optimization in one building also supplies a normalized portfolio view as more buildings connect. Thermal models, occupancy analysis, and anomaly detection run per building, then appear in one interface for portfolio performance, without separate data infrastructure for the facilities team.
The aim is not to replace each BMS. It is to add a portfolio layer that answers cross-building questions without visiting every BMS interface.