Reviewing, managing, and resolving clashes with Revit and BIM Collaborate or Pro

00:00

[MUSIC PLAYING]

00:10

Hello, hello.

00:11

Thanks for joining me in this accelerator which

00:13

is about reviewing, managing, and resolving clashes

00:17

with Revit and Model Coordination.

00:19

My name is Deepak Maini.

00:21

Please note that this is the second accelerator

00:23

in this series with the first one being

00:26

run clash detection with Navisworks and Model

00:28

coordination.

00:29

So I would strongly recommend you guys watch that accelerator

00:33

before you watch this one.

00:35

All right with this, let's get started.

00:37

Just a quick introduction about me.

00:39

As I mentioned, my name is Deepak Maini

00:40

I'm the National Technical manager at CAD group Australia.

00:43

Mechanical engineer by profession,

00:45

been in the industry for over 22 years.

00:48

I'm also an Autodesk expert elite and a BIM 360

00:51

certified consultant.

00:52

Been really blessed that I get to travel around the world

00:55

and do talks at various conferences,

00:57

won a few top speaker awards as well.

00:59

Written a few books also on programs

01:01

like Navisworks, Advanced Steel and Bluebeam Revu.

01:04

Outside my full time job, I also teach at a few universities

01:07

locally within Australia and some overseas universities

01:10

as well.

01:12

All right, so quickly talking about Autodesk Accelerators

01:15

these are designed to help your team stay ahead

01:17

of the curve with the latest workflows.

01:20

There are a lot of on-demand courses

01:22

and pre-recorded coaching available on the customer

01:25

Success Hub.

01:26

You can also request Live Coaching by visiting this Hub.

01:29

So make sure you visit the Customer Success

01:32

Hub by clicking on this link or by Google searching it.

01:36

This is the Safe Harbor statement.

01:38

I leave this on the screen for a few seconds for you

01:41

to quickly read through it.

01:51

All right talking about this accelerator,

01:54

this is the overview workflow for this accelerator.

01:59

And this is the detailed workflow for this accelerator.

02:02

As you can see, this accelerator is divided into three sections

02:06

and these are the detailed steps for these sections.

02:12

These are the learning objectives of this accelerator.

02:15

We're going to start with downloading and installing

02:17

Issues Add-on for Revit, because it is not available

02:20

out of the box.

02:21

We are then going to clash issues from Model Coordination

02:25

module inside Revit.

02:27

And then we'll resolve those clashes inside Revit

02:30

by modifying the elements.

02:32

And lastly, we are going to review the resolved clashes

02:35

from the Model Coordination interface

02:37

and close the issues that are resolved.

02:41

This is the graphic version of the learning objectives.

02:47

Now before we get started with the accelerator,

02:50

I want to introduce the project that we are going

02:52

to use for this accelerator.

02:54

The project we are going to use is a Revit cloud

02:57

workshared project hosted on Docs.

03:00

This project is hosted on Autodesk construction cloud

03:04

not on BIM 360.

03:06

It's a multidisciplinary project with architecture, structure,

03:11

mechanical, plumbing, and electrical disciplines.

03:14

As you can see, we've got individual folders

03:16

for these disciplines.

03:19

We have used the shared folder as the Coordination space.

03:23

That's where all the models are automatically copied

03:26

when we share the packages.

03:27

And we can see the automated clash tests on those models.

03:33

Now, I want to repeat this again,

03:35

the workflow shown in this accelerator

03:37

is also valid for manually uploading Revit files.

03:40

The only thing is that in that case,

03:42

you'll have to manually go and select the folders

03:44

where you're copying the Revit files

03:46

as your Coordination spaces.

03:48

So please be mindful of that.

03:51

The project that we are going to use for this accelerator

03:54

is a Revit cloud workshared multidisciplinary project.

03:60

We've got the architecture, structure, mechanical,

04:03

plumbing, and electrical teams in this project.

04:06

Each of these teams have their own models

04:09

in their team folders.

04:12

And because it's a multidisciplinary project,

04:15

we are going to use the design collaboration module

04:18

to share and consume packages.

04:21

So if I jump over to the design collaboration window.

04:25

We've got all these teams here, and you can see in these teams

04:28

Swim Lanes we've got all these packages that we

04:31

have been regularly sharing and consuming on this project.

04:37

The next thing which is really important, is the shared folder

04:40

here is selected as our coordination space.

04:45

Which means that all the models that

04:47

are copied in the shared folder as part of sharing packages

04:51

would automatically be selected for automated clash detection.

04:56

And this is the best part of this workflow, where as soon

04:59

as any team shares a package the Model Coordination

05:03

Module will show us clashes with those shared models.

05:08

Now having mentioned that, let me also

05:11

say that the workflow that I'm going

05:12

to show in this accelerator is also

05:15

valid for any other project which is not

05:17

design collaboration related.

05:19

Meaning a project where you can select any folder

05:22

as your coordination space and then

05:25

manually upload files in the coordination space

05:28

or sub-folders inside the coordination space.

05:31

The workflow shown in this accelerator

05:33

will still be valid.

05:36

Let's now also take a look at the issues that are already

05:39

created in this project.

05:41

These issues were created in the previous accelerator which

