Computational modelling, added mid-project
A script built complex additions from the existing Strand7 model, then sent the geometry to both Strand7 and Revit.
The problem
Computational modelling is usually treated as all or nothing. Either a project starts with it or it does not, and most projects do not. By the time the geometry gets hard, there is already a model in place and a team committed to it. So the complex additions get done by hand, node by node, on a model that is already large. It is slow, it is error-prone, and it has to be repeated: once in the analysis model, and again in Revit for documentation.
What I built
For this client I wrote a script that consumed their existing Strand7 model into Rhino, so new geometry could be built computationally right on top of what was already there. Nothing was rebuilt from scratch; the additions referenced the real model.
From that same source, the geometry went back into Strand7 for analysis and into Revit for documentation. When the design changed, the team regenerated both models from the same source instead of rebuilding the geometry twice.
What makes this work
It builds from the existing model rather than a blank file, and feeds two destinations at once. One pass gets you most of the way there, roughly 70% in Revit and 80 to 90% in the analysis model, and when changes come later you regenerate through the script instead of remodelling by hand. Computational modelling stops being a switch you flip at the start and becomes something you can add at any stage.
What changed
The team got their complex additions into both models from one source, mid-project, without modelling anything twice. When the design moved, the geometry regenerated rather than being rebuilt.
Notes on maintainability
Computational modelling can be added at any project stage, including after the team has committed to an existing model.