AU Class
AU Class
class - AU

Advancing Sustainable Architecture: Lake|Flato's Journey with Autodesk Forma

이 강의 공유하기

설명

Join Miguel Elizardo, Daniel Stine, and Autodesk Forma Representative Andrés D'Silva for an engaging case study and industry talk on sustainable architectural design. This session will spotlight Lake|Flato Architects' application of Autodesk Forma in competing for commissions and achieving WELL Pilot Credits and WELL Platinum Certification on its own office remodel. With a focus on outdoor thermal comfort and wind pattern analysis, participants will explore how data-driven insights from Autodesk Forma help inform Lake|Flato's approach to sustainable design, leading to successful project outcomes and enhanced client presentations

주요 학습

  • Discover the strategic use of Autodesk Forma in a WELL Platinum-certified project and its role in achieving sustainability goals.
  • Learn about using custom templates for client engagement and project validation, building trust and transparency on performance.
  • Discover how Autodesk Forma alternative proposals showcase the design's environmental comfort and acoustic benefits.

발표자

  • Daniel Stine 님의 아바타
    Daniel Stine
    Daniel John Stine AIA, IES, CSI, CDT, Well AP, is a registered architect [WI] with over twenty years of experience in the field of architecture. He is the Director of Design Technology and leads the internal research program at top-ranked Lake Flato Architects in San Antonio, Texas, USA. Dan has been appointed to a three-year term on the national AIA Committe on the Environment (COTE) leadership group. Dan has presented internationally on BIM in the USA, Canada, Ireland, Denmark, Slovenia, Australia, Scotland, and Singapore at Autodesk University, RTC/BILT, Midwest University, AUGI CAD Camp, NVIDIA GPU Technology Conference, Lightfair, and AIA-MN Convention. By invitation, he spent a week at Autodesk’s largest R&D facility in Shanghai, China to beta test and brainstorm new Revit features in 2016. Dan teaches graduate architecture students at North Dakota State University (NDSU) Dan is a member of the American Institute of Architects (AIA), Construction Specifications Institute (CSI), Member and Chair of the National IES BIM Standards Committee, and Autodesk Developer Network (ADN), Autodesk Executive Council - AEC, and is a Construction Document Technician (issued by CSI). He has presented live webinars for ElumTools, ArchVision, Revizto and NVIDIA. Dan writes about design on his blog, BIM Chapters, and in his textbooks published by SDC Publications.
  • Andrés D'Silva
    Andrés joined Autodesk through the Spacemaker acquisition. A mechanical engineer by training. He has worked with adoption of Forma in a wide range of clients from real estate developers, large architect firms and small practices. Now he is focused on scaling and enabling Forma's customer success in North America
  • Miguel Elizardo 님의 아바타
    Miguel Elizardo
    Miguel is the Design Performance Technologist in Lake Flato's Design Performance team, where he promotes technology and sustainable best practices. With a strong passion for sustainability and high-performance building design, Miguel believes that implementing best practices in these areas can significantly benefit the environment. He actively tests new strategies for building performance and analysis, focusing on design performance simulations for daylight, energy, and views, as well as in-house training and sustainability adaptation. Miguel earned a Bachelor of Science in Architecture from the University of Texas at San Antonio. He has a diverse professional background, with nine years of experience in Retail, Commercial, K-12, and Higher Education projects.
Video Player is loading.
Current Time 0:00
Duration 1:01:54
Loaded: 0.27%
Stream Type LIVE
Remaining Time 1:01:54
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

DANIEL STINE: Hey, everyone, thanks for coming to our Autodesk University 2024 presentation, Advancing Sustainable Architecture, Lake|Flato's Journey with Autodesk Forma. I'm going to do a quick introduction of myself, and then each of us will introduce ourselves. And then we'll get right into it.

Since we do have an Autodesker on the presentation, there's this brief safe harbor statement you should read and understand before making any purchasing decisions. Here's our agenda for today. I'm going to do an introduction of the firm. We'll do introductions of ourselves. Miguel has a couple of case studies to share. Andres has some Autodesk Forma development roadmap information that's really cool and exciting to know about.

So we'll jump right into it. I'm Dan Stine. I'm the director of design technology, and I lead the research program at Lake|Flato. I also teach graduate architecture students at NDSU. I have another class on using Autodesk Forma in academia, shameless plug. I'm on the Autodesk national-- I'm on the AIA National Committee on the Environment Leadership Group, and I've also written 19 textbooks. One of them is the number one book on Autodesk Revit in the academic market in North America. Miguel?

MIGUEL ELIZARDO: Thanks, Dan. Yeah, I'm the design technologist here at Lake|Flato in San Antonio, Texas. I have about eight to nine years of experience. I lose track sometimes. [LAUGHS] That's how long I've been already in the industry. I've been doing projects in residential, K through 12, higher ed and doing a lot of commercial retail work previously. But now I'm a design technologist, which is pretty cool, to be part of the design performance here at Lake|Flato.

And I've been here for about two years now. And I look forward to showing everybody what we have to show today. Andres?

ANDRES D'SILVA: Thank you. So my name is Andres D'Silva. I'm a part of the Forma team and joined in Autodesk through the acquisition of Spacemaker, the previous startup that sprouted this product. I'm a mechanical engineer by trade and been doing what is called, yeah, "adoption" with the new software in North America. And had the pleasure to get to meet Dan through this last year and very much looking forward to explain how they've been instrumental in creating such a good software.

DANIEL STINE: All right. Before Miguel gets into the meat of the information, I want to share a quick overview of Lake|Flato Architects, in case you're not familiar with us. We're based in San Antonio, Texas. We also have an office in Austin.

The firm has won the AIA National Firm of the Year Award in 2004. That was at our 20th anniversary. This year, at our 40th anniversary, our two founding partners won the AIA Gold Medal award, which is the highest award an architect can win in the United States. In 2019, Architect Magazine ranked us the number one architecture firm in the US in their architect top 50 list.

We've won the most COTE Top Ten-- COTE stands for Committee on the Environment-- Award, which is, arguably, the highest sustainable and design award a firm can win. And then we've been a member of the AIA 2030 Commitment since its inception.

We have five studios-- residential, learning, which is K through 12, higher education, eco-conservation and urban development. Our work is national. So about half of our work is regional, and the other half is national. We have projects all across the US and on three islands, two in the Pacific and one in the Atlantic, and a couple of projects at Cornell University and UPenn.

Here are a few examples of the 16 COTE Top Ten Awards that we've won. I always like to point out the one in the lower left, which is a really unique project type, a grocery store. In the lower right area is the World Birding Center, which was designed for deconstruction and also to have what was called "low-embodied energy" at the time. This is something like 15, 16 years ago. And now we call it "low-embodied carbon."

Basically, to give you an overview of our design performance strategy, it's our overarching framework of what Miguel is going to show in a little bit, is we have this design performance action plan or sustainability action plan which is broken up into practice, people and planet. We have our design performance team, which includes myself and Miguel, led by our director of design performance, Heather Holdridge, and design performance manager Kate Sector and then design performance intern Desiree Allen.

And then, another people shot-- the people are the most important ingredient in all of this-- is the studio champions. Each studio has a group of people who are really motivated and interested in sustainability. And they actually are pivotal in helping us keep our project goals on track and, also, the people through which we disseminate information. It actually goes in both directions. When they learn new things, they share it with the design performance team. And the design performance team, likewise, covers new things, like using a tool like Autodesk Forma.

Just a quick overview of how a typical project goes through the pipeline is, early in the project, the design performance team will do a microclimate analysis. And that includes some of the Forma tools. We used to use some other tools and still do use some Grasshopper and just some basic things that we like to understand about the site before we start taking the program and trying to come up with a design solution.

I have another slide for the integrated design workshop, which is across the bottom. But throughout the project, early and while the project is still able to be modified, we're analyzing the project and using tools and workflows, with the design team, to come up with the optimal design for the project.

