AU Class
AU Class
class - AU

3D Laser Scanning and Revit Design Workflow

共享此课程
在视频、演示文稿幻灯片和讲义中搜索关键字:

说明

We will cover the concept of 3D laser scanning and how to take it from a raw scan-a quick overview of processing to modeling of architectural, structural, and mechanical systems. The main portion of the class will be the import and the use of the 3D point cloud data in Revit software. Topics will be how to orient the data for use and how to work with the point cloud data visually, as well as the use of clipping boxes, section cuts, and view ranges to declutter and clearly see the point cloud data. We will show how to model walls and structure and also how to model in piping and mechanical equipment. Finally, we will cover a case study of how 3D scanning and using the data with Revit saves us time and money-and also helps us deliver a product that is accurate and greatly reduces the chances for addendum and change orders in a project.

主要学习内容

  • Learn how to successfully import scan data into Revit and align it for use
  • Learn how to successfully manipulate the view of the scan data with clipping boxes, sections, and view ranges to better visualize the data
  • Learn how to successfully model in architectural and structural elements with the use of scan data as a reference
  • Learn how to successfully model in mechanical equipment and pipes with the use of scan data as a reference

讲师

  • Lucas Pederson
    Lead Technician and Designer for the Water and Wastewater Group with 17 year of experience.Also the primary 3D laser scanning technician at SEH.Primary duties are the design of water/wastewater facilities using AutoCAD and Revit.3d scanning is an integral part of our work flow here at SEH and I incorporate that on most projects.Education is a Associates degree from Chippewa Valley Technical College and a Bachelor degree in Computer Science from Lakeland College.I also sit on an advisory committee for over 6 years for the Architectural and Engineering Technician program at Chippewa Valley Technical College.
Video Player is loading.
Current Time 0:00
Duration 0:00
Loaded: 0%
Stream Type LIVE
Remaining Time 0:00
 
