- [Instructor] Like to continue talking about
the package and consumed workflow
and discuss what happens when updates occur
within your projects.
So let's say that the MEP engineer
has added some Ductwork
to our new space over here on the second floor
in the architectural model.
So I want to bring that new version of the MEP model
into my workspace here by reloading that new link.
Now, you may recall that we're using the package
and consumed workflow.
Therefore, it's not as simple
as just simply updating the Revit link,
we have to receive a new package
and then we have to consume that package
and then we can reload the Revit link.
So there's actually a few steps involved.
So let's say that we had a conversation with Freya,
our mechanical designer and she has indicated that
they have in fact issued a new package for us to look at.
So I will switch over to BIM 360 and check it out.
So once again, I'm logged in here as the sheet
my lead architect.
I mean the architecture team space of design collaboration.
And I'm going to expand the swim lanes here.
And you can see on the shared timeline right here
on the far right, that there's an open circle
indicating that there's a new package for us.
And if I hover over that it says
that it is new duck work on the second floor.
So exactly what I was looking for.
So I will click on the package and then right here,
I will click the consume button
and then once again consume.
Now that will actually update
the version of the MEP model
that lives in the consumed folder under architecture.
So that means all we need to do now
is return to Revit and reload the link.
So I will scroll down on the project browser
and I'll do it here from the Revit links branch.
But you could of course do it
from the Manage links dialog as well if you prefer.
And I'll right click the MEP model and choose reload.
And it looked like something was happening
but you can see there's no new Ductwork in the space.
So what went wrong?
So naturally, a situation like this could be frustrating.
And so that's why I wanted to walk through it
because I wanted to give you some things to check
when you're trying to figure out why
you're not getting the latest version of the changes.
And in this case the most likely
scenario is that the MEP engineer
probably forgot to publish
their model before creating the new package.
So let's quickly review the process
and what's required just so that we make sure
that we're clear here on what needs to happen.
So remember that all of the work in Revit
takes place almost behind the firewall if you will.
So the Revit models do live in the cloud
but only folks that are working
in Revit didn't have permission
to those Revit models can actually see those changes.
If you want any of the Revit changes
to be visible in BIM 360,
then you have to publish them.
Okay, so that's a very important step
that we need to remember.
Once they're published, then folks in BIM 360
can see that version of the model.
Now then we can optionally go further
and package up that published version
and make it available through the shared folder.
So once you package something,
it's immediately available in shared.
Or optionally, if someone wants to use
the consumed workflow,
then they can take the extra step
to review the package first,
make sure it's in fact what they wanted
and what they expect.
Consume it and then that copies it to the consume folder
and they can link to it from there.
So now that we remember the big picture
of all the parts that are required here,
maybe we have a conversation with our MEP designer
and in fact we find out that yes, they forgot to publish.
So it's an easy step to forget.
So they assure us that they will go ahead
republish the model and create a new package for us.
So let's assume that that conversation is taking place
and that those steps have been done by our MEP designer.
And let's go back to BIM 360 and take a look.
So I'm back in my design collaboration module
in the architecture team space.
I will expand my swim lanes once again
and on the shared timeline,
you will now see this little hybrid symbol up here.
And it's actually multiple nodes in the same spot.
So you see that little three badge
indicating that there's three nodes there.
And the symbol is half colored and half white.
So the open part indicates that there's
an unconsumed package in that bundle of nodes.
And the colored part
indicates that there are some consumed items in that bundle.
Well, you can see it much more clearly
If you just simply click on that node.
That will expand it in zoom in on the timeline.
Over here on the left
we can see the parts we've consumed
our previous package and our previous model.
And then over here on the right,
we can now see the new unconsumed package
that MEP created for us.
Now, at this point when we select this,
we don't want to be too quick
about clicking the consume button.
I know we had the conversation with MEP
but let's just verify just to make sure
that everything is as we expect.
Well there's an explore button right here.
So I really encourage you
to get in the habit of using explore first.
Because you can preview the contents
of the package here in the browser
before going through all the steps in Revit
only to realize that it's not updated properly.
So already I can just glance at this model
and tell that there are some changes.
But there's a wonderful tool right here called show changes.
And when I click that,
it will load up a special change visualization mode.
So one of the interesting things you can do
in this visualization is expand the timelines
which have previously collapsed themselves
And notice that on the timeline,
it will actually highlight
the point that you're currently looking at
and the one you're comparing to.
So it gives you a nice visual
of the two points in time that you're currently comparing.
And then you can just close out of there
when you want to give the visualization more space.
Now what the visualization is showing me is graphically
the things that are the same,
that have changed or that have been deleted.
So you can see that in green,
it's showing me new elements.
In yellow, it's showing me elements that have changed
like that long trunk duct going down the space there.
I don't have any red elements.
So nothing's been deleted
and the stuff that's sort of ghosted in
is all the stuff that remains unchanged.
So you can further study this
and look around for changes
and certainly in a more complicated model.
You might want to spend some more time in here
but I've now seen enough to be satisfied
that I'm looking at the latest version of this model.
So I can come up here
to this exit Changes button right here
and that will close the visualization.
And then I want to look at one more thing here.
If you look over on the left hand side,
there are several different icons here
where you can look at the teams
or the issues and so on.
Well this one right here,
is called the Content Browser.
And if I expand that,
there's an additional item here called documents.
And what I wanted to show you here
was that you can actually attach
other non Revit documents to a package.
Now we actually did this in a previous video
but we never really saw where that came into play.
Well in this case,
the MEP designer has attached a PDF to this package.
And if I just simply click it here,
that will actually open up another browser window
and allow me to look at it
and it's just sort of a schedule here
that's kind of listing out some information
about the Ductwork.
So when I'm satisfied
that I understand what's in that document,
I can close out of that window.
Now that I'm thoroughly satisfied
with the contents of this package.
I can go ahead and click Consume
and then I'll click consume again.
And now I'm ready to go back into Revit
and reload the link.
So as I did before,
I will just go to the link here
on Project Browser.
Right click it, choose reload
and after a moment or two,
we will now see the latest changes to the MEP.
It can definitely be a little bit challenging
to get this workflow under your belt.
If you choose the consumed workflow,
it is certainly the one that requires
the most amount of effort to maintain.
But I think like most things,
once you get the hang of it,
it's really not that big of a deal.
You just have to remember
that if you're the one creating packages,
it's two steps you publish first,
then you create a package.
And if you're the one receiving packages,
you want to review that package.
That's best practice.
And then when you're ready, you consume it.
Okay, so there's something for both
the creator and the recipient to do.
And again once everybody
kind of gets the hang of that workflow,
it should move very smoothly.