Efficiency Elevated: Automating Clash Detection for Seamless Collaboration Between Architects and Structural Engineers in ACC

MICHAEL ECHAVE: Welcome, everyone. Today, we're going to be talking about-- myself and Matt are going to be talking about "Efficiency Elevated Automating Clash Detection for Seamless Collaboration Between Architects and Structural engineers." And if there's anyone outside of that discipline, don't worry, we're going to be covering from a holistic view of model coordination within the ACC platform.

My name is Michael Echave, and I'll be partnered here with Mr. Matt Linn. He'll take a second to introduce himself first, but let me go through and introduce myself.

My name is Michael Echave. I am an Autodesk certified instructor as well as a Bluebeam certified instructor. I know we're here to talk about Autodesk products. But a little bit of background-- so I start out in the industry doing architectural design, then mechanical fabrication for custom windows and doors and then structural design, which I fell in love with, and that's my passion.

Before going over to Applied Technology Group, ATG is where I currently work. I fell in love with the BIM management role and love providing that type of service for all of our clients here at ATG as well. I graduated with an associate's in applied tech-- sorry, not applied technology-- associate's degree in applied sciences.

I've spoken at Autodesk University the past couple of years as well. The first one I did was virtual, then moving over into in-person. And excited to be in front of you all again, specifically talking about this ACC platform. But enough about myself. I'll let Matt introduce himself as well.

MATT LINN: Thanks, Michael. My name is Matt Linn. I'm a licensed architect. I practiced in the traditional role of architect for about 17 years. While I did enjoy designing buildings, I found that what I enjoyed most was the digital practice in leveraging technology.

So about six years ago, I did make a transition into the BIN consulting role, much like Michael here with ATG. I've done that for about six years. And now recently, I have moved into the Director of Architecture + Structural Services here with ATG. And I am thrilled to be speaking at AU for my third time with my good friend Michael.

So today's presentation, we will hit three learning objectives-- introduction to Autodesk Construction Cloud, gain familiarity with the ACC platform and model coordination module; number 2, configure ACC and Revit for automated clash detection, define clash rules and parameters for seamless workflows; and number 3, collaborative class resolution, best practices for architects and engineers to resolve clashes efficiently. And I do promise this is the only slide we read verbatim.

MICHAEL ECHAVE: I also think we read a little bit about ourselves from a verbatim perspective. But first and foremost, let's talk about model coordination and that model coordination module within Autodesk Construction Cloud. So before we hop in, just be aware this course is specifically around people that have some type of knowledge of ACC in the platform in general from the design end, not from the build end, but the ACC platform altogether. So I just want to kind of bridge that gap here.

If you don't have any familiarity into that, this is going to be maybe a little bit of a high-level overview. But you still will get some items of it, but we're not going in through and talking about setting up Docs, setting up design collaboration. This is specifically on model coordination in that advanced module of going through and designing clash detection built into that module.

So what I wanted to do was go through and give you a little bit of an overview before we kind of detail this. What is the perspective of model coordination? And what does it look like from a high-level, quick little intro of that? So let's hop on in and show you exactly what this will look like.

So once you're in the platform itself of model coordination, you're able to go to clash module, and you're able to see different clashes that are highlighted. You can select into the clash field. And once you're selecting into it, live loading, you're going to be able to actually see a model where it's reflecting both different disciplines or multiple disciplines. It does give you a color code, which is great, and it allows you to highlight these different clashes and go directly into them.

You can actually see issues on this left hand side and identify those issues between two different modules that you want to go through and actually itemize for. And there are some rules and exclusions that you can provide in here to filter out that list. But that's just a little bit of an overview. And I wanted to give you all kind of a perspective of what we're going to be getting into from a high-level view of what model coordination is.

So on to our next one. Next one is going to be talking about model coordination setup. Great. So we liked what you just showed us. We're here to learn more about it. How do we go through and set up this process within Autodesk Construction Cloud platform?

So first and foremost, we need to go to the model coordination module, and we need to go through and set up. So let's hop on in and show you how we can set up this internally for our teams. So first and foremost, you go to the model coordination module.

From there, you're able to go to Settings, and then you got to create a coordination space. So within the coordination space themselves, there's a couple different ways that you can create spaces to coordinate models against one another.

