Structural and MEP-specific modeling elements, linking discipline models, shared coordinates across linked models, spatial coordination zones and routing conventions, and the common cross-discipline conflicts that surface before they ever reach a formal clash test.
Multi-discipline coordination starts with understanding what makes structural and MEP elements different from the architectural objects covered in Module 5: structural members carry a linked-but-separate analytical model, and MEP systems are connected, logically continuous networks rather than independent objects placed near each other. This module builds on Module 5's parametric-object foundation to explain how those discipline-specific elements are modeled, how independently owned discipline models get linked together through a disciplined publish-and-reload workflow, and why shared coordinates are what actually lets structurally and architecturally correct models line up in real-world space.
By the end of this module you should be able to explain why a stale, unreloaded link or a duct routed with no allowance for insulation thickness can produce a coordination problem that has nothing to do with a genuine spatial conflict — the exact distinction Module 8's clash-detection workflow depends on you already understanding before a formal coordination meeting ever starts.