So one thing we try to do on every project is have, ideally, a daylong workshop. It's not necessarily just about sustainability. It's about the project, in general, but goal-setting as a group, with all the key stakeholders involved, the client, the people who'll be doing the maintenance on the building, the mechanical, structural, the civil ecologist.

Whoever is on the project team, we try to have them all at this meeting. So as a group, we can decide what the goals and strategies are for the project and then come up with a report that we continue to compare to the project as it's moving forward, to hold ourselves accountable for the decisions that we made to come up with the optimal project. And so, with that quick introduction out of the way, to get on to the exciting stuff, I'm going to hand it over to Miguel.

MIGUEL ELIZARDO: Thank you, Dan. Now we're going to move on to the case studies that we talked in our agenda. First case study we're going to go over is 311 Third Street, which is our office here in San Antonio, Texas. We are located downtown, about maybe a mile, if not a block away or two from The Alamo, which is really neat. So we are in an urban, dense environment.

But a little bit of our office is we decided to renovate the office because, during the pandemic, we felt like we grew so much. We were an 80-person firm. We expanded to about 150 now. And then we were looking for spaces to actually move into. But then, at the same time, we were like, let's practice what we would preach and renovate our office and instill some of the things that we talk to our clients about.

So we decided to pursue some certifications, and one of them was the WELL certification, which we just recently got WELL Platinum certified for our office, which is a really great deal. As we all know, the WELL certification, in itself, is a rigorous process which we have to do a lot of performance testings ourselves and then, at the same time, get a third-party certifier to come onboard board and actually test and prove all of these items that we've mentioned and spoke about.

But that was one of the main things that we decided to do for our office. We decided to do our hoteling system, expanded the desk. We had a lot of large desks in our office which we didn't want to-- it wasn't working for us anymore. So with that renovation, we actually had a car garage right next door to us, what you see on the right-hand side. But that car garage--

Let's see am I able to go forward. So there you go. That car garage in the top Left hand corner housed a lot of the cars that we would come in. But at the same time, we decided that we needed to redo something with that space, just because we like to talk about connecting with nature, at the same time, having a space that we could spill out to. And what we ended up doing with that car garage was demolishing it and reusing a lot of the material, actually, within that space.

A lot of the wood members that you see on the images were actually repurposed and reused for the wood slats that you see throughout our office, which is a really cool thing and unique thing to see. We repurposed them and used it and installed it.

But at the same time, this courtyard experience really allowed us to host events and be something that we could go outside and have, in a sense, a third place to really relax and work at the same time. We host our produce markets. We posted artist events and stuff like that in that courtyard and even had our office Christmas party there, which is amazing. Because we have these spaces that are transitional, that transition into work to outdoor landscape areas, which we talk about a lot.

And then, as you see in these diagrams, I really just want to give you an overall overview of how our layout is. So we do have two buildings adjacent to us, next door to us. And then we have a little bit of a parking lot on the bottom. But, really, the main entries, it used to be, previously, that our entry points used to be right at the building. But now, because our car garage single-story went away, we have this beautiful courtyard that we created. That now is the main entry point for every guest and also us, where we come in through.

We get to experience the courtyard, in itself, for its natural beauty and landscapes, which we have a lot of Mexican Sycamore trees and a lot of bench seating. But at the same time, this is an area that we just come into first, before we actually go into the office, which is really cool.

And as I mentioned, WELL certification was something that we really wanted to pursue. We are also pursuing a net-zero zero carbon certification, both embodied and operational carbon. But with the WELL certification, as I mentioned, we scored a really high score. We surpassed our benchmarking. But at the same time, it is a rigorous process, as I mentioned.

But what we're going to be focusing on for this presentation is some of the pilot credits that we decided to pursue and some of the tools that we ended up using concurrently with Forma, which is really cool. Because Forma really uplifted all of the other items that we had and compared the two, which is really cool, too. And at the same time, it streamlined the process, which is awesome.

But we're going to talk about thermal comfort, which is the two pilot credits that we pursued, that we wanted to tackle. And the thermal comfort really relates to our courtyard, to see how it's performing. Since we've been exploring a lot of the spaces outdoors, we wanted to understand how these spaces really performed outdoors. And, especially in San Antonio, Texas, we have really hot weather. Especially in July, August, September, it's really hot, usually. We get to about 110 degrees sometimes. If you add humidity to that, it gets even worse.

Diving into our WELL pilot credits that we decided to pursue, on of them-- there's two subcategories for these, when we're pursuing thermal comfort for outdoor thermal, is T09.1, which is managing outdoor heat, which is one point. The two options that we were allowed to do, one is outdoor shading, and the other one is temperature modeling.

With these two options, we decided to go with option two, just because we wanted to see what the thermal perception was for each month and, at the same time, get the highest index within those months and then show the countermeasurements we were doing for those two months. So for example, you'll see a lot of the things that we ended up doing is adding a outdoor pavilion, adding a lot of open seating, ceiling fans and adding some trees that provide a lot of natural shading and, at the same time, provide cross-ventilation.

We do have walls that surround our courtyard, which block some of the northern winds, but at the same time, allowed us to cross-ventilate the space, which is really awesome. And you'll see that soon.

And then the other part of this was avoiding excessive wind. How do we model that? As we all know, modeling computational fluid design is not something that's really easy. Something I tasked myself and also, at the same time, took on, in a sense of-- more like a thing that I wanted to challenge myself. That's the word I was looking for. It was a challenging thing for me. But at the same time, I love a challenge.

And what I wanted to do was use these tools and then, at the same time, see how we could improve our space and, at the same time, if it's even working the way we intended, which is awesome. But Forma really stepped up the game with the introduction of computational fluid design. It really allowed us to really see how wind patterns were flowing through the space, as opposed to the other softwares that we ended up using, which we'll dive into next.

So some of the tools that we ended up using early on and that was available was Grasshopper with Ladybug. And then, at the time, as Andres mentioned, Spacemaker was out and then got formed into Autodesk Forma, which was still in development, in beta credit. We ended up using these two tools hand in hand, both, together, just to see how they would compare. And the results were almost identical. I was pleased to see that.

Because the whole process, as we all know-- and if you guys have used Grasshopper and Ladybug, the process can be tedious. And you have to develop a script. You have to do a lot of research and then implement the script. And it could be daunting for a lot of designers and technologists out there who are developing these things, that are maybe not aware or familiar with these tools, which is where Autodesk Forma really bridges that gap.

It provides a simple user interface. It allows us to expedite the process. And all of us, across the firm, here at Lake|Flato, we've ended up using Autodesk Forma for that. And it's really cool to see that our designers are using these tools, now, so easily, versus going to a single-point person and relying, for some of these analysis, as previously it was. And, I mean, a lot of firms are also doing that, right? We have a single-point person that we go to, to be doing these analysis. But Autodesk Forma has really bridged that gap, which is awesome to see.

So as I mentioned, this will show-- as you look in the bottom right-hand corner of the screen, when we're talking about tools that we're using, this is one of the tools we ended up using, initially, for the T09.1 option two, outdoor comfort. I had to develop a script. And the way that this script is broken up is into three parts. And what we do is we ended up getting a weather file. And the weather file is a historical data component that we get from EnergyPlus or Ladybug weather files. And we get it for each project location.

And as Dan mentioned earlier, we do this a lot, for a lot of the projects. And you'll see that we actually developed another in-house script that allows us to get a lot of the information early on. So that way, our designers understand some of the passive strategies and even rain, annual rainfall information for that project site. But for this component that I had to develop in-house, is a portion that we needed for our technical documentation that we needed to submit.

So the first part of this script really talks about these climate graphs that we needed to develop and show to them what the highest index of temperature would be here in San Antonio, Texas. So we see that, in these arrows that are pointing, April through September are showing high index of more than 80, 90 degrees Fahrenheit. And according to the technical documentation that we had submitted, there is an extreme temperature. We needed to show countermeasures and also, at the same time, show those temperatures that were being generated.

