Federate discipline models for coordination

Pull the latest issued model from each discipline and confirm you have the right revision of every one, so the federation reflects where the design actually is.

เหตุผล: Federating a stale structural model wastes everyone's review. Getting the current revision of each discipline first is what makes the clashes you find real and worth fixing.

Combine the discipline models into one federation and confirm their origins and coordinates line up, so an element sits where it really is against every other trade.

เหตุผล: A misaligned origin makes everything look like it clashes and hides the clashes that matter. Getting the models onto one coordinate system is the whole point of federating.

Walk the federated model zone by zone with the design team, looking for the clashes, tight spots and buildability problems the separate models could never show.

เหตุผล: The coordination review is where trades meet before the concrete does. An hour around the federated model saves the rework of a duct that has nowhere to go once the slab is poured.

Raise a BCF issue on each conflict with the viewpoint and the responsible discipline, so every one becomes a tracked action rather than a note in a meeting.

เหตุผล: A clash spotted and forgotten is a clash built. A BCF issue with an owner and a viewpoint is what turns a review into resolved coordination instead of a nice look at the model.