There is a private space, and then there's also a team space that you can coordinate from multiple models. Let's go through and create a space. We're going to go through and call this central. Oh, if I could spell right now. Don't worry, there's spell check, which is great-- coordination and space. You can go back and change this.

Next one, what you want to do is pick the folder, file folders that you want to actually coordinate against. So that allows you to go through and pick and select the different folders that you have pre-created. Now you can do the entire folder structure of whatever files are in them, but let's say you're doing a different kind of coordination between consumed files. You want to go into those subfolders themselves.

Now, this is the automation part. Do you want to automate this clash detection? Of course. I don't know why you wouldn't, but they give you the option to have it on or off. But again, you do get to select this at the beginning of this. So let's go through and create this.

Alrighty. So now that we're in this coordination space under Settings, you can see that the space has been actually created, and we're leveraging some files that we're going to get into later on. So again, just bird's eye view of what we're going through and utilizing from this perspective of models. We'll get into that.

But you can go through and create additional spaces if you needed to. So you're able to go through here and create some more. But let's cancel right out of here, and we're going to go through and talk about some settings.

So you can rename this at any point. You can view details of this as well. So you can see some information that's kind of built into here in terms of his automatic clash on. You can even edit your subfolders if you needed to.

So let's say we weren't actually going into the right subfolders that we needed to. You can actually change that from this perspective. So if you messed up at the beginning of the wrong folders, don't worry, you can go back and change that. So let's go through and cancel out of here.

And you can deactivate. So if you ever needed to deactivate a space, you do have that option. If you're no longer using it as a coordination space, you can go through and hit deactivate as well. So let's go to close out of here. You have status. It's active. Auto clash is currently on and then who was it updated or created by from that perspective as well.

Great so next, what we're going to go through and talk about is different spaces. So let's take a pause here. There are different types of spaces that you're actually able to create. The method that Matt and I chose for this was to create it from one single model. So this is from the architectural space.

That way there's more control on what is being clashed against. And that way, we can create rules and exclusions about that in that specific area. Again, what we're trying to do is create one single space so we're not having fragmented data and out-of-date data. So from this perspective, we're using the architectural team space to create a private coordination space.

Now, there are other ways to go through and do this. You can go through and create what's called a shared team space, and that's more of a formal coordination. There's just a lot of kind of BIM execution plan coordination that you have to do with the other teams to make sure they're publishing their views correctly into the model coordination area. Well, it's just publishing your views, which gets translated, translated into that space.

So be hyper aware. We're doing a private space because Matt took this time to create the proper coordination views and filters that you'll learn later on to go through and do this. So let's move forward, now that we've talked about our different spaces.

MATT LINN: Great. Thanks, Michael. So now we'll move into the learning objective 2 portion with the configuration of Revit. We're going to start with scope boxes because it is important to go ahead and break down projects down to scale.

So most of you probably recognize this project. This is the default project that comes out of the box with Revit. And it is a series of buildings. There's five or six buildings on-site. And so what I like to do is create scope boxes. So when it comes to the coordination and clash detection, you can isolate it down to one area.

So I'll quickly just create a scope box here. In addition, naming convention is extremely critical. So I like to give it a prefix of something that I'll remember. So for this presentation, I'll use coord for coordination and then underscore which structural bay it is.

So for example, structural bay 1 to 2 for that. And then so when I jump to my 3D view, I could easily isolate and silo out that section, jumping to the scope box, coordination 1 to 2, and we can jump right there. Now, I've already set up one called coordination 5 to 6, which will be the structural bay we'll use for the balance of this presentation.

OK, now we're going to jump into views and view templates. What's important here is to maintain a consistent naming convention. And as Michael mentioned, it's great to link everything into one file.

OK, so here's our structural bay 5 to 6. Now, as I mentioned, I like to link everything into the architectural model. I'm an architect. This is the one I feel most comfortable in. And you can see I have all of my model elements turned on.

Now, I like to turn off annotation and analytical. And you can see all of the links are linked in here, and I'll go ahead and turn them on. So at this point, you want to go ahead and add any graphic overrides that feel right.