So in the next portion of this script-- I think maybe I should highlight that they also wanted to see what the thermal stress, what the thermal condition and thermal comfort was for this courtyard. So we needed to model that, which is what leads us to the next portion of our presentation, where we actually ended up modeling our courtyard and which is the meat of the script that does temperature modeling for the actual site.

So the diagram on the right, that you see, shows us a very strong index of stress for thermal comfort outside. And it's a comparison that shows the site courtyard with nothing on there and then the courtyard, in itself, with the trees and the pavilion. And as you can see, the temperature within July is very hot. It goes up to 100.

And then, with the countermeasures that we incorporated, vegetation and the wood canopy, it dropped it down to about 90 degrees, which would be almost a 10-degree difference, which is awesome to see, just because that's what we intended. We wanted to be outdoors, to be able to enjoy the space and the hot summer, incorporate some water features and stuff like that, air circulation, ceiling fans that would really cool the area and allow us to be outdoors, even in July. [LAUGHS]

And then the last portion of the script is something that I started developing, that goes into Butterfly. But the next, I guess, portion of this presentation really highlights both of them. Eddy3D and Butterfly shared very similar results. And for redundancy, to reduce redundancy. I didn't show examples of Butterfly and Eddy together, just because they both shared similar results.

So the next items that I'm going to show you on the computational fluid design is really from one software. Because it comes-- it shows similar results from both. And then we're going to go on to showing how everything within Forma really steps up the game from that, moving forward.

But this took a while for me to develop, which was really cool to see when we were looking for the certification and looking for the technical documentation. And this really did provide a lot of the foundation, but, ultimately, we ended up also submitting some of the technical documentation with the Forma tools that we used.

So temperature modeling, as I mentioned, with the courtyard, we ended up using Forma. Actually, this slide was not supposed to come up first. For some reason, it did. But we see, in Forma, that temperature modeling shows us, in our courtyard, at 103 degrees, versus 104 degrees on the left-hand side, with no courtyard on there, with no pavilion, no strategies, interventions or anything like that, in the month of July.

And then, with the courtyard on the right-hand side, it shows us that, on the bottom of the actual pavilion, it's 93 degrees. And in the parking lot, its shows us at 103 degrees Fahrenheit. So that's a 10 Fahrenheit difference, which is substantial for the month of July, being in our courtyard. And then if we move into September, we see that Forma shows us, without a courtyard, at 97. And then, but, with our pavilion and trees, it shows us at 87 degrees, the difference, which is really cool to see.

And one way to do this, within Forma, is do the microclimate analysis, select the month and then, at the same time, do an inspect tool within Forma. And then you're able to select the surface. And it'll give you the temperature reading for that, what is perceived for that month.

And then, lastly, the month of October, which is now we see that temperatures are being expected to be around 90 degrees outside, with no interventions. And then it shows it to be 79 degrees cool in our courtyard, which is ideal, something we love seeing and being around. That's almost the ideal temperature to be at.

DANIEL STINE: And we have a high of 94 today, so it's right on--

MIGUEL ELIZARDO: [LAUGHS] Exactly. Dan, actually, I don't know why some of these slides did not show up, or the other ones that I initially was supposed to talk about.

DANIEL STINE: Well, just keep moving forward.

MIGUEL ELIZARDO: OK. OK.

DANIEL STINE: This will be the exclusive content for the live presentation.

MIGUEL ELIZARDO: [LAUGHS] Got it. OK. Now we're going to move on to the T09.2, which is avoiding excessive wind in our courtyard. And again, we're talking about the tools we ended up using and how-- early on, I mentioned that these tools really shaped and helped inform our design. But at the same time, some of these tools can take a long time to process.

And one thing I should note, that Autodesk Forma is a standalone tool. It's a cloud-based tool that allows us to see the information on the cloud. And you're able to do multiple analysis at the same time. And it'll let you know when it's done, which is something that's really awesome to do.

With the tools that I mention here, that you see, Butterfly and Eddy, it took a long time to do-- sometimes it would take about an hour or two to just do a single point of analysis, which is something that can be very frustrating for a lot of folks, if you've ever been in that position. I know that sometimes I've run a couple of simulations and I'm like, this is not the results that I was looking to see.

But it's also great to see that we're able to manipulate some of that data and be able to-- we have control of that, which, I know Autodesk Forma is moving towards that, which is really cool to see. But as I mentioned, highly intensive, not as friendly, user friendly. It could be daunting for a lot of people. But that's where Autodesk Forma bridges that gap.

Now, as Dan mentioned, we like to analyze and see and do climate weather information. So the left-hand side, it's a portion of our Grasshopper script that we have in-house, that's been developed. And we like to provide this to all of our designers to provide information, as far as the wind roses throughout the season, and see where the strong winds are coming from.

And we also like to provide these diagrams that you see, on the site. That allows us to display and show a client where some of our winter winds are coming from. That way, we can start to strategize and think about countermeasures to block some of those northern winds, but at the same time, open up to our summer winds.

And as you can see, there's a lot of density, right? There's a lot of high-rise buildings surrounding our site, which creates a challenge within our site, right? We want to try to open up to the summer winds. But maybe some of those winds are being Venturi effect throughout the site, but maybe not coming through our site. But we'll see some of those diagrams and how they look like.

And, first off, we're going to look at the tools we use, which is Grasshopper, Ladybug and Butterfly and Eddy. And like I mentioned, everything with Eddy and Butterfly are almost identical, which is why I'm showing just one diagram. So moving into the actual analysis itself, if you see the legend at the top left-hand corner, we see that the rectangle highlights that we want to be between 0 and 12 miles per hour, per the technical documentation.

We do not want to exceed wind speeds in our courtyard. If we do, what are some of the things that we're doing to mitigate that? And based off the initial analysis, we needed to show what the average wind speeds would be and then show some of them-- on the right side, you see that the document shows excessive winds. So we ended up modeling excessive winds.

Even though the high winds for San Antonio, Texas are being displayed at eight miles per hour, the average wind speeds within are being-- are shown at six miles per hour during the summer. And we see that the model on the right-hand side, at 19 miles per hour, that's just us tweaking the script to show that we have excessive winds and what does that look like in our courtyard.

So right now, in our courtyard, it's looking like seven miles per hour, which is not that bad, right? Based off NOAA, we see that would land between a gentle breeze. Anything above that would be considered a moderate breeze, something-- you don't want to be out there, sitting down, just because it's too windy to be able to do anything. And then we see, on the average wind speeds, that it is just one mile per hour in our courtyard, within our site building.

And then the other one that we needed to show was southern winds. So as I mentioned, we like to see where our wind patterns are coming mostly from. So we have southeast south winds, and then we ended up modeling northern winds. So again, our courtyard is sitting at one mile per hour. Everything else outside of that, average wind speeds are about six miles per hour, as you can see how the streets are being modeled. And then on the excessive winds scenario on the right-hand side, we see that our courtyard is sitting at five miles per hour, with southern winds coming through the site.

And one thing to notice, I think you guys should take a look at and pay attention to how the excessive winds are showing up. Because a lot of these diagrams that I'm displaying, some of it are going to look similar to Autodesk Forma, which is really cool to see. Because they're both speaking almost-- they're speaking the same language, as far as analysis goes.

Now, showing an example of northern winds coming through our site, we see that northern winds are really a big challenge for our site. Even though we have buildings surrounding us, those are the most challenging ones, for sure. But we do have, like I mentioned, a semi-open courtyard with walls blocking. But we do have some excessive winds still coming through our site at 12 miles per hour, which is not that bad, but still falls within that gradient where we want to be, right, in our courtyard.

