A mid-size office portfolio in New York faces three distinct data problems simultaneously. Its lease management system holds the CAM reconciliation terms for 47 active leases. Its LL97 compliance tracker shows projected fine exposure for 2026 and 2024. Its BMS records real-time HVAC runtime, chiller staging, and electricity consumption across 8 buildings.
These three data streams live in three different systems, managed by three different teams. None of them talk to each other in a way that generates an actionable answer to the portfolio manager's real question: "Which buildings are overpaying on operating costs because of lease structure, and which ones are actually triggering LL97 fines I could avoid with a targeted retrofit?"
That question cannot be answered by any single PropTech platform on the market today. This article explains why — and what to do about it.
The Three Layers and Why They Stay Siloed
Every commercial building portfolio has three operational data layers that intersect but are almost never integrated:
| Layer | Data type | Typical system | Team owner |
|---|---|---|---|
| 1. Lease / Financial | CAM terms, rent escalations, expense stops, pass-through caps | MRI, Yardi, VTS | Asset management / legal |
| 2. Compliance / Regulatory | LL97 fine exposure, ENERGY STAR ratings, ASHRAE audit requirements, BOMA standards | Spreadsheets, Arc, custom tools | Sustainability / compliance team |
| 3. Building Performance | Energy consumption (kWh/sqft), HVAC runtime, EUI, sensor telemetry | BMS, Schneider EcoStruxure, Siemens Desigo | Engineering / FM |
These layers are siloed for organizational reasons that predate AI by decades. Lease management belongs to asset managers because it is a legal and financial function. Energy management belongs to engineers because it is a technical and operational function. Compliance tracking belongs to sustainability teams because it is a regulatory and reporting function.
The problem: none of the decisions made in each layer are actually independent. They depend on each other.
Three Costly Blind Spots That Integration Would Close
Blind Spot 1: CAM Caps That Eat Retrofit ROI
A building owner approves a $400,000 HVAC retrofit projected to save $85,000/year in energy costs. Payback: 4.7 years. The project looks viable. But the lease for the anchor tenant — 42% of the building's leasable area — has a CAM cap clause preventing energy cost pass-through increases above 3% per year.
The retrofit reduces the building's energy bill by $85,000 — but because energy costs are passed through to tenants under gross lease terms, the owner captures only the savings above the CAM cap. Net benefit to owner: $23,000/year. Actual payback: 17 years. The project should not have been approved at that cost.
This analysis requires crossing Layer 1 (lease CAM terms) with Layer 3 (building energy performance). No lease management system and no BMS platform performs this calculation together. Most owners discover the mismatch after the retrofit is already approved.
Blind Spot 2: LL97 Fine Exposure Masked by Incomplete EUI Data
New York City's Local Law 97 levies fines on commercial buildings that exceed carbon intensity limits in 2024 and again in 2030. The fine is calculated per tonne-CO2 above the limit — currently $268/tonne. A building with a 15,000 sqft office floor plate emitting 50 tonne-CO2 above its limit owes $13,400 in fines that year.
Compliance teams track LL97 exposure using utility bill data. But utility bill data lags by 30–60 days, does not distinguish between base building and tenant consumption, and cannot identify which specific systems are driving the overage.
Layer 3 (real-time BMS sensor data) can identify the overage driver — an oversized chiller running at 20% load during shoulder season, a vestibule AHU left on a summer schedule year-round — with enough lead time to make an operational change before the compliance period closes. Layer 2 (LL97 compliance tracking) knows the fine threshold. But these two systems never talk to each other in real time.
Blind Spot 3: Net Lease True-Ups That Conflict With Energy Retrofit Timing
A net lease true-up cycle occurs annually, typically 90–120 days after year-end. If a building owner completes an energy retrofit in Q3, the energy savings will appear in the building's operating costs for Q4 only — a partial year. The annual true-up will reflect an anomalous hybrid cost baseline. Tenants under net leases may dispute the reconciliation. The correct response requires knowing the retrofit's activation date (Layer 3), the lease true-up clause language (Layer 1), and the applicable BOMA standard for expense allocation (Layer 2).
This intersection is handled manually, by email, between three different teams, weeks after the issue surfaces. It should be a two-second query.
Why No Single Platform Closes This Gap Today
The integration gap persists because the three layers grew up in different software ecosystems with different business models:
- Lease management platforms (MRI, Yardi, VTS) are optimized for lease abstraction, rent collection, and portfolio reporting. They do not ingest sensor data.
- BMS platforms (Schneider, Siemens, Honeywell) are optimized for HVAC control and alarm management. They do not ingest lease terms or compliance thresholds.
- Compliance tools are mostly spreadsheet-based or early-stage SaaS, built to satisfy reporting requirements — not to drive operational decisions.
Cherre connects these data sources via a unified data graph — but data federation is not domain intelligence. Connecting the data does not produce the answer to "should I approve this retrofit given my CAM cap?" That requires protocol knowledge: IPMVP measurement boundaries, BOMA expense allocation standards, LL97 fine calculation methodology.
The Integration Query
"Given my lease CAM structure, my building's current EUI, and my LL97 baseline period — what is my net-present-value case for a chiller replacement versus operational tuning?"
This is a three-layer query. AISB's Agent Door is designed to answer it.
What the Integration Actually Enables
When lease terms, compliance exposure, and building sensor data are queryable together — through an agent with embedded domain knowledge of all three — the operational decisions that currently take days of cross-team coordination become sub-minute queries:
- Which of my 12 NYC buildings have the highest LL97 fine exposure AND CAM structures that allow me to pass through retrofit costs?
- Which HVAC retrofits pencil out under IPMVP Option B after accounting for lease pass-through caps?
- My anchor tenant's lease expires in 18 months. What does my building's energy performance look like against ENERGY STAR in that lease's renewal window?
None of these questions require new data. The data exists in every mid-size CRE portfolio. What has been missing is an agent that can hold all three layers simultaneously and apply protocol-grade reasoning across them.
Query Across All Three Layers
Lease structure + LL97 compliance + building performance — answered together, not in separate siloed systems.
Ask about your specific building, lease type, or compliance exposure. Free to start.
Related reading: Why CBM Fails as a Bolt-On | Your Building Doesn't Need More Data | Why Enterprise Building AI Can't Use the Cloud