Imagine building a skyscraper without knowing the exact layout of the existing underground pipes. Chaos, right? This is where Scan to BIM steps in—a process that turns real-world structures into precise digital models. But when working on public projects in the UK (or globally), simply creating a model isn’t enough. It must comply with BIM Level 2, a set of standards ensuring collaboration, accuracy, and data-rich project delivery.

In this blog, we’ll explore the technical requirements for Scan to BIM services to ensure compliance with BIM Level 2 standards. Whether you’re an architect, contractor, or facility manager, you’ll learn how to bridge the gap between laser scans and BIM-ready models that tick all regulatory boxes.

What is BIM Level 2 Compliance?

BIM Level 2 is a UK-led framework (now adopted globally) that defines how teams should share and manage building data. Think of it as a rulebook for teamwork in construction. Here’s what it demands:

1. Common Data Environment (CDE): A shared digital workspace (like Autodesk BIM 360) where all project data is stored and updated.
2. Standardized Deliverables: Models and documents must follow ISO 19650 and PAS 1192 standards.
3. Structured Data: Information must be organized using systems like Uniclass (for classifying spaces) or COBie (for asset data like HVAC systems).

Why does this matter for Scan to BIM?

Laser scans capture the as-built conditions of a structure. To comply with BIM Level 2, these scans must turn into models that are not just visually accurate but also packed with usable data for architects, engineers, and facility managers.

Technical Requirements for Scan to BIM in BIM Level 2 Projects

1. Data Capture Standards

• Point Cloud Accuracy:
  Laser scanners (LiDAR) or photogrammetry tools create “point clouds”—millions of dots representing a structure’s surface. For BIM Level 2, these dots must be accurate within ±2mm to avoid errors in the final model.
• Georeferencing:
  Scans must align with real-world coordinates. Use control points (physical markers on-site) to ensure scans are positioned correctly.

2. Model Development Criteria

• Level of Detail (LOD):
  BIM Level 2 typically requires LOD 300-400, meaning models must show:
  • LOD 300: Exact shapes/sizes of walls, doors, and MEP systems.
  • LOD 400: Assembly details (e.g., how pipes connect to valves).
• Metadata Matters:
  A wall isn’t just a 3D shape—it needs data! Embed details like material type, fire rating, or maintenance schedules into the model.
• Clash Detection:
  Use tools like Navisworks to run clash tests. For example, ensure pipes don’t collide with beams in the final design.

3. Data Structuring

• Uniclass Codes:
  Tag every element (e.g., doors, ducts) with Uniclass codes. This helps teams quickly find data. For example, a door might be labeled Pr_25_50_10 for “Doors and Windows.”
• COBie Deliverables:
  COBie spreadsheets are like “user manuals” for buildings. They list asset details (e.g., pump model numbers, and warranty expiry dates) for facility managers.

4. Interoperability

• IFC Files:
  Save your BIM model in Industry Foundation Classes (IFC) format. This ensures it works across software like Revit, ArchiCAD, or Tekla.
• CDE Integration:
  Upload models to a CDE (e.g., Trimble Connect) so all stakeholders access the latest version. No more emailing huge files!

Step-by-Step Workflow for BIM Level 2 Compliance

1. Pre-Scan Planning:
   • Define scan density (e.g., 5 mm resolution for complex MEP systems).
   • Plan control point locations for georeferencing.
2. On-Site Scanning:
   • Use LiDAR scanners to capture data. Perform QA checks—like overlapping scans by 30% to avoid gaps.
3. Post-Processing:
   • Clean noise from point clouds (e.g., remove stray dots from moving people).
   • Import scans into BIM software (Revit, ArchiCAD) to trace walls, ducts, etc.
4. Model Validation:
   • Compare the BIM model with the original point cloud. Tools like CloudCompare can highlight discrepancies.

Tools to Use:

• Scanning: FARO Focus LiDAR, Leica BLK360.
• Software: Autodesk ReCap (for point clouds), Solibri (for clash detection).

Common Challenges (and How to Solve Them?)

• Problem: Incomplete scans lead to guesswork in models.
  Solution: Perform pre-scan site audits to identify obstacles (e.g., cluttered rooms).
• Problem: Missing metadata ruins COBie compliance.
  Solution: Use AI tools like ClearEdge3D to auto-tag assets in point clouds.
• Problem: Version conflicts in CDEs.
  Solution: Assign a BIM manager to control file uploads and updates.

Case Study: Hospital Renovation Done Right

Project: Upgrading a 1980s UK hospital’s MEP systems.
Challenge: Outdated floor plans didn’t match reality.

Scan to BIM Approach:

1. Scanned the building at 3mm accuracy.
2. Modeled ducts, pipes, and electrical systems in Revit with LOD 400.
3. Added COBie data for 500+ assets (e.g., pump installation dates).Result:

• Zero clashes during construction.
• The hospital’s FM team received a COBie spreadsheet for easy maintenance.
• Project certified as BIM Level 2 compliant.

Conclusion

BIM Level 2 isn’t just red tape—it’s about building smarter. By combining precise laser scans with structured data, Scan to BIM ensures your models are both accurate and actionable. Follow the technical steps we’ve outlined, leverage the right tools, and you’ll not only meet compliance but save time and costs long-term.

Need Help? Partner with a Scan to BIM specialist to audit your workflow. Compliance is easier when you’re prepared!