What is the difference between Project Haystack 3 and Haystack 4?

Haystack 3 provided a tag dictionary and REST API but had no formal ontology — tags were documented in a wiki but not machine-parseable. Haystack 4 introduced "defs," a rigorously specified ontology where every tag has a formal definition, inheritance relationships, and allowed conjuncts. This enables automated reasoning: a Haystack 4 engine can infer that a "chiller" is a type of "equip" without hardcoding that relationship. Haystack 4 also added the Trio and Zinc 2.0 formats and improved support for multi-site, multi-building portfolio management.

Does Project Haystack require a specific BMS vendor or platform?

No. Project Haystack is vendor-neutral and has been implemented by dozens of platforms including SkySpark (SkyFoundry), Niagara Framework (Tridium), Automated Logic WebCTRL, Johnson Controls Metasys, and numerous open-source projects like Haxall. The standard only defines the data model and REST API — the underlying BMS can be from any vendor as long as a Haystack connector or adapter exists. Most major BMS platforms provide native Haystack support or publish Haystack connectors.

How many tags does a typical VAV box point list require?

A typical VAV box in a Haystack model has 8–15 points: zone air temperature sensor, zone air temperature setpoint (occupied, unoccupied, heating, cooling), damper position feedback and command, reheat valve position (if applicable), supply airflow sensor and setpoint (CFM), and occupancy command. Each point receives 4–8 Haystack tags: entity marker (point), measurement type (temp/flow), side (zone/supply), state (sensor/sp/cmd), media (air), and references (siteRef, floorRef, equipRef). The equipment record itself (vav marker) carries additional tags for zone area (m²), design airflow, and space reference.

Can Project Haystack be used for energy metering data, not just HVAC?

Yes. Haystack includes a rich set of tags for electrical metering: elec, meter, ac, dc, kw, kwh, pf (power factor), volt, amp, freq, and phase (phaseA/phaseB/phaseC). Sub-meter data tagged with these conventions integrates seamlessly into Haystack analytics dashboards. Haystack also has tags for other utility meters: gas, water, steam, chilled water, hot water, and fuel oil — all with standardized unit tags (e.g., unit: "gal", unit: "Btu").

What is the typical effort to Haystackify an existing 200,000 sq ft office building?

For a typical 200,000 sq ft office with one primary BMS controlling 3,000–5,000 points, the Haystackification effort ranges from 40 to 120 engineering hours depending on the quality of existing point naming. Buildings with structured naming conventions (e.g., AHU-3-SAT for supply air temperature) auto-tag at 70–85% accuracy; buildings with cryptic legacy names (e.g., "AI_003_27B") may require manual review of every point. The process involves: BMS point export (4h), auto-tagging and review (20–60h), equipment hierarchy modeling (8–20h), validation and testing (8–20h), and analytics rule deployment (8–16h).

Engineering·9 min read·April 1, 2025

🏢 Project Haystack Semantic Tagging for Smart Buildings

Learn how Project Haystack standardizes building data models with semantic tagging, enabling interoperability between BMS, analytics, and IoT platforms across HVAC, lighting, and energy systems.

📖Building Management System Use Case (Full Access)

View →

What Is Project Haystack?

Project Haystack is an open-source initiative that defines semantic data models and tagging conventions for building automation, HVAC, lighting, energy, and IoT equipment. Launched in 2011 and now at version 4, Haystack solves one of the most persistent problems in facilities management: the inability to share and interpret building data across different vendors, platforms, and analytics engines without custom integration work.

Topics covered

Project Haystacksemantic taggingbuilding data modelsHaystack 4BMS interoperabilityHVAC datasmart building ontologyTrio formatZinc formatSkySparkbuilding automationdata normalizationpoint namingequipment tagging