Maximizing Your Time: BIM 360 Glue Tips and Tricks

ZANE HUNZEKER: Well, we've got the doors closed now, so how about we get started? I'm Zane, everyone. Hello. Welcome to the second day. Not everybody looks hung over. It's a good thing this class isn't tomorrow.

All right. So I'm the VDC Manager for the San Diego division of Swinerton. We're the number one contractor in California and San Diego by a large margin. We have roughly $900 million worth of work going on in San Diego County alone. And we have adopted Glue enterprise-wide for the past two years. So we have learned a lot definitely. And we're here to share that with you today

ANDREW RAMIREZ: Hi, everybody. I'm Andrew Ramirez. I'm the VDC Engineer at Swinerton San Diego. So I basically help out Zane with whatever he is busy to do. And basically, I'm fairly new to the company. And so since I've been there, I've really only dealt with BIM 360 Glue. So I've been able to pick up a lot of this stuff pretty fast because it was basically the only thing I had access to to begin with. It's a lot [INAUDIBLE] to there.

All righty, so to start off our presentation, we're going to give a quick overview, sort of intro. I guess we could start off-- I mean, has everyone here sort of used Glue before? I'm sure there's people that haven't.

ZANE HUNZEKER: Because Glue's really frustrated.

[CHUCKLING]

ANDREW RAMIREZ: OK, yeah. So this first part is sort of just an intro-- the real basics, for those who have completely pretty much not used it. File types that BIM 360 Glue takes-- if you have to use Navis at least, it's very similar or exactly Navis because it's basically Navis, but cloud-based.

So pretty much any 3D, 2D file you can think of, you can put on Glue. Revit of course, you can put it on the Glue site for download. That's very nice when you're using files to transfer. But of course, you can't put it in the actual merged model. But, yeah, all the NWCs, NWDs, DWGs, anything you can think of pretty much, you can put it on there and work it into a merged model [INAUDIBLE] in some way.

As far as the size limits, we've sort of looked into it. I haven't seen a specific number, but it lands somewhere around 150 megabytes. That sort of varies, I've seen and heard, depending on your internet connection and your computer or your hardware. But somewhere around there, you kind of want to keep it below that. Anything larger than that, it can kind of struggle with, especially if you have multiple large files, of course, in a merged model. That size limit per model.

As far as the hardware, the nice thing about Glue, it can basically run on very simple computers. Our field team has iPads that use it. So it can be run on there. But of course, the caveat to that is if you're running anything very large, it's going to struggle.

That has to do with your hardware but as well as your internet connection because it does have to go up to the cloud and download this information. So if you don't have good internet speed and a sort of beefier computer, if you're trying to deal with something fairly large, then it's going to have a problem. But if you are working in VDC and hopefully have that computer, it can pretty much handle anything we've tried to throw at it fairly smoothly.

Folder structure-- we threw this in here. We thought it was pretty important. This is an example of one of our projects-- how our folder layout is. It seems like something simple and can be forgotten, but especially when you're dealing with a program like Glue, how you set up your folders can be pretty important, especially if you're trying to collaborate with other subs that never use this program.

You really want to make it simple for them. Come up with a folder structure that works for them and for you to find files, and they can easily upload to the same location every time you guys upload. So as you can see here, we have all the trade layouts and where we put the design files. And then we usually have a subfolder broken in there if they're giving us NWCs or DWGs or whatever that may be.

And with this, of course, naming convention is key as I'm sure a lot of you may know. Come up with that naming convention along with the folder structure very early in the process. Make sure everyone who's uploading knows it, because, yeah, getting a sub that's going to-- or whoever may be throwing a file in there with the date just doesn't work.

So, yeah, if everybody has the same name and keeps that name throughout the life of the project, that's going to be best. Because that gets the file back in the same spot. Wherever you put it, whatever merged model has that file, it's going to load back into the exact same spot.

And the nice thing about having a cloud-based system is once it's up there-- of course, depending on your internet, it could take a few minutes. But as long as it has that same file name, it's going to be really nice and come back exactly where you had it previously.

So some of the admin that comes with 360, there's user types that you can assign with a lot of-- I'm sure if you use any other 360 programs, there's four that come with BIM 360 Glue. They are a Project Admin, a Full Member, a Limited Member, and a Reviewer. So I'll give some of the details that come with that.

