6D, 7D and the nD Hype

Three dimensions are stable and mean the same thing wherever you go. 3D is spatial coordination — the federated, clash-checked model (lesson 2.1). 4D is time — the model linked to the construction programme (lesson 2.2). 5D is cost — the model linked to quantities and rates (lesson 2.3). These are not controversial. You can say '4D' or '5D' in Delhi, London or São Paulo and be understood.

Notice what they have in common, because it is the key to the whole subject: each 'dimension' is a *type of information* linked to the model, not a new kind of geometry. 4D does not make the model more three-dimensional; it adds a time attribute. 5D adds a cost attribute. The word 'dimension' is a metaphor — a layer of data — and once you see that, the higher numbers become much easier to judge honestly.

Above 5D, agreement breaks down. 6D is most often used for sustainability / energy information — the data that lets you analyse energy use, carbon, and environmental performance. But a large body of sources uses 6D for facility management / lifecycle instead, and calls sustainability something else entirely. 7D has the mirror-image problem: to some it is facility management, to others it is sustainability, to others operations and maintenance.

There is nothing wrong with the underlying ideas — a model that carries reliable energy data, or reliable asset-management data, is genuinely valuable (Modules 6 and 8 cover both properly). The problem is purely that the labels are not standardised, so '6D' and '7D' are ambiguous shorthand. If someone commits to delivering '6D BIM', the only sensible next question is: *which* 6D — energy or facilities? The number tells you nothing on its own; only the specified information does.

Past 7D, the numbers are largely a sales ladder. '8D' for safety, '9D' for lean construction, '10D' for something loftier — these appear in vendor decks and conference talks, not in the standards that actually govern BIM. ISO 19650, the framework the serious world uses to manage information, does not speak in Ds at all; it speaks in *information requirements* — what information, to what quality, for what purpose, by when.

That is the tell. The standards body that most rigorously defines how to manage building information does not use the dimension ladder, because the ladder is a marketing device, not a technical one. A higher number sounds like more capability; often it just means more slideware. Whenever you meet an 8D, 9D or 10D, translate it back into the only question that matters: *what specific information are we actually producing, and what is it for?* If there is a real answer, the number was unnecessary. If there is not, the number was the whole point.

Strip away the numbers and one durable principle remains: you add a layer of information because a real purpose needs it — never to collect a dimension. Model energy data because someone will run an energy analysis and act on it. Capture asset data because a facility manager will operate the building with it. Link cost because decisions will be priced against it. Each layer must be *required* by an actual use, produced to the reliability that use needs, and no more.

This is exactly how ISO 19650 thinks (Module 5): start from what the information is *for*, then produce precisely that. 'Are we doing 7D?' is the wrong question; it cannot be answered because the term is undefined. 'Do we have reliable asset information the operator can actually use at handover?' is the right one, and it has a real answer. Chase purposes, not numbers — and the whole nD ladder resolves into something simple: the model, plus whatever information a genuine need requires, at the quality that need demands.