Now we're going to move on to Autodesk Forma's analysis, which is the exciting part. I really like to see this, just because the streamlines, at the same time, you have this option to be able to take the streamlines off and just be able to see the analysis on the bottom, which will be like a gradient. And you can inspect what the wind speeds look like in there. I really enjoyed seeing this.

And you're able to do multiple analysis, pretty much, in any direction. Once you click the analysis, singlehandedly, you're able to see the multi-direction of the winds coming in, which is something that's really awesome to see. And it doesn't take that long to be able to run an analysis. And you're able to even adjust the diameter of the analysis, which, in a sense, allowed us to incorporate more buildings to be able to see how our site is actually really performing.

With the other tool, we were limited to a site location, right? How many buildings can we incorporate before we start to-- the computations started to take forever. With Autodesk Forma, it has no limitations to this. It also even gives you a rough estimate of how long it's going to take to be able to compute this, which is really cool to see.

But we see that our average wind speeds in our site are right there, within the southeast, sitting below two miles per hour. And then, in our courtyard, for excessive winds, as I mentioned, paying attention to the colors of the arrows, we see these streamlines for excessive winds almost being site-and-site identical.

And then we're going to show the technical documentation portion of this because I'm not going to go one by one, to explain everything. But, really, this is the technical documentation that we ended up submitting, that showed northern winds coming in, northern east winds and then southern east winds at the average speed and then showing the excessive winds, which is really cool to see. Because our northern winds really did show that the excessive winds were coming around. But we do see that, on our site, there's a little bit of excessive winds, which is not that bad.

But even though the streamlines do go over our site, those are going over our site. They're not actually going through our site. If you look at the actual diagram with the color grading on the bottom, you see that some of the areas are below that threshold that we need to view, which is good to see.

And then the other portion of this really cool thing that we can do with Autodesk Forma is wind comfort. So this diagram really shows you how a person would be perceived, at the ground level, with wind speeds coming through the site. So without the courtyard in the space, we see that it is only standing. With the courtyard, it changes to sitting, which is really good, to see that it's designed and intended as we pictured it.

And this is what really created and sparked the idea of our courtyard. And this is just an example of an image that shows us how our courtyard is really laid out. We have ceiling fans. But again, I think one thing I failed to mention, which was the analysis doesn't take into account the ceiling fans that are in the space, the increased humidity that you can start to add within the water features, which data suggests, with research, that that could help increase the comfort within the space by 10 degrees.

So if you saw previously that we had seen that it was 80 degrees, that could go down to at least 70, with the introduction of more humidity, water features. And, of course, since we have our ceiling fans, that also adds a substantial amount. That decreases the temperature on the bottom of that space.

Now we're going to move on to our case study number two, which is 400-500 South Congress. This project is a unique project, in itself, just because we were approached by a client with a design. We then were told, hey, by the way, what do you think? Can you help us?

Actually, this was part of our urban design-- development studio project. And, ultimately, they ended up running most of the analysis. I ended up helping run some of the other analysis, but they ended up also putting a lot of the information on the documents and then submitting it. And then this case study that I'm about to show is really a cool case study, just because we ended up winning the project because of Autodesk Forma and all the tools that we ended up using.

So as I mentioned, with every project, we do a site analysis. We talk about where the winds are coming from, talking about site location and talking about strategies, where we need to start to block some of the winter winds and where we want to open up to our summer winds.

But at the same time, the other portion is understanding what the annual rainfall for water catchment, reuse-- and then also understanding what the humidity, air temperature, heating/cooling degree days is and, at the same time, understanding the psychrometric chart. Because we want to make sure that we're introducing the right passive strategies for our site.

So this is a proprietary Grasshopper script that we developed in-house, that grabs all the weather file data. And then we show this to-- we give this, early on, to our designers. So that way, they have all this information. And we're able to show this to the client, at the same time, to understand what we're trying to convey to them.

So this was the design option one that was given to us. And when we initially saw-- we saw a lot of opportunity. We noticed the placement of the buildings. You'll see that, in our design, the placement of some of the buildings are different. And some of the buildings almost stayed the same, but not really, because we introduced a lot of these areas where it's terraces and things like that.

But with this design, we saw that, one, we already knew what was going on, right? We've done so much work already, previously, that when we see something, we're like, yes, this is what's going to happen. We need to do this. We need to make these moves.

So what the urban team decided to do is propose a design. And the opportunities within this project was that it was enclosed. As you can see in the bottom building, that the one that says "130 FT," that building itself is already blocking a lot of those southern winds coming into the site. But that staggered 290-foot high-rise is actually opening up a lot of, through the summer-- through the winter winds.

As you can see on the diagram on the right, the northern winds are just flowing through the site. The Venturi effect is going just through there. So that was one of the biggest opportunities for this project, that it really had, that we were like, we need to come up with another solution. I think this would be very helpful for this project.

So the prevailing winds showing on this diagram really shows you what the southern one looks like and then the northern one, as I just displayed, but in 3D form, which is something that you can do in Forma, which is really awesome. You're able to spin around the model. You're able to even adjust the wind heights from the ground level all the way to the top. And you'll see the changes in patterns as the wind really-- the streamlines of the winds really flows through the buildings, which is something that really gets me excited to be able to see. I'm a huge fan of this type of analysis, to be able to see.

But as I mentioned, southern winds are being blocked. They're not really coming in through the site. So you can think that everything in that center spine of the design is going to get really hot during the summer. Not a good space to-- yeah, a lot of shading. So that was just what we initially saw and then-- along with all the other tools that we ended up using to analyze within Autodesk Forma.

So then we introduced a couple of design options, but, ultimately, we ended up landing with this design option. So as you can see, we incorporated a lot of green scapes in the project. But at the same time, one thing I failed to mention previously is that they didn't connect to the creek that was there previously. And that was an opportunity that we saw. We're like, no, we need to find a way for this community to be able to connect to the creek that's coming through there.

And so what we ended up doing is, one, of course, opening up to the southern winds in the summer, to be able to cross-ventilate through this space, and then repositioning some of these buildings and then adding some of these features-- terraces, open courtyards-- that allowed everybody to be able to see and be able to enjoy the outdoors.

So as you can see in the design itself, we have some-- in these sketches, too, is a lot of green vegetation, with open terraces and stuff like that. And it really created this community within the space that everybody could come and just enjoy and visit, work, live, in a sense.

So we're going to get into the analysis portion. So what we ended up doing is doing multiple analysis on this design, just to see how it would perform. And one of the things that you can do with Autodesk Forma is the sun hours. The sun hours analysis is a really good analysis, just because it gives you how much of a surface is actually being received by the sun. That, in turn, tells you whether you should apply photovoltaic panels in that location or not.

Or you could also get an idea of how dark your areas are going to be in the spaces below, which is something you want to try and avoid, right? You want to try to get a lot of that natural sunlight into those spaces, but not too many, right? Because, especially for this project, being in Texas, it's very hot. So trying to limit some of that, but at the same time, be conscious about it. We can do this analysis for multiple months. But we decided to show this for the four seasons, within the months June, March, September and October-- and December. Sorry.

And then we go into the other portion of this one, which is another really cool tool that we've used with Forma a lot, which is a noise analysis. This tool allows us to be able to see how our site is performing with the noise traffic surrounding the site. So all the streets have noise data within Forma. And we're able to run the analysis and be able to see how it's affecting and what countermeasures can we start to introduce.

So we had an idea of the spine of the design, that we wanted to make sure that we sat at a safe noise, low decibel. Because we wanted to have a space where everybody can come in and enjoy and sit down and have a lot of shopping experience, in a sense, there. So when we modeled this and we saw the results, we were pleased to see that a lot of the spaces in between really showed soft noises, as opposed to everything around these two busy streets at an intersection being blocked off, buffered from other buildings and stuff like that.