A Reviewer is just what it sounds like. They can literally just view the model. They can't really edit, touch anything, move anything, or adjust anything. But so anybody who just wants to see the model, that's perfect for them.

Limited Member-- they're able to upload models, but they can't delete anything. They have some very limited access to the clash detection, but it's really just for someone who's going to upload models and have someone oversee them, pretty much from there.

And the Full Member is more when you have-- whoever can view the sub, that's more interactive and it's going to actually handle their own models because Full Members are able to upload models, delete their own models, run clash detection, and everything else that comes with Limited and Reviewer-- view the model, all that normal stuff.

And finally, Project Admin has all those rights. But the biggest difference is they handle who gets to see this project. So they're able to add people, delete people, and basically see the back end of what user type every person who has access to that model is.

So along with User Admin, just a quick note-- if you've ever been on Glue or you have it, usually at the top, it looks like that little toolbar. And the administration button is a quick link to your User Admin. And of course, you only get to see that if you are a Project Admin.

And on that page, you get to see everyone's name who's been added to the project. And you're able to add people. So this is what the add page looks like with a quick screenshot of that. You're able to-- if they're already in your system, it comes up much faster. You can type a person's name. And if they've worked on projects with you previously, it looks just like that, or you could just add their email.

It sends them an email. It'll come straight from Autodesk. And it usually has a link, and it tells them if they don't have an Autodesk account, they'll have to make one. And they'll get Glue on their system. And then automatically, that'll be their first project that they have on there.

Final thing, personal preference. So this is what BIM 360 Glue looks like. So personal preference-- we put this in here just to give you an idea of some of the ways you can mold BIM 360 to your liking. And the reason we did this is because we notice even just between us two or other divisions or other people we've seen-- their Glue screens. And everybody does it slightly different.

So what you see on the screen is you have the black bar on the side which is all your windows. You have Measure, Models, Views, Clashes. So that pops up each window, but you have the ability to dock like most other programs. So that's what you're seeing here. You can dock on either side.

So if there's any windows particularly that use every program, it'll probably save you time not having to open that window every time. So like, Views, I use it all the time. So I usually always have it docked on one side. And you can dock multiple windows to one side and flip through those. Or of course, if you have two screens, you can move stuff between screens. So that's sometimes helpful as well.

ZANE HUNZEKER: So clashing in Glue. Has everybody actually clashed in Glue that's used it? What's the number one complaint? Just [INAUDIBLE].

AUDIENCE: [INAUDIBLE]

ZANE HUNZEKER: It's what?

AUDIENCE: Clicking on the actual list to get the clashes could even one clash [INAUDIBLE] all the way down-- all the way.

ZANE HUNZEKER: OK, so we don't have a tip on that. That's everybody's complaint.

ANDREW RAMIREZ: That's how it is though.

ZANE HUNZEKER: That's an Autodesk thing that they're trying to fix for 2.0 for those of you that are in the secret room meetings somewhere else. Was there another one? No? Yeah?

AUDIENCE: Goes exactly to the clash.

ZANE HUNZEKER: Going exactly to the clash? Just coming up and going back?

AUDIENCE: I mean, yeah, once you find it, it's [INAUDIBLE].

ZANE HUNZEKER: OK. And those--

AUDIENCE: [INAUDIBLE]

ZANE HUNZEKER: I have something for you.

AUDIENCE: The number of clashes?

ZANE HUNZEKER: The number of clashes. So we have more things for you too. OK, so we'll get into this. All right, so typically, organizing your clash tests in Navisworks-- if everybody is familiar with Navisworks, you have mechanical duct versus plumbing, mechanical duct versus mechanical pipe. And you end up with 15, 20 clash tests a lot of the time. It's a great, concise way to organize the data. And that's fine in Navisworks because you can hit the Update All button.

There is no Update All button in Glue. It takes a few minutes-- not a few minutes. It takes a few seconds to open up and update the clash. So that's typically a complaint with everybody because there's no easy button for updating.

ANDREW RAMIREZ: But when you have a lot of clashes, it takes a few minutes.

[CHUCKLING]

ZANE HUNZEKER: But when you have quite a few clashes, it does take a few minutes. So what we propose is you kind of organize this to where you only have five clash tests. And you can do that by organizing mechanical versus plumbing, fire, metal stud framing, electrical, and steel, or steel versus everything else, or framing versus everything else.

