














Create a data exchange from a federated Revit model, and then manage the exchange in Power BI.
Transcript
00:03
In construction and architectural project management,
00:07
it is standard practice to create models that include multiple linked Revit models.
00:12
These can cover various aspects, such as architecture, furniture, and MEP (Mechanical, Electrical, and Plumbing).
00:21
In some cases, entire buildings are each contained in separate Revit files and linked into a unified file,
00:28
often referred to as a federated model.
00:31
You can create Data Exchanges from federated models that include the contents of the linked Revit files.
00:38
Begin in Revit with an open federated model that links to the original Revit models,
00:43
and with the Revit Data Exchange Connector open.
00:46
In this case, one model contains only architecture-related elements,
00:51
the second model includes mechanical, electrical, and plumbing elements,
00:56
and the third model contains furniture items.
00:59
All three models are linked into this Revit file.
01:03
It is recommended to create a custom project parameter within each linked model.
01:08
This parameter will help to identify and distinguish the elements in subsequent workflows.
01:14
For example, in the linked Revit file, set a Revit Linked Model custom property to MEP for all relevant elements,
01:22
and similarly, create custom properties for architecture and furniture.
01:28
In this case, a Data Exchange is already created using the Revit connector.
01:34
From Autodesk Docs, in the Model Browser, you can filter for different categories using the project parameters,
01:41
such as architecture, MEP, and furniture-related items.
01:47
Expand one of the nodes to work on individual items independently.
01:52
Open the properties for one of the items to review both built-in and custom properties from the linked Revit model.
01:59
Here, you see the Revit Linked Model custom property created previously.
02:04
Once a Data Exchange is loaded into Power BI, you can build a detailed dashboard.
02:10
Using the custom properties, you can filter elements related to linked models by selecting the relevant checkbox, such as MEP.
02:20
Be aware that because an element can be represented by both itself and the RVT link,
02:26
there could be discrepancies in color assignment.
02:29
To mitigate this, from the ribbon, Home tab, Queries panel, select Transform data.
02:37
In the Power Query window, scroll to the right, and in the Revit Category Type Id column click Filter.
02:45
In the drop-down, deselect RVT Links, then click OK.
02:50
This will ensure smooth cross-highlighting and coloring of parts.
02:54
Here, you see the adjusted view in the Autodesk data viewer,
02:58
with elements colored by family and the slicer and charts working seamlessly.
03:03
Using Data Exchanges to view federated Revit models in Autodesk Docs and Power BI allows for end-to-end workflow creation.
00:03
In construction and architectural project management,
00:07
it is standard practice to create models that include multiple linked Revit models.
00:12
These can cover various aspects, such as architecture, furniture, and MEP (Mechanical, Electrical, and Plumbing).
00:21
In some cases, entire buildings are each contained in separate Revit files and linked into a unified file,
00:28
often referred to as a federated model.
00:31
You can create Data Exchanges from federated models that include the contents of the linked Revit files.
00:38
Begin in Revit with an open federated model that links to the original Revit models,
00:43
and with the Revit Data Exchange Connector open.
00:46
In this case, one model contains only architecture-related elements,
00:51
the second model includes mechanical, electrical, and plumbing elements,
00:56
and the third model contains furniture items.
00:59
All three models are linked into this Revit file.
01:03
It is recommended to create a custom project parameter within each linked model.
01:08
This parameter will help to identify and distinguish the elements in subsequent workflows.
01:14
For example, in the linked Revit file, set a Revit Linked Model custom property to MEP for all relevant elements,
01:22
and similarly, create custom properties for architecture and furniture.
01:28
In this case, a Data Exchange is already created using the Revit connector.
01:34
From Autodesk Docs, in the Model Browser, you can filter for different categories using the project parameters,
01:41
such as architecture, MEP, and furniture-related items.
01:47
Expand one of the nodes to work on individual items independently.
01:52
Open the properties for one of the items to review both built-in and custom properties from the linked Revit model.
01:59
Here, you see the Revit Linked Model custom property created previously.
02:04
Once a Data Exchange is loaded into Power BI, you can build a detailed dashboard.
02:10
Using the custom properties, you can filter elements related to linked models by selecting the relevant checkbox, such as MEP.
02:20
Be aware that because an element can be represented by both itself and the RVT link,
02:26
there could be discrepancies in color assignment.
02:29
To mitigate this, from the ribbon, Home tab, Queries panel, select Transform data.
02:37
In the Power Query window, scroll to the right, and in the Revit Category Type Id column click Filter.
02:45
In the drop-down, deselect RVT Links, then click OK.
02:50
This will ensure smooth cross-highlighting and coloring of parts.
02:54
Here, you see the adjusted view in the Autodesk data viewer,
02:58
with elements colored by family and the slicer and charts working seamlessly.
03:03
Using Data Exchanges to view federated Revit models in Autodesk Docs and Power BI allows for end-to-end workflow creation.