Skip to content
English
  • There are no suggestions because the search field is empty.

Asset Classification, Identifiers & Data Dictionary

Creating Consistent, Reliable Building Information

One of the foundations of a successful digital twin is having accurate, structured and consistently organised asset information.

Buildings contain thousands of individual components, from air handling units and pumps to lighting systems, meters and sensors. Information about these assets often originates from different sources, including BIM models, asset registers, O&M documentation, BMS platforms and facilities management systems.

Without consistent naming, classification and identification, it can be difficult to connect this information and maintain reliable asset records.

Twinview brings these different sources together, allowing building operators to establish a more complete view of their assets and associated information.

This guide explains three important principles:

  • Asset Classification: How assets are categorised using recognised classifications or project-specific structures.
  • Asset Identifiers: How individual assets are uniquely identified and connected across different information sources.
  • Data Dictionary: How asset information fields are defined and standardised to maintain consistency.

Together, these principles provide a foundation for reliable asset information management throughout a building's operational life.

1. Understanding Asset Classification

Asset classification is the process of grouping building assets according to an agreed system or structure.

For example, a building might contain hundreds of different pieces of mechanical equipment, including air handling units, pumps, fans, valves and heating systems.

Although each piece of equipment is unique, classification allows similar assets to be identified and grouped consistently.

This is useful for:

  • Finding and filtering particular types of equipment.
  • Applying consistent asset information requirements.
  • Identifying assets requiring planned maintenance.
  • Comparing equipment across buildings or an estate.
  • Supporting reporting, lifecycle planning and asset management.
  • Sharing structured information between different systems.

Classification Standards in Twinview

Twinview can work with recognised industry classification systems, including Uniclass 2015, as well as other classification schemes or project-specific requirements.

For many UK projects, Uniclass 2015 provides the default approach to organising building information.

However, the appropriate classification structure should be agreed during project onboarding, particularly when information originates from existing client systems or different geographical markets.

What Is Uniclass 2015?

Uniclass is an industry classification system maintained by NBS and widely used across the UK built environment.

It provides standardised classifications for different types of building information, including buildings, spaces, systems, products and equipment.

For asset information management, some of the most relevant Uniclass tables include:

Uniclass Table Purpose Example
En – Entities Classifies complete built assets or facilities Buildings and other constructed entities
SL – Spaces/Locations Classifies different types of spaces Classrooms, offices and plant rooms
EF – Elements/Functions Classifies building elements and functional requirements Heating, ventilation and structural elements
Ss – Systems Classifies collections of products working together Ventilation and heating systems
Pr – Products Classifies individual products and components Fans, pumps and valves

For example, an air handling unit may be classified at product level, while the wider ventilation installation can be associated with a system classification.

These are different types of information and should not be confused.

Important: Uniclass classifications are periodically updated by NBS. Where Uniclass is used, projects should adopt an agreed version and use valid published codes rather than creating their own variations.

The latest classification tables are available from NBS Uniclass.

Asset Classification vs Asset Categories

It's useful to distinguish an industry classification from a category used for operational management.

For example:

  • Classification: Identifies what an asset is, using an agreed classification system.
  • Operational Category: Groups assets according to the organisation's management or reporting requirements.

An air handling unit might have a Uniclass product classification while also belonging to a project-specific operational category such as Mechanical Plant.

This distinction allows standardised asset information to coexist with categories that reflect how a building operator manages its estate.

Twinview's available category structures and their application will depend on the relevant module and project configuration.

2. Understanding Asset Identifiers

While classification tells us what an asset is, its identifier tells us which specific asset we're referring to.

For example, a building may contain 20 air handling units.

They may all share the same classification, but each requires its own identifier so that information, documents and maintenance history can be associated with the correct equipment.

A typical naming convention might look like this:

