Researched by BEAST Library Curator | Verified by Harper | Quality: 8.4/10

BaaS Just Got a Standard: How UNI 11973:2025, JCI-Nantum, and HCaaS Utilities Are Hardening the Contract Substrate Underneath "Building-as-a-Service"

BLUF: Until Q1 2026, "Building-as-a-Service" was a vendor pitch. As of May 2026 it is becoming a procurement category with code-level scaffolding. Italy's UNI 11973:2025 is the first national BaaS standard. Johnson Controls absorbed Nantum AI on April 27 to put a guaranteed-outcome HVAC algorithm under OpenBlue Net Zero Buildings-as-a-Service. ERA Partners' February 2026 majority stake in GeoTility is rolling out heating-and-cooling-as-a-service (HCaaS) as a regulated-utility analog. None of these moves invent BaaS — together they tell facility owners that the contract substrate underneath BaaS is hardening fast, and the question is no longer "should we?" but "which contract structure?"

If you are an FM or owner-operator with a 2026 capital plan, this matters this quarter. We covered the three deployment archetypes on April 27. This piece is the follow-on: how the contract layer evolved in 30 days, and what to put in your next RFP.

1. The Three Hardening Signals — In 90 Days

Three independent moves landed between February and May 2026 that, taken together, change BaaS from "marketing language" to "procurable category." None on its own would matter. The convergence is the news.

SignalDateWhat HardenedPractitioner Implication
UNI 11973:2025 (Italy/EU) Effective March 2025; ENEA + UNI First national BaaS standard. Defines BaaS as continuous-performance delivery (energy, IAQ, comfort) over the building lifecycle, not a one-off install. EU-jurisdiction owners can now write RFPs that reference UNI 11973 as the SLA framework — vendors who can't conform are down-selected at procurement, not at contract signing.
JCI acquires Nantum AI April 27, 2026 JCI puts a verified AI optimization layer underneath OpenBlue Net Zero BaaS. Adds real-time airflow + occupancy-driven HVAC control to a guaranteed-outcome contract. OpenBlue Net Zero BaaS now has a credible "guaranteed savings" tier. Owners can ask for ESCO-style guarantees on AI-HVAC outcomes, not just installed equipment.
ERA Partners → GeoTility February 2026 (majority stake) Capital + acquisition into a heating-and-cooling-as-a-service (HCaaS) utility model. TerraSource + Orca Energy operate geothermal infrastructure as a regulated-utility analog with no upfront cost to the developer. Multi-family + commercial developers in North America now have a third financing path: not own-the-system, not lease-the-system, but subscribe-to-the-thermal-utility. Greenfield projects can scope HVAC out of CapEx entirely.

2. The Three BaaS Contract Structures — Side by Side

Owners now have three credible contract structures. They are not interchangeable. Here's the side-by-side that should sit on every FM's desk before the next RFP cycle:

Structure Capital Treatment Performance Risk Best Fit Watchout
Guaranteed-Savings ESCO / Net Zero BaaS
(JCI OpenBlue, Siemens, Schneider, Trane EaaS)		 OpEx (subscription) or CapEx with financed payback Vendor covers the shortfall if savings underrun — guarantee is in the contract Existing assets with high-meter-count, long hold horizon, complex MEP, where retrofit CapEx is the bottleneck Baseline gaming. Insist on IPMVP Option C measurement and an independent M&V agent. Otherwise the "savings" are arithmetic, not engineering.
HCaaS / Geothermal Utility
(GeoTility/TerraSource/Orca, district heating)		 Pure OpEx — no upfront equipment cost; per-unit thermal energy charge Utility takes equipment, financing, AND availability risk; owner pays only for delivered Btu Greenfield multi-family + mixed-use, master-planned communities, campuses with central plant feasibility Asset lock-in. The thermal utility owns the loop. Termination clauses, rate-review mechanics, and end-of-term buyout matter more than headline price.
Energy-Aggregation BaaS
(KilowattLogic-style portfolio aggregation, 2026 RFP wave)		 OpEx procurement + optional financed asset layer Owner retains performance risk on the building; vendor takes commodity-procurement and demand-flexibility risk Multi-property portfolios (>10 buildings) where load-profile-blending of office + industrial creates wholesale-tier pricing access "Aggregation savings" overlap with rate-class savings — make sure quoted savings are AI/optimization-driven, not regulatory arbitrage that any ESCO would deliver.