And then you'll just rotate around. So we did mechanical. Mechanical is covered in every direction. And then we would just rotate to plumbing and have plumbing versus fire, metal stud framing, electrical, and steel, and then fire versus metal stud framing, electrical, and steel, then metal stud framing versus electrical and steel, then electrical versus steel.

And that effectively completes the matrix. And so we have an example of that here. You can see that we don't have metal stud framing or steel in level 1 in this. It's a hotel that the level 1 is actually just parking. And so we end up seeing that we have mechanical versus electrical plumbing and fire, electrical versus plumbing and fire, and then plumbing versus fire. So that effectively completes the whole thing in half or less of the clash tests.

And then the clash grouping itself, which is one of the complaints. There was far too many clashes in the user interface when you click on a new clash, it zooms out, zooms in. And you kind of lose perspective. So the initial clash grouping you can do with the bigger column in the middle there.

And then the secondary grouping goes one layer deeper. So if you pair this secondary grouping with the way that we organize our clashes to where we have actually fairly few clash tests themselves, you can still break it out into the exact same level of detail that you would have in Navisworks with the 20-some-odd clash tests. And administration of these clash tests is how you keep track of everything. And we'll get into that in just a minute.

So we've talked about the grouping and the secondary grouping. And why do we do this? One trade versus the rest is purely because it takes 30-some-odd seconds sometimes to update a clash test. So we're saving ourselves. I don't know why. I think we did the math one time and it saves us an hour per clash detection meeting purely by taking the 15 tests to 5, just on waiting for it to find all the clashes.

Because what it has to do is it has to go up to the cloud, pull all that information, come back down, do some other hoodoo voodoo. I'm not a computer programmer, so I can't fully explain it. But, I mean, probably the first time you go through the clash test when you're new, or you're new and just got all the information, it probably takes the longest.

But the thing that we're trying to show with this is-- I mean, you can clearly see when you pop open that list, it shows you the numbers of each of those groupings. And from there, you kind of come up with a system. And then that will follow level to level. So once you have it set up once and you kind of know which files to group, [INAUDIBLE] makes it very fast when the next time you've got to look through the clashes.

ANDREW RAMIREZ: And you sort of just come up with a system that's like--

ZANE HUNZEKER: Right, and you have to keep in mind what files you're clashing. So if you have a fab MEP file that has plumbing fitting that has 17 polygons in it, it's going to show up as 17 redundant clashes. So this grouping, if you're lucky enough to have some trades in Revit, you can group by the Revit files, the NWCs. Because those are solid components. They're not broken up into a bunch of different little ones, right?

So in this grouping, you can see that we have-- this HOTEL LEVEL 01 is our mechanical file. And it has filtered through clashes with the electrical level 1 file. And there are 68. So that's total clashes with that one. But once you group it, it turns out being grouped into, like, 10 or 12 sometimes. Or you know what I'm saying though, right? Because some of you have a clash grouper in Navisworks potentially and it works very similarly. Yeah?

AUDIENCE: Distributing setting up the NWC is the best [INAUDIBLE]?

ZANE HUNZEKER: Whichever file has the least amount of polygons, right? So it could be a DWG. For instance, I believe the conduit in the CAD MEP is actual pipe, not seven polygons wrapped around into a circle.

But other programs like CAD sprink-- the fire sprinkler is made out of 17, 18 pieces. So when you have a register that would be one piece in Revit and that sprinkler, you're going to come up with 12, 16 of those pieces are clashing. So this filtering and grouping gets you to the point to where you are automatically reducing the number of redundancies. It's a major time suck trying to filter out all the redundancies.

ANDREW RAMIREZ: Yeah, it makes that view much better. I know someone said about just the amount of clashes-- when you even just if you're going through the views or just flying through the model just trying to get a scope of what's going on there, it turns those little orange dots from a big old blob to little tiny groups. I mean, obviously it's only one dot, but, yeah, it makes it much better for viewing.

ZANE HUNZEKER: And the way that we kind of keep track of what clashes we've actually viewed and what clashes we've either made a markup for or made a viewpoint for saying that we've actually addressed the problem, or that we've created some sort of visual aid to help us address the problem in the coordination meeting, we actually go through and take the group and we add a comment to it.