Asset Identifier Asset Name Location
AHU-001 Air Handling Unit 01 Level 01 – Plant Room
AHU-002 Air Handling Unit 02 Level 02 – Plant Room
AHU-003 Air Handling Unit 03 Roof Plant

The identifier should distinguish the individual asset, even where multiple assets have the same manufacturer, model or classification.

Asset Identifiers in Twinview

Twinview uses an Asset Identifier field to identify maintainable assets.

When creating a maintainable asset, both the asset name and Asset Identifier are mandatory, and the Asset Identifier must be unique.

A clear and consistent asset identification strategy is therefore an important part of preparing information for Twinview.

Where assets are imported from existing systems, we recommend retaining established asset identifiers wherever possible, provided they are unique, consistent and suitable for operational use.

This reduces the need to rename equipment and helps maintain continuity with existing maintenance records, drawings and asset schedules.

Recommended Asset Naming Conventions

There is no single naming convention that works for every building.

However, we recommend that asset identifiers should be:

  • Unique: Each maintainable asset should have a distinct identifier within the relevant project.
  • Consistent: Similar asset types should follow an agreed naming convention.
  • Persistent: Identifiers should remain stable throughout the asset's operational life wherever possible.
  • Recognisable: Building operators should be able to locate or identify equipment using the identifier.
  • Compatible: Identifiers should be suitable for use across systems such as CAFM, BMS and asset management platforms.

For larger estates, it may be useful to include a building or site reference within the identifier.

For example:

BLD01-AHU-001

This identifies Air Handling Unit 001 within Building 01.

However, avoid making identifiers unnecessarily complicated or embedding information that is likely to change, such as an asset's current condition, maintenance status or potentially its location.

Tip: If an asset is moved or its name changes, its underlying identity should ideally remain consistent so that historical information is not lost.

3. Different Types of Asset Identifiers

Building information systems often use several identifiers for the same physical asset.

Understanding the difference is particularly important when integrating Twinview with other platforms.

Identifier Purpose
Asset Identifier / Asset Tag The operational reference used to identify a particular piece of equipment
Twinview Internal Identifier A system-generated identifier used to reference a record internally
BIM Model Identifier A reference associated with an object in a source model, such as a Revit UniqueId or IFC GlobalId
External System Identifier A reference used by another platform, such as a CAFM/CMMS asset ID or ServiceNow CMDB identifier
BMS / IoT Point Identifier Identifies an individual data point, sensor or device within a connected system

These identifiers serve different purposes and should not automatically be treated as interchangeable.

For example, a physical air handling unit may have an operational asset identifier of AHU-001, while its BMS uses a different naming structure and its maintenance records are stored under a separate identifier in a CAFM system.

During integration, these references need to be mapped correctly so that information from different systems is associated with the intended asset.

Where a system-generated identifier is exposed through an integration or API, it should be handled according to that interface's documented behaviour rather than assumed to be editable or permanent.

Asset Identifiers vs IoT Device Identifiers

It's also important to distinguish between a physical asset and the sensors or data points associated with it.

For example, an air handling unit may have several connected data points:

  • Supply air temperature.
  • Return air temperature.
  • Fan running status.
  • Filter differential pressure.
  • Equipment fault status.

These data points may each have their own identifiers within the BMS or IoT platform.

They can be associated with the same physical asset without requiring the asset itself to share their identifiers.

Maintaining this distinction helps avoid duplicate assets and supports more reliable integration between operational systems.

4. What Is a Data Dictionary?

A data dictionary defines the structure, meaning and expected format of information recorded about your assets.

It helps ensure that everyone involved in producing, importing, updating or using building information understands what each field represents.

For example, one contractor might provide an asset's manufacturer in a field called Manufacturer, while another uses Make or Supplier.

Similarly, one asset register might record installation dates in DD/MM/YYYY format, while another uses a different date format.

Without agreed definitions, these differences can create inconsistencies when information is combined.

A data dictionary establishes a common reference for how information should be captured and managed.