Now, for me, I like a gray gradient. It has a nice, soft feel to it. Again, that's totally just a personal preference. Do whatever makes sense for you. And then after you get the graphics, what you want-- I recommend making a view template.

Again, sticking close with that naming convention, we'll call this coordination. And I recommend keeping all of the buttons checked with the exception of the VG overrides, or Visibility Graphics override, because this is where you will control what elements are on or off. And then all the others are simply graphics.

So with that, we'll go ahead and take this view and duplicate it. Again, remaining consistent with naming convention, I'm going to rename this as coord underscore and then give it the structural bay of 5 to 6. And then here you would indicate the discipline for which this view is representing.

Now, in this project, I'm going to go ahead and apply that view template. In this project, the project browser is being governed by view type. So because of that, I'm going to make a view type, specifically called coordination. If you're not portioning out your project browser by view type, then just do whatever makes sense.

Some people use a username folder system, which is great. You can do that. Just keep it nice and organized. So here are all of mine. They all, again, have that same consistent naming convention. This one is coord 5 to 6 all. So this is all of the links turned on.

OK, if I jump here, you can see all of the modeled elements are on, and all of the links are on. And it does have the view template applied. Jump next to the architecture view.

Now, here you can see all of them are turned off with the exception of facades, because facades is indeed architectural. Now, the consultant ones are a little bit different. Now, again, you could have made a siloed file and linked in all of the links and then turn them all off or on. But I'm live in the architectural model.

So for the consultant views, I come in, and I turn the visibility graphics. I make sure that link is turned on for the electrical. And then my model categories, you can see they're all turned off. And that's how I turn off the architecture. If it was its own link, then you would simply turn that link off. So you can go either route.

To me, it makes sense to go live in your model. That way, you're not having to jump and open up the other RVTs. So here, you want to come in, make it custom, and then you're going to override these to on because, by default, they are by host view, which, as you saw, was essentially turned off. So we're overriding on for all the consultants.

The structure one, I haven't set up yet, so we'll go ahead and apply that view template. You can see, again, the model category is off, which is what turns off the architecture. We will go ahead and turn on the structural link.

And when I say, OK, we still don't see it again. That's because I haven't overridden them to back on. They're by host view. So make that custom, make this custom, and then override everything to On. Like so, check all, check. OK.

Here's our structural model. Now, for this one, I'm going to take it a step further. So at this point, I'm going to explain in a Revit view becomes an ACC model, and that's how you run clash in coordination. OK, that's like the most critical piece. I'm going to say it again. A Revit view becomes an ACC model, and that's what we're running against each other for coordination.

In addition, any overrides or graphic overrides you set in Revit transfer to ACC. So because of that, I'm going to do a solid fill red overlay on the structural model. That way, the structure will pop with that red, not only here in Revit, but also in ACC. All right, I'm going to come in. Go ahead and select this floor.

Now, this is a little bit outside of the intent of this presentation, but you really need to have an upfront meeting with the architect and structural engineer, and all the engineers, for that matter, and determine who's modeling what. Because in this instance, both the structural engineer and the architect modeled floors, which is bad practice. You need to define who's doing what.

In the past, I have always done-- if it's part of the structure, meaning if it's part of the diaphragm, then the structural engineer would model it. So that'd be the deck essentially and sometimes the concrete topping. And then the architect would take everything above that. So the finished floors or non-structural topping, for example. So for this, I'm simply going to hide that category because, again, whatever overrides we have in the view will translate directly to the ACC model that we run clash against.

Next, we're going to jump into interference checks. And while interference checks isn't in line with ACC clash detection, it's just a quick way to quickly run interference check exclusively within Revit. You can see you can do it current project against current project and you choose whatever categories you want.

In this case, I'm going to do current project against structural and I'm going to do walls against framing. I'm anticipating a lot of interferences, which you can see here. Don't worry, I'm not going to go through them. Let's do one where we can expect to see less.

So I'll do current project. Again, you can do current against current. So I'm doing casework against furniture. None detected, so let's just go ahead and create one.

So I'm going to zoom in here to the cut section. I'm going to grab this piece of furniture, this bookshelf, nudge it over so it's clearly overlapping the casework. We can see like that. And I'll just quickly run this interference check with the same parameters applied, meaning current project to current project, casework category to the furniture category. And just like that, you can see it found that one.

