Hi @lejla.s,
Thank you for your response.
I saw your LinkedIn post sharing that announcement a few weeks ago.
My concern is that I am a BIM coordinator at a project and construction company, and I need to build a data workflow from design to the construction site.
In general, the process consists of having a federated model in Revit, from which I export to Navisworks and Data Exchange. With the clash report, I use Power BI to dynamically visualize the results through Data Exchange. However, at the moment, Data Exchange does not have any parameter indicating which model the objects belong to (there is a workaround shared here in the forum, but it is far from practical). Without this information being directly available, there is always a risk that the association is incorrect.
Another limitation in defining this workflow is that, since I cannot export the federated model from Navisworks 2024, I have to do it from Revit. This means that when the clashes reach an acceptable resolution, I have to export the federated model from Revit, running the risk of exporting changes that were not verified during the clash analysis. There are other ways to avoid this situation, but they require additional iterations and make the process more prone to human error...
This is precisely why I urgently need Data Exchange to be available, at the very least, for Navisworks 2024. Please don’t take this the wrong way, but we are talking about a two-version delay in Navisworks. What has changed between the 2023 and 2024 versions to justify such a delay?
If this situation is not resolved very soon, I will be forced to consider solutions outside Autodesk...
I appreciate your attention.
