Digital Twin Requirements & Project Readiness Checklist
A successful digital twin starts with the right objectives, information and people.
Before implementing Twinview, it's important to understand what building information you already have, which systems you want to connect and what you want the platform to achieve.
The good news is that you don't need a fully developed BIM model, complete asset register or connected smart building to get started.
Twinview can work with the information and systems you already have, with additional functionality introduced as your requirements and data maturity evolve.
This checklist will help you identify:
-
What information is available and ready to use.
-
What additional information or technical access may be required.
-
Which stakeholders need to be involved.
-
Any gaps or dependencies that could affect implementation.
-
Whether you're ready to begin onboarding.
Who should complete this checklist?
We recommend completing it with your project lead and representatives from the relevant Estates, Facilities Management, IT, BIM or building systems teams.
Not every requirement will apply to every project. Focus on the areas relevant to your intended use cases.
1. Project Objectives & Scope
Before considering the technology or data, establish what you want your digital twin to achieve.
A clear set of objectives will help determine which information, integrations and Twinview functionality are required.
Project readiness checklist:
-
We have identified the buildings, sites or areas to be included.
-
We have defined the main objectives of the digital twin.
-
We have identified the primary users and how they will use the platform.
-
We have agreed which functionality we want to implement initially.
-
We have identified how we will measure the success of the project.
Typical objectives might include improving access to building information, consolidating asset records, simplifying maintenance activities, monitoring energy consumption or identifying building performance issues.
Tip: Start with a small number of clearly defined objectives. You can expand your digital twin as new requirements emerge.
2. Project Stakeholders & Responsibilities
Implementing a digital twin often requires information and input from several teams.
Identifying these stakeholders early helps avoid delays caused by missing information, access restrictions or unclear responsibilities.
Project readiness checklist:
-
We have appointed a project lead responsible for coordinating the implementation.
-
We have identified who owns or manages our building information.
-
We have identified the people responsible for IT and system access.
-
We have involved our Facilities Management or building operations team.
-
We have identified any external consultants, contractors or systems integrators who may need to contribute.
-
We have an agreed process for resolving questions and approving decisions.
For projects involving live building data, the BMS maintainer, controls contractor or IoT provider should also be involved.
Tip: You don't necessarily need all stakeholders involved in every activity, but it's useful to know who to contact when their input is required.
3. Building Information & Asset Data
Twinview brings together information about your buildings, assets and spaces.
This information may currently exist in spreadsheets, BIM models, CAFM systems, document repositories or other databases.
Project readiness checklist:
-
We have a list of the buildings or sites to be included.
-
We can identify the relevant floors, rooms and spaces.
-
We have identified any existing asset registers or equipment schedules.
-
We know where our O&M manuals, drawings and other building documentation are stored.
-
We have identified the systems that currently hold this information.
-
We understand any significant gaps, duplication or inconsistencies in our information.
What Asset Information Is Useful?
Where available, a structured asset register can significantly improve the onboarding process.
Useful information includes:
| Information | Example |
|---|---|
| Asset identifier | AHU-001 |
| Asset name | Air Handling Unit 01 |
| Asset classification | Uniclass 2015 classification |
| Location | Level 02 – Plant Room |
| Manufacturer and model | Equipment manufacturer and model reference |
| Serial number | Manufacturer's serial number |
| Installation date | Date installed or commissioned |
| Warranty information | Warranty start and expiry dates |
| Maintenance requirements | Inspection and servicing requirements |
Not every field needs to be available at the outset. The information required will depend on what you want to achieve with Twinview.
Important: Where information comes from multiple sources, consistent asset and location identifiers will make it easier to connect records and avoid duplication.
Do We Need a BIM Model?
No. A 3D BIM model is not essential for a Twinview implementation.
If you have an existing Revit or IFC model, it may be possible to use this to establish a spatial representation of your building and extract relevant asset information.
If you don't have a BIM model, Twinview can still be configured around your available asset registers, documents, spaces and operational data.
Where models are included, we recommend checking that they are reasonably up to date and that the relevant assets and locations can be identified.
4. Facilities Management Requirements
Complete this section if you intend to use Twinview's Facilities Management functionality.
Twinview can support the management of maintainable assets, maintenance activities, tickets and associated building information.
To configure these workflows effectively, it's useful to understand how your organisation currently manages maintenance.
Project readiness checklist:
-
We have identified which assets require planned or reactive maintenance.
-
We have existing maintenance schedules, service requirements or PPM records, where available.
-
We understand how maintenance tasks, tickets and issues are currently raised and managed.
-
We have identified the people or contractors responsible for completing maintenance activities.
-
We have agreed whether Twinview will operate independently or alongside an existing CAFM/CMMS platform.
-
We have identified any historical maintenance information we would like to retain or make accessible.
If you're already using another facilities management system, you don't necessarily need to replace it.
Twinview may be able to integrate relevant information and workflows, subject to the capabilities and access arrangements of the existing system.
Tip: Identify which system will be responsible for creating and updating each type of record. This helps avoid duplication or conflicting information when multiple platforms are connected.
5. IoT, BMS & Building System Connectivity
Complete this section if you intend to connect live or historical operational data to Twinview.
Twinview can bring together data from Building Management Systems (BMS), IoT sensors, meters and other connected systems.
This enables users to monitor building performance, identify trends and develop operational dashboards.
Before integration begins, it's important to understand where the data originates and how it can be accessed.
Project readiness checklist:
-
We have identified the building systems, sensors or meters we want to connect.
-
We know who manages those systems and can arrange technical access.
-
We have identified the data points required for our use cases.
-
We understand how the data can be accessed, such as through an API, MQTT connection, BMS interface or gateway.
-
We know whether the systems are accessible through a cloud API or require local network connectivity.
-
We have identified any IT or cybersecurity approvals required.
-
We can provide technical documentation, example data or point schedules where available.
-
We have identified whether data is needed for monitoring only or whether any additional system interactions are proposed.
What Information Is Required for an Integration?
The following information is particularly useful when assessing a potential connection:
| Requirement | Example |
|---|---|
| Source system | Building Management System |
| Technology or protocol | BACnet, Modbus, MQTT or REST API |
| Data points | Room temperature, CO₂, equipment status |
| Units | °C, ppm, kWh |
| Update frequency | Every 5 minutes or on change |
| Connectivity | Local network, cloud API or gateway |
| Technical contact | BMS engineer or systems integrator |
Where available, details such as timestamps, point identifiers, example payloads and expected data volumes can also help the implementation team plan a reliable integration.
Important: Some integrations require an on-site gateway or additional network configuration. These requirements should be identified with your IT and building systems teams before integration work begins.
Credentials and other sensitive connection details should only be exchanged through an agreed secure process.
6. IT, Security & User Access
Twinview is a cloud-based platform, so your organisation may need to review access arrangements, information security requirements and any integration connectivity.
The extent of this review will depend on your organisation's IT policies and the functionality being implemented.
Project readiness checklist:
-
We have identified the teams or individuals responsible for IT and information security approvals.
-
We have an initial list of the users or organisations that will require access.
-
We understand which users need administrative, editing or read-only permissions.
-
We have identified whether Single Sign-On (SSO) or organisation-managed authentication is required.
-
We understand any network or firewall restrictions that could affect integrations.
-
We have identified any data protection, confidentiality or information governance requirements.
For larger organisations, access may need to be coordinated with a central IT or identity management team.
Where third-party systems are involved, the relevant system owners should also approve the proposed data access and sharing arrangements.
Tip: Involve your IT team early if the project requires integration with internal BMS networks, corporate systems or sensitive operational data.
7. Dashboards, Reporting & Analytics
Complete this section if you intend to use Twinview for operational monitoring, reporting or analytics.
Understanding what you want to measure is just as important as connecting the underlying data.
Rather than attempting to display every available data point, focus initially on the information that helps your team make decisions.
Project readiness checklist:
-
We have identified the key operational metrics or KPIs we want to monitor.
-
We know which data sources are required to calculate these metrics.
-
We have identified who will use the dashboards and reports.
-
We understand whether we need real-time monitoring, historical analysis or both.
-
We have identified any existing performance targets or benchmarks.
-
We have considered how insights will be acted upon by our operational teams.
Typical examples include:
-
Energy Performance: Electricity, gas and water consumption, with trends and comparisons.
-
Environmental Conditions: Temperature, CO₂ and indoor air quality across rooms and spaces.
-
Building Health: Equipment availability, faults and abnormal operating conditions.
-
Facilities Management: Open maintenance jobs, overdue activities and asset condition.
-
Space Utilisation: Occupancy levels, room utilisation and patterns of building use.
Where automated calculations, alerts or workflows are required, these should be agreed during implementation so the appropriate data and system dependencies can be established.
8. Reviewing Your Project Readiness
Once you've completed the checklist, you'll have a clearer understanding of your project's current readiness.
Not every box needs to be ticked before you begin.
Some information may be unavailable, some may need to be created and some may not be relevant to your project.
For each relevant requirement, we recommend identifying its status:
| Status | Meaning |
|---|---|
| Ready | The information, decision or resource is available |
| Action Required | Something is missing or needs further investigation |
| Not Applicable | The requirement is not relevant to the agreed project scope |
Where action is required, record the outstanding item, who is responsible and when it is expected to be resolved.
Are We Ready to Start?
You are generally well positioned to begin Twinview onboarding when:
-
You understand what you want to achieve.
-
You've identified the buildings and initial functionality to be included.
-
You have a nominated project lead and relevant stakeholders.
-
You know which building information and systems are available.
-
You've identified the main information gaps and technical dependencies.
You don't need everything to be perfect before getting started.
A phased implementation may allow you to begin with the information you already have and introduce additional functionality as your project develops.
For example, you could start with building documentation and asset information, then add live BMS data, operational dashboards and maintenance workflows in subsequent stages.
The best approach will depend on your priorities, available information and implementation scope.
9. Preparing for Your Twinview Kick-Off
Having completed the checklist, the next step is to share your findings with your Twinview implementation team or delivery partner.
Where available, it can be useful to provide:
-
An overview of your buildings, project objectives and intended use cases.
-
A list of relevant stakeholders and technical contacts.
-
Sample asset registers or building information schedules.
-
Details of available models, drawings and documentation.
-
A summary of the building systems or external platforms to be integrated.
-
An initial list of users and access requirements.
-
Any known information gaps, restrictions or outstanding decisions.
These don't necessarily need to be final versions. Early access to representative information can help the team identify potential challenges and establish realistic implementation requirements.
Your implementation team can then help agree the project scope, delivery responsibilities, information requirements and appropriate next steps.
Where to Go Next
Once you've assessed your project readiness, continue to:
Project Initiation & Onboarding
This guide explains how a Twinview implementation progresses from initial discovery and planning through to configuration, validation and go-live.
If you have questions about your project's requirements or readiness, contact your Twinview account manager or implementation partner.