DEMYSTIFYING LARGE POINT CLOUD DATA SETS FOR SIMPLE INTEGRATION ON COMPLEX PROJECTS Mark LaBell Jr – Technical Leader, SSOE Group
Dec 16, 2015
DEMYSTIFYING LARGE POINT CLOUD DATA SETS FOR SIMPLE INTEGRATION ON COMPLEX PROJECTS
Mark LaBell Jr – Technical Leader, SSOE Group
Project Execution
Where are we now?
• Prior to May 2014 few projects were scanned• Past 10 months we have spent > $0.5MM USD
on scanning facilities for our clients• Over 50 projects have been scanned since
May 2014• Construction value > $750MM USD
What changed?
Applications used
NAVISWORKS
REVIT PLANT 3D CIVIL 3D
KUBIT POINTSENSE PLANT
MICROSTATION V8i
INVENTOR POINTOOLSRECAP/RECAP 360
So how do we get data to another office and most importantly fast?
Storage Setup
• Large projects > 50GB users have 2nd HDD (SSD) with a robocopy routine to mirror network– Robocopy routine is specific to each project
• Small projects < 50GB users point directly to network drive
• Both drives have the same map IE. P:\client1\project1
Storage Setup cont.
• DFS is utilized to create a point cloud directory in each office– If local P:\ doesn’t exist then failover to closest
office• Robocopy routine is run in server task
manager to sync data between offices that need data
• ReCap 360 utilized for non-modeling staff and project stakeholders
Simple Network DiagramLarge Projects > 50GB
*Data is copied between offices via robocopy during off hours
Simple Network DiagramSmall Projects < 50GB
*Data is copied between offices via robocopy during off hours
How to make a large project small…
• Always edit data on local hard drive, NEVER edit on a network
• Make sure that you have a SSD– Single largest performance increase with minimal
capital investment.
• Make sure Ortho is set in ReCap• Always do editing in unified data set
How to make a large project small…
• Export data as is when you get spinning wheel of death
• Have two computers to post process data• For tips to utilize ReCap on a remote desktop
refer to handout
Laser Scans Pre Edit
Laser Scans Post Edit
Demo Plans/2D References
+/- of RCP files with Regions
• + Saves time for exporting each region• - Navis and Revit do not support regions• + Regions can control visibility in AutoCAD and
ReCap• - Regions are a confusing concept for the non-
ReCap user.• - Regions still process data while loading,
therefore they don’t reduce model load times
Tips for Referencing RCS data
• Do breakdown scans based on sheet breakdown and S.O.W.– Minimize crop regions for point clouds,
performance is drastically decreased in Revit model
• Create a work set for PointCloud models• Create a master NWF for point clouds only
RECAP DEMO
Planning for Reality Capture
Reality Capture Spec• Define processes of your firm– How you use the data including examples– Minimum requirements for good data acquisition
• Define project S.O.W.• Send 2D docs and pictures from site visit to
vendor– Narrative of each attachment is crucial for good scope
definition.• Define scanning service requested– Pre Demo, Post demo, As-built, Slab Flatness, Site
Survey, GPR
Reality Capture Spec cont.
• Define the scanning area– Interior, Exterior, Roof, Above ceiling
• Declare safety requirements• Declare deliverables and tolerances of
registration– File formats, file transfer method, be sure to
request raw data
SPEC DEMO
Questions?
• Contact InformationMark LaBell Jr Email: [email protected]: @mark_labell_jrLinkedIn: www.linkedin.com/marklabelljr Phone: 734.262.1523