- [Instructor] In this video,
we're going to continue our look at the various ways
that we can link Revit projects together within BIM 360.
Now, previously, we looked at the direct linking method,
which closely emulates how you're doing this
in your internal network.
We create a direct link to the model that we want to see.
And as that model is changed or updated by its team,
we can immediately reload those save changes in our host.
Now that workflow works perfectly fine
for certain kinds of projects,
but there are two other alternatives
that we can access using BIM 360.
So, both of them involve what we call a package,
but the first one that we're going to look at
of the two is the packaged shared workflow.
So let's go ahead and talk about the details
of the packaged shared workflow.
So we have our host model,
and we want to create a link to another file.
In this workflow, we kind of create a barrier,
or a firewall between the link and the host.
So the link is a live version that it's project team
works on in it's day to day work.
So think of that as their work in progress file.
So this happens within that team.
But none of the other teams in the BIM 360 project
will see that file directly.
They have to have permissions to that folder
in order to be able to access it.
Now, when that team is ready to share their changes
with the broader project team,
they create what we call a package.
So to share it with that outside team,
they create this package and share it.
And it goes into a shared folder
that everyone on the project has access to,
because well, it's shared.
And then that actually creates a packaged copy
of the linked file in that location,
and then that's what the host model is actually linking to.
So, when the host updates their link,
they're always seeing the changes that have occurred
to a packaged copy.
And that packaged copy doesn't reflect any changes
unless the original team republishes the file.
So you can see where that kind of creates that second step,
that barrier so that the host files are not always looking
at your immediate saved work in progress changes.
There may be things that you're trying out in your file
that you don't want these other teams to be seeing
and reacting to in real time.
So this method,
this workflow allows you to have some control over that.
Now, in order for this to function,
you have to make sure that your BIM 360 project
is set up correctly in order to support this workflow.
So we've already done a good deal of this setup
in some of the previous videos.
And I've also done some additional work behind the scenes.
So let me walk you through the setup that we currently have,
that I will be demonstrating this workflow within.
So I'm here now in BIM 360,
and I'm logged in as myself with admin level rights.
And I want it to start off by showing you
the members of the team again.
So I'm here in the project admin module,
and here are my various team members.
And of course, I'm right there.
And you can see that I have full admin rights.
There's another admin user here in the project, Zachary,
and he has full admin rights.
And then the remainder of the users,
you can see have different levels of access rights
depending on either their company, or their role.
All right, so let's click over here
on the services tab next.
And then I will click
the design collaboration module link here,
on the left hand side.
Now, I want to just remind you that in order
for you to be able to do this,
you have to have admin level rights to the project.
So, I'm editing the actual teams right now,
and only admin users can manage the teams.
Now you can see here that I have four teams.
And for this example,
we're going to focus on the architecture and MEP teams.
But next to each team,
you can see the path to the folders,
and you can see the members that are assigned to each one.
So let's start with the MEP team.
I will check the box next to that.
And one way that we could look at the team membership
is to click the manage team members button right here.
And you'll see three entries in here.
There's of course, myself and Zachary, the two admin users.
So we will always be there.
But then the third entry is the MEP Co.
So what I did here was I actually added the entire company,
this way, as new users come on board for that company,
I won't have to add them individually.
So anybody from the MEP Co International
comes into this project with the same level of access,
they have view and edit level permissions.
All right, so let me close out of there.
I'll uncheck MEP.
And then the other way that you can see the team membership
is to click the member link over here
in the far right column.
So I'll do that with this number five next to architecture.
And there are five entries here.
Again, myself and Zachary is admin.
We have Julie Parker who only needed view level access
to the project.
So she has a limited accessibility.
We have, instead of the Pinnacle Design Architects firm,
this time I did the role architect.
So anybody who's assigned the role architect
would get access to this folder.
And so that could actually be across different firms.
So if you want to manage it by firm, you can do that.
If you want to manage it by role, you can do that.
It's entirely up to you,
but in both of those methods,
anybody who gets added to that role, or to that firm later
will get access to that folder.
So just make sure you think that through carefully.
And then you can see here
that I have another individual user, Deshi.
Now you may recall that Deshi is my lead architect,
and I gave her an elevated level of permission.
So she has view, edit, and share,
where her other architectural colleagues
have only view and edit.
So that extra level of share permission
will become important later on,
when we're actually setting up the Revit links.
So let me close out of there.
And there's one last thing I want to show you here
in the project setup.
If I go back to the module picker here,
and choose the document management module,
we can actually see those folders that we saw a moment ago
in the teams space are now listed here under project files.
So notice that I have a folder for each discipline,
and there's also a shared folder.
So earlier we talked about the shared folder
as being the location for any of the files
that get packaged up and shared with the broader team.
So this is that folder.
And if I click on that folder,
you can see that there's an additional sub folder
for each discipline within there.
So, if the architecture team creates a package,
those files will get placed
in the shared architecture folder,
and all team members have access to the shared folder,
where only members of the architect role
have access to the architecture folder,
and only members of MEP Co have access to the MEP folder.
So you can see where the main folders themselves
are that behind the firewall location
that the teams work within.
And then the shared folder
is where their published packages go
when they're ready to share them
with the broader project team.
So I hope that gives you a little bit of an understanding
of the setup that's required
in order for us to do the packaged shared workflow.
In the next video,
we'll actually jump into Revit
and begin setting it up,
so you can see it firsthand.