AU Class
AU Class
class - AU

Live Case Study: The Peaks and Valleys of VDC Implementation on Major Projects

Share this class

Description

Presentation Focus is on live successes and challenges in the overall VDC delivery process on a major Project: -$240Million Project / 8 Buildings / Over 23 Acres / 30+ Design & Construction Professional Firms Learning Objectives: 1). The role BIM-enabled tools and the VDC process plays in the delivery process of 8 buildings, extensive sitework reconstruction across 23 acres within a 2-year construction schedule. 2). How early BIM Execution Planning set expectations, and peaks and valleys we endured as a team that followed. 3). The tangible value of BIM deliverables to enhance effective self-perform concrete installation. 4). The evolution of “standard” 3D Trade Coordination from “just a requirement” to really “trusting the model”. 5). Point of Attack “BIMing” to center BIM as the “Circle of Trust”. 6). Enhancing visual communications and decision-making on an Owner level through BIM-enabled concepts such as Virtual Mock Ups, 3D Virtual Walk-thrus, and 4D Model-Based Scheduling.

Key Learnings

  • Enhancing visual communications and decision-making on an Owner level through BIM-enabled concepts such as Virtual Mock Ups, 3D Virtual Walk-thrus, and 4D Model-Based Scheduling.
  • Point of Attack “BIMing” to center BIM as the “Circle of Trust”.
  • The evolution of “standard” 3D Trade Coordination from “just a requirement” to really “trusting the model”.
  • How early BIM Execution Planning set expectations, and peaks and valleys we endured as a team that followed.

Speakers

  • Avatar for Alex Belkofer
    Alex Belkofer
    Bio: As a regional leader and national collaborator at McCarthy, Alex is responsible for the overall strategy, implementation, and execution of the virtual design and construction (VDC) lifecycle process between all project stakeholders. From corporate office to construction site, the VDC Team promotes, trains and guides McCarthy Project Teams through VDC processes/practices over the course of a building’s design and construction lifecycle. Alex works closely with Project Directors, Project Managers, Owners, and A/E partners to establish early expectations and project deliverables at all project phases. Alex is a key contributor serving on McCarthy’s National VDC Leadership Group to enhance the delivery and consistency of VDC/BIM-enabled strategies and best practices company-wide. Education: Dual Degree – Architecture + Construction Systems Management | The Ohio State University
  • Chris Campbell
    Chris Campbell is the Visualization Manager for McCarthy’s Central Region where he also oversees McCarthy’s National Visualization Group. With this role Chris has been challenged to continue developing the way that McCarthy uses visualization services such as 4D Animations and Virtual Reality to provide an exceptional client experience.
Video Player is loading.
Current Time 0:00
Duration 1:04:59
Loaded: 0.26%
Stream Type LIVE
Remaining Time 1:04:59
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

ALEX BELKOFER: All right. Well, good morning, everybody. We're going to start on time here and be respectful everybody's schedule today. Good to see everybody at 8:00 bright and early. Thanks for coming out. So hopefully Chris and I aren't going to bore you too much. We got some cool stuff to show you guys today. We're excited about the opportunity. So, welcome. Hopefully, you're in this class and not another class.

CHRIS CAMPBELL: And if not, we're still glad you're here.

ALEX BELKOFER: Oh, absolutely. Absolutely, yeah. So thank you again. We'll go ahead and kick this off here. My name is Alex Belkofer from McCarthy Building Companies.

CHRIS CAMPBELL: And I'm Chris Campbell, also with McCarthy. We're both out of our St. Louis office. Snowing at home right now, and we got about 5 or 6 inches to welcome us home tomorrow.

ALEX BELKOFER: That's right.

CHRIS CAMPBELL: It'll be good.

ALEX BELKOFER: So, glad to be here today. Two messages before we start. This is an opportunity to share an ongoing case study that we have right now on one of our major projects in St. Louis with one of our great clients at Washington University in St. Louis. But while it's a case study, it's also a great time to take an opportunity to reflect on where we think we are as an industry from a project delivery standpoint. This is a very large project, and we'll get into all those details.

But at the end of the day, this presentation is hopefully meant to be a good status check for us. You know, how are we integrating as an organization in McCarthy with our design partners, with our owner partners, with our trade partners? Are we really doing the things that we think that we're doing in 2018 going into 2019? And so this project will highlight some of the things that have worked well. We'll talk about some things that are still challenges for us and how we're overcoming those in 2018 going into the new year. So thanks for joining us today.

So real quick, Alex Belkofer. My background's in construction operations. I began my career as a project engineer, found VDC later in my lifetime, and now I'm blessed with the opportunity to help McCarthy lead VDC in our central region.

CHRIS CAMPBELL: I'm Chris Campbell again. Come from an architectural background. Latched on to any kind of visualization presentation. And it has taken me to this point to help build a team in our St. Louis office and then manage our team across the country.

ALEX BELKOFER: Yeah. Let's get into it. Let's get into it. So, real quick before you get little bit of background on Washington University. Just so I understand the audience here, who are design professionals here in the audience? OK, Very good. Any owners in the audience? No owners today, OK. And then contractors? All right, what about any trade contractors? All right, good. We've got a couple. OK, good. Good.

So a little bit about Washington University if you do not know them-- founded in 1854, very known for its what they call Collegiate Gothic style architecture. So the campus, as you can see, is very ornate, very articulate with the way that they do their architectural practices. It's a beautiful campus. If you ever get a chance to come stop by and visit us, please come see the project. But this is a great opportunity to build something that they'd never done before.

This project specifically for Washington University, the East Campus Enhancements project is about a $250 million construction project, about eight different components. And as you look at the overall cross-section of what we're doing here, this is the university's largest undertaking that they've ever done as a one-time construction project. So pretty monumental opportunity for Washington University. We're really proud to be a part of it.

So we're construction manager-at-risk on the project. A lot of different components to this project. There's five new buildings. There's one addition to an existing building that we actually did prior, Kemper Hall. Of course, extensive site work. This project essentially is completely ripping up and redoing the entire front entrance to Washington University. So we'll get to some pictures here in a minute.

But this main drive right here-- this is Brookings Drive right here coming into the campus. Right now, this is all torn up and we've pretty much given it a whole facelift, OK? And so this is a major opportunity for them to change the approach and the entrance into their campus, OK? Two big things here, it's 24 acres over the course of three years. The project itself actually will be completed within a two-year construction frame. And then the last leg of it-- the last year is going to be the McKelvey Hall building, which is separate from the job but goes right there where that number 4 is.

One of the biggest challenges here with us, though-- we have over 20 different design and construction professionals that we have to interface with. So as a CM at risk, this is not design-build. This is not IPD. You can imagine the amount of challenges that we probably already faced going into the project. And we'll talk more about that as we get into this.

So, this was the existing state I mentioned, Brookings Drive. This was kind of that straight shot, that view into campus. Brookings Hall is their main building here. This is where the chancellor of the university has their office. And so you can imagine all this parking space and all this vegetation was completely transformed by the new design here. And so, a little bit bigger picture that gives you an idea of what it's going to be come May of next year. And again, the eight components here.

Probably one of the most things that is unique about this is we're putting an underground parking garage in that is one of the most ridiculous parking garages I think we've ever seen. We built-- literally buried a garage 80 feet in the ground. And this is probably the nicest concrete you'll ever see. We got some photos to show you. But they nicknamed this the Garage Mahal on the project job site. And there's a lot of reasons for that.

And then by building. The design of these buildings is meant to be very transparent. Our design partners from several different architecture firms that we're partnered with had this really very transparent style. It's meant to blend in with the vegetation of the new development of the park. There's a couple of buildings, though, that still reflect more of that Collegiate Gothic architecture style, primarily Jubel. Jubel really blends in well. The other buildings, though, are very high transparency-- a lot of glass, a lot of open space to really show off the system designs of the buildings.

And so this will be, at the end of the day, what it's going to be. This is that view that they wanted. So this is-- you know, when you enter Washington University from the main drive there on Skinker-- that's that view they were going for. You still get to see Brookings Hall, which is their crown jewel. And then McKelvey is going to end up going here. Again, separate project. We actually just started this. This one's coming out of the ground as we speak right now.

All right, so let's get into some of the challenges here, right? And this is where we really wanted to start to talk about the essence of deploying VDC on a major scale on a project like this. Scale, I think, was obviously the most important part of this, right? Eight major components to your time frame, 20 different design professionals. You know, that kind of speaks for itself that our overall schedule was going to be something that was going to be a challenge early.

And then, of course, the speed. With all those different people having to make decisions and make decisions timely, we knew that was going to be a challenge going into this. And then, of course, the management of everybody's expectations. And we'll get into more of those challenges as we have to walk through our approach to BIM execution, 3D coordination, putting work in place in the field, and some of the things that did occur early on.