05:45

was run clash detection with Navisworks and Model

05:48

Coordination.

05:49

And that's why I mentioned that it is important for you

05:51

to go and review that accelerator

05:54

before you come and watch this one.

05:57

We can see that there are some issues listed as coordination

05:59

issues, and then there are some issues listed as clash issues.

06:04

The coordination issues are the issues

06:07

that were created from Navisworks clash tests.

06:10

So for example, if I click on issue number 15,

06:13

which is a coordination issue, I can see the details here.

06:18

And if I scroll down, I can also see this screenshot.

06:21

So this issue was created from the clash test in Navisworks.

06:27

Similarly if I click on the issue number 13.

06:31

That's also a coordination issue,

06:33

which was created from Navisworks clash tests.

06:36

Now all these clash issues were created from the Model

06:40

Coordination environment.

06:42

If I click on issue number 11, I can see the details here.

06:46

And if I scroll down, I can see the screenshot here.

06:49

This issue was created from the Model Coordination environment.

06:54

So just a quick reminder, the issues

06:57

that have Type set as coordination issues

06:60

are the ones that were created from Navisworks clash tests.

07:04

The issues that have the Type set to clash,

07:08

were the issues that were created in the Model

07:10

Coordination environment.

07:12

In this accelerator, we are going

07:14

to download all these issues inside Navisworks

07:17

so we can resolve the issues created from Navisworks

07:20

as well as the Model Coordination environment.

07:24

All right, so we are now ready to look at this accelerator.

07:27

The first section, is to access the motor coordination issues

07:31

inside Revit.

07:33

These are the detailed workflow steps for this section.

07:38

In the first step, we are going to download the issues add-on.

07:42

The issues add-on is available for free for the subscription

07:46

customers.

07:47

You can download it from the Desktop app.

07:50

As you can see, it's the first one on the list.

07:53

Alternatively, they can go to the Autodesk account management

07:56

page.

07:57

And from the left when they click

07:59

on all products and services, they can scroll down to Revit.

08:03

And then when they click on View downloads for the version

08:06

that they want to download, it'll take them to this window.

08:10

On this window they can go to the Updates and Add-ons tab.

08:14

And this is where the issues add-on

08:16

is available for Revit 2020 version, Revit 2021, and Revit

08:24

From here, you can download the desired version

08:27

and then install it on your machine.

08:31

The next step is to add folders to access the issues.

08:35

Now, it's really important for us

08:36

to understand that the issues are

08:39

created on the model sitting in various folders.

08:42

So the model could be sitting in your team folder, which is

08:45

your work in progress folder.

08:47

The same model is also copied in the shared folder

08:50

when you share the packages.

08:51

And it's also copied in the consumed folders

08:54

of other disciplines when they consume the packages.

08:57

So the issues are created on this model

08:60

sitting in different folders.

09:01

The important thing for us to understand

09:03

is that there should be no issues in the consumed model,

09:06

because that is only available to that particular discipline.

09:11

The issue should either be in the work in progress folder

09:14

or in the shared folder.

09:16

A really cool thing about the issues add-on

09:18

is that it does not automatically

09:20

select all the folders.

09:22

By default, it only selects your work

09:25

in progress folder, which is your discipline folder.

09:28

And the reason is that by default, it only

09:30

shows you the design issues that are created by your own team.

09:35

But if you want to look at the coordination issues that's

09:38

where you can go and click on Load Issues

09:40

and select the other folders where this model is sitting,

09:44

so you can look at all the other issues as well.

09:47

So it's a really cool workflow available inside the Issues

09:52

plug-in.

09:53

Let's now take a look at this workflow in action.

09:57

All right, so in my case, I have now downloaded and installed

10:00

the Issues add-on on Revit 2022.

10:04

To let me now go into my ACC project.

10:07

And from the mechanical folder, I'll

10:09

open the mechanical Revit model, which

10:11

is a Revit work shared model.

10:19

So once the add-on is installed, you

10:22

will see a new tab in Revit called the Issues tab.

10:26

When I go to this Issues tab I cannot click on Manage Issues

10:30

to open the Issues window.

10:33

In my case, I've got the issues window

10:35

docked on the right side of the screen.

10:38

Now a really important thing that you need to understand

10:41

is that this model, this mechanical model,

10:44

sits in various folders in the project.

10:48

The first folder, which is the main folder in which this model

10:51

sits is this team's folder.

10:53

So the 03 mechanical folder where the cloud work sharing

10:57

was initiated.

10:59

The second folder where this model sits

11:01

is the shared folder, where this model is copied

11:05

when you share your packages.

11:08

Then this model also sits in all the consumed folders.

11:12

So if the plumbing discipline goes and consumes

11:15

the mechanical package, this model

11:17

is also copied into that folder.

11:20

Now the issues plug-in by default,

11:23

only looks at your team's folder.

11:26

Which in this case is the 03 mechanical folder.

11:29

And if there are some issues created

11:31

on the model in that folder, those

11:34

are the issues that are available by default.

11:37

In our case, we can see that there are no issues found.

11:40

That's because there are no issues created

11:43

on the mechanical model sitting in the 03 mechanical folder.

11:47

