Beruflich Dokumente
Kultur Dokumente
EXPERTISE
LEVEL OF DEVELOPMENT
ASSOCIATED FILES
BSI_PAS1192-2-A13
CIC_the-bim-protocol
OBJECTIVES
Understand the concept behind LOD and how to work with that when dealing with BIM Models,
requirements and documentation.
DESCRIPTION OF TERMINOLOGY
A BIM model or set of models contain a large amount of elements or objects. And in turn those
objects can contain a large amount of information, thought to represent several aspects of the
project or the building.
Since in a project there are several parties involved (client, designers, consultants, all kind of
intermediaries, building contractors), it is critical to determine how far they are going to define
the project, how much information will be included, how reliable that information is going to be
and what for, and what can they expect from other models and disciplines.
And that should be defined for each project stage or main milestone, also having in mind specific
deliverables needed for specific functions or intended BIM model uses.
For those reasons a common framework about development and certainty of information in
projects is needed. That makes collaboration easier. Every stakeholder will use then the same
language so that they can understand each other properly.
The framework would describe and establish in advance the depth of information to be included
in the elements composing the model and the adequate uses and applications of that
information (which sometimes is carried intended in models, but often unintentionally). Thus it
will be clear how models can be trusted:
That is LOD. It is a language, that serves to know what to expect, and the amount of certainty
about the properties, features and specifications of a given element.
With a sample we can understand better this thing about certainty of information:
There can be a Functional Description:
https://www.modelical.com/en/gdocs/level-of-development/ 1/22
9/5/2017 Level Of Development - Modelical
In an early stage of the project we place a HVAC equipment. Its appearance is simple, it is just a
box, and the information attached is not much. But somehow we have to make it clear what can
we use this model for.
https://www.modelical.com/en/gdocs/level-of-development/ 2/22
9/5/2017 Level Of Development - Modelical
The effort to include such information in the model should follow the impact that information
can have on the whole project development, and the goals we can achieve in the project.
Meaning for example:
There is no point in modelling and include a lot of information about costs and models in elements if we only intend to
perform a spatial coordination between disciplines.
For a detailed cost estimation of project we will need accurate modelling of elements, and detailed information about them.
It is hard to establish the LOD of a complete model as it will probably contain different elements
at different levels.
That is why it is recommended to detail a “Model Production and Delivery Table”, more
commonly referred to as a “Responsibility Matrix”, to clarify what information is going to be
produced at any stage and by who. And moreover, you assign an LOD code against each
building component or system at each progressive stage of the project so the complete team
knows what to expect.
https://www.modelical.com/en/gdocs/level-of-development/ 3/22
9/5/2017 Level Of Development - Modelical
There are two main LOD Standards or frameworks that are widely used, since they correspond to
the main two blocks of influence: US and UK. We will refer to those in this document.
In the US we will find the American Institute of Architects (AIA) - BIM Forum LOD Standard
In the UK we will find the BSI - British Standard Institution Specification (PAS 1192-2:2013)
Level
Of
Development
Level of Level of
Level Of Development
= Graphical + Information
Detail * Included
*Level of Graphical Detail is also known as Level of Detail or again, LOD, that is why there is so
much confusion about the terms. So LOD shall be understood differently depending on the
context.
https://www.modelical.com/en/gdocs/level-of-development/ 4/22
9/5/2017 Level Of Development - Modelical
The LODs are not defined by design phases. Rather, design phase completion, as well as any other milestone or deliverable,
could be defined through the LOD language.
There is no such thing as a “LOD ### model”. Project models at any stage of delivery will invariably contain elements and
assemblies at various levels of development.
LOD Tables or definitions do not replace BIM Execution Plan documents. They complement them. Project information
needs will vary from project to project, and therefore will not be included in the general specifications of the LOD
definitions. It will be then addressed in the individual BEPs.
The LODs provide five snapshots of the progression of an element from conceptual to specified development, there are
many steps in this progression between the defined LODs. LOD definitions, then, should be considered minimum
requirements.
LOD Definitions are Cumulative. For a given element each LOD definition includes the requirements of all previous LODs.
Thus for an element to qualify for LOD 300 it must meet all the requirements for 200 and 100 as well as those stated in the
LOD 300 definition. This rule has an exception for LOD 500, as it is explained in the next section of this document.
The LOD Specification facilitates the application of a pull-planning process to the modelling effort, limiting the development
of model elements and information to that which the team identifies as useful.
Much model information is common across several information exchanges. The LOD Specification facilitates the definition
of models that will support multiple exchanges for various uses. Intended uses of models should be clearly included in the
BEP documents.
The Model Element may be graphically represented in the Model with a symbol or other generic
representation, but does not satisfy the requirements for LOD 200.
LOD 100 elements must be considered approximate.
LOD 200
Elements are a rough representation of the intended object, containing basic functionality and
approximated dimensions. Usually the information contained is poor or nonexistent.
LOD 200 often corresponds to the output of schematic design.
https://www.modelical.com/en/gdocs/level-of-development/ 5/22
9/5/2017 Level Of Development - Modelical
LOD 300
Elements contain a decent representation of their features, both graphical and functional.
This is the minimum LOD an element must be specified in order to define its construction and
assembly.
A detail design project often corresponds to LOD 300.
https://www.modelical.com/en/gdocs/level-of-development/ 6/22
9/5/2017 Level Of Development - Modelical
LOD 350
There are intermediate states, like this widely used LOD 350.
It is the result of the need for a LOD that would define model elements sufficiently developed to
enable detailed coordination between disciplines – clash detection/avoidance, layout, etc–.
Usually the requirements for this use of models are higher than those for 300, but not as high as
those for 400, thus it was designated LOD 350.
Parts necessary for coordination of the element with nearby or attached elements are modeled.
These parts will include such items as supports and connections.
LOD 350 could correspond to a detail design project + detailed coordination between disciplines.
LOD 400
Elements are defined as they will be built, containing all necessary parameters for procurement,
assembly and commissioning.
Achieving a LOD 400 is only possible when contractors are involved, as it will be subject to
construction final budget and capabilities.
https://www.modelical.com/en/gdocs/level-of-development/ 7/22
9/5/2017 Level Of Development - Modelical
LOD 500
As previously stated, LOD stages are cumulative. But LOD 500 is not a linear evolution of LOD
400, as could be understood for what happens in the previous levels.
It is rather a functional representation of building elements in the operation phase. This means
only those objects which are relevant for building maintenance and use are important in this
level.
More important than geometrical accuracy is the information attached to objects.
https://www.modelical.com/en/gdocs/level-of-development/ 8/22
9/5/2017 Level Of Development - Modelical
Level
Of
Model Definition
Level Of Level of
Level of
Model Definition = Graphical +
Information
Detail *
https://www.modelical.com/en/gdocs/level-of-development/ 9/22
9/5/2017 Level Of Development - Modelical
*Level of Graphical Detail is also known as Level of Detail or again, LOD, that is why there is so
much confusion about the terms. So LOD shall be understood differently depending on the
context.
The minimum level of detail needed by the team or the employer for each model’s purpose shall be defined.
It is wasteful for the supply chain to deliver a greater level of detail than is needed which may also overload the IT systems
and networks available. Again this warning against over-modelling.
The level of model definition required in a model at an information exchange shall be defined in the Employer Information
Requirements, directly connected with the intended uses of the model.
The levels of model definition shall be articulated in the BEP and understood by all the stakeholders involved.
There should exist a Model Production and Delivery Table that includes the LOD that models need to meet at the project
stages or data drops. It is recommended that the table includes not MODELS but ELEMENTS.
In the following table we will find the correspondence between Project Stages (from APM) and
LOD Definitions. There is a direct relationship, but not always they should be related in that way.
Remember that is advisable to specify element LODs and not Model LODs.
(For further information see BSI_PAS1192-2-A13 document):
What the
Level of
Project model can be
Model Description
Stage relied upon
definition
for
1 1 At briefing Model
Brief Brief stage, the information
graphical communicating
model will the brief,
either not exist performance
or will inherit requirements,
information performance
from the AIM benchmarks
(for work on and site
existing constraints.
https://www.modelical.com/en/gdocs/level-of-development/ 10/22
9/5/2017 Level Of Development - Modelical
buildings and
structures).
Models which
communicate
2 2 the
Concept Concept initial response
to the brief,
At concept aesthetic intent
design stage and outline
the graphical performance
design may requirements.
only show a The model can
massing be used for
diagram or early design
specify a development,
symbol in 2D to analysis and
represent a coordination.
generic The model can
element. be used for
basic
coordination,
sequencing
and estimating
purposes.
3 At design stage A
3
Developed the objects dimensionally
Definition
Design shall be correct and co-
represented in ordinated
3D with the model which
specification communicates
attached. the response
The level of to
detail should as the brief,
a minimum aesthetic intent
represent the and some
space performance
allocation for information
the product’s that can be
access space used for
https://www.modelical.com/en/gdocs/level-of-development/ 11/22
9/5/2017 Level Of Development - Modelical
for analysis,
maintenance, design
installation and development
replacement and early
space in contractor
addition to its engagement.
operational The model can
space. be used for
Generalised coordination,
systems with sequencing
approximate and
quantities, size, estimating
shape, location purposes
and including the
orientation. agreement of a
first
stage target
price.
At definition A
stage the object dimensionally
shall be based correct and
4 4
on a generic coordinated
Design Production
representation model that can
of the element. be used to
The verify
specification compliance
properties and with regulatory
attributes from requirements.
design allow The model can
selection of a be used as the
manufacturer’s start point for
product, unless the
the product is incorporation
nominated, of specialist
free issue or contractor
already design models
selected. and can
It is a “design include
intent model Information
representing that can be
https://www.modelical.com/en/gdocs/level-of-development/ 12/22
9/5/2017 Level Of Development - Modelical
An accurate
model of the
5 At build and
5 asset before
Build & commission
Installation and during
Commision stage any
construction
generic object
Incorporating
shall be
co-ordinated
replaced with
specialist
the object
subcontract
procured from
design
the
models and
manufacturer.
associated
Any essential
model
information to
attributes. The
be retained
model can be
shall be
used for
reattached or
sequencing of
relinked to the
installation and
replacement
capture of as-
object.
installed
information.
6 At the An accurate
6
Handover handover and record of the
As Built
& Closeout close-out stage asset as a
all necessary constructed at
information handover,
about the including all
product shall information
be included in required for
the handover operation and
document and maintenance.
attached to the
commissioning
https://www.modelical.com/en/gdocs/level-of-development/ 13/22
9/5/2017 Level Of Development - Modelical
and handover
documentation.
The as-
constructed
model shall
represent the
as-constructed
project in
content and
dimensional
accuracy.
At the in-use
stage, the
object’s
information An updated
shall be record of the
updated with asset at a fixed
any point in time
supplementary incorporating
information any major
such as changes
maintenance made since
7 7
records or handover,
Operation In use
replacement including
dates, and performance
objects that and condition
have been data and all
changed or information
replaced with required for
different operation and
equipment maintenance.
shall be
updated
accordingly.
Following table is a sample of a Model Production and Delivery Table, as included in the CIC BIM
Protocol (See CIC BIM Protocol document):
https://www.modelical.com/en/gdocs/level-of-development/ 14/22
9/5/2017 Level Of Development - Modelical
Level of
Level of
Development
LOD Definition LOD
(BIM FORUM
(PAS 1192)
2015)
https://www.modelical.com/en/gdocs/level-of-development/ 15/22
9/5/2017 Level Of Development - Modelical
requirements, a symbol or
performance other generic
benchmarks representation,
and site but does not
constraints. satisfy the
At briefing requirements
stage, the for LOD 200.
graphical Information
model will related to the
either not exist Model Element
or will inherit (i.e. cost per
information square foot,
from the AIM tonnage of
(for work on HVAC, etc.) can
existing be derived
buildings and from other
structures). Model
Elements.
A
dimensionally
correct and
co-ordinated
model which
communicates
The Model
the response
Element is
to the brief,
graphically
aesthetic intent
represented
and some
within the
performance
Model as a
information
specific
that can be
system, object
used for
or assembly in
3 analysis,
300 terms of
Developed design
quantity, size,
Design development
shape,
and
location, and
early
orientation.
contractor
Non‐graphic
engagement.
information
The model can
may also be
be used for
attached to the
coordination,
Model
sequencing
Element.
and estimating
purposes
including the
agreement of a
first stage
target price.
https://www.modelical.com/en/gdocs/level-of-development/ 17/22
9/5/2017 Level Of Development - Modelical
information
may also be
attached to the
Model
Element.
The Model
Element is a
field verified
An accurate representation
record of the in terms of
asset as a size, shape,
constructed at location,
6
handover, quantity, and
As 500
including all orientation.
Constructed
information Non‐graphic
required for information
operation and may also be
maintenance attached to the
Model
Elements.
An updated
record of the
asset at a fixed
point in time
incorporating
any major
changes
made since
Updated
7 handover,
500 model.
In use including
performance
and condition
data and all
information
required for
operation and
maintenance.
https://www.modelical.com/en/gdocs/level-of-development/ 19/22
9/5/2017 Level Of Development - Modelical
Model Use LOD 200 LOD 300 LOD 400 LOD 500
Coordination
Optimal if Adequate if
review and
Adequate also done also done in Unnecessary
clash
LOD 200 LOD 300
detection
Adequate
Adequate if
but
4D Sequence Adequate also done in Unnecessary
intensive
LOD 200
labour
Quantity
Not
take-off and Adequate Optimal Adequate
adequate
review
Highly
Site planning Adequate Unnecessary Unnecessary
unnecessary
•Water
supply
system
•Fire
fighting
system
•Shafts and
shunts
•Lighting
fixtures
and panels
•Construction
•Earthworks
joints
•Structure
•Concrete •Only
4D assemblies
pouring major
Sequences •Formwork
joints elements
•Cranes and
•Facade
machinery
assemblies
•Ducts and
mechanical
equipment
•Sanitary
•Walls, columns
downpipes
•Partitions and retaining
and
and facade walls
branches
elements •Slabs and mat
•Water
with slabs
supply
specifications •Framing,
Quantity system
•Windows beams,
take-off and •Fire
and openings openings
review fighting
•Staircases •Foundations
system
and ramps. •Materials and
•Shafts and
Elevators coding
shunts
•Finishes •Reinforcement
•Valves
•Furniture general
and pumps
quantities
•Lighting
fixtures
and panels
•
https://www.modelical.com/en/gdocs/level-of-development/ 21/22
9/5/2017 Level Of Development - Modelical
BOTTOM-LINE
Model sparingly to meet the needed model development so it can serve the intended uses of the model.
Intended uses of the model should be clear in advance, so that the project and model development can be programmed
accordingly.
There is no point in defining whole models LODs. It is better to focus on element LODs.
https://www.modelical.com/en/gdocs/level-of-development/ 22/22