So, some of the key elements. I'm going to speak to communication and expectations first. One of the most important things I think that everybody needs to understand on a job like this with a VDC strategy is that communication piece-- who's touching who, when are they touching them, where these pieces of communication need to fall in line, whether it's cloud-based communication, whether it's by email, whether it's by phone-- all that needed to have a strategy.

And that all went into our early BIM execution effort. I think a lot of people just look at the technology in BIM execution, and they're not thinking about that people part of it. That people part is still critical for us. That still drives what we do. We have this wonderful technology out there. But without the people side of it and having a communication plan that actually goes into the BIM execution plan, none of this works.

And then the expectations piece. Again, at McCarthy, we have about 45 people on this photo on the job site full time for us. So it's all of our managers, our superintendents people really driving work at the point of attack. Outside those 45 people, we have another 300 to 350 McCarthy craft people on the job site, actually putting work in place. And then on top of that, there's expectations, and of course, from Washington University, all their owners, reps, and our design partners.

CHRIS CAMPBELL: So, yeah. And then there's a trust component too, right? Because to deliver a job of this scale in two years, our project superintendents and project directors came to us to say, look, we can't do this without performing in-house modeling of all the concrete, all the lift drawings, so that we can be as efficient as we can on site.

And that puts a lot of trust on our team, both our personnel that were in the office and the personnel that we had on site daily delivering those concrete models. But it's understanding that these aren't a representation of what's being built. These are what's being built, right? And so there is a trust there that we had of what they were telling us, and what they had with us, and what we're delivering to them so that we could execute this project in the time that was given to us.

And that just talks about our teamwork too. It was a one-team state of mind. It wasn't, oh, you guys are the BIM guys out in the middle of nowhere or coming to us virtually. It's, we're going to get together. We're going to work arm-in-arm on this job. And we're deliver a good project at the end of the day.

ALEX BELKOFER: And so a lot of that strategy going into the teamwork piece was our operational involvement as a VDC team with the project at the point of attack. This was not, as we like to say, Batman coming in and saving the day, doing VDC, and leaving. This was definitely a collaborative, hybrid approach. And that's how we like to approach it at McCarthy-- is that operational and VDC hybrid execution.

And so in order to do that, we had to come up with two things, really. It's an early start plan and an early execution plan and set expectations. I'll explain this graphic real fast. I think it's important. The project job site leader, Ryan Moss, our director, came up with this graphic-- this concept to feed the machine. And I'll be honest, the first time I saw that graphic on a poster in the job site, I'm like, man, it seems kind of mechanical. What does that mean, "feed the machine"? It just sounds like a bunch of robots going into work and just turning those wheels.

But the essence of "feed the machine" though is more about understanding what we had to do for our client in a short time frame. We knew that we had to be like a well-oiled machine. And so it wasn't about just being mechanical about doing what we're doing. It's about being methodical and being very intentional about how we do things so that we're not repeating work, so that we're able to work together, to keep that well-oiled machine, which is the whole McCarthy project delivery, going, OK?

And so, early start, right? So, planning and design, site prep and excavation. We'll get into that here in a minute. There's some really cool videos and some photos to show you guys about that. Getting out of the ground early was what was paramount for us. And you think, what does that have to do with VDC? Well, Chris is going to show you guys in a little bit how VDC helped us get out of the ground early.

And then, of course, setting expectations. It was my responsibility to really make sure that our BIM execution strategy at the beginning of this was clear. And we'll talk a little bit more with a couple examples on what was clear and where we lost some opportunity, where we thought we had clear expectations that we had to realign.

CHRIS CAMPBELL: Yeah, so planning on a job like this, although we had a two-year time frame to get the majority of these buildings done, the planning started well before that-- 2 and 1/2 years before that-- because of how monumental this project is in the city of St. Louis. All eyes were on this project, right? And so on top of that, Washington University employs a ton of really, really incredibly smart individuals, much smarter myself.

But that comes with a lot of opinions in the room, OK? Any of you who have worked with campus owners know that they take a lot of pride in their campus. And they have their campus at the top of their minds at all times. And so you have to be accommodating, but you also have to be real, in fact, that we have to get this job done for you guys. And so we bring a lot to the table in that planning effort. And so it was a great partnership. You always have your ebbs and flows, and we'll get to those.

But planning had to start early because we have to accommodate commencements and graduations and summer schedules and the height of the school year. And so there's a lot more-- as any of you who have worked on a massive college campus, when it's a live campus, there's a lot more to it. And so we'll get to the specifics of that. But planning started 2, 2 and 1/2 years before we ever put a shovel in the ground for a job like this. And we probably made 15 iterations of that small crane plan over there just because we were shifting and moving and seeing what would be best to accommodate the schedule.

ALEX BELKOFER: And in order to start a lot of that, we actually started in the modeling environment, right? So while Chris and our team really started to make a lot of these plans, modeling began very early. We had a strategy at beginning the project where we're going to have a model-based approach. And so everything we started to do from day one was model-focused, was model-centric.

So let's talk about that expectation piece of how we're going to employ a model-based approach as a builder on a project like this, right? So, preplanning for execution, right? So, BIM execution meetings. There's a couple of different types of meetings that we do at McCarthy. I usually like to start off with a VDC execution meeting with just our owner and our designers to make sure that we have good alignment, which is a good best practice that we have. We don't like getting halfway down the road and being misaligned. So we usually start off with that. And then we'll do our normal trade coordination kickoff meetings with our trade partners.

But the big part of that, though, is create an execution plan that was effective, but it worked across all eight components. So normally we do an execution plan per building. This was probably one of the rare ones where we did it for all eight buildings together. And so we had a very articulated LOD matrix that talked exactly about what was the expectation modeling content-wise on all the different components. And it talked about our processes and talked about how we were actually to deploy this throughout the two years.

CHRIS CAMPBELL: So our project director came to us and said, hey, everybody is talking about this job. And everybody's talking about bits and pieces. They say Jubel. They say Hub. They say McKelvey. They say Weil. But nobody knows what that all looks like over time. So they said, we need a tool to help communicate quickly to both our on-site personnel, our leadership, and our subcontractors. So they come on board. What this project is going to look like when it all comes together?

So we commissioned this job. And all it is is a very diagrammatic look at these buildings coming together, the crane schedules, over time. So you'll see the bar of information really light on the bottom. And so what you'll see is we've been on-site, according to this plan, for less than five months. And we've already got a 60-foot hole dug in the ground and foundations going in. And so just the breadth of this project was supposed to be communicating. As we developed this and we started to see all these things coming together, honestly it gave us a little bit of a scare. We're like, OK, this is going to be a serious undertaking. OK, all these pieces have come together.

But what it also did was it gave our subcontractors a little scare as well. They're scared right alongside us. And that's actually a good thing, because we wanted people who are going to get on board with us, and they're going to be real with us about, hey, for us to get a job done like this, we got to price it this way. And that's what we want to now. We want to know that these people are with us, that they're going to be with us through the entirety of this job, and they're going to give us their best personnel. Because that's what we need for a job like this. And so the job-- this did what it was supposed to do. But it wasn't supposed to be a super flashy thing. It was just supposed to be, hey, let's communicate what this is going to look like at any point in time so we can stop and see where we're at.

What you'll see next, we start to give some of the campus back. And that was a big part of this. We communicate to the ownership that we're going to give much as back as we could. And then we wanted to give him just a quick, early look. And these were early models, and they have changed a lot. Again, this is supposed give him an idea of, OK, what are these things supposed to look like at the end of the day? So you see, very unobtrusive, yes. We are installing full glass elevators out there. So that's to not obstruct the view of the campus in any way.

I mean, when Alex mentioned that this is their Broadway right here-- I mean, this is the campus right here. This is the entrance to the entire place. That's supposed to be a park-like feeling. It's supposed to be what WashU is known for. And so you'll see that communicated design and all the planning that goes into it.

ALEX BELKOFER: Just to feed on one thing that Chris said-- you know, the scare moment for a lot of the trades, seeing the simultaneous work-- that's a theme throughout this project, people needing to understand how things are happening both in sequence and how things are happening in more of a start-to-start, overlapped-type environment. That became a topic of conversation early on in trade coordination. We'll talk about, you know, people needed to understand that we're coordinating all the buildings at the same time. There was no, do one building and then go to the next and go to the next. It was all happening at the same time. And so resources became a challenge, and we'll talk about that.

CHRIS CAMPBELL: And that's why I put really peppy music to the background of it so people get really excited about that.

ALEX BELKOFER: That's right.

