Blog
Related Posts
Niagara AX to N4 Migration Guide
At the heart of what we do is a commitment to delivering exceptional HVAC solutions backed by quality HVAC parts and professional exper...
One thought on “Why Do We Need Haystack?”
Leave a Reply
You must be logged in to post a comment.
Instead of every project being configured with data references that are different for each sub-system and building, adoption of the Haystack standard for automation systems will enable buildings to share data in a uniform way. The principle benefit is that application software can automatically digest the data required to manage or analyse without requiring time consuming data integration for each project. The recently announced version 4.0 of the Haystack standard, now includes additional data modelling features, so that it provides an even more comprehensive solution for the needs of those designing and operating smart buildings.
Additionally, as Haystack is not just a set of tag definitions but also a protocol, the process of integrating multiple systems can be simplified since the Haystack protocol is “richer” than BACnet standard. The ASHRAE organisation, who manage the BACnet standard, recognizes the value of tagging, and is currently engaged in formal discussions with Project Haystack to explore how Haystack definitions can be included in future versions of the BACnet standard.