- Who knew it would take that long,
just to get a simple definition of BIM.
I think it's that I,
that information portion of Building Information Modeling
that makes it complex, so that's what we'll look at now.
That level of embedded information,
is what can really make one model look very different,
from another model.
A Building Information Model,
can contain as much or as little information,
as the team chooses to include.
This brings up an important concept
that I touched on in the last video of the team.
Remember, Bentley systems stated that in BIM,
better project outcomes are achieved,
through a complete flow of information among applications,
and across distributed project teams for greater accuracy,
across the entire supply chain.
Now, to me, in order to accomplish this,
the ideal situation on a project,
would be to have one model.
That one model is the repository of data and information
for the entire structure or facility,
and all of the project team members,
would contribute to that one model,
increasing its functionality and its size.
Ideally, there would not be multiple models.
We should not have one model created by the architect,
and another created by the mechanical contractor.
In many ways, I think that defeats the purpose,
yet, that's not uncommon to see.
The architect creates a model because,
that's how many architects are creating their designs,
as three 3D virtual models.
They'll include all their architectural details,
and then they'll use that model,
to generate the two dimensional construction drawings,
that we use out in the field during the building phase.
However, they won't always share that model with the trades,
like the mechanical contractor.
Many of whom also use three dimensional modeling,
to design their often complex installations of piping,
ducting and wiring,
to make sure that everything fits properly without clashes,
with other building fixtures.
All of a sudden, we end up with multiple models,
each one containing different pieces of information,
and making the overall model,
less useful as a tool to manage construction.
Now, I'll talk about how to manage that in a little while,
for now, let's stay focused on that information.
I'll come back to who puts it there, in just a little bit.
The information itself is one of the things,
that makes a Building Information Model different,
from just a three dimensional digital representation
of the building.
So, for example, if I had any artistic ability,
I could probably go in and draw a virtual building in 3D,
using any number of different drawing tools.
I could use this to walk through and visualize,
a three dimensional representation of something,
so that I can get a better visual feel,
for how it would look,
as opposed to creating a two dimensional model,
where it's just harder to visualize,
what things will really look like on a page.
The difference between this simple three dimensional model,
and a Building Information Model,
which is also in 3D,
is the information that each one contains.
So, my 3D model is really just shapes,
it doesn't contain any data or information.
There isn't enough here to build from.
A true Building Information Model,
is not just shapes,
it's made up of the actual parts and pieces and components,
that we'll use to build the structure.
That's what makes it so useful in design, construction,
operation and even maintenance.
The designer can create in 3D,
using the actual components that will be used in real life.
The model will then assemble all these components,
just like we will in the field in real life.
So, the designer can see how it all goes together,
and how the finished assemblies will actually look.
Each individual component is detailed and dimensioned.
Pipes are not just lines on a drawing,
they're pipes with a specific diameter
and a specific wall thickness.
When you place a pipe into a building model,
it occupies space in three dimensions,
you can rotate the model and make sure it actually fits.
This is where the promise
of improving the construction process really comes in.
Used properly, I should be able
to use a Building Information Model,
to make sure everything as designed, will actually fit,
that it's constructable.
I should be able to identify any clashes,
before we go out to the field.
It should also eliminate or at least drastically reduce,
the instances where the architect does a sidewalk,
and doesn't like the way an assembly looks.
In the old way of designing,
an assembly would just be shown as lines on a page,
with notes about the hardware to be used.
Until it was actually built,
or someone did a mark-up with the actual hardware,
It would be difficult for most people to visualize,
how it was actually going to look.
Using BIM, I can instead build
a three dimensional virtual model of this,
using the actual hardware and the components
that we'll use in the field.
Now, I get a 3D model I can look at,
but it's not just lines and shapes.
That model was built using virtual representations
of the components we'll use in the field.
I can click on them, and I can see what they are.
I can isolate them and view the components by themselves,
and rotate each one to see how it all comes together.
These 3D models are then detailed enough,
for the designer to use,
to create the two dimensional construction drawings,
that we want to see in the field.
This is what software like Revit does.
It allows the design team to design in 3D,
and extracts the 2D plan sheets.
But people will ask,
"Where did the data for these components come from?"
And that's the other thing
that really makes BIM pretty cool.
These components are themselves little 3D models,
like little BIM components or blocks.
Everyone from manufacturers and contractors,
can create libraries of these components,
that can be re-used in any building model.
Whether it's an architect designing a building,
or a trade contractor creating shop drawings.
The operator can select from a library of components,
and just drop them in the model,
where they're supposed to go,
creating really highly accurate and detailed,
Building Information Models,
with data that shows us visually,
what to build and how it's supposed to look,
and then data that's embedded and visible
when we click on a component,
that can tell us even more about the component,
or the fixture or the assembly.
The level of data that can be included here,
is really up to the user.
For example, for plumbing assemblies,
you could include the installation instructions,
or replacement part numbers.
Mechanical assemblies could include maintenance information
or warranty data.
In order for this information to get there though,
someone has to place it in the model.
This brings us back to my opening discussion,
of having just one model,
where all of the data is embedded and shared.
The architect can create
the original three dimensional Building Information Model,
but the trade contractors,
would really have to add to the model,
by embedding specific components,
and the detailed data from those assemblies,
that they're going to supply to the project.
Again, whether or not that happens,
and the level of detail and information included,
really depends on the specifications and the expectations,
of the stakeholders and your clients.