Work

RFI Railway

Revit and Dynamo workflow developed with LSB for two railway corridors, using changing DWG inputs to produce terrain models, tree placement, technical sheets, and IFC outputs across 33 km and 19 km assignments.

Year
2023–2024
Role
BIM Automation Specialist
Output
Revit Terrain Model + Technical Sheets + IFC Outputs
Railway corridor BIM technical sheet
Railway corridor technical sheet

Stage

Railway drawings across many kilometers.

The Revit and Dynamo workflow turns changing DWG inputs into terrain models, green-area categories, tree placement, technical sheets, and IFC outputs for two LSB railway assignments covering 33 km and 19 km.

Two long corridors

The assignments covered roughly 33 km around Venezia and 19 km in Sicily. At that scale, manual modeling and repeated sheet updates were not practical.

From DWG to Revit

Dynamo routines reloaded changing discipline files, generated terrain floors and topography, placed floors on terrain, and kept the Revit geometry aligned with the source drawings.

Trees and green areas

The workflow placed the correct Revit tree families at the correct points, categorized green intervention areas, and linked planting modules and species to the technical sheets.

A workflow worth reusing

After the first corridor, the method was shared with other team members and adapted more quickly when the second railway assignment arrived.

Backstage

How I made the updates repeatable.

I was not solving one drawing. I was trying to keep changing DWGs, terrain categories, tree placement, and many sheets coordinated across kilometers of railway.

I separated the repeated tasks

I built several Dynamo routines for reading DWGs, forming terrain and topography, placing model elements, assigning tree families, and supporting sheet generation.

I kept the information aligned

Terrain surfaces, green areas, planting modules, species references, route divisions, title blocks, and IFC exports all had to tell the same technical story.

I shared the method

I developed the workflow while collaborating with LSB, then explained it to other team members so it could continue beyond one person and one corridor.

The updates were the real problem

The useful part was not one automated result. It was a rule-based process that could absorb change and regenerate documentation across many kilometers.