AU Class
AU Class
class - AU

The Art of Bridge: SSOE Group's Secret Weapon for Long-Term Success

Share this class

Description

Whether a construction project is simple or complex, it's important that everyone on the project has the same information to deliver work faster. SSOE Group is no stranger to this concept. Named a top architecture, engineering, and construction firm for more than a decade, SSOE Group specializes in delivering complicated, high-stakes projects and sustaining client support through long-term program management, having saved their clients $2 billion since 2009. Even after 75 years in the business, SSOE continuously develops new workflows to facilitate effective cross-team collaboration by using the Bridge collaboration tool in Autodesk Construction Cloud. This agility has contributed to 150 of SSOE's clients staying with the firm for more than 20 years. Join Luis Angel Garcia from SSOE Group and Matt Burness from Autodesk as they walk through the product basics of Bridge and share SSOE's best practices of implementing Bridge to standardize data sharing and ensure everyone on the project has the information they need during and after construction.

Key Learnings

  • Explore the basics of the Bridge tool in Autodesk Construction Cloud.
  • Gain insight into how Bridge can optimize the sharing of documents throughout the project lifecycle, from design to operations.
  • Learn SSOE's best practices to implement Bridge for effective collaboration processes across client and partner stakeholders.

Speakers

  • Luis Angel Garcia
    I have over 15 years in the AEC industry, I've had the pleasure of wearing many hats. Currently, I'm a Technical Leader at SSOE Group, and part of the fantastic international SSOE team based in México. In my role, I lead technology initiatives within the Project Technology Team, including the implementation oc ACC as our Common Data Environment, and drive various VDC efforts. I'm truly passionate about the impact of technology. I believe it's a powerful catalyst for positive change, enhancing not just the efficiency and quality of our work, but also making it more enjoyable. Every day, I focus on finding innovative solutions that make a real difference in our daily workflows. Outside of work, I'm a proud husband and father. I enjoy life with muy wonderful family, fostering optimism and positive valuses as we look forward to a brighter future together. I'm excited to share my journey and insights with you all at AU. See you there!
  • Matt Burness
    Matt Burness is the senior manager of product management for standards in Autodesk Construction Cloud (ACC). He oversees product strategy and development for the Bridge, Project Templates, Library and As-built export tools. Matt joined Autodesk as part of the PlanGrid team where his focus was also on standardization and cross-company collaboration. Prior to this, he worked in design and architecture and holds a Master of Architecture from the University of Sydney.
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

      MATT BURNESS: Welcome, everyone, to the talk today, called The Art of Bridge, SSOE Group's Secret Weapon for Long-Term Success. Before we get started, just a reminder that we may talk about future-facing roadmap items. And at the time of this recording, that is what we will be building. But please know that plans can change as we learn more and adjust to what the market is asking for. But with that, let's move into the talk.

      To begin with, I'm going to introduce myself and briefly introduce Luis García, who will talk more about what he is working on later in the deck. My name is Matt Burness. I'm a Senior Manager of Product Management with a focus on collaboration and standardization in the Autodesk Construction Cloud.

      And today, I'm excited to talk to you about the basics of Bridge, how you might think about using Bridge, and understand how Bridge works. And then Luis is going to talk more about how he and his team at SSOE are using it. So let's dive in.

      I want to step back for a moment and talk about where we started with Bridge and the data fragmentation problem that has been present in the industry for some time. As more and more companies use cloud collaboration solutions for design and construction management, there are data silos created for each account or hub belonging to these companies.

      Historically, the only solution available was for everyone to participate in a single company's hub for a given project. This streamlines collaboration that causes data ownership, standardization, and operational risk. The construction industry is tirelessly working to improve processes to be as efficient and competitive as possible. And to drive these business goals, it is critical to standardize processes and derive insights across projects within a company.

      Folks are, of course, motivated to maintain their own hubs and projects to achieve these business goals. And so Autodesk worked with folks like Luis and SSOE to understand how we might build a solution in Bridge to ensure folks can work on their own hub while still collaborating seamlessly with other companies. With Bridge, we are working to break down data silos within hubs and accounts and allow companies to collaborate seamlessly with one another, to share data and initiate workflows across hubs, when it makes sense, while meaning maintaining full control for your teams, your intellectual property, and your data.

      At the heart of Bridge is the ability to federate data. And to better understand data federation, let's compare it to how most organizations are currently addressing the issue of disconnected or siloed data. As I mentioned, the most common practice for companies today is to consolidate project data and workflows within a single hub.

      This model has some downsides. It raises privacy and security concerns. Because teams are all plugging into a single hub, there's a risk that the wrong people can access sensitive information. And perhaps you don't even want to add sensitive information to the platform, in that case.

      It creates data silos, as I mentioned. Using a single hub for data consolidation doesn't eliminate the issue of disparate data and workflows. In many cases, what ends up happening is each team member plugs into the main account while simultaneously running their own project within a separate account or hub. As such, project information is still scattered across different sources, making data aggregation manual and time consuming. And this, of course, leads-- can lead to delays and potential rework.

      Other parties also risk losing access to important data. In this single-hub approach, data ownership is not necessarily clear cut. Since just one company technically owns the account, other stakeholders can lose access when the project ends.

      Instead, data federation with Bridge allows seamless collaboration across ownership spaces by connecting the right data to the right teams at the right time. Data federation doesn't require all teams to work in the same hub. Instead, every company has their own hub. And the information from these accounts is voluntarily shared to other project teams.

      As a result, each company can control the process of saving, storing and sharing project information without creating data silos. This diagram illustrates how data federation works at a high level. By federating data across hubs with Bridge, companies can rest assured that they will never lose access to their project data while critically being connected to, again, the right data and the right teams during the project.

      So now let's talk a little bit more about why you might need data federation. At a high level, we talked about operational efficiency, risk management, and being able to make better business decisions. But let's dive a little bit deeper into each of these areas.

      You may have invested some time in developing company standards or in managing your team in a way that makes sense for your organization. Bridge allows you to maintain those standards and continue to manage your team while providing the opportunity to optimize your processes over time. You can reduce risk by ensuring that you always maintain records for warranty or potentially litigation purposes. And you have an audit log that is maintained in your own hub and account.

      From a business decision standpoint, because all of your data is owned by you in your account and hub, you can more easily leverage business intelligence platforms across the standardized data within your account, across your projects.

      At a high level, in ACC today, Bridge allows you to share only what you need, when you need to share it. This is facilitated by automations. So you don't have to remember to share new versions of files or sheets. It provides an audit log of data that has been shared from your project or received into your project, and controls to allow you to stop sending or receiving data, as well as completely severing a connection to another project or hub if necessary.

      Let's dive deeper still into the Bridge workflows we support today in Autodesk Construction Cloud and some of the new features that we have released relatively recently. Today, we support sheets, files and folders, automations on both of those, push and pull workflows, design collaboration teams, and select Revit Cloud Worksharing workflows.

      Recently, we enabled the ability to bridge data exchanges. Data exchanges allow users to share data, such as the lighting fixtures in a model, without having to share the entire Revit file. This can then be consumed within and beyond the Autodesk ecosystem, with integrations in Revit, AutoCAD, Inventor, and some third-party systems.

      Now Bridge supports sharing data exchanges created in ACC. And to do this you simply need to share the Data Exchange file from within the Files tool. This means that for the first time, you can share a Data Exchange beyond the ACC project it was created in. And as designers, you now have more peace of mind knowing that you are not sharing your entire design model, only the views that are necessary for collaboration and coordination.

      We'll look a little bit more into this in the coming slides. But I want to also highlight another recent release. And this is support for Informed Design. Informed Design is a platform-based solution that brings manufacturing information to the beginning of the design process, to inform design decisions and improve project certainty, prevent errors, and accelerate workflows.

      The Informed Design integration with Bridge now allows manufacturers and subcontractors to publish products to their own ACC project folders and then seamlessly share those folders with designers in other accounts and ACC projects. Finally, if you are a PlanGrid user, you can now import PlanGrid as builds directly into an ACC project of your choosing.

      As part of all of these, we have-- we are striving to enhance the audit log in Bridge. With these recent enhancements, we are improving Bridge's visibility and traceability by logging activity data to provide more comprehensive and accurate audit trails. For the first time, you will have a record to see who sent an invitation to Bridge, who created a bridge, who created automations, and various other activities to do with those actions.

      This, of course, is just the beginning of Bridge. There is still a lot that we want to do. And we are excited to continue to work with SSOE and many others to continue to shape the future of Bridge.

      But let's dive a little bit deeper into each of the different workflows. Here, we can see the ability to link projects by sending an email invitation to a collaborator. The recipient can then choose a project they wish to connect with Bridge.

      This gives both the sender and receiver control over what they are sharing and the connection overall. Next, we see the ability to share files from within Bridge by searching across the project for the file you would like to send. You can then choose the Bridge project to send it to. And you will see the actions that you just performed, both creating the bridge and those share automations from the activity log that you can see on screen now.

      Next, we will see the ability to import files and sheets. This workflow is similar to the publish workflow we saw previously. But in this case, you are importing content from other projects, not pushing it from this project to others.

      In this case, you will, as a user importing content, need to have sufficient permissions in the origin project to pull in this information. This workflow, as you can see, supports files, sheets, and most recently, as I mentioned earlier, PlanGrid as-built exports. Here, you can see you can add messages for internal reference to understand why content was imported into your project. And of course, you can select the folder into which you would want that content to be added.

      Next, we are going to have a look at the ability to share a Data Exchange. For folks who are less familiar with Data Exchanges, this video is briefly going to show you how a Data Exchange is created. With a file that has various views, you can simply create the Data Exchange from the Model Viewer. Select a folder in files to save that Data Exchange to. And of course, give it a name.

      Once that is done, the workflow is very, very similar to what you have seen in those two previous workflows. You can then choose the file that was just generated, or the Data Exchange that was just generated. You will see here that this is a specific view, not the entire Revit model, with select content walls and columns. And then you can choose to bridge this to another project. This, of course, then means you can coordinate models without necessarily sharing everything in your model. And this flow will look very similar to previous flows.

      So let's now take a look at who might benefit from using Bridge. Because Bridge facilitates connections and data flows between any ACC hubs-- of course, both parties on the sending and receiving sides both need to opt in to this workflow-- it means that it can be used by anyone using the Autodesk Construction Cloud, from owners to general contractors to designers to subcontractors. And it has benefits to all of these parties, as we will talk about briefly now.

      As an owner, you want to maintain copies of all final documentation potentially within Autodesk Construction Cloud during construction and critically for the life cycle of the building that you own and operate. You want to ensure all of that data has been captured to maintain a living record and to facilitate reporting and analytics. With Bridge, collaborators, whether they are general contractors or other collaborators, can share information using Bridge directly into your ACC account.

      All documentation then is owned and maintained in a single location and then can be used throughout the life cycle of the building. As a general contractor, you want to maintain your own ACC hub, perhaps even if the client has one, or, if you're collaborating, trade partners or subcontractors have their own. You want to ensure all stakeholders are working from the latest project data. And you want to easily receive as-built information from trade partners and transmit that to clients.

      Bridge allows you to connect to all of these different stakeholders while maintaining your internal processes and complying with contractual obligations. Bridging files, sheets, and as-builts facilitate all of these different workflows.

      As a subcontractor, you want to confidently work from the most up-to-date information. You want to keep a historical data for your records. And you want to use your company's standards, not necessarily those of the GC or the owner.

      With Bridge, you can connect directly to the general contractor and receive up-to-date information via Bridge automations. You can also import information directly into your project and hub if necessary, while maintaining your own company standards and collaborating with the general contractor.

      Finally, as a designer, you want to ensure that you are maintaining ownership of your valuable intellectual property. And you want to share the latest versions of project files and designs for stakeholder feedback and review. With Bridge, you can select and share specific design versions through design collaboration features. You can use data exchanges to only share specific views within a model. And you can collaborate with other design and engineering firms on only the information they require for coordination.

      Now that we've seen the benefits for the various project stakeholders, I think one thing that we need to highlight with Bridge is the longer term vision, which is to enable a data lifecycle that supports how folks like yourselves want to work on the Autodesk Construction Cloud. Whether you are all working within a single hub or across multiple, building a building is only the beginning. Ensuring data is captured at every step along the building's lifecycle provides efficiencies for owners, general contractors, designers, and subcontractors.

      From the initial design and builds, to upgrades where owner building data is critical for understanding existing conditions, to retrofits where equipment and asset data is critical for efficiencies, Autodesk and the Bridge team are working to support the entire building data lifecycle and empower all participants along that journey.

      With that, I'm excited to hand over to Luis to talk about the journey that SSOE has taken with Bridge. Thanks, Luis.

      LUIS ÁNGEL GARCÍA: Thank you, Matt. Understanding the technical aspects is crucial. And you have done an exceptional job presenting all Bridge details. With a strong grasp of the tools and systems at our disposal, we wouldn't be able to achieve the level of innovation and efficiency that we strive for every day.

      Now I am excited to talk about how SSOE is using Bridge to improve our communication strategies in the new cloud collaboration scenarios. I'm going to tell you why, when, and how SSOE is using Bridge.

      My name is Luis Ángel García. And I am delighted to represent SSOE group at this year at AU. I am an architect from Guanajuato, Mexico, whose passion on technology and innovation had led me to become a VDC technical leader at this amazing company.

      In my four years at SSOE, I have been inspired by the communication culture. And I have had the honor to work with an amazing team of experts from different fields, cultures, and locations. This open and respectful culture isn't just something that we do internally. It is also how we work in every project.

      Our commitment to honor a clear and consistent communication has been the key to SSOE's success over the past 75 years. Many of our relationships have been growing for more than 20 years now. Since 2009, we have documented 2 billion in savings for our clients. This shows how much we value transparency and collaboration, ensure our clients benefit from our expertise and our commitment to their success.

      My own commitment as a VDC technical leader is to collaborate in the continuous improvement of our project-applied technology strategies, strategies that improve our work and help us build strong bridges with our clients and collaborators, bridges that create strong and lasting relationships.

      SSOE is always looking for ways to enhance how we work and collaborate. And our project technology team mission is to keep us at the forefront of the technology that really brings us value. Thanks to our partnership with Autodesk, we are informed with the latest and upcoming releases. And we get to be involved and collaborate in the refinement of their products.

      From our early exposure to Autodesk Bridge, we envisioned significant efficiency gains by securely improving information transfer across ACC project hubs and addressing ownership and security concerns that current workflows do not completely resolve. Bridge really shines for its security. All of the information is very securely transmitted within the ACC project hubs, respecting project hub permissions.

      It's super reliable transferring processes. It never fails. It's been really tested during our pilots. The capacity and speed enables large data sets that are shared almost immediately. And it has those special key features that really make it shine.

      Revit Cloud Sharing. File transferring facilitates Revit cloud linking strategies. You can Bridge and continue to link from the cloud like you do on the regular collaboration ways. The sheets. You don't need to reload sheets into another hub. Bridge will keep them updating. And yes, data exchanges, I'm really excited about that one because that brings granularity to curate information and share only what is needed. Data exchanges are improving security and increasing collaboration and production agility. And we will talk about that.

      These key features can be a big differentiator when it comes to data federation strategies. And that is why we started to think about using Bridge in our workflows. In the recent years, cloud platform collaboration has become the new standard for project development. SSOE was a pioneer in this transition, leading the shift to cloud environments with implementation of ACC.

      We created tools to automate cloud project creation and integrate information from different production data sources to federate our project information in the ACC cloud. During the transition, most of our collaborators were not in the cloud. This really allowed us to lead the strategies and help the transition, positioning our cloud strategies as the main project data environments, and integrating our clients and collaborators by providing them with the necessary means to collaborate seamlessly.

      We established a simple yet effective data federation strategy where we configure access and permissions to ensure privacy while fostering a robust framework for collaboration. The strategy consists in establishing clearly defined ownership spaces inside the project hub, and the final locations for work-in-progress information, and collaboration, as well as locations for official review information, and delivery package assembly for official recording.

      Additionally, we clearly communicate and document and rigorously honor the established strategy, ensuring that the permissions, privacy, and restrictions defined in these plans were consistently respected and upheld. This approach is shaped by our role, as we are most commonly the main design consultant for most of our projects, which allows us to set the plans and establish this effective strategy as our primary and most common method. And this strategy has been proven to be highly efficient and successful. However, this approach is not always applicable.

      As more clients and collaborators adopt ACC, we recognize that some projects are particularly more sensitive about altering privacy and information management and require multicloud collaboration to address these concerns. In these type of scenarios, we immediately identify some challenges. Designing based on growing information, construction without outdated information, siloed information, or ambiguity, these are all latent risks for these scenarios. And if we don't establish a good collaboration strategy, errors can occur.

      The amount of data created during project development is huge. And the communication complexities can be overwhelming. In our industry, high-impact decisions must be made. And we cannot take the risk to make them on unmanaged information flows.

      When multi ACC cloud collaboration is needed, then we need to update our plans. In SSOE, we work with our clients and collaborators to overcome these challenges. Our collaboration means offering our expertise to help build clear strategies that minimize information and management risks.

      Always looking to establish the most secure and efficient workflows that reduce problems to our clients. To create these new frameworks, we need a renewed cloud collaboration strategy. These strategies might seem a little bit intricate or more complex. But they are really not different from managing security and permissions within a single project hub.

      And they can also offer an opportunity to improve collaboration by respecting ownership spaces and reducing the risks for a single company, managing, and centralizing production processes of multiple collaborators within a single hub. But to do this, we need to have a comprehensive plan that all parties collaborating in a project need to agree on.

      Currently, we have identified two main scenarios in which we participate. One, when SSOE owns the central hub and integrates siloed project collaborators into a unified project hub, taking responsibility for all project data, data management, to simplify project outcomes for our clients. By having this structure and starting with a solid plan, we minimize the risk associated with data ambiguity in siloed, unmanaged communication. With collaborators directly integrated in our project hub or working on their own, our strategy ensures that clear definitions for project data allocations are established.

      These locations are the cornerstone to the strategy-- work-in-progress locations for link communication strategies. That meaning once it's published, it will be available for specific collaborators. Package assembly locations for review and preparing official transmitting of information for key milestones. And using sheets as an unofficial project record with versions by key milestones that create a single location for all current project sheets. And even we are starting to use Bridge with our clients with-- to continue record key milestones and delivery packages.

      Without Bridge, this strategy seems inefficient. It will take too much effort and time to distribute large amounts of information across many proprietary hubs. Now Bridge had changed that. It has enabled large data set information flow that allows almost instantaneous propagation. This strategy is not possible. We really mitigate risks by creating a centralized hub when information flow between the proprietary hubs.

      There is another scenario in which-- when we have more mature clients in cloud collaboration, they probably have their own internal management system that also started using ACC. We collaborate by following the established protocols. And Bridge is playing a crucial role in this collaboration, particularly for handling very large amount of data that require frequent, near-instantaneous transfer.

      This has significantly enhanced our capabilities and efficiency in meeting the data exchange demand of our largest clients. We particularly use Bridge for work in projects' information flows. Usually, large mega projects require hundreds of models, hundreds of documents constantly shared to the client central hub that function as the central source for true for collaboration.

      Then all companies are clearly pointed on where to share and pull information from. Bridge is enabling this type of workflows. Before it was really complicated to do.

      Before Bridge, we used a custom development application that uses our computational resources and downloads and upload information on schedule to the required location, losing probably days on crucial updates. Now we use Bridge folders. And we get automated updates triggered only by new file versions. We take advantage of the ACC service that reduces also our internal computational resource consumption.

      Bridge currently is not replacing official-- Bridge is not replacing official transmissions right now. We still manage to use the ACC transmittal tool to track our official delivery key milestone transmission to our client's hub. There might be other scenarios that are emerging with cloud collaboration adoption increasing.

      These are very simplified versions of our detailed strategies. And this might not be the definitive or ultimate solutions. And we are here at the AU to share, discuss, and learn. We will be happy to connect with any of you that are using some other strategies.

      Now let's talk about the specific workflows in the context of these strategies. For files and folders, one-time shares-- use on-demand single-shares when needed. But do not let them duplicate automated bridges. Always avoid file duplication.

      Automated folder transfers, this is your strategy. Plan for minimizing your automated bridges just enough to maintain your project and privacy needs. Sheet automations are powerful if managed properly. Strategy is all that matters. If one of your largest-- in one of our largest projects, we found that the local county responsible for reviewing was overwhelmed by the number of sheets and revisions. Then our project team launched a special ACC project for them to reduce their document management labors.

      We provide them with a full curated and management sheet set just with the information they needed and with the tools for reviewing. The strategy was well received and highly improved the revision process efficiency. Other projects might be divided by scope or compiling into a larger one. Use Bridge strategies for-- and forget about republishing sheets.

      Revit Cloud Shared. Trying to share cloud collaborative files was a real problem. Now you can simply use Bridge, and you will be able to link Bridge collaborative files just like you do in regular collaborative Revit environments. This came along after the release of 2023.1 in Revit. So just make sure you're using that.

      Data exchanges. Bridging data exchanges is a novelty. The advance of data exchanges is going to change how we collaborate in ACC. I'm pretty sure about that. By enabling the granularity to accurate and share data, new and even more mature collaboration strategies will emerge with the evolution of data exchanges. We are working with the Data Exchange team. And I'm happy to work with the Bridge team too. And we are exploring on new ways on how the combination of data exchanges in Bridge will highly improve the way we collaborate in between hubs.

      Now, here are some advices coming out of our implementation experience. Always set the foundation. Identify the right scenarios for Bridge. Create a plan that adjusts your project needs and improves the project communication efficiency. Align the team.

      Communicate the plan clearly to all project stakeholders. Identify and update the project documentation related to the information flow. And ensure everyone understands their role in these new strategies.

      Then just use the Bridge. With the plan ready and the team aligned, create the Bridge. And use the strategy. And rely on the process. You will be, like I am, really satisfied. Once the plan is going, everything just seems to flow. And you don't even notice the success.

      And finally, finish strong. Continue to use a formal delivery method to track project advance and key milestones. We use ACC Transmittals for that. And communicate any updates in the processes. And once project is completed, Bridge can also be valuable in transferring large project data sets and ACC as-builts.

      No matter the scenario, it is essential that all clients and collaborators rely-- clearly understand the communication strategies in place. As George Bernard Shaw said, "The single biggest problem in communication is the illusion that it has taken place." Ensuring that a message has been received and that your project team has agreed on a new strategy is key to a successful implementation.

      As we continue to advance our cloud collaboration practices, it is crucial that we maintain clear and consistent communication across all teams and stakeholders. By doing so, this will keep our business relationship strong and growing, because it is not just about the use of the tools. It is about strategically integrating them into our process to drive efficiency and better outcomes. Those who can rise to these challenges will lead the way, setting new standards for our industry. Thank you.

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