1x
  • Chapters
  • descriptions off, selected
  • subtitles off, selected
      Transcript

      LUKE PEDERSON: First of all, this is the 3D Laser Scanning Revit Design Workflow class. I assume you're all in the right spot, otherwise they wouldn't let you in here through the tight security.

      I'll start with a little bit about me in just a second here. But I want to know a little bit about you first just to give me an idea who we got in the class here. I gave this presentation to my wife a couple of weeks ago. And she just stood there with a blank look in her face. And it is really hard to give it to her. So it would be nice if I know who we got here.

      How many people are Revit users? Most. How about people that do laser scanning, actually, physically do the scans? About what I expected. And who are Revit users that have used point clouds or plan to use point clouds in their projects? And that latter one, I guess, I assume, if you plan to use them, that's why you're here. Otherwise, I'm not sure why you'd be here.

      So a little bit about me, and then we'll get started. I have an associate's degree-- well, first of all, my name is Luke Pederson. This is my first class here at AU. I have attended a couple of these before, but this is my first time teaching.

      I have an associate's degree in drafting-- just a generic term. There's a longer title than that, but we'll call it drafting-- a bachelor degree in computer science. I've been a design technician for SEH, in Chippewa Falls, Wisconsin, for the last 17 years.

      The bulk of what I do there is design water and wastewater treatment plants. I do basic architecture. I'm not an architect. The buildings I do are pretty utilitarian, so I get the job done, for the most part, but the architect takes over in the end.

      I do basic structural layout. I just have enough experience, I can kind of guess how big tanks need to be in walls. I do enough to get by, to get things started. And the bulk of what I do, the technical part of what I do, is process piping layout in Revit, process piping equipment, stuff that Revit does. We're using it a little bit outside the box, but it does what we do, pretty good, and it's getting better every year at it.

      So most of my work, nowadays, is done in Revit. Believe it or not, I still use AutoCAD a little bit. I think there's always a place for AutoCAD, for what I do, some simple things. It just doesn't pay to model things in 3D, sometimes. And I'll talk a little bit about ReCap. I use that also.

      So the class summary-- first, I want to talk about-- we've been here. This is the end of AU now, pretty much. We got one more session after this. So we've been dazzled by all kinds of fancy software and platforms that can seamlessly integrate design teams from around the world.

      We can take projects, from concept, to design, to construction, through the lifecycle of the building. And all of these people can be integrated in design teams and everywhere, all around the world, seamlessly working together. That is absolutely not what we're going to be talking about during this class here.

      I'm kind of a one-man-show doing what I do. I have a basic toolkit. And the basic toolkit I have is Revit, ReCap. I use FARO, FARO scanner, so I process in FARO SCENE. There's no reason why you couldn't use ReCap or use the other software processing that comes with whatever brand of scanner you are using. I happen to use SCENE.

      And that's about it. I don't use a lot of these other fancy stuff, that's really neat, but that's not what we're here today to talk about. It's not a basic level class, because you should know about point clouds, and you should know about Revit to be here.

      But it's basic, in the sense that, from what I see, in all those presentations that we went to, there are some crazy, wild stuff out there. But this is basic. If you want to call laser scanning and Revit basic, but I guess it is these days.

      I come from a relatively small town in Northwest Wisconsin. It's a relatively rural part of the community, and I'm in a branch office. I'm sort of a one-man-show. They just want me to get my job done with the basic toolkit.

      And so this is my workflow, that I'm going to talk about here, for bringing a point cloud in and designing, in Revit, with a point cloud as a reference.

      We used to use, a long time ago-- a long time ago, as in two years ago-- anything from as-built plans-- those are great if you have them. I work in water and wastewater. Those things get tucked down in a basement. And the basement floods, and they're gone.

      Sometimes they don't exist. Sometimes they do exist. Rarely are they accurate. Sometimes I have photos. And how many of you have designed from photos before? Counting the block on the wall to figure out where the door is in there and how high the ceiling is by counting horses and things like that. We've all done that.

      Or spent days or hours and hours out on a site with a tape measure-- maybe you got somebody to hold the end, maybe not. Maybe you're taping the tape measure to the wall trying to measure stuff. And then getting back and trying to decipher your notes, what you wrote, for the last four hours on site and getting just the very basic of measurements.

      So I got a new laser scan that's really-- it was a game changer for me. Our company doesn't have the-- we don't do some of the high-end stuff. So basically, what I've done here is just using the basic tools, with Revit, ReCap, and a laser scan to get the job done.

      We're going to talk a bit about laser scanning, first of all, because that is part of this. This isn't a course on laser scanning here. We're not going to talk about how to do it. But I think we do need to talk a bit about it to make the rest of it relevant.

      Importing scan data and talk a little bit about the scan files that Revit likes to use. There's lots of scan files that you can get. There's only two that Revit can use. But there's a way to get to that point.

      So once you have the scan data, you need to deal with it. It's a big blob of data. How many have used point clouds before? Yeah, it's a big thing That looks neat from afar but to get into the guts of it, it takes some work to make it usable in your drawing.

      Manually modeling architecture and structural elements using the scan data as a reference. The alternative being using field measurements as a reference, using photographs, or using as-builts as a reference. We're not going to talk about that. Scan data is our reference today.

      In a lot of cases, when I do a new project, coming in, and we're starting from as-built conditions, that's all I need. A scan really is everything that I need.

      And then manually modeling mechanical equipment, such as pumps and pipes, using the scan data. Now mechanical, in my world, is process piping. Plumbing, electrical is stuff that I don't do. So the same stuff, the same applies. A pipe's a pipe. Some of it's smaller. Some of it's bigger. Revit really treats it all the same.

      And then open questions and discuss from real world experience. I have some examples, some things where things went good and where things went bad.

      And with that, I'm going to say, I teach some adult photography. Not adult. Boy, that came out weird.

      [LAUGHTER]

      I teach some photography for adults.

      [LAUGHTER]

      I told myself, don't say it in the other way. And I said it the wrong way.

      AUDIENCE: I guess it's the right way.

      LUKE PEDERSON: Yeah, I guess so. I encourage people to interrupt me with questions, comments, stories, whatever. That's how I operate it. So you don't have to sit there, silent, just blurt out a question, raise your hand, whatever. It makes things go better for me.

      And I think it makes the class better, in the end, too. Well, few of us here are starting from scratch. So we all have something relevant to add to this.

      So we're going to start with, what is laser scanning? Many of you probably know. So we'll just start quickly here. Over there, that's the laser scanner I use. It's a FARO. It's not the current model. But it's, I think, one or two generations old.

      That's the brand I use. There's many out there. This isn't about FARO or anything like that. But the files that they put out, they're really kind of the same in the end. So it doesn't matter how you get it. That's just what I do.

      So what is laser scanning? The process of capturing three-dimensional spatial information about objects in the sightline and range of the laser scanner. I guess that's some technical definition, that I found online, that I modified a little bit.

      Different scanners use different methods. But all will compile a database of thousands to millions of points. That's per scan. They're spatial coordinates and possibly some other color data.

      So what I mean by that is, every time you set up the scanner, and I press go, in my settings that I use, it's usually 7 million to 11 million points. And each one of those points has an x, y, z-coordinate. And it has some color value to it. If I shoot with color, it's an RGB value.

      If I shoot with no color, it still records an intensity value, which some people call black and white, but it really isn't black and white. It's basically how bright the laser reflected off of something. So it kind of looks like black and white, but it really isn't.

      And what is a laser scanning project? A typical scan project consists of at least one but most of the time many individual setups. I don't think I've ever done one that's just been one scan, because I probably wouldn't take the time to scan it if it really was just something that could get captured with one scan.

      Basically, most, if not all of the projects, there's going to be multiple scans tied together into one point cloud when you're done with it. So individual setups, when you do a scan with multiple scans, they must be registered to create one point cloud.

      Each scan doesn't know how to relate to one another. So that's part of the step in the scanning process. We're not going to talk about that today, because that's kind of out of the scope of this class. But we all should know kind of what goes in behind it. If you do hire a scan, they're not going to come back and give you a memory card, and it's going to be just like that. There is some processing involved in it.

      The methods of registration include targeted, cloud-to-cloud, and survey control. And we'll talk a little bit about each of those. But first, some key terms. Laser scan, we kind of covered that. Registration, so that's tying all the individual scans together into one point cloud. And so those all those scans share the same spatial data relative to one another, so they're just not individual scans floating in random space.

      Targets, those are what I use to register the scans together. We'll talk about that in just a second. Point cloud, that's what you're going to get out of the scanner when you're all done. And you're going to use in Revit, in a format that's compatible with Revit. And there's a little bit to get to that point.

      Intensity versus color, I talked about that a little bit. When you scan, for various reasons, you might pick intensity versus color. Intensity is way faster to get. In the particular scanner that I use, it saves about 2 and 1/2 minutes a scan. And when we have a job that's 100 scans big, that is over four hours of time that it would take just to get the color data.

      A lot of times, it's very useful, especially for presentations, if you're in a pipe gallery, so you can see the color of the pipe, if the pipes aren't labeled, or if you couldn't read the labels, because they are too small.

      I just got done scanning a stockpile of sand for a mine. I don't care. The sand's all brown anyway, so it doesn't really matter, the color. It saved me a lot of time by flipping that color off.

      It's worth understanding that if you're scanning and also commissioning a scan. If somebody asks you, just don't default, well, yeah, if you got color, give me color. Well, there's a cost to that. And here is a term, intensity versus accuracy. I'm going to talk a lot about that coming up. I'm reading, intent versus accuracy.

      When you're scanning, the scanner is very literal. If two walls are apart-- in here, what are we, 30 feet? If these two walls are-- the scanner might say these two walls are 30 feet, 0 inches, and 117/256 of an inch apart. Are you going to model it like that?

      It's for you to decide. That's intent versus accuracy. The intent is probably 30 feet. Accuracy is that 30 feet and weird fraction of an inch. And it's up to you to decide how you want to model that. You're going to find that a lot, especially in older construction. You're going to find walls out of plumb. You're going to find pipe out of level and out of plumb. It'll drive you batty, sometimes, deciding how to model it.

      So there's a few terms I'm going to talk about here, target based registration. We'll just go through these quickly, because, again, this is a little outside the scope of the class, but it's worth understanding.

      So target base registration uses common targets, checkerboards or spheres, in my case, between scans to register together. So when you have a scan, and then you did another scan, there's points floating in space. And they don't know how they relate to one another. They're points floating in space. They can go any way they want to go.

      If they both share one common point, they still can relate together a lot. They can move all around relative to one another. But they're closer. If you have two points in common, those scans are pretty close. But there's still a lot of ways that they can not relate properly to one another.

      If you have three points in common, it's like three legs on a stool, it doesn't rock. There's no way for those to go other than that one way. So that's very important that we have three targets shared between each scan. That's just best practices in scanning.

      I do four, at least, because, inevitably, your target will get kicked, knocked over, fall off the wall. You forget to put it up. You set your scanner up, and you hit Start, and you realize that one of your targets is hidden by something. And so you only have two. I use four.

      There's actually a fifth hidden one. Every scanner knows what level is. So that level plane is one. So that's kind of your back-pocket, just in case, if all else fails, a target that no one can mess with, except for me, when I pick the scanner up too early, when it's not done, and it measures level all wonky. And that's just me.

      Targeted registration is slow to acquire but very fast to process. Because, in the end, the processing only has to look for a few points and line those points up. It's done in a relative instant in the processing. And when I say, "relative instant," I mean seconds. to do it. Versus some of the other methods, which are way longer.

      And that would be cloud-to-cloud registration. And cloud-to-cloud registration, it takes a lot less time to do, because I set my scanner up, I hit Start, and I move it. And I move it. And I move it. I move it. I never have to move the targets. I never have to plan where they have to be or anything like that. I'm just constantly hit and go, wait until it's done, moving it.

      It's when I get back, the processing time takes way longer. Because what the computer programs are doing, either ReCap or SCENE, in my case, are looking at the physical features. And it's finding patterns in the points. And it's matching those patterns up in the points.

      So what it has to do, it has to load in all these scans and look for patterns. And your computer, when it's doing that, becomes an awesome heater. And it just heats up the room and blows. And it takes forever to do.

      But if you're in the situation where you need to acquire the data quickly, or the place is so big that targets become impractical, because the scanner can only see targets maybe 30 feet away, 40, 60 feet away, you have to set up so many times to maneuver.

      In this case, this is a mine. You can see, there's a big pile, right here. It would take me forever, 60 feet at a time, around and around and around here. So I needed to get done quickly. So I opted for cloud-to-cloud registration.

      What you need is about 50% overlap per scan. So if I scan here, and I want to move it, as long as I can see half of what I could see in the previous one, they'll register together fine. There's some wiggle room each way. But that's kind of a general rule of thumb, 50%.

      Even if I do cloud-to-cloud registration, I still like to group them together and tie the groups with targets. So in this, each of these colors represents maybe six, eight scans. And each of the groups then is tied together with targets.

      So the red group saw some targets that were in the green group, and the orange to the red, and the orange to the blue, and the blue back to the green. So what I could do is process six of these at a time. And the computer registered them together.

      And then when I was done, the-- what do we have-- five groups registered together with targets, which was much quicker than loading 26, I think, scans in, live, on your computer, having them look for patterns and grind away. That can literally take hours of processing time. So it's best to keep cloud-to-cloud registration into smaller groups if you can.

      And then, finally, there's something that I don't use, because the scanner I used doesn't do it, but survey based registration. A lot of the scanners now that are coming out are also total stations. So you can set them up on survey control, either with like total station control or with GPS, and they know where they are in space. And then when you move it, it knows where it is again. And that's how they register together.

      I don't do that, so I can't talk a lot about it. Our company surveyors have some of those that they're just starting to use. The problems with it can be on the inside. GPS doesn't work real good in here. So you still have to be able to do the targeted or the cloud-to-cloud, whatever. You can do both. You can mix and match within scans. I don't do that much.

      So planning a laser scan-- One of the first questions you're going to get or have to answer is estimating time. How long is it going to take? That is a really open-end question. You're going to need to know a lot about the project to be able to properly estimate the time.

      So I'm just going to give you a couple of examples, here, in these next few slides. How long it takes is really a function of how many scans you have to do, and then, also, how long each scan is going to take. And that's where that color is probably the biggest determining factor. Because color automatically adds 2 and 1/2 minutes to every single scan.

      But size-- so this room here, very easy to scan. Well, with nobody in it and nothing here, very easy. Boom, run scan in the middle. It can see everything you need to see, pretty much, unless you really needed to get some detail up in those coves. But generally, this room is very easy.

      Imagine this room a lot more complex, pipe gallery with pipes and pumps sitting everywhere, a duct up there, pipe going everywhere. A scanner can only see what it can see from a point. And if there's something in the way, it won't see behind it. So you're going to have to move that scanner behind that to see. The more complex it is, the more time it will take, because you'll have more setups.

      It's not really a function of square feet. It can be, but square foot in a library is a lot different than square foot in a conference hall like this. Even though this conference hall is probably much bigger than a lot of the libraries, there's still a lot less setups, because it's just, boom, one in each room.

      So here's an example I have. This is a very simple room. We've got four walls. And we got like one internal dividing wall. One scan point, everything that's in red, the scanner can see. It can't see behind this wall. And it can't see under itself.

      This is usually not a problem, because one can assume the floor just keeps going right underneath the scanner. If there is something really important under there, you wouldn't get it. But hopefully, if you're scanning or you have a commission to scan, hopefully, the person scanning knows enough not to set it right on top of something really important. Because it can't see it. That's kind of a best practices thing.

      The second scan, in this case, gives you everything that the first one missed. So it's all that. This was before. This was before. 100% coverage in two scans, very easy. Here's the exact same size room but with a lot more dividers.

      All these are maybe office cubicles or something. And then there's a column or something in the way here. One scan gets you what's red here. And the rest of it is all not scanned. There's no data in that. Now, maybe this is good enough. Maybe when you walked in here, you notice that there is nothing back here other than a wall, up to the ceiling, down to the floor.

      Well, that wall plane is already defined there. That one's there. That one's there. The floor is there. The ceiling's above. That back wall's there. Maybe that's good enough. But maybe not. Maybe there's a window or a door in each one of these that you need to get the exact location of.

      So you've got to do another scan. That fills in a lot of the blanks. We're still missing something there and there and there and there. Again, if there's a window there, you're going to have to do another one here, another one here, and here, and here.

      So there is a point of diminishing returns. You don't necessarily need to get every square inch of everything in there. Like I said, if there's no window there, you have that wall plane there, you have that wall plane there. One can assume that wall just goes straight on through. That's probably fine.

      So you can get to a point of diminishing returns, when one more scan, all it's going to get you is a little bit here and a little bit here. So you're not getting a whole lot of bang for your buck once you start adding more scans in.

      So more is not always better. You're increasing file size. You're increasing time and cost just to get that wall plane, right there, which you probably could establish from that wall plane there and there. So stuff to think about when you're scanning and also when you're commissioning a scan.

      So the requirements of a scan project are going to be the scope. I've gotten such very vague things before, that it's crazy to answer. There's a foundry in Wisconsin, a metal foundry that makes kitchen and bath fixtures. How long would it take to scan it?

      Well, that's a pretty open-ended question. What do you need to scan? Do you need to see every bit, the roof, the ceiling, the walls, the site? You're going to need a lot of information. You're going to need to really define the scope down to what exactly needs to be scanned.

      Color data, very important, takes a lot of time. The resolution of the scan? Do you need to just establish the wall planes and the ceiling plans for dimensional data? Or do you need to capture the detail in the molding here for some sort of restoration? That's going to factor into the resolution of the scan.

      The detail there is the same as it is over there. So if you just got a high res of this area, one can assume the rest of it's the same. So knowing a lot about the project helps.

      Does it need to be geo-referenced? So if you had a scanner that was also a total station, you can do that all in one. If not, you're going to have to have some targets set or set your own targets and scan them and then reference them in, somehow, either after the fact, with your point cloud. So someone's going to have to set some control for you or pick up some control that you set, however way you want to do it.

      AUDIENCE: Do the objects you scan have to be [INAUDIBLE]?

      LUKE PEDERSON: Yeah. So what I do is I put out targets, paper targets, so checkerboards. And what I do is I set up-- like I just did a sand mine that we need to geo-reference, because we reference it into the zero-plane and calculate our volumes.

      I had a surveyor out there, because we need two people on the mine, anyways, on a mine site. So I set a target on the ground, right next to my scanner, so my scanner can very clearly see it. And then he shot it in with the GPS. He pulled his rod up. I hit Go on the scanner, and it scanned it. And then after I was done, then I used those points to line up to his control that he gave me.

      There's ways to do that automated, or there's ways that you can just bring it into Civil 3D and just say, this point goes here, this point goes here, and just do it that way, too. There's a couple of ways of doing it.

      And then after the scanning is done, the level of modeling afterwards, that is huge. Do need to model at all? Do you just need to know if something fits in there? Maybe you don't need the model at all. That's the easiest. You just put your new thing into the laser, the point cloud, and if it fits, it fits. If not, you tell them that you're going to have to move the pipe or make the door bigger or whatever.

      Or do you need to model the entire thing? Do you need to go in there, all the walls, all the ceiling, all the molding, everything about it, pipes, electrical conduits? A huge range, you need to know that. Because people will get really mad if you spend way more time modeling than you need to and blow their budgets.

      Laser scanning limitations-- it's not without them. Laser scanner cannot see through water. If you're lucky, maybe it can. But I wouldn't trust the results. There's refraction in there. Same thing through windows. It does a pretty good job of seeing through windows, sometimes. But I wouldn't trust that, because there is a bit of refraction in the glass. So what's out there may be shifted enough to matter. I don't use it.

      Noisy areas-- if there's a lot of edges, if you've got a lot of little conduits. The worst example I saw is scanning through a chain link fence. All of those chain links are edges. And when a laser hits an edge, it can scatter points. And so if you have a lot of edges, you've got a lot of scattered points in space that aren't anything other than clutter and noise.

      Now, the new scanning software, processing software is getting really good with removing that. So hopefully, in the future, that's not as bad or as much of a problem.

      Laser scanner is limited to line-of-sight. It cannot see through walls. You can't go in a basement and tell how thick the foundation wall is just by scanning the inside. It's not an x-ray. It's just a laser. You can't tell how the footing is. You can't tell how thick the slab is.

      Shiny surfaces-- I did where there was like a milk truck, a real shiny, round milk truck, in a garage. You got all kinds of crazy results off it. Basically, it's a curved mirror. It's like a funhouse mirror. So you get weird curves off of that.

      If you're scanning, maybe, a hotel room, every hotel room has mirrors. Maybe you want to hang a sheet up over each one of those mirrors, because you're going to get some weird results. I would rather see a sheet hanging on the wall in a point cloud than having to clean up a point cloud with all this mirror data in places where it's not supposed to be.

      Shiny surfaces or a wet floor is the same thing. If you go into a factory, and they need a lot of data about the floor, and the floor is all wet, that's a problem. Because it won't see. The laser reflects off. And it just doesn't bring back data off of a wet floor. Even a damp floor, it just has a real problem with it.

      And moving objects, of course, it'll scan them. Traffic, people whatever, It'll scan them. Moving objects are a problem. If something moves through the scan, that's fine. It'll just have a little stripe of data. It's best if they just move through fast.

      So if people come in there, and they say, can I walk through, I just say, sure, just go through fast, though. Step through the scanner. It got a couple stripes of them. Big deal. But if they take their forklift, and they come up and park it right in front of you, it's stop, start over.

      Anybody have any questions on laser scanning? That's as far as I'm going to go on laser scanning. It's important to know, because some of you may be doing it. Maybe you're new at it. Or you're going to commission it. So if you're commissioning it, I think it's really good that you understand what goes into it. It will help you tell the people what they need to do to get you what you need and not under budget or overcharge you for what you need.

      Any questions at all on that?

      AUDIENCE: What kind of time restraints do you have for long time in the field versus processing data in the office? And just end-to-end, ready to take it to the next like you're about to do?

      LUKE PEDERSON: Yeah, that's a good one. To take it, from the laser scanning, to the point where I'm going to bring it into Revit, it's one-to-one. If I'm out there for eight hours, I'm inside processing for eight hours. On average, that holds true. And I sat through another class, here, recently, and that's exactly what they said, too. So it seems to me pretty standardized. But yeah, so one-to-one. Yes?

      AUDIENCE: Is that with the automatic registration?

      LUKE PEDERSON: On average. Automatic, if it's fully targeted, yeah, it's a little better.

      AUDIENCE: So that doesn't apply with laser scans, so I don't use targets. I do manual. And I probably average 20%, 25%.

      LUKE PEDERSON: Yeah. So I just did a sand mine. It was way over one-to-one. It was like three-to-one, all cloud-to-cloud, big files. If I know every single scan is tied together with four targets, and all I have to do is bring it in, load it, hit Register, it's like, yeah, quarter-to-one.

      AUDIENCE: I guess it just depends on the size, right?

      LUKE PEDERSON: It depends on the size.

      AUDIENCE: Because if I did lots of scans in a room like this, there being partitions all over the place, I'd take four scans in this room. And if I end up having 300 scans, I could do 40 scans a day. And then 20% of that, so I'd say five days of scanning, one day of register.

      LUKE PEDERSON: And if it's all targeted, I would agree with that.

      AUDIENCE: No targets.

      LUKE PEDERSON: Oh, with no targets? How do you--

      AUDIENCE: Manual registration.

      LUKE PEDERSON: Manual registration, yeah.

      AUDIENCE: And I thought that was long. I thought, I want to use targets to get rid of that. But it doesn't sound like that's going to be the case.

      LUKE PEDERSON: No. Because there's still a certain amount of overhead loading the data in, recognizing the data. The computer grinds away. Even if it's not registering things, it still grinds away just loading them in and doing whatever it does. I don't know what it does, but it does stuff. It makes heat is what it does. Yeah?

      AUDIENCE: What are your best practices for outdoor scans-- sunlight?

      LUKE PEDERSON: Oh, nowadays, modern lasers, they're unaffected by light for the most part. You can scan on a bright, sunny day. You can scan in the complete blackness of the interior of a tank. The laser is its own light. So just like it sees what it reflects. It's not on the same wavelength as the sun, so outside it's fine. If you're inside with no light, basically, it's own light. Is that what you meant?

      AUDIENCE: Yes.

      LUKE PEDERSON: OK.

      AUDIENCE: So I work on a reservation. So we meet as a team and do the same site.

      LUKE PEDERSON: Yes.

      AUDIENCE: So there's just quite a bit of using geo-reference to scan the exact same location, terrain, exterior data. What are our methods for returning the year after?

      LUKE PEDERSON: Yeah. So there's a couple ways. You can put out geo-referenced shot in with GPS or survey control. You can put it out there and hope no one messes with it and just do that again. Or if it's survey control, I guess, you can put new ones, and just bring it into the same space.

      If you don't have survey control, there's ways of putting permanent targets up. Like if you trust the people, you can tape up a target, really good, and say, don't touch that. And make sure they don't touch it.

      Or you can screw these things into the wall, so when you come back, you can stick your magnetic balls that you have for registration. They'll go right back in the same place. And that's kind of relative.

      There's ways to do it. Most of it involves not messing with your control. And hopefully, you can trust the people on site not to do that, because it can be a problem.

      Moving on here. Check my time.

      The raw scan import-- so here we are. We've got the laser scan. Someone gave you a raw file type. Maybe they reprocessed in ReCap, and so you're already passed the raw point.

      Whoops, the wrong button.

      Maybe you're already passed this point, because ReCap will give you this, right away. But if you've got some sort of raw file, you're going to be up here. So we need to get down to this point. It's very easy to do. But you need to know how to do it.

      And there's many types of raw scan files. And we're just going to talk about the E57 now, because, as long as ReCap can read the raw scan files, which there's a bunch of them, the process is still the same.

      So what Revit does, when you bring in a raw file, it converts it. You can do this in ReCap, too, but Revit does it internally. I think it just runs ReCap behind the scenes.

      So you take one raw scan file. This is your whole point cloud. It grinds away on it, make some heat, and then it spits out a bunch of files. And these are your individual scans. In this case, there was eight of them. So this pile of data is all your scans, seven million points, seven million, blah, blah, blah, over and over again. Huge file size.

      It's all tied together with one RCP file, very small file size but important file. So ReCap is looking to load this, which then, in turn, grabs all these, puts them in the right spatial data, and brings it in your project for you.

      There is a chance, if you just had one or if it was processed so that it is all unified together, you can just bring in one scan. So a ReCap will load one of these. But in most cases, I load one of these, which, in turn, grabs the rest of these. Does that makes sense? Questions? Wrong way.

      So what we're going to do is we're going to import the E57 file. Now, this is my first time doing a class here at AU. And I'm a glutton for punishment. I'm going to do a live demo. I hope this goes good. Everything's staged and set up. And it's gone good for me so far.

      So what we're going to do is we're going to import the E57 files, and we're going to convert them. It's that first process there, that we talked about. So we go over to Revit, here. And my mouse, of course, isn't working. Let me get the right file up here. That one.

      So what Revit is wanting you to do is import that E57 file. And it's not like importing anything else in Revit. You just go to the Insert, and you have lots of Insert options here, obviously Point Cloud is grayed-out here. That's a problem. It's because I'm in this view here.

      So you need to be in some sort of floor plan view, first of all. So you're going to insert the point cloud. In our case, we're looking for the E57 file. We're going to pretend that that's all we got. So you want to go down to a Raw Format. And these are all the raw formats that Revit can use. There's a whole bunch of them.

      E57 seems to be sort of like the DXF of the raw point cloud files. That's sort of a generic thing that people are settling on. I don't know how much that's true, but it seems to me that's what I see, mostly generic.

      So we're going to switch over to Raw. And this is what we're going to do. We're going to import that E57 file. And it's going to tell you, it's not indexed, which means it's not ready. Revit can't really read it. Would you like to convert it? Well, yeah, that's the point of doing this. So we're going to hit Yes.

      And it's just going to ask you where you want to put them. And so you find out where you want to put them. And you just use simple, best practices stuff for file management. And you hit Start Indexing. I'm not going to do that now, because that's going to take a bit of time grinding away on the computer. But you have to trust me that it'll work.

      It's just going to give you this little green status bar, and it's going to tell you how things are going. But it's also going to switch over, down here, and ask you if you want to close this window. Because what's nice about Revit is it will do this behind the scenes. And it'll just give you like a little thing, down here, telling you that it's happening behind the scenes. But you can continue doing something else while this is happening.

      And then, when it's done, it just is done. It quietly finishes. And you never notice the difference, other than, I think, a little pop-up window comes down here and says, it's done. But it doesn't insert it. It doesn't do anything. It just finishes, which is kind of weird. Because I wanted to insert it.

      I'm just getting out of this. So we pretend that's what we did. I'm not going to do it, because it does take a while of grinding on the computer. So kind of counter-intuitively, we're going to have to come back in here and do the exact same thing as we did before.

      So we're going to insert the point cloud. But we already converted that E57. We don't want to do the same thing again. What Revit did is it went in there, and it created all these files for us. And in my case, I told them to put them here, Point Cloud files, files-- here they are.

      These are all the RCS files that it created. And this is the one RCP file. Notice the file sizes. Each of the scans are huge. This is where all the data is. This is the little file that just ties all these together. This is the guy we're looking for, right here, in this particular case, the one RCP file.

      So you go down here and change it to RCP. If you indeed just had one scan, you would change that to an RCS file. But in most cases, it's going to be an RCP. And you insert it.

      Whoops. Let me back out. I wanted to show you one thing first. Let me make sure I didn't insert that. Yep, it's not there. So Point Cloud, Insert, that one down here, Auto Center to Center. There's three ways of inserting it, just like a lot of reference files, Center to Center, Origin to Origin, and By Shared Coordinates.

      Center to Center makes the geometric center of your point cloud, that's the 3D center, and it will put it on the 2D center of your floor plan. So it's going to be centered in the center of your floor plan. But you don't know where it's going to be in the z-location.

      The reason I say, you don't know where it's going to be, is because, if you have a point, way off in space that I grabbed, it's going to throw this thing in a kind of weird 3D space. It's good to know going in.

      Origin to Origin, I don't really use, because I don't know where the origin is on mine, for the most part, unless I use control. And I don't really use control a whole lot in Revit. There's ways of doing that. Most of the time, what I do, I don't really care where it is geographically. I just need it to be in my model.

      So for me, most of the time, Center to Center works good. And you hit Open. And it put it in there. Doesn't look like a whole lot. That's because it threw it into some z-location somewhere. It's probably way in the background or way in the foreground. I don't know.

      So the best thing to do is just go to an elevation and find it. There it is, way down there. So this particular scan is a vault. It's a valve vault. It's mostly underground. So the valve vault has a floor on it. That floor has a thickness. Below that, it's got a grading deck some number of feet down. We'll get to that. And below that, it's got a sump in it. So there's kind of three levels that I care about.

      So I look at this point cloud here. And this is a little trick. And this goes for any reference files. Does everybody know about this, this little guy, here, in the corner? You turn that on and turn that off.

      If it's without the x, every time you hover on a reference file, it turns purple like that. Really bad in a point cloud, because there's points all over the place. And it's constantly, doo, doo, doo, turning on and off on you. It's really annoying. So I'm always flipping back and forth. Unless I want to do something with the point cloud, like actually move it, I leave that off.

      But we do want to move it in this case. So what I'm just going to do is I'm just going to move this point cloud up to the correct or some correct z-location, right about there. Good enough for what I want to do. Let me get my mouse back here. Yeah?

      AUDIENCE: Did you use any kind of reduction in the number of points?

      LUKE PEDERSON: Yeah, so that's another thing you can do out of ReCap or out of your point cloud software or your point called processing software. You can decimate it. And a lot of what I do, I highly decimate it. Because it really brings that file size down.

      And especially if you're just establishing centerline geometry of pipes and walls and things like that, you can really decimate it and bring the performance up a lot in it. Makes the file sizes a lot smaller. Yeah, I meant to mention that, so thanks.

      So I'm just going to put it here, in space. So Level 2 cuts through sort of that vault area. So we're going to go down to Level 2. Actually, I skipped ahead of myself a little bit. So I want to go back to here.

      So basically, that's the import of them. Anybody have any questions on actually getting it and converting it? Yeah.

      AUDIENCE: When you first brought in your first set of scans and started looking at it, you suddenly realize that you forgot to walk around the corner and scan the piece that you're missing.

      LUKE PEDERSON: Yes.

      AUDIENCE: Can you now come in and insert just that new, one, fresh scan?

      LUKE PEDERSON: Yeah, I can. And I can't do it targeted, because the targets, from the previous scans, are gone. Well, maybe they're there. But chances are, they're gone. But I can do cloud-to-cloud for that one.

      As long as I know where I scanned before to get enough, so I brought it in, yeah. But I would have to reprocess it. You'd have to redo all the processing and then re-bring it back into Revit.

      AUDIENCE: But not the other seven?

      LUKE PEDERSON: Not the other seven. Yeah, you can leave them. And you can actually lock them and say, you're good, just bring this one in.

      AUDIENCE: Plug it in.

      LUKE PEDERSON: Yep, then re-export it, do your little thing that we just did, and then you're ready to go again. Yes. So the next part we're going to talk about is actually, now that we have it converted, we bring it in. I got a little bit ahead of myself, but, either way, my mouse is back again.

      Or not? What is the deal with this mouse? USB not recognized. Does anybody have a wired mouse with them, anybody, anybody?

      AUDIENCE: [INAUDIBLE]

      LUKE PEDERSON: Maybe that's what it is. I don't know. Anyway, we'll do it this way.

      So we brought it in. Here's that point cloud. It's in some sort of space. Oh, wired, yeah, perfect. Remind me to come get it back from you when you're done. My little USB thing got hit, so it got knocked off. I think it's got a short in it.

      Revit's way easier to use not with a track-pad. If you've ever tried to use Revit with a track-pad, when you forget your mouse, it's pretty impossible to use. There we go. Mouse came to life.

      So we're going to move. So we have our laser scan here and our floor. So what we need to do now is we've got it sort of into, generally, the right z-elevation. So we're going to throw a section in here.

      And what I like to do with all of my laser scans-- here's the difference. If you look too deep in that section, and we go to this section, here, you will find that that's just a blob of data. It's sort of meaningless. It's just hard on the eyes. I'm going to turn that off. See, so now when I don't hover above it, it doesn't keep turning purple.

      It's hard on the eyes. I can't clearly see the top of that roof or the top of that ceiling. And I can't clear. There's just a lot of clutter in there. So what I like to do, when working with point clouds, when modeling with them and especially when aligning them, is I make an ultra thin section.

      Can you all see how thin that is? That's probably only a couple inches thin. What that allows me to do is clearly see that roof plane and ceiling and that floor grating. It's just grating at this point. The ground really isn't that fuzzy. This is actually grating that you're walking on.

      So like I said before, there's three levels in here. There's a ceiling, this, and then something below this grating that the scanner couldn't pick up, because it couldn't see through that grating, at an angle, very good. So I'm going to want to put this up on Level 3.

      So Activate Scan again. And it's as simple as moving the scanner. And you notice I can't snap to it. That's because earlier, I turned off-- if you go into Manage, Snaps, there's this hidden one, right down here, Snap to Point Cloud. Turn that thing on. You can turn it on and off. And there's times where you want to turn it off. But right now, we want it on.

      So we're going to move that point cloud from the top of that ceiling. We're going to move it right up to Level 3, here, we'll call it. So that's at 116. Doesn't really matter where we're at now. So you can measure right in point clouds. And since we can snap to them, I can measure how high that is down to there.

      It's 10 feet 11 and 213/256 of an inch. Do you really want to make it that dimension? I hope not. Because that would be a math nightmare all the time. Sometimes you might.

      I just sat through a class, here, where they were scanning ancient buildings. I guarantee the ancient people didn't have any kind of standardized measurements that they did. I would assume you're going to have to deal with these weird fractions.

      But for the most part, this is where I get into intent versus accuracy. The intent there was probably-- and I forgot what the measurement was. The intent was probably 11 feet. Would we all agree with that/ So 116 minus 11 is 105, boom. That level moves down there. That's close enough for what I need to do.

      A lot of times, in modeling, with point clouds, close enough. You're going to drive yourself insane if you try to make everything exactly right on, because it won't be. The contractors, in the real world, nothing got made exactly right. Yes?

      AUDIENCE: For that, the snap to point cloud, is that in Edit?

      LUKE PEDERSON: Is that what?

      AUDIENCE: Was that inside of Edit, too?

      LUKE PEDERSON: It was in Manage. And then it's just all of your general snaps in Revit. It's just one of the choices you have down here. It's a little bit out of the normal ones, so just look down here. Snap to Remote Objects, I'm not quite sure what that is. But Snap to Point Clouds is the one we're looking for.

      The reason why we'd want to turn that off-- and we'll go over that in a bit here-- is when they start modeling architectural stuff. And you're near your walls, your point cloud walls, it's going to snap, doo, doo, doo, doo, doo, doo, over here and here and here and here. And you're going to be making walls at half-degree angles and all kinds of weird dimensions. So you want to turn that off.

      I don't know what that lower level is, so we're just going to leave that for now. But basically, that's how you get it into some sort of space. We brought it in. We moved it up to some z-elevation that worked, then we went back. We cut a thin section. And we moved it to the exact z-elevation that we wanted.

      Now, if this was an actual MSL elevation we wanted to move it from, you could set these up pre and move it in there. Or you could do it afterwards. Like this is probably 1,000-some feet, in Minnesota, where this is at. I can just move the whole project up 900-and-some feet, whatever it needs to be. However you want to do it to get it to where you need it in the end.

      But you need to start somewhere. And then you start setting in your elevations. But that's kind of visual. You measure. You round, normalize your dimensions. And then you start setting your elevations. There's nothing above this, so I won't do it.

      Sometimes, when you bring a point cloud in, either because that's how it is or because that's how it got scanned, it's going to sit like that. I am not going to draw a plan of this thing at some weird angle like that. I mean if part of the building is, so be it.

      But I think we can all agree, we'd probably rotate are things to fit on the plan right. So a lot of times, it might come in like that. Or it might come in just slightly out of skew, where you just want to make sure that it's straight.

      So what I do here is-- this is just sort of normal Revit stuff. We're going to go in here. We'll make a reference plane, from there to there. And that establishes our horizontal alignment, I guess. So we're just going to move the Revit.

      And since we have those snaps on, we can snap to any one of these points here, millions of points to snap to. We're just going to move that right up there. Zoom in a bit, activate that, rotate. And we're going to place our point of rotation right on there.

      You click up to your wall, where you feel that the wall's plane is. This is best to reach your points out as far as you can, because, if you're aligning something up with two points, really close, the chance for error is a lot. So you want to get your points kind of far apart here.

      I would even do this, probably, way down here, my original point. So rotate that right down onto the reference plane. And there, we're lined up. It's a visual thing. Walls, in the real world, aren't exactly 90 degree angles to one another, either by accident or on purpose. So this is project-specific. Do what you need to do to line this thing up right. Yes?

      AUDIENCE: Normally, what we do, too, is we'll try to align it up and try to find a happy medium between that cluster--

      LUKE PEDERSON: Yeah.

      AUDIENCE: --right in the middle. That way it's easier overall.

      LUKE PEDERSON: What I do, since I scan, I process the scans, and I use my own scans, I do that, actually, beforehand. I process them. I pick a flat plane on a wall, and I say that is north. And it moves it in. So when I bring it in there, it's brought in square, already, based off of a flat plane.

      So if you're the one doing it all, like me, save yourself some time and do it that way. But you never know what you're going to get, so you might get something crooked. That's how you fix it.

      AUDIENCE: Do you do that in ReCap?

      LUKE PEDERSON: I don't use ReCap for processing, but I assume you can.

      AUDIENCE: Yes.

      LUKE PEDERSON: You can? OK. But basically, I just say, this plane is east. Spins it all. I don't know if that's east or not. So that's really about it for that.

      So we brought it in. We aligned it vertically. We set our levels. We spun it if it needed to be spun. Now we are ready to start modeling architectural elements. So anybody have any questions on that at all? If not, I'm going to move on here to, we're ready to start modeling but first. There's a whole lot of buts, here, to get set up.

      The point cloud is now a large, visual data set that's aligned in your model. It's a big blob of points that's really hard to-- I mean, it looks great from afar. You can see everything in there. It looks great. But if you really need to get inside the building, it is a mess of visual data that your eyes and our human brain will not make sense out of.

      So we need to know how to deal with it first. We're going to set up some shallow views. We're going to set up some sections to help us visualize it. This is kind of just standard Revit stuff. But it's a little bit more extreme than you would do with a model.

      So Architectural, this is the one I want to start with. So what we have here is you brought it in. And I'm going to turn that off. No, I don't want to save the project. There we go.

      You brought it in. And here's a floor plan. That's exactly right. That's how it looks. But there's so much stuff going on there, that it's so hard to see. You got the floor in the background. You've got some stuff in the foreground.

      I can't tell, exactly, where the wall is. I mean maybe you could, but it's really hard to tell. So what we're going to do is to start architecturally modeling this. I like to set up some really shallow views.

      Pick a spot that works for your building, four feet off the ground, three feet off the ground, a thin slice through that building to establish the perimeter walls. Again, each building's going to be a bit different from one another.

      But if we do a two-foot wide section through the building, from four feet down to two feet, and we hit Apply, you can start to see the perimeter of that building. It's still a little bit fuzzy up in this area. Maybe it's good enough to work.

      So we'll try 3.5. That's a six-inch thin section through there. That's pretty crisp. I can pretty much see those lines there. If we were doing some piping near the ceiling, you might want to expand that section, move it up to catch that piping up there.

      This is from eight feet down to three feet and everything in between. If we want to isolate some of this piping, maybe you want to only see eight feet to six feet, that helps isolate some of that piping from the background clutter. So you can clearly see what's going on there. That's just some best practices.

      Same thing in sections, you got a section that's impossible to see anything in that. So if you go to this section, and you're doing architectural modeling, we'll pull that right back to here. Ultra-thin, way thinner than you would use, probably, in a Revit model, but it does the job here.

      Well, we're cut through a beam on that point. But let me move that out of here. There you go.

      You can clearly see the thickness of the floors here. You can see the interior wall planes. Remember, laser scanners can't see through foundations, so we're missing a line out here. It's because it's underground.

      I'm going to go here. Same thing, a really thin section, pull that back, so we're looking right there, a real thin section through there. Look at that floor, down there, in the basement. It's got quite a slope. Where do you want to set 0 or whatever you're calling your base floor? That's up to you. There really is no right answer.

      Do you set it at the crown of the slope? Do you set it at the edge? Do you set it down in the trench drains? So there's a trench drain around this building. That's up to you.

      I elected to set it, because that's usually how they define it, the floor elevation on the perimeter, with the high point in the middle. The high point isn't representative of the actual floor elevation. It's kind of the perimeter. So that's what I did. It's up to you.

      The dimensions sort of made sense when I went and measured it. I measured from here to the high point. It was some really weird dimension. I measured from the low point of the floor to there. It was 10 feet 8". That probably was the intent. So that's what I went with.

      Some of these intermediate floors, the slabs are much flatter. So it all worked out well. I use decimal elevations. I do water, wastewater, so I work in that. Use whatever you want.

      And then 3D views, they help. They're pretty. I'm sure you all know, but I'll go over it. I mean, you can't see through the inside of it. So if you want a section box, if you want to clip that in, you can just click that button, right there, and activate your cube there, your View Cube, pull that in. And you can see into the building.

      If you unclick it and then click it again, Apply. Whoops, Unclick, Apply, it goes away. Click it again, it comes back to the extents of your point cloud. If you wanted to make it a section that was a cropped 3D view that was preloaded to your view cube, you can just go click on that View Cube there, Right Click, Orient View, to Sections, pick your Section. There, it preloads a 3D view exactly to that section. A couple of ways of doing it.

      I use the 3D views in the point clouds to help orientate myself, visually. I don't model in 3D. You're going to end up with results all over the place if you do it that way. I just use it to try and figure out how stuff relates to one another. It just helps me.

      Any questions on that? So we are at the point to start modeling now. All that stuff to go into just to get into the point of modeling. Any questions at all? I'm going to go right into the-- were you going to say something?

      AUDIENCE: Do you find it better to do all of your view states in Revit or to capture different view states with cropping [INAUDIBLE] and then enable that same cloud?

      LUKE PEDERSON: So if you have a really big point cloud, you might want to do it in sections. I've loaded some really big ones into Revit. I don't know. Does anybody have any experience with a really large file, large point clouds in Revit? They behave pretty good.

      AUDIENCE: Yeah. We also use-- we also have FARO. And FARO also [INAUDIBLE].

      LUKE PEDERSON: Yeah.

      AUDIENCE: And it actually defines half of what you did. You can run them parallel, and then the points, then register, and all the modeling in Revit.

      LUKE PEDERSON: Right. So that's a good point here. What I'm doing? This is like your basic toolkit stuff. Not everybody has some of these tools. If you go into the expo center, there's some vendors that will love to sell you some automated software to do a lot of what we did here. They work great when they work. When they don't work, you're going to have to do it this way.

      In this example, when we get into the piping, I'm going to show you why their piping tools would absolutely fail on this. They work great a lot of times. But they're not going to work real well for this. So you're going to have to at least know how to do it manually.

      But yeah, some of this stuff is automated. There's tools to do it. Not everybody has those tools. And those tools don't work sometimes. With big point clouds, yes, I have broken them up before and loaded them piecemeal. Sometimes I do the outside of the building, and sometimes I do the inside of the building. It just depends. You can do it.

      So now we're ready to start modeling architectural and structural items first. Anybody have a problem with that? That's the way I normally do it. I start with the building, if I need to model the building, which isn't the case all the time.

      We're going to set some reference planes to define our walls. This is not unlike modeling with existing, as-built plans sitting next to you or a bunch of scribbled dimensions. The only thing we're doing is we're tracing a 3D photograph.

      If you're doing this, and you need to explain what you're doing to people that don't know anything about point clouds or Revit or models or anything, it's very good to get a speech ready about how a point cloud is not a model.

      Just because you went out there and set up your scanner, that doesn't mean you have a 3D model ready to go. A scanner doesn't know a pipe. It doesn't know wall it's just a point in space.

      So the scans just bring you to the point of an as-built set of plans, field notes, pictures, whatever. It brings you to that point. You have a very good, all-encompassing reference that is almost everything you need to do to model that building, down to outlets and electrical conduits and faucets, and whatever you need to do. But it is not the model.

      So figure out the best way to explain that, to who you need to explain it to, and have that speech rehearsed. Because I use that a lot, at first, when we first introduced 3D laser scanning.

      So I'm going to try and quickly go through this stuff here. Architectural model, Floor Level 1. Whoops, that's the complete one. This is like a cooking show. I have it all done in the end. We're going to do a little bit, and then we're going to look at it in the end.

      So 2, we want to go to 2, Level 1. So here we go. We brought it in. We got a thin slice through this building here. So what we're going to do is just draw some reference planes. This is just your kind of best practices Revit modeling. Since I have snaps turned on to the point cloud, I can snap to the point cloud.

      There we go. And that defines the interior surface of that wall. That defines the interior surface of that wall. And I have very limited room for my mouse, up here, so I'm usually not this fumbly drawing. Well, I missed a couple of reference planes. Sorry, there.

      So you have these set up. I guess that one is there. So this reference plane-- and we're going to turn that and do a dimension, slide it out here, so we can all read it.

      Intent versus accuracy-- would you model that at 20 feet and 15/16 of an inch? I would hope not. Same thing with this one. This one is probably going to be 30 feet. It's just under 30 feet. It's 29 feet, 11 and some fraction of an inch.

      So what I do is I draw my reference planes. And I look at that. And I say that is now 30 feet. And this one is now-- if I click on it right. I got to click on that. This is now 20 feet not 2. And that's how I start.

      Then you may need to recenter. See how this got off a little bit here. You may need to readjust. Sometimes, you're just not going to be on the wall. And you have to figure out either, do you live with really weird dimensions, or do you live with it? Like this wall here might bow out a little bit or be a little off plumb in the particular stripe that we're looking at there. Very project specific--

      But you go in here, and then it's just best practices. We've got a wall. How thick is that wall? I don't from an interior. If this was an above-grade, you could see the thickness of the wall, because you'd have the outside scans and the inside scans. And you can measure it right there.

      From a foundation, it's a little hard. Because the outside is buried. I have no idea how thick that is. I do know, because I scanned this, that the outside of the foundation lined up with the outside of the exterior architectural wall above.

      So I just draw a plane in there. And there it is. It's at 1 feet, 19/64 of an inch. We're going to call it a 12-inch wall. And so you go in here, in your wall, and you set it up, 12-inch concrete wall. And it's a certain height. This particular one, it's going to go from Level 1 all the way up to Level 3-- again, super project specific.

      And then you just start. Now, here's where I go and turn off that point cloud. Because, if you saw there, when I tried to draw a wall from there, it's snapping to those points. And you're going to end up with some really crazy results if you're snapping to, potentially, millions of points.

      You're going to end up with walls at weird angles and weird dimensions off of your reference planes. So just remember, Manage, Snaps, Snap to Point Cloud, just turn it off in this case. And we're off and running.

      It was 30 feet over. I'm drawing it inside-out. But you guys get the idea, right? This is just Revit stuff from here on out. It's basically setting up the views. I go in here, and I set up a foundation slab, the same thing.

      There's no way to know. Other than an as-built set of plans, there's no way to know the thickness of that foundation slab. So you're just going to have to guess. If it matters, you're going to have to do whatever method you need to do to figure out how thick that foundation slab is.

      Columns, the same thing. You can measure your columns with this thin slice here. I know that that column is nominally 12 inches square. So you bring your column in there, and you do what you need to do to make the correct column, in this case, a 12-inch square concrete column. And you put it in there, and you line it up with reference planes.

      Same thing you do instead of referring to notes and as-builts, you're referring to the reality that you captured here. Regardless of how accurate your notes are, the condition, existence, or accuracy of your as-builts, this is how it is. There's not a lot to argue about here.

      With piping, they're notoriously changing over time. This building was built in 1954 according to the data plate on the outside of the building. Guarantee, this piping is not the same from the 1954 as-builts to now. I'm going to trust this.

      The next step is modeling some floors. Kind of a neat trick in modeling a floor here. I'm going to go to the second level floor. Because you want to see the floor to model it. I know that it has a hatch through it. And I know that has a stairwell through it.

      So if I go to the View Range, and I go from two feet above the floor to three inches past the floor, Apply. Whoops, three inches past the floor, negative three inches. It's pretty hard to read.

      I know there's a hatch there. You can kind of see it, right? I know there's a stairwell cut through the floor. You can kind of see it. I can't really define the edges. There's something in the way.

      What I like to do is I like to go a thin slice down into the floor, so we're actually going to start at negative 1 inch. And we're going to look down into the floor, two inches. So we're looking at a thin slice of the floor. Since I scanned below it, what we're actually going to see, here, now is the boundaries, the inside face of those vertical cuts through the concrete, the vertical shaft through the concrete.

      So I can very clearly see my floor penetrations here. Draw my reference planes, put my floor in there, trim out, whatever you need to do. If you have a floor hatch, they'll cut its own. And you put that in there. However you want to put your holes through your floor, with shafts or by manual, whatever.

      Anybody have any questions on architectural modeling?

      AUDIENCE: Why do you use so many reference points [INAUDIBLE]?

      LUKE PEDERSON: Just because that's what I do. Yeah. I could go in there. This is a very simple building. I could just have measured that and said, that's a 20 by 30 building. And that's where it starts. And I could go 30 over and 20 down, 30 back, whatever, do it that way.

      But if it's a very complex building, that's a lot of measuring, going to the wall, doing it, measuring, going to the wall and do it. If you just trace it out with the reference planes, and then-- actually, if you go one step further, then, and just turn off your point cloud, unreference it-- don't unload it, unreference it-- then all you see is your reference planes. And you just trace it, doo, doo, doo, doo. That's just how I do it.

      AUDIENCE: Or a grid line.

      LUKE PEDERSON: Or grid lines. I'm not an architect. I don't do that sort of stuff. I give it to them, and then they set all that up in the end. Yes?

      AUDIENCE: Just as a practice, is there a difference between unreferencing it and just closing it?

      LUKE PEDERSON: No, I don't think so. There's three things, too. So if you want to turn off that point cloud, if you don't want to see it, at this point in time, you can go over here. You can hover above it. You can do that, Hide in View by Elements, and it will turn off.

      And to turn it back on, you kind of got to go here. If that's off, you have to turn that, again, on. Go here, Unhide Elements, and you get it there. I don't know. That's one way of doing it. Or you can just do Manage-- not Manage-- Insert, Manage Links, Point Clouds, then you click on here and just say, Unload. This unloads it from all views versus one view.

      Don't remove it. Because if you remove it, it's gone. And its spatial data is gone. And you will have to get that back in and have to eyeball it all up. So whatever you do, don't remove it until you really want to remove it at the end. Yes?

      AUDIENCE: I go through [INAUDIBLE]. Just

      LUKE PEDERSON: Adding a what?

      AUDIENCE: Adding to the [INAUDIBLE].

      LUKE PEDERSON: OK, sure.

      AUDIENCE: And then completely turning it off until [INAUDIBLE].

      LUKE PEDERSON: Yep. Like all of Autodesk products, AutoCAD, Revit, whatever, there's lots of ways of doing the same thing. Yes?

      AUDIENCE: So when you bring it in that very first time, is it similar to bringing in like a CAD file?

      LUKE PEDERSON: Exactly the same.

      AUDIENCE: --just this one view?

      LUKE PEDERSON: Oh, can you say to bring it in just to one view?

      AUDIENCE: If you bring in a CAD file, there's actually, when you import it, it allows you to bring it to just this one view.

      LUKE PEDERSON: I don't think so. I don't think that was an option in here. So Point Cloud-- yeah, here's our options, right here. I don't think so. I think it's global. If you Hide from View--

      AUDIENCE: You're only hiding that one--

      LUKE PEDERSON: You're hiding it in that one view. That's the reason why you might want to do it that way. If you turn it off, that's like, I'm kind of done with this point cloud now, but I don't want to commit to removing it. So you just turn it off in every view at once. Yeah, there's reasons to do it, one versus the other.

      AUDIENCE: You can also do it with a temporary view.

      LUKE PEDERSON: Yep, lots of ways.

      AUDIENCE: It just gives the same thing.

      LUKE PEDERSON: Exactly. Yes? Two of them.

      AUDIENCE: I was going to say, [INAUDIBLE] coordinating with point files, so it's only visible [INAUDIBLE].

      LUKE PEDERSON: Yes.

      AUDIENCE: Kind of like working views for this purpose. But then it doesn't show up. [INAUDIBLE]

      LUKE PEDERSON: It's like in AutoCAD, how many ways are there to draw a line? You can type in L, LI, and do this and that. Lots of ways of doing it. Yep.

      AUDIENCE: We use the work stuff. But keep in mind, if you have multiple models, architectural, mechanical, and all that, if that's in the architectural, any time you link to the architectural, it shows up in that model.

      LUKE PEDERSON: As long as they have a valid path to that reference.

      AUDIENCE: Correct. The easy way to fix that is to set up a point cloud work set. Everybody makes it the same, and you default it off. And you can see the models that are on it.

      LUKE PEDERSON: Right. Which reminds me of something, little off-topic, but I wanted to mention it. My point cloud files, my way of doing it is I like to keep the point cloud files local on my machine. And if other people are using them, I like to keep them local on their machine.

      Loading gig, gig, two, three gigs of files over a network or over the internet, if you're working from home, impossible. So keep your current-- you're working on three projects that have them on there, sacrifice that hard drive space and keep a local copy or at least a local copy on an external hard drive that you can access quickly.

      What we do is we set up-- all of us have, on our C-drive, we have a folder that's named the same. So if the architect is in this office, he goes to C Local Point Cloud Files, and I go to C Local Point Cloud Files. Because if he calls his C Local Point Cloud Files For Temporary Use, and I call mine C Local Point Cloud, the paths are going to be broke, every time. And he'll switch them. And I'll switch them. And we'll constantly be fighting over them.

      So find a standard way to keep them local on your machine so the paths stay, the path is right. Don't use them over the network if you don't have to. It's hard.

      So architecturally, that's what I do. Any other questions? I'm going to go quickly into the process modeling here. It's looks like I'm running out of time. I didn't think I'd fill up 90 minutes but, boy.

      AUDIENCE: We're not your wife.

      LUKE PEDERSON: Yeah. Yeah, she just stood there. Any questions? No. You have no idea what I'm talking about, do you? Not really.

      So the process model-- how many people do process piping? I'm just interested. How many people do process piping in Revit? Oh, yeah, a few of us. Crazy idiosyncrasies with Revit, isn't it, trying to get process piping to work?

      It works. But you better know how to speak Revit really good to talk to it. There's a lot of tricks that we won't even get into here. But here is your nemesis in process piping, fitting on fitting. Doesn't work.

      I don't know if it'll ever work because of some reasons behind it with getting dimensions exactly right and fittings not being quite standardized. And it just won't work. I don't see it working in the foreseeable future.

      So the key to modeling, in a point cloud, in Revit, don't do your fitting on fittings in place. It won't work. It'll throw errors at you till you tear your hair out. Model off plane or off point cloud and move things back in when you're done.

      A lot of times, you'll get errors. If you have fitting on fitting, you've got a 90 in the 90 that bends like that, and you do something with this pipe over here, it will break that fitting on fitting. And then it won't heal it for you.

      So if you have that, a lot of times, don't join your fitting on fitting situations until you're done. Leave a little gap in there. And when you're all done messing with the piping, then go put all your fitting on fitting connections together.

      And that's just my helpful tip. It's sort of outside the scope of point clouds. That's just Revit in piping.

      AUDIENCE: [INAUDIBLE] for your pipes, could you use just raw data?

      LUKE PEDERSON: For our fittings?

      AUDIENCE: Yeah, your fittings.

      LUKE PEDERSON: We have out-of-the-box for some things. A lot of things, we have custom. Some valves, we have custom. We have wall pipes, which are like pipe fittings that go through a concrete wall. All of those are custom. Magnetic flow meters, all this stuff, we have libraries of custom stuff.

      But like the ductile iron flanged and the mechanical joint ductile iron fittings, they work pretty good out-of-the-box.

      AUDIENCE: I was wondering, because [INAUDIBLE].

      LUKE PEDERSON: Yeah.

      AUDIENCE: And that can be fitting to fitting. Or you [INAUDIBLE].

      LUKE PEDERSON: Yep.

      AUDIENCE: [INAUDIBLE]

      LUKE PEDERSON: Exactly. And that's what I wanted them to be into before. There's tools that help you do some of this stuff outside of it. Either some of us don't have those tools or those tools don't work sometimes.

      So you've got to know, when it keeps giving you that little orange box in the corner that says, cannot make that connection, and you're wondering, what the heck is going on, it's probably a fitting on fitting situation.

      So what I want to look at here is-- this is why. Are there any software people in here that sell the software that does all this automated stuff, which is great? But this is why, when I went down into this project to scan it-- I'm just going to look off the floor. Of four feet above the floor down to two feet above the floor.

      We'll go down here and look. We'll go one foot. There we go. Look at this, a fitting, a fitting, a fitting, fitting, fitting, fitting, fitting, fitting, valve, fitting, fitting, fitting, fitting, fitting. There's no pipe in there.

      [LAUGHTER]

      The automated pipe finding software-- well, there's no pipe to find. This is why you need to do it. I can't imagine. These pipefitters must have cursed those people not giving them any slack in here. You better have all these wall penetrations exactly right on, otherwise you're going to have some leaky pipes or some thick gaskets that you need to put in there.

      I don't mean to belittle the software. It works great. But there is certain situations where it won't work. And this is one of them that it won't work right. Were you pointing out how the pipe is not straight there?

      AUDIENCE: Yeah.

      LUKE PEDERSON: Yeah. Right. If you're really a type-A personality, you might want to find a different job. If you're working with point clouds in Revit, because you'll find--

      I was measuring a building, once, in a basement. And I was up here. How far is that? And we went into another view. i We come to find out the walls were out of plumb. So when you measure from a section cut up high, it's a different dimension as down low. It can drive you nuts.

      AUDIENCE: They actually do that on purpose now.

      LUKE PEDERSON: Yeah. So these aren't plumb or square with the walls. If you go up higher, you'll find pipe that isn't. Intent versus accuracy. I did one where I had to model it for somebody to bring it. And their sprinkler piping, which was just like two inch piping all through a huge warehouse, it was just like hanging rope. It just went up and down. Yes?

      AUDIENCE: So how far off, in reality, is that little piece right there?

      LUKE PEDERSON: Well, this is right on reality. I would never model something like that. I don't know how you would model something like that in Revit. Because Revit doesn't do pipe like that. I mean you can. If you really want to take the time to kink everything, but I don't want to do that.

      So what I did with that is I found kind of a best fit. Sometimes the sprinkler piping was below it, sometimes it was above it. I gave it to the client and said, your sprinkler piping is all over the place. It was for spatial. They needed to fit some equipment in there.

      I said, if you're clear within one pipe diameter, meaning, if you ever have something that gets within one pipe diameter of that particular pipe, you better field check it against my model. Because there's no way I'm going to model sprinkler piping that goes like that throughout the warehouse. Yes?

      AUDIENCE: [INAUDIBLE] or point cloud is a [INAUDIBLE].

      LUKE PEDERSON: It's possible.

      AUDIENCE: [INAUDIBLE] Because then you can just, you know, you may not need all of that to be able to do it.

      LUKE PEDERSON: Yeah. So you can use the point cloud as is. And I have used it as is. And that's one thing at the end. Does anybody want to go? I'm not going to go into it. I'm going to run short on time here.

      I'm not going to go into modeling piping. But the same thing applies. Your views, use cut views. You move them up. Thin sections work good with point clouds. They really work good. Don't look at your floor unless you have to. Don't look at beyond walls unless you have to.

      AUDIENCE: So we should just pick like, say, 10 by 6, and draw it like that and build a section like it?

      LUKE PEDERSON: Yeah.

      AUDIENCE: Do our best to connect the dots.

      LUKE PEDERSON: Right. That's what I do. It's all visual. And then I look at it. And then that pipe center line is 8 foot, 7 and 30-whatever, some crazy fraction. We'll call it a 8 foot, 8". Again, use your judgment, intent versus accuracy.

      I heard that phrase a while ago, and I use it a lot, because it's very applicable to modeling with point clouds. One thing I wanted to go through.

      Anybody have any questions on process pipe modeling? Is anybody from Autodesk in here? Nobody? Dang it.

      You cannot bring a point cloud into Family Creator. Why? They got the icon there. It's grayed-out. Is that just teasing me for later or what? I don't know what the deal is. I want it there. Because I need to model.

      I do not model in place. Don't model in place anything that is more than just a box or something like that. Use your Family Creator. Old school, I measure, write it down on a notepad, bring it into Family Creator. Use your shapes, your primitive shapes, do your modeling, put your pipe connections on, bring it in.

      That's the only answer I have for right now. You just simply can't. There is a hack. Let me talk about that hack. So here's the process model when we're all done. This is all modeled from the point cloud. Sometimes the pipe is off a little bit from the point cloud. You just have to deal with it. If you know about the project, you know where it matters, you know where it doesn't.

      Top tips, keep your point clouds local. We just talked about that. Leave your point cloud referenced until you are sure you don't need it. If you don't want to load it, just don't load it. But keep it in there. But if you really need to get rid of it, get rid of it at the end when you sure you don't need it. Because it's a real bugger to bring it back into the same space as you had it before.

      Hack for getting point cloud into Family Creator-- I haven't tried this. I just read this recently. Insert the point cloud into AutoCAD, then insert that AutoCAD drawing into your Family Creator. I heard that works. I haven't tried it. Yeah?

      AUDIENCE: Another hack for that might be if you make the model in place, which I know is discouraged, you could see if the point cloud thing activates there. Build in the model in place and then copy it out of the model in place.

      LUKE PEDERSON: It could be. I haven't gone real far into it yet. There may be some other hacks in there. But boy, I wish they would just make a point cloud able to be inserted into it. They can link an AutoCAD drawing into a Family Creator. I do that all the time to make pumps. I make a lot of pumps. I bring those top views, side views all in there and line them up, like that, AutoCAD drawings just like that and create it. But you can do point clouds.

      AUDIENCE: [INAUDIBLE] AutoCAD export to [INAUDIBLE]?

      LUKE PEDERSON: Yeah. Some of the file sizes get kind of big. It could. I don't know. There's probably other ways to do it, yeah, outside of Revit and AutoCAD, maybe, and bring it in. But if you're listening-- they're recording this-- Autodesk, can you please just make point clouds available in the Family Creator.

      One last thing-- we're about out of time here. Printing with a point cloud in a view, they print to a raster image. It really sucks. It makes for really poor prints. If you have a point cloud turned on in a view, and you print that sheet, it's going to give you this little warning that that view will print rasterized.

      Does everybody know what rasterized means? Meaning your view turns into a bunch of pixels, so all your lines are little squares. And it looks really terrible. I guess Revit, the only way it knows how to print point clouds is rasterized.

      So maybe for a future update in 2019, something, I don't know. Be aware of that. If you want to have that, you're going to have some weird results. I tore my hair out with that for hours and found out it was just how it is.

      Final questions or thoughts? We are up against time, I think. I'm on Central Time on my computer. I hope it's actually not 5 o'clock.

      [LAUGHTER]

      Yes?

      AUDIENCE: Do you have any familiarity or suggestions for automated software for just like cooperating?

      LUKE PEDERSON: For what?

      AUDIENCE: Cooperating?

      LUKE PEDERSON: Oh, yeah. I don't use it. But the people down here-- Scan to BIM, anybody use that? No. I think Scan to BIM is one of them. Our results were mixed with it. It worked when it was very plain. But when things weren't right, it gave you bad results. And you had to do a lot of handwork, anyways.

      AUDIENCE: FARO has PointSense.

      LUKE PEDERSON: PointSense, that was it.

      AUDIENCE: [INAUDIBLE]

      LUKE PEDERSON: Yep. They work great when they work. Anybody disagree with that? Yeah?

      AUDIENCE: And I know [INAUDIBLE] useful for architectural [INAUDIBLE]. I just draw [INAUDIBLE]. Unless it's historical, where you have to--

      LUKE PEDERSON: Exactly. Sometimes you need to.

      AUDIENCE: That creates like a mask.

      LUKE PEDERSON: A mesh or mask?

      AUDIENCE: A mask.

      LUKE PEDERSON: OK, mask. All right, thank you, all.

      [APPLAUSE]

      If you have any other, further questions, I got some cards there if you want them. If not, that's fine. I'll be here for a little bit, too.

      Downloads

      ______
      icon-svg-close-thick

      Cookie 首选项

      您的隐私对我们非常重要,为您提供出色的体验是我们的责任。为了帮助自定义信息和构建应用程序,我们会收集有关您如何使用此站点的数据。

      我们是否可以收集并使用您的数据?

      详细了解我们使用的第三方服务以及我们的隐私声明

      绝对必要 – 我们的网站正常运行并为您提供服务所必需的

      通过这些 Cookie,我们可以记录您的偏好或登录信息,响应您的请求或完成购物车中物品或服务的订购。

      改善您的体验 – 使我们能够为您展示与您相关的内容

      通过这些 Cookie,我们可以提供增强的功能和个性化服务。可能由我们或第三方提供商进行设置,我们会利用其服务为您提供定制的信息和体验。如果您不允许使用这些 Cookie,可能会无法使用某些或全部服务。

      定制您的广告 – 允许我们为您提供针对性的广告

      这些 Cookie 会根据您的活动和兴趣收集有关您的数据,以便向您显示相关广告并跟踪其效果。通过收集这些数据,我们可以更有针对性地向您显示与您的兴趣相关的广告。如果您不允许使用这些 Cookie,您看到的广告将缺乏针对性。

      icon-svg-close-thick

      第三方服务

      详细了解每个类别中我们所用的第三方服务,以及我们如何使用所收集的与您的网络活动相关的数据。

      icon-svg-hide-thick

      icon-svg-show-thick

      绝对必要 – 我们的网站正常运行并为您提供服务所必需的

      Qualtrics
      我们通过 Qualtrics 借助调查或联机表单获得您的反馈。您可能会被随机选定参与某项调查,或者您可以主动向我们提供反馈。填写调查之前,我们将收集数据以更好地了解您所执行的操作。这有助于我们解决您可能遇到的问题。. Qualtrics 隐私政策
      Akamai mPulse
      我们通过 Akamai mPulse 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Akamai mPulse 隐私政策
      Digital River
      我们通过 Digital River 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Digital River 隐私政策
      Dynatrace
      我们通过 Dynatrace 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Dynatrace 隐私政策
      Khoros
      我们通过 Khoros 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Khoros 隐私政策
      Launch Darkly
      我们通过 Launch Darkly 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Launch Darkly 隐私政策
      New Relic
      我们通过 New Relic 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. New Relic 隐私政策
      Salesforce Live Agent
      我们通过 Salesforce Live Agent 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Salesforce Live Agent 隐私政策
      Wistia
      我们通过 Wistia 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Wistia 隐私政策
      Tealium
      我们通过 Tealium 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Tealium 隐私政策
      Upsellit
      我们通过 Upsellit 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Upsellit 隐私政策
      CJ Affiliates
      我们通过 CJ Affiliates 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. CJ Affiliates 隐私政策
      Commission Factory
      我们通过 Commission Factory 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Commission Factory 隐私政策
      Google Analytics (Strictly Necessary)
      我们通过 Google Analytics (Strictly Necessary) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Strictly Necessary) 隐私政策
      Typepad Stats
      我们通过 Typepad Stats 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Typepad Stats 隐私政策
      Geo Targetly
      我们使用 Geo Targetly 将网站访问者引导至最合适的网页并/或根据他们的位置提供量身定制的内容。 Geo Targetly 使用网站访问者的 IP 地址确定访问者设备的大致位置。 这有助于确保访问者以其(最有可能的)本地语言浏览内容。Geo Targetly 隐私政策
      SpeedCurve
      我们使用 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、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Google Optimize 隐私政策
      ClickTale
      我们通过 ClickTale 更好地了解您可能会在站点的哪些方面遇到困难。我们通过会话记录来帮助了解您与站点的交互方式,包括页面上的各种元素。将隐藏可能会识别个人身份的信息,而不会收集此信息。. ClickTale 隐私政策
      OneSignal
      我们通过 OneSignal 在 OneSignal 提供支持的站点上投放数字广告。根据 OneSignal 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 OneSignal 收集的与您相关的数据相整合。我们利用发送给 OneSignal 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. OneSignal 隐私政策
      Optimizely
      我们通过 Optimizely 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Optimizely 隐私政策
      Amplitude
      我们通过 Amplitude 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Amplitude 隐私政策
      Snowplow
      我们通过 Snowplow 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Snowplow 隐私政策
      UserVoice
      我们通过 UserVoice 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. UserVoice 隐私政策
      Clearbit
      Clearbit 允许实时数据扩充,为客户提供个性化且相关的体验。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。Clearbit 隐私政策
      YouTube
      YouTube 是一个视频共享平台,允许用户在我们的网站上查看和共享嵌入视频。YouTube 提供关于视频性能的观看指标。 YouTube 隐私政策

      icon-svg-hide-thick

      icon-svg-show-thick

      定制您的广告 – 允许我们为您提供针对性的广告

      Adobe Analytics
      我们通过 Adobe Analytics 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Adobe Analytics 隐私政策
      Google Analytics (Web Analytics)
      我们通过 Google Analytics (Web Analytics) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Web Analytics) 隐私政策
      AdWords
      我们通过 AdWords 在 AdWords 提供支持的站点上投放数字广告。根据 AdWords 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AdWords 收集的与您相关的数据相整合。我们利用发送给 AdWords 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. 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、您的 Autodesk 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

      是否确定要简化联机体验?

      我们希望您能够从我们这里获得良好体验。对于上一屏幕中的类别,如果选择“是”,我们将收集并使用您的数据以自定义您的体验并为您构建更好的应用程序。您可以访问我们的“隐私声明”,根据需要更改您的设置。

      个性化您的体验,选择由您来做。

      我们重视隐私权。我们收集的数据可以帮助我们了解您对我们产品的使用情况、您可能感兴趣的信息以及我们可以在哪些方面做出改善以使您与 Autodesk 的沟通更为顺畅。

      我们是否可以收集并使用您的数据,从而为您打造个性化的体验?

      通过管理您在此站点的隐私设置来了解个性化体验的好处,或访问我们的隐私声明详细了解您的可用选项。