We built the BIM. Owners are still asking: why don’t my assets know what they are, where they are, or what they mean?
We’ve spent decades building up data about our buildings.
Models. Systems. Sensors. Dashboards.
And now we’re starting to talk about something new:
Asset Intelligence.
Not more data, but understanding.
The ability to ask a building a question,
“Why is this room too hot?”
and get a real answer.
What follows is a simple way to see the problem, and what’s starting to change.
The Illusion of Progress
We’ve made progress.
We can connect systems with APIs.
We can stream real-time data.
But connecting data is not the same as understanding it.
APIs don’t create meaning.
Dashboards don’t explain relationships.
We didn’t need more data.
We needed shared meaning.
Where Meaning Has Been Hiding
There’s another layer to this.
Building automation and control systems have always contained meaning.
They know how systems operate.
They know relationships, sequences, and dependencies.
But that meaning has largely been encoded,
in system-specific logic, naming conventions, and structures that don’t translate easily beyond their boundaries.
Not because the technology couldn’t do it.
But systems were never designed to share meaning beyond themselves.
They were designed to operate independently.
The result is that each system understands its own world,
but not the building as a whole.
Making It Visible
To make this clearer, we laid it out.
The same room becomes many different things depending on who is looking:
One Building. Many Perspectives.
Everyone interacts with a building differently. The occupant feels comfort. The architect defines space. The engineer designs systems. The operator sees alarms. The landlord sees lease rates and ROI. The building reports conditions through sensors. Humans and AI agents are now starting to ask questions of it.
They are all describing the same reality — but in different ways. Somewhere in between, meaning gets lost.
What each perspective sees
| Persona / System | What They Care About | How They Describe It | Example |
|---|---|---|---|
| Occupant | Comfort, safety, utility | Experience | “This room is too hot.” |
| Tenant | Usable space, services, occupancy dates | Suite, term, move-in, service expectations | Suite 210, occupied through 2028 |
| Landlord / Asset Manager | Lease rate per SF, dates, total cost, ROI | Revenue, vacancy, operating cost, portfolio metrics | $4.25/SF, lease expiring Q3, energy cost impacting margin |
| Architect | Space, size, intent, capability | Rooms, areas, function | Classroom 101, 900 SF |
| Owner | Performance, cost, outcomes | Portfolio, service levels | 72°F at 9am, every day |
| MEP Engineer | Systems, loads, flows | Equipment + relationships | AHU-3 serves Zone A |
| Controls System | Signals, setpoints, sequences | Points + values | Temp = 78°F, setpoint = 72°F |
| Operator | Maintenance, faults, uptime | Alarms + work orders | “AHU-3 fault” |
| Emergency Responder | Life safety, access, conditions | Risk + location | Smoke in Zone A, shutoff here |
| Utility | Energy usage, load, timing | Consumption patterns | Peak demand at 2pm |
| Sensors / Building Systems | Real-time state | Measurements + events | Temperature, airflow, faults |
| Technologist / Data Architect | Data structure, interoperability | Schemas, APIs, IDs | RDF, JSON, tags, URIs |
| Humans + AI Agents | Questions, diagnosis, action | Queries + reasoning | “Why is Room 101 hot?” |
What meaning means
Meaning is what connects these views.
It’s not just having data about a room, a system, or a sensor—
it’s knowing how they relate.
That this room is served by this system,
observed by these sensors,
and connected to everything around it.
Not as separate files.
Not as disconnected systems.
But as one connected understanding.
And that all of it can be understood together, without translation.
Not as separate files.
Not as disconnected systems.
As one connected understanding.
What Changed
In the PAE Living Building, the data was always there.
Solar. Batteries. HVAC. Sensors. Controls.
Everything was operating.
But no one could see how it worked together until it was connected.
Once connected, simple issues became obvious, like as a battery charging at the wrong time, creating unnecessary peak-demand costs.
Not a design problem.
Not a hardware problem.
A meaning problem.
One Quick Reality Check
You can have detailed BIM, advanced control systems, and sophisticated dashboards,
and still not understand your building.
Not because the data is missing,
but because the relationships between systems are not connected and not all systems are geometry based, there are business rules that need connections.
Visibility is not the same as understanding.
The Semantic Bridge
For the first time, we showed something we’ve been working toward for years:
A Semantic Bridge.
A way to finally connect what already exists.
It links the physical world of buildings, spaces, assets, and location,
with the semantic world of systems, relationships, rules, and dependencies.
Select a room, and you see the systems behind it.
Select a system, and you see what it actually serves.
And when you ask a question, the answer isn’t guessed.
It’s grounded.
Here’s a short look at the Semantic Bridge in action:
Why This Matters Now
AI doesn’t need more data.
It needs structured meaning.
Without meaning, AI guesses.
With meaning, AI can reason.
You can now ask:
- Why did this peak occur?
- Which systems are interacting?
- What changed?
And get answers grounded in both:
- live data
- and actual system relationships
That’s the difference between querying data,
and understanding a building.
Presentation at the Asset Leadership Network Webinar
With:
Tristan de Frondeville, CEO of SkyCentrics, presenting the SkyCentrics Super SkyBox
Daniel Colwell, Operations Manager at SkyCentrics, presents the Dream Platform and uses AI to converse with the energy systems in the PAE building. Pretty amazing!
Kimon Onuma, President of ONUMA, Inc., presenting the Semantic Bridge App
Michael Bordenaro, Executive Director of the Asset Leadership Network
The Role of Owners
None of this happens unless owners require it.
For decades, we’ve asked for deliverables:
- Drawings
- PDFs
- Disconnected models
What we should be asking for is:
- Persistent IDs
- Connected relationships
- Data that survives handover
The data already exists.
It’s just not being required in a usable way.
Until it is required, it will continue to be lost.
From Platform Wars to Platform Peace
This is about connecting platforms.
Bring your BIM.
Bring your digital twins.
Bring your building systems.
Bring your data.
If it connects, it belongs.
Closing
The occupant feels the outcome.
The building reports the condition.
Humans and AI try to respond.
But everyone has been working from fragments.
That’s starting to change.
And once buildings can be understood, we can finally improve them.
Credits
Videos:
Semantic Bridge Introduction: ONUMA Inc.
Knowledge Graph Animation: Unsplash
Asset Leadership Network: Thursday at 3 PM Webinar
Chalkboard Images: AI Generated, Human Prompt
