A modern building generates an enormous number of data points — tens of thousands of sensors, setpoints, and status values across HVAC, metering, and lighting. The problem is rarely getting the data. The problem is that a point called AHU3_SAT means nothing to anything except the person who named it. Project Haystack exists to fix that, and it is quietly one of the most important ideas in building automation. Here is why it matters.
The Problem: Data Without Meaning
Point names in building systems are historically a free-for-all. One integrator writes SAT, another writes SupplyTemp, a third writes AHU_3_DAT — all meaning the supply-air temperature of the same kind of unit. To a person who knows the building, these are readable. To software — analytics, fault detection, a portfolio dashboard — they are opaque. You cannot ask “show me every air handler’s supply temperature across all my buildings” when every building names it differently. That single limitation blocks most of the valuable things you would want to do with the data.
The Fix: Tags That Describe What Things Are
Project Haystack is an open standard for tagging building data with meaning. Instead of relying on a cryptic name, each point gets tags describing what it actually is — that it is a temperature sensor, that it measures supply air, that it belongs to a particular air handler serving a particular zone. The naming can stay whatever it is; the tags give software a consistent, queryable model of what everything means.
Once data is tagged, it becomes addressable by concept rather than by name. “Every supply-air temperature on every air handler” becomes a query that works across buildings, because the meaning — not the label — is what the software reads.
What Semantic Tagging Unlocks
- Analytics that scale. Fault detection and performance rules can be written once against tagged concepts and applied across a whole portfolio, instead of rebuilt per building.
- Faster onboarding. A new building added to a tagged system inherits existing analytics immediately, because its points describe themselves in the same vocabulary.
- Portfolio views. Cross-building comparison — energy, comfort, equipment health — becomes possible because the data finally speaks a common language.
- A foundation for AI. Any serious attempt to apply machine learning or AI to building data depends on that data being structured and labeled. Tagging is the groundwork that makes it feasible.
Where Niagara Fits
The Niagara Framework works naturally with tagging — points carried in a Niagara system can be tagged and organized so the data model is meaningful, not just a flat list. The value, again, is in doing it consistently and thoroughly: a half-tagged system delivers half the benefit, and inconsistent tagging reintroduces the very problem it was meant to solve. Done properly, tagging turns a pile of points into a structured asset you can actually build on.
The Bottom Line
Collecting building data is easy; making it useful is a data-modeling problem, and semantic tagging is the answer. If you have ambitions for analytics, portfolio-wide insight, or AI on your building data, structured tagging is not optional — it is the foundation everything else stands on.
SoftwarePile builds Niagara systems with data structure in mind — tagged, organized, and ready for the analytics you will want next. Tell us what you want to do with your building data and we will help you build the model to support it.