














Transcript
00:08
So what is this BIM
00:10
level of development?
00:11
Wait,
00:12
isn't it level of detail?
00:14
No, it's level of development.
00:17
Let's just get started with the general confusion.
00:19
When it comes to this acronym LOD,
00:22
there's two different LODs.
00:24
One is level of detail. That's the more popular assumption as to what LOD means.
00:29
And one is a level of development.
00:31
Both are LOD.
00:32
Right out of the gate, there's confusion - at
00:35
least I was confused.
00:37
I'll be honest, I get confused pretty easily.
00:39
So I'd rather you just tell me what you want me to put in the model and when you want it,
00:44
is that too much to ask?
00:47
Isn't using BIM supposed to make everything easier?
00:51
So here's the breakdown before I have a breakdown.
00:54
So what is the level of development?
00:56
The level of development is basically what needs to
00:59
be in the model at a specific milestone.
01:03
This is generally broken down by trade.
01:07
This will be consistent with the project milestones
01:09
agreed upon in the front end documentation.
01:13
This ensures that everyone stays on the same page and there's no surprises.
01:19
This is completely project specific.
01:22
Each project is going to have its own deadlines and milestones
01:26
and needs of level of development.
01:29
I like to
01:29
put these dates on everyone's calendar.
01:32
This is actually project management
01:36
level of detail.
01:38
This is what we're all more familiar with.
01:41
So what is the level of detail?
01:44
How much information is acceptable for this project?
01:47
On a scale from 100 to 501, 100 is a report or basic symbols,
01:53
calling out schematic design.
01:57
Level 200 means items are modeled but they're in there as placeholders,
02:01
they're not verified.
02:02
They might not be the right size, they might be floating around the floor.
02:10
Items modeled as designed with accurate dimensions.
02:14
All systems in level 300 are to be defined.
02:18
Level 350.
02:20
Well,
02:20
that gives us 300 plus clearances such as
02:23
no fly zones around mechanical or electrical equipment,
02:27
miscellaneous metals,
02:28
meaning angle iron, uplift, bridging, stuff like that,
02:32
reinforcing in concrete
02:35
hangers and brick and black cooing.
02:37
So 350 really drills in the specifics.
02:45
to be assembled as well as manufactured off site and installed on site.
02:50
This all needs to come from the model. If you're shooting for a 400 level of detail,
02:58
It's an as built condition as well as facility management info,
03:03
which is asset information
03:05
lockout tag out
03:06
or commissioning information.
03:09
In the next few videos, we'll look at how to bring all this stuff into context.
03:14
But what I like to say is try not to overthink this stuff. To be honest,
03:19
I think there's one too many committees overthinking this stuff as it is.
00:08
So what is this BIM
00:10
level of development?
00:11
Wait,
00:12
isn't it level of detail?
00:14
No, it's level of development.
00:17
Let's just get started with the general confusion.
00:19
When it comes to this acronym LOD,
00:22
there's two different LODs.
00:24
One is level of detail. That's the more popular assumption as to what LOD means.
00:29
And one is a level of development.
00:31
Both are LOD.
00:32
Right out of the gate, there's confusion - at
00:35
least I was confused.
00:37
I'll be honest, I get confused pretty easily.
00:39
So I'd rather you just tell me what you want me to put in the model and when you want it,
00:44
is that too much to ask?
00:47
Isn't using BIM supposed to make everything easier?
00:51
So here's the breakdown before I have a breakdown.
00:54
So what is the level of development?
00:56
The level of development is basically what needs to
00:59
be in the model at a specific milestone.
01:03
This is generally broken down by trade.
01:07
This will be consistent with the project milestones
01:09
agreed upon in the front end documentation.
01:13
This ensures that everyone stays on the same page and there's no surprises.
01:19
This is completely project specific.
01:22
Each project is going to have its own deadlines and milestones
01:26
and needs of level of development.
01:29
I like to
01:29
put these dates on everyone's calendar.
01:32
This is actually project management
01:36
level of detail.
01:38
This is what we're all more familiar with.
01:41
So what is the level of detail?
01:44
How much information is acceptable for this project?
01:47
On a scale from 100 to 501, 100 is a report or basic symbols,
01:53
calling out schematic design.
01:57
Level 200 means items are modeled but they're in there as placeholders,
02:01
they're not verified.
02:02
They might not be the right size, they might be floating around the floor.
02:10
Items modeled as designed with accurate dimensions.
02:14
All systems in level 300 are to be defined.
02:18
Level 350.
02:20
Well,
02:20
that gives us 300 plus clearances such as
02:23
no fly zones around mechanical or electrical equipment,
02:27
miscellaneous metals,
02:28
meaning angle iron, uplift, bridging, stuff like that,
02:32
reinforcing in concrete
02:35
hangers and brick and black cooing.
02:37
So 350 really drills in the specifics.
02:45
to be assembled as well as manufactured off site and installed on site.
02:50
This all needs to come from the model. If you're shooting for a 400 level of detail,
02:58
It's an as built condition as well as facility management info,
03:03
which is asset information
03:05
lockout tag out
03:06
or commissioning information.
03:09
In the next few videos, we'll look at how to bring all this stuff into context.
03:14
But what I like to say is try not to overthink this stuff. To be honest,
03:19
I think there's one too many committees overthinking this stuff as it is.
Download the dataset zip file. Inside it, you should see two LOD pdf files. Open each one and review the content in there: