Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Any referenced datasets can be downloaded from "Module downloads" in the module overview.
Transcript
00:01
DEEPAK MAINI: One of the biggest requirements of a good issue
00:04
creation and management system is its ability
00:07
to close the loop.
00:09
Now, when I say close the loop, what I mean
00:11
is, the fact that we were able to action
00:15
the issues in the last objective.
00:17
Now, a good issue management system
00:19
will then let us review whether those actions actually
00:22
resolve the issues or not.
00:24
And if they have, then we are able to close the issues.
00:29
So that's what we are going to do in this objective.
00:31
We are going to review resolve clashes,
00:33
and then we are going to update the issues.
00:40
Now, if you remember in the last objective,
00:42
once we moved the elements in Revit,
00:45
we actually changed the status of the issues to answered.
00:48
When that was done, the member who initiated those issues
00:52
was notified in an email that there was
00:55
a change in the issues status.
00:57
And from there on, that member can then
00:60
review those assigned clashes in the motor coordination module.
01:04
And if those clashes are resolved,
01:07
they can then change the status of those issues
01:09
to closed, which is what I mean by closing the loop.
01:13
So let's take a look at this workflow.
01:16
As you can see, I'm in the clashes tab, assigned sub-tab,
01:21
and I can see the status of these issues changed
01:24
to answered.
01:25
Now, before I click on these issues,
01:28
it is important to have a look at the top right of this window
01:31
and ensure that the last clash check was done
01:35
after the packages were shared.
01:38
Because if this was done before the packages were shared,
01:41
then obviously, you will not see the clashes resolved.
01:45
So I can now go ahead and click on the title of Issue ID number
01:49
two.
01:50
Because I clicked on that issue in the model coordination
01:53
module, it now opens it in the context
01:56
of both the models, which means we
01:59
can see all the elements that were
02:00
clashing in the original issue.
02:04
And you can see here that the clashing elements are no more
02:08
displayed in clash colors.
02:10
Remember those red and green colors?
02:12
These elements are no more displayed in those clashing
02:15
colors, which is a visual clue telling us that the clash has
02:19
been resolved.
02:21
You can also visually check to make sure
02:23
that there's clearance between these elements.
02:28
So in this case, I'm actually satisfied that the clashes have
02:31
been resolved, and now I can go and change
02:33
the status of this issue from answered to closed.
02:38
For that, I'll click on this answered dropdown list.
02:41
I'm going to change this to closed.
02:44
I write the description here.
02:49
I'll click Done.
02:51
And now the status of this issue is changed to closed.
02:56
And I can now repeat the same thing for the other
02:58
to answer the issues as well.
02:60
If I click on this issue now--
03:03
again, these elements are no more
03:04
displayed in clashing colors, And I can change
03:08
the status of this as well.
03:12
As I'm changing the status of this issue,
03:15
the user who changed the original status from open
03:18
to answered is also notified in an email
03:21
that I've changed the status to closed, meaning
03:24
I'm happy with the resolution.
03:26
And lastly, for the third issue, which was issue number four,
03:30
we can do the same thing.
03:34
And as I mentioned earlier, the user
03:36
who changed the status of this issue from open to answered
03:39
is also notified in an email that this issue is now closed,
03:44
which again, is an important part of a good resolution
03:47
process that it keeps everybody in the loop.
03:52
Once we have changed the statuses of these three issues,
03:55
if I go back to the assigned sub-tab,
03:58
I can see the status of these issues changed to closed here.
04:03
So this is the fantastic workflow
04:05
with this model coordination module
04:08
where we can use clashes to create issues.
04:11
We can assign those issues to the individuals
04:13
who need to take actions to resolve them.
04:16
Those individuals can then change the status
04:19
of those issues after taking the action, which
04:22
means that I am then notified that the issues have
04:25
been answered.
04:26
And from there on, I can then review whether those issues
04:29
have been resolved or not.
04:31
And if they are, I can change their status to closed.
04:34
This is where the BIM 360 Model Coordination module combined
04:38
with BIM 360 Document Management module
04:41
creates this really cool issue creation and management process
04:46
that lets you close the loop.
04:49
That's the end of this course.
04:50
I hope you enjoyed it.
04:52
Make sure you try this process with a few other clashing
04:56
elements and then see how you go.
04:58
Have fun.
04:59
Cheers.
Video transcript
00:01
DEEPAK MAINI: One of the biggest requirements of a good issue
00:04
creation and management system is its ability
00:07
to close the loop.
00:09
Now, when I say close the loop, what I mean
00:11
is, the fact that we were able to action
00:15
the issues in the last objective.
00:17
Now, a good issue management system
00:19
will then let us review whether those actions actually
00:22
resolve the issues or not.
00:24
And if they have, then we are able to close the issues.
00:29
So that's what we are going to do in this objective.
00:31
We are going to review resolve clashes,
00:33
and then we are going to update the issues.
00:40
Now, if you remember in the last objective,
00:42
once we moved the elements in Revit,
00:45
we actually changed the status of the issues to answered.
00:48
When that was done, the member who initiated those issues
00:52
was notified in an email that there was
00:55
a change in the issues status.
00:57
And from there on, that member can then
00:60
review those assigned clashes in the motor coordination module.
01:04
And if those clashes are resolved,
01:07
they can then change the status of those issues
01:09
to closed, which is what I mean by closing the loop.
01:13
So let's take a look at this workflow.
01:16
As you can see, I'm in the clashes tab, assigned sub-tab,
01:21
and I can see the status of these issues changed
01:24
to answered.
01:25
Now, before I click on these issues,
01:28
it is important to have a look at the top right of this window
01:31
and ensure that the last clash check was done
01:35
after the packages were shared.
01:38
Because if this was done before the packages were shared,
01:41
then obviously, you will not see the clashes resolved.
01:45
So I can now go ahead and click on the title of Issue ID number
01:49
two.
01:50
Because I clicked on that issue in the model coordination
01:53
module, it now opens it in the context
01:56
of both the models, which means we
01:59
can see all the elements that were
02:00
clashing in the original issue.
02:04
And you can see here that the clashing elements are no more
02:08
displayed in clash colors.
02:10
Remember those red and green colors?
02:12
These elements are no more displayed in those clashing
02:15
colors, which is a visual clue telling us that the clash has
02:19
been resolved.
02:21
You can also visually check to make sure
02:23
that there's clearance between these elements.
02:28
So in this case, I'm actually satisfied that the clashes have
02:31
been resolved, and now I can go and change
02:33
the status of this issue from answered to closed.
02:38
For that, I'll click on this answered dropdown list.
02:41
I'm going to change this to closed.
02:44
I write the description here.
02:49
I'll click Done.
02:51
And now the status of this issue is changed to closed.
02:56
And I can now repeat the same thing for the other
02:58
to answer the issues as well.
02:60
If I click on this issue now--
03:03
again, these elements are no more
03:04
displayed in clashing colors, And I can change
03:08
the status of this as well.
03:12
As I'm changing the status of this issue,
03:15
the user who changed the original status from open
03:18
to answered is also notified in an email
03:21
that I've changed the status to closed, meaning
03:24
I'm happy with the resolution.
03:26
And lastly, for the third issue, which was issue number four,
03:30
we can do the same thing.
03:34
And as I mentioned earlier, the user
03:36
who changed the status of this issue from open to answered
03:39
is also notified in an email that this issue is now closed,
03:44
which again, is an important part of a good resolution
03:47
process that it keeps everybody in the loop.
03:52
Once we have changed the statuses of these three issues,
03:55
if I go back to the assigned sub-tab,
03:58
I can see the status of these issues changed to closed here.
04:03
So this is the fantastic workflow
04:05
with this model coordination module
04:08
where we can use clashes to create issues.
04:11
We can assign those issues to the individuals
04:13
who need to take actions to resolve them.
04:16
Those individuals can then change the status
04:19
of those issues after taking the action, which
04:22
means that I am then notified that the issues have
04:25
been answered.
04:26
And from there on, I can then review whether those issues
04:29
have been resolved or not.
04:31
And if they are, I can change their status to closed.
04:34
This is where the BIM 360 Model Coordination module combined
04:38
with BIM 360 Document Management module
04:41
creates this really cool issue creation and management process
04:46
that lets you close the loop.
04:49
That's the end of this course.
04:50
I hope you enjoyed it.
04:52
Make sure you try this process with a few other clashing
04:56
elements and then see how you go.
04:58
Have fun.
04:59
Cheers.
Try it: Review Resolved 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.