- [Narrator] In this video, we're going to continue our look at
the Package and Shared Workflow.
And there are a few videos previously that we could consider
prerequisites to this one.
Those would include the Publishing Cloud Models video
and the Linking via Shared Folder video.
So if you haven't watched either of those earlier
in this chapter, then I encourage you to do so now,
before continuing.
What we're going to focus on in this chapter
is the process of actually creating the package
that gets shared with the extended project team.
So let me just reiterate the scenario
that we're currently in.
I am at the MEP engineer's desk Freya,
and we are looking at the model that has a link
to the architecture background.
So this right here is the architectural background
and the architect has added a space over here,
off to the left and we are not seeing
that space currently in our version of the link
and if you go to reload link, nothing happens.
And the reason for that is really quite simple.
The architecture team has not yet issued an updated package
for us to use in our model.
So all of the work they've done on that new space
is considered a work in progress within their internal team.
And it's only when they are ready to share
that work with us, does it become available to the MEP team.
So if you think about this in traditional terms before we
had CAD and BIM software, it's really not that dissimilar
to what would have taken place in those days.
When you were ready to share your design
with one of your external consultants,
you would gather up all of the supporting documentation,
so you would have some drawings and maybe some
specifications and any other pieces of information that were
pertinent to the issue at hand, and then you would package
that all up, literally into a package
that you would then ship to their office.
And you might send it via courier or UPS or FedEx,
but in some way they would get this physical package,
they would open it up and then
they would begin reacting to its contents.
So all we're really doing here in BIM 360 is sort of
emulating that in the digital and cloud-based realm
that we're working in.
So let's walk over to our architect's desk then
and create a new package for our MEP team.
Okay, so I've now walked over to Deshi's desk
and we are logged into the BIM 360 portal as her username.
And I'm in the Document Management Module.
And I wanted to start in the Document Management Module
because here in the architecture folder,
we can see our architectural model.
And I wanted to point out to you
that it's currently v2 version two, all right.
The reason that's important is because version two
does not include the new space that we want to share
with our MEP designers.
So in order to create a new package, we must first go back
to Revit and publish out a new version of the model.
So if you watched the video on Publishing Cloud Models,
you may recall that every time you save or synchronize,
it updates your actual Revit file,
but those changes are not visible to folks in BIM 360,
unless you publish.
So the publish is an important step to making sure
that the package that we're going to create contains
the correct contents.
So let me switch to Revit and here in Revit,
I am also logged in into Deshi's account
and we're looking at the same general location.
So we're in the architecture folder,
here's the architecture model.
Now I don't even need to open the architecture model,
if all I want to do is publish the latest changes.
And that's what I'm going to do here
to save a little bit of time.
So I'll use the menu over here on the far right,
choose Publish Latest, and then it will confirm
in this dialogue, and then I will click Publish.
Now, if you want to add sets and other views
and all of those things,
you can go back and review the Publishing Cloud Models video
for more information on that,
but let's go ahead and get that publish process started.
Meanwhile, we'll switch back to BIM 360
and back to Deshi's account here.
And you can already see that it's incremented the version to
version three.
So that's what we wanted, that's the important step here.
Now, I also want to point out that there's another file
in this folder.
This is actually a PDF file.
Now this is really just a placeholder PDF,
but I just wanted you to see that when you create a package
it's possible to include other documents,
not just Revit files.
So how exactly do we create a package?
Well, we need to do that in the Design Collaboration Module.
So I'm going to switch over to Design Collaboration.
And that will take me to my default team.
So, because I'm logged in as Deshi,
you can see that takes me to the architecture team.
Now you can see other teams that you have access to
by expanding this item right here,
which exposes the timelines.
So what you have here is a series of timelines
across the top of the screen,
one for each team that you have access to.
So Deshi has access to the architecture team
and the shared stream, okay,
so she's not seeing MEP or Structure because she doesn't
have access to those folders.
So there's a series of symbols that you see here on
the timeline and those symbols are meaningful in that
they indicate different kinds of items.
So a circle indicates a package
where a square indicates a model.
So notice that this is our initial coordination package,
and this is the model that we just published.
So there's a Plus sign right here,
and we can use that to create a new package.
So I'm going to do that.
It will suggest the name Architecture 4,
because this is the fourth time that I've done this command,
but there's a small pencil icon right next to it,
and you can actually rename this to anything that you like.
So I'm going to call this
(keyboard clanks)
Updated Second Floor.
So it's a pretty good idea to do a descriptive name
because that'll help people identify
what the contents of that package are.
Now here, you have to include at least one item
in the package and you can see currently
that I have no sets, no sheets, no views.
So here I can expand each one of these items
to choose something to include.
Well, I want to include the model for sure.
So I'm going to check it right there
and notice that it says v3.
So again, that's important because if it's still said v2,
we'd be sending them a package that looks exactly like
what they already have and that would not be very useful.
Now under Documents, it says no documents added,
but you can click this link
and that will take you to your available folders.
And if I expand the Architecture folder,
there's that PDF file.
So you can optionally include other documents like reports
and graphs and PDFs and Word documents, specifications,
anything that you want to include with this package
to support its contents.
So I will add that PDF document
and then down here, click Save.
So I'm saving the package and then up here,
there are some buttons available.
Now the Delete button is only here
before you actually share the package.
So up until the moment when you share it,
you could optionally delete this package,
if you decided you no longer needed it.
Once it's been shared, it becomes like a legal record
and it can no longer be deleted.
So just keep that in mind,
if you're trying to manage your existing packages.
Now the Share button here is actually controlled by
users permissions levels.
So if you think back to one of our earlier videos
where I introduced you to the team of this project,
I showed you the way that the team permissions
were set up on each folder and Deshi,
I added as a special elevated level of permission.
She had view, edit and share and by adding
that share level of permission,
this button right here becomes available
and Deshi can click that and share this package.
So until the package is shared,
it only exists for the architecture team.
So nobody outside of architecture would be able to view or
react to this package or it's contents.
Now you are welcome to put in a description here,
but that's optional and then simply click Share.
So that creates the package and we now have this little
hybrid icon here, which is just simply telling you
that you have multiple nodes in the same space.
And it's got that hybrid shape because one of them
is a package and one of them is a model.
And if you click on that node, it would actually expand it
and just zoom in on the timeline,
and you could see that these two items
are only a few minutes apart.
So now that we've done all of that,
we can actually go back to Freya's desk
and see the results.
Okay, so we're now back over it Freya's desk,
and we want to go back to work on our MEP model
and see the latest changes that the architect
has shipped over.
So I will click into my MEP folder here
and click on my MEP model.
Now this is going to load the model
and because it's got a Revit link attached to it already,
it's automatically going to bring in the latest changes
to the architecture model, and since we have published
and issued a new package,
those changes to the second floor will automatically be part
of the link as it reloads right here.
So from the MEP person's point of view,
there's really nothing special they have to do.
Notice how, as soon as the architect
has issued a new package,
it automatically shows up here in their work.
So at first it seems like there's a lot of steps involved
and admittedly there are but if we think about
the experience from the average everyday Revit user,
they will just go about their work as normal,
and the links will automatically load up
and behave the way that they expect them to.