3. APAC Read: Singapore Mandate + UNI 11973 Spillover

APAC is not a follower here — it is leading on two angles owners outside Singapore are missing:

For Taiwan and Hong Kong owners, UNI 11973:2025 is worth tracking even though it has no direct legal force in APAC. Italian standards have a habit of becoming EU-wide CEN reference standards within 24 months, which then become input to ISO TC 205 (building energy performance). If that pipeline runs its usual course, expect UNI 11973's BaaS definition to land as ISO reference language by 2028, at which point Singapore BCA and Hong Kong EMSD typically adopt within a single review cycle. Owners writing 10-year service contracts in 2026 should make sure their SLA language is forward-compatible with UNI's continuous-performance framing — otherwise a 2028 standard refresh forces a contract amendment with the vendor holding all the cards.

4. What I Would Do If This Were My Building (Next 90 Days)

  1. Audit your current vendor's contract against UNI 11973's BaaS definition. Three checks: (a) does the contract name continuous-performance KPIs or just installation milestones? (b) is there a measurement-and-verification clause that survives the warranty period? (c) does the SLA bind beyond Year 1? If any answer is no, the contract is "service" in name only.
  2. Pull a Tier-1 ESCO bid even if you don't intend to switch. Johnson Controls, Siemens, Schneider Electric, and Trane will quote OpenBlue / Building X / EcoStruxure / EaaS structures on request. The pricing is calibrating. Even if you stay in-house, the bid is the cheapest market intelligence you'll get on what your savings should be worth.
  3. If you are building greenfield in North America, add HCaaS to the financing menu. TerraSource, Orca Energy, Enwave, and a small bench of district-thermal players will quote the geothermal-utility model. Even if it doesn't pencil, the comparison reframes the CapEx conversation — your CFO will start asking why the in-house heat plant is on the balance sheet.
  4. For APAC operators, write the next RFP with optional UNI 11973 language. A simple "Vendor SLA shall be UNI 11973:2025 conformant or describe deviations" clause down-selects vendors who can't operate continuous-performance contracts. It costs nothing to add and saves a procurement cycle in 2027.
  5. Insist on a third-party M&V layer. Whether the contract is ESCO, HCaaS, or aggregation, the M&V instrumentation should be owned (or at minimum auditable) by the building owner, not the vendor. The vendor's optimization data flowing through their own meters is how baseline gaming happens.

5. The 2027 Question No Vendor Wants Asked Yet

Here is the question that will dominate the 2027 RFP cycle: if your AI-HVAC vendor and your BaaS vendor are different entities, who owns the optimization data? JCI's Nantum acquisition is the canonical "we own the stack" play — same legal entity owns the algorithm, the meter, the SLA, and the savings narrative. The HCaaS utility model is the canonical opposite — the utility owns the thermal infrastructure, the building owner owns the optimization data, and the boundary is metered.

For most owners, the right answer in 2027 will be hybrid: HCaaS for the thermal substrate, an independent AI-HVAC layer (which can but doesn't have to be the same vendor), and a third-party M&V agent that cannot be the optimization vendor. That's three contracts where there used to be one — but it's also three independent counterparties holding each other accountable. UNI 11973:2025 is the first standard that makes that separation legible in procurement language. Watch for the EU and APAC follow-on standards in the next 24 months.

6. Sources & Further Reading

Have a question about this topic? Ask our CRE AI Agent →