And so very quickly, you can see kind of in the top right-hand corner there-- this thing doesn't have a laser pointer.

ANDREW RAMIREZ: It does.

ZANE HUNZEKER: Oh, it does. Nice. OK, so, right there. That your comment button. So you're going to be able to comment across 21 clashes. And all we do with that is we say, reviewed. Save it. And then in the clash results, which we have here, there's going to be a orange little thought bubble or conversation bubble right there in the clashes that have it.

So no matter which way you group your clashes after the fact, you know that the ones that have a little orange tag have already been reviewed. So that way, you're not going back and retracking. And that's a good administrative way to really hone in on where you're going.

Transparency-- was that transparent views? Yeah. OK, so that transparent views-- I think you said that. If you keep this-- whenever you click on a clash, there's this pane that comes up-- this big one up here. Don't close it. It goes semitransparent, right? And that's a major worry for a lot of people because it's hard to see. It sucks trying to visually see that.

So if you click this button right there, it makes it from transparent to the normal appearance. And as long as you don't close that window after you've switched that setting, it will stay in your regular graphics, which that took us a long time to figure out a couple of years ago. But it definitely changed the way that we were going through that.

All right, so the major timesaver is limiting your clash tests. It's always updating the clash and the actual results at the same time. So one thing that you probably don't know-- and I didn't figure it out for probably six months-- is that clicking on the name of the clash goes right into the model, and it doesn't actually update the clash results.

If you click to the side over here and you have this orange or yellow dot, that means that something has been updated. So as long as you click over here first and then select Update Results Now, you're opening the clash and updating at the same time. And we found that that is more or less the exact same time as just opening the clash. So that saves you--

AUDIENCE: [INAUDIBLE] in those two arrows. There will be--

ANDREW RAMIREZ: They'll refresh.

ZANE HUNZEKER: But it doesn't open up the model.

AUDIENCE: [INAUDIBLE]

ANDREW RAMIREZ: The clash test-- it doesn't open up your clash list though, right?

AUDIENCE: [INAUDIBLE]

ANDREW RAMIREZ: But, OK. I'm pretty sure the--

AUDIENCE: [INAUDIBLE] figured out kind of couple of things [INAUDIBLE].

ZANE HUNZEKER: Yeah, right. So anyway, make sure you're opening them and updating them at the same time. Because that's a big problem if you just select over here.

ANDREW RAMIREZ: And especially, like-- I don't know about your guys' job, but for us, sometimes we have to show BIM 360 Glue to some of the subs who are not too sure about it or our project engineers. And things like this is very helpful, especially if someone's really against it. Because, yeah, one of the major questions we would always get is like, there's no Refresh All button. Like, yeah, we know. We deal with the same problem. So things like this can help them ease that process a little bit.

So the final couple of tips for the Clash Detective is to group everything mindfully. Really think about what file types you're actually getting into. And maybe try it both ways. I don't know. Sometimes you end up with different results.

Customizing your UI to fit your needs and wants-- if you have multiple screens, you can actually detach each of the modules to another screen. So that's always helpful to have as much of the model showing at the same time.

And then the Transparency Toggle button is a big one too. As long as you keep that one window open, it will always stay that regular graphics. I'll put this here again. That's the--

ZANE HUNZEKER: Yeah, so it's that button right there.

So one way for doing the coordination is markups. It's what Autodesk prefers you to use. It's a preferred workflow, as it were. Has anybody tried coordinating with markups? Looks like a couple, OK. The only problem is that if you have some trades that are not in Glue and don't like Glue and they wanted to use Navisworks, none of the markups go into Navisworks, but the shared views do. So that's a tip that we're going to go over later.

So using the standard markups, they're different from clash markups because they don't have the name-- kind of different. They don't have the name of the clash in them. You rename it whatever you want. It could be something as simple as something floating. So it doesn't actually show up in the Clash Detective because it is physically not touching anything else. So it's more of a constructability thing than an actual clash.

So a lot of these, we will have-- just use for communication. We went through a large airport job. And it took about a year and a half of design work. And we ran the entire design process through Glue. And that's what you see in here. So we had Michael Baker, Morrow Meadows, [INAUDIBLE] Gensler was a part of this as well. And Watry Architects was the main designer.

