A plant owner receives a 3D model of an existing unit and cannot tell which elements were measured and which were assumed. Scan to BIM, also called point cloud to BIM, converts a registered point cloud of an existing facility into a building information model (BIM). The model is a structured 3D representation whose components carry data such as type, size and tag. This guide covers scan to BIM for process plants and industrial buildings. It explains the process, the level of development (LOD) and level of accuracy (LOA) vocabulary, the deliverables and the checks. It draws on the BIMForum LOD Specification, the USIBD LOA Specification, ISO 19650 and the US General Services Administration (GSA) guide to 3D imaging. The approach reflects the 3D laser scanning and reality capture work that Global Formulation provides to plant owners.
A point cloud is a measurement of surfaces, not a description of objects. It holds millions of coordinates, but it does not know that one cylinder is a pipe and another is a vessel. Scan to BIM supplies that knowledge by identifying each component and recording it in a model. The point cloud stays in the project as the evidence the model is checked against.
Scan-to-CAD differs in the deliverable. It produces 2D drawings or simple 3D geometry, whereas the BIM route is chosen when the model will serve design coordination or asset management. The GSA guide, written in 2009, describes the modelling step as data cleaning, segmentation and the fitting of geometric primitives such as planes, spheres, cones and cylinders. It reported that most modelling was then done manually and that the operator's qualifications had a large effect on the quality of the model. The capture step is covered in our guide to 3D laser scanning.
Common uses in a plant project are design coordination for revamps, tie-in and shutdown planning, and asset data. A revamp's front-end design and cost estimate start from the existing plant, and the contract models that follow are compared in our guide to EPC vs EPCM. Hazard studies also depend on drawings that match the plant, as set out in our guide to the HAZOP study.
The work is a chain in which each step constrains the next. The brief fixes what the model must contain, the scan must capture the evidence for it and the checks must prove it. Figure 1 shows the sequence, the check that sends work back, and where the two specifications in this guide apply. A weak link anywhere produces a model that looks complete and cannot be trusted.
The brief is where ISO 19650 helps. ISO 19650-1:2018 defines exchange information requirements as the information requirements that relate to an appointment. It also defines level of information need as a framework that sets the extent and granularity of information. One stated purpose is to prevent the delivery of too much information. ISO 7817-1:2024 sets out how to specify that level of information need, and it replaced the European standard EN 17412-1:2020. ISO 19650-1 states that it can be adapted to assets or projects of any scale and complexity, so an owner can borrow the discipline without adopting the whole framework.
Level of development describes how far a model element has been developed and how far a user can rely on it. The BIMForum LOD Specification 2025 expands the level definitions of the American Institute of Architects (AIA) and sets out LOD 100, 200, 300, 350, 400 and 500. It does not prescribe the level required at any project phase, so each project team must decide. The table paraphrases the levels and says what an owner should read into each.
| Level | What the BIMForum specification says | What an owner should read into it |
|---|---|---|
| LOD 100 | A symbol or other generic representation, with information that can be derived from other elements | Existence only; anything derived from it is approximate |
| LOD 200 | A generic placeholder that is recognisable 3D geometry, with approximate quantity, size, shape and location | Recognisable shape in an approximate position, so not a basis for measured dimensions |
| LOD 300 | Quantity, size, shape, location and orientation can be measured | Geometry and position accurate enough to take dimensions from |
| LOD 350 | Adds interfaces with adjacent or dependent elements, to support construction-level coordination | Components modelled with their connections, which clash and clearance checks need |
| LOD 400 | Detail sufficient for fabrication, assembly and installation, at the level of shop drawings | BIMForum notes that most models contain few if any LOD 400 elements |
| LOD 500 | A representation of an existing or as-constructed condition, developed by observation, field verification or interpolation, with the level of accuracy noted | Observed rather than designed; the accuracy must be stated, and BIMForum points to the USIBD specification for it |
Three rules in the specification matter to a buyer. LOD requirements are minimums, and every requirement for a level must be met before an element can be designated at it. The levels are cumulative, so each includes those below it, with LOD 500 as the exception. Location counts: BIMForum states that an element which is highly detailed and geometrically accurate but not accurately located can be no higher than LOD 200.
The wording of LOD 100 to 400 is written around elements being designed, and BIMForum treats LOD 500 as the level for existing conditions. It also notes that ISO 7817-1 does not address existing-conditions modelling. The brief should therefore say which definitions apply to the as-found plant and state the accuracy separately. Its element tables follow CSI Uniformat 2010 and Omniclass, which classify building systems. A plant brief should also say how process pipework, vessels and equipment are represented and which attributes each carries.
LOD says what a model contains, but it does not say how closely the contents match the plant. The USIBD Level of Accuracy Specification fills that gap with five levels, LOA10 to LOA50, according to the LIDAR Magazine summary of version 3.1. BIMForum recommends it for stating the accuracy of existing-condition elements. Version 3.1 is the current edition, and USIBD offers it as a free download after registration.
The specification separates two accuracies. Measured accuracy describes how closely the captured data reflects real-world conditions. Represented accuracy describes how closely the model reflects the measured data, as a 2026 LIDAR Magazine article explains. A model cannot be more accurate than the data it is based on. The GSA guide adds that modelling introduces an error of its own, so the uncertainty of the model is greater than that of the raw data.
| Deliverable | What the tolerance describes | How the GSA guide suggests checking it |
|---|---|---|
| Registered point cloud | Measured accuracy of the captured data | Compare control network distances, independent distances, overlapping scans or a known-length artifact with the cloud |
| Model components | Represented accuracy, together with the LOD | Compare horizontal, vertical and diagonal distances, angles between planes, verticality and pipe widths with independent measurements |
| Drawings extracted from the model | Represented accuracy at the scan date | Compare distances with an independent measurement; rectified plans carry larger errors |
| Areas without data | Stated as gaps, not hidden | Mark missing data on the model and drawings, graphically or in words |
Three details turn these terms into a contract. USIBD version 3.1 adds a section on specifying tolerances as standard deviation and guidance on choosing the correct level from the required tolerance. The GSA guide defines tolerance as the allowed deviation of a deliverable from truth, a value measured by other means, and reminds readers that all measurements have errors. LIDAR Magazine adds that validation must match the accuracy being checked, because a wall-to-wall room measurement can compound deviations that are individually within tolerance.
The tolerance band for each level is set out in the specification itself. This guide does not reproduce the bands, so read them there before writing the contract.
The work should end with more than a model file. The model is one deliverable among several that let the owner and the design team check it and reuse the data. Each item below answers a question the owner will have after handover. The table lists them with what each one lets the owner do.
| Deliverable | What it is | What it lets you do |
|---|---|---|
| Registered point cloud | The joined scans in the agreed coordinate system, in an open format such as E57 | Re-measure or re-model without returning to site; ASTM E2807 defines E57 for point data, colour, intensity and photographs |
| Registration and control report | Registration error and control network results; the GSA guide asks for a narrative report that proves the accuracy of the work | Judge whether the cloud meets the measured accuracy |
| BIM model | Components identified with type, size and tag at the agreed LOD, in the design team's native format | Design coordination, clash checks and asset data |
| Open exchange model | An IFC file; IFC is the open international standard for BIM data, ISO 16739-1, whose 2024 edition replaced the 2018 edition | Open and reuse the model outside the authoring software |
| Deviation report | A comparison of the model with the point cloud, with the tolerance applied | See where the model departs from the as-found plant |
| Drawings extracted from the model | Plans, sections, elevations and isometrics tied to the scan date | Handover, permitting and maintenance records |
| Scope and assumptions note | The LOD and LOA used, the areas modelled and the areas with missing data | Know where the model is observed and where it is interpolated |
Agree the formats and the coordinate system before delivery, so that the data opens in the design environment without rework. Where more than one scanner or software system is used, the GSA guide reports that data compatibility problems in a pilot project increased post-processing time and delayed the work. It asks the provider to identify any incompatibility and propose a solution.
The GSA guide states that the time needed to generate a model from 3D data is proportional to the level of detail. It adds that tighter tolerances and higher resolutions increase scan times and costs. Effort therefore follows the area modelled, the detail and attributes required and the accuracy specified. Fix those in the brief before comparing quotations, so that every bid describes the same work.
These projects fail in a recognisable way: the model arrives, looks complete and then does not fit the work it was bought for. The causes sit in the brief, the modelling assumptions and the checks rather than in the scanner. Each failure has a consequence on a revamp and a preventable cause. The table lists the common ones.
| What goes wrong | Project consequence | How to prevent it |
|---|---|---|
| Level of detail not specified | Bids describe different work, or the model lacks what the design team needs | State the LOD for each area and system in the brief |
| Detail mistaken for accuracy | A richly modelled pipe sits in the wrong place and a tie-in point is wrong | State LOD and LOA separately; BIMForum caps a poorly located element at LOD 200 |
| Similar elements assumed identical | One support or valve that differs from its neighbours is modelled as a copy, and the fabricated spool does not fit | Require a field check of repeated elements; the GSA guide describes a duplicated column that was not identical |
| Hidden areas filled by interpolation without a flag | The model shows a clean pipe run where no data exists | Require missing-data notes on the model and the drawings |
| Checks that do not match the accuracy claimed | Deviations that pass one by one compound across a room or a unit | Match the validation method to the accuracy being checked |
| No agreed coordinate system or control | The model cannot be combined with the design model or the site survey | Fix the datum and control points in the brief |
| Only a proprietary file is delivered | The design team cannot open or reuse the model | Require open formats such as E57 and IFC alongside native files |
| Cost of rework not allocated | A dispute arises over who pays when missing or wrong data forces a return to site | Specify who bears corrective action, as the GSA guide advises for the solicitation |
| Plant changes after the scan | The model no longer matches the plant when the design is issued | Record the scan date on every deliverable and set re-scan triggers |
Most of these failures are specification failures. A provider can only meet a level of detail, a tolerance and a format that someone wrote down before the first scan.
The brief is the owner's main control over the work. A provider can only meet a requirement that someone wrote down first. Work through the items in order, because each one constrains the next. The result is a brief that any provider can price and any engineer can check.
On delivery, check a sample of dimensions against an independent measurement before accepting the model. Include distances in different directions, an angle between planes and pipe diameters, as the GSA guide suggests for 3D models. Read the deviation report and the missing-data notes before the model goes to the design team.
Owners planning a revamp, an as-built verification or reality capture for brownfield plants can start from our 3D laser scanning and reality capture service. It covers scan planning and survey control, point cloud registration, scan-to-CAD and scan-to-BIM deliverables, and revamp design and clash checks. Where the model will feed building services design, the same data supports our MEP, HVAC and fire protection engineering work. The checklist above is the brief to bring to that conversation.
Scan to BIM is the process of converting a registered point cloud of an existing facility into a building information model. The model identifies each component and records data such as its type, size and tag.
The point cloud supplies the measurements and the model supplies the identity, so the model can serve design coordination and asset data. The point cloud stays as the reference the model is checked against.
Scan to CAD produces 2D drawings or simple 3D geometry from the point cloud. Scan to BIM produces a structured model in which components carry information such as type, size and tag.
BIM is chosen when the model will be used for design coordination or asset management. Agree the target format and the level of detail before work starts, because both change the effort.
LOD stands for level of development, which describes how far a model element has been developed and how far a user can rely on it. The BIMForum LOD Specification 2025 defines LOD 100, 200, 300, 350, 400 and 500.
LOD 500 is the level for existing or as-constructed conditions, and it requires the level of accuracy to be noted. The specification does not prescribe which level a project phase needs, so the brief must state it.
LOD describes the content and development of model elements, while LOA describes the accuracy of the captured data and of the model built from it. LOD does not address the accuracy of the data underlying a model, which is the gap LOA fills.
The USIBD LOA Specification separates the measured accuracy of the captured data from the represented accuracy of the models or drawings. State both in the brief, alongside the LOD.
The answer depends on the scanning, the registration, the control and the modelling, so no single figure applies to every project. A model cannot be more accurate than the data it is based on, and the GSA guide notes that modelling adds its own error.
State the accuracy as a tolerance, name the level in the USIBD specification and agree how it will be checked. An independent sample of dimensions turns the figure into an acceptance test.
A sensible set is a registered point cloud, the BIM model in the design team's native format and an open exchange file. ASTM E2807 defines the E57 format for point data, colour, intensity and photographs, and IFC is the open international standard for BIM data.
Agree the formats and the coordinate system before delivery, so that the data opens in the design environment without rework. Ask the provider what was changed in each export.
Yes, for most areas. Scanning is non-contact and can be done during operation within the site's permits and safety rules, and classified areas need equipment and procedures approved for the zone.
The model records the plant at the scan date, so later changes need a re-scan or an update process. Agree the re-scan triggers in the brief.
The GSA guide states that the time needed to generate a model from 3D data is proportional to the level of detail. It adds that tighter tolerances and higher resolutions increase scan times and costs.
Effort therefore follows the area modelled, the detail and attributes required and the accuracy specified. Fix those in the brief before comparing quotations, so that every bid describes the same work.
Global Formulation provides 3D laser scanning, point cloud registration, scan-to-model deliverables and as-built verification for plant owners planning revamps and shutdowns.
Discuss a Scan to BIM Project