The issues that we created in the Model Coordination

11:50

space or the Navisworks program were

11:53

created on the model sitting in our coordination space, which

11:56

was the shared folder.

11:58

So the first thing that you need to do

11:59

is go and load the issues from all the folders

12:02

where the issues are created.

12:04

For that, all you need to do is click on Load Issues.

12:10

It'll now display this Load Issues window

12:12

where you would notice that by default, the part of the team

12:16

folder is selected.

12:17

Which in this case is the 03 mechanical folder.

12:21

If I resize this window, we can see

12:23

that this model is also copied in the shared folder, which

12:26

is our coordination space and there

12:28

are 10 issues on that model.

12:32

This model is also copied in the consumed folder of the 04

12:36

plumbing team and

12:39

Now ideally, there should be no issues created

12:42

in the consumed folder models, the issues

12:46

should only be in the shared folder model.

12:49

As I mentioned earlier, we can see here

12:51

that we've got 10 issues created on the model sitting

12:54

in the shared folder.

12:55

So I'm going to select the checkbox of the shared folder

12:59

and I'm going to click Open.

13:01

The program now starts to download all the 10 issues from

13:06

the shared 03 mechanical folder.

13:09

We can now see all the issues listed in the Issues window.

13:14

In the next section, we'll understand the Issues window

13:17

in detail.

13:18

The next step is the Issues window.

13:21

Now Issues window would be available

13:23

when you have downloaded the issues

13:25

add-on as I mentioned earlier.

13:27

Inside the Issues window the Navisworks

13:30

issues that means the issues that

13:32

were created using Navisworks, are displayed as coordination

13:36

issues, as shown here.

13:38

The issue is created from the Model Coordination environment

13:41

are displayed as clash issues, and this

13:44

is the default setting.

13:45

So by default, Navisworks issues are

13:48

displayed as coordination issues whereas, Model Coordination

13:51

issues are displayed as clash issues.

13:54

As soon as you click on any of these issues from the list

13:57

you are navigated to the issue pin.

13:60

And also the element on which the issue pin was placed

14:04

is highlighted and selected.

14:06

So the whole idea is that you don't

14:07

have to worry where that element is that you need to modify,

14:10

the Issues add-on I don't take you to that element

14:13

automatically.

14:15

Also, it selects that element so you can make changes to it.

14:18

Let's now take a look at the Issues window in detail.

14:22

Once you have downloaded the Issues,

14:24

the first thing you will notice are these issue pins

14:28

displayed on the model.

14:30

Now you can access any issue by simply clicking on the issue

14:33

pin, or you can go to the issues panel

14:36

and you can click on an issue to access that.

14:39

So for example, in my case, I'm going

14:40

to click on issue number 13.

14:43

As soon as I do that, this issues add-on

14:46

now opens the 3D view on which that issue was created,

14:50

which in this case is the clash detection view.

14:52

And also takes us to the location of that issue.

14:55

It shows us the issue from the angle on which we

14:58

place the issue pin, and it even highlights the clashing

15:02

elements.

15:03

Now if I orbit the model around I

15:05

can see that this duct is the actual clashing element

15:08

and it is highlighted.

15:10

Let me close out of this issue.

15:13

Similarly, if I go and click on any other issue,

15:15

let's say issue number 12.

15:17

The program does the same thing.

15:19

If the clash detection view was not open, it'll open that view.

15:23

It navigates to the view on which the issue was placed.

15:26

And also selects the element on which

15:28

they should pin was placed.

15:30

Let me again orbit the model so I

15:32

can see this element properly.

15:34

So that's one way of accessing the issues.

15:38

Alternatively, as I mentioned, you

15:39

can also click on the Issue pin.

15:43

So for example, in this case, if I go and click on this Issue

15:46

pin here, the program navigates me to that particular issue

15:50

and also displays that in the Issues window.

15:56

Now if you've got a large number of issues displayed

15:58

in your model and you don't want the issue pins to be displayed.

16:01

You can turn them off by clicking on the Issue pins

16:04

option.

16:08

The next thing that you would notice in the issue's window

16:11

is that we've got issues listed as coordination issues,

16:15

and then we've got issues listed as clash issues.

16:21

As I mentioned the start of the accelerator,

16:23

the coordination issues are the issues

16:26

that were created from Navisworks whereas, the clash

16:29

issues are the issues that were created from the Model

16:32

Coordination environment.

16:34

So the Issues system makes it really easy

16:37

for you to understand whether the issue was created

16:39

from the Navisworks clash test or from the Model Coordination

16:43

environment.

16:45

Now, let's say you've got a large number of issues listed

16:48

in the Issues window, for that you can use the Filter button,

16:51

to filter the issues that you want to see.

16:53

For example, in my case, I'm going

16:55

to click on the Filter button and now I

16:59

can say that I only want to see class issue type.

17:02

So from the Type list.

17:04

I can go and select Clash.

17:08

Now if I scroll down I can click Done.

17:13

Now I'm only looking at clash issues.

17:18

And to turn the filter off I can click on Filter, scroll down,

17:22

and I can go and set Reset.

17:25

Now I'm seeing all the issues here.

17:32

Finally I just want to quickly mention about this Refresh

