Back to Services
Asset Information Requirements

Asset information requirements that survive handover

Most owners discover what asset information they needed after handover. We help you define it before the contract is signed, and then make sure contractors can actually deliver it.

ISO 19650IEC 81346OTLIEC 61355
SA
"Every project has asset information requirements. Most of them are just never written down. The owner finds out what they needed when the handover package arrives and it is not it."

Sylvia Awoudu · Co-founder & COO, SøDera

Understanding the discipline

What asset information requirements are

Asset information requirements set out which objects, properties and documents an owner needs to operate and maintain an asset. Under ISO 19650 they feed the exchange information requirements in every contract.

In practice, AIR answers three questions for every asset class. Which assets must be delivered as named objects with attributes. Which attributes each object type must carry, with units and allowed values. Which documents must be linked to each object, so the owner can find the right drawing or datasheet from the asset it describes.

Without that specification, every contractor fills in what they think is needed. Twenty contractors produce twenty structures. The owner receives data that covers parts of what they need, with gaps, inconsistencies and no reliable link between the asset record and the documents.

Where they usually break

Requirements written without an object type library, without a designation system, or without a document classification leave every contractor to guess. You get twenty structures instead of one.

The other failure mode is timing. Requirements written after contracts are signed become variations. Variations cost money and goodwill, and they arrive while contractors are already producing data against whatever structure they assumed.

The result at handover is not a gap. It is a mountain of data that partially answers the question the owner needed to ask, in formats that require months of reconciliation before anything operational can be built on top.

Our approach

How we work

We map your operational needs to an object type library, connect objects to IEC 81346 reference designations, and set document classification to IEC 61355. Then we check a sample delivery against it before the real one arrives.

The check is the part most projects skip. Writing the requirement is not enough. If the requirement has never been tested against an actual delivery from an actual contractor, there will be surprises at the first data drop. We run a dry run before the gates open.

1

Map operational needs to asset classes

We start from what maintenance and operations need to run the asset, and work backwards to which objects, attributes and documents must be delivered.

2

Write the requirements against an OTL

We draft AIR that maps to the owner's OTL, or build the OTL if one does not exist. Each object class gets a clear set of required attributes, units and allowed values.

3

Connect designation and document classification

We link each object to its IEC 81346 reference designation and each document to its IEC 61355 classification code, so the owner can navigate from asset to document.

4

Test against a real delivery sample

We validate a sample data drop from one contractor before the first gate. Problems found at this stage cost days to fix. Problems found at handover cost months.

What we deliver

An AIR document per asset class, structured for use in contracts
OTL class definitions for each object type with attribute requirements and allowed values
IEC 81346 designation guidance for each asset class
IEC 61355 document classification mapping for each document type
A validation checklist the owner can run on every contractor delivery
A sample validation against a real contractor delivery before the first gate

Who leads this work

Who leads this

Sylvia Awoudu leads our asset information requirements work. She implements object type libraries and asset information requirements on large energy programmes.

She has worked as a document controller, a product owner of a common data environment, and an information management specialist on major offshore wind programmes. She understands what the owner needs to operate the asset, and what it takes to get contractors to deliver it.


Frequently asked questions

AIR, answered

What is the difference between AIR and an OTL?

Asset information requirements define which objects, properties and documents an owner needs to operate and maintain an asset. An object type library is the structured catalogue that lists those object types, their allowed properties and their relations. The AIR tells you what to ask for; the OTL defines the precise format in which it must be delivered.

Do asset information requirements need to follow ISO 19650?

ISO 19650 provides the framework for managing information through the asset lifecycle, and AIR sits within that framework. Programmes following ISO 19650 formally embed the AIR in every contract as part of the exchange information requirements. Programmes that do not follow ISO 19650 formally still benefit from documented AIR, because the alternative is contractors guessing what the owner needs.

When should asset information requirements be written?

Before the first contract is signed. Requirements written after contracts are binding must be agreed as variations, which costs time and goodwill. Requirements written at FEED, before the design freezes, can be tested against the emerging design. The earlier they are written, the cheaper they are to get right.


Define what you need before the contract is signed.

We help you write asset information requirements that contractors can follow and owners can verify.

Book an Assessment

Not sure where to start?

Book an assessment

A focused, paid review that usually takes two weeks. You get a clear picture of where you stand and what to fix first.

Book OTL and asset information assessment