One other thing that I'm going to mention, that I think was really cool, that our team discovered-- and like I mentioned, some of this information is already in Autodesk Forma. But another resource that was really helpful for us to use and explore was the external data that you can get from the Department of Transportation. And the Department of Transportation actually also gets the information from ArcGIS. So if you can't find it on the Department of Transportation for each state, you can also get it from ArcGIS. Because they both go hand in hand and show, sometimes, similar results.

But the Department of Transportation may have their own information, proprietary software that they're using. They may not be using ArcGIS for that information. But what you can get from there is the average daily traffic, which is really cool because you need to know, I mean, throughout-- it has historical data. So you want to get the latest data. And sometimes you may not have that. And this is where you can go to actually assess and get this data.

So this little diagram on the right-hand side, you can see that it shows a traffic count map throughout San Antonio. And as soon as you zoom in to a street level, you'll be able to see how much vehicles are passing through that street daily, which is really cool to see. And then the other portion of this is OpenStreetMaps. OpenstreetMaps has map data that can show you some of this information, too.

I've been a personal victim of going into Google Earth and scrolling through the streets, trying to find that sign. I don't know if you guys have done that with the miles per hour, but I've been a personal victim of that. And that can be tedious. Because you're like, I've been down this street, up and down twice, and I have not found that miles-per-hour sign. I don't know where it's at. [LAUGHS]

But with OpenStreetMaps, there is a layer that you can go into there. All you have to do is click it, and it'll show you the map data. And you're able to select the streets. And it'll tell you what the miles per hour is, which is something very easy, time saver, for sure. I really enjoyed finding this out, when we found out. And I was just like, this is a lifesaver.

But at the same time, take this with a grain of salt, just because, for rural areas, you might not be able to find this information. But for central cities, you'll probably find a lot of this information, for sure. So just a tip for you guys, for external data.

Now, moving on to the microclimate analysis, which is another really cool thing to show. For our site, we wanted to show how it's being affected throughout the years and the seasons. So we ended up displaying this, just to understand how the winds are coming through the site and then being affected, at the same time. So you can see how the temperature is being perceived throughout the seasons, which is another really cool, powerful tool within Autodesk Forma.

And then, as I mentioned earlier, talking about wind comfort, we modeled this and wanted to understand how these trees are buffering a lot of that southern wind speed and creating these sitting-- standing comfortable areas in our spaces. But at the same time, we did see that some of the areas are still showing as uncomfortable. But we ended up making some interventions for that, which we're not showing here. But we ended up making some interventions for that, to mitigate some of that uncomfortable wind speeds within that area.

DANIEL STINE: Yeah, Miguel, probably worth mentioning, in Forma, for the vegetation to work properly, you have to use Forma's trees. A regular tree is just going to block all the wind, instead of letting a small fraction of the wind through, like a tree normally would, right?

MIGUEL ELIZARDO: Correct. That is correct, yes. Good point, Dan. I actually ended up testing that previously, on a couple of projects where we actually ended up modeling some just lollipop trees, in a sense, that are solids. But it's always best to use the Forma trees because they have, already, the data that ends up slowing a lot of the wind speeds down and letting some of the air still filter through.

And then, finally, getting to the last portion of this wind analysis CFD for Forma, which is what really won the project. We ended up showing this to the clients and showing what our ideas were. Because we already had an idea of what we were-- but it's displaying this and showing that to the client that really elevates this. So with this wind analysis, we were able to show our ideas about how wind was going to pass through the site. It further just validated that, which is really cool to see.

And then, lastly, we're going to talk about some, really quickly-- I know we're running short on time, talking about in-house templates. This is something that we've developed in-house and started doing for all of our studios. And this template lives in our server. And what we do is we set up a lot of the views within Forma already. So if you go to that little icon with the camera, you set up your views, whichever perspective you want to set up.

And then snapshot them up, and then get all the vector images, which you can now do in Forma, is get the charts and then be able to import them into this template. And then export the views to and then just drag and drop, which has-- I call them "time-saving templates." [LAUGHS]

But the sun hours template that we have-- I mean, I'm not going to go through all the templates. But it's just something that we've developed in-house, that has saved us a lot of time, without having to-- it's standardized the process, in a sense. So we have this for our wind template and sun. We have one for daylight. We have one for microclimate. We have one for noise.

So it's just about setting up the views in the project after, you've imported your project within Forma, and then exporting those views. And now I'm going to hand it off to Andres.

ANDRES D'SILVA: Thanks so much, Miguel, for walking through all of these case studies and the ins and outs of the softwares, as a opening to-- I mean, it gives a lot of context to talking to what the product feedback loop has been with Lake|Flato. So, very simplified. I guess, we could start with product development cycle that we, in Forma, have been following the last few years, as well as our customer group, customer base has grown quite a lot through the inclusion of the AC collection.

And I guess you could say there are two entry points, as to how new features make its way into the platform. And firstly, that's through our customers voicing their needs, either through the chat and the support or forums or other interactions, digital or live. And secondly, we have more the longer-term projects where our team also makes a hypothesis for what should be a great capability to include. And we try to test this out with our customers.

And for this presentation, I will try to focus a bit on the latter. There are, during Autodesk University, several meetups with our software developers and product managers, which are all-- encourage everyone to participate in because that's a great interaction as well, in this getting to know what is needed.

The first point is really trying to enable customers to solve certain pain points. And this, I like to call it a "spaghetti diagram." The Ladybug diagram that was shown, it really does make or break certain days in our architects' week. It is a very meticulous work that is important. And our goal is never to try to replace everything of that detail and that control.

But we're trying to bring an early image of what the results can be for the site. And in that end, Forma does a good job in cutting out some of that work. And getting the end user pain points to be really felt by our team is the key. The next steps are really all about trying to connect and make the qualitative feedback on potential solutions very tangible. So for both sides, we try to understand what is needed.

And to Miguel's templates, we also were kind enough to be shared these quite early on, when sketching out what Forma's board functionality should look like. And we were able to illustrate what are our leading users trying to solve through this platform. So this is a very cool way of back and forth, going between customers and technical teams, where I play a bit of a matchmaking role, in that sense.

For the third, more important premise for doing this work is that the cloud development platform is really enabling us to push features daily or to at least enable certain features for certain customers to test and to verify if it's solving a need or if it's more of a "nice to have," which you definitely want to avoid.

And what has been mentioned several times during today's presentation of the different solutions that exist in the architecture's toolbox, we try to ensure that it's approachable, that Forma should be an easy to use. And we always try to strive towards that goal and try to avoid the super easy trap of having a very hard-to-learn solution that is too complex.

So on the right-hand side, just a small screen grab from our internal chat on the first version of our Forma board, which was used here. The same exists, for instance, with the embodied carbon, which, also, Lake|Flato has been a part of, as well as several features, like the vector export, I believe.

This timeline continues from September last year until January and April and, as well, August. This is trying to ensure that we capture as many ideas from as many architects and users as possible. And this is just a few examples of how we have engaged with the community, through our forum, on recruiting first beta testers, which is something that I would encourage everyone to do as well, for those listening or watching this, is to check out the Forma's forum, where you're able to test and get early access. You're also able to shift and shape the future developments.

And I think the last two are more about setting up one-to-one meetings where you can really dig and ask and challenge us. And as with conferences like this one, there's great enablement of connecting coders with customers. And during this week and also during any day of this year, we will have several occasions to engage with us, either through the digital channels or in physical arenas.

And I definitely hope that this can be a good inspiration to see how you can do more with the tools that you have access through by chiming in and voicing your needs through these channels. I'll pass it over to Dan for some amazing work you've been doing on the academia part.

DANIEL STINE: Yeah, I just wanted to close out, with the couple of minutes that we have left, to share two things. One is how I have been using Forma in academia. And then the other one is, technically, a third option to what Andres said. There's the customer feedback and then the developers dreaming up amazing things, kind of, with their crystal ball. But the idea that Autodesk Forma is not just a closed ecosystem is really, really exciting and compelling, about the future trajectory of the tool and its adoption, I think.