If you select it, it will highlight it in the model here. If you select it individually, it selects each element. Or if you hit the Show button, it'll take you directly to the interference, OK? So not through ACC, but a quick way to run any type of coordination or clash detection exclusively within Revit.

OK, finally we get to the Publish Settings piece within Revit. OK, so you're going to come up to the Collaborate tab. And here are your publish settings. And this is how you're controlling what you're pushing out from Revit to ACC.

If anything's unchecked, it's saying, hey, if you publish now, nothing's getting pushed, which is fine. So we want to have a set exclusively for coordination. So I'm going to do a new set. And before we get to that, let's just do one-- let's say we wanted to push out all the views in the model.

OK, so the first thing you do is give it a name. And you want to be name-cognizant. So views in the model. And I'm going to use this filter to say views in the model and then simply say Select All and Save and Close. It'll give me that same error because none of them are checked. So if I were to publish now, it would push out all the views in the model.

What if we wanted all the sheets in the model? We could do that same process. OK, so you'd come in, create a new, give it a name, sheets in the model. Then come through with the filter to show only the sheets in the model. And then you could simply say Select All and then save and close that.

OK, so now if I were to publish, it would publish all the views and all the sheets in the model. So for this presentation, we really want to be more strategic about what we're pushing out. So I'm going to make a new one, clash detection.

So now, since we have that nice naming convention, we can actually search it with chord underscore 5 to six. And now quickly, all the views populate. OK, so now I can say Select All. And I'm going to pause for a moment.

So if you recall, all views in Revit translate to models in ACC, and that's what we run against. So we only want the specific items per discipline. So we're not going to want the one that says All or the one that says Discipline. We want the specifics.

And now we have Arc, elect HVAC, plumbing and structural. And I only want to push these out and when I publish. So I'm going to save that. And that all looks good. So I'm not pushing out all the sheets and the views, only the clash views.

OK. You always want to sync before you publish, so I'll go ahead and sync. I compact central every time. It says it takes longer, but I don't think it does. Well, it doesn't if you do it every time because it's already tight.

So I'm going to jump to the home screen. And we can see right here that it is not published. We can see by that blue lightning bolt icon. So I'm simply going to come here, Publish Latest, Publish.

OK, here's a neat button a of people don't know about, but it's View Online. If this is right here in your Revit home screen, if you click that, it'll take you directly to the ACC project, which is kind of nice.

OK, so here if I go to the Architecture folder, I can see, we are currently on version 5. I'm publishing right now. The date is set to that. OK, we can see it working. And now we can see it's been updated to version 6. And that last updated date has been updated as well.

So this is obviously going at the same time both in Revit and ACC. I'm just showing you that it is going in tandem. All right, so we'll go ahead and verify that's been updated. Minimize it, come back here. We can see that green checkmark. We know it's complete. The date appears to be the same, so I'll go ahead and hit Refresh. And now we can see that date has been updated as well.

MICHAEL ECHAVE: Well, thank you, Matt. So kind of a high-level view of where we're at. We went through and created a space. We picked the project files and folders that we're going to leverage from a model perspective. We found the most efficient way to do this is creating it from a single model source that Matt just did. Otherwise, you have to coordinate and make sure people are publishing views in a specific way.

Matt went through and detailed how you can go through and publish those views into what we see in ACC as models. One of the great things about that, and that I'm going to show here, is the ability to go through and create model views and publish them even into Docs, because we need to be aware in order to get model coordination, you do need a BIM Collaborate Pro license to access model coordination or BIM Collaborate license.

Now if you have users that are joining your ACC project, and you just have Docs, they may want to see some of these views that you can go through and create. So let's actually hop on in and show you this process as well.

So starting out, these are all of the models, which we, again, created as views-- well, Matt did. Thank you, Matt. And you can see what space they've been uploaded from. So again, if you have multiple spaces, you can pick which ones they are. So we're going to go through and actually show you this view from an architectural and structural view level of comparing those two different models.

Now, this isn't actually clash detection here. This is specifically doing a model browser view of the two different models. Matt went through and took the time to create these filters so we can see the differences. Now, there are rules that you can go through and set if you wanted to filter out different items within here. So that is just reducing the amount of noise that's currently federated in this model, these two models that we've added.

