& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:00
DEEPAK MAINI: Welcome to the second objective
00:02
of this course.
00:03
In this objective, we are going to resolve clashes.
00:06
And we are going to action the issues in the Document
00:08
Management Module.
00:11
On a BIM 360 project which has got the Model Coordination
00:14
Module active, all the members may not necessarily
00:18
have access to that module.
00:20
And if those members have been assigned issues,
00:23
and they need to action the issues,
00:25
they can access those issues from the Document Management
00:27
Module as well.
00:29
The important thing to remember here
00:31
is that those members who need to action the issues,
00:35
need to have a minimum of view only permission to the folder
00:39
where the models are sitting.
00:40
Otherwise, they will not be able to access the models.
00:43
They'll be able to view the issues,
00:45
but not access the models.
00:48
The second thing to remember is that when
00:50
you look at an issue from the Model Coordination Module,
00:54
you will be able to view the clash in context
00:56
of both the models.
00:58
However, when you look at the issue from the Document
01:01
Management Module, you only look at a particular model,
01:06
which means that the issue is displayed
01:08
in the context of that model only, not in context
01:12
of a federated model.
01:14
So please keep that in mind.
01:16
Now the fantastic feature of the issues
01:19
created using the Model Coordination
01:20
Module is that the element IDs are automatically
01:24
included in the issues, which means that even though you are
01:28
looking at the issues in the Document Management Module,
01:31
you can still see the element IDs of the clashing
01:34
elements, which means that you can easily
01:36
access those elements in programs like Revit.
01:39
So let's now have a look at this workflow.
01:41
Right now I'm on the Model Coordination
01:43
Module, Clashes tab.
01:46
And on the Assigned subtab, I'm looking at the issues.
01:49
If I click on the title of the issue that has ID number 2,
01:54
it now opens this issue, and I'll
01:56
be able to view the clash in context of the federated model.
02:02
Let me now jump over to the Firefox window.
02:06
In this Firefox window, I'm logged
02:08
in as this user who does not have access to the Model
02:11
Coordination Module.
02:13
So if I click on the Module Selector on the top left,
02:17
I do not see the Model Coordination Module here.
02:19
However this user can access the issues assigned to him
02:24
by going to the Issues tab.
02:28
Now I'm looking at these issues here
02:30
in the Document Management Module, which
02:32
means that if I click on any of these issues,
02:34
I would be able to review the issues.
02:37
I would also be able to access the information of the issues.
02:40
But when I click on the linked document here,
02:43
it would show me the clash in context of this model only.
02:48
And this is where if I go to the Attachments tab,
02:52
I can see the screenshot.
02:54
The screenshot was automatically created
02:56
when the issue was created in the Model Coordination Module.
02:59
So this gives me the context of this clash with respect
03:02
to the other elements as well.
03:05
Now going back to the Details tab,
03:08
when I click on this linked document,
03:10
it would open the issue but, as I mentioned earlier,
03:12
in context of this model only.
03:19
And this is where if I scroll down,
03:22
I can look at the ID of all these clashing elements, which
03:25
means that I can access these easily in programs like Revit.
03:29
Let's now switch over to Revit and resolve the clashes
03:32
using these element IDs.
03:35
It is also a good time to mention here
03:37
that this MEP file has the structure model as a link.
03:42
However, none of the 3D views that we
03:44
used for automated clashes in the Model Coordination Module
03:48
have this link model turned on.
03:51
Otherwise, the linked elements would also
03:53
be included in the clash detection.
03:56
In this case, it's not a complicated model,
03:58
and we know the elements that we need to modify.
04:01
But in case of complicated models,
04:03
we can use the element IDs.
04:05
I'll go to the Manage tab, and on the Inquiry panel
04:09
I'll click on Select by ID.
04:13
And the ID that we are going to use in this case is 924961.
04:18
I'm going to click on Show.
04:21
It now navigates me exactly to the selected element.
04:25
Now a little tip here.
04:27
If you are selecting elements and you
04:28
need to navigate to them, you could also simply
04:31
click on your View cube, and it will navigate you
04:33
to those selected elements.
04:39
In my case, I'm going to pick all these elements in this row,
04:43
and in the issue we were told that we need
04:45
to move them down by 1 feet 6".
04:47
So I'm going to change the elevation level, to 10 feet
04:51
Similarly I'm going to move these elements as well,
04:55
these need to be moved by 10 inches.
04:58
I'll take them to 11 feet 6".
05:02
And lastly these elements here, these
05:05
need to be moved by 2 inches.
05:08
So I'm going to change them to 12 feet 2".
05:12
So in this case, I've actually addressed all the three issues
05:15
that were assigned to me.
05:18
Once I've done that, I'm going to sync this model.
05:25
And we have to go through the process
05:27
of now publishing this model, and also sharing the package.
05:31
Just to refresh this model so I'm able to publish it.
05:37
As this model is being published,
05:39
I'm going to switch over to the Firefox window
05:41
and change the status of the issues that
05:44
were assigned to me.
05:46
So in this case, I'm going to click on this open dropdown
05:49
list and change the status of this to Answered.
05:53
I'll add the description here that we have moved the elements
05:55
down, and you'll see the changes in the next package share.
05:60
We'll do the same thing for the other two issues as well.
06:06
Now, the other brilliant feature of this issue creation
06:10
and management system, is after I
06:12
change the status of these issues, the person who
06:16
originally created these issues would automatically
06:19
get an email that the issue status have been changed.
06:23
Now you need to action those issues.
06:27
So this is how we action these issues
06:30
in the Document Management Interface, which
06:32
was one of the main tasks of this objective.
06:37
Let's now go and share the package with the updated model,
06:40
using their Design Collaboration Module.
06:45
The square box on my team's swim lane
06:47
tells me that the latest model was published,
06:49
and now I'm ready to create and share the package.
06:52
I normally call my package weekly share,
06:55
so that way we know that these are weekly shares.
06:57
I'll make sure that I picked my published set,
06:59
and I'll hit Save.
07:02
I can now share the package.
07:05
I'll click Share here.
07:07
Now this is where BIM 360 Design is absolutely amazing.
07:11
As soon as we share the package, the updated model
07:14
is automatically copied in the shared folder.
07:16
And that was one of the reasons we used shared folder as one
07:19
of our coordination spaces, so we can straight away
07:22
see changes in the model once we share the new packages.
07:26
And that's all we have in this objective.
07:29
In the next objective, we are going
07:31
to review these issues in the Model Coordination Module,
07:34
we are going to check if the clashes are resolved,
07:37
and if they are, then we are going
07:39
to change the status of these issues to closed.
07:41
See you in the next objective.
07:43
Cheers.
Video transcript
00:00
DEEPAK MAINI: Welcome to the second objective
00:02
of this course.
00:03
In this objective, we are going to resolve clashes.
00:06
And we are going to action the issues in the Document
00:08
Management Module.
00:11
On a BIM 360 project which has got the Model Coordination
00:14
Module active, all the members may not necessarily
00:18
have access to that module.
00:20
And if those members have been assigned issues,
00:23
and they need to action the issues,
00:25
they can access those issues from the Document Management
00:27
Module as well.
00:29
The important thing to remember here
00:31
is that those members who need to action the issues,
00:35
need to have a minimum of view only permission to the folder
00:39
where the models are sitting.
00:40
Otherwise, they will not be able to access the models.
00:43
They'll be able to view the issues,
00:45
but not access the models.
00:48
The second thing to remember is that when
00:50
you look at an issue from the Model Coordination Module,
00:54
you will be able to view the clash in context
00:56
of both the models.
00:58
However, when you look at the issue from the Document
01:01
Management Module, you only look at a particular model,
01:06
which means that the issue is displayed
01:08
in the context of that model only, not in context
01:12
of a federated model.
01:14
So please keep that in mind.
01:16
Now the fantastic feature of the issues
01:19
created using the Model Coordination
01:20
Module is that the element IDs are automatically
01:24
included in the issues, which means that even though you are
01:28
looking at the issues in the Document Management Module,
01:31
you can still see the element IDs of the clashing
01:34
elements, which means that you can easily
01:36
access those elements in programs like Revit.
01:39
So let's now have a look at this workflow.
01:41
Right now I'm on the Model Coordination
01:43
Module, Clashes tab.
01:46
And on the Assigned subtab, I'm looking at the issues.
01:49
If I click on the title of the issue that has ID number 2,
01:54
it now opens this issue, and I'll
01:56
be able to view the clash in context of the federated model.
02:02
Let me now jump over to the Firefox window.
02:06
In this Firefox window, I'm logged
02:08
in as this user who does not have access to the Model
02:11
Coordination Module.
02:13
So if I click on the Module Selector on the top left,
02:17
I do not see the Model Coordination Module here.
02:19
However this user can access the issues assigned to him
02:24
by going to the Issues tab.
02:28
Now I'm looking at these issues here
02:30
in the Document Management Module, which
02:32
means that if I click on any of these issues,
02:34
I would be able to review the issues.
02:37
I would also be able to access the information of the issues.
02:40
But when I click on the linked document here,
02:43
it would show me the clash in context of this model only.
02:48
And this is where if I go to the Attachments tab,
02:52
I can see the screenshot.
02:54
The screenshot was automatically created
02:56
when the issue was created in the Model Coordination Module.
02:59
So this gives me the context of this clash with respect
03:02
to the other elements as well.
03:05
Now going back to the Details tab,
03:08
when I click on this linked document,
03:10
it would open the issue but, as I mentioned earlier,
03:12
in context of this model only.
03:19
And this is where if I scroll down,
03:22
I can look at the ID of all these clashing elements, which
03:25
means that I can access these easily in programs like Revit.
03:29
Let's now switch over to Revit and resolve the clashes
03:32
using these element IDs.
03:35
It is also a good time to mention here
03:37
that this MEP file has the structure model as a link.
03:42
However, none of the 3D views that we
03:44
used for automated clashes in the Model Coordination Module
03:48
have this link model turned on.
03:51
Otherwise, the linked elements would also
03:53
be included in the clash detection.
03:56
In this case, it's not a complicated model,
03:58
and we know the elements that we need to modify.
04:01
But in case of complicated models,
04:03
we can use the element IDs.
04:05
I'll go to the Manage tab, and on the Inquiry panel
04:09
I'll click on Select by ID.
04:13
And the ID that we are going to use in this case is 924961.
04:18
I'm going to click on Show.
04:21
It now navigates me exactly to the selected element.
04:25
Now a little tip here.
04:27
If you are selecting elements and you
04:28
need to navigate to them, you could also simply
04:31
click on your View cube, and it will navigate you
04:33
to those selected elements.
04:39
In my case, I'm going to pick all these elements in this row,
04:43
and in the issue we were told that we need
04:45
to move them down by 1 feet 6".
04:47
So I'm going to change the elevation level, to 10 feet
04:51
Similarly I'm going to move these elements as well,
04:55
these need to be moved by 10 inches.
04:58
I'll take them to 11 feet 6".
05:02
And lastly these elements here, these
05:05
need to be moved by 2 inches.
05:08
So I'm going to change them to 12 feet 2".
05:12
So in this case, I've actually addressed all the three issues
05:15
that were assigned to me.
05:18
Once I've done that, I'm going to sync this model.
05:25
And we have to go through the process
05:27
of now publishing this model, and also sharing the package.
05:31
Just to refresh this model so I'm able to publish it.
05:37
As this model is being published,
05:39
I'm going to switch over to the Firefox window
05:41
and change the status of the issues that
05:44
were assigned to me.
05:46
So in this case, I'm going to click on this open dropdown
05:49
list and change the status of this to Answered.
05:53
I'll add the description here that we have moved the elements
05:55
down, and you'll see the changes in the next package share.
05:60
We'll do the same thing for the other two issues as well.
06:06
Now, the other brilliant feature of this issue creation
06:10
and management system, is after I
06:12
change the status of these issues, the person who
06:16
originally created these issues would automatically
06:19
get an email that the issue status have been changed.
06:23
Now you need to action those issues.
06:27
So this is how we action these issues
06:30
in the Document Management Interface, which
06:32
was one of the main tasks of this objective.
06:37
Let's now go and share the package with the updated model,
06:40
using their Design Collaboration Module.
06:45
The square box on my team's swim lane
06:47
tells me that the latest model was published,
06:49
and now I'm ready to create and share the package.
06:52
I normally call my package weekly share,
06:55
so that way we know that these are weekly shares.
06:57
I'll make sure that I picked my published set,
06:59
and I'll hit Save.
07:02
I can now share the package.
07:05
I'll click Share here.
07:07
Now this is where BIM 360 Design is absolutely amazing.
07:11
As soon as we share the package, the updated model
07:14
is automatically copied in the shared folder.
07:16
And that was one of the reasons we used shared folder as one
07:19
of our coordination spaces, so we can straight away
07:22
see changes in the model once we share the new packages.
07:26
And that's all we have in this objective.
07:29
In the next objective, we are going
07:31
to review these issues in the Model Coordination Module,
07:34
we are going to check if the clashes are resolved,
07:37
and if they are, then we are going
07:39
to change the status of these issues to closed.
07:41
See you in the next objective.
07:43
Cheers.
Try it: Resolve Clashes
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.