I build automation that turns Revit from a drawing application into a production system where joins behave, views stay consistent, and configurations follow rules instead of tribal knowledge.
|
Experience |
15+ years in construction + façade engineering |
|
Approach |
Lean Six Sigma if it can't be measured and repeated, it doesn't ship |
|
Languages |
🇬🇧 English · 🇳🇱 Nederlands · 🇹🇷 Türkçe · 🇸🇦 العربية |
|
Typical output: production-ready, validated models cleared for detailing handoff. |
Typical output: enforce standards, automate repeatable tasks, cut manual correction cycles. |
|
Typical output: compiled tools with UI validation panels, batch processors, commands teams actually use. |
Typical output: services that move BIM data between Revit, cloud, and external systems. |
|
Typical output: dashboards that surface model health, quantities, and QA metrics. |
Typical output: automated pipelines that validate, notify, and move data without manual chasing. |
|
Typical output: versioned automation with checks so the code is as reliable as the output it produces. |
|
|
Rule-based component logic for walls, floors, roofs, façades. |
Section placement + consistency enforcement. |
|
Constraint-driven panel grids + sub-frames. |
Structured exports for downstream systems. |
The point is not clever automation. The point is boring consistency.
→ Clear rules instead of personal habits
→ Fewer manual edits, fewer surprises in deliverables
→ Downstream teams can trust the model without reverse-engineering intent
→ If it can't be measured and repeated, it doesn't ship
| 🌐 | Deeper APS integrations for cloud-based model data extraction |
| 🧱 | C# add-ins with proper UI for validation workflows |
| 🧪 | CI pipelines for Dynamo graphs (version control + automated testing) |

