MODEL EXCHANGE

Automated exports from Revit

Starting from a federated model

The first tool relied on a convention already in use as part of the BIM implementation: each discipline had to prepare a three-dimensional view whose name ended in _FED. That view defined the content intended for exchange and had to be reviewed by the coordinator before running the batch. Automation used this preparation rather than replacing it. From the federated Revit model, users could select links, choose between NWC and IFC, and specify an output folder. The add-in checked the references of collaborative files, including cloud-hosted models, and opened each selected document within the Revit session without making it the main working window.

Open, export, and close

For each link, the program located the corresponding _FED view, ran the export, and closed the document without saving changes. If a file could not be opened or the expected view was missing, it logged the issue and moved on to the next file whenever possible. In the NWC workflow, each discipline produced an individual file for coordination. The batch did not itself build a single federation in Navisworks. That process followed a different logic from the application that downloaded models from Autodesk Docs to build NWF and NWD files. The technical pattern was reusable: identify related files, open secondary documents, perform an operation, and release them. This led to an interest in exploring other tasks that could be automated across shared models.

Controlling IFC options

The second tool addressed another need. It worked on the open model and offered an interface for choosing an IFC version or retrieving an available export configuration. In addition to carrying out the export, I explored ways to retain configuration data through JSON and storage inside the Revit document. That difference matters because an export is not defined only by the name of the file it produces. The views, options, and criteria used influence the information received by the next team. The tool focused on making those settings recognizable and repeatable within the context of the active model. Both developments concentrated on automating existing exchange procedures. The quality of the views and the review of the resulting files remained BIM coordination decisions.