AU Class
AU Class
class - AU

From Prototype to Platform: Delivering New Design Capabilities on Autodesk Forma

Share this class

Description

To meet global demand for affordable and sustainable housing, the architecture, engineering, and construction (AEC) industry must streamline the design-to-construction process. Modular builders—like Factory_OS—are doing just that by productizing their building systems to generate customizable buildings from a catalog of construction-ready unit types. With Factory_OS, Autodesk Research has developed new design methods that connect their building unit catalog with AI-powered generative design to create multiple design options. This case study demonstrates how new procedural design systems enabled rapid, no-code design exploration while balancing trade-offs between cost, carbon, and habitability. The study also showcases how the prototype made it onto Autodesk Forma using the developer extension model to deliver customized novel design functionality and metrics. Going beyond existing capabilities, Autodesk Research and Autodesk Forma enabled Factory_OS to rapidly and intuitively evaluate new development projects in a data-informed manner.

Key Learnings

  • Learn how volumetric building and productized building systems deliver sustainable buildings faster.
  • Learn how catalog-based generative design can be used with volumetric building systems.
  • Learn how low-code/no-code generative methods make design automation more accessible.
  • Learn about how Autodesk Forma extensions enable customizable design experiences.

Speakers

  • Nate Kaylor
    Nate Kaylor is an architect-turned-technology specialist with a passion for cutting-edge design and innovative technology. He holds a bachelor's degree in architecture from the University of Kansas and a master's degree from the Institute for Computational Design in Stuttgart, Germany, an institute distinguished for its A.E.C. research leadership. With a decade experience, Nate specializes in Computational Design and Digital Fabrication, working on various projects with Architectural or Engineering Consultant Teams. His expertise lies in using computational design tools to model and fabricate complex geometries impossible by traditional methods. At Factory OS, Nate leads a team and collaborates with industry partners like Autodesk, combining innovative expertise in Virtual Design and Construction and Digital Fabrication to lower construction costs and timelines.
  • Lorenzo Villaggi
    Lorenzo Villaggi is a Principal Research Scientist within the AEC Industry Futures group, Autodesk Research. His work focuses on novel data-driven design approaches, reusable design intelligence, advanced visualization and sustainability. Recent projects include a net zero carbon and affordable housing development for Factory_OS in California, the NIS engine Factory for Airbus in Hamburg, the Alkmaar Affordable Housing District for Van Wijnen in the Netherlands, the Autodesk Mars Office in Toronto, and the Embodied Computation Lab for Princeton University.
  • Dale Zhao
    Dale Zhao is a Senior Research Engineer at AEC Industry Futures in Autodesk Research. He joined Autodesk in 2014 via the acquisition of The Living, a New York-based architecture firm. With a computer science background, his past and current research topics include generative design, evolutionary algorithms, computational geometry, and 3D interactive experiences.
Video Player is loading.
Current Time 0:00
Duration 31:48
Loaded: 0.52%
Stream Type LIVE
Remaining Time 31:48
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

PRESENTER: Hi, everyone. Welcome to our session From Prototype to Platform, Delivering New Design Capabilities on Autodesk Forma, presented by Lorenzo Villaggi and Dale Zhao from AEC Industry Futures at Autodesk Research. This session is based on a case study from Project Phoenix, a housing development project in collaboration with our customer, Factory_OS.

In the context of Project Phoenix, we will cover how we implement the software prototype for an innovative modular building design technique. To make the prototype accessible through a workflow based on Autodesk technologies that our customers are already using and familiar with, we will talk about how we integrate our prototype for modular building design with Forma, an Autodesk platform. We will also share our learnings from iterating the development of the prototype on a platform with our customer. And finally, we will summarize the takeaways from this case study and how they can be helpful for others who are developing software prototypes and planning to bring them to an Autodesk platform.

First, we'll give an overview of Project Phoenix which provides the background for the subject of the case study in this session. Project Phoenix is a 300-unit housing development that aims to address the housing crisis and demonstrate our net zero future. Project Phoenix is done in partnership with our customer, Factory_OS, a leading volumetric modular housing construction company based in California. Factory_OS combined pioneering technology with tried-and-true manufacturing methods to build multi-family modular buildings more efficiently and at a lower cost.

At Factory_OS, residential units are built as volumetric modules in an offsite construction factory. The volumetric modules are then transported to construction sites using trucks, lifted and stacked using cranes, and assembled into buildings with the utilities connected and a facade installed. With the modular building technologies from Factory_OS, Project Phoenix will be built on this empty lot in West Oakland, across the bay from San Francisco.

This is the current condition of the project site, a barren field where there used to be a steel factory squeezed between a highway and a residential neighborhood. The site has begun construction. Eventually, it will be transformed into a sustainable and habitable residential development that includes 300 affordable housing units. The research and the workflows developed for this project on this site will be generalized and applicable to other locations in the future as well.