You can actually see the two different models here that you can select on and off. So you can see my structure, and then you can also see the architectural. You can turn this on and off, and the filters add to that depth. So again, Matt did an excellent job of showing that.

You can go directly into clashes from here. So there is this clashes view that's from those two selected models, and you can see and identify the clashes that are being shown here. Now, there's some issues that we went through in detailed, labeling them as clashes. So, yes, this is model coordination, but clashes are defined from issues.

Going back in here, you can go through and actually use some of the browser features. So we can go through and pan around, fit to view. There was even the zoom to view and first person, which was I thought was pretty cool. So for all those people that play video games out there, first person, you can even actually go through and measure in here.

The measurement feature is actually great. You can select from elements, defining what type of measurement you want to verify. So that's a great feature. You can calibrate it, but let's go through and just hit Done.

Now, from here, you can save the view out. Now these are saved views. You can title it whatever you'd like. Now, you can save these views out as always and then use those in the clash portion. But save them out to Docs is what I really want to get into here.

And yes, there is spell checking here as well. For those folks that have difficulty spelling like myself, you can go to private. Can set this as public. You want this to be public because we're going to push it into Docs as well. You can add a description. Let's hit Save.

Then from here, we can go into Models. We'll see those highlighted models after we exit out of here. Then we're going to go to Views because that's where we saved our view out to. Now, here's that view I recently saved. I'm going to Select Save to Docs, and we're going to actually save it into the structural folder for our structural team members because some of them only have a Docs license, and I want them to see this view.

You can see one that I've already pre-created as well. This is going to be real-time loading so we can see how long this takes. You can see the details of these views as well. It's taking a little moment to push into Docs.

And then you can see from here, you can go to Model Coordination. Let's go just directly into Docs, too. But let's check this other one that I've created before-- again, just quickly flying around and showing those differences within that view. So it should be loaded. Yep, perfect. We're good, so let's go into Docs.

Again, not having that BIM Collaborate Pro or BIM collaborate license, people can access a model that you've pushed over from their, which is model coordination. I know said there, but model coordination. So from here, you can see these two different views.

Matt did an excellent job of filters as well. Just be aware issues do not transpire from model coordination over into here. So if you're going to create new detailed issues, this will be your coordination space if there's specific design issues that you want to address, but a great way to access things from Docs in that perspective.

So if you want to, you can save these views out into Docs and label clashes from this perspective, too. That filter is a little bit better, but it's not giving me a clash or an issue tracking from a coordination perspective, but can still be handled in Docs. And just kind of wanted to give you that visibility from a Docs perspective.

Let's go back into Model Coordination. Go back into our views from here. And we can see these views and when they were last updated and back saved into Docs.

So next one that we're going to be talking about is clashes. So the Clashes tab is what details all of our clashes that's automated from comparing the two different models-- again, views that you created within Revit and published into here. Again, we select those at the beginning when we were going from our space. We want to have a laid-out tabular view of identifying already from those models when things clash. So let's hop on in and show you what that looks like.

So from the clashes models, we were just in views. You actually get a detailed list of what's being clashed currently. We can see it's great and itemized. You can go through and see what space is being clashed currently if you had multiple spaces. You also can see when the last publish happened if different team members are publishing as well.

You have active. As we showed earlier, you can actually close them. So if you wanted to go through and close these. And then you also have different views. So you can specify just those views that I created earlier. You can even identify what models you want to see in this tabular view. Let's not go through and have this one or this one. And we'll just have a smaller level view.

So on your y-axis, you're going to have both the same. And on your x-axis as well, they're all the same models. You're just comparing between arc and structure. There's 250. Let's click in. So this is where you actually click into the clash area if you wanted to.

And we can see the highlighted two comparisons defaulted of red and green. You can see the primary model and what it's clashing against. You can do group by if you wanted to group by specific rules and exclusions. You can actually go through and show specific ranges. Maybe I don't want to have it clash when it's outside of a foot or something.

You see your issues. These are labeled as clashes directly right here, but you're creating an issue on that clash. So you can go through and select these. Now, when you select it, it does give you this transparent view. But when you check it, it actually highlights it to be more profound.

