Skip to main content

Management and Support

1. Software Management

License Management

  • It requires a valid Leica Geosystems license, which is managed through the Leica Geosystems Common License Manager (CLM).
  • Monitor license availability, seat usage, expiration dates, and renewals.
  • Properly manage license borrowing to support offline or field usage.

User Management

  • Assign user roles (Admin, Operator, Viewer) according to organizational requirements.
  • Restrict access to sensitive or critical projects by using secure storage locations and permissions.

Version Control

  • Ensure all team members use the same version of REGISTER 360+ to prevent project compatibility issues.
  • Regularly apply Leica service packs and software updates.

Data Management

  • Store raw scan data (LGS, E57, BLK, PTS, and similar formats) on centralized servers or within the environment.
  • Maintain consistent naming conventions and structured folder hierarchies.
  • Enable project file versioning and routine backups to protect data.

2. Maintenance

  • Keep hardware drivers (GPU, storage, and related components) updated to maintain optimal performance.
  • Periodically clear cache and temporary files to improve processing efficiency.
  • Run database integrity checks on REGISTER 360+ projects to reduce the risk of corruption.
  • Verify the accuracy of scan imports and exports on a regular basis.

3. Support

Internal Support

  • Train team members on scanning workflows, registration processes, and publishing outputs such as TruView, JetStream, or LGS files.
  • Maintain internal documentation and troubleshooting guides for common issues.

Leica Support

  • Use the Leica Geosystems Knowledge Base for reference documentation and known issues.
  • Contact Leica Customer Care for support with licensing, renewals, and technical problems.

Community Support

  • Participate in Hexagon user forums and Leica Geosystems community groups.
  • Leverage online tutorials, training courses, and webinars for continuous learning.

4. Best Practices

  • Standardize project workflows and registration templates across teams.
  • Perform QA/QC checks after each registration cycle.
  • Archive completed projects for long-term storage and future reference.