CHRIS CAMPBELL: And so we jumped right in, right? So this was less than one month out on the job site. We're out there. We're mobilized. We got trucks starting to roll. We've got foundation starting get dug in on multiple areas. You can see a lot of those trees have been removed, if not all of them at this point. We're starting to drill piles. We're starting to get our different footings dug. And so we're getting our personnel out there, but they were already out there. They are already moving. We didn't have any time to waste.

And what was an ace-in-the-hole for us and this project is being able to leverage our partners, Castle, who is an in-house contractor for us that got out there and they just rocked this excavation. What you're going to see is this is a three-month-- just drone own video of just the progression from month to month. So we've been going out since the start of this job. And we've been going once a month to just show the massive undertaking that's been going on. So this goes one month later, one month and a week or so, and we're already down--

ALEX BELKOFER: That's in one month.

CHRIS CAMPBELL: Look how far down in the ground. I mean, it was just constant truck traffic. Constant truck traffic backed up, truck after truck after truck after truck. And so these guys got us started. They crushed the excavation portion of this. They got us off to the right start and allowed us to continue to be successful when we started putting our footings and foundations in. So what you're going to see is we'll go from this one-month view. And you'll see just in two months how deep this hole really got. And the excavators being sunk in really gives you the scale of this thing.

But there's a lot more, too. We say, you know, trucks hauling out dirt. OK, it's a massive campus. No problem. Well, the route that they had to go, Skinker is-- I mean, it is right on Forest Park. Anybody who's been to St. Louis-- I mean, that is a monumental road. And everybody uses it, especially campus traffic. And so we had to agree to keep that baby clean, to keep it functional, and to not totally stop that for 2 and 1/2 years, 3 years.

So there's a lot more to it. And that's why the logitistics just took so many years beforehand. But you can see now in two months we're down and we're pouring footings and foundations. So it was a massive dirt undertaking. We'll get into some of the technology we used to make that a successful undertaking. And we can't give Castle enough credit for getting us jumped off to the right start.

ALEX BELKOFER: And so as you can see, the Garage Mahal is starting to take life now. OK. So let's get into the fun part here, right? So I like to look at it as pre-BIMing and BIMing, right? What are we doing before we actually start really creating model content and really starting to dig in with our trade partners? And then what actually happens during the actual story, right? Well, we all know about expectations and reality. The way I like to look at it is this.

We have two roads, right? We have an execution plan. And the road looks pretty straight. We can see the flag at the end. We know there might be a little bit of a challenge here and there. But we think we've got a pretty clear plan. The maximum effort, of course, is always going to be in that middle. We know that going into it that execution strategy is meant to communicate what that challenge is going to be early. We talk about resources. We talk about milestones, substantial completion for sign-off for coordination.

And then you have the actual journey and what actually happens, right? And that effort right there is really part of the story. And that's what we're going to share with you, is we're going to talk about those challenges. Because it's easy to come up and give a presentation that talks about everything that worked well. But we as an industry still have a long way to go. And we want to talk about how we overcame some of those challenges and [INAUDIBLE] on this project together.

So let's look at the pre-BIMing-- all the things that we did in advance to really get this thing going and really make sure that we had clear expectations, right? So starting with 3D coordination, I already talked about those execution meetings-- you know, letting our lead mechanical contractor drive the process. And I'll talk about that for a minute. A lot of different builders and mechanical contractors have different strategies in how they lead coordination.

St. Louis has a great opportunity. We're very blessed with a lot of very robust trade contractors. We have a lot of partners in St. Louis who are used to doing design-build MEP coordination. And so we gave them an opportunity early on to lead coordination for each building. What that means necessarily is they're driving the overall Navisworks process. They're driving the actual clash detection while McCarthy is still facilitating, still leading that though as the builder, OK?

But we had a lot of great feedback early from the trades going into bidding and scope reviews. And they said, we want to take on that responsibility if you'll let us. And we said, OK, we'll start out that way. One of the main reasons why we did that is because McCarthy made a commitment early to self-perform all this work and also model all of it.

Our 35-year superintendent, our senior superintendent, Mike Noll, on this project said we're modeling all the concrete in this building if McCarthy is going to be doing this work. That coming from a guy like that is very powerful. And he wanted to do model-based field layout. Everything was going be done with the digital total station, shot in for accuracy. And so we started down that road. And that's what we did early. We knew what that effort was going to take. That's primarily one of the reasons why we let our lead and mechanical contractors take on that responsibility in tandem with us, OK?

Cloud-based collaboration, of course, is going to be important. So multiple different cloud platforms we're using at McCarthy, so we had to make sure that that communication plan was clear on who's putting stuff where, how often, frequency, and then, of course, our meetings-- in-person, web meetings, you know. There's always a strategy going into trade coordination where people want to be remote at their computer back at their office. We had to emplore more of a hybrid strategy in this project because we had so many McCarthy people at the point of attack, driving this work. We needed to make sure that our trades were engaged with the people that are putting the work in place in the field. And so having a hybrid strategy of meetings in-person and web was critical in getting started out of the gate.

CHRIS CAMPBELL: And so another thing that our 35-year superintendent, as techie as he is, came to us and said, hey, we need a solution so that we have one single source to get all of our information. And so we developed this in house. It's just a simple project dashboard that acts kind of as a hub for all the information our on-site personnel would need. And so we didn't have anything that was working perfect. We were using different solutions for docs. We were using different solutions for our RFIs and contracts and everything. And we said, we need one hub for this project. Already we have six different mini projects going on. We need one area to access everything.

And so there are layers and layers behind this. You can break it out by building, but even down to just having the weather at the click of a finger. We're all about safety on our job sites. And so the only thing they're allowed to have out-- and they're never allowed to be on their cell phone. It's, hey, you got your iPad and you want to be able to have something that has all this information you might need. So we have everything from construction documents broken out by building, the concrete placement drawings, weather, site logistics, and they just act as one way to keep it all there.

And so in the site logistics, in that preplanning, before we ever started digging that massive hole, is we had to come up with these logistics plans. We had probably seven or eight that we went through, but we won't bore you with all of them. But essentially, you can see that this massive area on the right side here-- we essentially take all of it. We don't take it all at one time, but we take most of it.

And what that means is fire safety, entrances and exits for these students, overhead protection-- how's that all going to work, and how's it going to change? So when I say we had seven or eight of them, we had seven or eight because we would do one for fall school year. And then we would do one for summer when we're not as heavy on the traffic. And then we'd do one once kids are back in school. And so all those things had to adjust because of this being an active campus.

And then if we go the next slide, if you draw an imaginary horizontal line through this plan, the other factor that was really fun to deal with is this campus is almost perfectly split into two different fire districts. You've got the city fire district and you've got the county fire district. And you might think that fighting fire is just universal, but apparently it's not. And so they like to approach fire safety in two different ways, and neither of them is wrong. They're both right. But we had to get those guys working together with us to produce some of these plans so that we could be successful in making sure these students were safe in the event of any kind of fire safety drills.

ALEX BELKOFER: Again, big thing-- scale, all model-based, all things that VDC allowed us to do early. So let's talk a little more about these placement drawings. Making a commitment early to model all the concrete on this project-- well, it might sound like an easy task. We knew how much resources it was going to take us to do that internally in-house. Placement drawings are a big deal for a company like McCarthy because we self-perform work. There's a number of other builders out there in the industry that also go through this practice.

But what's important about understanding the way that we do it-- this is meant to be given off to somebody in the field that actually will take this drawing and put this work in place. And so the amount of effort that we put into the information and the detail in these drawings becomes critical for doing things one time and one time only. Making a commitment to make these drawings is trying to save people man hours in the field. And we have some numbers that we'll share with you guys on that with our recent success story we did with our Autodesk partner team.

But you look at making these drawings. What you're trying to do is prevent one person in the field from looking at nine drawings. We want to give them one drawing with cubic yardage, everything they need to put that wall or put that component in place, call the concrete truck, order it, get it there, but also leverage all the points in this drawing from a model-based layout standpoint to actually put this into our total station and shoot it in place.

So this drawing's doing quite a bit. We made 580 of these for the project. So there's quite a bit of work that we had to do as a VDC team. We leverage a lot of different VDC resources internally in McCarthy across our company to make that happen on this project.

And you can see the amount of detail here. And I'm going to show you a picture in a minute. I mentioned the Garage Mahal before, right? One expectation that was not clear at the beginning this project is how much our design team cared about how the concrete looked in this garage. You'll notice here how perfectly all of these form seams and all these tie holes line up in these drawings.

Well, that was not going to be the plan at the beginning. But it became the plan when all of our senior superintendents were out there in the field looking at the early concrete pourers, and the owner came out there and said, oh, well, I was expecting these joints to be lined up. I was expecting all these tie holes to be perfectly lined up. And they said, well, you guys are McCarthy. You guys can do that, right? And we're like, yeah. Yeah, we can do that.

