Model and facility context
A BIM model helps locate equipment, systems and spaces and connect them with agreed information.
LiDAR · BIM · Autodesk Tandem · APS
Digital Twin: a model connected to information.
A digital twin connects a spatial view of a facility with information about its systems and equipment. It can start with an existing BIM model or documentation captured through 3D scanning. We agree the intended outcomes, information requirements and update rules for each project.
Discuss your Digital TwinFrom a real facility to a model
LiDAR 3D scanning and cloud-ready models.
We capture the geometry of existing spaces and systems, then select a data-preparation workflow suited to the Digital Twin project.
LiDAR scanning
LiDAR-equipped cameras and scanners capture the facility's geometry; photographs can also be collected where needed.
Point cloud and verification
Scan data is organised and verified using tools suited to its format, required accuracy and project scope.
Cloud photo processing
Where agreed, the Autodesk Platform Services (APS) Reality Capture API uses photogrammetry to create 3D models from photographs in the cloud.
A viewable model
Models in supported formats can be prepared for Autodesk Viewer using the APS Model Derivative API.
A LiDAR scan or photo-derived 3D model is not automatically a BIM model. Tools, formats, data access, retention and any BIM modelling are agreed separately. This page does not accept scan uploads or let visitors start processing.
Explore the 3D model
Open the Tandem facility or a separately configured APS model. Autodesk sign-in and model permissions are required. The viewer connects to Autodesk only after you select it; access tokens remain in memory and are not saved in browser storage.
From documentation to operations
Autodesk Tandem as a digital-twin environment.
A BIM model is a starting point, not a finished Digital Twin. Operational value depends on data quality, links to assets and a process for keeping information current. Model preparation, configuration and integration scope are agreed individually.
Structured asset information
Identifiers, properties and equipment information form a foundation for operational handover and subsequent maintenance.
Agreed integrations
Connections to BMS, IoT, service or ERP systems require interface verification, data access and agreed update responsibilities.
Support for operations workflows
Consistent links between the model and information can support asset identification, documentation access and service workflows.
The Tandem Data API supports reading BIM model data and reading and writing custom schema properties. External-system connections are scoped separately after reviewing APIs, data quality and permissions. Publishing a model alone does not provide real-time telemetry.
Autodesk Tandem Data API — documentationHow we work
A clear scope from the start.
- 01
Outcomes and scope
Define users, workflows, required assets and acceptance criteria.
- 02
Model and data
Review the BIM model or scan data, identifiers, required attributes and input data quality.
- 03
Configuration and integrations
Agree the Tandem environment, permissions, data sources and feasible information flows.
- 04
Testing and handover
Verify links and information access, and establish ongoing maintenance responsibilities.
Publishing a model alone does not enable real-time telemetry or BMS integrations. Each connection requires agreed sources, configuration, permissions and maintenance responsibilities. Tandem access and Autodesk permissions remain customer-managed.