Attribute (AKA Slot): functional_parts
The functional objects that an asset is composed of, in case such a level of decomposition is desired. This is enables having assets composed of other assets and even devices composed of other devices and assets. An Asset must be addressable independently from other Assets (therefore they need to have an "id") and are therefore individually modeled. But not all parts of an Asset that are modeled need to be individually addressable, these are FunctionalObjects, but not Assets. Probably those functional_parts of an Asset providing some function for the Asset will be modeled here. Therefore an Asset can delegate the Interactions that it's offering to its functional_parts.
URI: base:functional_parts
Applicable Classes
| Name | Description |
|---|---|
| SoftwareAsset | Any kind of software element that needs to be considered |
| Dcd | Device Class Driver (DCD) running and registered |
| Gateway | Gateway as a software asset can be mapped using the class |
| SoftwareArtifact | Software asset representing software on rest |
| Asset | An asset is the representation of a functional object with a technical functi... |
| AssetLink | Asset Link (AL) running and registered |
| Device | A device is a special type of asset that can be managed with some asset manag... |
| RunningSoftware | Software asset representing running software |
Properties
- Range: Asset
- Multivalued: True
Examples
| Value |
|---|
| A server rack Asset can have following functional_parts that can be modeled like this: a frame (an Asset), servers (Devices), network switches/routers (Devices), power supply (a FunctionalObject),... |
| A library installed on a device |
| The firmware of a device |
Identifier and Mapping Information
LinkML Source
name: functional_parts
description: 'The functional objects that an asset is composed of, in case such a
level of decomposition is desired. This is enables having assets composed of other
assets and even devices composed of other devices and assets.
An Asset must be addressable independently from other Assets (therefore they need
to have an "id") and are therefore individually modeled. But not all parts of an
Asset that are modeled need to be individually addressable, these are FunctionalObjects,
but not Assets.
Probably those functional_parts of an Asset providing some function for the Asset
will be modeled here. Therefore an Asset can delegate the Interactions that it''s
offering to its functional_parts.'
title: functional parts
examples:
- value: 'A server rack Asset can have following functional_parts that can be modeled
like this: a frame (an Asset), servers (Devices), network switches/routers (Devices),
power supply (a FunctionalObject),...'
- value: A library installed on a device
- value: The firmware of a device
from_schema: https://common-device-management.code.siemens.io/documentation/asset-modeling/base-schema/v0.10.0/iah-base.jsonld
rank: 1000
alias: functional_parts
domain_of:
- Asset
range: Asset
multivalued: true
inlined: true
inlined_as_list: true