We're going to pick this shaft opening here that is having an issue so that we can coordinate with Matt on this perspective. And we all know structure's not going to be moving the shaft opening. We're going to have good old architecture team go through and maybe fix that shaft opening instead of us moving the wall.

We can go through here and see that the floor is penetrating directly into this wall here, so we need to go through and address this. So what I'm going to go through and do is create an issue. Now, depending on who you want to solve this issue, you're going to address it to that person by selecting the element.

So if it was a structural team, I would have clicked the wall. But since it's the architectural team, I'm going to click the floor. It's creating a node point. And now we're identifying what this issue is.

Yes, we're in the Clashes tab. It's not automated the clashes, but you do get a nice preview view. You can red line it if you wanted to. There was a pen feature in there, but I'm going to go through assign this to Matt because he needs to go through and address this.

You do have locations and details if you wanted to go through and add a location for this specific item. So I'm going to go through and say, this is roof floor opening issue, maybe a shaft issue. I don't know how he created it, but I'm hoping he did a shaft opening from that perspective. So let's go through and title this opening, and then a due date.

So we're going to go through and mark him a due date on Friday. So let's go through and say Friday. And then it's also set to Friday, so he's got a pretty strict deadline there. He needs to go through and address that.

And then any root causes-- so this is a design coordination issue. And then if we wanted to go through, we also have some more. So there's just additional ones If you wanted to go through and view what is available to everybody. But enough about that. We don't need to go through every single one.

We can add any references. So if you want to attach photos or files and then comments. So I really like to give comments versus just assigning it to Matt. This needs to fix. Perfect. So we're going to go through and assign this comment. We can then hit Submit.

Then you also have from here a publish or unpublished feature. So by default, publish to Matt. Matt's going to get an automatic awareness that this was sent out. And you can unpublish or publish.

There's also an activity log here. So you can go through and see the activity of what's been taking place. We're going to exit out of here. You can go through to your issues. As we can see our most latest issues on top, you can filter and sort these if you wanted to, then go back to our model browser or models. So again, views that were published from within Revit.

Now, going back, let's exit out of here. And we can go through and look back at our tab view, and we can see it went from 250 to 249-- again, reducing the amount of clashes because there is an issue that needs to be resolved. We can go through to look at our settings from our models. We can see all of the models that are part of this.

And then you also have this object exclusion. So they're building to this. There's 50 object exclusions you can actually add into here. This was in beta when I first got introduced into it, but now you can actually go through and create one.

We're not going to go through too in depth, but you can select the architectural model. Let's say Matt and I both modeled walls. We could go through and actually exclude a rule from Matt's model to exclude walls. So you do have that option to go and create exclusions if you wanted to-- again, just adding more depth to this platform and kind of filtering out that noise.

But let's go back into clashes here. And then next, what we're going to be going through and talking about is issues and meetings. So I just assign this issue directly to Matt and I need to create a meeting. Ironically enough, we're in the same office. But let's say you wanted to go through and schedule a meeting with your sub consultant because you assign them an issue. Let's hop on in and show you that process.

So again, I'm going to go to the Issues tab here. We're going to check out our issues. So you can go through and say, what issues do we want to look at? Is it just the clash issues?

That's just what I want to go through and look at. We can see all of our issues here as well. And we can export this out as a report. There's more reporting that will go through and list in our handouts, but you can do a detailed report, summary and how you want that to look from that perspective as well.

You can search by an issue or an ID. You can also filter to kind of give you a little bit more because, again, full project, you're going to have a lot of items in here, going through and just adding more exclusivity from it. You can then go through and see what space. But let's go through and talk about this one that we just assigned to Matt.

You can check on it from here. But again, we're going to go through in detail this in a meeting. But you can see some of the activity log and information associated to it. Let's go through and schedule a meeting with Matt around this issue.

So in order to go through, you create a meeting. You hit Create New Meeting. And then from here, you're going to go through and add a description. So what are we meeting about? So let's go through and say it's going to be a clash issue.

And it's at elevator. It may be the roof and a shaft opening, but let's go through and do roof. And then next, you can invite people, so we're going to go directly and invite people directly from the project. So it's going to be Mr. Matt Linn confirm this.

