Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Any referenced datasets can be downloaded from "Module downloads" in the module overview.
Transcript
00:08
Welcome to BIM 360 design collaboration,
00:11
the aggregate project model and data packaging.
00:14
In this video,
00:15
we will cover the aggregate project model packages and
00:18
how the ability to browse compare and analyze data
00:21
can streamline your overall design process, along with
00:24
the ability to digitally deliver your project milestones.
00:27
The focus is going to be on the functionality
00:29
of the aggregate project model and options available.
00:32
When creating data packages to share,
00:35
we will be focusing on three components of the aggregate project model.
00:39
First, the discipline
00:41
work in progress - this from team space,
00:44
we can look at our discipline work in progress model in a stand alone
00:47
manner or as part of a Federated or aggregate
00:50
project model.
00:52
Secondly, we will see how teams can interact
00:55
with discipline partner models at the properly determined intervals.
00:60
And lastly the ability to browse, compare, and analyze work-in-progress
01:05
and partner BIM data in a structured and easy to digest manner.
01:08
Okay,
01:09
As you can see, you see,
01:10
we switched over to the BIM 360 design collaboration user interface.
01:15
And in here,
01:16
we can see the structural on the bottom. So that is our current team.
01:20
If we look at our project model,
01:22
we will see
01:24
all the consumed content we have in there.
01:27
So if we click on our eye that shows our teams,
01:29
these are the consumed models and the versions,
01:33
which you know are current in our Federated or aggregate view.
01:39
So not only can we review the discipline content
01:42
in the 3d view of
01:44
context to our work in progress model, we can look at
01:47
it in sheet view as well. So
01:51
turn architectural back on,
01:53
remember we're in our structural team and we go to our content browser
01:57
and this is the set that was published from Revit.
02:00
And we can go through and look at the plans
02:04
as if they were PDFs.
02:06
You know, we can come in here and see, hey,
02:08
architectural with our doors and walls is overlaid with our
02:11
structural model and we can go ahead and browse through those sheets,
02:15
doing our analysis and comparisons.
02:19
Now we're going to look at how
02:21
disciplined models are packaged and shared. A team's ability
02:23
to control when and what data is shared is an important factor in minimizing risk.
02:30
So you can see we switched over our mechanical team is now current
02:33
and we can go ahead and hit the plus sign. You can see this is our create a new package.
02:40
Once we create a new package,
02:42
we have the ability to choose what we're going to include in the package.
02:45
You can see up here now there's nothing in there.
02:48
If we click on sets,
02:50
we can include this,
02:52
we can include electro sheets and then the set one is eight sheets as well.
02:56
You can see
02:57
how it's growing up here.
02:59
And we can also
03:00
attach any support
03:02
documentation, like specifications that add clarity to the package.
03:05
So
03:06
that's it.
03:07
and to do so we just create a documents folder and
03:11
in docs and we can attach this
03:13
PDF as well to go along with the package.
03:17
We can give it a name.
03:22
And once we're confirmed, we have everything shared, we can save it
03:28
and
03:30
save,
03:32
go ahead and share that out with the team. And if we misnamed it, we can fix that here.
03:37
We can add a package description
03:39
if needed. We can push it to a set that we've established within document management,
03:45
and
03:46
we are good to go,
03:47
I can send it along.
03:50
A key thing to remember when we're
03:51
creating these packages is there could be instances
03:53
where we have a large job site such as an infrastructure project where there may be
03:58
multiple buildings
03:60
and multiple models in those instances. We want to
04:03
be very cautious with the package naming
04:06
as well as, you know, what models we're including. You can see this one has
04:11
multiple models in it,
04:12
but just keep that in the back of your mind in those situations,
04:16
we can have, you know,
04:17
multiple models and create packages based on phases as needed.
04:24
Now, we can look at how we can analyze the different Revit
04:26
publishers. You can see in our structural model, we have multiple publishes here.
04:31
We can choose one
04:34
and we can do a change visualizer
04:38
to see what changed between the different publishers.
04:42
So you can see in this instance
04:43
between this publish and that publish everything that changed in the model. So
04:47
it's also itemized over here for us making it
04:50
very clear as to what happened between iterations in the model.
04:57
In the last few things to look at here is our schedule publish. If we click on this,
05:02
we can schedule a weekly, publish
05:05
a day
05:06
and a time
05:08
and that's the most frequent.
05:09
We can set of this weekly, but we can choose a day and time.
05:11
Typically we see Friday afternoon
05:13
and it just ensures that we
05:15
users latest data gets pushed out on a Friday afternoon or
05:18
a Monday whenever the case works for the project team.
05:21
So it doesn't sitting on the local drive somewhere and not pushed up to the cloud.
05:25
Because remember
05:26
it just syncs data that's changed, not the overall private data itself
05:33
and update the latest.
05:34
We'll grab our latest publish sets from our
05:36
work in progress model and bring everything in.
05:38
It will also version our model for us.
05:41
And we can always check our project status page by selecting here.
05:46
We can see within our structural team
05:49
what we've consumed. And if it was successfully published and the date.
05:54
If you don't think you get enough emails, you can always turn on email notifications,
05:59
and any time a package is shared and consumed, you can get a notification there.
06:05
And lastly our filters, if we expand these down, we can check our filters
06:10
and just kind of watch how it performs here. If we turn off my team's models
06:14
and we can turn off other team's models, not all we see
06:17
are our publish set. So this is actual data that's been shared
06:23
and that concludes the aggregate project model and data packaging. Thank you.
Video transcript
00:08
Welcome to BIM 360 design collaboration,
00:11
the aggregate project model and data packaging.
00:14
In this video,
00:15
we will cover the aggregate project model packages and
00:18
how the ability to browse compare and analyze data
00:21
can streamline your overall design process, along with
00:24
the ability to digitally deliver your project milestones.
00:27
The focus is going to be on the functionality
00:29
of the aggregate project model and options available.
00:32
When creating data packages to share,
00:35
we will be focusing on three components of the aggregate project model.
00:39
First, the discipline
00:41
work in progress - this from team space,
00:44
we can look at our discipline work in progress model in a stand alone
00:47
manner or as part of a Federated or aggregate
00:50
project model.
00:52
Secondly, we will see how teams can interact
00:55
with discipline partner models at the properly determined intervals.
00:60
And lastly the ability to browse, compare, and analyze work-in-progress
01:05
and partner BIM data in a structured and easy to digest manner.
01:08
Okay,
01:09
As you can see, you see,
01:10
we switched over to the BIM 360 design collaboration user interface.
01:15
And in here,
01:16
we can see the structural on the bottom. So that is our current team.
01:20
If we look at our project model,
01:22
we will see
01:24
all the consumed content we have in there.
01:27
So if we click on our eye that shows our teams,
01:29
these are the consumed models and the versions,
01:33
which you know are current in our Federated or aggregate view.
01:39
So not only can we review the discipline content
01:42
in the 3d view of
01:44
context to our work in progress model, we can look at
01:47
it in sheet view as well. So
01:51
turn architectural back on,
01:53
remember we're in our structural team and we go to our content browser
01:57
and this is the set that was published from Revit.
02:00
And we can go through and look at the plans
02:04
as if they were PDFs.
02:06
You know, we can come in here and see, hey,
02:08
architectural with our doors and walls is overlaid with our
02:11
structural model and we can go ahead and browse through those sheets,
02:15
doing our analysis and comparisons.
02:19
Now we're going to look at how
02:21
disciplined models are packaged and shared. A team's ability
02:23
to control when and what data is shared is an important factor in minimizing risk.
02:30
So you can see we switched over our mechanical team is now current
02:33
and we can go ahead and hit the plus sign. You can see this is our create a new package.
02:40
Once we create a new package,
02:42
we have the ability to choose what we're going to include in the package.
02:45
You can see up here now there's nothing in there.
02:48
If we click on sets,
02:50
we can include this,
02:52
we can include electro sheets and then the set one is eight sheets as well.
02:56
You can see
02:57
how it's growing up here.
02:59
And we can also
03:00
attach any support
03:02
documentation, like specifications that add clarity to the package.
03:05
So
03:06
that's it.
03:07
and to do so we just create a documents folder and
03:11
in docs and we can attach this
03:13
PDF as well to go along with the package.
03:17
We can give it a name.
03:22
And once we're confirmed, we have everything shared, we can save it
03:28
and
03:30
save,
03:32
go ahead and share that out with the team. And if we misnamed it, we can fix that here.
03:37
We can add a package description
03:39
if needed. We can push it to a set that we've established within document management,
03:45
and
03:46
we are good to go,
03:47
I can send it along.
03:50
A key thing to remember when we're
03:51
creating these packages is there could be instances
03:53
where we have a large job site such as an infrastructure project where there may be
03:58
multiple buildings
03:60
and multiple models in those instances. We want to
04:03
be very cautious with the package naming
04:06
as well as, you know, what models we're including. You can see this one has
04:11
multiple models in it,
04:12
but just keep that in the back of your mind in those situations,
04:16
we can have, you know,
04:17
multiple models and create packages based on phases as needed.
04:24
Now, we can look at how we can analyze the different Revit
04:26
publishers. You can see in our structural model, we have multiple publishes here.
04:31
We can choose one
04:34
and we can do a change visualizer
04:38
to see what changed between the different publishers.
04:42
So you can see in this instance
04:43
between this publish and that publish everything that changed in the model. So
04:47
it's also itemized over here for us making it
04:50
very clear as to what happened between iterations in the model.
04:57
In the last few things to look at here is our schedule publish. If we click on this,
05:02
we can schedule a weekly, publish
05:05
a day
05:06
and a time
05:08
and that's the most frequent.
05:09
We can set of this weekly, but we can choose a day and time.
05:11
Typically we see Friday afternoon
05:13
and it just ensures that we
05:15
users latest data gets pushed out on a Friday afternoon or
05:18
a Monday whenever the case works for the project team.
05:21
So it doesn't sitting on the local drive somewhere and not pushed up to the cloud.
05:25
Because remember
05:26
it just syncs data that's changed, not the overall private data itself
05:33
and update the latest.
05:34
We'll grab our latest publish sets from our
05:36
work in progress model and bring everything in.
05:38
It will also version our model for us.
05:41
And we can always check our project status page by selecting here.
05:46
We can see within our structural team
05:49
what we've consumed. And if it was successfully published and the date.
05:54
If you don't think you get enough emails, you can always turn on email notifications,
05:59
and any time a package is shared and consumed, you can get a notification there.
06:05
And lastly our filters, if we expand these down, we can check our filters
06:10
and just kind of watch how it performs here. If we turn off my team's models
06:14
and we can turn off other team's models, not all we see
06:17
are our publish set. So this is actual data that's been shared
06:23
and that concludes the aggregate project model and data packaging. Thank you.
Note: Prior to beginning practice exercise, a demo account and project or a sandbox project within a corporate account will need setup, teams created, and users added (account admin actions).
Go to Document Management.
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.