But we were able to get through DDs and CDs with very few clashes at the end of the process. But, by golly, did we have a lot of updating and figuring it out. But once we did get to actual construction coordination where we had the trades that weren't contracted underneath the design build-- once they came on board, it was two weeks, three weeks of coordination, and then we were done and out.

And the best part is even if you're not co-located, you can easily just hit the Glue It button if you're in Revit it or the Append to Glue button in CAD MEP and a few others. And it's so seamless, especially in AutoCAD. Most of the AutoCADs, you can actually append from Glue into your model.

And as long as your AutoCAD model is the same 00-- which it should be. I don't know why you wouldn't. It actually lines up perfectly. And so you can actually model around the other guy. So there's no reason for dragging clashed detection on. That's what I get most frustrated at.

And then the Clash Markups should be done in the Clash Detective. They're always coming out of the Clash Detective. They have that little pencil mark. And that opens up a clash, and then it names it, and puts it underneath the Clash Markups folder right there.

And with the same kind of folder structure as you would have for files, we'd like to the same folder structure in markups. It's very simple. It's simply just the trade. And then underneath the trade, we have a Resolved folder, so that way, no matter what, we still have what they did and when. It's just keeping track of everything.

AUDIENCE: So the markups-- are they in a central folder in the group? And I file notifications for that.

ZANE HUNZEKER: Yeah.

AUDIENCE: Look at this hanger. Look at this. This looks like the [INAUDIBLE]. And I couldn't bring up on the phone, but on the desktop, if I don't have Glue open and click on the link, it'll--

ZANE HUNZEKER: Open the Glue for you? Yeah.

AUDIENCE: So I'd be logged in. I wouldn't see that one coming. And then the next email-- put the the same link and wants me to-- it opens up another session in Glue. Is there a better way to open up Glue and find the list of file notifications?

ZANE HUNZEKER: You can filter them by "assigned to you," I believe, or notified too-- notified by.

AUDIENCE: So I'm using the email that I receive?

ZANE HUNZEKER: Yeah, I believe so.

ANDREW RAMIREZ: Yeah, I think part of that is what we're trying to get across where whoever set it up could potentially fix that problem. Obviously, I understand in your case that's-- you're on the other side, right?

So, but yeah, hopefully people understand the importance of that folder structure. And just like you're saying, to help whoever you're sending that to not have to go through multiple emails and you just have one folder to go through. But, yeah, in your case, I think the best thing would be an assigned-to filter. But, yeah, it should really be a dedicated folder to whoever--

ZANE HUNZEKER: Needs to look at that [INAUDIBLE] to your specific company.

ANDREW RAMIREZ: Yeah, so you need to open it one time.

ZANE HUNZEKER: But you don't have to hunt for it. That's just administratively a better way to do it. So the clash detection markups, as you can see, it gets interesting after a little while. And they're all typically for the construction phase, I don't do a whole lot of hard clashing in design unless it is design-built. Typically, the architects don't like to see 50 viewpoints a day on why.

But once the clash is run, you can group them. And then like we did before, you can't actually mark up a whole group. That's why we said that you should do the comment per the group. You have to mark up one in the group or multiple in the group. It doesn't matter.

But as you mark up, you can actually edit the markup. And it keeps a history. So you can see that right here. I started it out. One of our project engineers, Luis, kept going with it. And the fire protection main progressed and progressed and progressed until we ended up with where it is now.

So that's a nice way to see kind of the history of that issue as well. And that's why we never actually delete these markups-- so that you can see how and why we got there. It's nice in a claims situation.

So again, just to emphasize that the workflow-- and you shouldn't be getting notifications that aren't in your folder or aren't assigned to you. And it's much easier to work as a group if everything is organized. Yeah, and you should make those decisions early on and keep everything really concise.

So as a part of the little tidbit at the end, a lot of people like to use this tool, at least as far as I've seen. You mark up a measurement here, and then you just Save as markup. And then you can go back in and hit that little pencil button. And then you can then edit and add text and whatever sketches you want in addition to that.

ANDREW RAMIREZ: All right, so the clash workflow with markups. So we tried to lay out as best we can our workflow that we've used with markups. So if anybody, like-- I know a few people said you've used the markups before. You can compare and contrast of what you've done and see if anything we're doing can help you out.

