NavVis VLX3 Point Cloud Processing and Workflow Guide Malaysia
NavVis VLX3 Point Cloud Processing and Workflow Guide Malaysia
Capturing a building or industrial facility with a mobile 3D laser scanner is only the first stage of a professional reality capture project. The quality of the final deliverable also depends on point cloud processing, survey control, trajectory optimisation, data verification and export settings.
The NavVis VLX 3 Gen 3 wearable mobile 3D laser scanning system combines dual LiDAR sensors, panoramic cameras and Simultaneous Localization and Mapping (SLAM) to collect spatial information while an operator moves through suitable environments. After scanning, the recorded data must be processed into usable point clouds and associated imagery.
This NavVis VLX3 point cloud processing and workflow guide explains the main stages of mobile reality capture, from field preparation and data transfer to quality assurance, compatible file exports, Scan-to-BIM and facility management applications in Malaysia.
The exact software interface, processing options, export availability and computing requirements may vary by NavVis software version and licence. Operators should follow the current official documentation for their installed system.
What Is Point Cloud Processing?
A point cloud is a collection of three-dimensional coordinates representing measured surfaces in a physical environment. Each point typically contains spatial position information, while additional attributes such as colour may be available depending on the acquisition and processing workflow.
NavVis VLX 3 captures LiDAR observations and associated sensor information during a mobile survey. Processing estimates the scanner trajectory, combines measurements and produces spatial datasets suitable for visualisation, analysis and downstream applications.
Point cloud processing is not simply converting raw measurements into another file format. It includes trajectory estimation, spatial alignment, quality review and preparation of appropriate deliverables.
Poor scanning routes, incomplete coverage or unreliable control cannot always be corrected through software processing alone. Professional survey planning and independent checks remain essential.
Understanding the NavVis VLX 3 Data Workflow
A typical professional workflow begins with defining the project deliverables and survey accuracy requirements. The operator then plans scanning routes and suitable survey control before collecting data on site.
Captured data is transferred to an appropriate processing workstation, checked for completeness and processed using compatible NavVis software.
After processing, the point cloud should be reviewed for coverage, alignment and measurement reliability. Where required, suitable control information is incorporated into the processing or georeferencing workflow.
The approved dataset can then be exported in compatible formats and delivered for CAD, BIM, facility management or other supported applications.
Project documentation should record the scanning date, equipment, control information, processing configuration, known limitations and quality assurance results.
NavVis VLX 3 Gen 3 Technical Specifications
The manufacturer's 5 mm local point cloud accuracy specification refers to defined test conditions. It does not guarantee 5 mm absolute accuracy across every floor, building or industrial site.
Actual project quality depends on the scanning environment, route design, survey control, processing, coordinate alignment and independent verification.
Before planning a project, confirm the current manufacturer specifications and compatibility with the intended processing software.
System type | Wearable mobile 3D laser scanning system
LiDAR configuration | 2 x 32-layer LiDAR sensors
Maximum measurement rate | Up to 1,280,000 points per second per LiDAR sensor
Operational scanning range | Up to 50 m
Local point cloud accuracy | 5 mm under specified manufacturer test conditions
Panoramic cameras | 4 x 20 MP
Laser classification | Class 1
Display | 5.5-inch AMOLED touchscreen, 1920 x 1080
Portable storage | 1 TB SSD
System weight | Approximately 8.5 kg including two batteries
Typical operating time | Approximately 1.5 hours per set of two batteries
Operating temperature | 0掳C to 40掳C, non-condensing; thermal limitations apply
Ingress protection | IP42
Survey control support | Ground and wall control points
Point cloud exports | Including E57, LAS, PTS, XYZ, PLY and RCS, subject to workflow and software support
Step 1 - Define Project Requirements Before Scanning
Point cloud processing begins with understanding what the final dataset must achieve.
For general building documentation, the project may require a colourised point cloud and panoramic imagery. For Scan-to-BIM, the client may also require an agreed coordinate system, suitable geometric coverage and a specified modelling tolerance.
Industrial engineering projects may require additional control, targeted measurements and verification of critical equipment interfaces.
Identify the intended deliverables, site coverage, required accuracy, coordinate reference system, export formats and software compatibility before field capture.
Without these requirements, a visually impressive point cloud may still be unsuitable for the client's actual engineering task.
Step 2 - Plan the Scanning Route for SLAM
NavVis VLX 3 uses SLAM to estimate its movement through the environment while collecting LiDAR data.
A well-designed route should include sufficient geometric features, appropriate overlap and loop closures where practical.
Repeated corridors, similar-looking rooms, long feature-poor passages and large open areas can make trajectory estimation more challenging.
Operators should plan routes around visible structural features and ensure that important spaces are captured from appropriate viewpoints.
Moving machinery, pedestrians, reflective surfaces and temporary obstructions may affect data quality.
Where a survey covers several floors or disconnected areas, plan how the datasets will be connected and verified using appropriate control.
Step 3 - Establish Survey Control and Check Points
Survey control helps connect the point cloud to a project coordinate system and provides a means to assess measurement reliability.
NavVis VLX 3 supports ground and wall control points. Control coordinates should be established using suitable survey methods and checked for consistency.
Distribute control appropriately across the project, particularly for large buildings, multi-floor environments and industrial facilities.
Where possible, reserve independent check measurements that are not simply reused as processing constraints.
Control points and check points serve different purposes: control helps establish or constrain alignment, while independent checks help evaluate the resulting accuracy.
A local accuracy specification should never be substituted for an actual project-wide control and verification procedure.
Step 4 - Capture Data Using NavVis VLX 3
During field capture, the operator follows the planned route while monitoring the scanning system.
Maintain suitable walking speed, avoid unnecessary abrupt movement and ensure sufficient coverage of important areas.
Use additional passes or alternative viewpoints where equipment, furniture or structural elements block the scanner's view.
Panoramic imagery can provide useful visual context, but it does not replace close-up photography when small labels or equipment details must be recorded.
Before leaving the site, review available scanning feedback and confirm that the required areas have been captured.
Scanning must follow applicable site safety requirements. IP42 does not mean waterproof, and the system must not be assumed suitable for explosive atmospheres.
Step 5 - Transfer and Protect the Scan Data
NavVis VLX 3 uses portable SSD storage for captured data. After scanning, transfer the project files using the workflow specified in the current NavVis documentation.
Use a suitable workstation and preserve the original project data. Avoid changing or deleting raw files before successful transfer and backup.
Organise data by project, building, floor, scanning session and date so that datasets remain traceable.
Check that file transfer has completed successfully before clearing or reusing storage media.
For confidential commercial or industrial sites, follow the client's information security requirements. Restrict access to raw scans, panoramic imagery and sensitive facility layouts.
Step 6 - Select the Appropriate Processing Configuration
NavVis processing workflows may offer different processing configurations, including settings such as Dynamic, Eco 20 and Eco 40, depending on the installed software version.
These options may affect computational requirements, processing behaviour and output characteristics. They should not be interpreted as universal accuracy grades without reference to current official documentation.
Select a configuration according to the dataset, intended deliverables, available workstation resources and manufacturer recommendations.
NavVis documentation has recommended a processing workstation with approximately 192 GB RAM and at least eight physical CPU cores for VLX 3 workflows. Confirm current requirements before purchasing or configuring a workstation.
Record the processing configuration used so that project results can be reproduced and reviewed.
Step 7 - Process SLAM Trajectory and Point Cloud Data
The processing workflow estimates and refines the mobile scanner trajectory using the recorded observations and supported processing methods.
LiDAR measurements are combined to generate a spatial point cloud. Depending on the workflow, panoramic imagery and colour information may also be associated with the resulting dataset.
Loop closures, environmental geometry and survey control can contribute to spatial consistency.
Processing should be reviewed for trajectory problems, discontinuities, duplicated geometry and alignment inconsistencies.
Software processing cannot guarantee that a poorly captured or insufficiently controlled dataset will meet the required survey tolerance. Rescanning or additional measurements may be necessary.
Step 8 - Align the Point Cloud to Project Coordinates
Many engineering and BIM projects require point clouds to use an established coordinate reference system rather than an arbitrary local origin.
Coordinate alignment may involve surveyed control points, a project transformation or other supported georeferencing procedures.
Verify the coordinate units, axis orientation, elevation reference and transformation parameters before exporting the dataset.
Where a building uses a local grid, confirm how that grid relates to architectural drawings, structural models and other survey data.
Incorrect coordinate alignment can cause significant downstream errors even when the local point cloud geometry appears visually correct.
Step 9 - Perform Point Cloud Quality Assurance and Quality Control
Quality assurance is one of the most important stages of professional reality capture.
Review whether the point cloud covers the required spaces, whether important surfaces are sufficiently represented and whether there are visible registration problems.
Check the relationship between separate scanning sessions, floors and building sections.
Compare selected point cloud measurements with independent survey observations or known dimensions where appropriate.
Document missing areas, occlusions, reflective surfaces and features that cannot be measured reliably.
Acceptance should be based on the project's agreed requirements, not only on whether the point cloud looks visually complete.
Point Cloud QA/QC Checklist
1. Confirm Survey Coverage: Check that all agreed rooms, corridors, plant areas and relevant surfaces have been captured.
2. Review Trajectory Quality: Identify potential SLAM drift, discontinuities or alignment problems.
3. Check Survey Control: Verify the control network and inspect the quality of coordinate alignment.
4. Use Independent Check Measurements: Compare selected positions or distances against observations not used solely to constrain processing.
5. Inspect Multi-Floor Alignment: Confirm that floors, stairwells and connected spaces are consistently positioned.
6. Review Reflective and Transparent Surfaces: Identify areas affected by glass, polished metal or other problematic materials.
7. Check Critical Dimensions: Verify engineering-critical features using suitable measurement methods.
8. Record Processing Settings: Document software version, processing configuration and relevant transformations.
9. Document Known Limitations: List occlusions, missing areas and surfaces requiring additional investigation.
10. Approve Deliverables: Confirm that exported files meet the agreed scope, accuracy and compatibility requirements.
Step 10 - Export Point Clouds in Suitable Formats
After processing and verification, the dataset can be exported in formats supported by the selected NavVis workflow.
Different formats serve different purposes. Some are intended for general point cloud interchange, while others are associated with specific software ecosystems.
Before export, confirm whether the client requires colour information, coordinate metadata, structured scans, point attributes or particular software compatibility.
File format alone does not guarantee that all project information will transfer correctly. Test the exported dataset in the intended receiving application.
E57 | Common point cloud interchange format | Check structure, colour, coordinates and importer support
LAS | Widely used LiDAR point data format | Check scale, offsets, attributes and software compatibility
PTS | Text-based point cloud exchange format | Can create large files; verify coordinate precision
XYZ | Basic coordinate-based point data | Attribute and metadata support varies
PLY | Point cloud or mesh-oriented interchange | Check supported attributes and import settings
RCS | Autodesk-oriented point cloud workflow | Confirm export or conversion support for the installed software
E57 vs LAS vs PTS - Which Format Should You Use?
E57 for General Reality Capture Exchange
E57 is commonly used to exchange point cloud data between different reality capture and modelling applications.
It may be suitable for building documentation and Scan-to-BIM workflows, subject to the receiving software's implementation.
LAS for LiDAR Data Workflows
LAS is a widely recognised format for storing LiDAR point records and associated attributes.
It may be useful where the receiving application supports LAS and the required coordinate and attribute information.
PTS for Text-Based Exchange
PTS is used in some point cloud workflows as a text-based representation.
Large datasets can result in substantial file sizes. Confirm formatting and coordinate precision with the recipient.
XYZ for Basic Coordinate Transfer
XYZ is useful when simple three-dimensional coordinate data is required.
Because XYZ conventions vary, confirm delimiters, units, coordinate reference and optional attributes.
PLY for Supported Point Cloud Applications
PLY can store geometric point information and certain attributes, depending on implementation.
Check the receiving software before selecting it as a project deliverable.
RCS for Compatible Autodesk Workflows
RCS may be used in workflows involving Autodesk point cloud tools.
The availability of direct export or conversion depends on the installed software and supported processing pipeline.
Step 11 - Import Point Clouds into CAD and BIM Software
Processed point clouds can be used as references in compatible CAD and BIM applications.
Before import, verify coordinate units, scale, orientation and the relationship to existing project drawings.
Large datasets may need cropping, segmentation or other preparation to improve navigation and modelling efficiency.
BIM teams can use point cloud geometry to model visible walls, floors, columns, structural elements and building services.
However, NavVis VLX 3 does not automatically generate a complete BIM model. Element classification, modelling, interpretation and quality assurance are separate professional tasks.
Concealed pipes, hidden structural connections and other inaccessible elements cannot be reliably modelled from LiDAR observations alone.
Step 12 - Use NavVis IVION for Spatial Data Management
NavVis IVION provides a platform for visualising and collaborating around supported reality capture datasets.
Depending on software licensing and configuration, users can navigate panoramic imagery, inspect spatial information and work with location-based project content.
NavVis IVION can be useful for building owners, facility managers, BIM teams and engineering consultants who need to review captured spaces without directly operating the scanner.
Access permissions, data sharing and software integrations should be planned according to the project's security and information management requirements.
NavVis IVION does not automatically convert point clouds into validated engineering models or provide live asset monitoring without additional systems and integration.
Point Cloud Processing Applications in Malaysia
Commercial Building As-Built Documentation
Processed point clouds can support documentation of offices, shopping malls, hotels, hospitals and other accessible commercial interiors.
Industrial Plant and Factory Mapping
Spatial datasets can provide references for plant layouts, machinery surroundings, production areas and accessible building services.
Warehouse and Logistics Facilities
Point clouds can assist with spatial documentation of warehouse interiors, circulation areas and facility layout planning.
Construction Progress Documentation
Reality capture can support periodic recording of visible site conditions. Consistent control and repeatable workflows are important for comparisons over time.
Renovation and Retrofit Planning
Existing-condition point clouds can support design coordination before building modifications or equipment upgrades.
Scan-to-BIM and Digital Building Models
Point clouds provide geometric references for compatible BIM authoring workflows. Model production and validation remain separate tasks.
Facility Management and Digital Records
Organised point clouds and panoramic imagery can contribute to long-term building documentation and spatial data management.
Common NavVis VLX 3 Processing Problems and Troubleshooting
Problem 1 - Point Cloud Misalignment
Possible causes include SLAM trajectory problems, insufficient route overlap, unsuitable control distribution or inconsistent coordinate transformations.
Review the processing report, control information and independent checks. Additional scanning may be required.
Problem 2 - Missing Surfaces
Occlusions, limited viewpoints and inaccessible spaces can create incomplete coverage.
Review the original capture and consider additional scanning from suitable locations.
Problem 3 - Repetitive Corridor Distortion
Long corridors with similar geometry can challenge SLAM localisation.
Improve route planning, loop closure opportunities and control distribution in future capture sessions.
Problem 4 - Reflective Surface Artefacts
Glass, mirrors and polished materials can produce unreliable or missing LiDAR returns.
Identify affected areas and verify critical geometry using suitable supplementary methods.
Problem 5 - Incorrect Coordinate Alignment
Unit mismatches, incorrect transformations or control errors can shift the entire dataset.
Verify coordinate reference information, axis conventions and transformation settings.
Problem 6 - Very Large Processing Files
Extensive projects can create demanding processing and storage requirements.
Use a workstation that meets current manufacturer recommendations and manage project data systematically.
Problem 7 - BIM Import Problems
Point clouds may import with incorrect scale, position, colour or unsupported attributes.
Check export settings, file format compatibility and the receiving software's coordinate handling.
Problem 8 - Inconsistent Multi-Session Data
Separate scanning sessions may require careful registration and shared survey control.
Validate session alignment before combining datasets or using them for engineering measurements.
Point Cloud Processing Best Practices
1. Plan for the Deliverable: Define project accuracy, software requirements and expected outputs before scanning.
2. Use Appropriate Survey Control: Establish control and independent checks according to the site and project requirements.
3. Capture Sufficient Overlap: Plan routes and viewpoints that support reliable spatial alignment.
4. Protect Original Data: Keep verified backups of raw files and record scanning sessions.
5. Document Software Settings: Record processing software versions, configurations and transformations.
6. Inspect Processing Results: Review coverage, trajectory quality and registration consistency.
7. Verify Critical Geometry: Use independent measurements where errors would affect engineering or construction decisions.
8. Test Exported Files: Confirm compatibility, scale and coordinate alignment in the target application.
9. Maintain Revision Control: Identify dataset versions and record updates after renovation or construction.
10. Deliver QA Records: Provide known limitations and verification results alongside the final point cloud.
NavVis VLX 3 Point Cloud Workflow Across Malaysia
Kuala Lumpur and Selangor: Office towers, shopping malls, industrial facilities and commercial renovation projects are potential applications for professional point cloud processing.
Johor: Manufacturing plants, logistics facilities, warehouses and commercial developments may require reality capture datasets.
Penang and Kedah: Electronics factories, technical facilities and industrial building upgrades may use point clouds for documentation and BIM workflows.
Melaka and Negeri Sembilan: Factory expansion, engineering retrofit and building renovation projects may benefit from processed spatial data.
Perak, Pahang, Kelantan, Terengganu and Perlis: Institutional buildings, industrial premises and infrastructure-related facilities may require professional 3D documentation.
Sabah and Sarawak: Commercial buildings, industrial plants and facility modernisation projects may benefit from appropriately verified point cloud datasets.
These examples describe potential applications, not claims of completed MTM Precision NavVis VLX 3 projects.
Frequently Asked Questions About NavVis VLX 3 Processing
What happens after scanning with NavVis VLX 3?
The captured data is transferred to a compatible processing environment, processed into spatial datasets, checked for quality and exported for the intended application.
Does NavVis VLX 3 generate point clouds?
Yes. Processed NavVis VLX 3 data can produce point clouds and associated visual documentation using the appropriate software workflow.
What is SLAM processing?
SLAM estimates the scanner trajectory and spatial relationships while using recorded sensor observations. Its performance depends on environmental geometry and capture quality.
Can NavVis VLX 3 export E57 files?
E57 is among the supported point cloud formats. Confirm the specific export workflow and software version.
Can NavVis VLX 3 export LAS and PTS?
LAS and PTS are supported within appropriate NavVis point cloud workflows. Verify availability and settings in the installed software.
Does point cloud processing improve accuracy automatically?
Processing can refine alignment, but it cannot guarantee that a dataset meets project tolerances. Control and independent verification remain necessary.
Is the NavVis VLX 3 5 mm accuracy guaranteed for an entire site?
No. It is a local point cloud accuracy specification under defined manufacturer test conditions, not a universal absolute accuracy guarantee.
How much RAM is recommended for processing?
NavVis documentation has recommended approximately 192 GB RAM for VLX 3 processing workstations. Check current official requirements for the selected workflow.
Can NavVis VLX 3 point clouds be used in BIM?
Yes. Compatible exports can support Scan-to-BIM, but BIM modelling and validation require separate professional work.
Can NavVis IVION display processed reality capture data?
Yes, through supported workflows and software configurations. Available features depend on licensing and deployment.
What if the point cloud is misaligned?
Review control, trajectory quality, processing settings and coordinate transformations. Rescanning or additional measurements may be necessary.
Can point clouds detect hidden pipes or cables?
No. LiDAR cannot see through solid walls, ceilings or floors. Concealed services require other investigation methods.
How to Choose a NavVis VLX 3 Processing Workflow in Malaysia
Before selecting processing software or purchasing a mobile mapping system, identify the intended project deliverables and the software used by your clients.
Confirm the required coordinate system, point cloud formats, accuracy verification procedures and BIM compatibility.
Review the expected data volume, workstation requirements, processing resources, storage capacity and information security arrangements.
For engineering and construction projects, establish clear quality assurance criteria before scanning rather than relying only on visual point cloud appearance.
A well-designed workflow combines appropriate field capture, survey control, processing, independent checks and documented deliverables.
Contact MTM Precision for NavVis VLX 3 Malaysia
Looking for a NavVis VLX 3 Gen 3 wearable mobile 3D laser scanning system for point cloud processing, building surveys, industrial mapping or Scan-to-BIM in Malaysia?
Contact MTM Precision Sdn Bhd to discuss your project size, scanning environment, survey control, processing workstation, software compatibility and required output formats.
Send your project scope, site plans, preferred point cloud formats and accuracy requirements via WhatsApp for a product and application enquiry.
MTM Precision Malaysia Contact Information
MTM Precision Sdn Bhd
Showroom & Service Centre: No 29-1 & 2, Jalan Bandar 18, Pusat Bandar Puchong, 47160 Puchong, Selangor, Malaysia.
Tel: 03-8080 7172
WhatsApp: +6016-660 7346
Email: mtmpre@yahoo.com
Website: www.mtmpre.com.my
WhatsApp: https://wa.me/60166607346
Email: mtmpre@yahoo.com
Website: https://www.mtmpre.com.my
19 Oct 2026