17:35

button here.

17:36

Let's say after we have opened the model in Revit there were

17:39

some additional issues created in the Model Coordination

17:42

environment or in Navisworks.

17:44

In that case, I can click on this button

17:47

and the issues program will then download all those new issues

17:51

as well and they'll be listed in the Issues window.

17:55

In this second section, we are going

17:57

to resolve clashes inside Revit.

18:01

These are the detailed workflow steps for this section.

18:06

In this first step, we are going to edit clashing elements so we

18:10

can change the issue statuses.

18:13

It is important for you to know that

18:16

as soon as you click on an issue all

18:18

the information about that issue is displayed in the Issues

18:20

window.

18:21

What you need to do is scroll down

18:24

and look at the description section.

18:26

Because the description section will normally

18:28

have the details of what you need to do to fix this problem.

18:33

Once you have made the required changes to the element

18:36

you can then go and change the status of this issue.

18:39

So this is a really cool workflow

18:42

that I mentioned in the previous accelerator,

18:44

where from within Revit once we have modified the element

18:48

we can actually change the issue status.

18:50

And as soon as we change the issue status,

18:53

the initiator of the issue automatically

18:55

gets an email notification that the issue that they created

18:58

has been changed to whatever status you define here,

19:02

which normally would be in review.

19:04

So they get an email notification automatically.

19:07

Now, because this is a Cloud Workshared project

19:12

it is important for you to add a comment here

19:15

that the elements are updated but the changes

19:18

will be reflected in the next package share.

19:21

Because the initiator of the issue

19:24

automatically gets the notification straight

19:25

away when you change the issue status,

19:28

they also need to know that if they go and look at the model

19:31

now they may not see the changes.

19:33

They would only see the changes in the next package share.

19:37

So that's why it is important to add that comment here.

19:40

This is the most exciting part of this accelerator

19:44

where we are going to now modify elements to resolve clashes.

19:48

I'm going to scroll down in the Issues window

19:50

and let's look at issue number three

19:52

which we can see is a clash issue.

19:55

This means that this issue was created from the Model

19:58

Coordination environment.

19:60

I'm going to click on this issue.

20:02

And as you can see it now navigates me

20:04

to the clashing element and even select Start.

20:08

Now the first thing that I normally do

20:10

is I look at the description area of the Issues window

20:13

the description area was used to let

20:15

us know how much do we need to move this element by.

20:18

In this case, we need to move this ducked down by 8 inches.

20:23

Now depending on the element that you're modifying you

20:25

might want to open a plan view or a section

20:28

view or an elevation view.

20:29

In my case, I'm going to modify this duct in this 3D view

20:33

and to do that I'll simply modify

20:35

the top elevation of this duct.

20:38

I'll change this to 166 inches.

20:42

As soon as I do that, it now moves the duct down

20:44

by that value.

20:47

And now, because I have modified the element as requested,

20:50

I need to change the status of this issue.

20:53

For that, I'll click Status.

20:56

And in this case, I'm going to select In Review as the status.

21:02

As soon as I do this, the person who initiated this issue

21:06

gets a notification that this issue status is now

21:09

changed to In Review.

21:11

Now one thing that I strongly recommend

21:13

is to scroll down and add some comments here.

21:17

And in that comment we need to inform the issue creator

21:22

that we have modified the element

21:24

but they'll have to wait for the next package share

21:27

to be able to see the changes in the model.

21:30

And that's exactly what I'll mention in this comment.

21:34

Element modified, the changes will be reflected

21:37

in the next package share.

21:40

Now this is really important to mention here

21:42

because you do not want issue creator to go to the Docs

21:45

environment and then start comparing the current version

21:49

on Docs to the previous version, because it's not

21:51

going to reflect the changes.

21:53

The changes will only be reflected in the next package

21:56

share.

21:57

With this I'm going to click Submit.

22:00

So I have now modified this issue.

22:04

Let's now go to issue number four.

22:07

It navigates gets me to this element here.

22:10

And again under description they've

22:12

asked us to move this duck down by 8 inches.

22:15

I'll do the same thing here.

22:19

Once I've modified this element I'm

22:21

going to change the issue status.

22:24

And now I'll add the comment.

22:27

Duct moved the changes will be reflected in the next package

22:30

share, Submit.

22:35

Similarly, I can go to the other issues

22:37

and take action to resolve those issues as well.

22:41

Now I want to mention a really important thing here.

22:43

There are other factors also to be considered when you are

22:47

moving elements in the model.

22:49

In this case, we are not considering

22:51

those additional factors such as other services

22:53

to keep things simple.

22:56

Let's go to issue number 6.

22:58

In this case, again, we have been

22:60

asked to move the ducked down by 8 inches.

23:03

I'll go and change the value on the top elevation,

23:07

change the status, add the comment.

23:15

OK, so now that we have modified all these issues

23:18

and changed their statuses we can see even the issue pin

23:22

colors have changed.

23:24

This is a really good visual clue to us, telling us

23:27

that all these issues have their statuses changed

23:30

from Open to In Review.

23:34

The next step is to synchronize with cloud central

23:38

and publish the updated model.

23:40

Once you have finished editing the model

23:42

