© 2012 Autodesk AB6069-V A Few Million Points: Scan to BIM Beau Turner Product Director.
Spar 2013 Scan for BIM
-
Upload
keith-roberts-pls -
Category
Design
-
view
490 -
download
1
description
Transcript of Spar 2013 Scan for BIM
SPAR 2013
Scan for BIM “Success is in the Details”
Keith Roberts, PLSSSM Group, Inc.
April 17, 2013
SPAR 2013
� Multi disciplined engineering firm headquartered in Reading PA
� Our roots are in Surveying and Civil Engineering
� Laser scanning technology for 8 years
� Revit modeling technology for 5 years
SSM Group, Inc.
SPAR 2013
Equipment SSM utilizes for our scan to BIM projects include:
� Laser scanning Field Hardware� Leica Scan Station, 6000, 6200, C10
� Office Software� Leica Cyclone, Cloudworx, Autodesk
Revit
Success is in the Details
Three areas were we focused to reduce lost time and money
� Modeling to Level of Development
� Data Preparation for linking to Revit
� Navigating the Revit Coordinate system
Success is in the Details
Modeling to Level of Development
Modeling to Level of Development
Sources for LOD information
� AIA - E202
� Consensus Docs - 301
� Facilities Owners� Penn State � USC
Modeling to Level of Development
AIA – E202LOD is generally defined as follows:
� Level 100 - Conceptual Design
� Level 200 - Design Development
� Level 300 - Construction Documents
� Level 400 - Fabrication and Assembly
� Level 500 - As-built Conditions
Modeling to Level of Development
LOD is generally defined as follows:
� Level 200� Similar to schematic design or design
development, the model would consist of generalized systems including approximate quantities, size, shape, location and orientation. LOD 200 models are typically used for analysis of defined systems and general performance objectives.
Modeling to Level of Development
LOD is generally defined as follows:
� Level 300� Model elements equivalent to traditional
construction documents and shop drawings. LOD 300 models are well suited for estimating as well as construction coordination for clash detection, scheduling, and visualization. LOD models should include the attributes and parameters defined by the owner in the BIM deliverable standard.
Modeling to Level of Development
LOD is generally defined as follows:
� Level 500� The final level of development represents the
project as it has been constructed including as-built conditions. The model is configured to be the central data storage for integration into building maintenance and operations systems. LOD 500 models will include completed parameters and attributes specified in the owners BIM deliverable specification.
Modeling to Level of Development
Modeling to Level of Development
� Walls that are leaning
Modeling to Level of Development
� New roof top HVAC unit on an existing building
Modeling to Level of Development
Modeling to Level of Development
� Structural analysis for load capacity to support new HVAC unit
Modeling to Level of Development
� Clearly understanding the project needs before going into the field
� Know dimensional information required so it can be achieved
� Supplement with hand measurements to confirm critical information
� Detailed scan of one of repeated objects for modeling
Modeling to Level of Development
Industry Standard Levels defining existing conditions
Success is in the Details
Data Preparation for linking to Revit
Data Preparation for Linking to Revit
Scan data in Cyclone
� Registered Pointcloud set to project coordinate system
� BIM manager to create project plan for breaking up the pointcloud into export files for Revit
� Typical breakup areas� Interior� Exterior� By level� By sections
Data Preparation for Linking to Revit
Data Preparation for Linking to Revit
Data clean up
� Basic clean up to pointclouds� Remove not required to meet modeling goals� Typical data removed
� Interior / Exterior over shoot data not already removed
� Ground surface data� Floor surface data� Roof or ceiling surface data
Data Preparation for Linking to Revit
Model of building for elevation views� Total cleaned exterior
Data Preparation for Linking to Revit
Model of building for elevation views� Cleaned east elevation
Data Preparation for Linking to Revit
Model of building for elevation views
Data Preparation for Linking to Revit
Exporting data from Cyclone
� PTS format� Set export units to Meters � Common text file format
� PTX format� Can not be used with unified data� Always exports in Meters � Single file created by scan world
� PTG format� Can not be used with unified data� Set export to Meters � One file created for each scan world
Success is in the Details
Navigating the Revit Coordinate system
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� Use coordinates set by registration for export
� Use Cyclone to create a custom matching coordinates with existing drawings or Revit data for export
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� Create CAD drawing with site or building coordinate data to be used
� Create new Revit project from your template
� Create a view called Site, Revit default construction template contains a Site
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� Site view will contain project & survey origin marks
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� Insert drawing file into Revit using center to center
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� Acquire coordinates from drawing
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� First Pointcloud inserted origin to origin
� Make any modifications to match elevation data to Levels
� Insert subsequent Pointclouds with origin to last placed
Navigating the Revit Coordinate systems
� Use project north to set rotation
� Use crop region rotation for unique building situations
Navigating the Revit Coordinate systems
Workflow for Cyclone to Revit coordinate system
� CAD drawing for acquiring coordinates in Revit should not be modified moving forward
� CAD drawing should be locked after placement
� Pointclouds should be locked after placement
� Last pointcloud placed should not be removed from the project