So we had to go back and tweak our strategy for how we were doing these drawings, as you can see the care that went into making that. And it gave us some really beautiful concrete in a building that you will never see. But what's great about this, though, is that when you're in your vehicle, and you pull into your park assist space, and you look way down the row there, you'll see a lot of awesome-looking concrete in a very dimly-lit garage.

[LAUGHTER]

The one thing that is cool though about the care that the design team and the owner did want us to take with this is that it just allowed us to focus more though on our craft. I mean, we take a lot of pride in self-performing work at McCarthy. There are some very ornate tulip walls at the beginning of this garage. The garage, the way you pull into it-- you actually pull in underground from the street. Then you slope down.

They have these beautiful tulip walls, they call them. Basically it's this curved concrete that kind of blossoms like a flower. And that looks fantastic. I will tell you-- we just started pouring those about a couple weeks ago. That right there-- that work makes it worth it for us. So while you'll never see some of these walls, you will see some beautiful concrete when you pull into the tulip wall entries.

And you can see some of the crazy stuff that we're trying to do here. This is one of our more complicated buildings. I think this is Jubel. I mean, you just have some very unique shapes here that, to be honest with you, if I was a tradesperson trying to build this in the field, I'd be looking at probably 30 drawings. And to be able to look at one drawing to do this pour sequence for comes in pretty big handy. So just to give you guys some level of detail on how much work that's going into this.

What's important also realize too is, again, this is not VDC coming in like Batman saving the day. These drawings and this execution only works with our superintendents, our foremen, our craft people checking these things. And we'll talk more about that checking process because this is just not something that happens magically.

So let's talk about the challenges, right? All the pre-BIMing stuff-- we thought we did a pretty good job with, right? Expectations were clear, we had a good approach going into it, early start with excavation. Concrete, self-perform modeling, going awesome. We're rocking it. But of course, things do happen, right? And so understanding those challenges, I think, is important for us in order to get better. We want to be the best. We want to make sure that we have the best execution with our trade partners, with our design professionals.

But scope always becomes a moment of clarity or unclarity early. And we started to see that early on in coordination. We were about three months into the VDC coordination process. And we started to see people not modeling things, right? Things were not there in the model. Even from the design side, there was just some things that were not there that we expected. And so we had to really dig into those things, and they started to uncover themselves.

We did have an early challenge with coordination meetings, and just those meetings not being effective. A lot of project management issues started to creep into those VDC coordination meetings and really made those meetings more ineffective than they were effective, and they got bogged down. So a lot of this happened within that three-month time frame.

And of course, when that happens, what else happens, right? So, people become unfocused. Our trade partners who were leading the coordination on more of the actual clash-detection side of things, were getting very bogged down internally with trying to deal with the design challenges of their building systems, their specific systems, and our meetings started to fall apart from a standpoint of being very focused on trade coordination and being overly focused on project management issues.

So then, of course, we had some model management challenges that came with that-- people not posting things for the right location because they were distracted by doing other stuff. They were spending more time in one area of a building than another. And model content was just not developing the way that it needed to. And so then people got disengaged. And so having meetings on site was a good strategy early, and people stopped showing up. And so we needed to have some tough conversations about that.

Which led to more stuff like this. And so in order to prevent that, we had to hit the pause button. Because, as McCarthy, leading the process, there's some things that started to occur from that list that you saw that was just not going to work with what we promised ourselves and what everybody bought into. And so I'm going to give you something that's very real. And I'm sharing this very intentionally, because we're not perfect.

This is one of those concrete placement drawings undergoing an extensive review with the design team and the owner and many people. What's important about this drawing is two things. Number one, this is a shear wall in one of our first buildings. So it's a pretty important wall. That wall helps the building stand up, right? Well, there's eight major penetrations in that wall, all these guys right here. And you can see everybody's very passionate opinions about those penetrations.

You'll notice this date right here. That's five days. That was put on there for a reason. Because those sleeves needed to be in within that five-day time frame after that review period or else. Because concrete was coming, and Mike Noll wasn't going to stop these trucks. Because this was one of our first buildings. We're killing it early with execution.

Those eight sleeves didn't make it in that wall. That's not good. Why didn't they make it in that wall? Well, because of this process being so convoluted with all these opinions, what happened was the person at the point of attack, the person that mattered the most, didn't have the latest drawing and didn't know where to put those sleeves. And so that person said, we're pouring this wall. You guys can figure it out later.

That right there is not alignment. That is not good. So we had to hit that pause button and really make sure that we had a serious conversation with everybody involved in that process-- everybody. And that's not just McCarthy. That's our design team, our owner team, our tradespeople. Everyone had to understand why this process failed.

The worst part about it is all that was in the model. It was in our trade models. It was in our concrete placement drawing. It was in everybody's drawings, everybody's model. But this drawing, the final one, didn't make it to the person closing in that wall. And that's the person that matters the most. And so we can't forget about those people.

So that was the trade side of it. But I want to talk about the design side too because design intent and construction coordination oftentimes get very confused. That conversation doesn't happen often enough. I think we, as McCarthy, have recognized over the years that having that early alignment with our design team is probably the most critical thing-- to understand that difference and to understand that we have to have synergy and be on the same page with that conversation early.

There was early confusion between design intent and construction coordination. A lot of meetings-- those PM issues I talked about-- there's a lot of conversation early about, well, this is what's in the design model. This is what's not in the model. You guys need to be coordinating this. This area is going to be exposed. A lot of those things just graphically in the model-- it was not coming across that way to us. I think our design team didn't realize early how much we were leveraging the model as the builder. They thought that we were just using the model as a reference. But the model really becomes a driver for us. It becomes that single source of truth. And so having alignment midstream-- that conversation needed to happen.

And then there were some critical members of the design team that gave input a little bit too late in the process. There was people plugged in early the entire time. But there were some people who had very strong opinions about design intent in certain areas, and we had already coordinated some of those areas with the design intent that we thought that we were aligned with. And so making sure that all those key stakeholders, the right people, are plugged in from beginning so we can make effective decisions because of the scale and the speed of a project like this.

And of course, we always came back to one magical question. Because in that first three- to four-month time frame with everybody having a difference of alignment or difference of expectations, we kept coming back to this quite a bit. At the end of the day, what do you want? One of our people on site, one of our superintendents, would often say this phrase. Because he would go into meetings with the design team. He'd go into meetings with the owner team. He'd go into meetings with the trades. And people just didn't understand what they wanted at the end of the day.

Whether it was making a decision on where to move a main, or making a decision on is this going to be exposed or is this going to be concealed, everyone needs to know what they want at the end the day. But they have to be transparent. It can't be hidden in an agenda in a meeting. You have to come out with it. Especially on a project like this with a lot of key stakeholders, they're very passionate about how these buildings are going to look and function at the end of the day.

So, the adjustments. What do we do? Well, we modified that approach and went to more of what our standard practices at McCarthy is that builder-led coordination. Our trade partners are awesome. They're very good at what they do. On a project like this with all the simultaneous work happening, we recognized that they were be more effective really owning their craft and owning their scope and allowing our team to take more of that lead trade coordination role. And once they really started to kill it with the concrete placement drawings and getting those drawings into a seamless process internally at McCarthy and leveraging our internal resources, we started to shift more of our VDC experts into that role of leading that coordination and then transitioning that to our operational partners. And that became very effective.

The meeting agendas definitely had to become streamlined. And so we, again, took on more of that leadership role to have that VDC person plugged in with our apps person and lead more of that meeting and get those project management issues out into another meeting with people that can deal with those on more of the project side.

The design team became much more integrated. Once they started to realize how we were leveraging the model, they started to understand how critical it was for us to have the model content in there from the design side so that we can make effective decisions going into trade coordination. And so we got back to having people engaged, people in the trailer. We had the design team on the phone from multiple different areas of the country while we were there in person. And the meetings became very effective.

And then, of course, the model's driving that field information. Again, when you leverage that single source of truth so much, people understand what it can do in the field, how it can keep people moving. Again, we're trying to put things in one place at one time, one time only. We're not trying to rework stuff. So that model driving that field information became very important. And as people on the WashU side and people on our design side started to go into the field and then reviewing construction and seeing things going in place, they're seeing the connection between the drawings and the models and all of our submittals. And they're finally starting to understand, now, this is a big deal for us. This actually drives our work.

And of course, we simplified our cloud approach. There's a lot of different platforms. Again, as Chris said earlier, we had that early-- that dashboard that we made. The dashboard was great. But there were still a number of tools within that dashboard that people were just not taking advantage of or they were just confusing people. And so we leaned down a few of those.

