This is something that I've been doing rather a lot over the past couple years, as we get more and more projects with the budget for 3D scanning.
First thing I do is cut the point cloud down to a manageable size with Recap. If I need to copy an asset out of the cloud, that means that I might use the limit box to block out everything except the exact bit that I need.
Then, with Inventor:
1- create new assembly to be your point cloud host.
2- insert the point cloud into the assembly at the origin location. Don't screw around with the origins in the file where you have the cloud. If you're just doing an individual part this may not be important, but if you're going to be putting a full scene together later with Navisworks and you've got stuff crossing 3-5 different software packages, you do NOT want to be trying to get origins sorted out. If the origin locations in every one of your files don't match up, you're not going to have a lot of fun in Navisworks.
3- when you insert the point cloud, turn the point density up as high as it will go. (Or as high as your video card will let you go. I've got a couple of point clouds that really put some stress even on my 4090.)
This is where the workflows diverge, depending on what you're doing. If you're modeling something that will be fitting into the scene, then create a subassembly (or part) and, again, keep it grounded to origin, and model your stuff in whatever orientation that happens to land in. This is the important file, the one that you'll insert into Navisworks later, because it contains your models but does not contain the point cloud. (Navis seems to throw an error for Inventor 2023 and earlier if I append a part or ass'y that contains a point cloud. Doesn't seem to happen with '24, but I haven't played with that enough yet to be sure if I can get away with it or not.)
You can create new ersatz-origin planes if necessary to represent floor or platform levels or north-south / east-west for aligning parts added to your assembly, and below this level it's okay to model as normal around the origin planes. It's just the top-level file that goes into Navisworks that must have the same origin and orientation as the ReCap file.
If you're just trying to model assets out of the real world that you will then re-use in any assembly, then you don't have to be as sticky about origins. I'll still generally put the scan in the host .IAM file at origin, but I'll usually locate the part file directly on top of (or right next to) the point cloud, and aligned with it, just to make sketches easier.
If you're having trouble picking out shells of the point cloud to use for lining up sketch geometry, use the BOX CROP tool (Manage tab, Point Cloud panel) to cut down to just a slice. That will usually do the trick- hiding irrelevant points cuts down on the clutter substantially.
There's more to it, but those are the important bits that I can think of right off. If you have some specific questions, though...?
Rusty
