Skip to content
KitWren
BeginnerFree BIM course about 15 min

Level of development and information need

How detailed should a model be? LOD and Level of Information Need describe what geometry and data are required, when, and for what purpose — so teams neither under- nor over-model.

In this lesson you will

  • Explain LOD 100–400 in practice
  • Separate geometry (LOG/LOD) from information (LOI)
  • Understand Level of Information Need (ISO 7817-1)
  • Avoid over-modelling

Why specify detail

Without agreement, some teams model every bolt while others leave placeholders, and nobody can rely on the model. Specifying the required detail per element and stage makes the model fit for its purpose.

The same wall element shown four times with increasing detail: a generic mass at LOD 100, a generic wall with thickness at 200, a wall with its specified layers at 300, and the wall with fabrication details at 400.LOD 100concept massLOD 200generic wallLOD 300specified layersLOD 400fabrication detail
Figure: Level of development. Original KitWren diagram.

LOD

The widely used Level of Development scale (from the BIMForum LOD Specification) describes how far an element has been developed and how reliable it is:

  • LOD 100 — conceptual; a symbol or mass indicating something exists.
  • LOD 200 — generic element with approximate size and location.
  • LOD 300 — specific element with accurate size, shape, location and orientation.
  • LOD 350 — adds interfaces with other elements (connections, supports).
  • LOD 400 — fabrication detail.
  • LOD 500 — field-verified (as-built), though often treated separately.

The key idea: LOD is about how much others can rely on the element, not how pretty it is.

Geometry and information separately

Many frameworks split geometry (LOG, or geometric detail) from information (LOI — the data attached). A pump may be a simple box (low geometry) with complete manufacturer, capacity and maintenance data (high information). Specify both.

Level of Information Need

ISO 19650 and ISO 7817-1 replace fixed LOD tables with the idea of Level of Information Need: for each purpose, milestone and object, define the geometry, alphanumeric data and documentation actually needed. It's the same principle — only produce what's needed — made explicit per requirement.

Exercise

Specify a door

  1. Write what a door model needs at concept, developed design, construction and handover.
  2. Separate geometry from data at each stage.
  3. Mark anything you'd currently model that isn't needed.

You should end up with: A four-stage information-need table for one element.

Checklist

0 of 4 checked · saved on this device

Lesson quiz

1 / 4

An element with accurate size, shape and location is usually…

Finished this lesson?

Taking the quiz marks it complete too. Your course page picks up where you stopped.

Free KitWren tools that help

Free, independent learning material written for KitWren. We never provide software downloads, licence keys or cracks — use the official sources.