C.3 Enhancement with whole asset type

Use Case:

An existing type or instance model is to be extended by the complete powertrain specific asset definition.

In contrast to the use cases from C.1 and C.2, the complete powertrain asset definition is to be transferred to an existing model. Instead of taking over the individual Interfaces and AddIns, a new instance of the PtAssetType or a sub-type e.g. PtAssetMotorType is attached with a HasAddIn reference.

As in the previous use cases, the DefaultBrowsename of the PtAssetType definitions is also defined in this specification.

An advantage with this approach is the existence of an instance of a powertrain defined asset type, e.g. PtAssetMotorType. This gives the client confidence that it is an asset defined in this specification.

A disadvantage can be the additional hierarchy level in contrast to the approaches from C.1 and C.2.

In Figure 22 Enhancement with whole asset type only the enhancement on instance level is shown. Of course, this enhancement can also be done on type level.