Give campus places and assets a useful digital context.
A digital twin can help teams understand a physical place, asset or system through a digital representation connected to relevant information. The right scope depends on the decisions to support, the models and data available, and how the representation will be maintained over time.
A model becomes a useful twin when four things are in place.
A 3D model alone is not a fully operational digital twin. These four ingredients decide whether a representation stays useful after the first demonstration.
- Ingredient
A model
Plans, BIM, GIS or other spatial data at a fidelity suited to the question.
- Plus
Connected data
Asset records and, where authorised and feasible, sensor or system feeds.
- Plus
An update process
An agreed way to keep the representation current as the campus changes.
- Plus
Named owners
People responsible for the data, the model and the decisions built on them.
Potential digital twin scopes
Start with a bounded scope. Each has dependencies that are assessed before it is offered.
| Scope | Possible use | Dependencies to assess |
|---|---|---|
| Building / space | Spatial context, room or area information, planning and selected operational views. | Building plans, BIM, GIS or other spatial data, permissions, update process. |
| Asset | Asset location, attributes, maintenance context and lifecycle information. | Asset register, identifiers, condition and history data, owner and maintenance process. |
| Infrastructure system | Selected views of systems such as utilities or building services. | System documentation, sensor or controller feeds where applicable, safe access and interfaces. |
| Campus / multi-campus | A joined view across selected buildings, assets or locations. | Consistent data model, local variations, permissions and governance. |
How to approach a digital twin project
Define the question
Name the operational or planning question the twin should help answer.
Choose a bounded first scope
Pick one place, asset group or system for the first phase.
Assess the inputs
Review model availability, data quality, identifiers, refresh needs and ownership.
Define users and views
Agree user roles, visualisation requirements and any connected workflows.
Agree pilot success criteria
Set measures, and decide how the representation will be kept current.
Evaluate before expanding
Review the pilot results, then decide whether to widen scope.
Set the right expectations
What to assume, and what not to assume.
- A 3D model alone is not a fully operational digital twin.
- Live data cannot be connected without technical and security review.
- A twin is not automatically real-time, predictive or autonomous.
- A model does not stay accurate without an agreed data-update and ownership process.
What a good first scope looks like
Typical traits of a pilot that can be judged fairly.
- One building, one asset group or one system.
- A named question and a named owner.
- Data that already exists and can be accessed.
- Success criteria agreed before work starts.
Explore a digital twin pilot for your campus.
Tell us which place, asset group or system you would start with. We will assess the models and data that exist and suggest a bounded first scope.