But really quickly, about using form in the classroom, like I mentioned, I have another entire session on it. But it's a really great opportunity for students to test their assumptions and validate design strategies in an easy way. Using Rhino and Grasshopper is still really important, I think, for students to do. But this also, again, like Miguel is showing, gives them an opportunity to validate different tools and understand different workflows, to make them really valuable, in terms of getting their dream job.

In the bullet points here, there's a couple of things that are interesting. Testing the wind and different microclimate conditions of a site before you touch it is really interesting. And then, when you start impacting a site, are you actually maybe making the wind tunnel on a street worse than it was before? Not just focusing on your internal courtyard, for example. And then the fact that Autodesk actually made a connector for Rhino. And so you can still do Rhino and cool Grasshopper stuff.

There's somebody, Kevin-- I can't remember his last name-- from Nikken Sekkei in Japan, that has done a cool presentation last year. And I heard it's going to be at Autodesk University again this year, and Rhino and Grasshopper and pushing things through the connector, into Forma, for some almost real-time analysis.

And then this is-- I just have two slides left, I think. And then we're done. But this is an example of using the AI portion of Forma to analyze the traffic noise analysis. So this is before the clicking the blue button, which still only takes two to 10 minutes, as you can see there on the right. But as you start to manipulate buildings and move things around, you can both the wind AI analysis and the traffic noise AI analysis update in real time, based on adjustments that you're making, to try and mitigate noise and wind conditions.

And then, earlier, Miguel mentioned using historical weather data. There's a lot of really great resources out there now for projected future weather data and as it relates to climate change. And here in Forma, you can look at the wind as it might present itself in the future, using different carbon scenarios, as you can see highlighted there on the right.

And then the last thing is-- well, I guess there's this slide and one more. So this shows a third-party tool called FenestraPro, looking at detailed facade analysis for each orientation and understanding solar heat gains and some really robust tools from a company that's really spent many years in this space to help design window-to-wall ratios and specific testing, specific glazing types.

And then finally, Andres mentioned this embodied carbon workflow. So EHDD, an architecture firm in San Francisco, had developed this tool called EPIC. And behind it, it has this machine learning/AI, real-world building stock kind of embodied carbon database called C.Scale. And C.Scale has now been integrated into Forma.

And so here's an example. Autodesk sponsored me to create this Autodesk Forma video series I have on my YouTube channel. And this is an example of, really, how you should use these tools, right, to understand and iterate and look at good-better-best scenarios. So a concrete structure, a steel structure and a mass timber structure, and you can see the different embodied carbon scenarios.

And one really cool last comment about this embodied carbon database is that, for the cast-in-place concrete, the embodied carbon, global warming potential is accurate down to the zip code. Because every city and every location has different mixing plants. So there's not a global number for that.

And with that, we're super excited to have had this opportunity to present to you, show you what Lake|Flato is doing and a little sneak peek of Autodesk Forma, what's happening there and what will be happening at Autodesk University. And highly recommend you all definitely get involved in the beta or the user feedback channels to help influence the trajectory of the product. Miguel and Andres, do you want to add any last comments? And then we'll close her down.

MIGUEL ELIZARDO: No, yes, I'm just thankful for the opportunity. And I'm very excited for this. It's been a process. And I've enjoyed working with Autodesk and Andres and the team. Every time I've provided some feedback, they've been open and receptive to the information. And the product has come a long way. And I'm so happy to see its developments and implementation. I mean, our office really enjoys using the tools. So, I mean, I could see it getting better and better.

ANDRES D'SILVA: Yeah, all thanks to the end users, really. I think it's amazing to see what you've done in the time it's been on our beta, by select invitation-only to today and the access through the collection, as mentioned, for everyone, really. And, yeah, hope to see more engagements in our different channels to really push this forward.

DANIEL STINE: Thanks, everyone.

MIGUEL ELIZARDO: Thank you, everybody.

ANDRES D'SILVA: Thank you.

______
icon-svg-close-thick

쿠기 기본 설정

오토데스크는 고객의 개인 정보와 최상의 경험을 중요시합니다. 오토데스크는 정보를 사용자화하고 응용프로그램을 만들기 위해 고객의 본 사이트 사용에 관한 데이터를 수집합니다.

오토데스크에서 고객의 데이터를 수집하고 사용하도록 허용하시겠습니까?

오토데스크에서 사용하는타사 서비스개인정보 처리방침 정책을 자세히 알아보십시오.

반드시 필요 - 사이트가 제대로 작동하고 사용자에게 서비스를 원활하게 제공하기 위해 필수적임

이 쿠키는 오토데스크에서 사용자 기본 설정 또는 로그인 정보를 저장하거나, 사용자 요청에 응답하거나, 장바구니의 품목을 처리하기 위해 필요합니다.

사용자 경험 향상 – 사용자와 관련된 항목을 표시할 수 있게 해 줌

이 쿠키는 오토데스크가 보다 향상된 기능을 제공하고 사용자에게 맞는 정보를 제공할 수 있게 해 줍니다. 사용자에게 맞는 정보 및 환경을 제공하기 위해 오토데스크 또는 서비스를 제공하는 협력업체에서 이 쿠키를 설정할 수 있습니다. 이 쿠키를 허용하지 않을 경우 이러한 서비스 중 일부 또는 전체를 이용하지 못하게 될 수 있습니다.

광고 수신 설정 – 사용자에게 타겟팅된 광고를 제공할 수 있게 해 줌

이 쿠키는 사용자와 관련성이 높은 광고를 표시하고 그 효과를 추적하기 위해 사용자 활동 및 관심 사항에 대한 데이터를 수집합니다. 이렇게 데이터를 수집함으로써 사용자의 관심 사항에 더 적합한 광고를 표시할 수 있습니다. 이 쿠키를 허용하지 않을 경우 관심 분야에 해당되지 않는 광고가 표시될 수 있습니다.

icon-svg-close-thick

타사 서비스

각 범주에서 오토데스크가 사용하는 타사 서비스와 온라인에서 고객으로부터 수집하는 데이터를 사용하는 방식에 대해 자세히 알아보십시오.

icon-svg-hide-thick

icon-svg-show-thick

반드시 필요 - 사이트가 제대로 작동하고 사용자에게 서비스를 원활하게 제공하기 위해 필수적임

Qualtrics
오토데스크는 고객에게 더욱 시의적절하며 관련 있는 이메일 컨텐츠를 제공하기 위해 Qualtrics를 이용합니다. 이를 위해, 고객의 온라인 행동 및 오토데스크에서 전송하는 이메일과의 상호 작용에 관한 데이터를 수집합니다. 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 이메일 확인율, 클릭한 링크 등이 포함될 수 있습니다. 오토데스크는 이 데이터를 다른 소스에서 수집된 데이터와 결합하여 고객의 판매 또는 고객 서비스 경험을 개선하며, 고급 분석 처리에 기초하여 보다 관련 있는 컨텐츠를 제공합니다. Qualtrics 개인정보취급방침
Akamai mPulse
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Akamai mPulse를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Akamai mPulse 개인정보취급방침
Digital River
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Digital River를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Digital River 개인정보취급방침
Dynatrace
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Dynatrace를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Dynatrace 개인정보취급방침
Khoros
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Khoros를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Khoros 개인정보취급방침
Launch Darkly
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Launch Darkly를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Launch Darkly 개인정보취급방침
New Relic
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 New Relic를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. New Relic 개인정보취급방침
Salesforce Live Agent
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Salesforce Live Agent를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Salesforce Live Agent 개인정보취급방침
Wistia
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Wistia를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Wistia 개인정보취급방침
Tealium
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Tealium를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Upsellit
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Upsellit를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. CJ Affiliates
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 CJ Affiliates를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Commission Factory
Typepad Stats
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Typepad Stats를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Typepad Stats 개인정보취급방침
Geo Targetly
Autodesk는 Geo Targetly를 사용하여 웹 사이트 방문자를 가장 적합한 웹 페이지로 안내하거나 위치를 기반으로 맞춤형 콘텐츠를 제공합니다. Geo Targetly는 웹 사이트 방문자의 IP 주소를 사용하여 방문자 장치의 대략적인 위치를 파악합니다. 이렇게 하면 방문자가 (대부분의 경우) 현지 언어로 된 콘텐츠를 볼 수 있습니다.Geo Targetly 개인정보취급방침
SpeedCurve
Autodesk에서는 SpeedCurve를 사용하여 웹 페이지 로드 시간과 이미지, 스크립트, 텍스트 등의 후속 요소 응답성을 측정하여 웹 사이트 환경의 성능을 모니터링하고 측정합니다. SpeedCurve 개인정보취급방침
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

