What an independent MSI's point database looks like to an LLM in 2026
By Yves Habchy · June 2026
What: Vendor BMS platforms are shipping generative-AI layers into their own stacks. Independent MSIs running mixed-vendor portfolios have the point databases but no clean way to get them into semantic-tagged form for whatever LLM agent a client wants to run.
Why: An MSI running Alerton, Distech, JCI, and Honeywell in one client portfolio can't run OpenBlue across it because OpenBlue is a JCI-stack thing. Honeywell Forge agents work best on Honeywell-stack portfolios. Siemens Building X markets "open," but the semantic-enrichment layer sits inside the Xcelerator partner program.
Niagara 5's native AI isn't shipping until Q4 2026. Clients are asking about AI now. The MSI tier is inheriting the alignment work in the meantime, with no cross-vendor layer to hand a client's agent.
Where: Building automation, mid-2026. Vendor stacks (JCI OpenBlue, Honeywell Forge, Siemens Building X, Tridium Niagara 5) are moving to embedded AI. ASHRAE 223P is consolidating Haystack-Brick fragmentation into a BACnet-compatible standard.
MCP has become the de facto pattern for exposing tools to LLM agents. AWS shipped an IoT SiteWise MCP server September 2025, GA'd broader coverage May 2026. A solo developer maintains a FastMCP-based BACnet MCP at v0.3.7. Building automation's AI story is being written; the MSI tier hasn't been given a tool yet.
Who: Independent MSI shops running mixed-vendor portfolios across 5-50 buildings, mostly small-commercial and mid-market. These are the shops whose clients want AI outcomes but don't have a single-vendor stack to hand to a native platform. Semantic mapping between BACnet point databases and whatever ontology the client picks gets done by hand, usually by the MSI, every time.
What I built
brick-bacnet-mcp is a v0.1 alpha of the gateway. Brick and Haystack aware, 223P as it stabilizes, read-only in v0.1 to keep the write-path liability out.
It drops into Claude Desktop, Cursor, or any MCP host. An LLM agent calling it sees Building 7 → AHU-3 → discharge_air_temp_sensor instead of device 1234 object analog-input 56.
Code at github.com/Yveshby27/brick-bacnet-mcp. Run brick-bacnet-mcp --coverage-report against one of your buildings and it returns the fraction of your point names the starter rule library tags. No adoption needed.
An alpha because the read-only layer is what I can build cheaply and test first. Writes, fault-detection, hosted tiering come next if the read-only layer earns it.
The ask
If you run an independent MSI shop with a five-to-fifty-building portfolio and the semantic mapping between BACnet point databases and the AI workflow a client wants is expensive enough that you've thought about automating it, reach out. I'm not pitching anything; I want to know whether the gap is real from your side. If it isn't, that's what I need to hear. I'd rather find out from one MSI than from six months of building the wrong thing.
Also possible: the gap doesn't exist at this tier, or vendor platforms are closing it faster than my read suggests. If that's the answer, that's the most useful thing I could hear.
My LinkedIn and email are below if you're interested.
Or, if you're not ready to reach out
More detail
Verbatim quotes and sources from the research.
"Brick Schema builds on the concept of tags from Project Haystack and enriches the schema with an underlying ontology that crystallizes the concepts defined by the tags."
Therese Sullivan (BuildingContext, Project Haystack contributing editor), AutomatedBuildings January 2017. Note: 8+ year old citation; ASHRAE 223P has since consolidated much of this work into a BACnet-compatible standard.
Sullivan wrote that in early 2017. The underlying observation still holds: the ontology work has been on the table for the better part of a decade, and it's still not a shipped commodity for a working MSI. 223P is the current attempt to make it one, still stabilizing at time of writing.
"The role of the Master Systems Integrator (MSI) has fundamentally evolved from a project-based implementer to a strategic partner essential for portfolio success."
Kelly Sinclair, "The Evolution of the Master Systems Integrator", AutomatedBuildings, 2025-12-14.
Sinclair's framing matters because the timing of the MSI role-shift and the arrival of client-side AI questions are landing at the same time. MSIs are being asked to be a strategic partner on AI infrastructure that isn't natively available in their multi-vendor client portfolios. The tools to deliver on that ask haven't shipped yet.
LinkedIn DM or yves.habchy@gmail.com.