Subset: MostRelevant
Entry elements for the Industrial Asset Hub (IAH) base schema. This subset includes the most relevant elements (classes, slots, enumerations,...) to understand the Industrial Asset Hub (IAH) base schema.
URI: MostRelevant
Identifier and Mapping Information
Classes in subset
| Class | Description |
|---|---|
| Asset | An asset is the representation of a functional object with a technical functi... |
| Device | A device is a special type of asset that can be managed with some asset manag... |
| ConnectionPoint | A connection point is a hardware or software interface that enables an asset ... |
| AssetOperation | Operations that can be performed on the asset |
Asset
An asset is the representation of a functional object with a technical function that is known to Industrial Asset Hub (IAH). Industrial Asset Hub (IAH) might want to manage the asset, to model its relationships with other assets, it might know the asset and ignore it,... The only attributes that an instance of this class must provide are an ID to refer to it and the asset management state. An asset instance might represent a physical object (like a Raspberry Pi or an application running on a system) or a virtual object (like a router in a network topology, no matter which physical device it is). In both cases an identifier for the object being represented is needed.
| Name | Cardinality and Range | Description |
|---|---|---|
Note: table only showing attributes belonging to the specific subset.
Device
A device is a special type of asset that can be managed with some asset management system. In order to be manageable, it requires at least one connection point for the asset management to communicate with the device and software capable of interacting with the asset management.
| Name | Cardinality and Range | Description |
|---|---|---|
Note: table only showing attributes belonging to the specific subset.
ConnectionPoint
A connection point is a hardware or software interface that enables an asset to communicate with other assets. As of now this schema doesn't specify the structure of common connection points like Ethernet ports. But it will probably be added in future versions of this schema. Otherwise the details will be provided on specialized schemas.
| Name | Cardinality and Range | Description |
|---|---|---|
Note: table only showing attributes belonging to the specific subset.
AssetOperation
Operations that can be performed on the asset
| Name | Cardinality and Range | Description |
|---|---|---|
Note: table only showing attributes belonging to the specific subset.
Attributes (AKA Slots) in subset
| Attribute | Description |
|---|---|
Enumerations in subset
| Enumeration | Description |
|---|---|