it needs to be synced with the cloud central.

23:45

And to do that you can simply click on the Synchronize

23:48

button.

23:49

Now after syncing you also need to make sure

23:51

that you publish the latest version of the model.

23:54

Because publishing will make this model available on Docs

23:57

for you to share the new packages.

24:00

Once we modify this Revit model we'll

24:02

have to sync it with the cloud central.

24:05

But before we do that, I strongly

24:07

recommend to turn off the display of issue pins.

24:10

And the reason is if the issue pins are turned on

24:13

in the recent files window, it shows

24:16

you all the pins displayed on the model, which means it's

24:18

very hard to preview the model.

24:21

So in my case, I'll go to the issues window

24:23

and turn off the issue push pins.

24:27

And now I'm going to sync it with the cloud central.

24:30

For that, I'll click on Synchronize and Modify settings

24:33

button on the Quick Access toolbar.

24:38

Now, I'm a big fan of adding comments in this comment field.

24:42

Because this comment can later be

24:44

reviewed if you need to restore a previous version

24:48

of the model.

24:49

In this case, we'll add a comment

24:51

to say we have modified all the ducts to resolve

24:54

the coordination and clash issues up to issue number 13.

25:00

I'll click OK.

25:03

And now it starts the process of synchronizing this model

25:06

with the cloud central and also saving a local cached copy.

25:12

With this I'm going to close out of this model.

25:16

And now on my home screen I can see here

25:19

that it says update available.

25:21

Now in a lot of cases, you might not

25:24

see this update available here.

25:25

It will show that the latest version is already published.

25:28

In that case, you can click on the Refresh button

25:31

to refresh this page.

25:33

In our case because it's already showing update available,

25:35

I'll select the model, and then I'll

25:38

click on the Publish button.

25:41

It's confirming the published process as say yep,

25:44

I want to publish the model.

25:47

Now the publishing process will ensure that the latest version

25:51

of the mechanical model is copied onto the Docs

25:54

environment as well, which means that we'll see the latest

25:57

version of the model in the '03 mechanical folder.

26:01

This will also ensure that we can then

26:02

create a package with the latest model published.

26:07

We can now see this message that the latest

26:09

model has been published.

26:11

If I quickly go to the recent files area

26:14

because we turned off the visibility of the issue pins,

26:17

we can see the model preview here.

26:20

If the issue pins were not turned off

26:22

they would be displayed like here in the plumbing model.

26:27

The last step in this section is to share packages.

26:31

Once you have published the model

26:33

you can go to the Autodesk Construction Cloud

26:35

project via web browser window, which in this case

26:39

is recommended as Chrome.

26:40

So using Chrome window, when you go and access

26:43

the project the first thing that I need

26:46

to make sure you understand is the model

26:49

should not show any spinning wheel on the left of its name.

26:52

Because if it's showing the spinning wheel that means

26:54

the model is still publishing.

26:57

Also, make sure that the version has

26:59

been updated and the last updated shows

27:02

you the latest version.

27:05

Once you are satisfied with that,

27:07

you can then go into the design collaboration module

27:10

and then share the package.

27:12

Just make sure that you see the Field box

27:14

in your swim line that will ensure that the latest

27:17

package is published.

27:20

Let's take a look at this sharing package workflow

27:22

in detail.

27:24

I'm going to click on View Online

27:26

to open the Chrome window.

27:28

This will take me direct to my project

27:31

because I do not have the project open in the Chrome

27:33

window.

27:36

Now before you go into the design collaboration

27:38

environment, I strongly recommend

27:40

going to the folder of the discipline

27:42

that you want to share the package from

27:45

and ensuring that the latest model is

27:47

ready for viewing and sharing, and that there

27:50

are no spinning wheels displayed on the model.

27:53

I'll now open the design collaboration environment

27:56

in a new tab.

27:60

And because I'm the project admin,

28:02

I can make the mechanical team as the current team.

28:06

And now this Field box here on my swim lane

28:09

shows me that the latest model has been published.

28:12

I can now share the package.

28:14

For this, I'm going to click on this Plus button

28:16

at the end of my swim lane.

28:20

I'll specify the name for my package.

28:28

I'll select the set that I want to share.

28:31

In this case, I only have got one set.

28:34

I'll select it, Save.

28:38

And now I'm ready to share this package.

28:42

I won't worry about the package description.

28:44

In this case, I'll click the Share button.

28:48

Now by sharing this package I'm ensuring that the latest

28:52

version of the mechanical model is copied from the 03

28:55

mechanical folder into the Shared folder as well.

28:60

I'll do the same thing with the plumbing model,

29:02

because the plumbing model was modified

29:04

to resolve the clashes as well.

29:09

I'll make the plumbing team as the current team.

29:14

The field box here shows me that the latest model

29:17

has been published.

29:18

I can now create the package.

29:23

I'll select the set to publish, save, and share.

29:33

This would now ensure that the latest version of the plumbing

29:36

model is also copied from the 04 plumbing folder into the Shared

29:41

folder.

29:42

Now, this would also ensure that the changes

29:45

are reflected in the Model Coordination environment.

29:48

Now having shown you this workflow where our project is

29:52

