Scan to BIM: LOD 200 vs LOD 300 vs LOD 400 Explained

Level of Development (LOD) specifications in scan-to-BIM workflows determine the geometric accuracy, dimensional precision, and information richness of your final model. The difference between LOD 200, 300, and 400 models directly impacts scanning requirements, processing time, and project costs. Understanding these distinctions prevents over-specification that wastes budget and under-specification that fails project requirements.

Point cloud data from Trimble X7 scanners (2.4mm accuracy at 20m) or NavVis MLX mobile mapping systems (5mm SLAM accuracy) can support any LOD specification, but the modelling approach and time investment varies dramatically. A heritage documentation project requiring LOD 400 detail demands different scanning density and processing workflows than a LOD 200 conceptual renovation model.

The Australian Institute of Architects BIM Guidelines and Property Council BIM Standards reference LOD frameworks, but practical application requires understanding how point cloud accuracy translates to model geometry. This relationship between scan data quality and achievable LOD determines project feasibility and cost structure.

LOD 200: Conceptual Geometry and Approximate Dimensions

LOD 200 models represent building elements as generic placeholders with approximate dimensions and basic spatial relationships. Walls appear as simple rectangular volumes, structural columns as basic cylinders or rectangles, and MEP systems as schematic representations without specific product information.

Point cloud requirements for LOD 200 models are minimal compared to higher detail levels. Trimble X7 scans at 6mm spacing provide more than adequate density for extracting wall centrelines, floor elevations, and basic structural grid layouts. Even lower-resolution scans from older equipment like FARO Focus S70 (3.5mm accuracy at 10m) deliver sufficient accuracy for LOD 200 geometry extraction.

Processing workflows focus on extracting major building elements and spatial boundaries rather than detailed component geometry. Autodesk ReCap Pro handles point cloud segmentation for wall, floor, and ceiling identification, while Revit's "Create Wall" and "Create Floor" tools generate basic geometry from point cloud references. Manual modelling time averages 2-4 hours per 100 square metres of floor area.

Typical LOD 200 applications include:

• Feasibility studies: requiring basic spatial understanding
• Conceptual design: with approximate building dimensions
• Space planning: for tenant fit-outs and office layouts
• Preliminary cost estimation: based on gross floor areas
• Heritage documentation: at record-keeping level only

File size considerations favour LOD 200 models for large building complexes. A 5,000 square metre office building typically produces 50-80MB Revit files at LOD 200 compared to 200-400MB at LOD 300. This difference impacts file sharing, cloud collaboration, and software performance across project teams.

Accuracy expectations align with conceptual design requirements. Wall thickness variations of ±25mm are acceptable, floor level tolerances of ±10mm meet most planning applications, and structural grid approximations within ±50mm support preliminary engineering calculations. These tolerances exceed point cloud accuracy limitations and reflect modelling methodology rather than scanning constraints.

LOD 300: Specific Geometry and Accurate Dimensions

LOD 300 models define building elements with specific geometry, accurate dimensions, and recognisable product characteristics. Walls include actual thickness measurements, structural elements show true cross-sectional profiles, and MEP components appear as manufacturer-specific products with correct sizing and connection details.

Point cloud density requirements increase substantially for LOD 300 accuracy. Trimble X7 scans at 3mm spacing ensure adequate point density for measuring wall thickness variations, structural member dimensions, and mechanical equipment sizing. NavVis MLX mobile mapping provides sufficient accuracy for most LOD 300 requirements, though complex mechanical spaces may require supplementary static scanning for detailed component measurement.

Processing workflows emphasise dimensional accuracy and geometric precision. Cyclone REGISTER 360 point cloud registration maintains sub-millimetre accuracy across multiple scan positions, while CloudCompare measurement tools verify component dimensions before Revit modelling begins. Manual measurement verification becomes critical for structural elements, mechanical equipment, and architectural details.

LOD 300 modelling requirements include:

• Accurate wall thickness: measured from point cloud data
• Structural member profiles: matching actual cross-sections
• MEP component sizing: based on manufacturer specifications
• Door and window dimensions: including frame details and hardware
• Ceiling height variations: and structural penetrations

