What is BIM? A complete guide to Building Information Modeling

Building Information Modeling (BIM) is the process of creating, sharing and managing structured digital information about a built asset across its life cycle. The information is held in a model made of objects that represent real building elements, each carrying attributes such as type, material, dimensions, cost and maintenance requirements.

“Use of a shared digital representation of a built asset to facilitate design, construction and operation processes to form a reliable basis for decisions.”

The acronym is used in three related ways. It is the process of producing and managing information, the model that holds it, and the management of that information between organisations. That third meaning matters: most BIM failures are information failures, not modelling failures.

The practical test of whether something is BIM is not how good it looks on screen. It is whether you can query it. Can you count every door with a specific fire rating, check a level against a clash, price a change, or hand an asset register to a facilities team? If yes, you are working in BIM regardless of which tool produced the model.

A BIM process links who needs what information, when, and in which format. On a typical project the loop runs like this:

1. 1Define requirements. The client states what it needs the asset to do and what information it needs to manage it. On ISO 19650 projects this appears as exchange information requirements (EIR) for delivery and asset information requirements (AIR) for operation.
2. 2Plan the delivery. The delivery team responds with a BIM execution plan (BEP), a master information delivery plan (MIDP) and task information delivery plans (TIDP) that name the models, owners and dates.
3. 3Author discipline models. Architecture, structure, MEP and civil teams model their scope at the agreed level of information need, in tools suited to their discipline.
4. 4Federate and coordinate. Discipline models are combined for spatial coordination and clash detection. Issues are raised, assigned and tracked, usually in BCF so the conversation stays attached to the element.
5. 5Check against requirements. Automated checking validates the model against the client requirements: classifications, data completeness, and rules such as clearances or fire ratings.
6. 6Share through a CDE. Models and documents move through a common data environment with controlled states, so published information is always the current, approved version.
7. 7Hand over and operate. At completion the information is issued as an asset information model: COBie data, as-built models, O&M documentation, and the basis for digital twin or facility management systems.

On top of geometry, teams add time, cost and performance: 4D links model objects to a construction programme, 5D attaches quantities and cost, and 6D covers performance and sustainability data. These are views on the same information, not separate models, and they only work if the underlying data is consistent.

CAD (computer-aided design) is a drafting technology. BIM is an information technology that also produces drawings. Both can describe the same building, but they behave very differently when the design changes or another team needs the data.

In practice the two coexist. Detail drawings, reinforcement bar lists and survey data still use drafting conventions, and many practices run hybrid workflows. The distinction that matters for selection is whether a tool authors information models or only documents them.

BIM only pays off when information can move between organisations and tools. That is why the standards ecosystem matters more than any single software licence.

ISO 19650

Information management over the asset life cycle: concepts, delivery phase and operational phase. Defines information requirements, the CDE and the exchange process.

IFC

The open BIM data format, standardised as ISO 16739. Transfers geometry and data between tools, with model view definitions narrowing what must be exchanged for a specific use.

IDS

Information Delivery Specification: a machine-readable way to state the information a model must contain, so compliance can be checked automatically rather than argued over.

BCF

BIM Collaboration Format: carries issues, viewpoints and comments between coordination tools and authoring software, so a markup stays linked to the element it refers to.

bSDD

buildingSMART Data Dictionary: a shared classification and property source, so “fire rating” means the same thing in every model.

COBie

A structured handover dataset for asset information, commonly required at practical completion and read by facilities management systems.

Public-sector mandates vary by country and continue to evolve, so the requirement that matters is the one written into your appointment or contract. Rather than assume a tool is compliant, check documented support for the exact IFC version, IDS rules and BCF exchange your project specifies. Our OpenBIM hub tracks IFC 2x3, IFC4, IFC4.3, BCF, IDS and bSDD support per product, with the source for each claim.

• Better decisions earlier. Options can be modelled, measured and compared before commitments are made, when change is cheapest.
• Fewer coordination surprises. Federated models surface clashes and clearance problems in the office rather than on site.
• Reliable quantities and cost. Consistent object data supports take-offs, 5D cost models and change pricing without re-measuring drawings.
• Constructability and programme. 4D sequencing tests the build order, temporary works and site logistics before mobilisation.
• Manufacturing accuracy. Detailing models drive fabrication and prefabrication, where tolerance errors are expensive.
• Carbon and performance analysis. Material quantities feed embodied carbon and energy studies directly from the model.
• A usable handover. Asset data, O&M information and as-built models reduce the effort of commissioning and operation.
• Safer projects. Clash-free, sequenced models reduce rework, hot works conflicts and unplanned work at height.

These benefits are conditional. Evidence from industry surveys, including the NBS Digital Construction Report, consistently shows that value depends on clear requirements, trained teams and information being used rather than merely produced.

BIM is applied wherever an asset is complex enough that coordination and information continuity outweigh the cost of modelling.

• Buildings. Architectural, structural and MEP coordination, compliance checking, and fit-out with asset data for operation.
• Infrastructure. Roads, rail, bridges and utilities modelled with alignment-based tools, then federated with structures and systems. See the global infrastructure map for software in verified use on major programmes.
• Energy and industrial. Plant, piping and equipment models where clash avoidance and as-built accuracy drive shutdown planning. Hinkley Point C is a documented example.
• Existing assets. Survey and scan-to-BIM workflows capture what is already built, for refurbishment, adaptation or a digital twin.
• Operation. Asset information models feed maintenance planning, space management and connected building systems.

BIM changes who is accountable for information, not just how drawings are produced. The roles below appear in most formal frameworks; titles differ between organisations, so check the definition in the appointment rather than the job advert.

Information manager

Sets up and runs the information management process: requirements, the CDE, exchange schedules and compliance with ISO 19650.

BIM manager

Owns standards, templates, content and capability inside an organisation, and often represents it in project setup.

BIM coordinator

Runs day-to-day federation, clash resolution and model quality across disciplines.

Discipline leads

Author and QA their own models, and own the data their scope delivers.

Client or asset owner

Defines the information requirements and receives the asset information model at handover.

The documents that make it work are unglamorous and decisive: exchange information requirements, a BIM execution plan, MIDP and TIDPs, a federation schedule, and a naming and classification convention everyone actually follows.

No single product covers a project. A working stack spans authoring, coordination, checking, a common data environment and analysis, chosen so that information survives the handoffs between them.

Start with the full software market to filter by IFC version, API support, deployment and security posture, then shortlist with the side-by-side comparison.

Be sceptical of “BIM capable” as a marketing term. Ask which IFC version the tool imports and exports, whether it maps custom property sets, what it does with classifications, and whether issue exchange is BCF-based. BMI records each of these with a provenance label so you can see whether a claim is verified, vendor reported or community reported.

1. 1Pick one real project and one clear use case: coordination, quantity take-off or compliance checking. Do not attempt a firm-wide transformation first.
2. 2Write down what information you need and who needs it, before choosing software.
3. 3Agree the exchange format and version (IFC 4 or IFC 4.3), plus how issues will be exchanged (BCF).
4. 4Set up a single location for current, approved information, even if it is a shared folder with strict discipline.
5. 5Train one coordinator properly. Skills, not licences, are usually the constraint.
6. 6Measure something: clashes resolved before site, hours saved on take-off, change orders avoided.
7. 7Expand to other disciplines only once the first loop works end to end.

If you are choosing tooling, start from requirements rather than brand: the selection assessment scores the market against interoperability, security and commercial criteria you set.