A modern building is designed by many disciplines, built by many trades, and operated for decades after the last of them leaves. For most of construction’s history, the information tying all of that together lived in disconnected drawings and documents. Building information modelling — BIM — is the practice of replacing that fragmentation with a shared, data-rich model. This explainer sets out how BIM works, why it is a process and not just software, and how the ISO 19650 standard frames it.
What is BIM, and how does it work?
BIM is the creation and management of a shared digital model of a building or infrastructure asset — a model that carries not only three-dimensional geometry but structured information about each element: what it is, what it is made of, its performance, its relationships to other elements. That model is used collaboratively across the asset’s whole lifecycle, from early design, through construction, into operation and maintenance. The essential idea is that information is created once, enriched as the project proceeds, and reused by everyone who needs it, rather than redrawn and re-entered at each stage.
The most important thing to understand about BIM is that it is a process as much as a technology. The 3D model is the visible part, but the value comes from the data attached to objects and from the agreed ways of working around them: what information each party must provide, when, in what format, and where it is stored. Treating BIM as merely 3D software is the classic mistake; the coordination and information management are where the benefits actually live.
The building blocks of a BIM process
A functioning BIM process rests on a few core concepts, defined below.
| Concept | What it means |
|---|---|
| Information requirements | A clear statement of what information the client and project need, so models are built to purpose rather than guesswork |
| Common data environment (CDE) | The agreed single source of project information — a managed space for storing, sharing and controlling models and documents |
| Federated model | Discipline models (architecture, structure, services) combined into a coordinated whole for checking and review |
| Level of information need | How much geometric and data detail is appropriate at each stage — enough to serve the purpose, no more |
| Information handover | The structured data passed to the operator so the finished asset can be run and maintained |
These pieces work together: information requirements say what is needed, the CDE governs how it is shared, the federated model lets disciplines coordinate, and the handover carries data into operation. Because factory-based methods leave little room for on-site correction, this coordination is especially important for the off-site approaches described in our explainer on what modular construction is.
What BIM enables
Once a project works from a coordinated, data-rich model, several capabilities follow. Clash detection uses the federated model to find where elements from different disciplines would physically conflict — a duct running through a beam, say — so the conflict is resolved digitally before it becomes expensive rework on site. Quantity and cost information can be drawn from the model, since objects carry data about what they are. Scheduling can link model elements to a construction sequence, helping plan and visualise how the build will proceed. And the information handover gives the operator a structured record of the as-built asset — what equipment is installed, where, and with what maintenance requirements — turning the model into an operational asset in its own right.
These capabilities are frequently described with shorthand such as “3D” for geometry and higher “dimensions” for time and cost information, but the labels matter less than the underlying idea: structured data, coordinated once and reused throughout.
BIM across the asset lifecycle
The full value of BIM shows up only when the model is treated as a lifecycle asset rather than a design deliverable that is discarded once the building opens. In the design phase, disciplines develop their models, coordinate them into a federated whole, and resolve clashes and design problems digitally. In the construction phase, the model supports planning, sequencing and coordination, and is updated to reflect what is actually built, producing an as-built record rather than a theoretical design. In the operation phase — by far the longest and, over a building’s life, the most expensive — the operator inherits a structured information set describing what is installed and where, which supports maintenance, space management and future refurbishment.
That handover from construction to operation is where many projects fall short, and it is worth dwelling on because it is where much of BIM’s promised return actually sits. A building might be operated for decades, and an operator who knows exactly what equipment is installed, its specification and its maintenance regime is far better placed than one working from boxes of paper handed over at completion. Realising this benefit requires deciding, early, what operational information the client needs and ensuring the project produces it — which is precisely why clear information requirements at the outset matter so much. Coordinated models are also central to off-site methods, where factory production leaves no room for on-site improvisation and every dimension must be right before manufacturing begins.
Who does what: roles and responsibilities
BIM only works when responsibility for information is assigned as clearly as responsibility for physical work. In a mature BIM project, the client (or their representative) sets out what information they need and why; a party is responsible for coordinating information delivery across the project; and each discipline is responsible for producing its own models to the agreed standard, at the agreed level of detail, and delivering them into the common data environment on time. The ISO 19650 framework formalises these responsibilities so that information delivery is managed rather than left to chance.
This is the human core of BIM, and it is why the method so often succeeds or fails on organisation rather than technology. If no one owns coordination, discipline models drift out of alignment. If information requirements are vague, teams produce models rich in the wrong detail and poor in what the client actually needs. If the common data environment is not disciplined, people quietly revert to sharing files by email and the single source of truth evaporates. Good BIM is, in large part, good information management — clear roles, clear requirements and clear governance around a shared model.
Standards: ISO 19650 and open data
For BIM to work across organisations, everyone must agree on how information is produced, named, shared and controlled. The international framework for this is ISO 19650, a series of standards for managing information over the lifecycle of a built asset using BIM. It defines the key concepts — information requirements, the common data environment, roles and responsibilities for information delivery — and gives projects a common language and process. The standard series is published by the International Organization for Standardization; an overview of the first part is available from ISO.
Because a project uses many software tools, exchanging model information between them requires vendor-neutral formats. The most widely used is IFC (Industry Foundation Classes), an open data schema maintained by buildingSMART International, which allows a model created in one application to be shared and read in another. Open exchange formats matter because they prevent a project’s information from being locked to a single vendor and support the collaboration that BIM depends on. Some governments have made BIM a requirement on public projects, which has accelerated adoption of these standards.
Benefits, and the honest caveats
Infrastructure projects — roads, rail, utilities — increasingly use the same principles, and there the coordination benefit can be even larger, because linear assets cross many disciplines and existing constraints. The vocabulary shifts slightly, but the core idea is unchanged: a shared, data-rich model that many parties build and rely on over the asset’s life, rather than a stack of disconnected drawings.
The potential benefits of BIM are real: fewer clashes and less rework, better-coordinated design, more reliable information for cost and programme, and a usable data handover for operating the asset. But they are not automatic. BIM demands investment in skills, software and process discipline; its benefits depend on clear information requirements and genuine collaboration between parties who may have different commercial interests. Poorly implemented, BIM produces detailed models that no one maintains or trusts. Well implemented, it changes how a project handles information from start to finish. The difference is process maturity, not software licences.
How analysts study the BIM market
BIM spans software, services, training and the wider shift to digital construction, so it does not reduce cleanly to a single figure and any headline number should be read cautiously. A more reliable analysis segments by offering (software, services, consulting), by end-use sector (buildings versus infrastructure), by project stage (design, construction, operation), and by adoption driver (voluntary versus mandated), then studies each segment’s participants and dynamics. That segment-first discipline is the method we set out in our guides to market sizing and market-research methodology. For readers evaluating BIM, the durable questions concern process rather than product: are the information requirements clear, is there a working common data environment, and does the team actually collaborate around the model? Further coverage sits in the construction and infrastructure hub.