And then we finally got to having one synonymous federated coordination model of all eight components which became very powerful because this was truly live. This was in real time-- very hard to do on a project this size to have a federated model of all those components. But we finally got to that. And people finally started to realize that as we go through these different coordination meetings, whether it was in Jubel or in Weil or in the Garage, every meeting, these models were so up to date-- they were so important that people were starting to see model content generated within hours. And they were just like, wow. Like, people are really finally starting to buy into this being a very active, real-time coordination effort.

And now we're BIMing. Now we're good. Now we're finally at a point where people are trusting something at the same time in real time across the job. And people aren't in silos and not working on building and one building only. It's truly something that's effective now. So, but one does not simply BIM, right? We have to get from doing BIM to leading VDC.

And I get on my soapbox sometimes with this. But we as an industry still have this challenge. We still think BIM. We're not thinking VDC. We have to. And the reason why we have to is for these two primary reasons-- is what can it do for us, what can BIM as a tool do for VDC as a process in this current generation moving forward? Chris is going to talk about visualization. And then we're going to talk about taking BIM to that next level and really making BIM a VDC process. And that's how McCarthy approaches it.

So real quick on the flythrough side of things, I will say that the flythroughs in this project are very intentional. What we basically do is we have an intentional sign-off process where we bring in the owner at the point of signing off a floor, as we like to call it. And we walk them through it in 3D to make sure that we have their alignment, have their buy-in before we start the official shop drawing process. That's the most intensive part of what our trades do. They spend all their time and effort in coordination and then making those drawings. Because once things go into fabrication, they don't want to change stuff.

This project was huge for that though, because all these green lines here in this picture-- this was all electrical work. These are all electrical conduits that were supposed to be in the corridor for the design intent. All those lines didn't fit in the corridor. And so we made some critical decisions early to move those into a room that really didn't have a lot of space. And all those penetrations right there-- that's another shear wall in that same building. And we sure as heck weren't going to miss those on this time. And so making a decision to take all those lines that were out there and put them in that room-- again, one of those big things that we had to use visualization to really help us communicate what we were trying to do which was different than the design intent initially.

Reality capture became a big thing. That garage, as we said, is buried. It's underground. So that garage at some point someday may turn into something different, or they may do something else on the lawn of WashU at some point. So we made an early decision with the owner to actually scan the lid of the garage because the garage is only, I think, about 3 feet under the cover of Tisch Park. So we scanned the lid of the garage for future. And so all the conduits, post-tensioning cables, all those good things-- we documented all that. And we have this beautiful point cloud of the lid of garage that WashU can use at some point and tie it to the GIS system, because they're an ArcGIS user.

CHRIS CAMPBELL: Yeah, and so another way that we help the client to visualize this project and help our own team visualize this project is by doing mockups. Any job site you go to for the majority of these massive jobs are going to have enclosure mockups. But what we like to do as a company beforehand is we like to do them virtually. And I'm sure a lot of other companies do. But it's just another way of checking ourselves before we get out there and start spending money on these.

So what we're going to do-- you know, we're going to build it first in that controlled environment, make sure we're very comfortable with these systems, making sure that they're airtight, that we're not going to have leaky systems, making sure that we understand for five different buildings and five different types of enclosures how those systems go in place, and we're going to test them all virtually before we ever start doing it again as a test on site. And so that's something we definitely implemented on this job for each one of these buildings.

And then take them to the next level, OK? So we've talked a lot-- if you remember back the beginning, we talked about this massive hole we had to put in the ground. You've already seen how deep it had to go. Well, we didn't have a lot of time to do that. And on top of that, we didn't have a whole lot of time to check ourselves as we did that because of the pace we were going. We were moving about a thousand cubic yards a day. That's a lot of dirt. People who don't do dirt, that's a lot of dirt.

And so what you're seeing here is our actual concrete model setting into a site scan-- our drone scan that we took out on site. And what the importance of this is our old method of doing this was putting a couple guys in a buggy with their stick, and we go and we drive across the site and we map our points. And we take our point after point after point. We try to interpolate those and we get our best accurate look of what this site looks.

Well, you're talking about at least a day of shooting on a site this large and then a couple of days of processing. Well, we didn't have that kind of time. And on top of that, with the amount of dirt we were moving, by the time our guys got halfway across the site, the site behind them was totally different. And so we're really trying to mix two sites together to understand our cut field for that day.

So come in with some open ideas and enter the drone, right? Everybody's using drones. Drones are hot right now. Everybody's got them. So what we did was we set up drone calculation. We did site scans. And what used to take us essentially three to four days of processing between getting the points and then getting them spit out to know where we were at calc-wise, now took us a 10-minute drive to the site, a 12-minute total flight time, and 10 minutes back to your car, upload, and you'd have it the next day. And so our efficiency increased off the charts, not even really calculatable. But our accuracy also went up about 7% to 10%.

And so between those two things, we looked back, and I don't know how we could have done this job and kept track of our calcs without using that new technology. And it was our project team that embraced that and allowed us to implement it. And then we get to do cool stuff, like just set our building in there and say, hey, it fits in the hole we dug. And so that's a good check, right?

And then we have some other techniques too. So this is us walking our concrete pours. This was a way of-- we color-coded our different crews and things. But don't pay attention to dates. This isn't actually accurate as far as dates. We actually didn't pour them that fast, as much as we'd like to. But what it did was it allowed us to get-- this was an early test. But what we did do is we actually allowed us to get in these meetings that we had weekly with the owner and let them get in a human-scale environment, whether they wanted to put a headset on or walk around it like a video game, put their put their virtual vest on and go in and walk the job, understand where pours were going.

And what it does for our project team-- it says, hey, we've got crews converging at this point right here. Why don't we just flip-flop? Instead of saying you're limits end here, now you've got to flip all the way to the other side because you're the orange crew and this is the green concrete crew, it lets us look at that in a virtual environment instead of just a flat PDF and say, OK, we can be smarter with this. We can be more efficient at a human scale and start to visualize that before we get out and start pouring.

ALEX BELKOFER: Another thing too this did for us is this really started to debunk the myth that 4D scheduling is not for actual construction sequencing and operations. We believe that it is. A lot of people still think that 4D scheduling is still pretty BIM. But this actually gave a tangible example to our team and to the owner to say, look, these concrete placement drawings, these models we're spending all this time and effort on-- it's real. And we can tie that to the schedule and we can show you how that sequencing is going to work.

And so while Chris mentioned about the dates being a little bit off, we started to actually articulate this a little more and tweak it and get to the point where we can now finally ask our project teams if they give us these dates and keep these dates updated, that hybrid approach we talked about between ops and VDC, us helping them drive the model content updating process of them driving that field management, that scheduling piece-- this can start to become a functional tool now finally for us. So it's not just pretty BIM.

CHRIS CAMPBELL: And they don't need to put a headset on to experience. It adds a layer, right? It can be fun on a Friday afternoon for someone to get in. But for those of them who did buy in, they really enjoyed it. And it can be taken from either walking it, or it can be taken from, let's just zone in on this view and get a better view, a better representation. Let's print it off as a 2D platform just on a piece of paper. You don't have to be in it virtually. But it just gives them a better visual than a PDF marked up with highlighters to tell them where the pours are going on that day.

ALEX BELKOFER: Speaking of visual.

CHRIS CAMPBELL: Yeah. So we tried some other things. And what you're seeing here is us in the HoloLens, doing some augmented reality QA/QC. So we got it on site. We picked our points. And this is our fully coordinated MEP model. Now, I'm not going to stand up here and tell you this is 100% accurate and that I was going out there with the intention of telling the trades to rip all our stuff out because they're wrong, because it's just not going to happen. It's just not there yet. I know some other people might tell you that it is.

But from our experience, this is a live test. This was also verifying. You can see blue duct over where it was installed. You know, it's pretty dang close. And I'm actually really impressed with how close it is. But it's just not there yet to where we can say, OK, you're off 1/8 of an inch, you're off 1/4 of an inch, to where we can start saying, hey, we're holding you accountable based on what we're seeing in the HoloLens. But we're getting there as an industry.

Other people might-- like I said, maybe somebody has a magic trick too. But we've tested this extensively and we're working with the product suppliers and the software suppliers, and you'll see in the expo out there today right alongside of them, making sure that we're getting it as close as we can and we're testing real-life simulations. But what it is doing is it allows our on-site personnel to at least go out and understand, hey, I got a lot of stuff to install in here still. I've got stuff that's got to wedge in these gaps, and how is that going to fit even if we are a little bit off.

And where we're really finding value right now where we've tested on some other facilities is as a facilities management turnover tool, because you don't have to be within 1/16 of an inch accuracy on that. It's not a QA/QC check. You can turn something over and have them go through a hospital or a campus like this, where there's a ton of systems, and go through and click on objects and pull up their Revit data and understand what's hidden underneath all their finishes. So we're loving this tool. We're trying it more and more.

