Coordination of Design Subteams

Enhancing Coordination Between Architectural, Structural, and MEP Models in BIM In a BIM environment, seamless coordination between architectural, structural, and MEP disciplines is critical to reducing clashes, minimizing rework, and ensuring a smooth construction process. However, many projects still suffer from misalignment, inconsistencies, and communication gaps between disciplines. So, how can we improve multidisciplinary BIM coordination? 🔹 1️⃣ Establish a Clear BIM Execution Plan (BEP) ✅ Define roles, responsibilities, and data exchange protocols ✅ Standardize naming conventions, file structures, and modeling guidelines ✅ Set clear Level of Development (LOD) and Level of Information (LOI) requirements 🔹 2️⃣ Implement a Robust Clash Detection Workflow ✅ Use Navisworks, Solibri, or Revit Interference Check to detect conflicts early ✅ Conduct regular coordination meetings to resolve clashes before construction ✅ Categorize clashes into critical, moderate, and minor to prioritize resolutions 🔹 3️⃣ Work with Shared Coordinates for Spatial Accuracy ✅ Ensure all disciplines align to a common coordinate system ✅ Regularly audit models to prevent geometric misalignment ✅ Use a Common Data Environment (CDE) to manage file locations and references 🔹 4️⃣ Optimize Worksharing and Model Linking ✅ Use Worksets and Linked Models efficiently to avoid file overload ✅ Maintain consistent model updates and regularly synchronize with central ✅ Set clear visibility and discipline-specific view templates for clarity 🔹 5️⃣ Improve Cross-Discipline Communication ✅ Foster collaboration between teams rather than working in silos ✅ Schedule regular model coordination reviews at key project milestones ✅ Use BIM Collaboration Tools (e.g., BIM 360, ACC, or Trimble Connect) for real-time issue tracking 📌 Key takeaway: Effective BIM coordination is not just about software—it’s about clear workflows, strong communication, and a shared commitment to accuracy. When all disciplines work in sync, projects benefit from fewer clashes, smoother execution, and improved project efficiency. 👉 How do you handle BIM coordination challenges in your projects? Let’s discuss! ⬇️ #BIM #Coordination #DigitalConstruction #MEP #StructuralEngineering #ArchitecturalBIM #ISO19650 #ClashDetection #CDE #BIMManagement

Let's be honest: extensive cross-team coordination is often a symptom of a larger problem, not an inevitable challenge that needs solving. When teams spend more time in alignment than on building, it's time to reconsider your organizational design. Conway's Law tells us that our systems inevitably mirror our communication structures. When I see teams drowning in coordination overhead, I look at these structural factors: - Team boundaries that cut across frequent workflows: If a single user journey requires six different teams to coordinate, your org structure might be optimized for technical specialization at the expense of delivery flow. - Mismatched team autonomy and system architecture: Microservices architecture with monolithic teams (or vice versa) creates natural friction points that no amount of coordination rituals can fully resolve. - Implicit dependencies that become visible too late: Teams discover they're blocking each other only during integration, indicating boundaries were drawn without understanding the full system dynamics. Rather than adding more coordination mechanisms, consider these structural approaches: - Domain-oriented teams over technology-oriented teams: Align team boundaries with business domains rather than technical layers to reduce cross-team handoffs. - Team topologies that acknowledge different types of teams: Platform teams, enabling teams, stream-aligned teams, and complicated subsystem teams each have different alignment needs. - Deliberate discovery of dependencies: Map the invisible structures in your organization before drawing team boundaries, not after. Dependencies are inevitable and systems are increasingly interconnected, so some cross-team alignment will always be necessary. When structural changes aren't immediately possible, here's what I've learned works to keep things on the right track: 1️⃣ Shared mental models matter more than shared documentation. When teams understand not just what other teams are building, but why and how it fits into the bigger picture, collaboration becomes fluid rather than forced. 2️⃣ Interface-first development creates clear contracts between systems, allowing teams to work autonomously while maintaining confidence in integration. 3️⃣ Regular alignment rituals prevent drift. Monthly tech radar sessions, quarterly architecture reviews, and cross-team demonstrations create the rhythm of alignment. 4️⃣ Technical decisions need business context. When engineers understand user and business outcomes, they make better architectural choices that transcend team boundaries. 5️⃣ Optimize for psychological safety across teams. The ability to raise concerns outside your immediate team hierarchy is what prevents organizational blind spots. The best engineering leaders recognize that excessive coordination is a tax on productivity. You can work to improve coordination, or you can work to reduce the need for coordination in the first place.

