FEDERATION AUTOMATION

Models ready for coordination

A single entry point for shared models

The application started with the Autodesk credentials and permissions each user already had. Through Autodesk Platform Services, it navigated their workspaces, projects, and folders until they could choose the main model. Once selected, it checked the model's version and retrieved references to linked models available for download. The operator no longer needed to rebuild the file list manually before each run. This meant connecting two environments that are often used separately: Autodesk Docs, where models were shared, and Navisworks, installed on the coordinator's computer. I designed the Windows application in C# and .NET, with a WPF interface bringing those operations together in a single workflow.

Downloading is not the same as federating

The first stage retrieved the selected model and its links to a local folder. The program could download several linked files concurrently, with a configured limit of four simultaneous transfers. Another integration then came into play: local Navisworks automation, which opened the RVT files and added the links to the set. The output included an NWF for continued work and an NWD for sharing the prepared federation. It was not an NWC exporter from Revit: the application used Navisworks itself to build the set the team needed to review. That distinction also defined how this application related to the separately developed exporters.

Working with errors rather than hiding them

Not every link could be incorporated without difficulty. Some references could fail because of their condition or the circumstances of access and processing. The workflow therefore logged file names, operations, and incidents, skipped problematic files when appropriate, and continued with the remaining ones. The log helped identify where an interruption had occurred and review the federation before using it for coordination. During its use on an industrial project in Nuevo León, some runs took several hours, depending on the files and the connection. It was useful to start them at the end of the workday and review the results the following morning. The application automated preparation, while the coordinator retained the responsibility for checking whether the required models had actually been assembled. This work also allowed me to propose an enterprise console that could bring together other AEC integrations. That idea did not become additional modules in this application; the workflow from Autodesk Docs to Navisworks was the part that was put to use.