In the last blog post we took a look at IFC5 and explained why the granular approach is so interesting. The vast amounts of data generated by today's BIM processes require new approaches and technologies - because files often represent data silos and make it difficult to access certain content. It does not matter whether it is an open format such as IFC or a proprietary format - to access the data, the entire file must be opened.
However, we don't have to wait for IFC5 to use this approach. Data Exchange is based on a very similar principle, where models are broken down into granular data. This data is stored on Autodesk Docs and is accessible to various tools and services through the API or via the Data Exchange Connectors.
The following Data Exchange Connectors are currently officially available: Revit, Inventor, Tekla Structures, Rhino, Power BI and, since November 13, IFC (on Autodesk Docs).
The Data Exchange Cloud Connector for IFC allows the simple filtering of IFC files according to classes, types, component names or other properties. The filtered subset can then be saved as a Data Exchange on Autodesk Docs. The Data Exchange remains connected to the IFC and is automatically updated as soon as a new version of the IFC file is uploaded - while keeping the originally set filters active.

What possibilities does Data Exchange offer? The workflows can be divided into three main areas:
1. Loading the Data Exchange into another authoring system (e.g. Revit or Tekla Structures)
The advantage of this method over referencing the complete IFC file is that Data Exchange only loads the relevant data. The elements are mapped as DirectShapes or meshes to the corresponding Revit categories and can then be used in schedules or referenced in labels. This means that a wall is recognized by Revit as a wall - though please note that it is currently not possible to edit the elements loaded as Data Exchanges (this is part of the official Roadmap).
Another interesting aspect is that the loaded Data Exchanges are visible in all views and sheets in Revit files published on Autodesk Docs, which offers another advantage over regular links. This workflow is currently being tested in pilot projects at Deutsche Bahn and the Tidhar Group in Israel - you can find out more in our Autodesk University session.

2. Data analysis and visualization in Power BI
In most projects, there are numerous stakeholders whose expertise lies in areas other than BIM - e.g. finance, sustainability, or general project management. Power BI is an easy way to make BIM data accessible to everyone, regardless of their BIM or software knowledge. With the Autodesk Data Connector for Power BI Data Exchanges can be loaded directly into Power BI and even visualized in 3D. The dashboard can then be shared - without the need to give the recipient access to Autodesk Docs or the ACC project. There are also some very interesting use cases for this in our Autodesk University session - e.g. from WSP or V&V Bravo.
In my latest Youtube video I guide you step by step through the entire workflow, starting with the creation of the Data Exchange from an IFC file to the creation of a simple Power BI dashboard.

3. Direct access via the GraphQL API
For everyone who needs even more flexibility and customized access to their data, the Data Exchange GraphQL API Beta offers another way to query specific data from Data Exchanges - and pass the results directly to other systems, such as ACC Connect (Workato), or other platforms. The official Autodesk Data Connector for Power BI Connector is also built on this API - in this Autodesk University session Autodesk developers provide first-hand insights on how this connector was developed.
The Data Exchange Model Explorer is the easiest way to familiarize yourself with the GraphQL API - we will look at this in detail in one of the next blog posts.

What do you think about Data Exchange for IFC - have you already tested it, do you have any questions or would you like a deeper insight or tutorial into one of the workflows? I'm looking forward to your comments!