The goal of design coordination should be to eliminate RFI’s on site.   So how do we make sure our models are problem-solvers, and not just digital objects?   Instead of just modeling, ask these 3 questions: - What is the impact of this element on all other disciplines? This forces us to think beyond our own scope. It's not just about whether our element fits; it's about whether it creates a problem for the structure, the services, or the architectural intent. - Have we allowed for installation, access, and maintenance? A component might fit perfectly in the model, but if a crew can't get tools in to install it or it can't be accessed for future maintenance, it's a design failure. We must model the true spatial requirements. - Is the necessary data embedded for downstream teams? We must embed the critical data that the procurement, construction, and operations teams need to make decisions. This prevents the RFIs that arise from missing or ambiguous information.   This shift from a drafting-centric to a problem-solving approach turns the model from a contractual obligation into your project's most powerful risk mitigation tool.   #BIM #DigitalConstruction #VDC #Revit #ConstructionManagement #AEC

Design Coordination and Shop Drawings ! Client Question: What would you do differently if we had to do it again to avoid delays in producing 3D coordinated models and shop drawings? My Response: 1. Avoid Value Engineering (VE) changes during construction. Once construction has started, changes initiated by the client can create a ripple effect throughout the entire team — from design consultants to subcontractors. These late changes are a major source of delay and should be minimized. 2. Improve communication between suppliers, subcontractors, and the BIM team. Direct and transparent communication is essential. Information often takes too long to flow through the current chain, and this causes major delays. It would help significantly if suppliers, subcontractors, and BIM coordinators were connected early and directly. In addition, the client-side review/approval process needs to be more streamlined and responsive. 3. Ensure BIM teams are skilled, fully dedicated, and accountable. Having BIM coordination meetings without seeing updated models a week later doesn’t move the project forward. Subcontractor and supplier BIM teams must be upskilled where needed and fully committed to keeping models current. 4. Structure coordination efforts around levels and issue freeze versions. Focus on resolving critical coordination issues per level. Then, issue shop drawings and freeze the 3D model for that level. Set clear targets and deadlines for coordination and shop drawing completion (weekly or biweekly), covering all trades — including support models and setout drawings. 5. Prioritize coordination in the following order: 5.1 Equipment supports and clearance on all sides 5.2 Roof deck structure supports and openings for major equipment 5.3 Water treatment systems — early coordination with specialist suppliers 5.4 Busbar factory shop drawings — clearances from structure, architecture, and all MEP trades 5.5 Gravity pipes vs structure — maintain proper clearances 5.6 Corridor coordination — busbars, trays, chilled water pipes, ducts, fans, air terminals, and fire systems. There should be a clear hierarchy or design principle that subcontractors follow in terms of spatial priority. 5.7 Fire pressurized systems and gas tanks — confirm space and routing without unnecessary bends or elevation changes 5.8 Electrical vs mechanical support clashes — start early with support load calculations and integrate designs with routing of trays, pipes, ducts, and busbars 5.9 Ensure all MEP elements are clear of structural columns, beams, doors, and windows 5.10 Pay attention to all MEP openings in RC walls, floors, and roofs 5.11 Double-check that lift dimensions from suppliers match the design requirements #projectmanagement #BIM #VDC #Doittherightway #HappyEaster

