More Sharing Options
Key Points
Scan-to-BIM Cost from an Existing Point Cloud
When the point cloud already exists, Scan-to-BIM cost is driven by the work required to turn that reference into the agreed model. The main variables are input quality, included elements, geometric requirements, information fields, delivery format, quality review and revisions. Compare quotations against the same modeling scope before comparing their totals.
Our Approach
How we help your team
Your existing point cloud is the starting point for a useful model and a clear quotation. We help you define the elements, detail and delivery requirements so you can see what the price covers before committing to the work.
We review your available point cloud and intended use before defining the modeling work. Together, we identify the elements, tolerances, properties and files your team needs. Processing requirements, data gaps and review rounds are addressed in the proposal, giving you a clearer view of what the price covers and what could change it.
Part 1 of 7
Start with an input review, even when scanning is complete
An existing point cloud can save a new site visit when it contains the information needed for the model. Before estimating production, review its coverage, capture date, registration information, units, coordinates and file organization. Supply a representative sample from a congested or detailed area as well as a typical space. That gives the modeler a practical basis for assessing the work.
We identify any indexing, cleanup, alignment review or data repair your files need before modeling begins. We also distinguish usable observations from hidden or missing surfaces. If your model needs a concealed face or an area that was never scanned, we agree whether to exclude it, label an assumption or arrange additional capture. Modeling cannot recover measurements that were never made.
Part 2 of 7
Define the modeled elements rather than relying on area alone
Floor area is useful for describing a building, but it does not describe every task inside it. A simple shell and a congested plant room can occupy the same area while requiring very different element counts, interpretation and review. Identify the disciplines and categories the receiving team will actually use.
For architecture, specify walls, openings, ceilings and relevant irregularities. For structure, identify members and any connection detail required. For MEP, state whether the scope includes main runs only, fittings, valves, supports, insulation or equipment connections. Also define a minimum feature size and the treatment of inaccessible areas. These decisions give a quotation a more useful basis than an undefined price per square foot.
Part 3 of 7
Separate model development from geometric accuracy
Use BIMForum’s Level of Development (LOD) framework to describe the content and reliability of model elements. State the required agreement with the point cloud separately, including tolerances and how they will be checked. USIBD’s Level of Accuracy (LOA) guidance supports that discussion. Together, these requirements define what we will model and how your team will review it.
Define whether the model should retain measured slopes and offsets, use nominal dimensions or represent local deformation. Fitting a simple object within an agreed tolerance is different from reproducing every visible irregularity. Ask for detailed geometry where it affects your design or coordination decisions. Extra detail adds work, so it should serve a clear purpose.
Part 4 of 7
Include properties, coordinates and software requirements
Geometry is only part of a BIM deliverable. Required categories, system assignments, asset identifiers, parameter fields, naming and model organization also take work to establish and check. Identify the source of each required property. A point cloud may support geometry while equipment names, materials or operational data require photographs, schedules or other owner-provided records.
Specify the authoring application and version, exchange formats, model divisions and coordinate requirements. Autodesk supports RCP and RCS point cloud links in Revit, but a correctly opening reference file is not a completed BIM model. Confirm that linked files, external dependencies and deliverable versions will work in the recipient’s environment before production starts.
Part 5 of 7
Compare two scopes using the same reference data
A space planning model and a coordination model can start from the same cloud but require different production and review work. The example below compares those scopes without assigning a price. Ask each provider to identify what is included, optional or excluded against your requirements before comparing the totals.
Scroll horizontally to see all columns
| Decision | Space planning model | Coordination model |
|---|---|---|
| Purpose | Room arrangement and major existing constraints | Defined interfaces for multidisciplinary coordination |
| Elements | Agreed walls, openings and major structure | Same base scope plus named equipment and MEP categories |
| Geometry | Agreed simplification of observed surfaces | Agreed representation at critical offsets and connections |
| Information | Basic category and level organization | Specified systems, identifiers and parameter fields |
| Review | Checks suited to the stated planning use | Documented checks at selected interfaces and sampled areas |
| Revisions | Defined correction and comment allowance | Defined coordination review stages and issue closure |
Part 6 of 7
Specify quality review, comments and revision boundaries
Ask which elements receive model-to-cloud checks and what review record comes with the delivery. The proposal should explain the acceptance criteria and how exceptions will be reported. Compare this work alongside the modeling scope: a lower total may reflect fewer included elements, less detailed checking or a different revision allowance.
Separate correction of a deliverable that misses agreed requirements from new scope requested later. Adding a previously excluded pipe system, changing the coordinate basis or replacing the reference cloud can create additional production and review work. Identify the number of comment rounds, who consolidates comments and how changed inputs will be assessed before they affect the schedule.
Part 7 of 7
Prepare your files for a Scan-to-BIM quote
Provide the scope matrix, reference files and intended use together. Flag the required delivery date and any staged areas, dependencies or review deadlines. If the supplier cannot inspect the entire dataset initially, ask what assumptions remain provisional and what would change the estimate after the full input review.
Review the total against the same deliverables, exclusions and acceptance requirements. Your quote should state what is included, what is excluded and which questions still need an answer. If your site has not yet been scanned, start with our laser scanning quote guide. This guide covers modeling from a point cloud you already have.
- Supply the cloud revision, coverage record, coordinates and available quality information.
- List included categories, feature sizes, properties and geometric requirements.
- Confirm application versions, deliverable formats, review evidence and comment rounds.
- Identify missing inputs, exclusions and the process for changes to scope.
Compare Scan-to-BIM quotations against the same deliverable, input condition and review scope. Send us your available cloud, a marked scope and the intended use so we can identify the preparation, modeling and checks your project needs before work begins.