We're implementing it on-- we're getting better, right? We're implementing it on as many jobs as we can. But we're not here to tell you that it's 100% accurate. And if somebody has found a way to make it 100% accurate, I'd love to hear about it. And I'd love to test alongside you. But we're excited about it. I truly think this is a feature-- people ask me all the time about AR, VR-- is it just a flash in the pan? I truly think this is where we're going. You can imagine the quickness and the value it would add to an on-site layout carpenter or someone trying to install on site.

ALEX BELKOFER: All right, so let's get back to the conversation about BIM is the tool. VDC is the process. And this is a good opportunity for us to just talk about that for a minute. Because you see all these value-adds. And while a lot of these value-adds are value from McCarthy, I think it's important for people to realize that this is a lifecycle process. McCarthy isn't just doing this for ourselves. We're doing this because we believe this is the right thing to do as an industry. And a lot of this has to do though with the holistic product stakeholder team, right? Not just the owners, not just the trades, not just the design team-- it's everybody.

Chris mentioned the point about facilities. So often, people don't begin with the end in mind. And then we have to. And those people are, at the end of the day, the people that are the most important. People are going to live in this building, operate this building, and you have to think about it from a lifecycle standpoint. So this is very important for how we approach this, which is why VDC execution early has to happen so that we can get to the point of fabricate, operate, and then renovate at some point someday, and give people a building that they're going to be able to use, they're going to be happy with, and we can stand behind and say, yes, we helped build that project. But we did it the right way. We did it with the right people, focused early, and then began with the end in mind.

So let's talk about those value points for this project. Again, there's a lot of project benefits. But there's a lot of owner benefits. And it's important to articulate those. Because that engaging and informing part early-- I recommend anybody who wants to really start to approach VDC as a process and not just looking at BIM tools as a component of what we're doing to think about how you're going to get those people involved early and get them aligned, right?

Early identification of those issues with breakdowns-- you know, those pause moments that we had early? While we couldn't have predicted some of those things, that happens. That's just how our building industry works, right? People have one set of expectations. Sometimes things become misaligned. But it's how you recover. It's how you change after those pause points that defines what happens after that, right? And then you have to document and adjust, right? You have to make sure you're capturing best practices, capturing the lessons learned, and actually using those going forward.

BIM really driving, again, the way that we build that single source of truth, the way it's going in place-- we're there now finally. It's finally at that point now as an industry. We can trust it to that level. But we all have to be clear on how much we're going to trust it, when we're going to trust it, and what's going to happen in the field when something happens where there's a deviation between the modeling world, the drawing world, the spec world, and any other world that comes into play. And so we get back to that single source of truth.

But the benefits that WashU finally started to see is what you see is what you will get. That example about the seams line up-- the seams lining up with our form work and the tie holes in the Garage Mahal-- you know, that's what they finally started to see was we had one plan at the beginning and we had to change that plan because they wanted to have that expectation that everything would look beautiful. And we were able to deliver that.

Multiple mediums for information review-- we talked about those different platforms, right? We leveraged studio sessions for those drawings. We leveraged these 3D flythrough meetings with the owner to review the modeling effort. Using those multiple mediums really got people to get their arms around what exactly was going to happen out there, and if the model was driving that.

And the end deliverables-- you know, the handover piece. That was not a topic of focus at the beginning for a lot of the project stakeholders. We had to really make sure people were aware on what McCarthy and our trades were going to be providing as a deliverable at each stage of the project and at the time of substantial completion come May of next year. And I think our design partners too started to realize as well that what we were doing from a handover standpoint, what we're going to be providing, needed to be synonymous with what they're providing us during the project from a record document and record modeling standpoint.

And so now it's time to seal the VDC deal, right? The project still going on. This is a live case study. It's intentionally meant to be that. And so we have to be at the point now where we have to continue to deliver what we said we were going to deliver, right? Keeping the models live is probably the most paramount thing. The marriage between the models being live and the contract documents always being behind is reality, especially on a project like this. And so we have to continue to push BIM back into the documents, as I like to say.

Models need to continue to drive the documentation process for the project because the models are more current than our drawings in a lot of cases because bulletins aren't being issued every week. Because the drawing changes don't happen as fast as they need to-- still big challenges we have as an industry. We have to think about how we can leverage all these new tools and these new workflows out there to continue to make that process better. Because that right there is probably our biggest challenge as an industry, is how does BIM continue to influence our contract documents which is still what we have to build off of and what we're tied to.

Effective model management, of course, making sure that McCarthy operations and VDC team members-- our team to keep the models as live as possible. Management's use of the model-- I love this. Our operational leaders in the company-- Ryan Moss even is taking BIM into his meetings as a project director. I think that's awesome. We need more of that. We need people that are engaged at a higher level to show people, look, we trust this. This is what we're doing. This is how we're building.

And somebody in his position coming back and saying, you know, this is paramount for us. We wouldn't be able to do this job without BIM, without VDC coordination, or without a VDC strategy-- that's fantastic. And then, of course, that communication of the point of attack-- the example about the person closing in a wall who had all the information-- it was all there in 3D. It was all there in the model. But the right person didn't have the right information.

So, real quick here-- some metrics, because people love metrics. And this is a big part of why we believe this is important at McCarthy. I'll talk about that concrete placement drawing effort that we did, right? I mentioned the 560 CPDs, right? 87,000 tons of concrete-- that effort was just so important for us early to get our arms around. But these last two numbers is the result of that.

Why we made this commitment as a VDC team, as an operational team is this right here. These eight hours per day that model-based layout saved us, doing digital layout in 3D before we gave it to the shooter who went out there and put it in their total station gun and put it in place-- those eight hours are real. That's important for us because, again, this is McCarthy self-perform work, putting that work in place and trying to do it one time, and one time only.

But then the 14 hours is probably the more important number which talks to the actual number of hours that we probably saved by making all those drawings versus traditional methods of trying to look at 9 to 10 different drawings and go and put something in place, and also mitigate the issues that that would have caused-- you know, RFIs, putting things in wrong, and having to rework things. So those numbers are real, and those are things that we saw in the project. And we're still seeing those benefits now, especially with the concrete placement effort wrapping up.

So, key takeaways. We talked about scale, speed, management, right? So scale of the work relative our overall schedule-- of course, it's paramount to trust the model. If I had to implore any of you to go and do any of the stuff that we're doing, it's you got to have that trust, that model management strategy at the beginning, and get people to believe that the model can be a single source of truth.

CHRIS CAMPBELL: Yeah, and then speed. Just as we talked about, the schedule drove a lot of it. But being able to get our owners and our designers and our subcontractors to be able to visualize the project so that they could understand quicker and put their knowledge to use in a way that we could understand it quicker and be able to relate faster.

ALEX BELKOFER: And then, of course, the management expectations, right? It's just paramount at the beginning. You have to know your decision makers and have those people plugged in from the beginning.

And so with that, we want to say thank you. Great opportunity to present you guys this case study to give you guys the information. We got about five minutes left, so I want to give you guys a chance to ask any questions. And we'll play the drone flythrough while the questions are being asked.

[MUSIC PLAYING]

Yeah.

AUDIENCE: Two quick questions. What cloud platform did you use, and what software and hardware did you use for the augmented reality?

CHRIS CAMPBELL: What cloud platform for which part?

AUDIENCE: For the project that you talked about everything needing a cloud [INAUDIBLE].

CHRIS CAMPBELL: Do you want to talk more on that?

ALEX BELKOFER: Yeah, a combination of a couple of different things. Well, C4R, BIM360 Design was big for our VDC team, concrete placement models, coordination with the other trades. So it's combination of that. [? Moving ?] Studio, obviously, for the placement drawings and that review process. And then leveraging Navisworks, leveraging Glue, all those things.

CHRIS CAMPBELL: And for augmented reality, in that particular example, we are using HoloLive, which they're downstairs in the expo. So they've been a good partner to us. We've been working alongside of them for a while now.

AUDACITY: So my question is we-- [INAUDIBLE] and we have around [INAUDIBLE]. Sometimes we get a lot [INAUDIBLE]. So how do you guys handle that part in updating the model? Because do you guys have, like, [INAUDIBLE] system [INAUDIBLE]?

ALEX BELKOFER: That's probably the hardest part about doing what we do, is keeping that model alignment, right? And so we'd like to have a model alignment meeting every month. We actually call it that. And that's our opportunity to pause with the design team and say, OK, here's what construction coordination has driven through this month, right? Here's all the RFIs that we've written, what's open, what's closed. Here's where the models stand. Do the record documents need to be updated any further? Because we try to preplan for these bulletins, right, rather than just getting bulletins thrown at us.