🚦 The Overlap of Division 14 & Division 28: Why Coordination Matters One of the most critical coordination points in building design is where Division 14 (Elevator Systems) and Division 28 (Electronic Safety & Security) intersect. When it comes to floor-by-floor access control, destination dispatch, and hall call control, success depends on early and detailed collaboration between both divisions. -Floor-by-Floor Control ensures that cardholder permissions are correctly tied to elevator stops. Without coordination, you risk misalignment between security credentials and elevator programming. -Destination Dispatch Integration requires Div 28 systems to talk seamlessly with Div 14 equipment, so that passenger assignments honor both efficiency and security. -Hall Call Control is another shared responsibility—security must authorize the call while elevator controls manage the movement. 🔗 There are several methods of interfacing Div 28 with elevator systems, each with its own implications for cost, complexity, and functionality: -Dry Contact/Relay Interface – simple, reliable, but limited in flexibility. Serial Communication (RS-232/RS-485) – allows richer data exchange but requires manufacturer coordination. -Network/IP Integration via API – provides the most seamless and scalable option, supporting advanced features like real-time floor access changes and destination dispatch. -Third-Party Middleware or Certified Interfaces – often required by elevator manufacturers to maintain warranty and ensure compliance. When Division 14 and Division 28 work in silos, the result can be conflicting scopes, gaps in responsibility, or costly reprogramming. But when these teams coordinate early, we achieve a system that is not only secure and efficient, but also intuitive for end users. 💡 The best way to bridge these gaps? Hire a professional security consultant early in the design process. A consultant can align the requirements of both divisions, ensure the correct interface method is selected, and protect the owner’s investment by avoiding rework. In today’s projects, access control and vertical transportation are inseparable—and bridging the gap between Div 14 and Div 28 is key to delivering smarter, safer buildings. #AccessControl #ElevatorSystems #Division14 #Division28 #Coordination #BuildingDesign #SecurityConsulting

Mastering ACC + BIM 360 Collaboration The Smart Way to Coordinate BIM Projects In a fast-paced AEC industry, collaboration isn’t a luxury—it’s a necessity. That’s why tools like Autodesk Construction Cloud (ACC) and BIM 360 are game-changers when used the right way. To help you and your team stay aligned, I created a simple visual roadmap that breaks down the full workflow into 8 clear, action-driven steps. Here’s how effective collaboration should look like in your BIM process: 1. Project Setup in ACC Kick off by creating your project in ACC. Enable the needed modules (Docs, Design Collaboration, etc.) and define roles, permissions, and folder structure. This sets the foundation for smooth teamwork. 2. Upload & Organize BIM Models Revit and IFC models are uploaded and categorized in WIP, Shared, and Consumed folders. This structure allows for versioning and clear control over what’s visible and editable. 3. Team Creation in Design Collaboration Form dedicated teams (Architecture, Structure, MEP). Each gets its own WIP space to work independently while staying part of the bigger ecosystem. 4. Worksharing in Revit (Cloud Models) Collaborate live in Revit using cloud worksharing. No more local model confusion—everyone accesses the same source of truth. 5. Model Publishing When models are ready, publish them from Revit to the cloud. They’re versioned automatically and only visible to other teams once shared. 6. Package Creation & Sharing Create coordination packages—containing views, sheets, and model elements—and move them from WIP to Shared folders. Other teams can now reference your updates. 7. Consuming Packages Teams review and consume packages into their own models. This is where design coordination becomes truly collaborative. 8. Issue Management & Clash Detection Using Docs and Model Coordination, teams can perform clash checks, raise issues, assign responsibilities, and track resolutions—all within the platform. Why this visual matters: • It simplifies onboarding for new team members • It brings clarity to inter-team workflows • It boosts accountability and reduces rework • It aligns your field and office teams around a clear data flow Whether you’re managing a small project or a multi-disciplinary mega-development, having this visual roadmap ensures consistency, transparency, and efficiency. Let’s build smarter, together. #BIM360 #ACC #AutodeskConstructionCloud #BIMWorkflow #Revit #ModelCoordination #BIMManager #DigitalConstruction #AEC #ClashDetection #BIMStrategy #ProjectManagement