So of course, first you start off. You run your clash, right? Keep in mind everything we've said so far to save you time. Update results. Update the results and open the clash at the same time. Try to always remember that. Then you drop into your actual clash test. And hopefully, if it's your first time or if you're ever looked at it, hopefully you already set up a-- or have an idea of what your best group is for each clash. And you can jump straight into that.

So you drop into your group. And then, the most important step, you create your clash. So whether you're doing that through groups or single clashes, it's really the same process. Down in here, whatever clash you need to make that markup for, you just hit that pencil button. And hopefully, you have your view window set up to somewhere you need it to be for that markup.

And it'll pop up the toolbar for Markups. From there, you can do your circles cloud, whatever you may be, and your text. Once you hit Save on that, like we've said so far, it's going to jump straight into that clash markup. So if you haven't had one, it'll make one for you. And then if you already one, it'll jump into there. So that's actually the one that jumped in there.

So like some of the things we just said, one of the important steps now-- at least for us on the creator side, I guess-- is to move that clash into the applicable subfolder. And sometimes we may even rename clashes if we have more information behind it or have suggestions, but this is sort of an important thing to help everybody out-- keep organized and not just have a list of hundreds of markup clashes there.

And then an intermediate step, which sounds like that's what happened to you here, is if need be, you can notify basically anybody who's on the project but whoever needs to know about this clash or who knows about the markup on this clash. And you do that with that little email button right there. And then that will pop up everybody who is associated with this project. And it'll give you the ability to customize a little note to them.

But if you're not doing that, usually you're reviewing it in a meeting. That's how our process goes in a GoToMeeting. And you go through the markup that's made, either make more notes to it, sort of like the one we just saw. It sometimes keeps going-- and hopefully come up with a solution. And then from there, you resolve it.

And then finally, like we were saying, to keep that record, especially if multiple things have happened to this markup, it's nice to have that folder structure and have a Resolved folder for every assigned folder. And from there, you can move it into that Resolved. And that's the end of your clash workflow using markups.

So next section here, I'll jump into--

ZANE HUNZEKER: You have a question.

ANDREW RAMIREZ: Yeah?

AUDIENCE: Quick question. For the markups, [INAUDIBLE] multiple folders [INAUDIBLE] folders into folders [INAUDIBLE] ended up [INAUDIBLE].

ANDREW RAMIREZ: Like other people on the project moving the folders for us?

ZANE HUNZEKER: It happens occasionally, but most people are careful enough. Yeah, just like that gentleman right there. No.

ANDREW RAMIREZ: Yeah, I mean, most of the time, we're doing all that. So they-- whoever else, at least on our end, we're handling most of it. I mean, we're usually creating that markup or marking it up. If they sometimes they have an answer, they might mark it up too, but at least for us, the subs we're doing don't usually mess with the moving of clashes. They might let us know that they fixed it in the median, or whatever that may be. So not too much problems. Yeah?

AUDIENCE: [INAUDIBLE]

ANDREW RAMIREZ: Yeah.

AUDIENCE: Are you [INAUDIBLE] that [INAUDIBLE]. So I see that you can [INAUDIBLE] from the clashes [INAUDIBLE]. Usually, a clash [INAUDIBLE] two or more trades at the same time. So how do you [INAUDIBLE] merges it and then you go clashes. Each folder you have [INAUDIBLE]. How do you extrude that into the right folders?

ZANE HUNZEKER: So, experience. [LAUGHS] Yeah, I wish it was that-- no, if it's unclear, if it's nothing that's easy-- so if it's a half-inch water line next to an eight-inch fireman, guess who's moving? But if it is something that needs actual coordination, we'll have a coordination meeting folder. And then we'll review it in that.

ANDREW RAMIREZ: We'll work it through there.

AUDIENCE: Sometimes we may not want to decide [INAUDIBLE].

ZANE HUNZEKER: Yeah.

ANDREW RAMIREZ: Oh, trust me we know.

ZANE HUNZEKER: And, no, that's part of the process sometimes. I mean, sometimes early on in the project, we try to lay out and make clear that we can't-- obviously, in these meetings, usually we were doing a meeting a week. We can't go through everything. So there are some very obvious things and we say from the get-go that we're going to assign certain views that are obvious to us to certain people. And everyone should keep up with those clashes.

And if they're looking at them and they do have a problem with that-- like, maybe we assign something to them and they feel that they can't move it or they might know something that we didn't see right away. So sometimes there's that back and forth, a little bit. But for the most part, yeah, if there's anything really obvious and we have a meeting coming up, we usually put in a coordination meeting and then figure it out there and then move it into the respective folders. Yeah?