We're trying to help them preplan by saying, OK, here's all the things that have changed. Are you capturing this this month? Is that happening next month? We document all that though in our project management solution. So whatever the solution is for that project, as McCarthy has a couple different platforms that we're using right now, that's all documented from that monthly model alignment meeting so that our record documents can continue to stay as live as possible. We know it's not realistic for the record documents to be updated every couple of weeks. So trying to get on that monthly cycle, having that monthly alignment meeting becomes pretty important.

AUDIENCE: What changes did you have to the ASIs bulletin to keep track [INAUDIBLE]?

ALEX BELKOFER: Where are we at right now?

AUDIENCE: Yeah.

AUDIENCE: [INAUDIBLE]

ALEX BELKOFER: That's a good question. I'm pretty sure right now on the overall project-- because, again, there's eight different components to this project. I think right now, I want to say we're probably around a thousand RFIs right now overall to your project. But eight components-- you know, there's a lot of questions.

AUDIENCE: What are the given design processes where you involved prior to construction? Like, with the design professionals.

CHRIS CAMPBELL: With them and with us? I got involved. I was looking at models at 25% when I was starting to do logistics with them. We had basic footprints at that point. So we were doing logistics planning based off of that. So that's when I got involved. But they were already couple months into the process of planning. So I think they came in with a pretty high-level design. But we progressed with them over almost three years of design.

ALEX BELKOFER: One thing that I will say that we can provide as an industry overall in an at-risk model is to be involved much earlier in the process. You know, a lot of people have strong feelings about, well, the models from a design standpoint really aren't that developed until you get to about 50% DD, or 75%, or whatever your milestones are.

But what I would argue though is that that 3D constructability-- some of the things that we can just help provide as a builder early on doesn't even have to be looking at any piece systems. It's just looking at building enclosure skin. It's looking at how the building is going to be, how we're going to sequence the work in there. I would just really encourage folks on the design side to get us involved as early as possible there.

AUDIENCE: So did you take over the model at any point, or did you work with design professionals through the construction process? When a live truck's coming down, we'll rebuild a model, but I want to take over a model, because if we get multiple entities, you're bringing in all their models, and you end up with-- the way that you get it is different from [INAUDIBLE]. More precise, but a lot of the times you're planning to rebuild that model. Did you do something like that, or did you continue to [INAUDIBLE] professional model?

ALEX BELKOFER: Yeah, well, that early strategy of who's modeling what, when they're modeling, and to what level of detail was that conversation that needs to happen in every job. You know, there's not a lot of value from our standpoint to just rebuild something that the designer of record is already going to maintain throughout the project. Where is the value there? Where we want to see the value, though, is who can enhance the model in certain areas, right?

I'm going to have my framing contractor model king studs and model some of the critical components of enhancing the design intent. Construction gap modeling is kind of how we look at that, right? Where can we add value, right? Is there a lot of value in having my framer remodel all the walls in the building? Probably not, because the design professional record's already done that. Where can they add value? Where can and they enhance it to enhance our coordination? So in my mind, it's a lot more of a strategy of model management and then enhancing modeling where it's needed, versus just reworking something to rework something.

AUDIENCE: Do you throw the LODs all away?

ALEX BELKOFER: Yes, yes.

CHRIS CAMPBELL: But the concrete, we did remodel all of it.

ALEX BELKOFER: Because we self-performed it.

CHRIS CAMPBELL: Exactly.

AUDIENCE: So to tag on to that question, in regards to the gap modeling, are you going back to the design turnkeys to get that opportunity to fill in some of those gaps and maybe an issue you're responsible for?

ALEX BELKOFER: Absolutely. I mean, there's definitely situations where there were some design elements from a record modeling standpoint that were just missing that we caught in those flythrough meetings. And that was important because people just didn't-- they didn't see that as a potential gap of information until we actually went through it with our trades and said, well, you want all these systems to be concealed.

But do you realize that in the design model, there's a big gap here in this soffit, or that you can see through these two ceiling planes? You're going to see all these things. Those are those opportunities where the design team's like, wow, you guys really are leveraging this model, and you're really trying to think ahead to what the end condition's going to be. And so there's a lot of those moments that happened early.

AUDIENCE: Do you see any great method that you guys preferred? [INAUDIBLE] there or design build, or just did additional ones?

ALEX BELKOFER: Oh, I would do design build all day if I could.

[LAUGHTER]

Yeah.

CHRIS CAMPBELL: Any integrated project delivery format for us where we can be involved earlier and really [? open ?] that preconstruction effort-- that future-proofing, that future planning-- that's ideal for us. I mean, CM at risk is still a very real delivery method for us across the board at McCarthy. And we're going to continue to operate that way because it's a very effective model for many owners. But the earlier we get involved, the better, so we can start to look at these things more from that constructability standpoint.

AUDIENCE: It might not have been totally the way to [INAUDIBLE] this project. I don't know how the jurisdiction works there. But when you're building off of a BIM model, and [INAUDIBLE] and your documents are falling behind, how do you handle inspections and [INAUDIBLE] review at the jurisdiction model?

ALEX BELKOFER: Sure. I understand. That's one of those ongoing challenges. We're trying to get those people into these meetings. And I think they're very open to it in our market. They're just not used to working in that environment. So, getting them involved in those studio review sessions, right? Anything that's much more collaborative and less static, I look at it as going from static to dynamic. How do we get those co-professionals, those AHJs, in that dynamic environment? Because that's the reality of where we live in.

We get it though. You've got to put a stamp on it at some point and turn it in. But at least getting them to see more into the process and have them be a part of it rather than them just being an entity on that outer circle. And so we're looking at just, again, those collaborative environments-- just starting to get them that level of effort, right? Get them into that 3D flythrough meeting before they mark up our drawings and bleed all over them and send them back with a bunch of exclusions, right? So really just trying to get them in more of that dynamic environment.

AUDIENCE: What is the 4D scheduling software you were using for that virtual walkthrough?

CHRIS CAMPBELL: For the one where the concrete was going? That was Fuzor. They're downstairs as well. So a lot of folks are using them now. It's a combination of a lot of things. It's not just a-- sometimes it's not as easy as just a click. But yeah, we've tested a bunch of them from Synchro and everything through. And that was the particular one we used there.

AUDIENCE: What software do you use to model the concrete?

CHRIS CAMPBELL: Revit.

AUDIENCE: Revit?

CHRIS CAMPBELL: Revit, or Tekla now. We're implementing Tekla on one of the jobs now that we have those in-house experts. So kind of depends. We want to be able to collaborate across our VDC team across the country, and so we've got to be mindful of our skills cross-country. But Revit on this one, yeah.

ALEX BELKOFER: All right. Thank you guys very much. Appreciate it.

[APPLAUSE]

______
icon-svg-close-thick

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

icon-svg-close-thick

THIRD PARTY SERVICES

Learn more about the Third-Party Services we use in each category, and how we use the data we collect from you online.

icon-svg-hide-thick

icon-svg-show-thick

Strictly necessary – required for our site to work and to provide services to you

Qualtrics
We use Qualtrics to let you give us feedback via surveys or online forms. You may be randomly selected to participate in a survey, or you can actively decide to give us feedback. We collect data to better understand what actions you took before filling out a survey. This helps us troubleshoot issues you may have experienced. Qualtrics Privacy Policy
Akamai mPulse
We use Akamai mPulse to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Akamai mPulse Privacy Policy
Digital River
We use Digital River to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Digital River Privacy Policy
Dynatrace
We use Dynatrace to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Dynatrace Privacy Policy
Khoros
We use Khoros to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Khoros Privacy Policy
Launch Darkly
We use Launch Darkly to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Launch Darkly Privacy Policy
New Relic
We use New Relic to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. New Relic Privacy Policy
Salesforce Live Agent
We use Salesforce Live Agent to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Salesforce Live Agent Privacy Policy
Wistia
We use Wistia to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Wistia Privacy Policy
Tealium
We use Tealium to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Tealium Privacy Policy
Upsellit
We use Upsellit to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Upsellit Privacy Policy
CJ Affiliates
We use CJ Affiliates to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. CJ Affiliates Privacy Policy
Commission Factory
We use Commission Factory to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Commission Factory Privacy Policy
Google Analytics (Strictly Necessary)
We use Google Analytics (Strictly Necessary) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Strictly Necessary) Privacy Policy
Typepad Stats
We use Typepad Stats to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. Typepad Stats Privacy Policy
Geo Targetly
We use Geo Targetly to direct website visitors to the most appropriate web page and/or serve tailored content based on their location. Geo Targetly uses the IP address of a website visitor to determine the approximate location of the visitor’s device. This helps ensure that the visitor views content in their (most likely) local language.Geo Targetly Privacy Policy
SpeedCurve
We use SpeedCurve to monitor and measure the performance of your website experience by measuring web page load times as well as the responsiveness of subsequent elements such as images, scripts, and text.SpeedCurve Privacy Policy
Qualified
Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

