More Sharing Options
Key Points
FARO SCENE Registration Workflow: From Raw Scans to a Reviewed Point Cloud
A FARO SCENE workflow starts by preserving raw scans and grouping them into useful clusters. Process the scans, then register them using targets, cloud-to-cloud constraints or a combined method. Review the scan network and its agreement with survey control. Document and approve the result before creating point clouds or exports. Automatic registration still needs a quality review.
Our Approach
How we help your team
Your design team needs scan data that fits together and arrives in a usable form. Our FARO-certified team manages the SCENE workflow from source files through registration review and delivery, with checks tied to your project requirements.
Our FARO-certified team keeps the source scans intact and organizes the project. We define the registration strategy, then review the scan network and survey control. We approve the registration before exporting customer files. The handoff includes the agreed data in a clear, usable structure.
Part 1 of 7
Begin with project structure and an untouched source copy
Copy field data to protected project storage and preserve an untouched source set before processing. Record scanner serials, firmware, field notes, station naming, capture date, units and any survey control files. Confirm the SCENE version required by the hardware; FARO states that SCENE 2022 or later is required for Focus Core and Focus Premium data, while its 2026 production list identifies SCENE 2026.1.
Organize scans into clusters that reflect floors, zones, buildings or logical registration groups. A clear hierarchy makes large projects easier to diagnose and lets the team isolate a weak area without losing the relationship to the whole network.
Part 2 of 7
Process scans deliberately
Processing can include target detection, colorization, filters and preparation for registration. SCENE supports automatic searches for spheres, checkerboards, coded markers and natural references, along with dark-point, stray-point, edge-artifact and moving-object filtering options. Apply settings that match the site rather than treating every filter as mandatory.
Keep enough source information to reproduce the result. Aggressive filtering can remove useful edge or low-reflectivity data, while insufficient filtering can make cloud-to-cloud relationships noisier. Check representative scans before batch processing the full project.
Part 3 of 7
Choose the registration relationship that fits the site
Target-based registration uses detected spheres, checkerboards, coded markers or other references. Cloud-to-cloud registration uses overlapping surface geometry. Survey control relates references to known coordinates. FARO describes Hybrid Registration as a way to combine control points with cloud-to-cloud registration, and Interactive Registration exposes the network of scan connections so users can inspect and influence automatic results.
No method eliminates planning. Repetitive corridors, moving machinery, vegetation, water, reflective surfaces and limited overlap can create false or weak relationships. A robust project may use different methods in different zones while preserving one documented coordinate strategy.
Scroll horizontally to see all columns
| Method | Useful when | Primary review question |
|---|---|---|
| Cloud-to-cloud | Adjacent scans share distinctive stable surface geometry | Is overlap well distributed, or is the solution constrained by one repetitive or narrow area? |
| Targets | Artificial references can be placed and observed from multiple stations | Are targets distributed in three dimensions and identified correctly? |
| Survey control | The project must relate to known coordinates or limit network drift | Are units, target IDs, coordinate order and residuals correct? |
| Hybrid | Geometry and controlled references should contribute together | Do control and local scan relationships agree without forcing a distorted network? |
Part 4 of 7
Build a redundant scan network
Connect adjacent scans through multiple defensible relationships and close loops where the site permits. A registration that depends on a single bridge scan or a long unclosed chain is more vulnerable to accumulated orientation and position error. Interactive Registration is useful because the graph makes isolated scans, questionable links and weak zones easier to find.
Manual correspondence tools can help locate, clear or force a relationship, but a forced correspondence is not automatically correct. The operator should verify the actual common feature in panoramic and 3D views and avoid using a manual link to hide inadequate field overlap.
Part 5 of 7
Optimize, inspect and compare against control
Run the appropriate optimization after the intended links and constraints are established. Then inspect the full project and local zones. Review connection quality, scan poses, matched objects, point distances, tension, control residuals, inclinometer use and representative sections through planar and detailed geometry.
FARO's registration report documentation explains that tension describes discrepancy between corresponding references in the global coordinate system and that values close to zero indicate better agreement. It remains one diagnostic among several; a low summary value does not prove complete coverage or eliminate a localized mismatch.
Part 6 of 7
Create downstream data only after approval
Once the registration and coordinate basis are approved, create project point clouds, regions or exports required by the receiving workflow. SCENE supports project, cluster, scan and section exports, including Autodesk RCP/RCS, and provides other import/export options documented for the installed version.
Record which scans and clips are included, the units and coordinate basis, and whether station structure, imagery or filtering is preserved. Keep the approved SCENE project and report alongside the exported derivative so future questions can be traced to the source registration.
Part 7 of 7
What a professional SCENE handoff should contain
A defensible handoff includes the approved project or agreed native data, requested exchange files, a registration or QA summary, coordinate and unit notes, capture limits, exclusions and software version information. For a large project, a zone map and file manifest save the receiving team substantial time.
The exact deliverable should be established before processing. A beautiful visualization is not a substitute for a tested dataset that opens in the recipient's software and aligns to the project coordinate framework.
Use SCENE's automation to accelerate processing, then approve the project through network, correspondence, control, coverage and downstream compatibility review.