AU Class
AU Class
class - AU

Connected Roundabouts: Roundabouts with Connected Alignments and Corridors

Share this class

Description

In this class, we will explore the use of Connected Alignments, advanced features of Corridors, and modeling workflows to design complex roundabouts as part of peanut-shaped and diverging diamond interchanges. We will use Offset and Widening, and Alignments/Profiles derived from Corridor to automate layout, grading, and 3D design modeling.

Key Learnings

  • Learn how to use Connected Alignments and Profiles
  • Learn how to use Offset Alignments and Widening tools
  • Learn how to organize Assembly sets for the project
  • Learn how to create dynamic Corridor models for roundabouts and interchanges

Speaker

  • Avatar for Rad Lazic
    Rad Lazic
    Rad is a Master of Civil Engineering and an accomplished professional in the fields of Highways, Airports and Railways engineering. Rad has been a Subject Matter Expert in all aspects relating to automation of BIM/VDC and CAD for over 25 years. Rad's goal is to inspire and empower engineers and technical staff towards achieving their ultimate potential through sensible and meaningful skills development, application of technology and design automation. Rad has founded a technical consulting services company, Associated Consultants for Enterprise Solutions. A.C.E.S. are empowering engineering professionals and organizations to succeed with technology implementations for engineering surveys and design, visualizations, safety audits and process automation. Rad's clients consistently succeed in achieving the highest levels of quality and automation through delivering highly customized software implementations, rapid skills development and through building a comfortable and inspiring technological environments that promote creativity, motivate productivity and energize technical teams. Rad is connecting with diverse and large audiences through public speaking at technical and engineering conferences, delivering presentations with high technical impact and professional values.
Video Player is loading.
Current Time 0:00
Duration 40:29
Loaded: 0.41%
Stream Type LIVE
Remaining Time 40:29
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

RAD LAZIC: Hi, everyone, and welcome to my presentation for connected roundabouts. My name is Rad Lazic, and I will be your presenter today. I'm a Civil engineer by trade like most of you, probably, and I worked as a designer and engineer in transportation industry for most of my career, designing highways, interchanges, more recently subways and other transportation facilities. I worked on the LAX airport for the People Mover as well and mostly dealing with software integration, customization, training, and other technical services.

My specialty is putting together disparate technologies, software, exchanging models, 3D, and building information modeling. So today, we're going to talk about connected alignments. This is a feature in Civil 3D that enables us to work better and faster with intersections, and the application is also on interchanges.

Then we're going to utilize some offset alignments and widening tools for fine detail. Then we're going to use the assembly and corridor technology to complete the design. This is a fairly complex interchange in the roundabout model, so we are going to require an assembly set, a little library of assemblies, also known as typical cross sections for highway design.

Then we'll look at the dynamic nature of corridors and put together some fancy 3D models so that you know how to do that yourself. Obviously, the time will not permit for us to go in every detail, but I will show you the overall workflow and some of the detailed processes, and then we'll analyze some of the models that I put together for this class. So let's take a look at what's there.

First of all, the overall workflow provides a lot of opportunities for integration between highway design and structures design, specifically bridges and roadways. And a very popular workflow is that we start within Infraworks that has a model builder where you can select the area of interest and collect any existing data.

That is free service, and you can utilize that online. Simply register with Autodesk with your email and password. From there, we'll collect the existing roads and existing ground and then send from that to Civil 3D to do some design.

Now once we finish with Civil 3D design, we can collect the corridors, which is basically what will be the focus of our work today, and then send those corridors to InfraWorks. InfraWorks is very good with quickly creating a conceptual bridge design and modeling. So for a typical interchange, you might end up with maybe two, three, four or more bridges. So it's very useful to be able to do that quickly in InfraWorks.

Those can then be sent to Revit, and Revit can develop a structural model for fine design to refining the design and doing all the structural modeling and work that is done in Revit where the design can be completed in detail. That finished design in Revit can then be sent back to Civil 3D and/or InfraWorks as the requirement may be. What we will not do today-- we will not work with Revit.

In Revit, this is a separate class, and I encourage everyone to take some Revit classes. I'm sure there will be some that are dealing with bridges. If not, there will be some are dealing with exchanging data with Civil 3D, at least, and InfraWorks.

All right, so take a look at a little more detail. So we will begin first by designing some mainline alignments and profiles. Those mainline alignments are basically the intersecting roadways.

