Realsee's BIM Model files(.rvt) are hand-built deliverables created from your scan data. Unlike automatically generated 3D meshes (OBJ/GLB), these are true design files: walls are walls, doors are doors, and every element carries the structure and naming your workflow depends on.
Revit models are best for BIM workflows, coordination, and downstream analysis.
1. What You Get
A LOD 200 as-built model of existing conditions, built from a laser scan.
Every order includes:
-
Native Revit model (
.rvt) — parametric, not traced linework -
IFC export (IFC 2×3 by default) for OpenBIM workflows
-
Registered point cloud (
.rcp/.rcs) — included at no extra charge, so you can check our work yourself -
PDF view exports — for quick preview
Optional add-ons: Built-in Casework；Furniture & Appliances；Visible MEP Fixtures
What it is: a reliable record of the building as it exists today, at LOD 200 geometry.
What it is not: a permit BIM, a construction/coordination model, an MEP engineering deliverable, or a code-compliance certification. If you need those, this is the accurate starting point — not the finished product.
2. Accuracy
Most accuracy disappointments come from one number that doesn't survive a tape measure. So instead of one number, here's how accuracy actually works — on two independent axes (per the USIBD LOA framework):
| Axis | What it measures | What determines it |
| Measured Accuracy | How closely the point cloud matches the real building | The scanning device (see device specs) and how the scan is captured |
| Represented Accuracy | How faithfully our model reproduces the point cloud | Our modeling standard |
Most "inaccurate model" experiences are Represented Accuracy failures — the scan was fine, but the modeler didn't reproduce it faithfully or didn't understand how buildings go together. That's the axis our modeling standard is built to control.
2.1 How we handle Represented Accuracy today
-
Our modeling standard requires elements to be built within 15 mm (5/8") of the point cloud on scanned surfaces — the LOA 20 working class.
-
If you find a deviation beyond that, we fix it free of charge.
-
We do not currently publish formal accuracy declarations, warranties, or verification reports. Those capabilities are on our roadmap — until then, we'd rather under-promise than hand you a number we haven't earned.
2.2 Relative, not absolute
We deliver relative accuracy — the correctness of dimensions within the building (a room's size, a wall's thickness, the distance between two columns).
We do not provide absolute accuracy (position in a site/survey coordinate system). If your project requires survey-grade absolute coordinates, that needs a surveyor with ground control — it's outside our service.
2.3 You can check our model yourself
The registered point cloud ships with every model, so you can run a model-to-point-cloud deviation check yourself (Verity, CloudCompare, or Revit's own tools) and see exactly where it lands. You don't have to take anything on faith.
2.4 Where the scan can't see
Occlusions and scan shadows are inevitable. Geometry we had to infer is noted per element inside the model (modeler notes) — disclosed, not silently modeled as if precise.
And before modeling starts, we check your point cloud; if it can't support the target quality, we tell you before we begin, not after.
3. Scope
Modeled by default: structural shell (foundations, exterior/interior walls, floors, roofs), vertical circulation (stairs), doors, windows, ceilings, curtain-wall glazing and skylights — all at LOD 200.
Modeling conventions that prevent the usual problems:
-
Walls come from a controlled type library keyed to real assemblies (not traced from scan noise); any genuine non-standard condition is modeled and noted, never left as an unexplained thickness.
-
Phasing — existing conditions are modeled on Revit's Existing phase, so you can build New/Demolition phases on top without rework.
-
Families are native Revit families matched to your building type — residential families for houses, commercial assemblies for commercial buildings.
Not modeled (unless added): furniture, visible MEP fixtures, detailed materials, signage/artwork.
4. Standards & Interoperability
-
Geometry: BIMForum LOD 200; Accuracy: USIBD LOA (v3.1, 2025)
-
Interop: native Revit
.rvt+ IFC (2×3 default; 4 on request) -
Families: native Revit only — no imported SketchUp/CAD geometry
-
Deliverable governed by a written LOD 200 As-Built modeling standard, so quality doesn't vary by modeler
5. Add-ons
| Category | Items |
| Base model (every order) | Exterior & interior walls, floors, roofs,ceilings, stairs, doors , windows, curtain-wall glazing, skylights, rooms/spaces |
| Add on: Built-in Casework | Kitchen cabinets & countertops, bathroom vanity cabinets, retail counters, reception desks, built-in wardrobes / walk-in closets — cabinet bodies only; sinks & faucets are plumbing, see Visible MEP |
| Add on: Furniture & Appliances | Movable furniture: sofas, dining tables & chairs, desks & office chairs, beds; Major appliances: washer, dryer, range/cooktop, dishwasher, refrigerator |
| Add on: Visible MEP Fixtures | HVAC: supply/return/exhaust grilles & diffusers; Lighting: downlights, linear & pendant fixtures; Electrical: panels, outlets/sockets (gang count noted) , TV/media outlets, doorbells; Safety: smoke/heat detectors; Ventilation: extract/exhaust fans; Plumbing fixtures: sinks, toilets, bathtubs, showers; Heating: radiators |
The three add-ons are independent — order any combination.
The registered point cloud is always included at no extra charge.
6. Acceptance & Warranty
-
Every model passes our internal QA before delivery — Revit audit, purge, warnings resolution, parameter completeness, and standards compliance.
-
Modeling tolerance: elements are built within 15 mm (5/8") of the point cloud on scanned surfaces.
-
Find something off? Report deviations beyond tolerance on scanned surfaces and we fix them free of charge.
-
Not covered by rework: inferred/occluded areas (noted in the model — there's no scan data to model against), expectations tighter than the 15 mm working tolerance, absolute/site-coordinate comparisons (we deliver relative accuracy only), and — for self-captured orders — issues caused by the point cloud itself.
-
A formal acceptance and warranty framework (accuracy declarations, verification reports) is on our roadmap.
7. Delivery time
Standard delivery is tiered by floor area.
|
Area
|
Delivery time - business days
|
|
0 – 1000 sqft
|
6 - 10
|
|
1000 – 2,000 sqft
|
6 - 10
|
|
2000 - 3000 sqft
|
6 - 10
|
|
3000 - 4000 sqft
|
8 - 12
|
|
4000 - 5000 sqft
|
8 - 12
|
|
5,000 – 10,000 sqft
|
8 - 12
|
|
10,000 - 20,000sqft
|
12 - 18
|
|
20,000 - 30,000sqft
|
14 - 22
|
8. FAQ
1. Does point-cloud accuracy equal model accuracy?
No — they're separate axes (Measured vs Represented).
A great scan can still yield a poor model if it isn't reproduced faithfully.
Our modeling standard controls the reproduction, and we ship the point cloud so you can check it.
2. Can I check the model against the original point cloud?
Yes. The registered point cloud ships with every model — run a deviation check in Verity, CloudCompare, or Revit's own tools.
A formal verification report from us is on the roadmap.
3. Is your accuracy model-vs-actual-building or model-vs-point-cloud?
Our 15 mm modeling tolerance is defined model-vs-point-cloud. How well the point cloud matches the actual building (Measured Accuracy) depends on the scanning device and capture.
We deliver relative accuracy; absolute/ground-truth positioning needs survey control, which is outside our service.
4. What if my point cloud isn't good enough?
We tell you at intake, before modeling — you can re-capture, or we proceed at a quality level the data supports, agreed in writing. Areas the data can't support are noted in the model, not faked.
5. Why did another vendor's model measure 15'3" on a 15' room?
That's ~1.6% error — no scanner spec'd at 1/4"/100' produces it.
It's a registration/scale failure or a model never built to the cloud.
It's exactly why we ship the point cloud with the model: so you can check it.