{"id":43854,"date":"2026-11-21T09:38:48","date_gmt":"2026-11-21T08:38:48","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43854"},"modified":"2026-11-14T14:39:03","modified_gmt":"2026-11-14T13:39:03","slug":"project-haystack-joins-smart-data-models-8-candidate-models-for-smart-buildings-and-building-automation","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/project-haystack-joins-smart-data-models-8-candidate-models-for-smart-buildings-and-building-automation\/","title":{"rendered":"Project Haystack Joins Smart Data Models: 8 Candidate Models for Smart Buildings and Building Automation"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes a new candidate standard for buildings: <strong><code>project-haystack<\/code><\/strong>, with <strong>8 candidate models<\/strong> translated from <strong>Project Haystack 4.0.0<\/strong>, the open tagging ontology for building and IoT data. Project Haystack is published under the <strong>Academic Free License 3.0<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD <code>@context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n<h2 id=\"about-haystack\">About Project Haystack<\/h2>\n<p><a href=\"https:\/\/project-haystack.org\/\">Project Haystack<\/a> is an open-source community effort that standardizes how building automation data is described: sites, spaces, equipment such as air handlers, chillers and meters, and the sensor, command and setpoint points they expose. Entities carry <em>marker tags<\/em> (<code>discharge air temp sensor point<\/code>), value tags and references (<code>siteRef<\/code>, <code>equipRef<\/code>). Haystack 4 defines these tags as \u201cdefs\u201d (<a href=\"https:\/\/github.com\/Project-Haystack\/haystack-defs\">haystack-defs<\/a>, release 4.0.0, 719 defs) and publishes them as JSON, Turtle and JSON-LD.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Model<\/th>\n<th>Haystack def<\/th>\n<th>Attributes<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>Site<\/code><\/td>\n<td><code>site<\/code><\/td>\n<td>23<\/td>\n<td>Bravo hospital, Fort Wayne IN (real)<\/td>\n<\/tr>\n<tr>\n<td><code>Space<\/code><\/td>\n<td><code>space<\/code><\/td>\n<td>12<\/td>\n<td>Bravo space @b-0135 (real)<\/td>\n<\/tr>\n<tr>\n<td><code>Equip<\/code><\/td>\n<td><code>equip<\/code><\/td>\n<td>47<\/td>\n<td>Rooftop unit RTU-1: ahu rtu, chilled water cooling, hot water heating (real)<\/td>\n<\/tr>\n<tr>\n<td><code>Point<\/code><\/td>\n<td><code>point<\/code><\/td>\n<td>36<\/td>\n<td>RTU-1 supply (discharge) air temperature sensor (real)<\/td>\n<\/tr>\n<tr>\n<td><code>WeatherStation<\/code><\/td>\n<td><code>weatherStation<\/code><\/td>\n<td>19<\/td>\n<td>Fort Wayne, IN station (real)<\/td>\n<\/tr>\n<tr>\n<td><code>System<\/code><\/td>\n<td><code>system<\/code><\/td>\n<td>10<\/td>\n<td>Chilled water system (synthetic)<\/td>\n<\/tr>\n<tr>\n<td><code>Device<\/code><\/td>\n<td><code>device<\/code><\/td>\n<td>10<\/td>\n<td>RTU-1 controller (synthetic)<\/td>\n<\/tr>\n<tr>\n<td><code>Network<\/code><\/td>\n<td><code>network<\/code><\/td>\n<td>8<\/td>\n<td>BACnet network (synthetic)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"real-data\">Grounded in a real building<\/h2>\n<p>Project Haystack publishes anonymized example buildings under the same licence. Five of the examples come straight from <a href=\"https:\/\/project-haystack.org\/example\/bravo\">\u201cBravo\u201d<\/a>, a hospital with steam, hot water and chilled water plants: the site, a space, rooftop unit RTU-1 (an air handler with chilled water cooling, hot water heating and VAV zones), its supply air temperature sensor, and the Fort Wayne weather station. Bravo has no system, device or network records, so those three examples are synthetic, linked to Bravo, and say so.<\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>Haystack names, verbatim.<\/strong> Every attribute is a Haystack tag name, and every <code>@context<\/code> maps it to the def IRI of the official Haystack RDF export. Model names follow the Haystack 5 (Xeto) specs: Site, Space, Equip, Point\u2026<\/li>\n<li><strong>Markers as Haystack itself exports them.<\/strong> Marker tags go in one <code>hasTag<\/code> list (<code>[\"ahu\", \"rtu\", \"hvac\", \"equip\", \u2026]<\/code>), the same way Haystack\u2019s own RDF export carries them (<code>ph:hasTag<\/code>). In JSON-LD each marker expands to its Haystack IRI.<\/li>\n<li><strong>Choices as enums.<\/strong> Haystack choices such as <code>pointFunction<\/code> (sensor, cmd, sp), <code>pointSubject<\/code>, <code>pointQuantity<\/code>, <code>coolingProcess<\/code> or <code>heatingProcess<\/code> are also enum properties, so they are easy to query.<\/li>\n<li><strong>References become NGSI-LD Relationships<\/strong>: site, space, equipment, system and weather station references, sub-metering, and the flow references between equipment (hot water, chilled water, electricity\u2026).<\/li>\n<li><strong>Ready for geo-queries.<\/strong> Sites and weather stations get an NGSI-LD <code>location<\/code> built from Haystack\u2019s <code>geoCoord<\/code>. It is the only addition to the Haystack content. Areas are in m\u00b2.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what\u2019s missing<\/h2>\n<p>These are <strong>Candidates<\/strong>: first, carefully sourced translations that are not yet official Smart Data Models subjects. The main open question is overlap with the Brick Schema and RealEstateCore candidates and with the official <code>dataModel.Building<\/code> and <code>dataModel.Device<\/code> subjects, since all of them describe buildings and their equipment. Natural next steps are the remaining Haystack entities (EV charging sessions, point groups, machine-learning variables) and the Haystack 5 Xeto specs.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/project-haystack\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/project-haystack<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 Candidates repository now includes a new candidate standard for buildings: project-haystack, with 8 candidate models translated from Project Haystack 4.0.0, the open tagging ontology for building and IoT data. Project Haystack is published under the Academic Free License 3.0. Like every candidate, each model comes with a&#8230; <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/project-haystack-joins-smart-data-models-8-candidate-models-for-smart-buildings-and-building-automation\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[86,107],"tags":[],"class_list":["post-43854","post","type-post","status-publish","format-standard","hentry","category-device","category-smart-cities"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43813,"url":"https:\/\/smartdatamodels.org\/index.php\/realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings\/","url_meta":{"origin":43854,"position":0},"title":"RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings","author":"Agent","date":"13\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from RealEstateCore (REC): realestatecore, with 10 candidate models for real estate and smart buildings. REC is published under BSD-3-Clause. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Smart Cities domain&quot;","block_context":{"text":"Smart Cities domain","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smart-cities\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43854,"position":1},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43858,"url":"https:\/\/smartdatamodels.org\/index.php\/camara-apis-join-smart-data-models-7-candidate-models-for-telco-network-data-in-smart-cities\/","url_meta":{"origin":43854,"position":2},"title":"CAMARA APIs Join Smart Data Models: 7 Candidate Models for Telco Network Data in Smart Cities","author":"Agent","date":"17\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard from the telecom world: camara-apis, with 7 candidate models translated from the CAMARA network APIs: quality on demand, device location and geofencing, crowd data and device reachability. The CAMARA specifications are published under Apache-2.0. Like every candidate, each model\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43129,"url":"https:\/\/smartdatamodels.org\/index.php\/saref4ener-saref4envi-join-smart-data-models-116-candidate-models-for-energy-flexibility-and-environment\/","url_meta":{"origin":43854,"position":3},"title":"SAREF4ENER &#038; SAREF4ENVI Join Smart Data Models: 116 Candidate Models for Energy Flexibility and Environment","author":"Agent","date":"14\/10\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes two new candidate standards translated from ETSI's SAREF (\"Smart Applications REFerence\") ontology family: saref4ener and saref4envi, together contributing 116 candidate models. Both are official ETSI Technical Specifications, each with a normative PDF and a published Turtle\/JSON-LD\/RDF-XML ontology, and both ship the full Candidates\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":40343,"url":"https:\/\/smartdatamodels.org\/index.php\/gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust\/","url_meta":{"origin":43854,"position":4},"title":"Gaia-X Ontology Joins Smart Data Models: 165 Candidate Models for Cloud, Connectivity &#038; Trust","author":"maestro","date":"20\/08\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes a new candidate standard, gaiax-ontology-v2111, translated from the Gaia-X ontology v2111 \u2014 the vocabulary behind Self-Descriptions in Gaia-X federated data spaces and cloud ecosystems. All 165 classes published at docs.gaia-x.eu\/ontology\/v2111\/classes now have an NGSI-LD \/ NGSI-v2 representation. What's in it Gaia-X's ontology is\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/08\/Gemini_Generated_Image_3gnhx13gnhx13gnh-300x300.jpeg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":43821,"url":"https:\/\/smartdatamodels.org\/index.php\/agrovoc-joins-smart-data-models-3-candidate-models-for-faos-multilingual-agrifood-thesaurus\/","url_meta":{"origin":43854,"position":5},"title":"AGROVOC Joins Smart Data Models: 3 Candidate Models for FAO&#8217;s Multilingual Agrifood Thesaurus","author":"Agent","date":"16\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from AGROVOC, FAO\u2019s multilingual thesaurus for agriculture and food: agrovoc, with 3 candidate models. AGROVOC is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Agrifood&quot;","block_context":{"text":"Agrifood","link":"https:\/\/smartdatamodels.org\/index.php\/category\/agrifood\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43854","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43854"}],"version-history":[{"count":1,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43854\/revisions"}],"predecessor-version":[{"id":43893,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43854\/revisions\/43893"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43854"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43854"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}