Rhino–Tekla Bidirectional Workflow — Korean Environment

Grasshopper Tekla
1

My original goal was to create the structural model in Rhino, complete the connections in Tekla Structures, and then bring the completed model back into Rhino.

As a first step, however, I have been testing the transfer from Tekla to Rhino and then sending the transferred model back into an empty Tekla model.

I have not yet been able to test every type of object and modeling situation that Tekla supports. One practical difficulty has been finding suitable Tekla models for testing.

When transferring the model back to Tekla, I spent considerable time considering how to reconstruct the original components. For now, I have decided to omit the component definitions and transfer their resulting physical geometry instead.

The next stage will be to create structural models in Rhino using CAD structural drawings as references and then transfer those models into Tekla Structures.

All of my forum posts are translated into English with the assistance of AI.

2

Here is the second video, showing the transferred Rhino model being sent back into an empty Tekla model.

3

For clarification, this workflow does not use Grasshopper or Rhino.Inside. Rhino and Tekla Structures run as separate standalone applications and communicate directly

4

how about the bolts and assemblies ??
and curved profiles how it handle them ??

5

Thank you for the question.

Bolts: Bolt groups are transferred with their position, bolt standard/name, diameter, length, grip, and nut/washer configuration. When the model is sent back to Tekla, they are recreated as editable native Tekla bolt groups.

Assemblies: Assembly membership and main-part relationships are also transferred. The workflow recreates the assembly structure from the transferred members. However, at the moment, I do not recreate the original parametric connection component definition itself; I transfer the resulting physical members, bolts, welds, and assembly relationships instead.

Curved members: Curved members are handled from their centerline/path and profile data. For supported curved members, the curved path and section are reconstructed in Rhino. When a native reconstruction is not sufficiently reliable, the final verified geometry is preserved as an exact fallback so that the member shape is not lost.

This is still under development, but bolts, assemblies, grids, levels, and curved members are all part of the current workflow.