& 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
[MUSIC PLAYING]
00:12
Good morning, good afternoon, good evening
00:14
wherever you guys are.
00:15
Thanks for joining me in this second part
00:17
of the three-part series of accelerators,
00:20
where we are learning about BIM Collaborate Pro.
00:23
My name is Deepak Maini.
00:25
If you talk about some of the main pain points of the AC
00:28
industry, I reckon the problem with sharing the data
00:31
with the external stakeholders and also with the outside teams
00:35
will have to be right up there.
00:37
And the reason is because it's not just
00:39
about sharing the data.
00:41
It's sharing it in the right format at the right time,
00:44
and also making sure that when we share our revised
00:48
version of the data, the other teams
00:50
don't have to spend hours and hours re-linking our data.
00:54
And this is where the design collaboration
00:56
module of BIM Collaborate Pro has totally
00:59
changed the way industry works.
01:01
I would say it's a game changer.
01:03
And the reason is because it makes
01:05
the process of sharing the data so much easier,
01:08
using the packages that you can create and share
01:11
with the external stakeholders and also with the other teams.
01:14
In this accelerator, we are going
01:16
to talk about all these advanced design collaboration
01:19
features in detail.
01:20
So let's get started.
01:23
Just a quick introduction about myself.
01:25
I'm the National Technical Manager at Cadgroup Australia.
01:28
I'm a qualified mechanical engineer.
01:30
I've been in the industry for almost 22 years.
01:33
I'm also an Autodesk Expert Elite and a BIM 360
01:37
certified consultant.
01:38
I've been really privileged that I
01:40
get to travel around the world and do talks
01:42
at various conferences.
01:43
I've won several top speaker awards as well.
01:46
In addition to this, I've also written a few books
01:49
on programs such as Navisworks, Advance Steel, and Bluebeam
01:53
Revu.
01:54
Outside my full time job, I do a bit
01:56
of teaching at some universities locally in Australia and also
01:59
overseas.
02:03
Just a reminder about Autodesk accelerators,
02:06
these are designed to help you and your team
02:08
stay ahead of the curve with the latest workflows.
02:11
There are several on-demand courses
02:14
and pre-recording coaching available,
02:16
but you can also request live coaching
02:18
using the Customer Success hub.
02:23
This is a Safe Harbor statement.
02:25
I'll leave it on the screen for a few seconds.
02:32
We're going to start this accelerator with the Design
02:35
Collaboration module overview.
02:39
Now what are the benefits of the Design Collaboration module?
02:42
This module allows you to connect design teams
02:45
to improve project outcomes.
02:48
It boosts productivity and also improves project efficiency.
02:54
But most importantly, it accelerates project delivery.
02:59
Now how does the Design Collaboration module
03:02
achieve this?
03:04
It's done by controlled data exchange between the teams.
03:10
This module curates and shares packages
03:13
on a project timeline for tracking and accountability.
03:18
It facilitates model exchange and deliverable coordination
03:21
between teams.
03:22
And again, most importantly, it allows
03:25
you to review project data via the model change visualization
03:29
so you can clearly see what are the changes made
03:31
between different versions of the models.
03:35
By using the Design Collaboration module,
03:38
the project managers, design principals, and QA QC
03:42
associates can review work directly
03:44
within the Document Management module,
03:46
resulting in time and money savings.
03:49
That's because they don't have to open Revit just
03:52
to review work.
03:55
This module also creates issues to communicate
03:58
outstanding tasks within the team.
04:00
You can assign the issue to a team member
04:03
and also define a deadline for that issue
04:06
to keep the team members accountable.
04:09
The whole idea is that there is no need
04:11
to send emails that eventually get lost or forgotten.
04:16
With this module, you can also review and present
04:18
project models using virtual walkthroughs, flybys,
04:22
or 3D sections.
04:23
So basically, you can have the project visuals ready
04:26
for any ad hoc design meetings.
04:31
Now this is the overall workflow of BIM Collaborate Pro,
04:34
including Rivet cloud work sharing, design collaboration,
04:37
and so on.
04:38
This accelerator will focus on creating and sharing
04:42
packages and reviewing latest updates without opening Revit,
04:45
and also communicating issues with the team
04:48
all within the Design Collaboration module.
04:53
Let's now talk about handing of your data
04:55
to the external stakeholders, which is done via packages.
05:02
The Design Collaboration module provides each stakeholder
05:06
with a dedicated team lane.
05:09
Using these team lanes, you can review packages created
05:12
by your team, you can access packages shared by other teams
05:17
and consume their data, you can review when a Revit model was
05:22
published by your team, and you can review all Revit models
05:27
saved to a team folder.
05:31
Talking about the dedicated lane for each stakeholder,
05:35
each team gets their own team lane,
05:37
including the team supplying the IFC files.
05:41
These team lanes show when that team had shared a package
05:46
or published their Revit model to Document Management.
05:50
The icons on these team lines will dynamically
05:53
change their fill depending on the team viewing
05:56
the information.
05:59
Now talking about the active team lane,
06:01
the active team lane will always be listed at the bottom.
06:06
Each team lane can be expanded to list all Revit models saved
06:10
within the team folder.
06:12
This includes the works shared model, as well as the cloud
06:15
model.
06:18
The square icon on your team lane
06:21
represents each time a Revit model gets published
06:24
to Document Management.
06:27
Now you need to remember that project admins can switch
06:30
between teams on demand because they get access to every team.
06:36
Talking about the team lane icons,
06:40
an empty circle on another team's lane
06:43
represents a package that they shared,
06:46
but my team hasn't consumed it yet.
06:50
A filled hybrid, which is a combination of a circle
06:54
and square on another team's lane,
06:56
represents a package that my team has consumed.
07:01
A filled square on my team's lane
07:04
represents the published model as I mentioned earlier.
07:07
A filled circle on my team's lane
07:10
represents a package that my team has shared.
07:14
A dotted circle on my team's lane
07:17
represents the start of a package,
07:20
but that package has not been shared yet.
07:24
If you see an icon with a number,
07:26
that means there were multiple packages shared
07:29
within a short period of time.
07:31
You can click on that number to expand and see when
07:35
those packages were shared.
07:38
To create a new package, the current team
07:42
can click on the plus icon on the right of their team lane.
07:47
Using the Design Collaboration module,
07:49
you can also click on Issues on the left,
07:52
and you can review the issues of the current team.
07:57
These issues can also be exported to PDF or CSV files.
08:03
Clicking on Project Status, you can review the publishing
08:06
states of the current team.
08:10
Now using the Changes option, you can create watch groups.
08:14
And these watch groups are basically
08:16
used to keep a track of the model items changing.
08:19
So for example, if I need to keep a track of all the beams
08:22
and columns changing in the structure model,
08:25
I can create a new watch group to keep a track of that.
08:30
Now again, talking about the current team, when
08:34
you click Home from the left, you
08:36
can look at the sets and the models of your current team.
08:40
You can also sort and view these models and sets if you want.
08:45
And just a reminder, these sets are
08:48
created inside Revit, where we go and create published sets
08:52
and select views and sheets to be included in those published
08:55
sets.
08:58
As mentioned in the previous accelerator,
09:00
we can also publish the latest version of the model using
09:04
this interface here.
09:06
For that, all we do is click on the Update to Latest button.
09:11
This interface also lets you create a scheduled publishing
09:15
of your team.
09:17
For example, let's say if I want to publish
09:19
the model every Tuesday at 2:00 in the morning,
09:21
I can do that from this interface right here.
09:26
You can also sign up for email notifications
09:30
so that every time a team creates and shares a package,
09:33
you can receive a notification.
09:36
Now while creating the packages, you
09:39
can include one or more published sets
09:41
in those packages.
09:43
You can also include additional models.
09:46
Now these models could be cloud workshared models,
09:49
or even uploaded non-workshared Revit models.
09:53
You can even include IFC models, DWG files and so on.
09:59
In addition to those files, you can include Word documents,
10:02
Excels, PDFs, JPEGs, and so on.
10:06
Now as I mentioned earlier, the project admins
10:09
can switch between teams.
10:11
So in this case, the project admin
10:13
went and made the mechanical team as the current team.
10:18
As a result, mechanical can now go and consume packages.
10:22
For example, there's an architecture package available.
10:25
The mechanical team can click on that circle on the architecture
10:28
team line, and then consume that package.
10:32
The current team can also click on Project Model
10:35
to view a federated model where they can see their model
10:40
federated with the other models that they have
10:42
consumed from different teams.
10:46
And in that federated view, you can also
10:48
control the visibility of the models.
10:50
You can even display the models using color theming.
10:55
Let's now take a look at the demonstration
10:57
of creating, sharing, and consuming packages.
11:02
All right.
11:03
So here I am in the Chrome window.
11:06
I'm currently logged in as the project admin.
11:09
And because I'm the project admin,
11:11
I've got access to all the teams' work in progress folders
11:14
as you can see here.
11:16
Also, notice in the Architecture folder,
11:19
I've got the Hospital Architecture model which
11:21
is a cloud workshared model.
11:23
Then I have got the standalone house here, the Revit file.
11:27
I also have the NWC file of that model.
11:30
And I've got an Excel file here as well.
11:33
Now let me go into the Design Collaboration module.
11:36
For that, I'll go into Document Management on the top left.
11:39
And normally I prefer opening this module in a new tab.
11:44
So that's how the Design Collaboration
11:46
module looks like by default.
11:48
The first thing I'm going to do is click on these three dots
11:50
here, and then click on this arrow to look at all the teams.
11:55
Right now structure team is the current team.
11:59
And that's why I'm looking at the information
12:01
about the structure team here.
12:04
I can also see that the structure team shared
12:06
a couple of packages within a short duration of time
12:09
I can click on this note here to look at more information
12:13
Also notice these blank circles in all these other team
12:17
lines that's because the structure team has not
12:20
consumed packages from any of these teams
12:23
Also notice that there are no packages created
12:26
by the architecture team and that's
12:28
what we're going to do now.
12:29
As a project admin, I can click on the architecture team name
12:33
to make the architecture team as the current team.
12:37
Now I can see that the architecture team had already
12:40
published the model on this date here.
12:43
To make sure that I'm using the right information,
12:45
I can actually click on Update to Latest here.
12:48
The program will go and check if there
12:51
are updated sets available.
12:53
In this case, it's telling me that there are no new sets
12:55
to update.
12:56
I'll click OK.
12:58
Now if I click on this arrow of the architecture team,
13:01
I can see that there are two Revit models--
13:04
the cloud workshared architecture model here
13:07
and the cloud model here.
13:10
I can also see the models and sets in the architecture team.
13:15
The sheet and the 3D view are also available in these sets.
13:20
Now as I mentioned earlier, I can create a schedule
13:23
publish for this team.
13:24
For that, I'll click on Schedule Publish.
13:28
I'll say every Tuesday morning at 2:00 AM I want the models
13:34
from this team to be published.
13:35
So I'll click on Schedule Publish.
13:39
This means that from here on every Tuesday morning
13:41
at 2:00 AM, the architecture models
13:43
will be published to Document Management.
13:47
I can also review the email notification settings
13:49
right now.
13:50
So if I click on Email Notifications,
13:52
I can click on this option here to receive an email every time
13:55
a package is shared and consumed.
13:58
I don't want to do this right now,
13:60
so I'm going to leave it turned off.
14:02
Let's now talk about creating a package.
14:05
To create the package I'll click on this plus sign
14:08
here at the end of my team's lane.
14:13
The first thing I'm going to do is rename this package.
14:16
I'm going to call this zero one architecture weekly share,
14:20
and enter.
14:22
Now if I expand sets, the cloud workshared
14:27
model had two published sets-- architecture share,
14:30
which has got two 3D views, and the A100 series, which
14:35
has four sheets.
14:37
I'm going to select both of these.
14:40
Now I can also go and select the cloud model.
14:42
In this case, I'm not going to do it.
14:44
Under models, I can select the cloud model from here as well.
14:51
Now if I go into documents, I can add supporting documents
14:54
with my package share.
14:56
For that, I'll click on Add Documents.
14:60
And from the architecture team folder
15:02
I'll select the Excel file, and I'll also select the NWC file.
15:08
I'll click Add.
15:09
So now this is all the information added to package.
15:13
I'll click Save.
15:16
So as soon as I click Save, the package is saved.
15:20
If I do not share the package right now,
15:22
it would appear as a dotted circle in my team lane.
15:27
In this case, I'm going to go and say Share.
15:30
It'll ask me to confirm if I want to share package.
15:33
I'll say, yes, I definitely want to share the architecture
15:36
package.
15:37
So that, now, is the architecture package shared.
15:42
I can see that as a filled circle in my team's lane.
15:47
Now I'm going to jump over to the Firefox window
15:51
and show you the workflow from one of the other teams.
15:55
This is the Firefox window, and I'm currently logged
15:58
in as mechanical team lead.
16:01
As you can see, I only have access
16:03
to the mechanical folder.
16:05
I'll now go into the Design Collaboration module.
16:09
Let me click on these three dots and the arrow again.
16:11
Now because I only have access to the mechanical team,
16:15
I cannot make any other team current.
16:18
That can only be done by the project
16:20
admins or the members that have got access to multiple teams.
16:25
Now from my mechanical team folder,
16:27
I can see that there's an architecture package available.
16:31
I'm going to click on this architecture package.
16:34
Now before I consume it, I can click Explore.
16:38
If I had already consumed this package,
16:40
I could also go and compare it with the previous version.
16:43
We are going to talk about this in detail later on.
16:47
I can see that this package comes
16:50
with two sets, so architecture share and A100
16:54
series, which has got two
16:59
There's only one model, and there
17:01
are two additional documents.
17:04
Before I consume this package I can actually click Explore.
17:11
It now opens this architecture model.
17:14
If I go under sets, I can look at the sheets
17:17
in this A100 series set as well.
17:21
In this case, I'm happy with this.
17:23
So I'm going to click Consume.
17:26
As soon as I click Consume, this architecture model
17:30
is copied from the shared folder straight
17:33
into the mechanical teams consumed folder.
17:36
If I just quickly jump over to the Document Management window
17:39
to show you that.
17:40
So in the zero three mechanical, if I expand under consumed,
17:44
I now also have the architecture folder here.
17:48
And in this architecture folder, I
17:50
can see I've got the Revit file of the architecture cloud
17:53
workshared model, plus I also have the Excel and NWC files.
17:58
How cool is this?
18:01
Going back into Design Collaboration,
18:04
let me click on Home.
18:07
I can now go and click on Project Model.
18:11
The Project Model option lets me look at the federated models.
18:14
At this stage it has federated my model,
18:17
which is a mechanical model, and the two models that I consumed,
18:21
which are architecture and structure.
18:23
I can turn off the visibility of any of these models
18:26
to review only the selected models.
18:30
I can also review these models based on the color theming.
18:35
So if I click on this option here,
18:37
it uses my team's color to display my content.
18:42
Similarly, if I click on zero two structure color theming,
18:45
it now uses the structure team's color
18:48
to display the content of the structure team.
18:50
Again, how cool is this?
18:54
Let me now close out of this.
18:56
If I click on Issues on the left,
18:59
currently my team does not have any issues.
19:02
That's why they are not listed here.
19:04
If I click on Project Status, it's
19:08
showing me all the publishing states of my team.
19:11
Similarly, if I click on Changes,
19:13
I can create watch groups to keep
19:15
a track of changing in different elements of different models.
19:19
We are going to talk about this in detail later on.
19:23
And that's the demonstration about creating, sharing,
19:26
and consuming packages.
19:28
Let's now switch back to the slide deck.
19:32
All right.
19:33
So the next thing is reviewing model changes.
19:36
This is hands-down one of my favorite features
19:40
in this Design Collaboration module.
19:42
Using this feature, we can review
19:44
changes between the current version of the package
19:47
and the previous versions of the packages.
19:50
Let's take a look at this now.
19:54
Now to visualize changes, you can do it
19:56
while in the Project Model view, but you can also
19:60
do it using the package timeline, which is actually
20:03
what I recommend.
20:04
You can click on a package in a team's timeline,
20:07
and then you can simply click Compare.
20:11
In the Compare window, you can actually
20:13
decide to compare which versions of the packages.
20:16
And in that window, It would straightaway
20:19
tell you how many changes exist between the two packages
20:23
that you are comparing.
20:24
You can then click on Show Changes
20:26
to actually open the model and show the changes.
20:31
Now while reviewing the changes in the Compare window,
20:34
it shows you all the elements that
20:36
have been added, all the elements that
20:38
have been modified, and also all the elements that
20:41
have been deleted.
20:43
At the top, it'll also tell you which versions of the packages
20:47
are being compared.
20:49
In this interface, you'll also notice
20:50
that the elements that have not changed
20:53
are displayed as ghosted.
20:55
And all the changes are also color coded.
20:58
So elements that have been added will be displayed in green.
21:01
The elements that have been modified
21:03
will be displayed in orange.
21:05
And the elements that have been deleted
21:07
will be displayed in red.
21:10
At any point of time, you can click on any of these changed
21:13
elements.
21:13
And in the Object Change window it
21:15
will show you all the information
21:17
about what the changes are.
21:19
In this window, you can also click on the current version
21:22
or the previous version to review how these elements look
21:25
in the current version, or how they
21:27
look in the previous version.
21:31
Let's now take a look at the demonstration of this.
21:34
And for that, I'll jump over to the Firefox window.
21:38
All right, so here I am in the Firefox window.
21:41
If you look at the structure team lane,
21:44
there was a package shared on this date here.
21:48
There's also a package shared recently.
21:51
So I can see that the package that was shared on this
21:54
date I actually did not consume.
21:57
And after that there was also another package shared.
21:60
Now what I'm going to do is I'm going to click on this package
22:03
here.
22:04
Just like last time, I can click Explore
22:07
to explore this package.
22:09
But in this case, I'm going to go and click Compare.
22:12
Now when I click Compare, it says, all right,
22:15
you are comparing two versions.
22:16
Tell us which versions you want to compare.
22:18
I'll say I want to compare the current package
22:21
with the first package that I actually consumed.
22:26
It's not telling me that there are a total of 98 changes.
22:30
I can click on Show Changes to have a look
22:33
at those changes in detail.
22:35
So in here it's now telling me that I'm
22:38
comparing version 3 of the package against version
22:41
one of the package.
22:43
There are 21 elements added, there are 77 elements modified,
22:48
and there are none deleted.
22:50
How cool is this?
22:54
I can navigate closer to those elements alternatively
22:58
irrespective of what view I am in.
22:60
I can go and click on any of these changes
23:02
here to review them.
23:04
So for example, if I go and expand Pile Cap Nine pile,
23:08
it's not telling me that there are 21 one of these pile caps
23:13
that have been added, there are 49 pile
23:16
caps that have been modified, and there are none deleted.
23:20
And if I go and expand these I can look
23:23
at all of these elements here.
23:25
As soon as I click on any of these elements,
23:27
I'm actually navigated to that element there.
23:31
I can also click on any of these elements on the screen.
23:34
And when I do that, it displays the Object Change window.
23:37
It's showing me all the changes that were made in the elements.
23:42
And it's also telling me that this is how this element looks
23:45
in version 3.
23:46
If I click on version
23:49
that that's how that element looked in version 1.
23:52
How cool is this?
23:55
Similarly, if I go and pick any other pile steel pipe,
24:00
it navigates me to that element here.
24:03
And again, I can see that this is
24:04
how it looks in version
24:07
and this is how it looked in version 1 of the package.
24:13
If I scroll down here, I can go into any of these elements that
24:16
have been added.
24:17
That's how it is in version 3.
24:18
And obviously it did not exist in version 1.
24:27
And this is the reason I mentioned
24:29
that this is one of my favorite features of the program.
24:33
How cool is this?
24:37
I'm going to now close out of the Compare environment.
24:41
I'm happy with this package here because it's not
24:43
affecting any of my work.
24:45
So I'm going to go and click Consume.
24:47
It's now going to ask me to confirm if I
24:49
want to consume this package.
24:51
I'll say yes.
24:53
Now as soon as I do that, the version
24:55
of the structure model in my team's consume folder
24:59
will be automatically bumped.
25:02
If I go back to the Document Management module,
25:05
under my team's consumed structure folder,
25:09
I can see that this version is now bumped to version 2,
25:13
because that's the second package that I consumed.
25:18
And what this means is that in Revit,
25:21
as soon as I go and open my mechanical model,
25:24
I would automatically see all the latest packet changes.
25:28
I don't have to reload or re-link and so on.
25:31
And that's the best part of this Design Collaboration module
25:35
and the concept of package sharing and consuming.
25:43
In this section, we are going to understand the Aggregated
25:46
Project Model Navigation.
25:49
Using Project Model, you can review your model federated
25:52
with the models of the other teams that you have consumed.
25:56
This actually is a really cool feature,
25:58
and I cannot tell you how many times it has helped me
26:01
understand if the coordinates of the models match or not.
26:05
So even before I link them inside Revit,
26:08
in this Project Model view, when I look at the federated model,
26:12
I can see if the coordinates of the models match or not.
26:16
Also, when you're reviewing the federated models,
26:19
you can easily control the visibility of the models here.
26:22
You can even display them using the color theming, which
26:26
basically are the colors of each of these teams in the design
26:30
collaboration environment.
26:33
You can also review sets with sheets or views that
26:36
have issues created in them.
26:39
By clicking on any element, you can access their element
26:42
properties within the model viewer,
26:44
so you don't have to open Revit to do that.
26:49
You can perform different measurement types.
26:51
So you can measure in 2D or 3D.
26:53
You can measure angles and heights.
26:55
You can even snap onto the objects
26:57
while performing these measurements
26:59
so you get the accurate measurement values.
27:03
On 2D sheets, the hyperlinks are automatically
27:06
extracted for easy navigation, and you can even
27:10
place perspective views by choosing a point on the plan
27:14
and a view direction.
27:17
You can section using planes or create a section box.
27:22
Let's now take a look at the demonstration
27:25
of hypermodel navigation.
27:29
All right.
27:30
So I'm back in the Firefox window, logged
27:32
in as the mechanical team lead.
27:34
And that's my mechanical team, which is the current team.
27:38
I'm now going to click on Project Model.
27:41
And as soon as I do that, I can see the federated model
27:45
of my team model, which is the mechanical team
27:48
model, along with the architecture and structure
27:51
models.
27:52
These are the two discipline models
27:54
that have consumed as of now.
27:56
I can now orbit around the models and have a look at them.
27:60
But most importantly, as I mentioned earlier,
28:02
I can control the visibility of any of these models.
28:05
In this case, I'm going to turn off the architecture model
28:08
so I can review mechanical with structure.
28:13
I can also now display these models using color theming.
28:16
So when I click on this icon here,
28:19
it displays the mechanical discipline using my design
28:22
collaboration color theming.
28:25
Similarly, if I go and turn on this option for structure,
28:28
it now displays structure model with the design collaboration
28:31
color theming.
28:32
How cool is this?
28:37
Let me now click on Content Browser.
28:41
I can see that my mechanical model has M100 CD set,
28:45
which has got these five sheets in it.
28:48
And the mechanical share has got a couple
28:50
of sheets and some 3D views.
28:52
Let me now click on this GA plan 100 on level one.
28:58
It now opens this view so I can look at the 2D sheet here.
29:04
Let me now use this Place Me tool.
29:07
I'm going to say the location of the tool is here,
29:10
and I want to look at the model reviewing in this direction.
29:15
As soon as I do that, it now takes me to the 3D view.
29:18
It's now giving me this information on how
29:20
to navigate in this view.
29:22
I'll say, yep, I've got it.
29:23
And now as you could see, I'm looking at the 3D view
29:27
from that display.
29:31
I can use the W key on the keyboard to walk forward.
29:35
And as I'm walking forward, I can navigate around as well.
29:41
Right now I'm on level one.
29:42
If I click on this arrow here, I could go to a different level.
29:45
Let's go to level three.
29:47
And now I'm looking at this
29:52
Again pressing the W key on the keyboard, I can walk forward.
29:56
Pressing the A key I can walk left, D key right, and so on.
30:02
Let me go back to Teams.
30:06
And again, if I do not want to look at the structure model
30:08
right now, I can turn off the visibility of the structure
30:11
model so I'm only looking at my mechanical model.
30:14
How cool is this?
30:18
And again, I can simply click on this cross here
30:20
to close out of the project model.
30:23
But going back into the project model,
30:27
I turn on the visibility of the structure model,
30:31
and now I can perform different measurements using this measure
30:34
tool here.
30:35
Let me display the elements using color theming first.
30:40
I'll go measure.
30:41
I can look at my measurement settings.
30:43
Make sure the unit type is set correctly, which in this case,
30:46
I want feet and fractional inches.
30:50
Precision is 1 by 2.
30:53
And now I want to find out what's
30:54
the distance between the bottom of this slab here
30:57
and this duct.
30:59
I would also change my display type to orbit display,
31:02
rather than the other display I was in.
31:05
And now I can pick this edge of this duct.
31:08
So the program now shows me the x, y, and z values, and also
31:12
the shortest distance.
31:14
Similarly, if I go in here, and I also want to find out
31:17
what's the distance between the bottom of this beam here
31:22
and the top of this duct.
31:25
Again, the program shows me all of these values here
31:28
in the x, y, and z, as well as the shortest distance.
31:32
I'll click Done to close the measurement tool.
31:36
Just zooming out now, I can also go to the Home view.
31:41
The next thing I want to show you are the section tools.
31:44
So if I click on this Section Analysis fly out,
31:47
I can create sections on x plane, y plane, z plane,
31:52
or even a box.
31:55
I'm going to start with the z plane here.
31:57
As soon as I do that, it now sections the model.
31:60
I can use this arrow to move the section plane up and down.
32:03
I can even rotate the section plane if I want.
32:06
Similarly, if I see a section using y plane,
32:10
it now sections the model using y plane here.
32:13
And finally, I can using a box as well.
32:17
That's the box placed by default.
32:19
I can use these arrows to move the box around.
32:24
I can also click on any of these faces
32:26
here to resize that section face.
32:32
So that's the section analysis.
32:34
The whole concept of this hypermodel navigation
32:37
is for you to be able to review the models
32:40
inside this interface rather than opening Revit and then
32:44
reviewing the model there.
32:45
This makes it a lot easier, especially for non-Revit users
32:50
to access the information of the model.
32:52
In this case, if I go and click on any of these elements,
32:55
let's say if I go and click on this AHU,
32:57
I can now go into properties, and I get all the information
33:00
about this AHU right here.
33:04
Similarly, if I go and click on, let's say, this element here,
33:07
which is a supply diffuser, I can now
33:09
look at all the parameters here.
33:12
As you can see, for non-Revit users,
33:14
this is a fantastic view where they can access the model,
33:18
they can review the properties, perform measurements, section
33:21
elements, and so on.
33:24
Let me now close out of this display.
33:30
In this section, we are going to understand
33:32
how to create and review issues in the design collaboration
33:36
environment.
33:37
I'm a big fan of the issue management system
33:40
that comes with BIM 360, because it's a closed-loop issue
33:44
management system.
33:45
What that means is that you can create issues here in BIM 360.
33:50
You can then download the issues inside Revit.
33:52
You can review and fix the issues inside Revit.
33:55
And then you can change the status there in Revit as well.
33:58
And finally, in the BIM 360 environment,
34:01
you can then review those resolved issues
34:04
and change their statuses to closed.
34:08
In the design collaboration environment,
34:09
when you click on the Issues tab on the left,
34:12
you can see all the issues of the current team.
34:17
Alternatively, you can click on any of the shared packages
34:20
and review the issues associated with the packages of a team
34:24
as well.
34:25
And the really cool thing is that this
34:27
could be for your team's package or the packages shared
34:31
by other teams as well.
34:32
Just be mindful that you need to have
34:34
the right set of permissions to view those issues.
34:40
You can also access issues by clicking on the project model,
34:43
and then clicking on the Issues tab on the left.
34:48
Now as I mentioned earlier, from within the design collaboration
34:51
environment, you can also create new issues.
34:55
The issues that you create must have type, status, title,
35:00
and other fields.
35:03
The assignees and owners can be selected from the project team
35:06
members, roles, or companies.
35:09
Now remember that the owners could only
35:11
be selected from the users of the current project.
35:15
Once the issues are created, they'll
35:17
be available when you click on the Issues tab from the left.
35:22
And in the Project Model view, when
35:24
you go into the model content, the views with issues
35:27
will have a caution tag in the content browser.
35:32
You can click on any of these issues at any point of time
35:35
to review them, sort them, and filter them.
35:39
If you have the right set of permissions,
35:41
you can also edit an issue, and you can change their statuses
35:45
from within the design collaboration environment
35:47
as well.
35:48
Now one of the most important things that you need
35:50
to remember is that an existing issue cannot be deleted.
35:54
It can only be voided.
35:58
And again, one of my favorite features
35:59
in this environment related to issues
36:01
is that from within the design collaboration environment,
36:04
you can also export issues as reports.
36:07
And these reports could be in PDF format, XLSX format,
36:11
CSV format, and even BCF formats that you can then import
36:15
in some of the other programs.
36:18
Let's now take a look at the demonstration of this.
36:23
OK, so here I am back in the Firefox window, logged
36:26
in as the mechanical team lead.
36:29
Now before we talk about issues, you
36:32
need to make sure that the project admin has given you
36:35
the right set of permissions to view and create issues for you
36:39
to be able to do all of these steps
36:41
that you are going to learn in this demonstration.
36:45
On the home screen, if I click on issues here,
36:49
I can see all the issues associated
36:51
with the current team, which is my mechanical team.
36:54
It's telling me that there are three issues associated
36:57
with the mechanical team.
36:58
I can click on any of these issues to open the issue panel,
37:02
and I can review the information about the issues.
37:06
If I click on this dropdown list here,
37:09
I can change it to team work in progress issues or team package
37:13
issues.
37:14
Similarly, if I go and click on any of the existing team's
37:18
packages, I can look at the issues associated
37:21
with those packages as well.
37:24
So basically, if you have the right set of permissions
37:27
you can not only look at the issues associated
37:29
with your team, but also issues associated with the packages
37:33
of other teams as well.
37:35
Let me go back to the Home tab.
37:37
Now if I go to the project model,
37:42
and if I go to Issues on the left,
37:44
it shows the issues of my team.
37:47
I can click on any of these issues
37:49
to be navigated to that particular element on which
37:52
the issue pin was placed.
37:55
I can look at all the information about that issue
37:57
here as well.
37:59
Let's go back.
38:01
Now as I mentioned earlier, from within this environment,
38:04
I can also create new issues.
38:06
Let's say a mechanical engineer or a mechanical project lead
38:11
is reviewing the mechanical design from this environment.
38:15
As they're reviewing the design, they
38:17
notice that there's an AHU sitting right here.
38:20
Let me go back to teams and display
38:23
the model using color theming.
38:25
This AHU appears to be out of place.
38:30
In this case, I can go to the Issues panel,
38:34
and I can say Create Issue.
38:36
I'm going to place the issue pin on this issue here.
38:40
And now in this issue I can instruct
38:43
the mechanical designer to delete this AHU.
38:47
For title, I'm going to go and say delete AHU.
38:51
Assigned to, this is where I can go and assign it
38:54
to a user role or a company.
38:57
In this case, I'm going to assign it to this user here.
39:01
Due date, I'll go and say fix it by 31st.
39:07
If I had locations in my project,
39:08
I can go and define the locations here.
39:12
On location detail, I am the owner of this issue.
39:17
And the root cause is design coordination.
39:22
Under description, I can add a description here.
39:24
This AHU is out of place.
39:26
Please delete it.
39:29
And now as soon as I click Create,
39:30
this issue is created and would be
39:33
available in the list of issues for my team.
39:36
Let me close out of the project model display now.
39:40
So that was about the issues associated with my team.
39:43
Let's now talk about issues associated with another team.
39:46
In this case, we'll take the example of the plumbing team.
39:49
Plumbing team, as you can see, has already
39:52
shared two packages-- this one here on this date,
39:55
and this one here on this date.
39:58
I haven't consumed any of these packages.
40:01
If I click on the first package here,
40:04
I can see that it has three issues associated with it.
40:07
I can click on Issues here to actually see
40:09
those three issues.
40:11
There are two open issues, and there's an answered issue here.
40:16
I'm going to click on this answered issue,
40:18
and it opens the Issue window.
40:21
I can see that I am the owner of this issue.
40:24
It was assigned to this user here.
40:26
And the issue was because the coordinates of the models
40:29
do not match.
40:31
I can now look at the activity associated with this issue,
40:35
and I can see that this user actually
40:38
went and fixed the problem.
40:39
They are saying that this is already done,
40:41
and the latest package has been shared.
40:44
I can also see that they changed the status
40:46
from opened to answered.
40:48
What I'm going to do in this case is click on Explore
40:52
to explore this first package.
40:55
And I'm going to go under Teams on the left.
40:58
I'm going to turn on the visibility
40:60
of the mechanical model.
41:02
Now if I go to the home view here,
41:04
I can see that this was the problem.
41:07
The coordinates of the plumbing model
41:09
did not match the coordinates of the mechanical model.
41:12
And hence, that issue was created.
41:15
If I close out of this display, I'm
41:18
now going to go and click on the second package shared
41:21
by this team.
41:24
I'm going to go and say Explore.
41:27
And now with this one here, when I go and turn
41:30
on the mechanical model, I can see
41:32
that, yes, they have fixed the coordinates of their model.
41:36
How cool is this?
41:39
Now that I'm happy with this, I can go into the Issues panel.
41:43
I can click on this issue here, and I can go and change
41:47
the status of this issue from answered to closed.
41:50
I can add a comment here saying that the coordinates are
41:53
fixed now.
41:58
And now that I'm happy with this package here,
42:01
I can click on Consume to consume the plumbing package.
42:06
So my mechanical team now has consumed the last plumbing
42:09
package that was shared.
42:12
Going back into Issues tab on the left,
42:15
I can use the Export option to export all of these issues.
42:19
Now please note that in this case,
42:21
I am only given the option to export in the CSV and BCF
42:25
format, and the reason is because I'm
42:28
logged in as a mechanical team lead, not as a project admin.
42:33
But a project admin can also export in additional formats.
42:37
To show you this, let me switch over
42:39
to the Google Chrome window where I'm
42:41
logged in as a project admin.
42:45
All right.
42:45
So here is the Google Chrome window.
42:47
I'm logged in as the project admin.
42:50
And for the mechanical team, when
42:53
I click on the Issues tab on the left, I can go and say Export.
42:57
I can now export as PDF and XLSX as well.
43:01
Please note that these options were not available
43:04
when I was not logged in as a project admin.
43:08
So please be mindful of this.
43:11
And that's all we have in the demonstration of the Issue
43:14
Management system from the design collaboration
43:16
environment.
43:17
Let's jump over to the slide deck now.
43:23
In this section, we are going to understand watch groups.
43:27
This is one of the newer features
43:29
that was added to the design collaboration environment.
43:33
When you click on the Changes tab,
43:35
you can create a new watch group.
43:38
Watch groups are used to keep track
43:41
of changes of certain elements in your model,
43:44
or in the models of other teams.
43:47
To create a new watch group, you can click on New Watch Group.
43:51
You can then select either your team model or the model of one
43:55
of the other contributing teams.
43:57
You can then select the elements that you
43:59
want to include in the watch group,
44:01
and then define the name for that watch group.
44:05
The whole concept is next time when
44:07
there is a new package shared, the program
44:10
would automatically show you the number
44:12
of changes between the current package
44:15
and the previous package.
44:16
It'll also show you the number of elements that have changed.
44:20
You can click on that watch group name
44:22
to review the changes.
44:24
You can also click on Show Changes
44:26
to actually open the model in the design collaboration
44:29
environment, and then review the changes one by one.
44:32
Let's now take a look at the demonstration
44:34
of creating watch groups.
44:39
All right.
44:39
So I'm back in the Firefox window, logged
44:42
in as the mechanical team lead.
44:45
I'll now click on the Changes tab,
44:47
and then click on New Watch Group
44:49
to create a new watch group.
44:51
As you can see, I can select my team model,
44:55
or I can select the models of the other contributing teams.
44:59
In this case, I want to select the structure model.
45:02
The reason I want to keep a track of the elements
45:04
in the structure model is because I've
45:06
used some references of some beams and columns
45:09
to place the duct work.
45:11
For this, I'm going to click on Structure Model here.
45:16
Next.
45:18
And now I can expand the structure model
45:21
and select the elements I want to keep track of.
45:23
In my case, I want to keep track of the changes
45:27
in the structural columns, as well as beams,
45:31
which are structural framing.
45:33
I'll go and click Next now.
45:37
I'll go and specify the name for this watch group, beams
45:40
and columns.
45:42
And now I'm going to simply click on Save.
45:46
Once I've saved this watch group.
45:49
I can now straightaway see that between the last package
45:52
and the current package, there are 21 changes.
45:56
Six columns have changed, and 15 beams have changed.
46:04
Now let's assume the structure team
46:07
has published their new model and also shared
46:11
a brand new package.
46:14
So in this case, the watch group is telling me
46:16
that there are a total of 252 changes.
46:21
I can expand the watch group and get some more details
46:24
of how many columns have changed and how many beams
46:28
have changed.
46:29
If I click on the watch group name,
46:31
I can actually see that I'm comparing
46:34
this version, which is the version 4 package,
46:37
against version 3.
46:39
If I go and say compare it against version 2,
46:42
it'll now update and tell me how many elements have changed.
46:46
And we can see here between version 4 and version 2,
46:50
there are same number of changes, meaning the beams
46:53
and columns were not changed between version 2 and version
46:57
I can now go and say Show Changes.
47:01
The program now opens the model in this environment
47:04
here under Change Visualization.
47:07
And this view, as you can see, is very similar to the Change
47:11
Visualization view that we looked at earlier
47:13
in this accelerator.
47:14
We can expand these elements, and we can
47:17
look at what the changes are.
47:19
How cool are these watch groups?
47:24
Let me close out of this environment.
47:27
Now at any point of time, I can click on these three dots
47:30
here on the right of my watch group name.
47:33
I can edit this watch group, or I can delete the watch group.
47:38
And that's all we have in this demonstration of creating
47:41
and reviewing watch groups.
47:44
Let me return to the slide deck.
47:47
Now again, talking about some useful links,
47:50
these are several links that you can click on
47:53
to access additional information.
47:56
And don't forget about the Enterprise Hub page as well.
48:02
And that's all we have in this second accelerator.
48:04
I hope you enjoyed learning about
48:05
these advanced collaboration features in BIM Collaborate
48:08
Pro.
48:09
In the next accelerator, which is also the last in the series,
48:12
we are going to learn about some best practices.
48:15
I'll see you there.
48:16
Cheers.
Video transcript
00:00
[MUSIC PLAYING]
00:12
Good morning, good afternoon, good evening
00:14
wherever you guys are.
00:15
Thanks for joining me in this second part
00:17
of the three-part series of accelerators,
00:20
where we are learning about BIM Collaborate Pro.
00:23
My name is Deepak Maini.
00:25
If you talk about some of the main pain points of the AC
00:28
industry, I reckon the problem with sharing the data
00:31
with the external stakeholders and also with the outside teams
00:35
will have to be right up there.
00:37
And the reason is because it's not just
00:39
about sharing the data.
00:41
It's sharing it in the right format at the right time,
00:44
and also making sure that when we share our revised
00:48
version of the data, the other teams
00:50
don't have to spend hours and hours re-linking our data.
00:54
And this is where the design collaboration
00:56
module of BIM Collaborate Pro has totally
00:59
changed the way industry works.
01:01
I would say it's a game changer.
01:03
And the reason is because it makes
01:05
the process of sharing the data so much easier,
01:08
using the packages that you can create and share
01:11
with the external stakeholders and also with the other teams.
01:14
In this accelerator, we are going
01:16
to talk about all these advanced design collaboration
01:19
features in detail.
01:20
So let's get started.
01:23
Just a quick introduction about myself.
01:25
I'm the National Technical Manager at Cadgroup Australia.
01:28
I'm a qualified mechanical engineer.
01:30
I've been in the industry for almost 22 years.
01:33
I'm also an Autodesk Expert Elite and a BIM 360
01:37
certified consultant.
01:38
I've been really privileged that I
01:40
get to travel around the world and do talks
01:42
at various conferences.
01:43
I've won several top speaker awards as well.
01:46
In addition to this, I've also written a few books
01:49
on programs such as Navisworks, Advance Steel, and Bluebeam
01:53
Revu.
01:54
Outside my full time job, I do a bit
01:56
of teaching at some universities locally in Australia and also
01:59
overseas.
02:03
Just a reminder about Autodesk accelerators,
02:06
these are designed to help you and your team
02:08
stay ahead of the curve with the latest workflows.
02:11
There are several on-demand courses
02:14
and pre-recording coaching available,
02:16
but you can also request live coaching
02:18
using the Customer Success hub.
02:23
This is a Safe Harbor statement.
02:25
I'll leave it on the screen for a few seconds.
02:32
We're going to start this accelerator with the Design
02:35
Collaboration module overview.
02:39
Now what are the benefits of the Design Collaboration module?
02:42
This module allows you to connect design teams
02:45
to improve project outcomes.
02:48
It boosts productivity and also improves project efficiency.
02:54
But most importantly, it accelerates project delivery.
02:59
Now how does the Design Collaboration module
03:02
achieve this?
03:04
It's done by controlled data exchange between the teams.
03:10
This module curates and shares packages
03:13
on a project timeline for tracking and accountability.
03:18
It facilitates model exchange and deliverable coordination
03:21
between teams.
03:22
And again, most importantly, it allows
03:25
you to review project data via the model change visualization
03:29
so you can clearly see what are the changes made
03:31
between different versions of the models.
03:35
By using the Design Collaboration module,
03:38
the project managers, design principals, and QA QC
03:42
associates can review work directly
03:44
within the Document Management module,
03:46
resulting in time and money savings.
03:49
That's because they don't have to open Revit just
03:52
to review work.
03:55
This module also creates issues to communicate
03:58
outstanding tasks within the team.
04:00
You can assign the issue to a team member
04:03
and also define a deadline for that issue
04:06
to keep the team members accountable.
04:09
The whole idea is that there is no need
04:11
to send emails that eventually get lost or forgotten.
04:16
With this module, you can also review and present
04:18
project models using virtual walkthroughs, flybys,
04:22
or 3D sections.
04:23
So basically, you can have the project visuals ready
04:26
for any ad hoc design meetings.
04:31
Now this is the overall workflow of BIM Collaborate Pro,
04:34
including Rivet cloud work sharing, design collaboration,
04:37
and so on.
04:38
This accelerator will focus on creating and sharing
04:42
packages and reviewing latest updates without opening Revit,
04:45
and also communicating issues with the team
04:48
all within the Design Collaboration module.
04:53
Let's now talk about handing of your data
04:55
to the external stakeholders, which is done via packages.
05:02
The Design Collaboration module provides each stakeholder
05:06
with a dedicated team lane.
05:09
Using these team lanes, you can review packages created
05:12
by your team, you can access packages shared by other teams
05:17
and consume their data, you can review when a Revit model was
05:22
published by your team, and you can review all Revit models
05:27
saved to a team folder.
05:31
Talking about the dedicated lane for each stakeholder,
05:35
each team gets their own team lane,
05:37
including the team supplying the IFC files.
05:41
These team lanes show when that team had shared a package
05:46
or published their Revit model to Document Management.
05:50
The icons on these team lines will dynamically
05:53
change their fill depending on the team viewing
05:56
the information.
05:59
Now talking about the active team lane,
06:01
the active team lane will always be listed at the bottom.
06:06
Each team lane can be expanded to list all Revit models saved
06:10
within the team folder.
06:12
This includes the works shared model, as well as the cloud
06:15
model.
06:18
The square icon on your team lane
06:21
represents each time a Revit model gets published
06:24
to Document Management.
06:27
Now you need to remember that project admins can switch
06:30
between teams on demand because they get access to every team.
06:36
Talking about the team lane icons,
06:40
an empty circle on another team's lane
06:43
represents a package that they shared,
06:46
but my team hasn't consumed it yet.
06:50
A filled hybrid, which is a combination of a circle
06:54
and square on another team's lane,
06:56
represents a package that my team has consumed.
07:01
A filled square on my team's lane
07:04
represents the published model as I mentioned earlier.
07:07
A filled circle on my team's lane
07:10
represents a package that my team has shared.
07:14
A dotted circle on my team's lane
07:17
represents the start of a package,
07:20
but that package has not been shared yet.
07:24
If you see an icon with a number,
07:26
that means there were multiple packages shared
07:29
within a short period of time.
07:31
You can click on that number to expand and see when
07:35
those packages were shared.
07:38
To create a new package, the current team
07:42
can click on the plus icon on the right of their team lane.
07:47
Using the Design Collaboration module,
07:49
you can also click on Issues on the left,
07:52
and you can review the issues of the current team.
07:57
These issues can also be exported to PDF or CSV files.
08:03
Clicking on Project Status, you can review the publishing
08:06
states of the current team.
08:10
Now using the Changes option, you can create watch groups.
08:14
And these watch groups are basically
08:16
used to keep a track of the model items changing.
08:19
So for example, if I need to keep a track of all the beams
08:22
and columns changing in the structure model,
08:25
I can create a new watch group to keep a track of that.
08:30
Now again, talking about the current team, when
08:34
you click Home from the left, you
08:36
can look at the sets and the models of your current team.
08:40
You can also sort and view these models and sets if you want.
08:45
And just a reminder, these sets are
08:48
created inside Revit, where we go and create published sets
08:52
and select views and sheets to be included in those published
08:55
sets.
08:58
As mentioned in the previous accelerator,
09:00
we can also publish the latest version of the model using
09:04
this interface here.
09:06
For that, all we do is click on the Update to Latest button.
09:11
This interface also lets you create a scheduled publishing
09:15
of your team.
09:17
For example, let's say if I want to publish
09:19
the model every Tuesday at 2:00 in the morning,
09:21
I can do that from this interface right here.
09:26
You can also sign up for email notifications
09:30
so that every time a team creates and shares a package,
09:33
you can receive a notification.
09:36
Now while creating the packages, you
09:39
can include one or more published sets
09:41
in those packages.
09:43
You can also include additional models.
09:46
Now these models could be cloud workshared models,
09:49
or even uploaded non-workshared Revit models.
09:53
You can even include IFC models, DWG files and so on.
09:59
In addition to those files, you can include Word documents,
10:02
Excels, PDFs, JPEGs, and so on.
10:06
Now as I mentioned earlier, the project admins
10:09
can switch between teams.
10:11
So in this case, the project admin
10:13
went and made the mechanical team as the current team.
10:18
As a result, mechanical can now go and consume packages.
10:22
For example, there's an architecture package available.
10:25
The mechanical team can click on that circle on the architecture
10:28
team line, and then consume that package.
10:32
The current team can also click on Project Model
10:35
to view a federated model where they can see their model
10:40
federated with the other models that they have
10:42
consumed from different teams.
10:46
And in that federated view, you can also
10:48
control the visibility of the models.
10:50
You can even display the models using color theming.
10:55
Let's now take a look at the demonstration
10:57
of creating, sharing, and consuming packages.
11:02
All right.
11:03
So here I am in the Chrome window.
11:06
I'm currently logged in as the project admin.
11:09
And because I'm the project admin,
11:11
I've got access to all the teams' work in progress folders
11:14
as you can see here.
11:16
Also, notice in the Architecture folder,
11:19
I've got the Hospital Architecture model which
11:21
is a cloud workshared model.
11:23
Then I have got the standalone house here, the Revit file.
11:27
I also have the NWC file of that model.
11:30
And I've got an Excel file here as well.
11:33
Now let me go into the Design Collaboration module.
11:36
For that, I'll go into Document Management on the top left.
11:39
And normally I prefer opening this module in a new tab.
11:44
So that's how the Design Collaboration
11:46
module looks like by default.
11:48
The first thing I'm going to do is click on these three dots
11:50
here, and then click on this arrow to look at all the teams.
11:55
Right now structure team is the current team.
11:59
And that's why I'm looking at the information
12:01
about the structure team here.
12:04
I can also see that the structure team shared
12:06
a couple of packages within a short duration of time
12:09
I can click on this note here to look at more information
12:13
Also notice these blank circles in all these other team
12:17
lines that's because the structure team has not
12:20
consumed packages from any of these teams
12:23
Also notice that there are no packages created
12:26
by the architecture team and that's
12:28
what we're going to do now.
12:29
As a project admin, I can click on the architecture team name
12:33
to make the architecture team as the current team.
12:37
Now I can see that the architecture team had already
12:40
published the model on this date here.
12:43
To make sure that I'm using the right information,
12:45
I can actually click on Update to Latest here.
12:48
The program will go and check if there
12:51
are updated sets available.
12:53
In this case, it's telling me that there are no new sets
12:55
to update.
12:56
I'll click OK.
12:58
Now if I click on this arrow of the architecture team,
13:01
I can see that there are two Revit models--
13:04
the cloud workshared architecture model here
13:07
and the cloud model here.
13:10
I can also see the models and sets in the architecture team.
13:15
The sheet and the 3D view are also available in these sets.
13:20
Now as I mentioned earlier, I can create a schedule
13:23
publish for this team.
13:24
For that, I'll click on Schedule Publish.
13:28
I'll say every Tuesday morning at 2:00 AM I want the models
13:34
from this team to be published.
13:35
So I'll click on Schedule Publish.
13:39
This means that from here on every Tuesday morning
13:41
at 2:00 AM, the architecture models
13:43
will be published to Document Management.
13:47
I can also review the email notification settings
13:49
right now.
13:50
So if I click on Email Notifications,
13:52
I can click on this option here to receive an email every time
13:55
a package is shared and consumed.
13:58
I don't want to do this right now,
13:60
so I'm going to leave it turned off.
14:02
Let's now talk about creating a package.
14:05
To create the package I'll click on this plus sign
14:08
here at the end of my team's lane.
14:13
The first thing I'm going to do is rename this package.
14:16
I'm going to call this zero one architecture weekly share,
14:20
and enter.
14:22
Now if I expand sets, the cloud workshared
14:27
model had two published sets-- architecture share,
14:30
which has got two 3D views, and the A100 series, which
14:35
has four sheets.
14:37
I'm going to select both of these.
14:40
Now I can also go and select the cloud model.
14:42
In this case, I'm not going to do it.
14:44
Under models, I can select the cloud model from here as well.
14:51
Now if I go into documents, I can add supporting documents
14:54
with my package share.
14:56
For that, I'll click on Add Documents.
14:60
And from the architecture team folder
15:02
I'll select the Excel file, and I'll also select the NWC file.
15:08
I'll click Add.
15:09
So now this is all the information added to package.
15:13
I'll click Save.
15:16
So as soon as I click Save, the package is saved.
15:20
If I do not share the package right now,
15:22
it would appear as a dotted circle in my team lane.
15:27
In this case, I'm going to go and say Share.
15:30
It'll ask me to confirm if I want to share package.
15:33
I'll say, yes, I definitely want to share the architecture
15:36
package.
15:37
So that, now, is the architecture package shared.
15:42
I can see that as a filled circle in my team's lane.
15:47
Now I'm going to jump over to the Firefox window
15:51
and show you the workflow from one of the other teams.
15:55
This is the Firefox window, and I'm currently logged
15:58
in as mechanical team lead.
16:01
As you can see, I only have access
16:03
to the mechanical folder.
16:05
I'll now go into the Design Collaboration module.
16:09
Let me click on these three dots and the arrow again.
16:11
Now because I only have access to the mechanical team,
16:15
I cannot make any other team current.
16:18
That can only be done by the project
16:20
admins or the members that have got access to multiple teams.
16:25
Now from my mechanical team folder,
16:27
I can see that there's an architecture package available.
16:31
I'm going to click on this architecture package.
16:34
Now before I consume it, I can click Explore.
16:38
If I had already consumed this package,
16:40
I could also go and compare it with the previous version.
16:43
We are going to talk about this in detail later on.
16:47
I can see that this package comes
16:50
with two sets, so architecture share and A100
16:54
series, which has got two
16:59
There's only one model, and there
17:01
are two additional documents.
17:04
Before I consume this package I can actually click Explore.
17:11
It now opens this architecture model.
17:14
If I go under sets, I can look at the sheets
17:17
in this A100 series set as well.
17:21
In this case, I'm happy with this.
17:23
So I'm going to click Consume.
17:26
As soon as I click Consume, this architecture model
17:30
is copied from the shared folder straight
17:33
into the mechanical teams consumed folder.
17:36
If I just quickly jump over to the Document Management window
17:39
to show you that.
17:40
So in the zero three mechanical, if I expand under consumed,
17:44
I now also have the architecture folder here.
17:48
And in this architecture folder, I
17:50
can see I've got the Revit file of the architecture cloud
17:53
workshared model, plus I also have the Excel and NWC files.
17:58
How cool is this?
18:01
Going back into Design Collaboration,
18:04
let me click on Home.
18:07
I can now go and click on Project Model.
18:11
The Project Model option lets me look at the federated models.
18:14
At this stage it has federated my model,
18:17
which is a mechanical model, and the two models that I consumed,
18:21
which are architecture and structure.
18:23
I can turn off the visibility of any of these models
18:26
to review only the selected models.
18:30
I can also review these models based on the color theming.
18:35
So if I click on this option here,
18:37
it uses my team's color to display my content.
18:42
Similarly, if I click on zero two structure color theming,
18:45
it now uses the structure team's color
18:48
to display the content of the structure team.
18:50
Again, how cool is this?
18:54
Let me now close out of this.
18:56
If I click on Issues on the left,
18:59
currently my team does not have any issues.
19:02
That's why they are not listed here.
19:04
If I click on Project Status, it's
19:08
showing me all the publishing states of my team.
19:11
Similarly, if I click on Changes,
19:13
I can create watch groups to keep
19:15
a track of changing in different elements of different models.
19:19
We are going to talk about this in detail later on.
19:23
And that's the demonstration about creating, sharing,
19:26
and consuming packages.
19:28
Let's now switch back to the slide deck.
19:32
All right.
19:33
So the next thing is reviewing model changes.
19:36
This is hands-down one of my favorite features
19:40
in this Design Collaboration module.
19:42
Using this feature, we can review
19:44
changes between the current version of the package
19:47
and the previous versions of the packages.
19:50
Let's take a look at this now.
19:54
Now to visualize changes, you can do it
19:56
while in the Project Model view, but you can also
19:60
do it using the package timeline, which is actually
20:03
what I recommend.
20:04
You can click on a package in a team's timeline,
20:07
and then you can simply click Compare.
20:11
In the Compare window, you can actually
20:13
decide to compare which versions of the packages.
20:16
And in that window, It would straightaway
20:19
tell you how many changes exist between the two packages
20:23
that you are comparing.
20:24
You can then click on Show Changes
20:26
to actually open the model and show the changes.
20:31
Now while reviewing the changes in the Compare window,
20:34
it shows you all the elements that
20:36
have been added, all the elements that
20:38
have been modified, and also all the elements that
20:41
have been deleted.
20:43
At the top, it'll also tell you which versions of the packages
20:47
are being compared.
20:49
In this interface, you'll also notice
20:50
that the elements that have not changed
20:53
are displayed as ghosted.
20:55
And all the changes are also color coded.
20:58
So elements that have been added will be displayed in green.
21:01
The elements that have been modified
21:03
will be displayed in orange.
21:05
And the elements that have been deleted
21:07
will be displayed in red.
21:10
At any point of time, you can click on any of these changed
21:13
elements.
21:13
And in the Object Change window it
21:15
will show you all the information
21:17
about what the changes are.
21:19
In this window, you can also click on the current version
21:22
or the previous version to review how these elements look
21:25
in the current version, or how they
21:27
look in the previous version.
21:31
Let's now take a look at the demonstration of this.
21:34
And for that, I'll jump over to the Firefox window.
21:38
All right, so here I am in the Firefox window.
21:41
If you look at the structure team lane,
21:44
there was a package shared on this date here.
21:48
There's also a package shared recently.
21:51
So I can see that the package that was shared on this
21:54
date I actually did not consume.
21:57
And after that there was also another package shared.
21:60
Now what I'm going to do is I'm going to click on this package
22:03
here.
22:04
Just like last time, I can click Explore
22:07
to explore this package.
22:09
But in this case, I'm going to go and click Compare.
22:12
Now when I click Compare, it says, all right,
22:15
you are comparing two versions.
22:16
Tell us which versions you want to compare.
22:18
I'll say I want to compare the current package
22:21
with the first package that I actually consumed.
22:26
It's not telling me that there are a total of 98 changes.
22:30
I can click on Show Changes to have a look
22:33
at those changes in detail.
22:35
So in here it's now telling me that I'm
22:38
comparing version 3 of the package against version
22:41
one of the package.
22:43
There are 21 elements added, there are 77 elements modified,
22:48
and there are none deleted.
22:50
How cool is this?
22:54
I can navigate closer to those elements alternatively
22:58
irrespective of what view I am in.
22:60
I can go and click on any of these changes
23:02
here to review them.
23:04
So for example, if I go and expand Pile Cap Nine pile,
23:08
it's not telling me that there are 21 one of these pile caps
23:13
that have been added, there are 49 pile
23:16
caps that have been modified, and there are none deleted.
23:20
And if I go and expand these I can look
23:23
at all of these elements here.
23:25
As soon as I click on any of these elements,
23:27
I'm actually navigated to that element there.
23:31
I can also click on any of these elements on the screen.
23:34
And when I do that, it displays the Object Change window.
23:37
It's showing me all the changes that were made in the elements.
23:42
And it's also telling me that this is how this element looks
23:45
in version 3.
23:46
If I click on version
23:49
that that's how that element looked in version 1.
23:52
How cool is this?
23:55
Similarly, if I go and pick any other pile steel pipe,
24:00
it navigates me to that element here.
24:03
And again, I can see that this is
24:04
how it looks in version
24:07
and this is how it looked in version 1 of the package.
24:13
If I scroll down here, I can go into any of these elements that
24:16
have been added.
24:17
That's how it is in version 3.
24:18
And obviously it did not exist in version 1.
24:27
And this is the reason I mentioned
24:29
that this is one of my favorite features of the program.
24:33
How cool is this?
24:37
I'm going to now close out of the Compare environment.
24:41
I'm happy with this package here because it's not
24:43
affecting any of my work.
24:45
So I'm going to go and click Consume.
24:47
It's now going to ask me to confirm if I
24:49
want to consume this package.
24:51
I'll say yes.
24:53
Now as soon as I do that, the version
24:55
of the structure model in my team's consume folder
24:59
will be automatically bumped.
25:02
If I go back to the Document Management module,
25:05
under my team's consumed structure folder,
25:09
I can see that this version is now bumped to version 2,
25:13
because that's the second package that I consumed.
25:18
And what this means is that in Revit,
25:21
as soon as I go and open my mechanical model,
25:24
I would automatically see all the latest packet changes.
25:28
I don't have to reload or re-link and so on.
25:31
And that's the best part of this Design Collaboration module
25:35
and the concept of package sharing and consuming.
25:43
In this section, we are going to understand the Aggregated
25:46
Project Model Navigation.
25:49
Using Project Model, you can review your model federated
25:52
with the models of the other teams that you have consumed.
25:56
This actually is a really cool feature,
25:58
and I cannot tell you how many times it has helped me
26:01
understand if the coordinates of the models match or not.
26:05
So even before I link them inside Revit,
26:08
in this Project Model view, when I look at the federated model,
26:12
I can see if the coordinates of the models match or not.
26:16
Also, when you're reviewing the federated models,
26:19
you can easily control the visibility of the models here.
26:22
You can even display them using the color theming, which
26:26
basically are the colors of each of these teams in the design
26:30
collaboration environment.
26:33
You can also review sets with sheets or views that
26:36
have issues created in them.
26:39
By clicking on any element, you can access their element
26:42
properties within the model viewer,
26:44
so you don't have to open Revit to do that.
26:49
You can perform different measurement types.
26:51
So you can measure in 2D or 3D.
26:53
You can measure angles and heights.
26:55
You can even snap onto the objects
26:57
while performing these measurements
26:59
so you get the accurate measurement values.
27:03
On 2D sheets, the hyperlinks are automatically
27:06
extracted for easy navigation, and you can even
27:10
place perspective views by choosing a point on the plan
27:14
and a view direction.
27:17
You can section using planes or create a section box.
27:22
Let's now take a look at the demonstration
27:25
of hypermodel navigation.
27:29
All right.
27:30
So I'm back in the Firefox window, logged
27:32
in as the mechanical team lead.
27:34
And that's my mechanical team, which is the current team.
27:38
I'm now going to click on Project Model.
27:41
And as soon as I do that, I can see the federated model
27:45
of my team model, which is the mechanical team
27:48
model, along with the architecture and structure
27:51
models.
27:52
These are the two discipline models
27:54
that have consumed as of now.
27:56
I can now orbit around the models and have a look at them.
27:60
But most importantly, as I mentioned earlier,
28:02
I can control the visibility of any of these models.
28:05
In this case, I'm going to turn off the architecture model
28:08
so I can review mechanical with structure.
28:13
I can also now display these models using color theming.
28:16
So when I click on this icon here,
28:19
it displays the mechanical discipline using my design
28:22
collaboration color theming.
28:25
Similarly, if I go and turn on this option for structure,
28:28
it now displays structure model with the design collaboration
28:31
color theming.
28:32
How cool is this?
28:37
Let me now click on Content Browser.
28:41
I can see that my mechanical model has M100 CD set,
28:45
which has got these five sheets in it.
28:48
And the mechanical share has got a couple
28:50
of sheets and some 3D views.
28:52
Let me now click on this GA plan 100 on level one.
28:58
It now opens this view so I can look at the 2D sheet here.
29:04
Let me now use this Place Me tool.
29:07
I'm going to say the location of the tool is here,
29:10
and I want to look at the model reviewing in this direction.
29:15
As soon as I do that, it now takes me to the 3D view.
29:18
It's now giving me this information on how
29:20
to navigate in this view.
29:22
I'll say, yep, I've got it.
29:23
And now as you could see, I'm looking at the 3D view
29:27
from that display.
29:31
I can use the W key on the keyboard to walk forward.
29:35
And as I'm walking forward, I can navigate around as well.
29:41
Right now I'm on level one.
29:42
If I click on this arrow here, I could go to a different level.
29:45
Let's go to level three.
29:47
And now I'm looking at this
29:52
Again pressing the W key on the keyboard, I can walk forward.
29:56
Pressing the A key I can walk left, D key right, and so on.
30:02
Let me go back to Teams.
30:06
And again, if I do not want to look at the structure model
30:08
right now, I can turn off the visibility of the structure
30:11
model so I'm only looking at my mechanical model.
30:14
How cool is this?
30:18
And again, I can simply click on this cross here
30:20
to close out of the project model.
30:23
But going back into the project model,
30:27
I turn on the visibility of the structure model,
30:31
and now I can perform different measurements using this measure
30:34
tool here.
30:35
Let me display the elements using color theming first.
30:40
I'll go measure.
30:41
I can look at my measurement settings.
30:43
Make sure the unit type is set correctly, which in this case,
30:46
I want feet and fractional inches.
30:50
Precision is 1 by 2.
30:53
And now I want to find out what's
30:54
the distance between the bottom of this slab here
30:57
and this duct.
30:59
I would also change my display type to orbit display,
31:02
rather than the other display I was in.
31:05
And now I can pick this edge of this duct.
31:08
So the program now shows me the x, y, and z values, and also
31:12
the shortest distance.
31:14
Similarly, if I go in here, and I also want to find out
31:17
what's the distance between the bottom of this beam here
31:22
and the top of this duct.
31:25
Again, the program shows me all of these values here
31:28
in the x, y, and z, as well as the shortest distance.
31:32
I'll click Done to close the measurement tool.
31:36
Just zooming out now, I can also go to the Home view.
31:41
The next thing I want to show you are the section tools.
31:44
So if I click on this Section Analysis fly out,
31:47
I can create sections on x plane, y plane, z plane,
31:52
or even a box.
31:55
I'm going to start with the z plane here.
31:57
As soon as I do that, it now sections the model.
31:60
I can use this arrow to move the section plane up and down.
32:03
I can even rotate the section plane if I want.
32:06
Similarly, if I see a section using y plane,
32:10
it now sections the model using y plane here.
32:13
And finally, I can using a box as well.
32:17
That's the box placed by default.
32:19
I can use these arrows to move the box around.
32:24
I can also click on any of these faces
32:26
here to resize that section face.
32:32
So that's the section analysis.
32:34
The whole concept of this hypermodel navigation
32:37
is for you to be able to review the models
32:40
inside this interface rather than opening Revit and then
32:44
reviewing the model there.
32:45
This makes it a lot easier, especially for non-Revit users
32:50
to access the information of the model.
32:52
In this case, if I go and click on any of these elements,
32:55
let's say if I go and click on this AHU,
32:57
I can now go into properties, and I get all the information
33:00
about this AHU right here.
33:04
Similarly, if I go and click on, let's say, this element here,
33:07
which is a supply diffuser, I can now
33:09
look at all the parameters here.
33:12
As you can see, for non-Revit users,
33:14
this is a fantastic view where they can access the model,
33:18
they can review the properties, perform measurements, section
33:21
elements, and so on.
33:24
Let me now close out of this display.
33:30
In this section, we are going to understand
33:32
how to create and review issues in the design collaboration
33:36
environment.
33:37
I'm a big fan of the issue management system
33:40
that comes with BIM 360, because it's a closed-loop issue
33:44
management system.
33:45
What that means is that you can create issues here in BIM 360.
33:50
You can then download the issues inside Revit.
33:52
You can review and fix the issues inside Revit.
33:55
And then you can change the status there in Revit as well.
33:58
And finally, in the BIM 360 environment,
34:01
you can then review those resolved issues
34:04
and change their statuses to closed.
34:08
In the design collaboration environment,
34:09
when you click on the Issues tab on the left,
34:12
you can see all the issues of the current team.
34:17
Alternatively, you can click on any of the shared packages
34:20
and review the issues associated with the packages of a team
34:24
as well.
34:25
And the really cool thing is that this
34:27
could be for your team's package or the packages shared
34:31
by other teams as well.
34:32
Just be mindful that you need to have
34:34
the right set of permissions to view those issues.
34:40
You can also access issues by clicking on the project model,
34:43
and then clicking on the Issues tab on the left.
34:48
Now as I mentioned earlier, from within the design collaboration
34:51
environment, you can also create new issues.
34:55
The issues that you create must have type, status, title,
35:00
and other fields.
35:03
The assignees and owners can be selected from the project team
35:06
members, roles, or companies.
35:09
Now remember that the owners could only
35:11
be selected from the users of the current project.
35:15
Once the issues are created, they'll
35:17
be available when you click on the Issues tab from the left.
35:22
And in the Project Model view, when
35:24
you go into the model content, the views with issues
35:27
will have a caution tag in the content browser.
35:32
You can click on any of these issues at any point of time
35:35
to review them, sort them, and filter them.
35:39
If you have the right set of permissions,
35:41
you can also edit an issue, and you can change their statuses
35:45
from within the design collaboration environment
35:47
as well.
35:48
Now one of the most important things that you need
35:50
to remember is that an existing issue cannot be deleted.
35:54
It can only be voided.
35:58
And again, one of my favorite features
35:59
in this environment related to issues
36:01
is that from within the design collaboration environment,
36:04
you can also export issues as reports.
36:07
And these reports could be in PDF format, XLSX format,
36:11
CSV format, and even BCF formats that you can then import
36:15
in some of the other programs.
36:18
Let's now take a look at the demonstration of this.
36:23
OK, so here I am back in the Firefox window, logged
36:26
in as the mechanical team lead.
36:29
Now before we talk about issues, you
36:32
need to make sure that the project admin has given you
36:35
the right set of permissions to view and create issues for you
36:39
to be able to do all of these steps
36:41
that you are going to learn in this demonstration.
36:45
On the home screen, if I click on issues here,
36:49
I can see all the issues associated
36:51
with the current team, which is my mechanical team.
36:54
It's telling me that there are three issues associated
36:57
with the mechanical team.
36:58
I can click on any of these issues to open the issue panel,
37:02
and I can review the information about the issues.
37:06
If I click on this dropdown list here,
37:09
I can change it to team work in progress issues or team package
37:13
issues.
37:14
Similarly, if I go and click on any of the existing team's
37:18
packages, I can look at the issues associated
37:21
with those packages as well.
37:24
So basically, if you have the right set of permissions
37:27
you can not only look at the issues associated
37:29
with your team, but also issues associated with the packages
37:33
of other teams as well.
37:35
Let me go back to the Home tab.
37:37
Now if I go to the project model,
37:42
and if I go to Issues on the left,
37:44
it shows the issues of my team.
37:47
I can click on any of these issues
37:49
to be navigated to that particular element on which
37:52
the issue pin was placed.
37:55
I can look at all the information about that issue
37:57
here as well.
37:59
Let's go back.
38:01
Now as I mentioned earlier, from within this environment,
38:04
I can also create new issues.
38:06
Let's say a mechanical engineer or a mechanical project lead
38:11
is reviewing the mechanical design from this environment.
38:15
As they're reviewing the design, they
38:17
notice that there's an AHU sitting right here.
38:20
Let me go back to teams and display
38:23
the model using color theming.
38:25
This AHU appears to be out of place.
38:30
In this case, I can go to the Issues panel,
38:34
and I can say Create Issue.
38:36
I'm going to place the issue pin on this issue here.
38:40
And now in this issue I can instruct
38:43
the mechanical designer to delete this AHU.
38:47
For title, I'm going to go and say delete AHU.
38:51
Assigned to, this is where I can go and assign it
38:54
to a user role or a company.
38:57
In this case, I'm going to assign it to this user here.
39:01
Due date, I'll go and say fix it by 31st.
39:07
If I had locations in my project,
39:08
I can go and define the locations here.
39:12
On location detail, I am the owner of this issue.
39:17
And the root cause is design coordination.
39:22
Under description, I can add a description here.
39:24
This AHU is out of place.
39:26
Please delete it.
39:29
And now as soon as I click Create,
39:30
this issue is created and would be
39:33
available in the list of issues for my team.
39:36
Let me close out of the project model display now.
39:40
So that was about the issues associated with my team.
39:43
Let's now talk about issues associated with another team.
39:46
In this case, we'll take the example of the plumbing team.
39:49
Plumbing team, as you can see, has already
39:52
shared two packages-- this one here on this date,
39:55
and this one here on this date.
39:58
I haven't consumed any of these packages.
40:01
If I click on the first package here,
40:04
I can see that it has three issues associated with it.
40:07
I can click on Issues here to actually see
40:09
those three issues.
40:11
There are two open issues, and there's an answered issue here.
40:16
I'm going to click on this answered issue,
40:18
and it opens the Issue window.
40:21
I can see that I am the owner of this issue.
40:24
It was assigned to this user here.
40:26
And the issue was because the coordinates of the models
40:29
do not match.
40:31
I can now look at the activity associated with this issue,
40:35
and I can see that this user actually
40:38
went and fixed the problem.
40:39
They are saying that this is already done,
40:41
and the latest package has been shared.
40:44
I can also see that they changed the status
40:46
from opened to answered.
40:48
What I'm going to do in this case is click on Explore
40:52
to explore this first package.
40:55
And I'm going to go under Teams on the left.
40:58
I'm going to turn on the visibility
40:60
of the mechanical model.
41:02
Now if I go to the home view here,
41:04
I can see that this was the problem.
41:07
The coordinates of the plumbing model
41:09
did not match the coordinates of the mechanical model.
41:12
And hence, that issue was created.
41:15
If I close out of this display, I'm
41:18
now going to go and click on the second package shared
41:21
by this team.
41:24
I'm going to go and say Explore.
41:27
And now with this one here, when I go and turn
41:30
on the mechanical model, I can see
41:32
that, yes, they have fixed the coordinates of their model.
41:36
How cool is this?
41:39
Now that I'm happy with this, I can go into the Issues panel.
41:43
I can click on this issue here, and I can go and change
41:47
the status of this issue from answered to closed.
41:50
I can add a comment here saying that the coordinates are
41:53
fixed now.
41:58
And now that I'm happy with this package here,
42:01
I can click on Consume to consume the plumbing package.
42:06
So my mechanical team now has consumed the last plumbing
42:09
package that was shared.
42:12
Going back into Issues tab on the left,
42:15
I can use the Export option to export all of these issues.
42:19
Now please note that in this case,
42:21
I am only given the option to export in the CSV and BCF
42:25
format, and the reason is because I'm
42:28
logged in as a mechanical team lead, not as a project admin.
42:33
But a project admin can also export in additional formats.
42:37
To show you this, let me switch over
42:39
to the Google Chrome window where I'm
42:41
logged in as a project admin.
42:45
All right.
42:45
So here is the Google Chrome window.
42:47
I'm logged in as the project admin.
42:50
And for the mechanical team, when
42:53
I click on the Issues tab on the left, I can go and say Export.
42:57
I can now export as PDF and XLSX as well.
43:01
Please note that these options were not available
43:04
when I was not logged in as a project admin.
43:08
So please be mindful of this.
43:11
And that's all we have in the demonstration of the Issue
43:14
Management system from the design collaboration
43:16
environment.
43:17
Let's jump over to the slide deck now.
43:23
In this section, we are going to understand watch groups.
43:27
This is one of the newer features
43:29
that was added to the design collaboration environment.
43:33
When you click on the Changes tab,
43:35
you can create a new watch group.
43:38
Watch groups are used to keep track
43:41
of changes of certain elements in your model,
43:44
or in the models of other teams.
43:47
To create a new watch group, you can click on New Watch Group.
43:51
You can then select either your team model or the model of one
43:55
of the other contributing teams.
43:57
You can then select the elements that you
43:59
want to include in the watch group,
44:01
and then define the name for that watch group.
44:05
The whole concept is next time when
44:07
there is a new package shared, the program
44:10
would automatically show you the number
44:12
of changes between the current package
44:15
and the previous package.
44:16
It'll also show you the number of elements that have changed.
44:20
You can click on that watch group name
44:22
to review the changes.
44:24
You can also click on Show Changes
44:26
to actually open the model in the design collaboration
44:29
environment, and then review the changes one by one.
44:32
Let's now take a look at the demonstration
44:34
of creating watch groups.
44:39
All right.
44:39
So I'm back in the Firefox window, logged
44:42
in as the mechanical team lead.
44:45
I'll now click on the Changes tab,
44:47
and then click on New Watch Group
44:49
to create a new watch group.
44:51
As you can see, I can select my team model,
44:55
or I can select the models of the other contributing teams.
44:59
In this case, I want to select the structure model.
45:02
The reason I want to keep a track of the elements
45:04
in the structure model is because I've
45:06
used some references of some beams and columns
45:09
to place the duct work.
45:11
For this, I'm going to click on Structure Model here.
45:16
Next.
45:18
And now I can expand the structure model
45:21
and select the elements I want to keep track of.
45:23
In my case, I want to keep track of the changes
45:27
in the structural columns, as well as beams,
45:31
which are structural framing.
45:33
I'll go and click Next now.
45:37
I'll go and specify the name for this watch group, beams
45:40
and columns.
45:42
And now I'm going to simply click on Save.
45:46
Once I've saved this watch group.
45:49
I can now straightaway see that between the last package
45:52
and the current package, there are 21 changes.
45:56
Six columns have changed, and 15 beams have changed.
46:04
Now let's assume the structure team
46:07
has published their new model and also shared
46:11
a brand new package.
46:14
So in this case, the watch group is telling me
46:16
that there are a total of 252 changes.
46:21
I can expand the watch group and get some more details
46:24
of how many columns have changed and how many beams
46:28
have changed.
46:29
If I click on the watch group name,
46:31
I can actually see that I'm comparing
46:34
this version, which is the version 4 package,
46:37
against version 3.
46:39
If I go and say compare it against version 2,
46:42
it'll now update and tell me how many elements have changed.
46:46
And we can see here between version 4 and version 2,
46:50
there are same number of changes, meaning the beams
46:53
and columns were not changed between version 2 and version
46:57
I can now go and say Show Changes.
47:01
The program now opens the model in this environment
47:04
here under Change Visualization.
47:07
And this view, as you can see, is very similar to the Change
47:11
Visualization view that we looked at earlier
47:13
in this accelerator.
47:14
We can expand these elements, and we can
47:17
look at what the changes are.
47:19
How cool are these watch groups?
47:24
Let me close out of this environment.
47:27
Now at any point of time, I can click on these three dots
47:30
here on the right of my watch group name.
47:33
I can edit this watch group, or I can delete the watch group.
47:38
And that's all we have in this demonstration of creating
47:41
and reviewing watch groups.
47:44
Let me return to the slide deck.
47:47
Now again, talking about some useful links,
47:50
these are several links that you can click on
47:53
to access additional information.
47:56
And don't forget about the Enterprise Hub page as well.
48:02
And that's all we have in this second accelerator.
48:04
I hope you enjoyed learning about
48:05
these advanced collaboration features in BIM Collaborate
48:08
Pro.
48:09
In the next accelerator, which is also the last in the series,
48:12
we are going to learn about some best practices.
48:15
I'll see you there.
48:16
Cheers.
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.