STEEL TRACKER
Steel traceability on site
Recognizing a piece across different sources
The first challenge was to ensure that steel pieces retained a recognizable identity as they moved from design to fabrication. Analytical models shared from structural tools arrived as CAD files; using Dynamo and Revit, we developed procedures to interpret lines, layers, directions, and positions, and turn that geometry into structural elements with preconfigured sections. Once a change was validated, we could prepare a new representation and compare it with the previous snapshot. On the fabrication side, IFC models exported from Tekla were used. Although both models described the same structure, they did not always match in their organization or version. That is why the comparison required more than a single identifier. The assembly mark was linked to location, gridlines, erection fronts, and the schedule to understand which steel each record referred to.
Documents tell part of the story too
Shop drawings contained revisions, dates, marks, pieces, and weights that were impractical to transcribe one by one. I contributed to automations that processed AutoCAD files in batches and extracted that information into comparable tables. Keeping successive extractions made it possible to identify changes without losing sight of the documents they came from. The decision was different for delivery records. The contractor provided PDFs and spreadsheets, but the structured Excel log offered a more consistent source for automating supply tracking. We worked with that source rather than relying on recognition of every scanned document. Data from models, drawings, delivery records, and the schedule were then linked in Power BI to build views around the questions arising on site.
Consulting and recording from the same environment
The tool included a workflow for site engineers to consult elements and record erection progress. From the dashboard's three-dimensional representation, they could select a piece and record its status through Power Apps. The information was associated with the user and date in SharePoint lists and entered the analysis through scheduled refreshes. This introduced an important difference between a reference view and progress tracking fed by people in the field. Superintendents, managers, and executives began to need different views: some focused on locating assemblies; others on reviewing progress, quantities, or financial implications. Reconciliations were adjusted as those needs emerged. My contribution combined solution architecture, automation, and integration within a collaborative R&D effort and in dialogue with site users.