What Should a Data Dictionary Define?

A well-structured data dictionary should identify:

  • Field Name: The agreed name of the information field.
  • Description: What the field represents.
  • Data Type: Whether the value is text, a number, a date or another supported type.
  • Required Status: Whether the field is mandatory, optional or required only for certain asset types.
  • Format or Units: Any applicable formatting conventions or units of measurement.
  • Allowed Values: Any restrictions, controlled lists or validation rules.
  • Data Source: Where the information originates.
  • Ownership: Who is responsible for maintaining or validating the information.

The dictionary may also document how a field maps to corresponding fields in other systems.

For example, a client might require the same operational asset identifier to be used across Twinview and its existing CAFM platform, even if each system labels that field differently.

Note: A project data dictionary is an agreed information management specification. It does not necessarily represent a separate configuration screen or module within Twinview.

5. Example Asset Data Dictionary

The following is an illustrative set of fields that might be included in a project asset information dictionary.

The exact information required will depend on the building, asset types and intended use cases.

Field Description Example Suggested Requirement
Asset Identifier Unique operational reference AHU-001 Mandatory for maintainable assets
Asset Name Human-readable asset name Air Handling Unit 01 Mandatory for maintainable assets
Classification Agreed asset classification Uniclass product classification Project-defined
Building Building containing the asset Main Building Recommended
Level Floor or level associated with the asset Level 02 Recommended
Space Room or location associated with the asset Plant Room 201 Recommended
Manufacturer Equipment manufacturer Example Manufacturer Ltd Asset-dependent
Model Number Manufacturer's model reference ACME-500 Asset-dependent
Serial Number Manufacturer's serial reference SN123456 Asset-dependent
Installation Date Date equipment was installed 2026-01-15 Lifecycle-dependent
Warranty Expiry End of the applicable warranty 2031-01-15 Lifecycle-dependent
Expected Service Life Expected operating life 20 years Lifecycle-dependent
Replacement Cost Estimated replacement cost £15,000 Lifecycle-dependent

These fields provide an example of a useful operational asset record rather than a definitive list of fields enforced by Twinview.

The availability of individual fields, their mapping and any project-specific extensions should be agreed during implementation.

Mandatory vs Optional Information

Not every asset requires the same level of information.

For example, a basic temperature sensor may only require an identifier, name, location and connectivity details.

A major piece of mechanical equipment may require considerably more information, including manufacturer details, maintenance schedules, installation dates, warranty information and replacement cost.

A project's Asset Information Requirements (AIR) should establish what information is required for different asset types and operational activities.

The data dictionary then provides the detailed definitions and formats needed to deliver those requirements consistently.

6. Applying Consistent Asset Information in Twinview

Twinview can bring together asset information from building models, spreadsheets and other sources.

When preparing this information, the following principles will help maintain consistency.

Use a Common Classification Structure

Agree which classification system and version will be used before importing large volumes of asset information.

Where information originates from different sources, review any differences in classifications and establish the necessary mappings.

Retain Existing Asset Identifiers

Where an organisation already has a reliable asset identification strategy, aim to retain it rather than introducing unnecessary new references.

If identifiers need to be changed, maintain a record of the previous values and their corresponding new references.

Standardise Field Names & Formats

Agree common field names and data formats.

For example:

  • Use consistent date formats.
  • Agree standard units of measurement.
  • Use controlled values for fields such as asset status.
  • Avoid multiple names for the same information field.
  • Distinguish between missing, unknown and not-applicable information.

Avoid Duplicate Asset Records

An individual piece of equipment may appear in several information sources, such as a BIM model, asset register and CAFM platform.

Before importing data, establish how these records will be matched.

A shared operational identifier, supported by other reliable references, can help prevent the same physical asset from being created multiple times.

Validate Information Before Use

Information should be checked for completeness, accuracy and consistency before it is relied upon for operational decisions.