Then I'll build a temporary finish grade surface. This temporary finish grade surface will be used as a reference for a very quick design of the ramp surfaces profiles and curb return profiles. Then we'll do the offset edge of travel way alignments and add profiles because that's part of the automated system. That's the easy part. Then we do a design of widening alignments for simplified exit and entrance ramps, and we do the masking for parts of the mainline and widening alignments.

In a very rough sketch, I'm here giving you the layout of what is the starting point. And to simplify the work, we will just use the taper for the widening where we'll also reach the offset from the mainline and arrive at a location that is about 220, 230 feet away from the actual intersection where we will work on the two roundabout or rotary shape type of alignment.

I also have the taper length, about 1,500 feet, and then about 1,000 feet in the middle to accommodate the grating, side grating, and also the bridge area in the middle. Then we're going to design four connected alignments. Using connected alignments, we'll design four curb returns, or, if you like, on and off ramps that are direct access to the intersecting highways.

The standards that I worked from are just simply described here, and you can see that for the off ramp, the stationing will be following the direction of driving. And then if you look at these distances, the taper itself is about 300 feet to transition from 0 to 12 feet wide lane.

And then we have another 200 and then the 400. That's about 900 feet just to arrive at the point where we will depart the same formation for the road. Then we need plus additional widening or some curves to exit from the main line. So using the standard exit ramp, I will apply that and extend this 25 to 1 taper for a further 500 or 600 feet.

On the entrance ramp, same situation, only the minimum requirements are even more demanding. Have a 600 feet main taper that translates to 70 to 1 to 50 to 1 taper. And then I have another 600 feet taper. I am not designing such horizontal curves. That's construction level detail. So I am just using a simple taper and also extending this for another 300 feet so that we can reach the offset from the main line so that we can do the roundabout design.

Continuing with this, we will design the two rotaries alignment, south and north of sideline, and sample the finish grade surface profiles for rotaries alignments. Then we'll go and design the four connected alignments for curb returns. We will disconnect those so that we'll able to extend and fine tune those curb returns or on and off ramps. We will then design the profiles for the four curb returns.

This is what we will end up with. I call this a peanut style interchange, but it's a diamond interchange with two rotaries. Sometimes, they're completely disconnected, completely two separate roundabouts.

I have chosen to accept this shape where you can see what I referred to as a curb return is actually that off ramp and the opposite side on ramp. The orientation of the interchange is exactly what you see here. So I have designated the west one and west two, east one and east two off ramps so that we can reference them as letters and numbers for this side, west side, and east side and maintained a clockwise direction.

All right, so I'm going to switch over to an application, Civil 3D and jump into just a simple layout just to show you some of the techniques that I've employed to create these models. Other than that, we do have models completed, and we'll utilize those to explain what was done and go into more detail that way. Like I said, I began by creating a full model for-- this is what I refer to as a mainline.

So that's the freeway, and that's what I referred to as a sideline, which is the intersecting road. So for those two, obviously we designed two center line alignments for mainland north and sideline east because the mainland is in the north and the sideline continues to the east. From there, I also have some offset alignments I've created on the sideline and used for corridor modeling for the main line and the sideline as well.

I've used a couple of simple assemblies you can see on the sideline. And also, it's important to say that the surface was generated from the sideline. And I have a sideline finish grade surface.

This is then used to aid in design of the main line alignment over the sideline by virtue of creating that surface model and including that in the profile. To check the clearances, I went in with 23 feet between the surface of the intersecting road and the alignment, which is the top of pavement for the main roadway. So those were the basic layout.

Now working on the main line, I'll show you some of the assemblies for that. So I'm going to go to mainline type A. And you can see that we have the median with the concrete barrier. And I also have the offset, the shoulders at four feet each side.

Then I have a 24 feet for two lanes and then the additional 8 feet for the shoulder. And then it slopes as a side slope. So with that in mind, I'm going to go and create offset alignment.

So that's my first step. So offset alignments, as some of you may know, are created from that selected parent alignment. And I will name them using the parent alignment name, the side and the offset distance, and maybe some additional feature coding such as edge of travel [? lane. ?] Actually, pardon me. This will be edge of shoulder first.

So each one on the left and right, we'll go with four feet first using the offsets and simply let the software complete that step. Then I'm going to go in and do another one-- another two, actually. And those will be for, like I said, from the assemblies, those will be at 28 on each side. Now they will be edge of travel [? lane. ?]