Revit families require specific product selection rather than generic placeholders. Structural steel members reference actual Universal Beam or Universal Column profiles from Australian steel suppliers. Mechanical equipment families match manufacturer model numbers and dimensional specifications. This specificity demands extensive family libraries and product knowledge beyond basic modelling skills.

Quality control processes verify dimensional accuracy against point cloud source data. Revit's "Point Cloud" visibility settings enable direct comparison between model geometry and scan data. Acceptable tolerances typically range from ±5mm for structural elements to ±10mm for architectural components, reflecting both point cloud accuracy and modelling precision limitations.

Time investment increases significantly compared to LOD 200 workflows. Manual modelling averages 8-12 hours per 100 square metres, with complex mechanical spaces requiring 15-20 hours per 100 square metres. This time investment reflects detailed measurement, family selection, and quality verification processes essential for LOD 300 accuracy.

LOD 400: Fabrication-Ready Detail and Assembly Information

LOD 400 models contain fabrication-ready geometry with assembly details, connection information, and installation specifications. Structural connections show bolt patterns and weld details, MEP systems include support brackets and connection fittings, and architectural elements display construction joints and material interfaces.

Point cloud requirements reach maximum density and accuracy specifications. Trimble X7 scans at 1.5mm spacing capture fine detail necessary for connection geometry and assembly interfaces. Static scanning positions require careful planning to eliminate shadow zones around structural connections, mechanical equipment, and architectural details. DJI Matrice 4T photogrammetry supplements point cloud data for areas requiring visual texture and material identification.

Processing workflows integrate multiple data sources and verification methods. Cyclone REGISTER 360 processes high-density point clouds with sub-millimetre registration accuracy, while Trimble Perspective enables detailed measurement and annotation workflows. Photogrammetric models from DJI Matrice 4T provide colour information and material identification supporting fabrication documentation.

LOD 400 detail requirements include:

• Structural connection details: with bolt patterns and weld specifications
• MEP support systems: including brackets, hangers, and seismic restraints
• Architectural assembly details: showing material interfaces and construction joints
• Equipment access panels: and maintenance clearance requirements
• Utility connection points: with pipe sizing and electrical specifications

Revit modelling approaches shift from generic families to custom component creation. Structural connections require detailed family development showing bolt patterns, plate thicknesses, and weld symbols. MEP systems include support brackets, pipe fittings, and electrical junction boxes as separate model elements. This level of detail demands advanced Revit family creation skills and fabrication knowledge.

File management becomes critical due to model complexity and file size. LOD 400 models typically generate 500MB-1GB Revit files for medium-scale buildings, requiring workstation-class hardware and robust network infrastructure. Point cloud reference files may exceed 10GB, necessitating local storage and high-speed data transfer capabilities.

Quality assurance processes include dimensional verification, assembly clash detection, and fabrication feasibility review. Navisworks Manage clash detection identifies interference between detailed components, while fabrication consultants review model geometry for constructability. These verification steps prevent costly field modifications and ensure model accuracy supports fabrication workflows.

Scanning Requirements by LOD Specification

Point cloud density and accuracy requirements scale directly with LOD specifications, but scanning methodology remains consistent across all detail levels. Trimble X7 static scanning provides the accuracy foundation for any LOD requirement, while NavVis MLX mobile mapping offers efficient coverage for large areas at LOD 200-300 specifications.

Scan spacing calculations depend on target LOD and object complexity. LOD 200 models accept 6-10mm point spacing, allowing rapid scanning with extended range settings. LOD 300 requirements demand 3-5mm spacing for accurate dimensional measurement, while LOD 400 detail requires 1.5-3mm spacing to capture connection geometry and assembly interfaces.

Scanning density by LOD level:

• LOD 200:: 6-10mm point spacing, 20-30 scan positions per 1000m²
• LOD 300:: 3-5mm point spacing, 40-60 scan positions per 1000m²
• LOD 400:: 1.5-3mm spacing, 60-100 scan positions per 1000m²

