By month 18, H&A had federated over 1,400 MicroStation files into a single integrated model. Clash detection between structural steel and HVAC runs—normally a three-week ordeal—was reduced to a 45-minute automated session because the requirements enforced consistent origin points and reference offsets.
At the project closeout, the MDA CIO asked David, “What was the secret to delivering without a single fatal clash?”
The client, MDA, requested an urgent change: move a pier foundation 6 meters west to avoid an unexpected underwater rock shelf. Because the MicroStation requirements mandated parametric cells and design history , Elena changed a single input variable ( pier_location_offset ), and the entire foundation, rebar, and formwork updated across 22 referenced files in under 15 minutes.
Three weeks later, the script flagged a new revision from the drainage team: they had created a custom level named PIPE-FLEX-CLV outside the approved library, and their Working Units had drifted to m for a single file.
The drainage lead grumbled but fixed it in two hours. No misalignment. No rework.
“We didn’t assume everyone ‘knew MicroStation,’” he said. “We wrote down exactly how this team, on this project, would use it. The software works. It’s the human agreement on requirements that makes it magic.”
David opened the master .DGN file on his workstation. He toggled the structural reference file. The mismatch was glaring—a red line cutting through grey slabs.
“David, the structural team’s foundation plans don’t align with my roadway profile. Their concrete piers are 1.2 meters east of my centerline.”