AUDIENCE: So we've got one PC [INAUDIBLE] that requires Glue. It was kind of cumbersome because native Navisworks is still a little bit more user friendly.

ZANE HUNZEKER: For you.

AUDIENCE: For me. So what we're using it for is to track our progress and coordination, then the owner, engineer, architect, review what we're doing in coordination. And they don't need a [INAUDIBLE] contractor. So what we did at the same was we do it in Navisworks and we keep popping NWDs on every once or twice a week.

ZANE HUNZEKER: For progress.

ANDREW RAMIREZ: Yeah.

AUDIENCE: --review the progress that way. We're not jumping into Glue. We're just [INAUDIBLE].

ZANE HUNZEKER: Sure. And at the end of this, we have a Navis-Glue--

ANDREW RAMIREZ: Yeah, we'll touch on that.

ZANE HUNZEKER: --workflow that we'll talk about. Cool. So, yeah, I'll jump into views. Has anybody tried to use views as a clash workflow instead of markups?

AUDIENCE: [INAUDIBLE]

ZANE HUNZEKER: OK, so not as many.

AUDIENCE: Do you mean viewpoints?

ZANE HUNZEKER: Viewpoints, yeah. So, yeah, for those who have it, we'll sort of jump into what we're doing. But quickly, if you don't really mess with views too much, when you pop up their window, you have Shared Views and you have My Views. You really want to be using Shared Views. If you're using BIM 360 Glue, you're using it for a collaborative project, usually.

So Shared Views is just views that everybody on the project can see. My Views is only that specific user. So if you're making views just for yourself, it's very rare. But most people probably wouldn't mess with that. So just keep that in mind. Make sure you're making your views in Shared Views.

And then if you haven't created views or sections, this is, again, just a close-up of that view tab. You're going to want to hit that first button there, which is your view. The next one here is your section. And then the Folder button is pretty important since we've talked about folder structure a lot here.

But once you hit that View button, this is usually what comes up. Like I said before, hopefully you have a-- you're pretty close to where you want to be. You can still maneuver before you hit that Save button, but you usually try to get it somewhere where you want that view. And then you put your name down, make sure you're in the project-- that basically means it's going to go in the shared location and not only you can see it. That makes it like a locked view. And then you just come up with the name, whatever it may be, hit Save, and it goes to that list.

A little note there-- to save a little bit of time, instead of just hitting that View button, you could actually-- if you know it's going into a specific folder already, you could hit the folder first then hit the View button. It'll go into that folder instead of making the view then having to move it afterwards.

Creating a section is similar. This is what it looks like. You get the snap button to snap to a specific plane. But you also have the little view cube helper on the side. You can make multiple sections just like Navis. So in this example, I did a little top-plane cut. And then I did a right side. And right now it's on the move, but I also did a rotate because you can see the section's kind of slanted. It also gives you coordinates if you need that information, but it's usually not.

From there, we threw this in here just because we've been talking about that notifying project members. This is what it looks like. Yeah, go ahead.

AUDIENCE: So I have tried doing that and-- using the sections and stuff. [INAUDIBLE] I guess. [INAUDIBLE] upload everything that has every [INAUDIBLE] in there. And a lot of times, when you have that section and you're going through your other things, is there a way to hide things that the right view can't get that view to show, I guess, [INAUDIBLE].

ZANE HUNZEKER: So, I think-- did you touch on that on markups that you can? But on views, you can. So, you can do that. So you can hide-- like and while this is going on here, if you need to hide-- I think I understand. Like if you need to hide a wall, that's something behind there. Is that what you're talking about?

AUDIENCE: I'm talking about upper-right [INAUDIBLE] putting in or something like that. So a lot of the times the new views are available on-- you're looking through a little [INAUDIBLE], or you're looking through other people's [INAUDIBLE]. It's all [INAUDIBLE].

ZANE HUNZEKER: So you can create a side-- just like you did here, a top and a side. You take your top just below the bottom of deck, and then the side to maybe the edge of the room. And then that kind of gives you almost like an [INAUDIBLE] view if you've ever seen Navis--

And it all depends because you can put in six planes in here. And you can make it any which way you want. You can hide things and then save the view.

