BIM AUTOMATION
Automating processes in Revit
Identifying the rule before programming it
Automations usually begin with a very specific question: which elements to select, where the data are, what condition must be met, and what change needs to be made. Dynamo made it possible to turn many of those sequences into visual graphs; Python and the Revit API came into play when more specific control was needed. Some tools generated geometry, others updated properties, and others prepared files for analysis. A substantial part of the work focused on information and interoperability: reading Excel or JSON, locating elements, creating or filling parameters, linking codes, and normalizing values. For example, I developed a procedure to back up the Sub-Discipline classification alongside each element's UniqueId in Parquet. When restoring it, the routine could locate the corresponding objects, report matches, and log exceptions before writing changes.
Models can also be built from existing data
Several developments used CAD geometry and annotations to create elements in Revit. Depending on the case, lines, layers, points, or text references were interpreted to build walls, slabs, ceilings, and building services components. Other work focused on massing, façades, repeating modules, and parametric geometry, or on structural elements and reinforcement for columns and foundations. In building services, the rules also covered conduits and fittings, length calculations, and transferring wiring data when enough references existed to link them. In topography, I worked with coordinates, surfaces, slopes, platforms, and georeferenced elements. For quantity takeoffs, the routines prepared lengths, areas, volumes, or weights that could be analyzed in other reports.
From a single command to a reusable procedure
The collection also includes documentation operations: creating sheets from tables, preparing and placing views, applying templates, tagging, dimensioning, and reviewing information. Some solve a specific task; others chain steps together to support an entire activity. They do not all depend on the same packages, parameters, families, or project conventions. I have preserved 165 automations for these purposes. Their value lies in the problem each one addresses and the logic that can be used again, not in presenting them as a single application. When a process comes up again, the work begins by checking its inputs, the conditions of the new model, and which operations still make sense to reuse.