사용자 경험 향상 – 사용자와 관련된 항목을 표시할 수 있게 해 줌

Google Optimize
오토데스크는 사이트의 새 기능을 테스트하고 이러한 기능의 고객 경험을 사용자화하기 위해 Google Optimize을 이용합니다. 이를 위해, 고객이 사이트를 방문해 있는 동안 행동 데이터를 수집합니다. 이 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 오토데스크 ID 등이 포함될 수 있습니다. 고객은 기능 테스트를 바탕으로 여러 버전의 오토데스크 사이트를 경험하거나 방문자 특성을 바탕으로 개인화된 컨텐츠를 보게 될 수 있습니다. Google Optimize 개인정보취급방침
ClickTale
오토데스크는 고객이 사이트에서 겪을 수 있는 어려움을 더 잘 파악하기 위해 ClickTale을 이용합니다. 페이지의 모든 요소를 포함해 고객이 오토데스크 사이트와 상호 작용하는 방식을 이해하기 위해 세션 녹화를 사용합니다. 개인적으로 식별 가능한 정보는 가려지며 수집되지 않습니다. ClickTale 개인정보취급방침
OneSignal
오토데스크는 OneSignal가 지원하는 사이트에 디지털 광고를 배포하기 위해 OneSignal를 이용합니다. 광고는 OneSignal 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 OneSignal에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 OneSignal에 제공하는 데이터를 사용합니다. OneSignal 개인정보취급방침
Optimizely
오토데스크는 사이트의 새 기능을 테스트하고 이러한 기능의 고객 경험을 사용자화하기 위해 Optimizely을 이용합니다. 이를 위해, 고객이 사이트를 방문해 있는 동안 행동 데이터를 수집합니다. 이 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 오토데스크 ID 등이 포함될 수 있습니다. 고객은 기능 테스트를 바탕으로 여러 버전의 오토데스크 사이트를 경험하거나 방문자 특성을 바탕으로 개인화된 컨텐츠를 보게 될 수 있습니다. Optimizely 개인정보취급방침
Amplitude
오토데스크는 사이트의 새 기능을 테스트하고 이러한 기능의 고객 경험을 사용자화하기 위해 Amplitude을 이용합니다. 이를 위해, 고객이 사이트를 방문해 있는 동안 행동 데이터를 수집합니다. 이 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 오토데스크 ID 등이 포함될 수 있습니다. 고객은 기능 테스트를 바탕으로 여러 버전의 오토데스크 사이트를 경험하거나 방문자 특성을 바탕으로 개인화된 컨텐츠를 보게 될 수 있습니다. Amplitude 개인정보취급방침
Snowplow
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Snowplow를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Snowplow 개인정보취급방침
UserVoice
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 UserVoice를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. UserVoice 개인정보취급방침
Clearbit
Clearbit를 사용하면 실시간 데이터 보강 기능을 통해 고객에게 개인화되고 관련 있는 환경을 제공할 수 있습니다. Autodesk가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. Clearbit 개인정보취급방침
YouTube
YouTube는 사용자가 웹 사이트에 포함된 비디오를 보고 공유할 수 있도록 해주는 비디오 공유 플랫폼입니다. YouTube는 비디오 성능에 대한 시청 지표를 제공합니다. YouTube 개인정보보호 정책

icon-svg-hide-thick

icon-svg-show-thick

광고 수신 설정 – 사용자에게 타겟팅된 광고를 제공할 수 있게 해 줌

