This Information Model provides a general model for Assets in an OPC UA FX system (illustrated in Figure 2). An Asset is defined as a component with a lifecycle, where the lifecycle includes version information. Fx AssetType (see 6.3) provides a base concept of the asset model defined in this document. The OPC UA FX Information Model supports the modelling of hard Assets and soft Assets. A hard Asset represents physical hardware like devices, controllers, modules, hardware components, or other hardware-based products. A soft Asset represents firmware, software, licenses, etc. The asset model can model an actual physical device or a virtual representation of the physical device. The asset model is capable of defining a simple Asset, such as a sensor or a complex Asset, such as a machine with multiple nested and/or related Assets.


Figure 2 – Asset overview

The asset model is designed to support the nesting of Assets into higher-level devices. The asset model may be used as a base model for plant-wide asset management systems.

The asset model (illustrated in Figure 3) requires that Assets provide a minimum level of information. This includes Asset type identification as well as the unique identification of Asset instances. It also contains vendor information and information from the model defined in OPC UA Devices (see OPC 10000-100). The asset model supports functionality to verify the identity and compatibility of the Assets. For a complete description of the FxAssetType, see 6.3.


Figure 3 – Asset model

The asset model provides a means for representing the relationships between Assets. It also supports the concept that there might be multiple types of relationships between various Assets. These types of relationships might be used to provide multiple views of the asset model. For example:

  • Asset management view
  • Physical hierarchy view
  • Maintenance view
  • Interconnected view (network, electrical, hydraulic)

Vendors or end-users are free to create their own view of the Asset relationships. The asset model makes use of specific ReferenceTypes to represent these relationships. OPC 10000-5 and OPC 10000-23 define some base ReferenceTypes, but this document further extends the available list of ReferenceTypes (see 11.1). Figure 4 illustrates some possible views that an asset model can include. Some Assets may contain other Assets (blue speech bubble), while some are just related to each other (orange lightning bolts). There may be network views showing the network topology (yellow dashed lines), which can be derived from LLDP or other input (see OPC 10000-82). There may be a list of sensors or other devices that require routine maintenance (solid red line). There might be a list of all software Assets that an engineer is responsible for (purple dash-dot lines), and the software Asset might be related to the hardware in which it is executed (green dash-dot-dot lines). All of these Assets might be part of a single plant.

The asset model may be as complex or simple as a specific installation requires. This basic asset model may be part of a plant-wide asset management system or might be a simple asset model used for identity verification. OPC UA FX expects that this model will be extended and that it can operate with other higher-level asset management systems. The asset model might be dynamic during operation.

OPC UA FX defines a minimum asset model that all AutomationComponents are required to support.


Figure 4 – Illustration of asset views