To achieve the desired outcome of Project Phoenix, we need a way to navigate the trade-offs between a number of design metrics in different domains. On a total carbon side, we need to consider embodied carbon, operational carbon, landscape sequestration, and facade sequestration. On a habitability side, we need to think from the perspectives of the neighborhood, the site, and the units. Finally, on the cost side, we are balancing construction costs and net operating income.

To tackle the complexity arising from the trade-offs between these many different metrics, we utilize a generative design workflow. A generative design workflow involves three interdependent steps in a loop. Generate, Evaluate, and Evolve.

With generative design, first, we need to create the parametric model consisting of computational logic authored by a designer. It picks a set of inputs, such as geometric parameters, and projects specific settings, and generates a design with corresponding outputs, such as geometries and metadata. But initial inputs can be directly specified by the designer, or provided using some more systematic approach known as design of experiments. The generative design is then evaluated for metrics, which are often calculated by running simulations such as solar analysis and structural analysis, or by computing statistics such as floor area ratio or counting objects.

The next step is to evolve. Guided by metrics evaluated on generative designs and driven by an optimization module, the evolution process starts to explore the design space and learns to navigate in the directions that lead to increasingly high-performance designs. To close the loop, in the high-performing part of the design space identified through evolution, new and further improved designs are generated with iterated inputs.

Next, we will focus on the specific design model developed in Project Phoenix. This image shows one example of the countless designs that can be created using the generative design model in Project Phoenix. There are four main components in the design model, each responsible for part of the design. Midrise massing, townhouses, landscape, and facade.

Here on the left side are some of the inputs taken by the four components in the design model. Some inputs are variables, meaning they can be changed for each design. For instance, the townhouse starting locations and orientation settings can be different in each design, leading to a variety of siting layouts. Other inputs are constants, and they remain the same for the entire run of the generative design workflow. But they can be changed in different rounds. For instance, all the designs from a single run will share the same tree species and use the same unit catalog.

On the right side, the outputs from the design model reflect metrics in total carbon availability and cost, where the trade-offs have to be made through evolution, as discussed in earlier slides. As the loop of generation, evolution, and evolution continues, we will get a large number of design options from the design space with increasingly desired metrics over time. They're considered high-performing, but with trade-offs to be made between certain metrics.

With this many design options, how do we narrow down the designs of interest and identify one or a few to move on to the next stage of design process? For these purposes, we develop an interactive visualization tool for design exploration. Here, each point in the plot represents a design generated. Its various properties are encoded using different channels.

For instance, its x-coordinate encodes the landscape carbon sequestration. The y-coordinate is for unit habitability. The color is for embodied carbon. And the size of the point is for unit virulence.

Zooming and panning are supported to examine design subspace of interest. As before, additional properties, such as metadata from optimization, and a thumbnail of the design corresponding to a point, can be displayed. And the channels can be changed dynamically to visualize and compare other aspects of the designs generated.

This is interactive. This interactive visualization proves to be an effective technique for navigating the design space, as well as the trade-offs discussed earlier. This concludes the overview of Project Phoenix, including our partnership with Factory_OS, the site information, the desired outcome of the housing development, and the generative design workflow we employed in this project.

In this section, we will focus on the research software prototype we developed for modular building design as part of Project Phoenix. Recap. This generative design model in Project Phoenix consists of four main components. The subject of this section is the midrise massing. Midrise massing has a great impact on the designs, and the techniques for creating it are generalizable beyond this project.

Based on the volumetric modular construction technology itself Factory_OS introduced in the previous section, the figure shows an example the midrise massing generated using our software research prototype, which implements tile-based and example-based modeling techniques. On a high level, it takes the units from the unit catalog designed by Factory_OS, and features learned from a set of design samples, to create new designs guided by additional parameters and constraints.

The inputs of this process are shown on the left side. As with other components in the generative design model, the midrise massing design is also evaluated for certain metrics related to the total carbon availability and cost, as shown on the right side. Next, we will describe a few main aspects of this prototype and explain the benefits of the modeling technique with implements.

First, we will look at the unit catalog, which provides the basic building blocks for midrise massing. These are some of the unit types from the prefab unit catalog designed by Factory_OS, including studio units, one bedroom units, and two bedroom units, et cetera. They were originally created as Revit models for efficient use in the tile-based modeling procedure. Our software prototype converted these Revit models into a format with essential metadata and geometries at the proper level of details. The mapping between the converted format and the original Revit models is maintained, so that when a massing design is generated, it can be converted to a Revit model with full details when needed at certain points in the design process.

