Eco Park

Background

Eco Park South required a coordinated federated model and a complete asset information set for client handover. The model files spanned two Revit versions and arrived with inconsistent positioning and orientation.

The problem

Two things had to be resolved before handover. Asset codes needed embedding into model files where the underlying BIM data was incomplete, and the federated model needed to actually federate: individual files were not properly positioned or oriented relative to each other.

What I built

KKS asset codes were embedded into Revit and IFC model files using available BIM data, with the associated take-off sheets supported alongside. Across 21 models, more than 6,000 KKS codes were embedded, using the element GUID as the key. Exceptions were documented where GUIDs, ElementIDs, missing Revit files or version mismatches broke the workflow, rather than being silently worked around.

The embedding ran through a reusable Dynamo Player script rather than a one-off for this project. Each run takes an Excel workbook and worksheet, a key column (GUID), a value column (KKS), the Revit parameter holding the matching key (IfcGUID) and the parameter to fill. It matches each row to the elements in the active view, writes the value to every match, and saves a copy of the workbook with _result added to the name. That copy adds two review columns: Read-Only, for destination parameters that could not be written, and Number of Elements Found, where zero means no visible match and more than one means the same code went to several elements. Because the search is limited to the active view, a named processing view was set up for each model before running. The same script can be pointed at other coding systems and projects by changing the inputs.

On the federation side, the routes the client could realistically use to view the models were assessed: Navisworks Freedom, Navisworks Manage, NWD output, Revit host models and Autodesk Construction Cloud. That assessment set the federation approach. Coordination issues in the federated model were then worked through directly, covering remediation, software access and coordinate checks.

Outcome

Issued a final coordinated folder: every model in Revit, IFC and NWC formats alongside the federated Navisworks model, all project-north aligned per the project BIM Execution Plan.