AU Class
AU Class
class - AU

How Clayco, Inc. Made the Switch to Autodesk Construction Cloud and Autodesk Build

Share this class

Description

Join us as we have a candid and in-depth discussion about how Clayco, Inc., transitioned to the Autodesk Construction Cloud software Autodesk Build from BIM 360 and PlanGrid. This session will cover in detail the specific areas of our Autodesk Build implementation, including how we redefined account admin standards on roles and companies, how projects were onboarded to the new platform, and how Clayco, Inc., took a measured approach to its rollout of Autodesk Build modules. We will provide extensive lessons learned from our adoption, and tips on how we track the effectiveness of our Build rollout. In general, attendees will develop a deeper understanding of how a large design builder develops a framework to carefully scale up its adoption of Autodesk Build throughout its enterprise. This includes having direct and open feedback channels with key internal stakeholders, being transparent with Autodesk product managers on where improvement is specifically needed, and iteratively refining training content over time.

Key Learnings

  • Learn how to create account admin standards to streamline how projects are created in Autodesk Construction Cloud Autodesk Build.
  • Learn how to implement specific training techniques and feedback mechanisms to get buy-in from project teams that are new to Autodesk Construction Cloud Autodesk Build.
  • Discover why it is necessary to have a controlled approach to rolling out new modules to all projects.

Speakers

  • Avatar for Mark Da Gama Rose
    Mark Da Gama Rose
    Mark has over 22 years of experience in the AEC industry. He has worked in a variety of capacities that have provided invaluable insight into the perspective of different design and construction stakeholders. This includes training multiple AEC firms on various design related software programs, performing BIM services on numerous design-build projects and leading enterprise BIM 360/ ACC implementation initiatives at Clayco, Inc. His current focus is on enterprise technology adoption of platform tools such as ACC. Mark enjoys working to meet the needs of architects, engineers, construction managers, subcontractors and building owners. By reverse engineering what is required from an implementation perspective he focuses on what standards are needed, how the end user will adopt these workflows on web and mobile platforms and how data will need to be analyzed at a project and enterprise level. Engagement with IT data teams and software vendors is an essential part of the implementation journey. The main emphasis is to seek feedback about the technology approach from each stakeholder while keeping a constant mantra of questioning its value. This tight feedback loop allows Mark and his team to provide effective training and support while keeping track of lessons learned within the enterprise execution. The goal being to help project teams and executives that face complex design, constructability, financial and schedule challenges to realize the benefits of working as one within the common data environment.
  • Jacob Finley
    Jacob has been at Clayco for three years currently is a Quality Data Analysis Manager in Clayco's Quality Control Department. Prior to Clayco, he received a Bachelors in Construction Engineering Technology and Masters in Engineering and Technology Management from Louisiana Tech University. At Clayco, Jacob works with project teams to make sure Clayco's Best Practices and Industry Standards are followed. Pushing the Punch As You Build Culture to help achieve the goal of a Zero Punchlist. Jacob interacts with teams on a daily basis to provide Safe and Quality projects to Clients using ACC and Dashboards to get to the bottom of issues teaching teams our means and methods to achieve these goals.
  • Christina Norbeck
    Christina has 10 years of experience in the Construction Management industry. Christina has a Associates in Applied Science Construction Management Technologies from Southwestern Illinois College and an Associates of Applied Technology in Carpentry & Building Construction Technology from Ranken Technical College. Christina is currently a Project Coordinator for the Procurement department at Clayco, Inc and has been with Clayco for 1.5 years. Christina's focus is project documentation and implementing platform tools like ACC BUILD. She helps manage the project tasks such as RFIs, submittals, coordinating delivery schedules, and liaison between fabricators and the clients. Christina's goal is to have a comprehensive manual created for her department over all the ACC modules they use.
Video Player is loading.
Current Time 0:00
Duration 0:00
Loaded: 0%
Stream Type LIVE
Remaining Time 0:00
 