Next, we will look at the design samples. As the name suggests, design samples are themselves also massing designs created from Factory_OS's unit catalog. They can be from previous projects by Factory_OS, or can be authored by designers to specifically express features desired in new designs. The modeling technique implemented in our research prototype would then analyze the design samples for features such as what is allowed and disallowed for certain types of units to be placed relative to one another, how these placements are affected by the form constraints of the massing, and how often certain placements would happen in new designs.

Now that we have covered the unit catalog and the design samples, we will look at how, with other inputs, they can be used to generate new massing designs. The design sample set needed by the prototype can be as small as a single design. Together with other inputs such as unit weights, which affect the frequencies of different unit types appearing, massing length, and break direction, which determine the overall form of the massing, massing pre-constraints, which can be used to directly specify desired unit, or units, at certain locations, et cetera, one or more designs can be generated, incorporating the features and constraints from the design sample.

The design samples can be changed as needed. Then, based on features extracted from the updated samples, new designs can be generated accordingly. The midrise massing design does not only produce geometries. With metadata from the unit catalog, metrics on total carbon availability, cost, and so on can be evaluated. Furthermore, as shown in this animation, the metrics can be evaluated rapidly whenever a new design is created. This supports the navigation of trade-offs between a variety of metrics such as embodied carbon, cost, Net Operating Income, or NOI, pro forma, unit count, et cetera.

So why did we build this software prototype for massing design? Shifting to a catalog-based, product-driven business model, Factory_OS wants to enable their customers to quickly configure valid building layouts. But the current methods using shared Revit families are prone to user errors that impact constructability.

Also, this often requires tedious rework of Revit models between their design partners and factory engineers. The prototype addresses the challenges by providing an intuitive experience for their customers to engage with their unit catalog, and rapidly creating validated designs that conform to requirements based on previous designs and additional inputs. With the generative design model and the workflow described earlier, they will be able to effectively explore the design space.

Focusing on the prototype alone helped us move fast in the early phase. We could rapidly experiment with ideas and make adjustments. As we made more progress on the prototype itself, we started thinking about leveraging capabilities from Autodesk platforms to support further development of the prototype, as well as bringing the outcome of the research to technologies that are accessible to our customer, Factory_OS. In this section, we will discuss how we transitioned from prototype to platform, and share the results we have by the time of this presentation.

The platform we integrated our prototype with is Autodesk Forma, a cloud-based platform for early-stage planning and design. Autodesk Forma helps planning and design teams deliver projects digitally from day 1 with its conceptual design capabilities, predictive analytics, and automations to make solid foundations for a design project. To learn more about Autodesk Forma, we would like to invite you to visit its homepage using the link on this page.

What makes it possible for us to move our prototype to Autodesk Forma is Forma API, currently in beta phase. Forma API allows the user to introduce their custom design capabilities into Forma in the form of extensions while leveraging the powerful features available from Forma. Currently, there are four ways to extend Forma, with different ways to access in the UI and targeting different functionality.

Embedded views, as the name suggests, allows embedding custom UI and run front end logic in JavaScript or WebAssembly. Generators allow integrating custom logic for creating geometries in a Forma proposal based on parameters provided by the user. Analysis takes the geometry and project data as inputs and returns information to guide the user's decision-making process. Finally, data providers provide contextual data to the project, such as property boundaries or terrain.

The massing design prototype developed for Project Phoenix is integrated into Forma as a generator. We are also experimenting with extension via embedded views. But in this session, we will talk more about the Forma generator.

Forma supports two types of generators, script-based and HTTP-based. Depending on scenarios, one may be more suitable than the other. A script-based generator runs directly in the browser, which means it is subject to the limitation of client-side runtime environments such as features and performance. It is suitable for highly responsible user interactions with instant rendering.

An HTTP-based generator, on the other hand, runs on a server of the developer's choice. Forma communicates with the generator using HTTP requests, hence the name. This means that the runtime environment of the generator can be very flexible.

There is a trade-off on performance, though. An HTTP-based generator is less responsive than a script-based generator due to the communication over network. But since it runs on a server side, it is possible to incorporate complex computation without impacting UI responsiveness.

The cool part of the software prototyping, Project Phoenix is integrated out into Forma as an HTTP-based generator. One reason is that, over time, the prototype has been developed primarily using Python and C#, which are more suitable for server-side deployment. Also, a powerful server environment allows us to add more computationally intensive logic in the future, such as evaluating a complex metric.

Now let's take a look at the Forma extension developed based on the massing design prototype in Project Phoenix. The prototype is wrapped into an HTTP-based Forma generator, which is essentially a server with HTTP endpoints as specified by Forma generator framework. The Revit unit catalog created by Factory_OS is first converted into a format that can be efficiently used by the massing design prototype, then hosted on a storage server. It is worth noting that both the Forma generator and the unit catalog are hosted on infrastructure of the extension developer's choice, as long as the generator can be accessed via HTTP. This can be, AWS, for instance, or even a localhost server for debugging during development.