And finally, the edges of shoulder, which I'm going to leave out for now and just move on to a different steps-- like I said, we are going to apply widening to this edge of travel way following some of the basic standards. So I marked here to speed up the process in front of you where we're going to start a taper and end it and do the taper at 50 to 1 and arrive at the location where we can join here the roundabout. In between the two, I will also have some geometry to extend about 220 feet away from the main line.

So this is done by using the widening option, and I will not create a new alignment, rather edit the existing one. Over here, I can start from selecting that intersection where I first sketched out schematically, the station value is the same, and finish over here. Oh, my bad. Let me do that again.

[INAUDIBLE] everything is fine except the direction. So we're going to start from here because this goes from south to north. And I'm going to use that intersection there and finish that widening at the intersection point over here.

Now we're going to change the lengths of each one of the widening. So the total region rate is 3,000 feet, but the transition parameter is at entry. I'm going to have a transition length of 1,500 feet.

And we're going to do a simple taper or linear transition. And I'm going to do the same for the transition out. And that's going to be also 1,500 feet.

The stock station will be at 500 feet, and the end station will be at the 4,000 station. So now this could be a 1,500 and the region, that full transition region, will be at [? 1,000 ?] feet. It's just going to enter those values.

This we would normally repeat on both sides of the alignment. And then we could add some additional geometry. So without spending too much more time on that, this is what you'd end up with the final product. Clearly, like I said in my slide-- let's go take a look at that slide again.

Oh, I didn't size them, I think. Yes, I did. So the inner circle diameter for those two roundabouts will be-- diameter will have [INAUDIBLE] radius of 50.

And the outer is 24 feet more. So it will accommodate two lanes. So that's 148 feet radius. And then for the on and off ramps joining this widening, we're going with 700 feet or 350 feet radius.

So I'm going to go back to that alignments drawing, and let's take a look at quickly what we have there. So in this widening, all that's left is from basically where, if you like, the nose of that exit ramp is, before and after, I've utilized masking. So you could see that I started masking from 0 to 1,400 and then again from about 3,600 to the end of the alignment. So from here, that edge of [? travel ?] way offset is being masked.

All right, so as you can appreciate, this is a fairly complex interchange. I'm just going to show you the number of alignments there. So the centerline alignment, do not even go to existing. There are a few of them over there.

So here from the two centerline alignments, I've also designed a rotary it's actually rotary as one alignment. Let's select it-- rotary north and rotary south. They are two road alignments derived from those circles.

And also, I have offset climate created for each one of them. As I said, offset alignments are easy to create. Here I have these [INAUDIBLE] alignments that I used, I created as connected alignments.

So I simply connected between the edge of travel way on a mainline and the edge of travel way on the sideline. And then again, I utilized the offset of both sides for that alignment. Again, I utilized the masking.

So I'm got a masking for parts of that alignment, or offset alignments can be created with the specific start and end station where you can stop at any time. You don't have to create an offset alignment all the way through. If you look carefully at some of the shaping of the design here because we have a turn in to this off ramp, there's more space left for that.

Where we are on the off ramp, we don't require and don't have that much. So there is no such space left. So this is the difference between the off ramp and the on ramp.

So there are also a bunch of offset assignments for each one of these that you can see. And there's also curb return alignments. There are basically four of them.

E1, which is, like I said, in the lower left corner. That's east one. And the west one is in the lower right corner. And then we are just numbering them clockwise.

In the overall process, we are now where we can create the temporary surface from the roadways. Why do I need that temporary surface? Temporary surface will allow me to read elevations from the design surface on the main road and on the side road.

And then I will use those to find design the profile on my connected ramps. Temporary surface is simply created by utilizing a temporary assembly. That assembly was created to cover for the overall width so that I have very little space left in the middle to bridge across and smooth out that transition between the two.

Of course, that temporary surface can be said to have an invisible style, and you could also turn off the corridors if you don't need to see it. The main purpose is to design the finish grade. So I'm going to go to profiles and show you how did that work for profiles.

I already said how we use the finished grade to design the main line profile. But for each one of these, I utilized that temporary surface, and I also-- on both of the main road and main line and the sideline. And then we just smooth out the-- yeah, I call them curb returns, but they are off ramps and on ramps. But if you look at the overall context, they really look like curb returns.