And then we're going to go through and add a topic. So there does need to be a topic because what you really trying to get is assigning the issue to this. And in order to do that, you have to have a sub issue. So class issue with the subtopic of review.

So once you've created the subtopic-- If I can spell. It's a great day for spelling for me-- we can go through and add a second subtopic if we wanted as well. So let's go through and show that because you can open and close these, and then you can move these around. So if you had an issue that changed within the sequence of having the meeting, you can actually readdress it there. But let's go through and just show you that second item is our second topic.

But let's attach this issue. So if you hit this little three dots, you can actually reference to an existing issue. So we're going to click this. And we can see that number 10 issue that we just created is what we want to have our discussion about.

And now you can see this reference to it as well and over here, the reference items too. You can go through and add any additional references, so files or issues. We want to add a secondary issue, which we're just going to address one issue right now, or any files, which you can reference from Docs. So we're going to go into our structural file and that saved coordination model, we're actually going to attach it directly into here to.

Perfect. So next, we're going to add a summary. What are we going to reference from a meeting summary? So we're just going to do an example for everybody. And then we can also add any meeting attachments from this perspective, too.

So we can go and hit Attach. Choose any files. Nope, we're good-- nothing from desktop. And then any references on the top right, too. We can see some create follow-up, which we'll do secondary, share invites, add a calendar, export to PDF. We can delete the meeting if we wanted to.

We're not done yet because you can actually go through and change the title, which I probably should have done at the beginning. I do little things out of order, a little dyslexia. So clash issue with Matt.

And then we can do the meeting by agenda or by minutes if you want to have a per minute meeting, stay strict to what you're setting. But we're not actually completely done yet because what we do need to do is set a time because I don't think Mr. Matt wants to meet at 12:00 AM. So we'll do Friday, and we're going to meet at an appropriate time, which is not 1:00 AM or even 12:00 AM. Let's go and meet at 1:00 PM.

Then you're going to set your ending time because it's not going to be that long of a meeting. So go through and say 1:30, and we can specify a location. This will actually be on Teams. So we can go through and do is we can actually add a link directly to here. So we can add a Microsoft Teams link, too.

So it's definitely all integrated. , And of course, we have to authentication, so we're not going to prove this. But you can approve it as well. And there's my meeting clicking back in. And again, if you wanted to add that link.

Now, let's go through and also address any follow-ups. So let's say the meeting resulted in another follow-up; you can actually go over here and add a follow-up directly to this meeting to add more information if you ever needed to. So have a follow-up up on the 20th-- perfect, boom, good to go. And now we have a secondary follow-up meeting for this, and it's all referenced here, right?

So we're going to take a moment and pause real quick because what I want to identify and just make everyone aware of is full transparency. That's the greatest thing about ACC is there's no more fragmented data between individuals and losing information along the way and email trails because you can actually put correspondence in here, which is emails. We're not going to get into that. But same thing with meetings, right? Everyone sees who's meeting, what they're meeting about, full transparency.

But let's continue forward because we're going to talk about items. So you can see all of your items that were being addressed in any of the meetings. And then you can also create templates if you wanted to, which we don't have any created. Just again, creating meetings a little bit more efficiently for you and your team members here.

Perfect. So now that I've assigned my issues, we're going to go through and have Matt address the issue. So on to you, Matt.

MATT LINN: Great. Thanks, Michael. So we're going to jump into the issues add-in. Now, before we get started, notice I am in Revit 2024. So we actually did start this presentation in 2025. And we realized that the issues add-in has not been released for 2025 yet. So if and when you do want to go this route and use this add-in, which is incredibly helpful , as of now, make sure you're in 2024 or previous.

OK, so it is right here. It has its own tab called Issues. The far left button is an overview. So if you come in, you can see it has three open issues. Scroll down. It's got one closed, just kind of a dashboard.

Most of what you'll do is in this Manage Issues tab here. And you can see it's very similar to what Michael's been showing. We have all the issues here. You can go directly online and view them in ACC, as we've seen from Michael. So from that, we can come, bring us directly to them here.

If you go ahead and click on one of the issues, it opens it up, and it shows you all the details that we've been seeing from Michael's screen already. So with that, it selects the element for you. It shows you the push pin. You have the thumbnail here, the title, status, the type, and the description.