Project Haystack standardizes semantic data models and web services with the goal of making it easier to unlock value from the vast quantity of data being generated by the smart devices that permeate our homes, buildings, factories, and cities. Applications include automation, control, energy, HVAC, lighting, and other environmental systems.
Project Haystack encompasses the entire value chain of building systems and related intelligent devices. Owners and consultants can specify that Haystack conventions are used in their building automation systems to ensure cost effective analytics and management of their buildings for years to come.
System integrators and manufacturers who integrate Haystack support into their projects and products are better positioned for the future of providing value-added services.
Project Haystack is a 501C tax-exempt non-stock corporation formed May 28, 2014 under the provisions of Chapter 10 of Title 13.1 of the Code of Virginia of 1950. All work developed by the project-haystack.org community is provided for use as open source software.
Dartmouth College pushes BACnet firmware and device data from Matasys to Planon so IT and ops teams can budget and plan upgrades.
CannonDesign watched a BAS access quote climb from $66K to $100K, then brought in an MSI to review the architecture and cut it to $29K.
Northern Arizona University’s CIO realized that aggregating IoT data wasn’t the hard part; relational context was. After choosing buy over build, the team moved from raw BACnet feeds to ontology-driven HVAC control, achieving 30% energy savings.
At LAX, environmental reporting once meant field visits, clipboards, and emailed meter photos. The airport is now connecting 1.2M+ data points and normalizing what already exists to improve compliance and create new sustainability opportunities.
Lincoln Property Company’s Chris Lelle realized that burdened engineers can’t each manage 300,000 sq ft by diving deep into BAS data—so he used FDD to simplify the troubleshooting his techs need to do.
CannonDesign added smart building scope to their office after bids were in, and Div 23/26 partners didn’t understand what “IDL” meant to their scope. They had to redraw Division 25 boundaries and clarify responsibilities to prevent the job from slipping.
Head over to Nexus Connect and see what’s new in the community. Don’t forget to check out the latest member-only events.
Go to Nexus ConnectJoin Nexus Pro and get full access including invite-only member gatherings, access to the community chatroom Nexus Connect, networking opportunities, and deep dive essays.
Sign Up
Nexus Labs exists to move the smart buildings industry forward, without the fluff.
On Wednesday, we send out the renowned (and free) Nexus Newsletter.