For example, an incorrect asset location could make maintenance more difficult, while an incorrect installation date could affect lifecycle planning.

The level of validation should reflect the importance and intended use of the information.

7. Classification & Maintainable Assets

In Twinview, it's important to distinguish between a model object and a maintainable asset.

A BIM model may contain thousands of objects, including walls, doors, fittings, mechanical equipment and individual components.

Not every object needs to be managed as an operational asset.

Twinview allows relevant objects to be designated as Maintainable Assets, making them available within the Facilities Management asset register and associated operational workflows.

A maintainable asset can be used to manage equipment information, associated documentation, maintenance activities and relevant operational data.

For example, an individual air handling unit may be designated as a maintainable asset because it requires scheduled maintenance and ongoing management.

However, not every component within the air handling unit necessarily needs its own separate maintainable asset record.

The decision should reflect the organisation's asset management strategy and information requirements.

Important: An asset's classification and its maintainable status are different concepts. Classification describes what the item is, while maintainable status determines whether it is managed through Twinview's maintainable asset workflows.

For instructions on creating and managing maintainable assets, see Introduction to Maintainable Assets.

8. Maintaining Asset Data Throughout Its Lifecycle

Asset information doesn't remain static.

Over time, equipment may be serviced, relocated, repaired, upgraded, replaced or decommissioned.

Maintaining accurate information throughout these changes helps ensure that the digital twin continues to reflect the operational building.

We recommend establishing clear responsibilities for:

  • Reviewing and correcting existing information.
  • Adding newly installed equipment.
  • Updating asset specifications or warranty details.
  • Recording relevant maintenance and replacement activities.
  • Updating external system references when integrations change.
  • Reviewing classifications and data requirements.
  • Managing historical records when equipment is replaced or decommissioned.

What Happens When an Asset Is Replaced?

When an asset is physically replaced, the organisation should determine how the new equipment will be identified and how the history of the previous equipment will be retained.

For example, a replacement pump may occupy the same operational position as its predecessor but have a different manufacturer, model and serial number.

The operational asset naming and replacement strategy should distinguish between the location or function being served and the individual physical item.

This is important for maintaining a reliable record of asset history, warranty information and lifecycle events.

Twinview provides asset decommissioning and replacement workflows, which are covered in the maintainable asset documentation.

9. Supporting Information Exchange & COBie

Consistent classification, identifiers and data definitions also support structured information exchange between Twinview and other systems.

One widely used approach is COBie (Construction Operations Building information exchange).

COBie provides a structured method for exchanging information about building spaces, systems, components and associated operational data.

Where COBie is part of the project's requirements, Twinview can support the export of building and asset information in COBie format.

However, successful information exchange depends on the quality and completeness of the source information.

Before preparing a COBie deliverable, the project team should confirm:

  • Which COBie version and exchange requirements apply.
  • Which buildings, spaces, systems and assets are in scope.
  • Which fields are mandatory for the required deliverable.
  • How asset classifications and identifiers are mapped.
  • Which party is responsible for checking and approving the information.

A COBie export should be validated against the client's agreed requirements rather than assumed to be complete solely because a file has been generated.

10. Getting Started with Your Asset Information Strategy

Before populating Twinview with large volumes of asset information, we recommend agreeing five things:

  1. Classification: Which classification system will be used?
  2. Identification: How will each maintainable asset be uniquely identified?
  3. Data Requirements: What information is required for each asset type?
  4. Data Dictionary: How will fields, formats, values and units be defined?
  5. Ownership: Who is responsible for maintaining and validating the information?

Your Twinview implementation team or delivery partner can help align these requirements with the available source information and intended project functionality.

Establishing these principles early can reduce duplication, simplify integrations and create a more reliable foundation for facilities management, analytics and future asset lifecycle planning.

Where to Go Next

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

For project-specific classification, mapping or information requirements, contact your Twinview implementation lead or delivery partner.