No one had documented MicroStation-specific requirements before the project started. The structural team had used a seed file from a previous bridge project with a different Geographic Coordinate System (GCS) – a custom Lambert projection instead of the mandated State Plane NAD83(2011). They also had their Working Units set to ft (decimal feet), while civil used ft-in (architectural). MicroStation had tried to align them, but cumulative rounding errors over 2 km of bridge had drifted the models apart.
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. microstation software requirements
With the requirements signed off by all discipline leads, David pushed the document into a lightweight change management system. Each week, a scheduled MicroStation Batch Process ran a validation script that checked every updated .DGN against the requirements. MicroStation had tried to align them, but cumulative
“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.” With the requirements signed off by all discipline