a design collaboration enabled project meaning, as soon as we

29:56

shared the packages the models in our shared folder, which

29:60

is our coordination space will be updated,

30:03

let's take an example of a project which is not a design

30:07

collaboration enabled project.

30:09

In that case, once the models have been modified

30:12

you'll have to manually upload the updated files

30:14

in the coordination space.

30:16

Which means that the versions of the model in your coordination

30:19

space will be updated and then you'll

30:21

be able to see the changes in the Model Coordination

30:24

environment.

30:24

So please, be mindful of this.

30:26

If the project is not a design collaboration

30:29

enabled project you'll have to manually upload

30:32

the updated files in the coordination space.

30:36

We are now at the last section of this accelerator which

30:39

is reviewing resolved clashes and motor coordination

30:42

and closing the resolved issues.

30:45

These are the detailed workflow steps for this section.

30:50

In the first step, we are going to review

30:52

the updated issue in the Model Coordination environment.

30:56

So in the Model Coordination environment

30:57

before you do anything, make sure you look at the top right

31:02

and it should show the last clash check

31:05

after the packages were shared.

31:07

Because if this shows before the packages were shared,

31:10

that means it has not run the latest clash test yet.

31:13

So make sure it shows the last clash check

31:16

after the packages were shared.

31:18

Once you are satisfied with that,

31:20

you can go to the clashes tool and click on the Assigned tab.

31:25

Let's take a look at this workflow in detail.

31:28

Before you go to the Model Coordination environment,

31:31

one thing that I strongly recommend

31:33

is go to the Shared folder, and then

31:37

go to the folder of the package that you recently shared.

31:41

Make a note of the time when this package was shared.

31:45

Because we need to ensure that our clash tests were run

31:48

after the packages were shared.

31:51

We'll have a look at that in the Model Coordination Module,

31:54

so let's go to that module now.

31:56

I'll open the module coordination module

31:58

in a new tab.

32:05

Now in this module, the first thing we'll make sure

32:08

is that we are in the right coordination space.

32:10

And the second thing, is to ensure that the last check was

32:15

after the package was shared.

32:16

In this case, it's telling us that the last check

32:18

was today at 2:08 PM, which was after the sharing of packages.

32:24

This way I can rest assured that the models

32:26

I'm looking at in this environment

32:28

now are from the latest packages that were shared.

32:32

Now let me go to the Clashes tool.

32:36

And if I go to the Assigned tab, I'll

32:41

see all these issues listed here.

32:44

Now please note, that I do not see issue number

32:48

And the reason is because those two were Navisworks issues.

32:52

And as we discussed earlier, Navisworks issues

32:54

are not available in the Assigned tab.

32:57

To review the Navisworks issues will have

32:60

to open the Federated model.

33:01

We'll have a look at that a little later.

33:03

But in this case, I can see all the issues

33:06

have their color changed, except for issue number five.

33:09

So issue number five is still set

33:11

to orange, which means its status is open

33:14

whereas, the rest of them have their status

33:17

is changed to in review.

33:20

In this step, we are going to review clashing elements

33:23

and change their statuses.

33:25

Now as mentioned in the previous step on the Assigned tab,

33:29

you will see all the issues here.

33:31

All you need to do is click on one of the answered issues.

33:35

As soon as you do that, the program separates the models

33:39

and shows you the issue pin and the location of that issue pin.

33:44

Now if the clashing elements are displayed in model colors

33:48

as shown here, that means the issue has been resolved

33:51

the clash has been fixed.

33:53

Now you can orbit the model and do a visual check,

33:56

but you can rest assured that if the clashing elements are

33:59

displayed in model colors that means

34:01

the clash has been resolved.

34:03

In that case, you can change the issue status to closed.

34:07

And when you do that, you can also add a comment.

34:10

All the people who were involved in this issue

34:13

would get a notification that this issue has been closed.

34:17

Now when you click on the issue if the elements clashing are

34:21

still displayed in the clashing colors as you can see here,

34:24

that means the clash has not been resolved.

34:28

In that case, you can restore the Open status of this issue.

34:32

Which means that the person who changed the status to In Review

34:36

gets an email notification that the issue status has

34:39

been restored to Open.

34:40

That means the clash was not resolved.

34:44

Let's not take a look at this workflow in detail.

34:48

Let's look at the status of the clashes

34:49

that these issues are associated with.

34:52

Let's start with the issue number

34:53

two, which was a clash between a plumbing

34:56

pipe and a structural section.

34:59

Now I'm going to click on this issue here.

35:02

As soon as I do that, the program

35:04

now federates the plumbing and structural model.

35:07

Takes me to the exact view on which the issue pin was placed.

35:12

Now if the clash was resolved, it'll

35:15

show us the elements in the model color.

35:17

Which is the case here, as we can see.

35:19

We do not see the clashing red and green elements anymore,

35:23

we see the elements in the model color.

35:25

But as I mentioned earlier, it is still a good idea

35:28

to do a quick visual check to ensure that the clash has

35:32

been resolved.

35:33

Let me navigate to this view here.

35:35

And I can see yes, there's a clearance between this pipe

35:38

and the structural section.

35:43

With this, I'm pretty satisfied that this clash

35:45

