---
title: Project Initiation & Onboarding
description: How your Digital Twin is born!
---

[Skip to content](https://content.twinview.com/knowledge-base/getting-started/project-initiation-onboarding#main-content)

English

Show submenu for translations

[![Twinview Academy - Purple Background (3).png\]](https://content.twinview.com/hs-fs/hubfs/Twinview%20Academy%20-%20Purple%20Background%20(3).png?height=50&name=Twinview%20Academy%20-%20Purple%20Background%20(3).png)](https://content.twinview.com/knowledge-base?hsLang=en)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Go to twinview.com](https://www.twinview.com/)

[Go to twinview.com](https://www.twinview.com/)

 Welcome To The Twinview Knowledge Base

- There are no suggestions because the search field is empty.

1. [Getting started](https://content.twinview.com/knowledge-base/getting-started?hsLang=en)

# Project Initiation & Onboarding

## Bringing Your Digital Twin to Life

Every successful digital twin starts with a clear understanding of what you want to achieve.

Whether you're deploying Twinview for a single building, managing an estate or connecting live operational data from multiple systems, the onboarding process is designed to ensure your project is configured around your objectives.

Twinview's Customer Success and Technical Onboarding teams, or an approved implementation partner, will work with you to establish your project environment, organise your building information, configure the relevant functionality and prepare your team to use the platform.

The exact onboarding activities will depend on your project requirements, the modules being implemented and the information and systems available.

This guide explains the typical stages of a Twinview implementation, the information you may need to provide and what to expect before your project goes live.

### 1. Project Discovery & Planning

The first stage is understanding what your digital twin needs to deliver.

During project initiation, your Twinview implementation team will work with key stakeholders to establish the project's scope, intended use cases and implementation requirements.

Typical areas covered include:

- **Project Objectives:** What do you want to achieve? Examples include improving access to building information, simplifying facilities management, monitoring operational performance or identifying opportunities to reduce energy consumption.
- **Building & Estate Scope:** Which buildings, floors, spaces, assets and systems will be included?
- **Required Functionality:** Which Twinview modules and features will be used, including asset management, documentation, facilities management and IoT analytics?
- **Available Information:** What BIM models, asset registers, O&M documentation, drawings and existing system data are available?
- **Integrations:** Will Twinview need to connect with a BMS, IoT sensors, energy meters, CAFM/CMMS platform or other third-party system?
- **Users & Permissions:** Who will access Twinview, what will they need to do and what information should they be able to see or edit?
- **Success Criteria:** How will you determine whether the implementation has been successful?

These discussions inform the project's Digital Twin Implementation Strategy, helping ensure that the platform configuration, data requirements and delivery activities are aligned with your objectives.

**Key outcome:** An agreed implementation scope, delivery responsibilities, information requirements and success criteria.

### 2. Preparing Your Building Information

Once the project requirements have been agreed, the next step is to identify and prepare the information that will populate Twinview.

Depending on the project, this may include:

| Information type | Typical examples |
| --- | --- |
| Building models | Revit models or other supported 3D model formats |
| Drawings & spatial information | Floor plans, room schedules, building levels and space references |
| Asset information | Asset registers, equipment identifiers, classifications, locations and technical attributes |
| Documents | O&M manuals, warranties, commissioning records, certificates and maintenance instructions |
| Facilities management data | Maintenance schedules, existing asset histories and information from CAFM/CMMS systems |
| Operational data | BMS points, IoT devices, environmental sensors and energy or water meters |

Not every project requires every information type.

#### **Do I need a BIM model?**

No. A 3D BIM model is not a prerequisite for using Twinview.

Twinview can support implementations based on structured building information, asset registers, documents and operational data without requiring a fully modelled building.

Where a BIM model is available, it can provide an interactive spatial representation of your building, allowing users to navigate the building and access information associated with assets and spaces.

Where no BIM model is available, the project can be configured around the available asset and location information, with relevant functionality accessible through other parts of the platform.

Your implementation team will help establish the most appropriate approach for your project.

#### **Data Quality & Preparation**

The quality and consistency of the source information are important to the success of the implementation.

Before information is imported, the project team should consider:

- Whether asset and room identifiers are unique and consistent.
- Whether equipment locations and classifications are accurate.
- Whether required asset attributes are populated.
- Whether documentation can be associated with the relevant assets or spaces.
- Whether operational data points can be reliably mapped to their corresponding equipment, meters or locations.

Identifying and resolving information gaps early can significantly reduce rework later in the implementation.

**Key outcome:** An agreed set of information sources, with identified gaps, data owners and a plan for preparing and importing the required information.

### 3. Creating & Configuring Your Twinview Project

Once the implementation requirements have been established, the Twinview environment can be configured.

Depending on the deployment and agreed scope, this stage may involve:

1. **Organisation & Project Setup:** Creating the relevant organisation and project within the Twinview environment.
2. **Building Structure:** Configuring building names, levels, rooms, spaces and zones where required.
3. **Project Settings:** Establishing the relevant project configuration and available modules.
4. **Users & Organisations:** Inviting users and configuring any participating organisations.
5. **Roles & Permissions:** Assigning appropriate access based on each user's responsibilities.
6. **Authentication:** Configuring the agreed login and authentication arrangements, including Single Sign-On (SSO) where applicable.
7. **Initial Navigation:** Preparing relevant models, views and information so users can navigate the project effectively.

The exact configuration will vary depending on the project, its subscribed functionality and the agreed implementation approach.

Your implementation team will help determine which settings should be configured centrally and which can be managed by authorised project administrators.

**Key outcome:** A configured Twinview project with the appropriate structure, settings and user access.

### 4. Configuring Your Building & Asset Information

With the project environment established, the next stage is to populate Twinview with the relevant building information.

#### **Building Models & Spatial Information**

Where applicable, the implementation team can upload and configure supported building models, establish the primary model and prepare associated views and 2D drawings.

Building levels, spaces and room information should be checked to ensure they reflect the intended project structure.

For projects without a BIM model, the implementation will focus on establishing the necessary spatial and asset information through the available data sources.

#### **Asset Information**

Asset registers can be imported and configured to support the intended use cases.

Typical activities include:

- Importing or creating asset records.
- Assigning appropriate asset classifications.
- Associating assets with buildings, floors and spaces.
- Populating technical information and asset attributes.
- Identifying assets that will be maintained or monitored.
- Linking assets to relevant documentation and operational data.

Where required, additional asset information can be populated or validated using the applicable Twinview data management and capture workflows.

#### **Document Management**

The Document Vault provides a central location for storing and accessing building documentation.

Documents can be organised and, where applicable, associated with the relevant assets or spaces, making information easier to locate during building operations.

Typical documentation includes O&M manuals, asset specifications, drawings, commissioning records, warranties and compliance information.

**Key outcome:** A structured building information environment, with the agreed assets, spaces and documentation available to the relevant users.

### 5. Configuring Additional Twinview Modules

Depending on your implementation, further activities may be required to configure facilities management and operational analytics functionality.

#### **Twinview Facilities Management**

If your project includes Twinview Manage, onboarding activities may include:

- Defining maintainable assets and their associated information.
- Configuring ticket, issue and maintenance job categories.
- Setting up maintenance workflows and relevant user permissions.
- Establishing planned preventative maintenance (PPM) schedules.
- Preparing operational dashboards and reports.
- Importing relevant information from existing facilities management systems, where included in scope.

These activities should reflect the building operator's existing processes and agreed operational requirements.

#### **Twinview IoT & Analytics Module**

If your project includes live operational data and analytics, additional technical onboarding will be required.

This may include:

1. Identifying the building systems, sensors and meters to be connected.
2. Agreeing the data points, units, identifiers and update frequencies.
3. Establishing the appropriate integration method, such as an API, MQTT connection or on-site gateway.
4. Configuring any required gateway infrastructure or Node Assistant integrations.
5. Creating IoT devices and mapping incoming data points to the corresponding records in Twinview.
6. Validating data accuracy, timestamps, units and connectivity.
7. Configuring dashboards, charts, reports and any agreed calculations or workflows.

Where integration with building control systems or third-party platforms is required, collaboration with the relevant IT teams, BMS engineers, systems integrators or technology providers may be necessary.

**Important:** Access to source systems, network connectivity, API credentials and third-party permissions should be agreed early. These dependencies can affect the implementation programme.

**Key outcome:** The relevant Twinview modules and integrations are configured and ready for validation.

### 6. Testing, Validation & Go-Live

Before the project is handed over for operational use, the agreed functionality and information should be tested.

Validation activities will depend on the project's scope, but may include the following:

| Area | Example validation |
| --- | --- |
| Project access | Users can access the correct project and functionality |
| Permissions | Representative user roles have the intended access and restrictions |
| Models & spaces | Building navigation, drawings and spatial information work as expected |
| Asset information | Sample asset records, identifiers, locations and attributes match the agreed source information |
| Documents | Relevant documents can be located and accessed by authorised users |
| Facilities management | Tickets, maintenance jobs and other agreed workflows operate as expected |
| IoT integrations | Data is being received correctly, with appropriate timestamps, units and device mappings |
| Dashboards & reporting | Agreed visualisations and calculations display the expected information |

Any identified issues should be reviewed, assigned and resolved or documented before the relevant functionality is accepted.

#### **Project Handover**

A typical handover may include:

- Confirmation that the agreed implementation scope has been delivered.
- Completion of relevant testing and user acceptance activities.
- Confirmation of project administrators and operational owners.
- Provision of relevant configuration and integration documentation.
- User onboarding and training.
- Agreement on support arrangements and any outstanding actions.

Once the agreed acceptance criteria have been met, the project can transition into normal operational use.

**Key outcome:** An accepted and operational Twinview project, with clear ownership and support arrangements.

#### 7. Roles & Responsibilities

Successful implementations typically involve several parties working together.

The responsibilities below are illustrative and should be confirmed during project initiation.

| Role | Typical responsibilities |
| --- | --- |
| **Client / Building Owner** | Defines business objectives, approves scope, provides or arranges access to building information and accepts agreed deliverables |
| **Twinview / Implementation Partner** | Coordinates onboarding, configures the agreed platform functionality, supports data onboarding and manages implementation activities |
| **BIM / Asset Information Team** | Provides and validates building models, spatial information, asset registers and relevant documentation |
| **IT / BMS / Systems Integrator** | Supports source-system access, network connectivity, gateways, API integrations and technical validation |
| **Facilities Management / Operations Team** | Defines operational requirements, validates workflows, participates in testing and assumes day-to-day operational ownership |

A nominated implementation lead should coordinate activities, dependencies, decisions and communication between these stakeholders.

For larger or more complex projects, a responsibility matrix and agreed implementation programme can help clarify individual accountabilities.

### 8. How Long Does Onboarding Take?

There is no single onboarding duration applicable to every Twinview project.

The implementation programme will depend on factors including:

- The number of buildings, spaces and assets being onboarded.
- The availability, quality and completeness of existing information.
- Whether BIM models require preparation or coordination.
- The modules and functionality being implemented.
- The number and complexity of external integrations.
- The availability of IT, BMS and other third-party stakeholders.
- The scope of testing, validation and user training.

A project focused on importing existing building information will typically have different requirements from one involving extensive asset data preparation, live BMS integrations and multiple operational workflows.

Your Twinview implementation lead will help agree an appropriate programme, milestones and responsibilities based on your project requirements.

### 9. Training & Ongoing Support

Onboarding doesn't end when the project goes live.

Your Twinview Customer Success team or implementation partner can help familiarise your organisation with the platform and support the transition to everyday use.

Training may include:

- Navigating buildings, spaces and asset information.
- Accessing documents, drawings and building records.
- Using facilities management tools.
- Interpreting dashboards and operational data.
- Managing users and project settings.
- Understanding relevant administration and integration workflows.

Twinview also offers specialist partner training for organisations looking to specify, implement and support digital twin projects for their own clients.

The content, duration and format of partner training should be confirmed with your Twinview account manager.

Following implementation, the agreed support arrangements will provide a route for reporting technical issues, requesting assistance and accessing relevant guidance.

### Where to Go Next

Now that you understand the typical onboarding process, the following guides will help you explore specific areas of Twinview:

- [**The Project Environment**](https://content.twinview.com/knowledge-base/user-interface-navigation?hsLang=en) — Learn how to navigate the platform and access project information.
- [**Project Settings**](https://content.twinview.com/knowledge-base/user-interface-navigation?hsLang=en) — Understand the available project configuration options.
- [**Facilities Management Toolkit**](https://content.twinview.com/knowledge-base/facilities-management-toolkit?hsLang=en) — Explore asset management, tickets, issues and maintenance jobs.
- [**IoT & Analytics Module**](https://content.twinview.com/knowledge-base/iot-analytics-module?hsLang=en) — Understand how Twinview displays and analyses operational building data.
- [**IoT Setup & Integrations**](https://content.twinview.com/knowledge-base/iot-setup-integrations?hsLang=en) — Learn how building systems and external data sources connect to Twinview.

For project-specific implementation requirements, please contact your Twinview account manager or implementation lead.

- [Getting started](https://content.twinview.com/knowledge-base/getting-started?hsLang=en)
- [User Interface & Navigation](https://content.twinview.com/knowledge-base/user-interface-navigation?hsLang=en)
- [Asset & Information Management](https://content.twinview.com/knowledge-base/asset-information-management?hsLang=en)
- [Facilities Management Toolkit](https://content.twinview.com/knowledge-base/facilities-management-toolkit?hsLang=en)
- [IoT & Analytics Module](https://content.twinview.com/knowledge-base/iot-analytics-module?hsLang=en)
- [IoT Setup & Integrations](https://content.twinview.com/knowledge-base/iot-setup-integrations?hsLang=en)
- [Node Assistant](https://content.twinview.com/knowledge-base/node-assistant?hsLang=en)
- [Training Excercises](https://content.twinview.com/knowledge-base/training-excercises?hsLang=en)
- [Appendix Documents](https://content.twinview.com/knowledge-base/appendix-documents?hsLang=en)

[![Twinview\_BLACK\_RGB](https://content.twinview.com/hs-fs/hubfs/Twinview_BLACK_RGB.png?width=200&height=78&name=Twinview_BLACK_RGB.png "Twinview_BLACK_RGB")](https://content.twinview.com/knowledge-base?hsLang=en)

Copyright © 2026, Twinview