Forma extension framework receives parameters, inputs from Forma UI and sends the parameters to Forma generator. The generator executes the modeling logic from the prototype internally and returns the model created back to the extension framework, which then asks the model to a Forma proposal so that it becomes part of the design. Now we'd like to share a demo of the current version of the Forma extension running on the actual site in West Oakland.

We select the generator named Factory_OS Tile-Based Modeling, set the display mode to Unit Type, and change the number of rows to 3, then draw a line that guides the footprint of the midrise building directly in the viewport. Firstly, a massing is generated based on the footprint guideline and other inputs. It uses the units from the catalog and design samples which are currently not shown in this version of the generator. The parameters remain connected to the design and can be changed.

Alternative display modes are available. For instance, we can color-code the units by carbon embodied based on data from the unit catalog, or similarly by net operating income switching back to Unit Type display mode. And we now change the random seed used by some stochastic process in the modeling logic to create alternative designs. The footprint guideline is still connected and interactable. So making adjustments will trigger the generation of the updated designs.

The design created by the extension works with multiple types of building analysis in Forma. Scenario analysis works on the massing, even with some floor geometries. And here is the daylight potential analysis on all the buildings on-site.

We are also able to run two modes of window analysis, Comfort mode and Direction mode. And here is the microclimate simulation at different times of year. Finally, the noise analysis based on the traffic data on the roads surrounding the project site. The extension has yet to support area analysis and operating energy simulation, which requires additional metadata on the design created.

Here is a demo of stress testing the Forma generator by creating a massing with a lot of units. Due to the use of geometry instancing, there is little impact on the performance. The Forma generator also supports showing floor plan views at a selected floor. This allows the user to verify the details of the massing and examine them in the context of the construction site.

It is worth noting that we are not developing the research prototype alone. Instead, we are iterating the development along with our customer, Factory_OS. In this section, we will briefly cover how Autodesk Forma as a platform helps us achieve this collaboration effectively.

To get our customer involved in more depth, we can deliver our evolving prototype in the form of Forma extension. With just the extension ID we shared, Factory_OS can easily install the Forma extension, which remains unpublished as a prototype, through whichever updated Forma projects that need this functionality. Factory_OS can then experiment with this Forma extension prototype from their own devices and provide feedback based on their hands-on experience.

We can then discuss the feedback together and respond by adding features, making improvements, fixing issues, and supplement future works. Updates will be pushed to the cloud infrastructure hosting the Forma extension. The new version will be instantly accessible by Factory_OS with no re-installation needed.

Streamlining the customer feedback and development iterations is one of the major benefits from delivering prototype over a platform. Delivering the prototype on Forma as a platform enables the user to perform Revit design iterations with essential information front-loaded in the process, which leads to greater predictability. Specifically, the essential information is extracted from the Revit unit catalog and turned into a format that can be used in early stages of the design process. The quick modeling capability is provided by the Forma extension based on our research prototype.

Another piece in the design build, Revit design analysis, comes from Forma's built-in analysis features. Such a workflow makes it possible for Factory_OS to achieve mass customization as they transition to a catalog-based, product-driven business model. Another area of the feedback from Factory_OS we need to focus on is the generalized usage of the Forma extension prototype in different contexts.

For instance, Factory_OS should be able to update the unit catalog as their business evolves, and the prototype should expect and handle such changes. Also, the modeling technique should be applicable to other sites that Factory_OS will work on in the future, which can be very different from the one in Project Phoenix. On top of this, the Forma extension needs to maintain the ability to quickly test-- for quickly testing out new design iterations in different contexts. By iterating with our customers through the delivery of an evolving prototype on a platform, and learning the changes required, the generalizability of technologies can be considered and supported from early on in the development process.

Finally, we would like to summarize what has been covered in this session into a few takeaways. In section Project Phoenix, we covered all challenges from Project Phoenix in collaboration with Factory_OS, guided the scope of research and the identification of an effective design workflow. In section A Prototype for Modular Building Design, we shared the what, how, and why of our software prototype for midrise massing design. Focusing on the prototype first helps us move fast in tackling core research problems. In section From Prototype to Platform, we demonstrated our Forma extension based on the prototype and how it leverages the capabilities from Forma and makes sure that research is integrated with Autodesk technologies that our customer uses. In section Iterating with Customer, we explained how delivering the prototype on the platform supports our efforts in iterating the research and development with our customer, which leads to better outcomes for both sides.

This concludes our session From Prototype to Platform, Delivering New Design Capabilities on Autodesk Forma. We hope the contents will be helpful for your current or future projects. Please feel free to reach out to us for any questions you may have regarding this session. Thank you for joining.

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