has been resolved.

35:47

As a result, I can now close the issue

35:50

associated with this clash.

35:51

For that, I'm going to click on the issue status,

35:55

and I'm going to change the status to Closed.

35:58

And now I can scroll down and I can add a comment here,

36:03

reviewed the clash it is resolved.

36:07

And I can submit this now.

36:10

So the status of this issue is set to closed.

36:13

We can see that in the issue's window on the left side

36:16

of the screen as well.

36:18

Now that I'm in this model I can also

36:20

see that issue number

36:23

which is a coordination issue, meaning it was actually

36:26

created inside Navisworks.

36:28

Let me click on this issue here.

36:32

Now, because this is a Navisworks issue

36:35

we would not have seen the clashing red and green elements

36:38

anyway.

36:39

And because we have turned off the display of ghost elements

36:42

in the viewer settings we don't see other elements.

36:45

I can go into Settings now.

36:48

And I can turn on the option to ghost hidden objects.

36:53

But again, it doesn't give me any understanding

36:55

of whether this clash was resolved or not.

36:59

Now one option is, I can close this Issues window.

37:03

Now it turns on the visibility of all the elements.

37:06

In this case, I know that the clash

37:08

was with this structural section I can do a visual check.

37:14

And I can see yes, there's enough clearance.

37:16

But having said that I would personally

37:18

prefer changing the status of this issue inside Navisworks.

37:23

And that is why in one of the previous accelerators

37:26

we saved the Federated model in the NWF format.

37:29

Which means that when we open the NWF file now

37:32

it'll load all these updated models.

37:35

And when we go to this particular clash issue

37:38

we'll see that it's resolved.

37:40

Let me close out of this view now.

37:44

And back in the Assigned tab, I can

37:47

see that the color of issue number 2

37:48

is changed to gray, meaning it's a closed issue.

37:52

Let's now go to issue number 3, which

37:54

was a clash between a duct and five structural elements.

37:60

Similar to last time, when I click on the issue

38:02

it federates the mechanical and structural model,

38:05

and navigates me to the view in which the issue pin was placed.

38:10

Now in this case, I can still see

38:13

that the duct is displayed in red

38:15

and the structural element is displayed in green color.

38:18

Let's scroll down in the Issue window.

38:22

I can see this screenshot that was attached to this issue.

38:26

And in this screenshot, I can see

38:28

that initially this duct was clashing

38:31

with five structural elements.

38:34

Out of those 5 by moving the duct down,

38:37

we have resolved the clash with four structural elements,

38:40

but there's one clash still remaining.

38:43

Which means that I cannot close this issue.

38:45

I'll have to change the status of this issue back

38:47

to Open, and add the comment there.

38:53

Now what you can also do is take a screenshot of this,

38:56

and attach that as a reference to this issue.

38:59

But in my case, I'll simply change the status to open.

39:04

Which means that the project member this issue was assigned

39:07

to who changed the status to In Review,

39:09

gets a notification straight away

39:11

that the status of this issue has changed back to Open.

39:15

I can now add a comment here.

39:18

Moving the duct resolved the clash with four beams

39:22

but not with the fifth, please move it further down

39:26

by 2 inches.

39:28

And now I can click Submit.

39:32

And if you want, you can add that in the description

39:34

as well, move it further down by 2 inches.

39:41

Now because the rest of the issues

39:42

were in the same model I don't have to close out of it

39:45

I can go to the issues window on the left,

39:48

and I can go to the next issue from here.

39:50

Let's go to issue number four.

39:53

I can now see that the elements are

39:55

displayed in the model color, meaning this issue is resolved.

39:59

In this case, I can change the status of this issue

40:02

as well to Closed.

40:05

I can also add a comment here, clash resolved issue closed.

40:12

Similarly, I can go to the rest of the issues that

40:15

had their status is changed to In Review

40:17

and ensure that all the clashes are resolved.

40:20

If they are, I can change their status to Closed.

40:23

Otherwise, I can change them back to open.

40:27

Coming back to the clashes tool Assigned tab,

40:30

we can see that all these issues have their status changed

40:33

to closed because they are displayed in gray,

40:36

and we still have three active issues.

40:39

This is how the Model Coordination

40:40

Module is used to review whether the clashes are resolved

40:44

or not.

40:44

And if the clashes are resolved, this

40:46

is how we close the issues associated with those clashes.

40:51

In this last step we are going to resolve

40:53

the remaining active issues.

40:56

Now as I mentioned earlier, if there are some issues that

40:59

are not resolved meaning the clashes are not fixed,

41:02

you can then return to Revit open the cloud worksheet model

41:07

and load the issues from the shared folder.

41:09

And in that case, you can filter the issues

41:12

by open status only, that means you are only

41:16

looking at the open issues.

41:18

You can then click on those open issues

41:20

and make the suggested changes.

41:22

And finally, you can sync the model

41:25

to cloud central and also publish the latest model.

41:29

That way, you'll be able to share the packages

41:32

with the latest models and update the clashes in the Model

41:35

Coordination module.

41:36

So we need to repeat this process until the time

41:39

all the clashes are resolved.

41:42

So this is the really cool closed loop end

41:45

to end issue management process that