So curb returns on an at grade intersection you can create by utilizing connect alignments. It's very easy. Might go and show you one of those. So for the connected alignments, you simply select where you want to go from the first alignment. So that would be somewhere here.

And then the second alignment would be somewhere in the edge of travel way on that alignment. And this will be the location. You see how it understands the direction.

And now it's asking me to accept the current location. After that, I will get this control, and I can use the design criteria. I can control the parameters.

For example, in this case, I'm going to go with the radius that's 350. Also, you can design a connected profile. And when I click OK, that connected alignment will be designed in such a way. And of course, I'm just not going from the widened alignment. I'm going from the original [? edge of ?] travel way.

So if this is the off ramp, you can also disconnect. So if I go to Alignment Properties, you can work on connection. And here it is, the update mode. You can go from dynamic to static.

What that will enable you is to change any of the design. For example, you can change the overlap on both sides or at a taper like I did to follow some general design. And basically, this opens up that connected alignment to further design refinement. That's basically what I've done before I went in there and created all the other offset alignments from those and also connected the profile.

So each profile will have its own little intrinsic design challenge and so on. I think I have here-- should be. Profile for these-- it's not. We can create one.

So profile for one of these rotaries, right? So what happened with rotaries, if you look carefully, the rotaries are basically running on the surface, the temporary finish grade surface. I'm going to show you what that profile is. So the temporary finish grade surface that I created from the very simple slope on the pavement and respecting the cross grades as well as the profile on the sideline-- and I'm now using that surface profile to design lanes around that rotary.

There are two of them. And then the rest of it is just a simple offset alignment. Now the offset alignment, again, is just the first pass of that design.

In the next step, when we go and create the corridors, the big decision was-- let me just switch back to my PowerPoint. So when you move from all of your components alignments, connected, offset, widening, curb returns, rotaries, and you start thinking about creating a corridor model, this is a time for big decisions, how complex corridors can be created with multiple baselines. Basically, we have seven controlling-- actually, we have, six, eight controlling baselines, basically, because I have two for the rotary and four for the curb returns or on and off ramps and then two for the intersecting highways.

So the big decision time is what type of corridor, how will I split my corridor. I decided to create a separate corridor for each one of those alignments, first of all, because they have a lot of dependency between each other and also because I really wanted the lighter corridor models to deal with targeting and so on. So also, each one of these corridors will have multiple regions.

And so each region will require the maintenance of the target. So I'll explain all that once we get into the corridor model. So I ended up with mainline that has a start and end region plus the middle section, I call it, ramps to ramps, and the bridge segment in the middle. The sideline has the same.

Instead of bridge, it has the through the rotary section. And then the rotary corridor has a north and the south side. Those are two baselines. So this, just the rotary corridor is a complex corridor, you can call it, because it has multiple baselines.

And then I have four separate curb returns to corridors. So I opted for seven simpler corridors-- larger number but simpler and easier to manage. Of course, when you get into corridor modeling, then you start also working on development and managing your library of assemblies.

Here are all the assemblies used in the model. And you can see that on the mainline, like I said, the region when there's no connection points, that would be-- actually, this is further work done after my presentation class to add the retaining walls. And then you have where there's those shoulders, even this is if you like going through the [INAUDIBLE] area in close proximity with the adjacent on and off ramps. And then the rest of the corridor is just a simple highway with the concrete barrier and the median.

All right, so the sideline has a-- this is real life example. So it has the median where it's basically planters. So there's this room left for the planters. And then through the rotary-- between the two rotaries, actually. You'll see that in the corridor model. This is just almost the same as the main line.

It's important to also have on model such as this null assembly to connect areas where there's no other assembly on any given corridor. Either that, or you're going to break that corridor into separate corridors and have nothing in between or have some other parts of the modeling objects such as maybe creating object. Then through the rotary, you'll see in the model I had some of the detailed requirements where we do want to have the shoulder on the inside and then we don't want to have it past certain spot.

There's that highway bridge as well. It's really simple, stock standard, nothing-- by the way, nothing custom here, no custom subassemblies developed or anything like that. Everything you see in this presentation is stock and comes straight from factory-- I mean, if you download Civil 3D from Autodesk website for 30 days, you can use it for free. It's a trial. And then everything you see here can be delivered or created using that trial software.

