Baserton
Book a call Send a scan

Scan-to-BIM modelling, delivered to your specification.

Send a registered point cloud. Get back native Revit, IFC or DWG at the LOD you specify, checked against the scan and ready to issue under your name.

Point cloud of a process manifold: four rows of pipe outlets on a steel frame, captured by mobile LiDAR.

Scan: the registered point cloud, before any modelling.

40,431 points shown

Fig. 0Process manifold EQ-01, section A: eight columns of outlets in four rows on a 2.26 m frame. From a mobile LiDAR scan, subsampled for the web. The model demonstrates the levels of development; it is not a checked survey deliverable. Drag to turn it.
You send
Registered point clouds from any scanner
You get
RVT, IFC and DWG on your own template
Checked
A deviation report with every model

Capture takes a day. Modelling takes the month.

Your crews can capture and register a site in a day or two. Then the scan waits for modelling time, because modelling is where the hours go: every wall, duct, pipe and pump traced from the points by hand, then checked, then fixed.

Most survey firms have three ways to handle the queue:

  1. Hire and train more Revit modellers, and keep them busy between peaks.
  2. Turn work away when the queue is full.
  3. Send it offshore, then spend evenings checking what comes back.

Baserton is a fourth way: we do the modelling, to your standard and behind your name. You keep the scanner, the client and the invoice.

What you send

Inputs for a modelling job
ItemWhat we need
Point cloudRegistered scans from any scanner, including Leica, FARO, Trimble, NavVis and Z+F. E57, RCP/RCS, LAS/LAZ or PTS.
ScopeThe area, the element categories and the LOD for each. Add an LOA band if your contract specifies one.
Your standardsYour Revit template, families, naming and title block, so the model drops straight into your deliverable.
Site contextPhotos, field notes and any existing drawings. Optional, always useful.
TransferA share link from your own storage, or an upload link from us. Large files are expected.

What comes back

RVT

Native Revit

Built on your template, with your families, worksets and naming. Opens in Revit as if your own team had modelled it.

IFC

Open BIM

For coordination, model checking and clients who work outside Revit.

DWG

Drawings

Plans, sections and elevations cut from the model, on your title block.

You set the level of development for each category

Levels of development
LODWhat is modelledTypical use
200Generic elements at approximate size, shape and position.Space planning, early feasibility
300Specific elements at their measured size, shape, position and orientation.Design, coordination, as-built record
350LOD 300 plus the connections, supports and interfaces between elements.Trade coordination, clash detection

LOD terms follow the BIMForum Level of Development Specification. If your contract defines levels differently, send the definition with the scope and we model to it. Fig. 0 steps a real scan through LOD 100 to 300.

Plant rooms, production lines and process equipment

Most scan-to-BIM work stops at walls, floors, ducts and pipes. Equipment-heavy sites are where modelling hours pile up, and we take them on as standard: manifolds, conveyors, skids, tanks, racking and the pipework between them, each modelled as its own object with its own schedule entry.

Equipment schedule from the factory floor demo
DrawingTagElementCountModelled as
Drawing of the process manifoldEQ-01Process manifold1Frame and 60 outlets in four rows
Drawing of the roller conveyorEQ-02Roller conveyor, straight run1Frame, legs and 56 rollers
Drawing of the caged IBC tote on its palletEQ-03IBC tote, caged35Pallet, cage, tank and cap
Drawing of the IBC tote with a valve outletEQ-04IBC tote with valve outlet9Pallet, tank, valve and handle
Drawing of the steel drumEQ-05Steel drum5Body, rolling hoops and lid
Fig. 4.1Equipment schedule for the factory floor that Fig. 0 is cut from. Counts come from the model, and each drawing is rendered from it.

Every element checked against the points

Before a model ships, we compare it with the scan it came from. The deviation report lists every element: how many points support it, how far the model sits from them, and anything we had to infer rather than measure, such as a face hidden behind equipment. You see the evidence before your client does.

Deviation report · what each model ships withOne row per modelled element. The values come from your scan.
Contents of the deviation report
ColumnWhat it tells you
ElementEach modelled element, by the tag and name it has in your model.
PointsHow many scan points support it.
Median, 95th pct.The distance from those points to the model surface, in millimetres.
Against specThe element checked against the tolerance band in your scope: within, review or inferred.
InferredFaces with no points behind them, such as a wall hidden by a panel. They are modelled where you need them and always flagged.
Distances run from each scan point to the nearest model surface.Bands and LOA come from your scope.
Fig. 5.1The deviation report that ships with every model. Inferred elements are flagged and never presented as measured.

Your title block. Your client.

We don't scan, we don't bid and we never contact your client. Models arrive on your template, with your naming and your title block, ready to issue as your own work. How your data is handled is agreed with you before any scan moves.

Send one scan. Judge us on your own data.

  1. Day 0

    Send one completed, registered scan: a floor or a plant area. Include your template and the LOD you would specify for the job.

  2. Within 48 hours

    The model and its deviation report come back at that LOD, in your formats, on your template.

  3. After that

    If it meets your standard, we quote your next job from the scan and the scope, so you can price your bid with real numbers.

Pilot request

Tell us what you scan. We'll reply by email to set up the pilot.

Formats you deliver (any)
We use these details to reply to you about the pilot.

    Notes

    8.1
    Do you scan sites?
    No. We model scans you have already captured, so the site visit and the client relationship stay yours.
    8.2
    Which LOD and LOA can you work to?
    You set the LOD for each element category (clause 3). If your contract specifies LOA bands, tell us and the deviation report is checked against them (clause 5).
    8.3
    What state should the scan be in?
    Registered and cleaned the way you would hand it to your own modellers. E57 is the easiest to work with; the formats in clause 2 all work.
    8.4
    How do large scans reach you?
    By link: a share from your own storage, or an upload link we send you. Large files are expected.
    8.5
    Can you match our standards?
    Yes. Send your template, families, naming and title block with the pilot and the model is built on them.
    8.6
    How is a job priced?
    Per job, from the scan and the scope. The pilot gives you real numbers to price your bid with.
    8.7
    What happens to our data?
    That is agreed with you before any scan moves.