Adobe Analytics
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Adobe Analytics를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID 및 오토데스크 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. Adobe Analytics 개인정보취급방침
Google Analytics (Web Analytics)
오토데스크 사이트에서 고객의 행동에 관한 데이터를 수집하기 위해 Google Analytics (Web Analytics)를 이용합니다. 여기에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 오토데스크는 사이트 성과를 측정하고 고객의 온라인 경험의 편리함을 평가하여 기능을 개선하기 위해 이러한 데이터를 이용합니다. 또한, 이메일, 고객 지원 및 판매와 관련된 고객 경험을 최적화하기 위해 고급 분석 방법도 사용하고 있습니다. AdWords
Marketo
오토데스크는 고객에게 더욱 시의적절하며 관련 있는 이메일 컨텐츠를 제공하기 위해 Marketo를 이용합니다. 이를 위해, 고객의 온라인 행동 및 오토데스크에서 전송하는 이메일과의 상호 작용에 관한 데이터를 수집합니다. 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 이메일 확인율, 클릭한 링크 등이 포함될 수 있습니다. 오토데스크는 이 데이터를 다른 소스에서 수집된 데이터와 결합하여 고객의 판매 또는 고객 서비스 경험을 개선하며, 고급 분석 처리에 기초하여 보다 관련 있는 컨텐츠를 제공합니다. Marketo 개인정보취급방침
Doubleclick
오토데스크는 Doubleclick가 지원하는 사이트에 디지털 광고를 배포하기 위해 Doubleclick를 이용합니다. 광고는 Doubleclick 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Doubleclick에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Doubleclick에 제공하는 데이터를 사용합니다. Doubleclick 개인정보취급방침
HubSpot
오토데스크는 고객에게 더욱 시의적절하며 관련 있는 이메일 컨텐츠를 제공하기 위해 HubSpot을 이용합니다. 이를 위해, 고객의 온라인 행동 및 오토데스크에서 전송하는 이메일과의 상호 작용에 관한 데이터를 수집합니다. 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 이메일 확인율, 클릭한 링크 등이 포함될 수 있습니다. HubSpot 개인정보취급방침
Twitter
오토데스크는 Twitter가 지원하는 사이트에 디지털 광고를 배포하기 위해 Twitter를 이용합니다. 광고는 Twitter 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Twitter에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Twitter에 제공하는 데이터를 사용합니다. Twitter 개인정보취급방침
Facebook
오토데스크는 Facebook가 지원하는 사이트에 디지털 광고를 배포하기 위해 Facebook를 이용합니다. 광고는 Facebook 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Facebook에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Facebook에 제공하는 데이터를 사용합니다. Facebook 개인정보취급방침
LinkedIn
오토데스크는 LinkedIn가 지원하는 사이트에 디지털 광고를 배포하기 위해 LinkedIn를 이용합니다. 광고는 LinkedIn 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 LinkedIn에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 LinkedIn에 제공하는 데이터를 사용합니다. LinkedIn 개인정보취급방침
Yahoo! Japan
오토데스크는 Yahoo! Japan가 지원하는 사이트에 디지털 광고를 배포하기 위해 Yahoo! Japan를 이용합니다. 광고는 Yahoo! Japan 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Yahoo! Japan에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Yahoo! Japan에 제공하는 데이터를 사용합니다. Yahoo! Japan 개인정보취급방침
Naver
오토데스크는 Naver가 지원하는 사이트에 디지털 광고를 배포하기 위해 Naver를 이용합니다. 광고는 Naver 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Naver에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Naver에 제공하는 데이터를 사용합니다. Naver 개인정보취급방침
Quantcast
오토데스크는 Quantcast가 지원하는 사이트에 디지털 광고를 배포하기 위해 Quantcast를 이용합니다. 광고는 Quantcast 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Quantcast에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Quantcast에 제공하는 데이터를 사용합니다. Quantcast 개인정보취급방침
Call Tracking
오토데스크는 캠페인을 위해 사용자화된 전화번호를 제공하기 위하여 Call Tracking을 이용합니다. 그렇게 하면 고객이 오토데스크 담당자에게 더욱 빠르게 액세스할 수 있으며, 오토데스크의 성과를 더욱 정확하게 평가하는 데 도움이 됩니다. 제공된 전화번호를 기준으로 사이트에서 고객 행동에 관한 데이터를 수집할 수도 있습니다. Call Tracking 개인정보취급방침
Wunderkind
오토데스크는 Wunderkind가 지원하는 사이트에 디지털 광고를 배포하기 위해 Wunderkind를 이용합니다. 광고는 Wunderkind 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Wunderkind에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Wunderkind에 제공하는 데이터를 사용합니다. Wunderkind 개인정보취급방침
ADC Media
오토데스크는 ADC Media가 지원하는 사이트에 디지털 광고를 배포하기 위해 ADC Media를 이용합니다. 광고는 ADC Media 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 ADC Media에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 ADC Media에 제공하는 데이터를 사용합니다. ADC Media 개인정보취급방침
AgrantSEM
오토데스크는 AgrantSEM가 지원하는 사이트에 디지털 광고를 배포하기 위해 AgrantSEM를 이용합니다. 광고는 AgrantSEM 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 AgrantSEM에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 AgrantSEM에 제공하는 데이터를 사용합니다. AgrantSEM 개인정보취급방침
Bidtellect
오토데스크는 Bidtellect가 지원하는 사이트에 디지털 광고를 배포하기 위해 Bidtellect를 이용합니다. 광고는 Bidtellect 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Bidtellect에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Bidtellect에 제공하는 데이터를 사용합니다. Bidtellect 개인정보취급방침
Bing
오토데스크는 Bing가 지원하는 사이트에 디지털 광고를 배포하기 위해 Bing를 이용합니다. 광고는 Bing 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Bing에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Bing에 제공하는 데이터를 사용합니다. Bing 개인정보취급방침
G2Crowd
오토데스크는 G2Crowd가 지원하는 사이트에 디지털 광고를 배포하기 위해 G2Crowd를 이용합니다. 광고는 G2Crowd 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 G2Crowd에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 G2Crowd에 제공하는 데이터를 사용합니다. G2Crowd 개인정보취급방침
NMPI Display
오토데스크는 NMPI Display가 지원하는 사이트에 디지털 광고를 배포하기 위해 NMPI Display를 이용합니다. 광고는 NMPI Display 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 NMPI Display에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 NMPI Display에 제공하는 데이터를 사용합니다. NMPI Display 개인정보취급방침
VK
오토데스크는 VK가 지원하는 사이트에 디지털 광고를 배포하기 위해 VK를 이용합니다. 광고는 VK 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 VK에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 VK에 제공하는 데이터를 사용합니다. VK 개인정보취급방침
Adobe Target
오토데스크는 사이트의 새 기능을 테스트하고 이러한 기능의 고객 경험을 사용자화하기 위해 Adobe Target을 이용합니다. 이를 위해, 고객이 사이트를 방문해 있는 동안 행동 데이터를 수집합니다. 이 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역, IP 주소 또는 장치 ID, 오토데스크 ID 등이 포함될 수 있습니다. 고객은 기능 테스트를 바탕으로 여러 버전의 오토데스크 사이트를 경험하거나 방문자 특성을 바탕으로 개인화된 컨텐츠를 보게 될 수 있습니다. Adobe Target 개인정보취급방침
Google Analytics (Advertising)
오토데스크는 Google Analytics (Advertising)가 지원하는 사이트에 디지털 광고를 배포하기 위해 Google Analytics (Advertising)를 이용합니다. 광고는 Google Analytics (Advertising) 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Google Analytics (Advertising)에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Google Analytics (Advertising)에 제공하는 데이터를 사용합니다. Google Analytics (Advertising) 개인정보취급방침
Trendkite
오토데스크는 Trendkite가 지원하는 사이트에 디지털 광고를 배포하기 위해 Trendkite를 이용합니다. 광고는 Trendkite 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Trendkite에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Trendkite에 제공하는 데이터를 사용합니다. Trendkite 개인정보취급방침
Hotjar
오토데스크는 Hotjar가 지원하는 사이트에 디지털 광고를 배포하기 위해 Hotjar를 이용합니다. 광고는 Hotjar 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Hotjar에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Hotjar에 제공하는 데이터를 사용합니다. Hotjar 개인정보취급방침
6 Sense
오토데스크는 6 Sense가 지원하는 사이트에 디지털 광고를 배포하기 위해 6 Sense를 이용합니다. 광고는 6 Sense 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 6 Sense에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 6 Sense에 제공하는 데이터를 사용합니다. 6 Sense 개인정보취급방침
Terminus
오토데스크는 Terminus가 지원하는 사이트에 디지털 광고를 배포하기 위해 Terminus를 이용합니다. 광고는 Terminus 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 Terminus에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 Terminus에 제공하는 데이터를 사용합니다. Terminus 개인정보취급방침
StackAdapt
오토데스크는 StackAdapt가 지원하는 사이트에 디지털 광고를 배포하기 위해 StackAdapt를 이용합니다. 광고는 StackAdapt 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 StackAdapt에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 StackAdapt에 제공하는 데이터를 사용합니다. StackAdapt 개인정보취급방침
The Trade Desk
오토데스크는 The Trade Desk가 지원하는 사이트에 디지털 광고를 배포하기 위해 The Trade Desk를 이용합니다. 광고는 The Trade Desk 데이터와 고객이 사이트를 방문하는 동안 오토데스크가 수집하는 행동 데이터 모두에 기초하여 제공됩니다. 오토데스크가 수집하는 데이터에는 고객이 방문한 페이지, 시작한 체험판, 재생한 동영상, 구매 내역 및 IP 주소 또는 장치 ID가 포함될 수 있습니다. 이 정보는 The Trade Desk에서 고객으로부터 수집한 데이터와 결합될 수 있습니다. 오토데스크는 디지털 광고 경험에 대한 사용자화를 개선하고 고객에게 더욱 관련 있는 광고를 제시하기 위해 The Trade Desk에 제공하는 데이터를 사용합니다. The Trade Desk 개인정보취급방침
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

정말 더 적은 온라인 경험을 원하십니까?

오토데스크는 고객 여러분에게 좋은 경험을 드리고 싶습니다. 이전 화면의 범주에 대해 "예"를 선택하셨다면 오토데스크는 고객을 위해 고객 경험을 사용자화하고 향상된 응용프로그램을 제작하기 위해 귀하의 데이터를 수집하고 사용합니다. 언제든지 개인정보 처리방침을 방문해 설정을 변경할 수 있습니다.

고객의 경험. 고객의 선택.

오토데스크는 고객의 개인 정보 보호를 중요시합니다. 오토데스크에서 수집하는 정보는 오토데스크 제품 사용 방법, 고객이 관심을 가질 만한 정보, 오토데스크에서 더욱 뜻깊은 경험을 제공하기 위한 개선 사항을 이해하는 데 도움이 됩니다.

오토데스크에서 고객님께 적합한 경험을 제공해 드리기 위해 고객님의 데이터를 수집하고 사용하도록 허용하시겠습니까?

선택할 수 있는 옵션을 자세히 알아보려면 이 사이트의 개인 정보 설정을 관리해 사용자화된 경험으로 어떤 이점을 얻을 수 있는지 살펴보거나 오토데스크 개인정보 처리방침 정책을 확인해 보십시오.