CoreBIM converts 2D documentation and registered point clouds into coordinated Revit models — architectural, structural and MEP — at the level of development your project actually needs, with a clash-checked federated file at handover.
Take one service or the whole chain — the delivery standard does not change: one scope sheet, weekly issues, and a check against the source data before anything reaches you.
Drawings or registered scans become one coordinated architectural, structural and MEP model at LOD 100–400, authored under a single scope sheet with one QC record and one point of contact.
PDF, DWG or scanned paper sets rebuilt as a parametric Revit model — walls, floors, structure, MEP routes and families — with sheets and schedules that read back to your original set.
Registered scans modeled as as-built geometry to a stated deviation tolerance, checked in Undet against the cloud, and issued with the RCP linked so every element stays verifiable.
Raw stations from Leica BLK360, RTC360, BLK2GO or any scanner registered in Cyclone REGISTER 360 into one coordinate-correct cloud — cleaned, decimated and reported with per-station residuals.
Mechanical, electrical, plumbing and fire protection modeled as connected, system-aware geometry — sized, routed and clash-ready, so the model carries coordination rather than visualization alone.
Model output turned into an issuable drawing set — plans, sections, elevations, details and schedules on your title block, annotated to the standard your permitting authority expects.
Parameters for the three modeling routes below. MEP Modeling and construction documentation are scoped against the model they are built from and confirmed on the same sheet.
| № | Parameter | 2D to BIM | Point Cloud to BIM | Registration |
|---|---|---|---|---|
| 01 | Level of development | LOD 100–400 | LOD 100–400 | — |
| 02 | Geometric tolerance | Per drawing set | ±5 mm to cloud | ≤ 4 mm residual |
| 03 | Typical turnaround | 1 week, two-storey house | 1–2 weeks, typical house | 2–4 working days |
| 04 | Clash review included | Yes, federated | Yes, federated | Residual report |
| 05 | Revision rounds | Two | Two | One |
Parameters are per-project and confirmed in writing before work starts.
Four stages, each with a defined output you can check before the next one begins.
Raw scan stations are imported, registered and cleaned into one coordinated point cloud, aligned to your project coordinate system with stray and duplicate data removed.
Output Registered cloud and deviation reportThe verified cloud is built into Revit or drafted in AutoCAD at the agreed LOD and tolerance, discipline by discipline, using your template, naming convention and worksets.
Output Weekly model issues for reviewEvery model and drawing is checked back against the point cloud and the agreed scope: dimensional deviation, clashes, categorization, layers, worksets, levels and grids.
Output QC checklist, signed off internallySheets, schedules and annotations are produced to your drawing standard and issued as native files plus IFC, with two revision rounds included after handover.
Output Submission-ready set, native and IFCEvery project is issued as a native file and an open exchange copy at no additional charge. Where a BEP or practice template applies, the model is authored in it from the outset rather than converted at handover.
Files are purged, named to ISO 19650 status codes and version-stamped before issue. Additional formats can be produced on request and confirmed in the scope sheet.
| № | Deliverable | Format | Notes |
|---|---|---|---|
| 01 | Federated model | RVT | Revit 2020–2027, linked by discipline |
| 02 | Exchange model | IFC 2x3 / IFC 4 | Mapped to your classification system |
| 03 | Registered cloud | RCP / RCS | Unified and georeferenced to site control |
| 04 | Cloud exchange | E57 / LAS / LAZ | Full-resolution and decimated copies |
| 05 | Drawings | DWG / PDF | Plans, sections, elevations and details |
| 06 | Schedules | XLSX / CSV | Quantities and component data |
| 07 | Reports | PDF / XLSX | Registration residuals, deviation and clash log |
| Information management | ISO 19650 naming and status codes |
| Level of development | Stated per element, AIA-style LOD |
| Exchange | IFC 2x3 / IFC 4, mapped classification |
| Coordinates | Shared site control, survey point recorded |
| Your standards | BEP or practice template followed as issued |
| Modeling | Autodesk Revit 2020–2027 |
| Coordination | Navisworks Manage, BIM Collaborate |
| Cloud processing | ReCap Pro, Leica Cyclone, FARO Scene |
| Mobile capture | NavVis VLX, IVION datasets |
| Drawings | AutoCAD, published PDF sets |
Revit warnings reviewed and cleared, or listed with reasons at issue.
Model measured back against the cloud, worst-case figures published.
Federated hard and soft clash run before every issue, log attached.
Purged, named and version-stamped; workset structure documented.
Data is handled under NDA on request; scan data and models are held only for the agreed retention period.
Every project, every sheet we issued. Pick a project from the register and step through its sheets on screen. Title blocks and client stamps are removed; full sets are shared under NDA on request.
Sheet 1 / 6
Large-format warehouse surveyed across 156 setups and registered as one cloud — bundle error 0.005 m at 81% strength.
Cyclone REGISTER 360 · 156 setups · 405 links
Sheet 1 / 8
Clubhouse surveyed inside and out — each modeled view issued beside the point cloud it was built from.
Scan to BIM · model vs cloud, eight views
Sheet 1 / 4
Registered scan drafted as a full CAD set — basement, two floors and roof, dimensioned and annotated.
Floor and roof plans · one week
Sheet 1 / 4
Exterior views rendered from the modeled set, issued alongside the working drawings.
Rendered exterior views
Sheet 1 / 12
Retail unit converted to a wash tunnel — demolition, existing and proposed plans, elevations and details.
Permit set · plans, elevations, details
Sheet 1 / 2
Airport concession surveyed and drawn up as a fixture plan with four interior elevations.
As-built plan · interior elevationsScanner make does not matter. If the data is readable we will tell you what it supports before you commit to a scope.
Anything not covered here, call or send the drawings and we will tell you straight.
A drawing set or sample scan data, the disciplines wanted, and the level of development. If you have a BEP or a Revit template, send that too — we model in it.
Yes. We accept registered clouds from any scanner in RCP, RCS, E57, LAS or LAZ. If the registration is unverified we check residuals first and tell you what we find.
We state a tolerance per project and measure the finished model back against the cloud, publishing worst-case deviation rather than an average.
Every discrepancy is logged as we find it and raised before we assume. The log is issued with the model so decisions stay traceable.
Yes, before data transfer. Scan data and models are retained only for the agreed period, then deleted on confirmation.
Drawings, scan stations or a scope sheet — we come back with LOD, tolerance, turnaround and a fixed fee. Quotes inside one working day.