Scan more, process less — turn captured data into project-ready deliverables.
Scanning takes a day. Modelling takes weeks, and difficult datasets come back unfinished.
What you get
Organized, usable models from E57 and RCP — including proxy-object cleanup, coordinate remediation and confined MEP zones.
Scanning takes a day. Turning the cloud into a model somebody can work in takes weeks — and the datasets that get abandoned are rarely the easy ones.
From registered E57 and RCP we produce organised Revit models at a stated LOD: real families with real parameters, not geometry that falls apart the first time somebody schedules it. Where a model already exists and has gone wrong, the work is remediation.
- Revit models from registered E57 and RCP, at an agreed and stated LOD
- Architectural fabric — walls, floors, ceilings, openings, structure
- MEP modelling in confined plant rooms, risers and ceiling voids
- Proxy-object cleanup: rebuilding imported junk geometry as real families
- Coordinate remediation — shared coordinates, project base point, survey point
- Deviation and accuracy reporting against the source cloud
Formats in
Formats out
Software
Where our work stops
We take the awkward jobs specifically. If it's straightforward volume work, a larger bureau will beat us on price.
A genuine limit, not a negotiating position. We compete on jobs that need judgment rather than throughput. Two hundred straightforward rooms on a deadline? A production bureau is the right answer, and we would rather say so now.
Agreeing the level of detail
Most disputes are an LOD that was never written down.
"As-built model" means one thing to the person paying and another to the person modelling. We agree the level in writing and state it on the deliverable.
| Level | What it means | Typically used for |
|---|---|---|
| LOD 200 | Generic placeholders, approximate size and location | Early feasibility and space planning |
| LOD 300 | Specific objects, accurate size, shape and location | The usual as-built request |
| LOD 350 | Adds interfaces and connections between systems | Coordination and clash detection |
| LOD 400 | Fabrication-level detail | Prefabrication and installation |
A model can be mixed — LOD 350 on services that need coordinating, LOD 200 on fabric that does not. Usually the cheapest honest answer.
The trial job
Send the dataset another vendor struggled with.
We reply within 24 hours and send a full written scope within two business days.
Specifically: the difficult one
The dataset another vendor returned unfinished. The plant room with 40 mm between services. The model whose shared coordinates stopped agreeing with the site survey three consultants ago.
Send it with a note on what went wrong. If it turns out to be straightforward we will say so, and point you at somebody cheaper.
Before you ask
What scanning contractors ask first
Why would we not just use a cheaper bureau?
For straightforward volume work you should, and we will say so. A large bureau on clean scans of a simple building will beat our price. Send us the job that came back unfinished, the plant room nobody wants to model, or the coordinate problem no one has traced.
What LOD do we need?
Most as-built requests are LOD 300. Coordination work usually needs LOD 350, because the interfaces between systems are the point. We agree the level in writing before starting and state it on the deliverable.
Do you register the scans?
We work from registered data as standard — registration belongs with whoever ran the scanner. If yours is incomplete or the targets did not work out, say so up front. Usually fixable, but it changes the scope.
What is a proxy-object problem?
Geometry imported from another package often arrives as unintelligent solids — correct in a view, but no parameters, unschedulable, and broken the moment anyone uses the model. Cleanup means rebuilding it as real families. Unglamorous, and a common reason a model gets abandoned.
Our model has a coordinate problem nobody can fix.
One of the jobs we want. Shared coordinates, project base point and survey point interact in ways that are easy to break and hard to unpick once several consultants have linked in. Send it with a note on what you expected and what you got.
Send a problem scan.
Send the dataset another vendor struggled with.
Reply within 24 hours. Written scope within two business days.