I reopen the BIM/Haystack WG because I am dealing with it and want to help towards connecting the worlds of BIM and Project Haystack.

From design to construction and commissioning, the same data and information have been generated over and over again leading to an increased total cost of ownership of each entity. This leads to a manual, labor-intensive process to "map" the data before value creation can begin. Pragmatic use of ontology-based metadata schemas can make it more cost-effective to analyze, visualize, and derive value from our design and operational data.

Bridging common BIM IFC classes with the Haystack convention is the focus of the group to enhance Haystack capability to work with BIM data. This working group would specifically address Project Haystack and the potential to integrate Haystack data modeling with the BIM standard to streamline the handoff of essential facility data from the design/retrofit/construction phase to the operational phase of a building's life.

Now more than ever when companies like Autodesk introduce their digital twin capabilities, I think it's a great time to integrate BIM with Project Haystack!

Some potential areas of overlap with other similar initiatives.

• NREL-PNNL collaboration to develop semantic metadata models (Brick and ASHRAE 223P) from BIMs, which I'm involved in.
• Energy Modeling via the USA affiliate of the International Building Performance Simulation Association (IBPSA-USA) Building Data Exchange (BDE) committee. Justin Schulz from Page is leading the BIM working group. https://bde.ibpsa.us/about/

Hi Matt,

Thanks for sharing. I will have a look. It would be good if ways of collaboration can be identified. Happy to have a chat on that.

I think another potential direct work of this group could be to extend and define better Building Device and Asset Naming Standards Initiative (BDNS) for Project Haystack

https://github.com/theodi/BDNS

In this initiative, people defined Abbreviations for a number of different assets ( https://github.com/theodi/BDNS/blob/master/BDNS_Abbreviations_Register.csv) with ifcClass and ifcType if applicable. I think a great step will be to add Project Haystack tags, defs, taxonomy, and ontology there and expand this great work that people have done as well.

What are the community's thoughts on that?

Hi All,

FYI, I shared with everyone our dedicated repository for capturing information.

The first meeting will take place on the 4th of September. If anyone hasn't received the invitation please let me know.

If anyone else is interested and is not on the list, please create an account in Project Haystack if you haven't one and join the group.

Best Regards, Georgios Grigoriou

I've looked at the IfcClass & Type mappings on the BDNS for a few years now, it's not always the simplest but possible. Your suggestion to start there would make total sense.

Hi all,

I hope you are well.

Just a reminder that today 06/09/2023 at 17:00 UK time we will have our first 1-hour meeting.

I'll try to record the session for those who can't attend

Best Regards,

Georgios Grigoriou

Hi all,

I hope you are well.

Just a reminder that today 15/11/2023 at 17:00 UK time we will have our second 1-hour meeting.

Best Regards,

Georgios Grigoriou

Hi All,

Did this group come to a consensus on bridging the IFC and Haystack standards?

Really interested in this as well. There is open source rendering engine called https://thatopen.com/. They are also building fragments to render large IFC files over 5GB in seconds. I think all the build industry could utilize this.

That being said utilizing XETO and IFC 4x spec might speed up things.

This is the spec that would be related to our domain.

https://github.com/buildingSMART/IFC4.3.x-development/tree/master/docs/schemas/domain/IfcBuildingControlsDomain

It might make sense to contact IFC and Create collaboration with Haystack.

Asked AI on potential roadmap that this is the response from it.

1. Data Extraction Use XETO to extract relevant data from the IFC 4.0 model. Focus on: IfcElement: Building elements like walls, doors, HVAC systems, etc. IfcPropertySet: Property sets containing metadata. IfcRelDefinesByProperties: Relationships between elements and their properties.
2. Define Mapping Rules Create a mapping schema between IFC entities and Haystack tags. For example: IfcSpace → space (Haystack tag) IfcBuildingElementProxy → equip (Haystack tag for generic equipment) IfcPropertySet properties → Haystack point tags (e.g., temperature, pressure).
3. Semantic Alignment Use XETO's ontology alignment features to match IFC's schema to Haystack's tagging system. This involves: Identifying equivalent concepts (e.g., IfcSensor → sensor in Haystack). Adding custom mappings for elements not directly supported by Haystack.

Agree with all of this. Would love to see the industry move towards IFC modeling and away from proprietary revit models.

I've created a demo application built on top of thatopen.com. You can upload and use AI to chat with the IFC model. https://davinci-viewer.vercel.app/ This also leverages ifcopenshell which is great for programmatically interacting with ifc models.

I also lead a digital twin company called Syyclops which is built on top of autodesk revit and the brickschema. We leverage knowledge graphs to correlate information from BIM, BAS, and IOT. Try a demo here: https://app.syyclops.com/setty/dcoffice?guest=true website: https://www.syyclops.com/

Also: https://bonsaibim.org/ is worth checking out. Free and open source IFC modeling software. With the ability to tag equipment with the brickschema baked in.