Improve your experience – allows us to show you what is relevant to you

Google Optimize
We use Google Optimize to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Google Optimize Privacy Policy
ClickTale
We use ClickTale to better understand where you may encounter difficulties with our sites. We use session recording to help us see how you interact with our sites, including any elements on our pages. Your Personally Identifiable Information is masked and is not collected. ClickTale Privacy Policy
OneSignal
We use OneSignal to deploy digital advertising on sites supported by OneSignal. Ads are based on both OneSignal data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that OneSignal has collected from you. We use the data that we provide to OneSignal to better customize your digital advertising experience and present you with more relevant ads. OneSignal Privacy Policy
Optimizely
We use Optimizely to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Optimizely Privacy Policy
Amplitude
We use Amplitude to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Amplitude Privacy Policy
Snowplow
We use Snowplow to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Snowplow Privacy Policy
UserVoice
We use UserVoice to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. UserVoice Privacy Policy
Clearbit
Clearbit allows real-time data enrichment to provide a personalized and relevant experience to our customers. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID.Clearbit Privacy Policy
YouTube
YouTube is a video sharing platform which allows users to view and share embedded videos on our websites. YouTube provides viewership metrics on video performance. YouTube Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

Customize your advertising – permits us to offer targeted advertising to you

Adobe Analytics
We use Adobe Analytics to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Adobe Analytics Privacy Policy
Google Analytics (Web Analytics)
We use Google Analytics (Web Analytics) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Web Analytics) Privacy Policy
AdWords
We use AdWords to deploy digital advertising on sites supported by AdWords. Ads are based on both AdWords data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AdWords has collected from you. We use the data that we provide to AdWords to better customize your digital advertising experience and present you with more relevant ads. AdWords Privacy Policy
Marketo
We use Marketo to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. We may combine this data with data collected from other sources to offer you improved sales or customer service experiences, as well as more relevant content based on advanced analytics processing. Marketo Privacy Policy
Doubleclick
We use Doubleclick to deploy digital advertising on sites supported by Doubleclick. Ads are based on both Doubleclick data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Doubleclick has collected from you. We use the data that we provide to Doubleclick to better customize your digital advertising experience and present you with more relevant ads. Doubleclick Privacy Policy
HubSpot
We use HubSpot to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. HubSpot Privacy Policy
Twitter
We use Twitter to deploy digital advertising on sites supported by Twitter. Ads are based on both Twitter data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Twitter has collected from you. We use the data that we provide to Twitter to better customize your digital advertising experience and present you with more relevant ads. Twitter Privacy Policy
Facebook
We use Facebook to deploy digital advertising on sites supported by Facebook. Ads are based on both Facebook data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Facebook has collected from you. We use the data that we provide to Facebook to better customize your digital advertising experience and present you with more relevant ads. Facebook Privacy Policy
LinkedIn
We use LinkedIn to deploy digital advertising on sites supported by LinkedIn. Ads are based on both LinkedIn data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that LinkedIn has collected from you. We use the data that we provide to LinkedIn to better customize your digital advertising experience and present you with more relevant ads. LinkedIn Privacy Policy
Yahoo! Japan
We use Yahoo! Japan to deploy digital advertising on sites supported by Yahoo! Japan. Ads are based on both Yahoo! Japan data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Yahoo! Japan has collected from you. We use the data that we provide to Yahoo! Japan to better customize your digital advertising experience and present you with more relevant ads. Yahoo! Japan Privacy Policy
Naver
We use Naver to deploy digital advertising on sites supported by Naver. Ads are based on both Naver data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Naver has collected from you. We use the data that we provide to Naver to better customize your digital advertising experience and present you with more relevant ads. Naver Privacy Policy
Quantcast
We use Quantcast to deploy digital advertising on sites supported by Quantcast. Ads are based on both Quantcast data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Quantcast has collected from you. We use the data that we provide to Quantcast to better customize your digital advertising experience and present you with more relevant ads. Quantcast Privacy Policy
Call Tracking
We use Call Tracking to provide customized phone numbers for our campaigns. This gives you faster access to our agents and helps us more accurately evaluate our performance. We may collect data about your behavior on our sites based on the phone number provided. Call Tracking Privacy Policy
Wunderkind
We use Wunderkind to deploy digital advertising on sites supported by Wunderkind. Ads are based on both Wunderkind data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Wunderkind has collected from you. We use the data that we provide to Wunderkind to better customize your digital advertising experience and present you with more relevant ads. Wunderkind Privacy Policy
ADC Media
We use ADC Media to deploy digital advertising on sites supported by ADC Media. Ads are based on both ADC Media data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that ADC Media has collected from you. We use the data that we provide to ADC Media to better customize your digital advertising experience and present you with more relevant ads. ADC Media Privacy Policy
AgrantSEM
We use AgrantSEM to deploy digital advertising on sites supported by AgrantSEM. Ads are based on both AgrantSEM data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AgrantSEM has collected from you. We use the data that we provide to AgrantSEM to better customize your digital advertising experience and present you with more relevant ads. AgrantSEM Privacy Policy
Bidtellect
We use Bidtellect to deploy digital advertising on sites supported by Bidtellect. Ads are based on both Bidtellect data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bidtellect has collected from you. We use the data that we provide to Bidtellect to better customize your digital advertising experience and present you with more relevant ads. Bidtellect Privacy Policy
Bing
We use Bing to deploy digital advertising on sites supported by Bing. Ads are based on both Bing data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bing has collected from you. We use the data that we provide to Bing to better customize your digital advertising experience and present you with more relevant ads. Bing Privacy Policy
G2Crowd
We use G2Crowd to deploy digital advertising on sites supported by G2Crowd. Ads are based on both G2Crowd data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that G2Crowd has collected from you. We use the data that we provide to G2Crowd to better customize your digital advertising experience and present you with more relevant ads. G2Crowd Privacy Policy
NMPI Display
We use NMPI Display to deploy digital advertising on sites supported by NMPI Display. Ads are based on both NMPI Display data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that NMPI Display has collected from you. We use the data that we provide to NMPI Display to better customize your digital advertising experience and present you with more relevant ads. NMPI Display Privacy Policy
VK
We use VK to deploy digital advertising on sites supported by VK. Ads are based on both VK data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that VK has collected from you. We use the data that we provide to VK to better customize your digital advertising experience and present you with more relevant ads. VK Privacy Policy
Adobe Target
We use Adobe Target to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Adobe Target Privacy Policy
Google Analytics (Advertising)
We use Google Analytics (Advertising) to deploy digital advertising on sites supported by Google Analytics (Advertising). Ads are based on both Google Analytics (Advertising) data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Google Analytics (Advertising) has collected from you. We use the data that we provide to Google Analytics (Advertising) to better customize your digital advertising experience and present you with more relevant ads. Google Analytics (Advertising) Privacy Policy
Trendkite
We use Trendkite to deploy digital advertising on sites supported by Trendkite. Ads are based on both Trendkite data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Trendkite has collected from you. We use the data that we provide to Trendkite to better customize your digital advertising experience and present you with more relevant ads. Trendkite Privacy Policy
Hotjar
We use Hotjar to deploy digital advertising on sites supported by Hotjar. Ads are based on both Hotjar data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Hotjar has collected from you. We use the data that we provide to Hotjar to better customize your digital advertising experience and present you with more relevant ads. Hotjar Privacy Policy
6 Sense
We use 6 Sense to deploy digital advertising on sites supported by 6 Sense. Ads are based on both 6 Sense data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that 6 Sense has collected from you. We use the data that we provide to 6 Sense to better customize your digital advertising experience and present you with more relevant ads. 6 Sense Privacy Policy
Terminus
We use Terminus to deploy digital advertising on sites supported by Terminus. Ads are based on both Terminus data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Terminus has collected from you. We use the data that we provide to Terminus to better customize your digital advertising experience and present you with more relevant ads. Terminus Privacy Policy
StackAdapt
We use StackAdapt to deploy digital advertising on sites supported by StackAdapt. Ads are based on both StackAdapt data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that StackAdapt has collected from you. We use the data that we provide to StackAdapt to better customize your digital advertising experience and present you with more relevant ads. StackAdapt Privacy Policy
The Trade Desk
We use The Trade Desk to deploy digital advertising on sites supported by The Trade Desk. Ads are based on both The Trade Desk data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that The Trade Desk has collected from you. We use the data that we provide to The Trade Desk to better customize your digital advertising experience and present you with more relevant ads. The Trade Desk Privacy Policy
RollWorks
We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.