41:46

is available within Autodesk construction Cloud, that

41:49

lets you create issues and resolve them

41:53

without too many dramas.

41:55

Let's now take a look at this workflow in detail.

41:58

Now back in Revit, I've opened this mechanical model

42:02

and I've loaded all the issues from the shared folder.

42:06

Because I don't want to see all the closed issues,

42:09

I'm going to use this filter tool in the issues window

42:12

to filter the issues only to display open issues.

42:17

For that, I'll go to the status dropdown list

42:19

and I'll go and say Open.

42:23

Now I can scroll down and say Done.

42:26

The issue's window now filters down the issues only

42:28

to the open issues.

42:30

We can also see at the top there is a filter applied

42:33

in the Issues window.

42:34

Let me now click on issue number 3.

42:38

It takes me to this element.

42:40

In the description field, I can see

42:42

that I'm advised to move this element further down

42:45

by 2 inches.

42:46

And I can do that in the top elevation field.

42:50

I'll change this to 164 inches.

42:54

With this I can now change the status back to in review.

42:59

And as I mentioned in the previous section

43:01

the initiator of the issues notified

43:03

that the status of this issue is changed to In Review.

43:07

Again, do not forget to add the comment here saying

43:09

that the changes will be reflected in the next package

43:12

share.

43:13

I can actually copy this from here, and then Submit.

43:19

Let me close out of issue number three.

43:22

Similarly, I can go to issue number 11

43:24

and make the requested changes.

43:26

Once I've made these changes I can then

43:29

sync this model to the cloud central

43:31

and publish the latest model.

43:33

And finally, I can share the package with the latest model.

43:37

That way these changes will be reflected in the Model

43:40

Coordination environment, and the clashes

43:42

will be updated based on these changes.

43:45

So this way we can go through all these different iterations

43:48

to make sure that we have resolved all these clashes.

43:53

And this is the fantastic closed loop end

43:56

to end issues workflow that we can use from the Model

43:59

Coordination environment into Revit

44:02

and back into the Model Coordination environment

44:04

to ensure that we resolve clashes on our project.

44:08

How cool is that!

44:12

Now at the end I want to provide you

44:14

some additional information.

44:15

The first one is exporting issue report.

44:18

In a lot of cases, you may need to export issues

44:21

in a report format so you can send it

44:24

to the external stakeholders.

44:26

To do that you can go to the Docs environment

44:29

and when you click on Issues you can click on Export all.

44:34

Now you can export the report as a detailed report or a summary

44:38

report in PDF format or XLSX format.

44:43

Personally, I'm a big fan of generating a detailed PDF

44:47

report, because it includes all the screenshots that

44:50

were attached to the issues.

44:52

That gives the reviewer of the report a lot

44:54

more information than a summary report.

44:58

The other additional information I want to provide

45:00

are the limitations to the Issues Add-on.

45:03

It is actually a really good idea for you

45:05

to look at this Limitation to Issues Add-in page

45:08

on a regular basis.

45:09

Because this is where it lists all the limitations,

45:13

and also if there are any prerequisites for the issues

45:16

add-on.

45:17

There's also a lot of additional resources available

45:19

if you want to do better testing for the issues add-in.

45:23

The information is available on this slide here.

45:27

With this we are at the end of this accelerator,

45:30

let's now wrap up with a Visual Workflow.

45:34

We started with a Revit cloud shared project

45:37

where we selected the shared folder as the coordination

45:40

space.

45:41

We used the design collaboration module

45:43

to share our packages, which copied

45:46

or updated the models in the shared folder.

45:49

We then reviewed the clashes between the shared models

45:53

in the Model Coordination Module.

45:55

And the clashes that were non-problematic,

45:58

we changed them into non-issues.

46:01

But the real clashes, we actually

46:03

created issues on them in the Model Coordination environment

46:06

as well as using Navisworks in the previous accelerator.

46:11

And then in this accelerator we downloaded those issues inside

46:14

Revit it using the Issues Add-on.

46:17

We then made changes to the model

46:19

and synchronized it with the cloud central.

46:21

We then published the latest model on Docs.

46:24

And shared the packages again using the design collaboration

46:27

module.

46:28

We then reviewed those clashes again in the Model Coordination

46:31

Module.

46:32

And the clashes that were resolved we

46:34

changed their statuses to closed,

46:37

and the clashes that were not resolved we

46:40

change their statuses to open, and took them back into Revit

46:44

to resolve those clashes.

46:46

And we continued with this loop till the time we

46:48

resolved all the clashes.

46:51

So that was the Visual Workflow of this accelerator

46:54

as well as the previous accelerator.

46:58

Now on the customer Success Hub there

46:59

are a lot of other courses and learning paths available

47:02

as I mentioned at the start of this accelerator.

47:04

I would strongly recommend you guys

47:06

visit the Customer Success Hub.

47:08

And that's all we have in these two accelerators.

47:11

I hope you enjoyed both of them.

47:12

I definitely had a lot of fun.

47:15

I hope you also visit the Customer Success Hub

47:17

and take a look at a lot of other accelerators and courses

47:20

we've got available there.

47:22

With this, I'm going to sign off.

47:24

Cheers.