Exchange Asset
Project Stage
| Stage | Name | Valid | |
|---|---|---|---|
| 0 | Portfolio requirements | ||
| 1 | Conception of need | ||
| 2 | Outline feasibility | ||
| 3 | Substantive feasibility | ||
| 4 | Outline conceptual design | ||
| 5 | Full conceptual design | ||
| 6 | Coordinated design and procurement | ||
| 7 | Production information | ||
| 8 | Construction | ||
| 9 | Operation and maintenance | ||
| 10 | Disposal |
Overview
The scope of this exchange requirement is to support the exchange of information concerning assets where an asset is a grouping of elements that are identified together for financial or operational or maintenance purposes.
The intent is to know:
- What elements make up the asset
- Asset identity
- Where the asset is
- When it was incorporated
- The value of the asset
- Who owns, uses and is responsible for the asset
The exchange of asset information should occur within the construction phase of a project (at the latest). Practically, it is expected that asset information should be available at the point of turnover (handover) from the organization performing the construction, installation or erection role to the facility owner or operator. However, owning/operating knowledge may be required for grouping products into assets and this could cause the completion of this exchange requirement at the beginning of the operation and maintenance stage. This is typically the case in current working; this exchange requirement seeks to improve this process.
If the knowledge of the facility owner/operator is brought to bear early in the project, there is no reason why the grouping of elements into assets cannot be applied even during the design stage of a project. Much of the information that may be needed about products and assets is available even at that time and can be applied.
This is shown in the project stage/attribute matrix at the end of this exchange requirement which shows attributes that may be (should be) asserted at each point in the lifecycle leading up to the contractual exchange requirement.
Information Requirements
| Context | Description |
|---|---|
| Precursor | All objects that are to be incorporated into assets are properly identified (through a globally unique identifier) and have their owner histories. |
| Group | Assigns the set of elements and sub assets that will participate in the asset |
| Asset | Provides for the collection of all information about the asset |
| Optional Information | Further optional information that may be provided about the asset |