1x
  • Chapters
  • descriptions off, selected
  • captions off, selected
      Transcript

      Hey, welcome, everyone. We're going to start this class CS4487-- How Clayco made the switch to Autodesk Construction Cloud and Autodesk Build. My name is Mark Da Gama Rose I'm the VDC Operations Director at Clayco. I've been here about eight years. But my role is primarily to help implement ACC Build, Autodesk Construction Cloud at Clayco.

      JACOB FINLEY: Hi, my name is Jacob Finley. And I'm the Quality Data Analysis Manager for Clayco's QC department. I've been with Clayco three years. And I deal with handling how we use our data and how we change and learn from that data.

      CHRISTINA NORBECK: Hi, my name is Christina Norbeck. I'm the Project Coordinator for our Steel Procurement division, and I've been here for a little bit over a year.

      MARK DA GAMA ROSE: So what we're going to talk about in this class is definitely how important it is to have standards in place when you're looking to go to this platform, how to get buy-in from new project teams that are adopting it, why it's necessary to really have a controlled way to roll out the modules inside of Autodesk Build. And then, how do you collect feedback?

      When you have training, content, what do they think about the content? How do we get feedback from project teams? What's working, what's not? And how do we share that with Autodesk product managers?

      So a little bit about Clayco, we are a full service engineering, procurement, and construction company. The company's been established 40 years ago, revenues of close to $6 billion, EMR of around 0.40 and about 3,500 employees. So a little bit now about the group that I help manage, it's called the Process & Technology Implementation Group. They work across the enterprise.

      We have about five people, primary tasks, I like to call it ABCDE, A being administering applications such as Autodesk Build, BIM 360, Numerix, Drone Deploy. We are available on projects when we go and do trainings and help with project support tasks. And then related to going to doing trainings, we go to the job sites, we develop relationships with that project team. We provide them training, we seek feedback from them.

      We also need to be subject matter experts on all the modules that we support. So really doing a deep dive and how they're used, troubleshooting, understanding the workflows. And then speaking of workflows, just working with all of Clayco's entities, all the way from early design, quality safety, project management, and understanding what they need, capturing their workflow, and being able to train on it.

      JACOB FINLEY: So my role is with the Clayco Quality department. We've had a quality department since 2018. In 2021, we coined the term "punch as you build." It's now our company mission on the QC side of doing projects. With the punch, you build mentality, which is a three-phase quality control plan, starting with the prep work, Pre-Con meetings, getting to define the work, the initial, with all the inspections, and then following up to close out those with the goal of a zero punch. Our quality control department is constantly growing. Currently we have over 40 people in project-specific roles, office support, and regional roles across the country.

      CHRISTINA NORBECK: My department is a Consolidated Distribution Company, also known as CDC. We were established in 2008. Our divisions go from steel, mechanical, electrical processing, and architectural. We can get anything within those divisions.

      Our revenue is over $125 million last year. And this last year alone, our department has doubled in size. And we're close to 35 people now.

      MARK DA GAMA ROSE: Yeah, just a little bit about if you're new to Autodesk Construction Cloud and Autodesk Build, just some understanding of the hierarchy and the terminology. So Autodesk Construction Cloud, also known as ACC, is a cloud-based common data environment platform that is used from early design to handover. It incorporates many different products, one of them being, for example, ProEst, BuildingConnected Autodesk Build, Autodesk Docs, those are all entities of this umbrella, Autodesk Construction Cloud.

      In construction, the primary tool used in ACC is Autodesk Build. And inside of Autodesk Build, there's numerous modules, sheets where all the construction documents live, forms where quality inspections occur, issues where you track anything that is outstanding or deficiencies that need to be rectified by the field teams and subcontractors. Assets, think of an asset as a container. It's where you can track equipment, where you can track construction sequences. There's many ways to use assets.

      And then, of course, since this is saved on the cloud, there is a mobile app. It's available on iOS and Android, it's called ACC app. And that way, you can sync what's in the field to what's behind the computer.

      Now, a little bit about Clayco's timeline of adopting AC Build. You can see we've been around for a while and how we've got to this point. So in 2009, we were an early adopter of Vela Systems, which then got acquired by Autodesk in 2013, which became BIM 360 Field. In 2017, Clayco started using BIM 360 Docs. And the year after that, Clayco started using PlanGrid for issued documents and BIM 360 for its QA/QC proactive safety tracking.

      Then last year in 2023, Clayco switched to Autodesk Build, including our design entity, Lamar Johnson Collaborative, LJC, and our engineering entity, CDE, and also our self-perform concrete division, Concrete Strategies, CSI. And then right at the beginning of this year, Christina's group, CDC switched to Autodesk Build as well. So you can see, this has been quite an evolution the last 15 years of using this Autodesk workflow.

      And then in terms of how we're set up currently right now in the enterprise with Autodesk Build, we've incorporated quite a few account admins or hubs, one of them being primarily being Clayco ACC. That's the hub name. For Lamar Johnson Collaborative, LJC, our design architects and interiors, they have about 225 projects, over 400 users. Our engineering division is in that same hub, Clayco ACC, they have close to 100 projects and 138 users.

      CHRISTINA NORBECK: Next, we have our Clayco Pre-Con hub. They have 16 projects right now and 66 users. Next, we have my division, my department, CDC. And our hub has 37 projects and 235 users.

      JACOB FINLEY: Then within the Clayco hub itself, we have 84 current active projects and 797 users. Within the Concrete Strategies hub, we have 29 projects and 146 users. And then Ventana, in their own hub, has 3 projects in 35 users.

      MARK DA GAMA ROSE: Yeah, so this is a really good context about from early design through construction, how we're set up, which gives us flexibility. We're going to talk about that today. But if you can see how we've kept LJC, CDE, and Clayco within the same hub. But our Pre-Con group has their hub, CDC has theirs, Ventana and CSI has theirs. So it gives us flexibility in how we manage our projects.

      Now we're going to do a deep dive into Clayco's implementation of Autodesk Build. First of all, why did we make the switch? We realized that having construction documents and PlanGrid and doing our QA/QC and BIM 360 was not really ideal. You always needed to have drawings updated when you go to the job site to do inspections. So it's best to really have it in the same platform.

      You can tell with our timeline of the last 15 years, really transitioning to Autodesk Build was more logical than going with alternative separated platforms, such as Procore. And then, we're going to show you that we switched live to Autodesk Build in November of 2023. But really, there was over a year of evaluation, testing, troubleshooting, talking with Autodesk, really doing this proper deep dive evaluation of the tool, understanding what's different to it versus BIM 360 and PlanGrid.

      Then the last point there is just saying, look, we can test only so long. But we really need to learn by actually using it in real jobs. That's the way you really know whether it's effective or not. And so we set a date, and we started to use it.

      And now we're going to talk about how we actually made that switch. I'm going to go through many different areas. And so the first one being, that we really need to think about what could we do better when we went to Autodesk Build. So of course, we said we have the new hub, Clayco ACC hubs for those projects. Now for the last 9 or 10 years, we were in a hub called Clayco Inc that had all our BIM 360 projects.

      You can see on the screenshots here, our companies and role names were slightly different naming convention. So we wanted to do things better when we went to ACC or Autodesk Build. We kept all the employees with their legal company name. So everyone from Clayco was Clayco Inc. And then we really tried to streamline the roles that we're going to have and how we can take advantage of them, and we'll talk about that in a second.

      So obviously, by having this additional hub or account admin now, we can ensure that Autodesk Build projects are set up with their right company and roles, only in that hub. But on the flip side, we now have two different hubs to manage because we still have so many projects that are still in BIM 360 that will close out in BIM 360. And it's just another hub to manage. So just to clarify that, BIM 360 projects in Clayco Inc and Autodesk Build projects in Clayco ACC hub.

      In terms of roles, we really spend a lot of time wanting to maximize the power of this functionality. If you did not role-certified purposes, they're aesthetic, they show up in reports, who that person is and what their role is at the company. Permissions, they drive permissions. And permissions can come in from a template.

      So you can have your folder structure with role permissions. You can have your issues set up with roles. So there's a lot of ability to leverage roles from a template.

      Notifications, this is huge. How does your roles impact how often do people get notified by email? And then ball-in-court, whether it's an RFI, a submittal, an issue, roles have big impact on that. So note that you can always have more than one role assigned to a person.

      Just be really clear while you're doing that, so all of our field staff have this additional role, called Clayco Jobsite Team. But you can see with these screenshots, we've put our reasoning out there for everyone to see on our projects, why we have those roles, who's in those roles, what type of access you have when you're in a certain role, to different modules inside of Autodesk Build, and including what kind of notification settings do you have. So we're going to do some tips here.

      One of the first tips that I'm going to share with you is, when you're looking to go to Autodesk Build, strive to have the fewest amount of roles possible in your hub. And then you can build additional roles if needed. In addition to the hub and the roles, we needed to think about how are we doing project setup. So related to that, you saw we've got this large design and engineering arm of the Clayco Enterprise. And they're within the same hub as the Clayco construction team.

      The reason we decided to do that is a lot of times Clayco will start a design job with LJC or CDE, that then Clayco gets awarded the project later on. And it's easier to transition and rename the project, add the additional standards that Clayco needs. And also, we talked to LJC and CDE leadership. They didn't want to have to create new projects on their side, they didn't want to have to add their own design consultants on their side. If they can be managed all by the Clayco team that does it, they wanted to take advantage of that.

      But now here is where we have the flexibility. Even though Clayco, LJC, and CDE are all in the same hub, they all have their own templates. So if LJC is working on a project without Clayco, they can easily name their project in a certain way, and they can start from their own template. So tip here, make sure you really evaluate before creating a new hub. You don't need to create a new hub just because there needs to be clearer reasoning for it.

      Related as well to project setup, we knew that we had to document all the steps. We knew who primarily is going to be responsible to create the projects. That's people in my team. And then we knew if that person is going to be out, we've clearly documented all the setup steps so that someone else in the team can follow it.

      But we also knew that not every part of the setup was templated. So you can have as much as you want in the template. But then there are certain additional things that need to happen after the project is created from the template. And the screenshots here shows a classic example.

      We have standards on issues and issue types. We have standards on which fields and issue types are required in our projects. Unfortunately, required settings, as of right now, they have to be set per project after the project is created, so it's important to have that documented in your project setup. Tip here, have a template that is just for troubleshooting that doesn't have default members. So you can test permissions, test ball-in-court workflows without notifying all the people in your default template.

      The next part of how we made the switch was, we really wanted to take advantage of having a clear folder structure. Because we were having a structure that starts in early design, all the way through handover, we really have many entities. We have our architects, our engineers. We have our outside design professionals.

      We have all the Clayco staff. We have our subcontractors. We have our owners on our projects. So we needed a document that would clearly explained, what's our folder structure, what's in each folder, what's the permissions for each folder? So that way, we can put it out there, and then we can constantly update this document.

      Because as you can imagine, there's been a lot of tweaking of, as we start to see, oh, we need to add a folder. Or we need to change the permission. Or we need to consolidate these two folders here. So tip here is make sure if you have a folder-structured document, you keep it up to date, you keep your templates up to date so new projects can take advantage of that updated structure.

      And then going into some of the deep dive that we did, we knew what we wanted to start with when we went live. In terms of what we were doing in BIM 360 and PlanGrid, we had files, we had sheets, we had forms and issues. So those form modules in Autodesk Build were going to be used when we made the switch.

      If you are not familiar with forms, they're the equivalent of BIM 360 checklists. So we had to do a deep dive into understanding, OK, what are the statuses between BIM 360 and ACC when a form starts, and then it goes in progress, and then it gets closed out? We not only need to know that for training purposes, but we need it to know that because we have Enterprise dashboard that takes data from BIM 360 projects and Autodesk Build projects.

      But then during this evaluation, we realized that some of the forms data couldn't be extracted for our Enterprise dashboard. So that caused us to delay til November of last year. And then speaking of forms, we really have to think what is the workflow?

      Forms act differently to BIM 360. So how do permissions work per template? They have new things like review status. So we really have to really understand that and document it. Tip here is when you're looking to go to Autodesk Build, know what is your bare minimum modules you're going to start every project with as the baseline.

      Related to training content, we really wanted to put our training content out there. We want it to be public-facing. We wanted it to iterate quickly. So we leveraged the Bridge module in Autodesk Build to do that.

      We have a central project. We push any updates to it. Tip here is make sure if you're doing this that any file that gets renamed or deleted doesn't auto-update in all the projects that are receiving the Bridge content.

      JACOB FINLEY: So as we were making the switch, we really wanted to leverage the Punch As You Build momentum. Punch As You Build is our key thing that we've been pushing so that we get to that zero punch. We promoted this in the Autodesk Build improvements, whereas now the forms go into a review, which forces all of our teams to take that extra look to make sure the work's done the correct way the first time.

      Now we're able to require that you have to give an assign to. So you have to assign that issue. We have a whole dashboard that just basically tells us what issues are unassigned. Because in BIM 360, you couldn't require the locations or the assigned to. And the real heartburn there was those issues would not be assigned. And then 60 days later, they're still unassigned and haven't been taken care of when really, they were a quick fix.

      The locations, we've had several issues. You can go look at it and go to the person that made the issue, knows exactly where it's at. Anybody should be able to pull it out.

      So those two key pieces, along with other required fields, have helped us on the data side a ton. The other thing we're able to leverage now is to its highest level on the projects that have full time QC and VDC is the asset to really take that Punch As You Build and process to the next level.

      MARK DA GAMA ROSE: Yeah, and one of the things we had to do is make sure we had a clear training So project teams knew how we were going to engage with them. They knew how we were going to assist them with the transition to Autodesk Build.

      And that all starts with, we have a 30-minute remote call introducing the team to Autodesk Build. We then, from there, schedule on-site training with that awarded team once trailers are mobilized with Clayco team. And then a separate call where the early work subs on training them how to do Punch As You Build Inside of Autodesk Build.

      And then six weeks from there, my team will do an audit and say, OK, is that team really kind of following the standards that we talked about? And reach out to them if they're not. You can see the screenshot here on the right. We do use the Plan module in Autodesk Build to show our engagement with every project when they're created in Autodesk Build, when the project is closing out. When we do some training, our audits are attached in there as references. So it's a great tool to help us be organized.

      And then I've told you that we started going to Autodesk Build November 1 of 2023. Well, when we did that, because Clayco's a large full service company, we had all these projects that were in BIM 360 in design up to that point, maybe 8, 9 months in design. But when we announced we were going to Autodesk Build from November 1, all Clayco operations projects that were transitioning to construction at that time said, hey, we want to transition as well.

      Easier said than done, so it's really understanding what can transition from BIM 360 to Autodesk Build. There is no upgrade button. So things like transmittals, issues, checklists, those can be archived. But they can't be transitioned up to Autodesk Build. So you really need to be clear if that's going to happen for you.

      And you can see here with the screenshot on the right, we documented our whole procedure of how we're going to do it. We'll work with the project team, set expectations. What do they have in BIM 360? Has them team been informed that when we're making the switch and why we're making the switch.

      And then what's the plan per week to transition the team? And this screenshot is actually from a large, high-rise project in Phoenix where three towers, we were actually not at the infancy of construction when we did switch from BIM 360 to ACC Build or Autodesk Build. And we made it happen.

      JACOB FINLEY: That was how we roll out that Autodesk Build while so many people are still using the PlanGrid and BIM 360 projects, that becomes a struggle. Because in our different meetings across the enterprise, we're constantly showing our new processes, our new changes, and new things that everybody should be focusing on, while so many are still in those older projects.

      MARK DA GAMA ROSE: And related to BIM 360 and PlanGrid, when people start getting onto the new project and Autodesk Build, of course, they compare it to what they in BIM 360 and PlanGrid. So in the Sheets module is imperative, to look at issue drawings in the field. Well, everybody loved in PlanGrid how easy it was to search sheet content. In Autodesk Build, it for sure happened. It's just a different process.

      And it was just kind of training, setting expectations, clarifying how the process works and just saying, look, get on board. This is how you can search your content in Autodesk build.

      JACOB FINLEY: Another really big challenge that we're coming across with some of these major big projects is the clients that they want to use Autodesk Build, but they want to use their hub, which is a problem for us. Because we're wanting to learn off the data of those projects and go back for warranty in the future. But with those being in their hub, right now, there's no connection to give us that data to learn off of, to go back to. And there's no guarantees we'll always have access to that data.

      MARK DA GAMA ROSE: Another challenge we faced is that the software. But like I said, with Forums, we particular had a limitation, where in BIM 360, you can assign checklists when a user is creating a checklist. In Autodesk Build, you're assigning a form as part of the form template permission.

      So it's a totally different way of working. We had to wrap our heads around it. We had to really set up our procedure, our standard. Who's the editor, who's the reviewer, who's the manager and really be clear on what those standards are, but a lot of testing. And then we really had to train project teams. Hey, the difference of BIM 360 now, if you're looking at the questions, look at that in the Template tab. Don't look at it after creating a form.

      Because now you've created a form. The form is already in progress. So we need to make sure that we don't have all these accidental forms just getting created because people are looking at the questions.

      JACOB FINLEY: Another big issue we've been seeing is who's closing out the issues. We've gone through and set up processes. So our technical assurance group, if they create an issue, they think it's rare enough that they want to close those issues.

      Well, there's no workflow problem. There's no workflows to limit that. The same thing with creating the issues, there's nothing that prevents anybody else from creating an issue under those types. So that's causing major issues on the data side to make sure that the right people are using the correct issue types and closing on that.

      MARK DA GAMA ROSE: Another big challenge, and all of you should be aware of it, is notifications. So we met with the Notifications product manager to get guidance on, what does this notification setting really mean, and where is the impact for it? So they gave us information about that. And then we use that to help set up our internal standards.

      So again, document, document, document, all your frequencies, all your standards, and why your reasoning for setting that setting. Because you'll invariably need to come back and reference the reason why. For example, Forms have this particular type of notification frequency. It's a tip here, but really important when you're going to Autodesk Built, leverage notification groups carefully.

      Notification groups are powerful. They are an override. You need to take advantage of them without getting yourselves in trouble.

      And then, of course, like I said, and success is right off the bat. We knew we were going to see the value of having our QA/QC and our issue drawings and specs in the same application, same platform. I mean, whether you're behind the computer or walking on site, and so that was a huge benefit.

      JACOB FINLEY: One of the really big improved capabilities over BIM 360 and PlanGrid was our scheduling. The scheduling module, as well as the asset markups, where our teams can go and look at their schedules and then go make the assets markups within ACC, within Autodesk Build, so that they can fully leverage that Punch As You Build mentality by using both those modules.

      So as one of our big successes is that high rise project that Mark brought up earlier. So it's a very early stage. Transitioning them was getting a team of probably about 30 people to learn, OK, you're going from BIM 360, now to Autodesk Build. This is how you do it.

      So we reached out and said, we want to see what was your actual struggles, what feedback do you have? And I said the subs, the subs, having trying to teach all these people of different levels, how to use the software. A lot of people thought it was really seamless. The biggest thing, I think, that makes a difference is having a good support team, not only on site, but for others to reach out to away from site. That was our basic success with that is the amount of support given.

      So this table shows our success within the last year. Data started trickling in September 2023 before we made that really big jump in November of 2023 of where are we going into ACC. Our Autodesk Build now, with almost a quarter of all Clayco projects within Autodesk Build, which is a big step for a company that does projects that last a minimum of about 18 months to 2 or 3 years, a quarter of your projects. It is great. And we're seeing the issues and form numbers just continue to trickle up.

      MARK DA GAMA ROSE: Yeah, so now what we're going to do is we're going to show you-- we've talked about Clayco's implementation. Now we're going to show you one of the Clayco companies called CDC and how they've implemented in the past year to go to Autodesk Build.

      CHRISTINA NORBECK: So like Mark said, we're a separate-- we're an entity of Clayco. So because of that, we don't have the same process and standards as Clayco. And because of that, we started off pretty much with just working off an Excel spreadsheet. And we need to standardize our cover sheets and our processes.

      Because we just were using Excel, we had no way of tracking any of our open RFI submittals or issues. We needed a platform that could help us improve that tracking of our RFI submittals and issues and also our assets. When we looked at transitioning, we originally looked at Procore just because some of our vendors had used it. And then we realized that Clayco had already been looking into Autodesk Build, and we figured out it was the right fit for us.

      Something else that we were wanting to look into for CDC was cost reporting. Some of the main areas that were greatly needed for us for improvement were our RFIs, submittals, our schedule plan, and assets. An added bonus of what we use right off the bat were Sheets, Correspondence, with the different types and the Reporting.

      So our switching to Autodesk Build was a little bit harder than if we were part of Clayco. So we started off with a job that was close to our office so that we could monitor the activities. We had continuous training with Autodesk and with Mark's team on all the different models. I'm creating a training model that's specific for CDC because we're separate from Clayco, that some of our standards are different from theirs. We have started telling our vendors to switch to Autodesk Build also, and for them to submit their RFI submittals and any of their larger files directly into our hub.

      So we had a few challenges. We've grown quite large with Autodesk Build in these last months since we've started. We have 37 projects now. Like Mark and Clayco, there's definitely a lack of automated features when you're creating a new project. So to the right is a snip of just a checklist for all the coordinators to know when we have a new project. These are the things that we need to make sure are up to our standards.

      We're growing so fast that we're continuously adding to what we have started and what we're learning. And with that, we're figuring out the best way to track our assets and tracking what will work for us. We've been working with Mark's team and Clayco to connect our asset tracking with how Clayco wants their standard assets to be tracked also. As we're growing, we're continually teaching the rest of the team, so that way we can bring all the divisions into this to our hub and all the new projects.

      We are also working with transmittals. When we get new drawings, we want to send those out to our vendors so that if there's any cost impacts, they can let us know. Recently, the Reviews module has come out. And we found that is probably going to work better for us than Transmittals. So that's something that we're transitioning to right now.

      With Correspondence, we send that out with all of our RFIs and our submittals. And we put on there the due dates that we expect them back. Right now, there's no report to go off the Correspondence tab.

      These pictures right here is our success story as it is. We had no way to track any of our RFI submittals issues, anything. And this shows how much we have come from a spreadsheet. The work status is up great.

      Just quick glance for any of us to be able to look and see what are we still missing. What do we need to get back to our vendors? With assets, we've got the QR code now, where we can have our vendors be able to update, and then once we get to the job site, for the receiving team to check material in. And this is a great improvement for us.

      CDC is also working on an Insight Builder. Right now, we had no way for our PMs to be able to look across the board, which projects they had that had overdue items. So this is something that they asked a lot about. And Autodesk Build is providing it for us. So an individual can look in here and see their jobs. Or our managers can look in here and see across the board, how CDC is performing and what we need improve on.

      MARK DA GAMA ROSE: So now you've heard about Clayco's implementation to Autodesk Build, CDC's implementation. I'm going to show you how we're trying to marry the two together and how they're impacting each other. Go ahead, Jacob.

      So what's next for Clayco? Using that data from Autodesk Build to teach and train to minimize recurrence of issues. Recurring issues cost money. Also, the rework causes more injuries. 40% of injuries happen during rework.

      And our safety department, as you saw, had a really low MR, is trying to capture that information. But we want to get ahead of it so that we can teach on what's causing the most rework and reduce not only the cost for us, but for our subcontractors. We're all wanting to use that data from Autodesk Build to also know what our high-risk issues are, as well as implementing the different modules and spec sections.

      The end goal right now, we're using a software called Domino to look at all this information. But in the future, we're hoping to be able to use Autodesk Build so everything's within the same place. Because simplicity is the key for us.

      CHRISTINA NORBECK: So what's next for CDC? We're looking into the cost module to see how we can incorporate each division into the cost management for full reporting, full integration. Data analytics, I just showed you the Insight Builder, which is great. But we're looking how to incorporate the whole CDC department with that. And with that, we have found out that we have to give the executive role to everyone to be able to view that

      AutoSpecs, we're learning the functionality between AutoSpecs and submittals to streamline submittals process. And then we're also looking to additional division integration between Autodesk Build. We're figuring out which modules work best with each division.

      So how does CDC implementation impact Clayco? So we're working on our equipment material receiving inspection process or our MRI form. With CDC, we start that process with putting that in our hub first with our list of assets and then creating a form inside the Clayco hub to let them know that they're going to be receiving a BOL shortly.

      As soon as Clayco gets that notification that there's a delivery coming, they will then assign that to the vendor, the sub that is working on receiving the material. From that stage, they will then mark it as everything came in great. There's a damaged material, there's something missing, or even something that's an additional item on the truck that wasn't on the BOL.

      From there, they'll create an issue. That issue will be assigned to CDC. And then CDC and our hub will then create an issue on our side and then assign it to our vendor. So it's going to be a full circle.

      Once that form has been completed and Clayco has reviewed it, they'll then close it out, which then we will then get notified that it's been all received. Then if there's an issue, we will go through that process of getting that fixed.

      MARK DA GAMA ROSE: And there's a lot of senior management watching how CDC is taking advantage of Autodesk Build, what benefits they're gaining from it. You can tell from this presentation that there's slightly different adoption and how they've rolled it out. There are different companies.

      So they're using submittals, they're doing RFIs, they're using the correspondence module. So they're really making sure that Autodesk Build is their central platform for all project functions. And Clayco can glean from that and leverage Christina's team and what they're doing and hopefully influence Clayco with our Autodesk Build adoption.

      So now what we're going to do is, we've talked about why and how we've implemented and how we're working together to help each other and where we're going. But I want to leave you guys with some understanding of a term we call a process framework. And this is really for implementing a large platform tool such as Autodesk Build.

      So step 1 is really knowing what are the areas that you're tracking to help you. So I'd like to call it-- there's nine areas of the process framework. They work together. They're constantly in motion. By looking at each one, one of the nine areas, you can implement carefully and correctly.

      And of course, every day, every week, there are changes come up, changes to a standard, changes to a training document, changes on getting stuff approved. So you really need to have these gates in place so they can help you. This process involves a lot of people outside of just Christina, Jacob and I. We have a whole slew of people at the company that provide feedback to help us improve our implementation of this build.

      Tip here is, you don't wait for any of these areas of the process framework to be perfect before you start on them. Start on them immediately so you can get an understanding of how they can help each other. So we're going to go through them in detail, starting with standards.

      So the standards is really the kickoff of again, how we get into Autodesk Build, how we can leverage it. So on the left, this first picture is our quality issue, standard-type poster. That's on every job site. It's required.

      You scan any of these, and it brings you up to a QR code of a PDF that shows you how to use that issue type, not only how to use it, when to use it, but how that issue should look. Who does it go to? How does it get closed out? Doing this allows the data to get filtered correctly.

      And this actually started right shortly after the Punch As You Build really took off with momentum. In the center here, we have our issue workflow for our architects. How does the architect create the issue? Well, they need to use one of two types.

      Let's fill out these fields. And then with that required part, it automatically gets assigned to the Clayco jobsite team. Or we're requiring a field, we tell them, get on the job site team so it's always going to somebody.

      Then we have the analytics. This is the part that again, we're learning off these issues. We're trying to build off these issues and prevent the reoccurrence of these those standard issue types.

      That's what you see in the top right. Before we came up with those standard issue types, jobs were kind of just doing what they felt was right, what the owner told them to do, what the project team really wanted to do. It was like a kid in a candy store trying to figure out what was going on with these issues. Then one of our required fields is a CSI division number that shows us where our issues are going to lie. Because each month, though finishes is always probably going to be the number one with as many high rises and different buildings that we do, we're able to see where the issues drill down into each one of those divisions, based off of how big that number is.

      JACOB FINLEY: The next one of the process framework is training. So like I said, we have a standard process. Our team goes out there, we have standard email address. The clock starts as soon as the project gets created and in Autodesk Build.

      We track that date. From there, we reach out to the team, and we schedule an intro training, 30-minute call. So as more projects start to use Autodesk Build, there will be pushback. Hey, we already know how to use the software. We're good.

      No, maybe the call will then be shorter. But there's always process improvements. There's always updates. Each new team needs to go through this.

      And then from there, the next chain and the link is with training, we schedule the technology training on site. So it's with the Clayco team. We sit down with them for an hour, and we talk to them about how to manage the Punch As You Build process in Autodesk Build.

      And then the early work subs, the earthwork sub, the underground utility subs, the concrete sub, we work with them. And we say, OK, this is how you're going to fill out your forms and how you need to respond to an issue Clayco assigns to you. We will come back later after around drying, around the framing point to train the additional subcontractors. And also, we really are excited to take advantage of using location QR codes, so that on all of our floors and all of our rooms that we can have a QR code, that anyone can scan on the mobile app on the project. And I'll tell you what forms are outstanding, what issues are outstanding, and how the information is tracked using assets.

      So with every time we do a training, we're going to do audits. So six weeks after going there, we'll create an audit. So that way we can monitor how that team is following our standards.

      CHRISTINA NORBECK: So we always want our feedback from the end users. So we have a group email which provides the following. Timely response from anyone in Mark's team that they can react to. Project teams do not need to know who that support person's name to contact. And the support email is easy to remember.

      We have that QR. So anyone on the build can scan that and reach out to Mark's team. At the end of on-site training, we want feedback from everyone that was involved. Six weeks after doing on-site training, we send a project member back a survey to request their feedback from Autodesk Build and we don't discount any feedback from any user because it can all be different perspective.

      JACOB FINLEY: So in all of this, there has to be a change approval workflow. The right stakeholders that are responsible for all the changes that happen, without this, it becomes, again, just a kid in a candy store, creating what they want. Before we created this process, we had five of the same checklists. They were all different variations.

      So now, our director and associate director, everything has to go through-- it goes to Mark's team. They go, OK, yes, we've already got this. We don't need this. Or, hey, we'll take it to the QC heads and get them to look at it and whether or not they approve it, where it goes, keeping this centrally managed so that it prevents the pathology teams from making these changes and prevents that kid in a candy store-kind of mentality.

      So with this change approval workflow, we have the two workflows on the right that tells all our teams, that is located in Autodesk Build with our training material. This is what process you need to follow in order to get those changes you may want approved.

      MARK DA GAMA ROSE: And also, since there are changes that happen daily, weekly, monthly, it's easy to forget, maybe after a year, of all the changes and the reasoning, why we made the change, who approved it, when it happened. So we log it. We log it in a spreadsheet. We make sure we track that so we can capture why and when and who approved that change.

      JACOB FINLEY: Then we get into auditing the projects. This is really important because you can't limit people from using the quality-quality, architect-architect, those standard issue types that Autodesk Build has built into it. So how do you constantly go in and teach teams have to pick a subtype in order for the data to really be meaningful?

      Then while auditing, we also do our Punch As You Build process audit. This is what that looks like. The picture on the left is issue created by month from our demo software. And you can see that issues really didn't start til the very end of the project, which is not ideal.

      You're costing more money. Probably, somebody's going to be there months after the project is completed trying to get these issues done. It should look more like a roller coaster effect, where you're just kind of, at the end of the project, settling down to one or two issues, ideally zero at the end, and then the days aging on the right. How old are the issues. Why are they staying open?

      At Clayco, we have a policy. If it's older than 20 days, somebody needs to comment on it and say, why is this older than 20 days? Try to keep that zero punch mentality down going.

      MARK DA GAMA ROSE: Yeah, and then we really wanted to make sure we get buy-in from senior management, sharing updates with them, sharing what's working, sharing what's not, being really factual, so that we're not sugarcoating. And just really kind of understanding benefits of our workflows within Autodesk Build.

      As you can see with Punch As You Build, how it benefits owners, Clayco's subs. And the screenshot down the bottom right, just really kind of breaking down, like Jacob said, working within a different platform or getting subs to buy in. It's really important to keep your senior management involved so they can help promote, but also let them know the challenges you're facing with current implementation.

      And then regarding workflows, really, don't focus on the software in the modules. Focus on the workflow. Focus on how to get traction with an established workflow at your company.

      So speaking of workflows, what is it? And then what's the particular value that it provides to the project team and the organization at large? That is really here. It needs to be documented and defined.

      You can bring in more modules if they kind of enhance that current workflow. And the last bullet here cannot be understated. Once you go to Autodesk Build, you'll notice there's synergies between the Asset module and the Forms module or maybe the Issues module and the Correspondence module. And they need to work together in tandem.

      And so how do you define that workflow? How do you train people on it. And how do you make sure that synergy between modules happens? The screenshot is just really showing you again, in detail, how forms, get started, how they get closed out.

      The next one in the process framework is really, if you're not sharing feedback with the Autodesk product managers, you're losing something to help your organization. Have a process that you can lock feature requests. You're going to hear feature requests all the time. We have a way we track them inside of an Autodesk Build project. They go to our account team that ensures it with the product manager at Autodesk.

      We also keep a top list of features that we want per module. And then we share these documents with the product managers and schedule meetings with them. So we can go through in detail, what do we want to see? What updates do we need? And why do we need it? Why is that important, how that impacts our projects?

      The screenshot at the very bottom there is showing just a simple example of the mobile app, how we stress the need for wrapping the issue title when you're looking at issues on your phone or iPad. And that was so critical to. Have and Autodesk delivered on that.

      And then the last one, but not the least in the process framework is, we have all these projects inside of Autodesk Build. They're all running and doing their project. They need to get the job done. They need to stay on schedule, they need to delight the client, they need to focus on their QA/QC.

      Well, they're doing some great things inside of Autodesk Build? How do we, as an organization, capture that quickly? So we're starting to catalog these one-pagers, where we can say what are they using within the platform, who is the proponent of it, and just do a little write-up with a couple screenshots. If you do not do this, it will get lost within the projects. And by the way, it's important to have this because project teams want to see how their peers have used it, instead of just hearing from someone like myself, Jake, or Christina because they know we might be biased.

      So to wrap up now, we're just going to talk about a different way of how Clayco is rolling out Autodesk Build. You saw our numbers with members and hub arrangement. Now we're going to talk about just really how we use it, simply from a use case and modules we use.

      So LJC, right. Lamar Johnson Collaborative on the design side, architects and engineers, of course, they use it for design coordination. They also do it for all their construction admin, and they use several modules within Collective Projects. But because LJC is working on projects without Clayco, they could take advantage of modules that Clayco doesn't use on their own projects, like just RFIs and submittals. Our engineering group CDE, they also use it for design and construction admin. And they are using several modules within the platform as well.

      Next, we have Pre-Con. They're mainly using it for estimating. And their main platforms that they use for their projects are BuildingConnected, and then within Autodesk Build is Files, Sheets, Markups, AutoSpecs, and Takeoff. For CDC, my department, for procurement, we're mainly using it for material tracking. And the models that we use within Autodesk Build is pretty much all of them at this point.

      JACOB FINLEY: So then you get into the construction part of Clayco. And how Clayco uses it is the QA/QC, the safety, and the field management. With the modules that we've talked about, the Files, Sheets, Issues, Forms, transmittals, Reviews, Meetings, Reports, and Schedule Assets.

      Then you have Ventana uses it specifically for field management, using it for RFI submittals, and photos on non-Clayco projects. And then on the use cases for CSI, under Strategies, they use it for and their field management. While on Clayco projects, they use the Files, the Sheets, Issues, and Transmittals and Forms. But when they're not on a Clayco project, they're using the RFI submittals and photos.

      MARK DA GAMA ROSE: Yeah, so now we're just going to wrap up and just kind give you some key reminders, takeaways.

      CHRISTINA NORBECK: So it's critical to have a robust standard in place, troubleshooting all workflows before implementing them, and then making sure you're focused on employing solid workflows, not just all about the Autodesk or Autodesk Build modules.

      JACOB FINLEY: Then it's documenting all those processes, including the administrative and end user training. Probably some of the biggest parts is document everything you're doing, developing a process framework that seeks feedback from the end users and stakeholder approval for any changes so that everything's kind of locked down. But you're still open to what everybody's ideas are.

      MARK DA GAMA ROSE: Yeah, and then make sure you're sharing your feedback with Autodesk, especially the product managers and the Autodesk consulting team. They can really give you good guidance. And then the last one here is if you're not sharing how your implementation is going with senior management, you really are missing a big gap there. So be clear with them. Let them help you to get the buy in.

      And we just want to say Thank you guys for joining this session. We're excited to share it with you and appreciate you sitting in.

      ______
      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.