So here's at the end, the corridor. And I'm going to switch over to the application. I'm going to go back to the Civil 3D. It's just a slide.

And sometimes it's hard to tell them apart. So this, I'm going to go and create another corridor. And here I'm going to create the RTW2.

So I said RT stands for ramp and curb return, right? [INAUDIBLE]. So this is the W1, west number one. And this will be west number two.

So I'm going to select the alignment now even without knowing exact alignment name. I'm just going to select it from the screen there and use the layout profile right there. That's the one that we designed.

And the starting assembly is going to be from my library. I'm going to go and select it from the drawing. And here they are. I'm going to tell you something about these assemblies in a moment.

So this is ramp, typical east. And the ramp is in the right. I need the one that has the ramp on the left.

So I'm going to start from there. I'm going to select it right there on the assembly. And then the target surface will be existing route.

Then I'll go in there and split this corridor into multiple regions. So everything comes into one region, but I'm going to go and split that into multiple regions. So simply for this alignment, I'm now going to have the first region [INAUDIBLE] here.

Now I don't know exactly. This will give me a clue on the opposite side. But I'm going to say, let's say, summary here matching that we are-- most likely, we have a beginning of a retaining wall.

So that's going to be first. The second one is going to be somewhere really close to where it joins with the-- let's change that to a parent intersection, where it rejoins with the rotary.

And the rest of it will be just controlled with that edge of the rotary. So I'm going to hit Enter. And I'm going to leave that as is.

The fine tuning there would be to target the offset alignment. So let's take a look at how that's done. I'm going to show you something else here as part of this little exercise.

So of course we're going to change the assembly. So I like to go to modify region and control the region properties where I click inside that region. And I'm going to change the assembly where it doesn't have the-- this is LT, no left shoulder, also the target.

So for the targets, I have the lane supervision on the left. And I'm going to assign that to have a couple of targets there. First will be the alignment.

I'm going to select that alignment on the rotary. And I'm going to select this alignment on the side and add those two as targets. And basically, I'm going to do the same thing for the elevation using the profile.

Also going to use the profile on that offset alignment. And that's using that temporary surface. And I'm just going to click that-- so just this one to illustrate what we're going to-- think I have a part of the [INAUDIBLE] alignment missing there.

So what happens is-- I'll show you over here. So this corridor object for that on ramp is divided into three parts. And if I go to Corridor Properties, it's not that hard to match them because I'm using that temporary surface.

And I'm deriving the profile. So whatever it is on the surface, I'm staying on that surface as much as I can. And so I have no left shoulder in the first region.

That's highlighted right there. And then I have a direct ramp. That's a full ramp program with daylight [? planes ?] and catch points there and then no left catch point.

And then I have something that even doesn't have a shoulder. Now this area here will be a separate gore area. So those that will be-- so I'm going to target this edge from the main line so that the main line is going to extend all the way from where the nose is. And then the rest of it is in the gore area.

So basically, repeating that about four times around, and then also a lot of work goes to cleaning up where the gore area is and the nose of those on ramps and off ramps. And then as part of the modeling, Civil 3D allows us to grab all this. For example, I'm going to start from the mainline and then create extra corridor solids from it.

And when I do-- let's do that again. I had to switch off the command prompt for a good reason. And so I'm going to utilize all regions.

This is only three. But the interesting part is I can add this to an existing drawing. And what happens is if I had the rest of the interchange in that existing drawing with all the solids from my corridor models-- and this will just add the current one to the rest.

So it's not hard to build corridors solids model using that method. Here I am in that drawing file, a separate file where I have each one of these corridor regions as a separate solid model. Here you can see later on, I've added that bridge deck. Now what I mentioned at the beginning, the corridors can be transferred over to InfraWorks.

And I think we're not going to have time for that today. They can be transferred to InfraWorks. And then instead of having this solid, it doesn't really know it's a bridge. It's basically thinking it's another assembly.

And then we can replace that part with the bridge model in InfraWorks and then send that bridge model over to Revit for final design and detail. So that's how much time we had. I think I was a little ambitious.

I actually have plans to show you where those two are just a simple and completely automated design for roundabouts, which you can do, and then also the very popular and very modern diverging diamond interchange. But obviously, that will require a couple more hours to do. So with that, I'm going to complete and go back to my PowerPoint. And thank you very much for attending my class and taking the interest in using Civil 3D for designing interchanges.

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