Search filters
Search in title
Search in content
Exact matches only
Filter by Categories
Select all
Academy
AI
Automation
Blog
BPMN
Classification and Standardisation
Common Data Environment (CDE)
Dictionary
Digital Twin
Electrical
Fire
How To
Level of
Management
Organization of information
Procurement
Requirements
Standards
State
Sustainability
Uncategorized

Blog
Digital Construction (electrical)

Industry 4.0 in AEC, means to me a decentralized connection between the physical space and the cyberspace through global connectivity.

Read more…

Exchange Information Requirements (EIR) term introduced by BS EN 19650 replace the PAS 1192 term Employer Information Requirements (EIR) on all projects where BS EN ISO 19650 compliance is required.

Read more…

The term introduced by ISO 19650 typically describes the Tier 1 Main Contractor.

Read more…

breakdown structure to help plan the production of information

Read more…

schedule of information containers and delivery dates, for a specific task team

Read more…

An MPDT its old PAS 1192 term, the MPDT defines who produces what, when and to what level of detail.

Read more…

Delivery Team context of information exchange

ELI5-S2 BIM in Practice E3 Delivery Team context of information exchange

ELI5-S2: BIM in Practice E3: Delivery Team context of information exchange explained

Understanding the context of information exchange from the delivery team’s perspective is essential to optimising project outcomes. This post delves into the nuances of information exchange through the lens of the Delivery Team.

The Six 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

Delivery Team Perspective

  • Focus on Project Information Model (PIM) and Exchange Information Requirements (EIR): The delivery team often prioritises these over the client’s goals and objectives.
  • Detached Appointing Party: The appointing party tends to be too detached from the delivery team, leading to gaps in communication and expectations.
  • Cyclic Information Exchange: The cycle of information exchange between the PIM and the Asset Information Model (AIM) requires constant updates and adjustments.
  • Lack of Expertise: The delivery phase frequently suffers from a severe lack of expertise, especially in low-value projects.
  • High Risk, Low Profit: Delivery teams often face high risks with little profit margins.
  • Limited Learning Opportunities: Projects’ fast-paced nature leaves little room for learning from past mistakes, resulting in repeated errors.
  • Uncertainty in Common Data Environment (CDE) Management: There is often uncertainty around who is responsible for managing the CDE.
  • Focus on Immediate Demands: The delivery team is often seen as having little interest in the Asset Information Requirements (AIR) and AIM, focusing instead on immediate project demands.
  • Dynamic Phase Pressure: The dynamic nature of the delivery phase creates an ever-increasing pressure to learn while simultaneously prioritising project delivery.

By viewing the project through the delivery team lens, we can better manage the challenges faced, ultimately improving the efficiency and success of BIM projects.

Stay tuned for more insights as we continue to explore BIM in an easy-to-understand format. Let’s make BIM knowledge accessible to all!

The idea for the ELI5 series is based on ‘General Relativity for Babies’ by Chris Ferrie.

Leave a Reply

Your email address will not be published. Required fields are marked *

share this page