Registration accuracy requirements increase with LOD specifications. LOD 200 models tolerate ±5mm registration errors without affecting usability, while LOD 400 fabrication models require sub-millimetre registration accuracy. Cyclone REGISTER 360 cloud-to-cloud registration achieves 1-2mm accuracy with proper target placement and overlap planning.

Data processing time scales exponentially with point density and registration requirements. LOD 200 point clouds process in 2-4 hours for typical building scans, while LOD 400 datasets require 8-16 hours for registration, cleaning, and export preparation. This processing time impacts project schedules and delivery timelines.

Cost Implications and Project Planning

LOD specification directly impacts project costs through scanning requirements, processing time, and modelling effort. Understanding these cost relationships enables accurate project budgeting and prevents scope creep during model development.

Scanning costs remain relatively stable across LOD levels, as equipment mobilisation and site setup represent the majority of field expenses. Additional scan positions for higher LOD requirements add 10-20% to scanning costs, while processing time increases more substantially. LOD 400 processing typically costs 2-3 times LOD 200 processing due to density and accuracy requirements.

Typical cost multipliers by LOD level:

• LOD 200:: Baseline scanning and processing costs
• LOD 300:: 1.5-2x baseline costs for increased modelling time
• LOD 400:: 3-4x baseline costs for detailed geometry and verification

Modelling costs show the greatest variation between LOD specifications. LOD 200 models require basic geometric extraction and generic family placement, while LOD 400 models demand detailed measurement, custom family creation, and extensive quality verification. Project timelines must account for these modelling requirements during planning phases.

Value engineering opportunities exist through LOD specification optimisation. Mixed LOD approaches model critical areas at higher detail levels while maintaining LOD 200-300 for less critical spaces. Mechanical rooms and structural connections may require LOD 400 detail, while office areas and circulation spaces function adequately at LOD 200-300.

Project delivery methods influence LOD requirements and cost structures. Design-build contracts may specify LOD 300 for design development and LOD 400 for fabrication documentation, requiring phased scanning and modelling approaches. Traditional design-bid-build projects often specify consistent LOD levels throughout, simplifying scanning and processing workflows.

Software Workflows and File Format Considerations

Different LOD specifications require specific software workflows and file format handling to maintain data integrity and model accuracy. Understanding these technical requirements prevents compatibility issues and ensures deliverable quality meets project specifications.

Point cloud processing workflows remain consistent across LOD levels, but export settings and file formats vary based on downstream modelling requirements. E57 format provides universal compatibility for LOD 200-300 workflows, while LOD 400 requirements may demand higher-precision formats like LAS or native scanner formats (RCS for Leica, RCP for FARO).

Revit integration approaches differ significantly between LOD specifications. LOD 200 models use point clouds as reference geometry for basic element creation, while LOD 400 workflows require detailed measurement and verification against point cloud data. Revit's point cloud display settings must accommodate these different usage patterns.

Software workflow by LOD specification:

• LOD 200:: ReCap Pro → Revit with basic family libraries
• LOD 300:: Cyclone REGISTER 360 → ReCap Pro → Revit with manufacturer families
• LOD 400:: Cyclone REGISTER 360 → CloudCompare → Revit with custom families

File size management becomes critical at higher LOD specifications. LOD 400 models with detailed point cloud references may exceed Revit's performance limitations, requiring point cloud segmentation and selective loading. Cloud-based collaboration platforms must accommodate larger file sizes and longer sync times for detailed models.

Quality control workflows integrate point cloud verification at all LOD levels, but verification methods vary based on accuracy requirements. LOD 200 models require basic dimensional checks, while LOD 400 models demand comprehensive geometric verification and clash detection. These quality control processes impact project schedules and resource allocation.

Conclusion

LOD specification selection requires balancing project requirements against scanning costs, processing time, and modelling effort. LOD 200 provides adequate detail for conceptual design and space planning at minimal cost, while LOD 300 supports detailed design development with moderate investment. LOD 400 delivers fabrication-ready detail but demands maximum scanning density, processing time, and modelling expertise. Understanding these relationships enables informed LOD selection that meets project objectives without unnecessary cost or complexity. Mixed LOD approaches often provide optimal value by applying appropriate detail levels to different building areas based on their specific requirements and project criticality.