ANDREW RAMIREZ: You can-- like, I'm sure you know. But anything you right-click, you can hide it. But I think I understand what you're saying. There's other equipment in there. We'd probably would say not to do that. Because then once you start doing that, then people forget that there's something there. So I don't know if there's a speci-- I mean, if you're-- yeah, there's--

AUDIENCE: The best way to [INAUDIBLE] the--

AUDIENCE: [INAUDIBLE] you can't set the transparency.

ANDREW RAMIREZ: The transparency? Yeah. That's really only why you're doing the clashes. So, yeah, if you had during this process, if you have your clash window open and you're looking at a specific clash, this workflow that I'm about to get into-- yeah, you can leave the transparency on. But, yeah, just keep in mind with the transparency option that Glue has, it's really only everything's transparent except that clash. So that's probably the best option.

AUDIENCE: [INAUDIBLE].

ANDREW RAMIREZ: Are you going to answer that?

ZANE HUNZEKER: Nope, go ahead.

ANDREW RAMIREZ: Yeah, so final thing-- once you have your views made, whatever they may be, if you need to notify just like you're notifying about markups in your view window, you just hit that button. And then this is what the window looks like. It looks the same for markups. So that's everybody on the project. You can click on everybody and then write a message, if you need be. Send them. You get an email and a link back to that markup. And it'll open Glue for them. Usually you have to be on a desktop, obviously, or iPad.

OK, so this is clash workflow with views. So it'll look very similar in aspects to markups, but hopefully you guys can catch the differences here. So you start off the same. You're going to run that clash, save that time and group. And then instead of creating your markup, you want to create your view.

So again, you're going to get to whatever clash it may be. Like, over here, we a hanger clash. And then while doing this, obviously, you'll need to have-- so it's different in markups in that the markup you can do-- what we saw in the last workflow, you can do within the clash window.

So with this workflow, you're doing it with views. So you'll want to have the view window open, whether you have two screens in doing that or docking windows. But just keep that in mind.

ZANE HUNZEKER: You're naming the view the clash number and what area it's in so it's clear. A little bit extra work, but it actually transfers into Navisworks, which we'll get--

ANDREW RAMIREZ: Yeah, so it's different in the markups. It's that markups is making straight from the clash window. And then it's naming it whatever that clash just was, then a number. On here, you'll have to make a view and name it. But we've definitely found this workflow to help us out, especially on certain projects.

And here, you'll name it whatever it may be. Usually if we have more information, we'll put it there, but usually it'll just be whatever the two things that are clashing and maybe a suggestion or it could also be numbered if you're going down a list and working through a number, then you give it a name, right that Save button, and then it'll go onto your list, hopefully in a specific folder if you've done that.

And then similar to the markup workflow, in order to know what you've gone through, we use comments for that. So you could also do that with the markups which we've said earlier. But in that little text bubble there will give you an option to comment. And you can actually write helpful comments.

But if you're using it just to denote a view clash, you could write "viewed" on there. And then this helps out because next time you open that clash test, all the ones that you wrote a comment on will have a little orange-filled-in comment. So you can skip those and know that you've already gone through them.

And then at this point, yeah, if you need to, you can get that viewpoint and notify people. But pretty much after this, the process is the same except that once you go through the meeting and come up with a solution and resolve it, you'll move the clash in your views window and not the markup window, obviously.

So that's the difference. But I guess if you want to talk a little bit about our views, we'd definitely do this workflow on most of our projects compared to markups.

ZANE HUNZEKER: Right. A lot of subs are deeply ingrained in Navisworks. And so we use what we're going to call later on in the presentation, Medium Glue. It's not Full Glue. It's not Light Glue It's Medium Glue. And that's kind of where we're going to go into in just a minute here.

ANDREW RAMIREZ: OK, so Glue options is basically just the little options bar that you have, the things you can change within Glue. So first, just the general options, just in case people have never seen it. General and Background are very simple. Just as you can see, these are what the windows look like. You can change very simple things.

Grid lines are sometimes helpful. Certain architects' files-- it could get very hard to see things when you have too many grid lines there. So you should actually turn off the grid lines. But the other options are just to turn off navigation tools which you usually need, so there's no real need for that.

But sometimes it's harder to see certain things. You can change background colors if need be to help you view your model. But Advanced options is really where it's at.