---
title: Asset Information Requirements & Data Quality
description: "A digital twin is only as useful as the information it contains.\n\nHaving a detailed building model or an extensive asset register doesn't necessarily mean that the information is complete, accurate or suitable for managing a building."
---

[Skip to content](https://content.twinview.com/knowledge-base/asset-information-management/asset-information-requirements-data-quality#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. [Asset & Information Management](https://content.twinview.com/knowledge-base/asset-information-management?hsLang=en)

# Asset Information Requirements & Data Quality

A digital twin is only as useful as the information it contains.

Having a detailed building model or an extensive asset register doesn't necessarily mean that the information is complete, accurate or suitable for managing a building.

For example, an air handling unit might be represented in a 3D model, but without its manufacturer, model number, maintenance requirements or associated documentation, the information may be of limited value to a facilities management team.

**The key is not simply collecting more data, but ensuring you have the right information, at the right level of detail, for the decisions you need to make.**

Asset Information Requirements (AIR) help establish what information is needed, while data quality processes ensure that the information provided is reliable and remains useful throughout the building's operational life.

This guide explains how to:

- Define Asset Information Requirements for your building.
- Identify the information needed for different asset types.
- Understand the main principles of data quality.
- Check asset information for completeness, accuracy and consistency.
- Identify and resolve missing or incorrect information.
- Establish processes for maintaining data quality over time.

*Note: The examples and quality checks in this guide are recommended information management practices. Some validation activities can be supported by Twinview's available tools, while others may require project-specific configuration or review by the responsible information providers.*

### 1. What Are Asset Information Requirements?

**Asset Information Requirements (AIR)** define the information an organisation needs about its physical assets to support their operation, maintenance and management.

They establish what information is required, why it is needed, when it should be provided and who is responsible for supplying it.

AIR are recognised within the ISO 19650 information management framework, particularly in relation to information required during the operational phase of an asset's lifecycle.

For example, a building operator might need to know:

- What equipment is installed within the building?
- Where is each asset located?
- Who manufactured it, and what is its model number?
- When was it installed or commissioned?
- What maintenance does it require?
- When does its warranty expire?
- What is its expected operational life?
- Where can the relevant O&M documentation be found?

The AIR establish which of these questions need to be answered and what information must be available to answer them.

**AIR vs Asset Registers and Data Dictionaries**

Although related, these terms have different meanings.

| Term | Purpose |
| --- | --- |
| **Asset Information Requirements (AIR)** | Define what asset information an organisation needs and why. |
| **Asset Register** | Contains the records and information associated with individual assets. |
| **Data Dictionary** | Defines the meaning, format, data type and permitted values of individual information fields. |
| **COBie** | Provides a structured format for exchanging building and asset information between systems. |

For example, your AIR might specify that all maintainable air handling units must have their manufacturer, model and installation date recorded.

Your data dictionary would define the corresponding field names, formats and validation rules.

Your asset register would then contain the actual information for each air handling unit.

**Important:** AIR should be established based on your organisation's operational requirements, rather than simply accepting whichever fields happen to be available in an existing model or spreadsheet.

### 2. Defining the Information Your Organisation Needs

The starting point is understanding how your organisation intends to use its building information.

Different operational objectives require different information.

For example:

| Operational Objective | Information Required |
| --- | --- |
| Locate and identify equipment | Asset identifier, name, classification and location |
| Manage planned maintenance | Equipment type, maintenance requirements, service intervals and relevant documentation |
| Manage warranties | Manufacturer, installation date, warranty terms and expiry date |
| Plan equipment replacement | Installation date, expected service life, asset condition and estimated replacement cost |
| Monitor building performance | Asset or space references, connected sensors, data point mappings and relevant operating information |
| Support compliance activities | Relevant equipment records, certificates, inspection requirements and supporting evidence |

An organisation focused on asset lifecycle planning will typically need more information than one initially using Twinview to organise drawings and O&M documentation.

The required information should therefore reflect the project's intended functionality and the decisions users need to make.

**Not Every Asset Needs the Same Information**

Different asset types have different information requirements.

For example:

- **Air Handling Unit:** May require manufacturer, model, serial number, installation date, maintenance instructions, filter specifications and warranty information.
- **Electricity Meter:** May require meter identifier, location, unit of measurement, meter type, supply information and the area or system being monitored.
- **Fire Safety Equipment:** May require equipment identification, location, installation information, applicable inspection requirements and associated certificates or records.
- **Temperature Sensor:** May require device identifier, location, measurement units, source system and associated room or asset.

These examples illustrate why a single universal list of required fields is not always appropriate.

A more effective approach is to define **information requirements by asset type and operational importance**.

**Prioritising Critical Assets**

Some assets are more important to building operations than others.

For example, equipment supporting critical building services may require more comprehensive information and more frequent review than equipment with limited operational impact.

When defining AIR, consider whether an asset is:

- Essential to building operations.
- Important for safety or statutory obligations.
- Expensive or difficult to replace.
- Subject to frequent maintenance.
- Important for energy or environmental performance.
- Connected to other systems or operational processes.

This helps ensure that the most important information receives the greatest attention.

### 3. Creating an Asset Information Requirements Schedule

Once you've identified the information required, it should be recorded in a structured schedule.

An AIR schedule defines which information fields are required for different asset types and establishes responsibility for delivering them.

A simple schedule might look like this:

| Information Field | Air Handling Unit | Electricity Meter | Temperature Sensor |
| --- | --- | --- | --- |
| Asset Identifier | Required | Required | Required |
| Asset Name | Required | Required | Required |
| Location | Required | Required | Required |
| Manufacturer | Required | Required | If applicable |
| Model Number | Required | Required | If applicable |
| Serial Number | Required | If applicable | If applicable |
| Installation Date | Required | Required | If applicable |
| Warranty Expiry | Required | If applicable | Optional |
| Maintenance Requirements | Required | If applicable | Optional |
| Measurement Units | If applicable | Required | Required |
| Source System Reference | If applicable | Required for integration | Required for integration |

*This is an illustrative example rather than a standard Twinview template or a list of fields required by the platform.*

*The exact requirements should be established by the asset owner or operator.*

**Required, Optional and Conditional Fields**

We recommend distinguishing between three types of information requirements:

- **Required:** The information must be provided for the asset to meet its agreed requirements.
- **Conditional:** The information must be provided when a particular condition applies, such as an asset being connected to a BMS.
- **Optional:** The information may be useful but is not necessary for the agreed use case.

This helps avoid treating every blank field as a data quality problem.

For example, a temperature sensor may not require a replacement cost for basic environmental monitoring, while that field could be essential for an asset lifecycle planning exercise.

**Defining Information Responsibilities**

For each requirement, it's useful to establish:

- Who is responsible for providing the information.
- Where the information originates.
- When it must be delivered.
- How it will be checked.
- Who is responsible for accepting it.

For example, the mechanical contractor may provide equipment specifications, the commissioning team may provide installation and commissioning records, and the facilities management team may confirm that the information is sufficient for operational use.

Agreeing these responsibilities early helps prevent information gaps from being discovered at handover.

### 4. Understanding Data Quality

Once the information requirements have been established, the next challenge is ensuring that the data meets them.

Data quality is not simply about whether a field has been populated.

An asset record may appear complete but still contain incorrect, inconsistent or outdated information.

We recommend evaluating asset information against the following quality principles.

| Quality Principle | What It Means | Example |
| --- | --- | --- |
| **Completeness** | Required information is present | Every maintainable AHU has a recorded manufacturer |
| **Accuracy** | Information reflects the actual equipment | The model number matches the equipment nameplate |
| **Consistency** | Information follows agreed standards | Locations use the same naming structure across systems |
| **Validity** | Values meet agreed rules and formats | Installation dates use an accepted date format |
| **Uniqueness** | Individual assets can be distinguished | Two different AHUs don't share the same Asset Identifier |
| **Currency** | Information reflects the current asset or situation | A replacement pump has the correct installed equipment details |
| **Integrity** | Relationships between records are correct | An asset is linked to the correct space, documents and BMS points |
| **Traceability** | The origin and history of information can be established | The source of an updated asset specification is known |

All of these contribute to creating building information that can be trusted.

For example, a record containing every required field may achieve a high level of completeness, but if its equipment location is incorrect, the information may still cause problems for a maintenance technician.

**A complete asset register is not necessarily an accurate asset register.**

### 5. Checking Asset Information Quality

There are several checks that can help identify potential problems before information is used operationally.

**Check 1: Missing Information**

Review asset records to identify required fields that have not been populated.

Examples include:

- Assets without an identifier.
- Equipment without a recorded location.
- Missing manufacturer or model information.
- Missing installation dates where required.
- Absent warranty or maintenance documentation.

The checks should be based on the agreed AIR rather than assuming that every field is mandatory for every asset.

**Check 2: Duplicate or Conflicting Records**

Check whether the same physical asset has been recorded more than once.

For example, equipment may appear in both a BIM model and an existing CAFM system, potentially with different names or identifiers.

Before combining the information, confirm whether the records refer to the same physical equipment.

Similarly, two different assets should not share the same unique operational identifier within the agreed identification scope.

**Check 3: Incorrect Values or Formats**

Look for values that are inconsistent with the agreed data dictionary.

For example:

- Dates stored in different formats.
- Invalid asset classification codes.
- Numbers recorded as text.
- Inconsistent units of measurement.
- Unexpected abbreviations or placeholder values.
- Information entered into the wrong field.

A common example is storing a value such as `25` without specifying whether it represents years, months, kilograms or another unit.

**Check 4: Incorrect Asset Relationships**

Review the relationships between assets, locations, documents and external systems.

For example:

- Is the asset assigned to the correct building or room?
- Does its linked O&M manual relate to the correct equipment?
- Are maintenance activities associated with the intended asset?
- Are connected BMS or IoT data points mapped to the correct equipment?

These relationships can be particularly important when information originates from several disconnected systems.

**Check 5: Physical Verification**

Where appropriate, asset information should be checked against the equipment installed in the building.

For example, a technician could verify an asset's manufacturer, model, serial number and location against its physical nameplate.

This is particularly useful for older buildings where asset information may have changed since the original construction or handover.

**Tip:** Prioritise physical verification for critical equipment, records with conflicting information and assets where inaccurate data could affect maintenance or operational decisions.

### 6. Measuring Data Completeness

Measuring information quality helps identify areas requiring attention and track improvements over time.

One useful starting point is **Data Completeness**.

This measures how much of the required information has been populated.

For example, suppose your AIR specifies five mandatory fields for every air handling unit:

1. Asset Identifier
2. Asset Name
3. Location
4. Manufacturer
5. Model Number

An air handling unit with all five fields populated would have 100% completeness against those requirements.

An air handling unit with only four of the five required fields populated would have 80% completeness.

**Calculating Data Completeness**

A simple calculation is:

**Data Completeness (%) = (Populated Required Fields ÷ Total Applicable Required Fields) × 100**

This can be measured at several levels:

- **Individual Asset:** How complete is the information for one asset?
- **Asset Type:** How complete is the information for all air handling units, for example?
- **Building:** What proportion of required information is available across the building?
- **Portfolio:** How consistent is information completeness across multiple sites?

**Understanding the Limitations**

Completeness is useful, but it should not be treated as a complete measure of information quality.

For example, a manufacturer field containing `Unknown` is technically populated but may not satisfy the actual information requirement.

Similarly, an incorrect serial number may pass a basic completeness check while still being inaccurate.

Meaningful quality assessment should therefore consider completeness alongside validity, accuracy and consistency.

Where formal data quality scoring is used, the scoring rules and any weighting should be agreed and documented so that users understand what the results represent.

**Establishing Quality Targets**

Different information fields may require different acceptance thresholds.

For example, you may decide that all assets included in a maintenance system must have a valid unique identifier and confirmed location before operational acceptance.

Other information, such as estimated replacement costs, might be completed later if lifecycle planning is not part of the initial implementation.

There is no universal completeness percentage suitable for every Twinview project.

Targets should reflect the agreed AIR, asset criticality and intended operational use.

### 7. Managing Data Quality in Twinview

Twinview brings together asset information from models, spreadsheets, documents and connected external systems.

This provides an opportunity to consolidate information and identify inconsistencies that may previously have been hidden across separate sources.

However, **importing information into Twinview does not automatically guarantee that it is accurate or complete**.

Data quality should be considered throughout onboarding and subsequent asset management activities.

**Step 1: Review the Source Information**

Before importing large volumes of data, review the available information against the agreed AIR.

Identify missing fields, inconsistent naming, duplicate identifiers and any known quality concerns.

Where possible, resolve issues in the source information before importing it.

**Step 2: Agree Field Mapping**

Ensure the fields in the source data are mapped to the intended Twinview asset information.

For example, the same information may be described as `Asset ID`, `AssetIdentifier` or `Equipment Reference` in different source systems.

The appropriate mapping should be agreed before importing or synchronising information.

For more information about field definitions and identifiers, see **Asset Classification, Identifiers & Data Dictionary**.

**Step 3: Validate the Information**

Check that the imported information meets the agreed requirements.

Depending on the workflow and available functionality, validation may involve:

- Reviewing asset records within Twinview.
- Checking imported information against the original source.
- Using available data validation or reporting tools.
- Reviewing exceptions identified during an import.
- Comparing asset data with physical equipment records.
- Using Twinview Capture or other agreed data collection workflows where applicable.

The precise automated checks available will depend on the Twinview tools and project configuration being used.

**Step 4: Resolve Identified Issues**

Where missing or incorrect information is identified, establish who is responsible for resolving it.

For example, an equipment supplier may need to confirm a model number, while the facilities management team may need to verify an asset location.

Once corrected, the relevant information should be checked again.

**Step 5: Confirm Operational Acceptance**

Before information is accepted for operational use, the responsible project team should confirm that it meets the agreed requirements.

This may involve reviewing:

- Information completeness.
- Outstanding data quality issues.
- Asset identification and location accuracy.
- Associated documentation.
- Required maintenance information.
- Relevant data mappings and system relationships.

The intended users, particularly Facilities Management and Estates teams, should be involved in confirming that the information is suitable for their needs.

### 8. Managing Missing or Unavailable Information

Not every piece of information will be available when a digital twin is first created.

This is particularly common when onboarding existing buildings, where documentation may be incomplete or information may be held by multiple contractors.

Rather than delaying the entire implementation, it can be useful to establish a structured approach to managing these gaps.

For each outstanding information requirement, consider recording:

| Field | Example |
| --- | --- |
| Asset Identifier | AHU-001 |
| Missing Information | Installation Date |
| Issue | Original commissioning record unavailable |
| Responsible Party | Estates Team |
| Proposed Action | Review maintenance records or verify on site |
| Status | Awaiting Verification |
| Target Resolution | Agreed project date |

This is an example of an information quality issue register, not necessarily a dedicated screen within Twinview.

**Handling Unknown and Not Applicable Values**

It's important to distinguish between:

- **Unknown:** The information is required but has not yet been established.
- **Not Applicable:** The field is not relevant to the asset.
- **Not Yet Available:** The information is expected to become available at a later stage.
- **Verified:** The information has been checked against an appropriate source.

Avoid using placeholder values simply to make a record appear complete.

For example, entering an arbitrary date in a mandatory installation-date field may allow a spreadsheet to appear complete, but creates misleading information for future lifecycle planning.

Where information cannot be provided, record the exception and agree how it will be resolved or accepted.

### 9. Maintaining Data Quality Over Time

Data quality is not just an onboarding activity.

Building information changes continuously as equipment is installed, serviced, relocated, upgraded or replaced.

Without an agreed maintenance process, even a highly accurate asset register can become outdated.

We recommend establishing clear responsibilities for:

- Adding new assets when equipment is installed.
- Updating asset details when equipment is modified.
- Reviewing documentation and warranty information.
- Managing changes to asset locations or identifiers.
- Maintaining relationships with external systems.
- Reviewing information following maintenance or replacement activities.
- Periodically checking the quality of critical asset records.

**Establishing Data Ownership**

Different information fields may have different owners.

For example:

| Information | Suggested Owner |
| --- | --- |
| Asset identification and classification | Asset Information Manager |
| Equipment specifications | Relevant technical or maintenance team |
| Asset location | Estates or Facilities Management |
| Maintenance schedules | Facilities Management |
| Warranty information | Asset owner or maintenance team |
| External system mappings | IT or Systems Integrator |

These responsibilities should reflect the organisation's operational structure.

**When Should Information Be Reviewed?**

Typical review points include:

- When new information is imported.
- Following equipment installation or replacement.
- When an asset is moved or modified.
- Following significant maintenance activities.
- During periodic asset information audits.
- When integrating or replacing connected systems.

Twinview's project activity records and available audit capabilities can help support traceability, but data ownership and review processes remain important responsibilities for the organisations managing the information.

### 10. Good Practice Checklist

Before accepting asset information for operational use, consider the following:

- Asset Information Requirements have been agreed.
- Required information is defined for each relevant asset type.
- The asset naming and classification conventions are consistent.
- Maintainable assets have unique identifiers.
- Required fields have been checked for completeness.
- Key information has been validated against reliable sources.
- Duplicate and conflicting records have been investigated.
- Asset locations and relationships are accurate.
- Required documentation is available and associated correctly.
- Missing or unavailable information has been recorded.
- Outstanding issues have been assigned to responsible parties.
- Operational users have confirmed that the information is suitable for its intended purpose.
- Ongoing data ownership and review responsibilities are established.

A well-managed information quality process helps create a more reliable asset register and supports more effective maintenance, reporting, analytics and lifecycle planning.

**The goal isn't to collect every possible piece of information. It's to ensure that the information your organisation actually needs is available, accurate and trustworthy.**

### Where to Go Next

For more information about managing asset information within Twinview, see:

- **Asset Classification, Identifiers & Data Dictionary** — Understand asset classifications, identifiers and consistent field definitions.
- **Creating & Managing Asset Records** — Learn how to create, locate and update asset information.
- **Bulk Asset Imports & Excel Round-Tripping** — Understand how to import and update large volumes of asset information.
- **Twinview Capture** — Learn how asset information can be collected and validated through structured data capture workflows.
- **COBie Import, Export & Validation** — Understand structured information exchange and handover requirements.
- **Asset Lifecycle & Replacement Management** — Explore how asset information supports equipment replacement and long-term planning.

For project-specific information requirements, validation rules or data quality concerns, contact your Twinview implementation team or delivery partner.

- [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