Setting the Scene
Most structural engineers don’t lose time on engineering. They lose it on translation: moving geometry, data, and decisions between Rhino, analysis software and Revit by hand, again and again.
That was the thread running through Turn Rhino.Inside.Revit into a Real Automation Tool for Structural Engineers, a 90-minute workshop hosted by Learn Grasshopper on 30 September 2026. Learn Grasshopper is one of the widely followed learning platforms in the AEC computational design community, and the session brought together hundreds of engineers, BIM specialists and computational designers from different parts of the World.
As a Computational Design Engineer at Zutari, working across structural engineering, BIM and automation in the Middle East, I was invited to share how we use Rhino.Inside.Revit on live projects. Not as a demo tool, but as part of everyday structural delivery.
From Manual Translation to Connected Workflows
The traditional structural workflow is a chain of handoffs. Architectural geometry arrives. The engineer rebuilds it in ETABS or SAP2000. Someone remodels it in Revit. Documentation is set up by hand. When the design changes, and it always does, the chain runs again.
Every handoff is a rework. Every rework is a chance for the analysis model, the BIM model and the drawings to quietly drift apart.
Rhino.Inside.Revit changes the starting point. It runs Rhino and Grasshopper inside the Revit session, so that Grasshopper can read and write native Revit elements directly, no exports, no intermediate files, no rebuilding. The question shifts from how do we model this faster? to how do we make the model update itself?
The distinction I drew in the session was simple: a script solves a task once; a workflow solves it every time the design changes.
What We Showed: Automation on Real Projects
The session walked through ten workflows from our structural projects. They fall into five themes:
|
Theme |
Workflows shown |
Manual task it replaces |
|
Geometry to BIM |
Wireframes to native Revit families |
Hand-modelling complex freeform elements |
|
Geometry to analysis |
Wireframes to SAP2000 elements; as-built Revit models to ETABS/SAP2000 |
Rebuilding analysis models from drawings |
|
Staying in sync |
Crown slope frame realignment with architectural updates Lighting alignment tracking, architectural, and electrical models Connection between shear values pushed from Excel into Revit |
Re-checking and re-placing elements after every revision |
|
Coordination and QA |
Point clouds and setting-out coordinates visualised as ID spheres Road alignments swept for clearance checks |
Visual checks and manual clash triage |
|
Documentation |
Bulk tagging and alignment TIDP automation, with GPT proposing sheet names and numbers, and Grasshopper building the project browser and parameters |
Days of sheet setup and tagging |
None of these is exotic. They are the repetitive tasks every structural team does every week. That is exactly why they are worth automating.
The Engineer Still Owns the Decision
Automation doesn’t remove engineering judgement. It concentrates it.
A script that places 2,000 beams will place 2,000 wrong beams if the rule behind it is wrong. The engineer still defines the rules: member orientation, end releases, load paths, acceptable tolerances, and what constitutes valid geometry.
Validation stays human, too. Every workflow we showed has a built-in visual QA check in Rhino, with ID’d elements traced back to source data, and analysis results compared against hand checks. The same applies to AI. In our TIDP workflow, GPT proposes sheet names; the BIM lead approves them in accordance with the BIM Execution Plan.
The model can be automated. The accountability cannot.
Lessons from Practice
What surprised us most is where the value sits. Complex freeform geometry gets the attention, but the biggest time savings come from unglamorous work: tagging, keeping sheet setup, and keeping parameters in sync.
What proved harder than expected was the data, not the code. Inconsistent family naming, missing parameters and ad hoc model standards break automation faster than any bug. Automation exposes every gap in your BIM standards. Fixing those gaps is half the work.
Where hesitation remains is trust and ownership. Who maintains a script when its author moves on? What happens when Revit or Rhino.Inside updates? A tool nobody understands is a liability. The answer is to treat automation like engineering: documented, version-controlled, and packaged as reusable components with clear inputs and outputs.
The Structural Engineer of the Future
Structural engineers don’t need to become software developers. But the skills that defined a strong engineer a decade ago are no longer enough on their own.
Computational literacy. Enough Grasshopper logic, data structures, and C# or Python to read a workflow, question it, and adapt it.
Thinking in data, not drawings. A structural model is now a data pipeline: geometry, properties, loads and documentation flowing between tools. Engineers who understand that flow can design it.
Standards discipline. Clean, consistent models are what make automation possible. This is now an engineering responsibility.
Explaining automated outputs. Project managers and clients need to trust the results that the workflow produces. Being able to explain how it works and where it stops is a core skill.
In short, engineering the workflow is as important as engineering the structure.
Looking Ahead
The next shift is from individual scripts to shared, maintained toolkits. Workflows that live in a team library, not on one engineer’s laptop.
AI will accelerate this. Language models are already helping with naming, data cleanup and script writing. The next step is AI agents that can drive Rhino, Grasshopper and Revit directly, with engineers setting the rules and checking the results.
The end goal is a connected model: an architectural change that flows through to analysis, BIM and documentation in hours, not weeks, with the engineer reviewing every step that matters.
At Zutari, this is how we approach digital and information management on buildings and infrastructure projects across the Middle East and Africa: connecting engineering and digital delivery so our teams spend less time translating and more time engineering.
Automation doesn’t replace the structural engineer. It gives them back the time to engineer.
