Welcome to the first post in our new series, “BIM in Practice,” where we aim to make the complexities of Building Information Modeling (BIM) accessible to everyone. Inspired by the simplicity of “General Relativity for Babies,” this series will break down key concepts using clear explanations and minimalistic visuals.

ELI5-S1 BIM in Practice: E1: Shared Context of Information Exchange Explained

In any BIM project, understanding the shared context of information exchange is crucial. We’ll begin by viewing information management through what I call the “contextual lenses.”

The Six Contextual Lenses:

1. Shared Context
2. Operational Team
3. Delivery Team
4. Tier 0 (T0) Appointing Party
5. Tier 1 (T1) Lead Appointed Party
6. Tier 2 to Tier 4 (T2-T4) Appointed Party

Shared Context: A Closer Look

This first lens, “Shared Context,” is derived from my extensive research and professional experience. It highlights the following common characteristics essential for effective information exchange across all six lenses:

• Responsibility Transfer: Efficient handover of tasks and responsibilities between teams and phases.
• Effective Use of Expertise: Leveraging the right skills and knowledge at the right times.
• Increasing Value of Data: Understanding how data gains importance and utility over the project lifecycle.
• Key Elements (BEP, OIR, CDE, MIDP, TIDP): These are vital for managing project requirements and ensuring smooth information flow.
• Focus on Delivery vs. Outcome: Emphasizing the process of delivery to achieve the desired outcomes.
• Collaborative Processes: Ensuring teamwork and collaboration at every stage.
• High Expertise for Large Projects: Projects over $100M require significant expertise and management.
• Providing Only What’s Requested: Avoiding information overload by delivering exactly what is needed.
• Creating Output Requirements, Not Templates: Tailoring requirements to specific needs rather than relying on generic templates.
• Establishing Volume Strategy: Planning how much information is necessary and manageable.
• Security and Legal Implications: Addressing these critical aspects to protect data integrity and compliance.
• Poor Naming Strategies: Highlighting the importance of consistent and clear naming conventions.
• Overlap Between Operations and Delivery CDE: Managing information overlap effectively.
• Irrelevance of Visual Geometry Aspects: Focusing on functional rather than purely visual information.
• CDE as a Fundamental Requirement: Central Data Environment (CDE) is crucial for successful information management.
• Dependency on Asset Scale and Type: Tailoring information management strategies to the specific asset.
• Templates Limiting Creative Thinking: Encouraging innovative solutions beyond standard templates.
• Interoperability Issues: Addressing challenges with different CDE solutions working together.
• Unwillingness to Learn New Methods: Overcoming resistance to adopting new information management practices.
• CDE Without Rules Is Ineffective: Establishing clear rules for CDE use.
• MIDP and TIDP Without BEP Are Impractical: Ensuring these elements are integrated for effective information management.
• Rare But Serious Security Breaches: Recognizing and mitigating potential security risks.
• IDP as Output Rather Than Resource: Viewing Information Delivery Plans (IDP) as an ongoing resource, not just a final product.
• Priority of CDE Not Always Understood: Ensuring the importance of CDE is recognized and prioritized.
• Confusing Relationship Between AIR and BEP: Clarifying how these elements interact.
• Incompatibility of CDE Solutions: Working towards seamless integration of different CDE systems.
• Importance of Establishing CDE Early: Setting up the CDE at the project’s inception.
• Need for Adequate Supply Chain Training: Ensuring all stakeholders are properly trained.
• Poor Briefs Lead to Poor Delivery: Emphasizing the need for clear and detailed briefs to ensure successful outcomes.

The analysis of these characteristics underscores the importance of crystallising information requirements by creating specific output requirements rather than relying on templates. This approach helps address the various challenges and ensures a more effective information exchange process.

In conclusion, the “Shared Context” lens highlights the foundational aspects that underpin successful information management in BIM projects. By focusing on these elements, we can enhance collaboration, improve data management, and ultimately achieve better project outcomes.