Latest / NOXTalks / The Cloud BMS Exit Plan Nobody Wrote

Transcript

The Cloud BMS Exit Plan Nobody Wrote · NOXTalks

• 0:07
  SPEAKER_00: Welcome to Knox Talks, the AI-generated podcast exploring the groundbreaking ways technology shapes our built environment.
• 0:14
  SPEAKER_00: Today we're diving into the cloud BMS contract you probably already signed, and the four questions that should have been in it.
• 0:21
  SPEAKER_00: Because cloud-based BMS isn't an early adopter idea anymore.
• 0:26
  SPEAKER_00: The migration is happening, contracts are getting signed, and too often the conversation moves on before anyone asks the boring exit questions.
• 0:34
  SPEAKER_00: Here's the data: the Association for Smarter Homes and Buildings, working with Harbor Research, ran its 2025 Smart Building Trend Survey across 308 North American respondents.
• 0:46
  SPEAKER_00: Nearly half said they use cloud-based BMS for most or all systems.
• 0:50
  SPEAKER_00: Another 28% said they're actively planning adoption.
• 0:54
  SPEAKER_00: So the trend is real, but too few teams seem to be asking what happens when they need to leave.
• 1:00
  SPEAKER_00: Question one: Who owns your historical trend data, not the live points, the history?
• 1:07
  SPEAKER_00: Five years of chiller performance, three years of override patterns, the long tail of fault data that could become valuable for AI, analytics, and optimization.
• 1:18
  SPEAKER_00: In many cloud BMS contracts, that history sits on the vendor's infrastructure, in the vendor's schema, and the contract is quiet about whether it can be pulled down on the way out, and quiet isn't good enough.
• 1:31
  SPEAKER_00: Question two: if the data does come with you, what format is it in?
• 1:37
  SPEAKER_00: A CSV dump of 800,000 time-stamped rows with cryptic point names is technically your data, but practically it's painful to use.
• 1:46
  SPEAKER_00: This is where semantic data models became a procurement issue.
• 1:49
  SPEAKER_00: Project Haystack, BRICS Schema, and the proposed ASHRAY 223 standard can give the metadata around your data a structure that travels, equipment, relationships, units, locations, and point meaning.
• 2:03
  SPEAKER_00: But semantic schemas describe context.
• 2:06
  SPEAKER_00: They don't automatically guarantee the trend values come with the export.
• 2:10
  SPEAKER_00: That still has to be in the contract in writing.
• 2:14
  SPEAKER_00: Fun fact: Project Haystack announced Haystack 5 with the new Zeto schema language on May 13, 2025.
• 2:22
  SPEAKER_00: Zeto added formal schema definitions, validation, inheritance, composition, and RDF export.
• 2:29
  SPEAKER_00: Translation: The tooling for portability got more real.
• 2:33
  SPEAKER_00: Whether your contract uses it is another question.
• 2:36
  SPEAKER_00: Question 3.
• 2:38
  SPEAKER_00: What happens if the vendor gets acquired or sunsets the platform?
• 2:42
  SPEAKER_00: The BMS market has been consolidating for years.
• 2:45
  SPEAKER_00: Smaller analytics platforms get bought by larger OEMs.
• 2:50
  SPEAKER_00: Larger OEMs retire legacy products to move customers onto the new flagship.
• 2:55
  SPEAKER_00: Kimonuma's Four Laws for Intelligent AI and Digital Twins, published on automatedbuildings.com in March 2025, included a law that's basically a procurement principle.
• 3:07
  SPEAKER_00: Owners retain control and there should be no vendor lock-in.
• 3:11
  SPEAKER_00: The fact that this had to be written down tells you a lot.
• 3:14
  SPEAKER_00: Question four.
• 3:15
  SPEAKER_00: What does your building do during a cloud outage?
• 3:18
  SPEAKER_00: On October 19th and 20th, 2025, AWS US East One had a regional disruption involving Dynamo DB DNS failures, EC2 launch issues, and network load balancer impacts.
• 3:32
  SPEAKER_00: There's no public evidence that specific BMS platforms went dark, but any building system depending heavily on one cloud region faces the same question.
• 3:41
  SPEAKER_00: What works locally and what disappears when the cloud layer is unavailable?
• 3:46
  SPEAKER_00: In some cloud-first architectures, supervisory functions like schedules, alarms, set point workflows, and graphics may depend on the cloud.
• 3:55
  SPEAKER_00: That doesn't mean the plant stops running, but it can mean the operator loses visibility or control right when they need it.
• 4:04
  SPEAKER_00: So what does this mean on Monday morning?
• 4:06
  SPEAKER_00: Three things.
• 4:06
  SPEAKER_00: First, before signing or renewing a cloud BMS contract, get three clauses in writing.
• 4:13
  SPEAKER_00: A data export clause that specifies format, frequency, and confirms historical trend values are included, not just metadata, a termination assistance clause with a defined transition period, 90 days minimum, 180 is better, and a survival of control clause that says the building keeps operating safely if the cloud connection drops.
• 4:36
  SPEAKER_00: Second, make open semantic modeling a procurement requirement.
• 4:41
  SPEAKER_00: If a vendor can't tell you whether their data model maps to Haystack, BRIC, or the proposed ASHRAY 223 standard, that's a yellow flag.
• 4:51
  SPEAKER_00: C4SB brought key technical projects under the Linux Foundation in 2025, giving open building data and interoperability work a neutral home.
• 5:02
  SPEAKER_00: Use that as leverage.
• 5:03
  SPEAKER_00: Third, audit what's running in the cloud versus at the edge.
• 5:07
  SPEAKER_00: Walk into the mechanical room and ask: if the internet went out tomorrow morning, what would still work?
• 5:13
  SPEAKER_00: Schedules, alarms, set point changes from a wall stat?
• 5:17
  SPEAKER_00: Critical sequences should live on the edge controller.
• 5:20
  SPEAKER_00: Full stop.
• 5:21
  SPEAKER_00: The cloud is allowed to optimize the building.
• 5:24
  SPEAKER_00: It is not allowed to own the building's safe state.
• 5:27
  SPEAKER_00: Bottom line, the best time to write the cloud BMS exit plan was before signing.
• 5:33
  SPEAKER_00: The second best time is at the next renewal.
• 5:36
  SPEAKER_00: Because the contract running the building today may still shape how that building operates five years from now.
• 5:42
  SPEAKER_00: And ten years from now, the boring questions are the ones you'll wish had been asked.
• 5:47
  SPEAKER_00: Cloud is the future.
• 5:48
  SPEAKER_00: Lock-in doesn't have to be.