BIM Insights

Building Information Modeling (BIM) is a collaborative digital process for creating, managing, and coordinating information about a built asset throughout its lifecycle. BIM models combine geometry with structured information to help project teams improve visualization, coordination, documentation, and decision-making.

BIM is not simply 3D modeling. It also involves information management, coordinated workflows, data exchange, and clearly defined project requirements.

Sheet
I-300
Scale
1:100
Rev
04
Status
Issued for information
Double H · BIM Services
01

BIM vs traditional CAD

CAD drawings are compositions of lines, arcs and text. A BIM model is made of objects: a wall knows it is a wall, has a material, a height, a location and data attached to it. When the design changes, the model and the views derived from it can update together. In a drawing-based workflow, each affected sheet usually has to be edited separately. BIM is therefore not simply CAD in three dimensions; it is a different way of holding and sharing project information.

Learn more
  • A CAD line has no inherent meaning beyond its geometry. A model element can carry a classification, properties and relationships to other elements.
  • Drawings do not disappear in a BIM workflow. They become views of the model, produced for a specific purpose and checked before issue.
  • The value depends on the information requirements: a geometrically rich model with poor data is not automatically a better deliverable.
02

Multidisciplinary coordination

Architectural, structural and MEP teams often work in separate models. Coordination brings those models into a common space so interfaces can be reviewed before construction. The team looks for physical conflicts, clearance problems and sequence issues, then agrees who will resolve each one. Coordination is a process, not a single clash report: models change, issues are closed, and new information can create new interfaces. A federated model gives everyone the same picture at the same moment.

Learn more
  • Federation means combining reference copies of discipline models without merging authorship into one file.
  • A coordination cycle usually runs from model exchange to clash review, resolution, re-check and sign-off.
  • The most useful coordination meetings are built around a short, prioritised issue list, not every clash in the model.
03

Architectural, Structural & MEP models

The architectural model describes spaces, envelopes, partitions, circulation and the design intent. The structural model describes the frame, slabs, foundations and the load path. MEP models describe mechanical, electrical and plumbing systems: equipment, ducts, pipes, trays, fixtures and the spaces they need. Each discipline relies on the others. A duct route depends on the structure above the ceiling; a structural opening depends on the services passing through it. Keeping the models separate but coordinated preserves authorship while making the interfaces visible.

Learn more
  • Architectural: rooms, walls, doors, windows, finishes, vertical circulation and site context.
  • Structural: columns, beams, slabs, walls, foundations and reinforcement information where modelled.
  • MEP: mechanical equipment and ductwork, electrical distribution and containment, plumbing supply and drainage.
04

Clash detection

A hard clash is a physical intersection between elements, such as a duct passing through a beam. A soft clash, or clearance issue, is a conflict in the space needed for installation, access or maintenance. Detection software finds candidate conflicts; people decide which ones matter. Each issue needs a severity, an owner, a due date and a resolution path. A clash report is only useful if the team can track what happened next. The aim is not zero clashes on a report; it is fewer surprises on site.

Learn more
  • Hard clash: two elements occupy the same space.
  • Soft clash: the elements do not intersect, but the required clearance or access zone is compromised.
  • Workflow: detect, classify, assign, resolve, re-check, close. The re-check is what makes the record trustworthy.
05

LOD and information reliability

Level of Development (LOD) describes how developed an element is and how far its information can be relied on. It is defined per element, not per model: a structural frame may be at a different LOD from the furniture or the fire dampers. LOD is not a measure of visual detail. A highly detailed-looking element can still carry unreliable information. The appropriate LOD depends on the project stage, the decisions the model must support, and the agreed information requirements.

Learn more
  • LOD 100: conceptual; LOD 200: approximate; LOD 300: defined design.
  • LOD 350 adds coordination interfaces; LOD 400 supports fabrication and installation.
  • LOD 500 concerns verified existing conditions and is only claimed where field verification and documentation exist.
06

BIM dimensions 2D–9D

The language of BIM 'dimensions' is a framework for describing what information is connected to the model. 2D is drawing production; 3D is geometric modeling; 4D links time; 5D links cost; 6D supports sustainability; 7D organises asset information for operation; 8D supports safety planning; 9D is used for lean and lifecycle optimisation. Definitions vary between markets and standards. Not every dimension belongs in every engagement, and each one depends on data supplied by the project team.

Learn more
  • The dimensions are a communication tool, not a certification ladder.
  • 4D needs a programme; 5D needs cost data; 7D needs the owner's asset information structure.
  • Agree the dimensions in scope before modeling starts, so the model is built to support them.
07

Shop drawings & as-built documentation

Shop drawings translate the design into the level of detail a fabricator or installer needs: dimensions, connections, supports, penetrations, levels and interfaces. When they are derived from a coordinated model, the sheet and the model can stay aligned. As-built documentation describes what was actually installed. It depends on verified site information, measured conditions and approved changes. A model is not as-built simply because construction is finished; the information has to be checked and recorded.

Learn more
  • Shop drawings are typically produced by or for the trade contractor and reviewed against the design intent.
  • As-built information can include dimensional changes, substitutions, concealed routes and equipment data.
  • LOD 400 is often associated with fabrication and installation; LOD 500 with verified existing conditions.
08

Common Data Environment (CDE)

A Common Data Environment is the agreed single source of truth for project information. It controls where information is stored, who can access it, which version is current, and how it moves between states. Those states are commonly described as work in progress, shared, published and archived, although terminology varies between projects and standards. A CDE is as much a set of rules and responsibilities as it is a software platform. Without those rules, it becomes another folder structure.

Learn more
  • Work in progress: information being developed by its author, not yet for wider use.
  • Shared: checked information made available to other teams for coordination or review.
  • Published: authorised for a defined purpose; archived: retained as a record.
09

Open BIM & IFC

IFC is an open, vendor-neutral exchange format for building information, published as ISO 16739-1. It allows model data to move between different software platforms without requiring everyone to use the same authoring tool. IFC is not a perfect copy of a native model. Not every authoring feature, constraint or material definition survives a round trip. Teams therefore agree what information must be exchanged, how it will be checked, and which version of the format is required.

Learn more
  • IFC is developed and maintained by buildingSMART International.
  • Exchange requirements should name the IFC version, model view definition and information to be included.
  • Always validate an IFC export before relying on it for coordination or delivery.
10

BIM execution planning

A BIM Execution Plan (BEP) sets out how information will be produced, exchanged, checked and used on a project. It typically covers scope, model breakdown, LOD, file formats, naming, coordinate systems, review cycles, roles and delivery dates. A pre-appointment BEP describes the capability and approach a team offers; a post-appointment BEP turns that into the project-specific plan. The document is most useful when it is short enough to be used and specific enough to be checked.

Learn more
  • A BEP should connect each deliverable to a decision or project use.
  • It should define who checks what, when, and against which requirements.
  • It is a living document: changes to scope or programme should be reflected in it.

Standards referenced

ISO 19650 series
The international series for managing information over the lifecycle of built assets using BIM. This page uses the terminology; it does not claim certification or formal compliance by Double H.
IFC · ISO 16739-1
An open, vendor-neutral format for exchanging building information between software platforms, maintained by buildingSMART International.
LOD framework
Level of Development is applied through the framework agreed for each project, such as the BIMForum LOD Specification or project-specific requirements.

This page is general BIM education. It does not describe certifications or formal compliance held by Double H.