Document Number: XMP1011

Date: 2011-08-31

Version: 1.0.3m

Example Physical Asset Profile

IMPORTANT: This specification is not a standard. It does not necessarily reflect the views of the DMTF or all of its members. Because this document is a Work in Progress, this specification may still change, perhaps profoundly. This document is available for public review and comment until the stated expiration date. This document expires on: 2012-02-28. Target version for DMTF Standard: 1.0.3. Provide any comments through the DMTF Feedback Portal: http://www.dmtf.org/standards/feedback

Document Type: Specification

Document Status: Work in Progress

Document Language: en-US

## Copyright notice

Copyright © 2006-2011 Distributed Management Task Force, Inc. (DMTF). All rights reserved.

DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability. Members and non-members may reproduce DMTF specifications and documents for uses consistent with this purpose, provided that correct attribution is given. As DMTF specifications may be revised from time to time, the particular version and release date should always be noted.

Implementation of certain elements of this standard or proposed standard may be subject to third party patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, or identify any or all such third party patent right, owners or claimants, nor for any incomplete or inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, disclose, or identify any such third party patent rights, or for such party's reliance on the standard or incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any party implementing such standard, whether such implementation is foreseeable or not, nor to any patent owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is withdrawn or modified after publication, and shall be indemnified and held harmless by any party implementing the standard from any and all claims of infringement by a patent owner for such implementations.

For information about patents held by third-parties which have notified the DMTF that, in their opinion, such patent may relate to or impact implementations of DMTF standards, visit http://www.dmtf.org/about/policies/disclosures.php.

# CONTENTS

## Figures

[Insert table of figures here ...]

## Tables

[Insert table of tables here ...]

# Foreword

This document was prepared by the Physical Platform Profiles Working Group and Server Management Working Group.

DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability.

Design Note: This document contains design notes (like this one), that provide information about the way the document is written, or to demonstrate certain things. Such design notes would not appear in a released version of this document.

Design Note: This MRP document represents DSP1011 1.0.2 as a machine readable profile. Since machine readable profiles need to be compliant to DSP1001 1.1, this document utilizes the newly introduced concepts, such as adaptations, features and collaboration diagrams.

## Acknowledgements

DMTF acknowledges the following individuals for their contributions to this document:

- Jon Hass, Dell Inc. (editor)
- Khachatur Papanyan, Dell Inc. (editor)
- Jeff Hilland, HP (editor)
- Hemal Shah, Broadcom Corporation (editor)
- Christina Shaw, HP
- Aaron Merkin, IBM
- Jeff Lynch, IBM
- Arvind Kumar, Intel
- Perry Vincent, Intel
- John Leung, Intel

## Document conventions

Any text in this document is in normal text font, with the following exceptions:

- References to clause names use normal text font; if they consist of more than one word, the clause name is quoted using double quotes, such as in "CIM elements".
- Important terms that are used for the first time are marked in italics.
- The usage of terms link to the term definition defined in the "Terms and definitions" clause, enabling easy navigation to the term definition.

# Scope

The Physical Asset profile extends the management capability of the referencing profiles by adding the capability to represent the physical aspects of elements in the managed environment, the relationship with their logical aspects, and the implementation of this profile.

# Normative references

The following referenced documents are indispensable for the application of this document. For dated or versioned references, only the edition cited (including any corrigenda or DMTF update versions) applies. For undated and unversioned references, the latest published edition of the referenced document (including any corrigenda or DMTF update versions) applies.

DMTF DSP0004, CIM Infrastructure Specification 2.5,
http://www.dmtf.org/standards/published_documents/DSP0004_2.5.pdf

DMTF DSP0223, Generic Operations 1.0,
http://www.dmtf.org/standards/published_documents/DSP0223_1.0.pdf

DMTF DSP1001, Management Profile Specification Usage Guide 1.1,
http://www.dmtf.org/standards/published_documents/DSP1001_1.1.pdf

DMTF XMP1033, Example Profile Registration Profile (sample profile in DSP2023) 1.0,
http://www.dmtf.org/standards/published_documents/DSP2023_1.0.zip

ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards,
http://isotc.iso.org/livelink/livelink?func=ll&objId=4230456&objAction=browse&sort=subtype

# Terms and definitions

In this document, some terms have a specific meaning beyond the normal English meaning. Those terms are defined in this clause.

## General

The terms "shall" ("required"), "shall not", "should" ("recommended"), "should not" ("not recommended"), "may", "need not" ("not required"), "can" and "cannot" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Annex H. The terms in parenthesis are alternatives for the preceding term, for use in exceptional cases when the preceding term cannot be used for linguistic reasons. Note that ISO/IEC Directives, Part2, Annex H specifies additional alternatives. Occurrences of such additional alternatives shall be interpreted in their normal English meaning in this document.

The terms "clause", "subclause", "paragraph", "annex" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Clause 5.

The terms "normative" and "informative" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Clause 3. In this document, clauses, subclauses or annexes indicated with "(informative)" as well as notes and examples do not contain normative content.

The terms defined in DSP0004, DSP0223, and DSP1001 apply to this document.

The following additional terms are defined in this document.

##

connecting element

A physical element that has the ability to connect with a physical connector. It is modeled through the abstract base adaptation AbstractConnectingElement.

##

delimited substring

A substring of a vendor compatibility string that starts at the beginning of the vendor compatibility string and ends at the end of the string, or at a character that precedes a colon (:) within the string. See features PackageSlotCompatibilityForPackage and PackageSlotCompatibilityForSlot.

##

field replaceable unit

A physical element that can be replaced in the field. Also sometimes called a part.

##

FRU information

Information that supports the replacement of a FRU in the field.

##

FRU number

A string that identifies the FRU. The uniqueness of that string and potential correspondence to a part number is defined by the manufacturer of the FRU. The FRU number is part of the FRU information.

##

physical component

A physical element that cannot be further decomposed. It is modeled through the adaptation PhysicalComponent.

##

physical element

An element in the managed environment that has a physical presence (e.g. could be touched). It is modeled through the abstract base adaptation AbstractPhysicalElement.

##

physical package

A physical element that has the ability to contain (or house, host) other physical elements. It is modeled through the adaptation PhysicalPackage.

##

physical connector

A physical element that has the ability to connect with a connecting element. It is modeled through the PhysicalConnector adaptation.

##

slot

A place to plug a physical package into.

##

system chassis

The physical package of the managed system.

# Symbols and abbreviated terms

This clause defines the symbols and abbreviations used in this document.

## General

The abbreviations defined in DSP0004, DSP0223, and DSP1001 apply to this document.

The following additional abbreviations are defined in this document.

##

FRU

Field Replaceable Unit

# Synopsis

Profile name: Example Physical Asset

Version: 1.0.3

Organization: DMTF

Abstract indicator: False

Profile type: Component

Schema: DMTF CIM 2.22 (experimental)

Central class adaptation: AbstractPhysicalElement

Scoping class adaptation: AbstractSystem

Scoping path: Realizes, LogicalDevice, SystemDevice

The Physical Asset profile extends the management capability of the referencing profiles by adding the capability to represent the physical aspects of physical elements in the managed environment, the relationship with their logical aspects, and the implementation of this profile. Physical aspects include asset, inventory, and other descriptive physical information. The profile does not cover the geographic location of the physical assets.

The following table identifies the profile references defined in this profile.

Profile references
Profile reference name | Profile name | Organi​zation | Version | Relation​ship | Description
--- | --- | --- | --- | --- | ---
PRP | Profile Registration | DMTF | 1.0 | Mandatory | Used to represent the implementation of this profile.

The following table identifies the features defined in this profile.

Features
Feature | Require​ment | Description
--- | --- | ---
FRUInformation | Optional | See subclause "Feature: FRUInformation".
FieldReplaceability | Optional | See subclause "Feature: FieldReplaceability".
LogicalElementRelation | Optional | See subclause "Feature: LogicalElementRelation".
PackageSlotCompatibilityForPackage | Optional | See subclause "Feature: PackageSlotCompatibilityForPackage".
PackageSlotCompatibilityForSlot | Optional | See subclause "Feature: PackageSlotCompatibilityForSlot".
SystemChassisForSystem | Optional | See subclause "Feature: SystemChassisForSystem".
SystemChassisForComputerSystem | Optional | See subclause "Feature: SystemChassisForComputerSystem".
ConfigurationCapacity | Optional | See subclause "Feature: ConfigurationCapacity".
PackageContainmentHierarchy | Optional | See subclause "Feature: PackageContainmentHierarchy".
PackageSlotConnection | Optional | See subclause "Feature: PackageSlotConnection".
ConnectorConnection | Optional | See subclause "Feature: ConnectorConnection".

The following table identifies the class adaptations defined in this profile.

Adaptations
Adaptation | Elements | Require​ment | Description
--- | --- | --- | ---
Instantiated, embedded and abstract adaptations
AbstractSystem | CIM_System | See derived adaptations | See subclause "Adaptation: AbstractSystem".
ComputerSystem | CIM_ComputerSystem | ConditionalExclusive | See subclause "Adaptation: ComputerSystem".
System | CIM_System | ConditionalExclusive | See subclause "Adaptation: System".
ComputerSystemPackage | CIM_ComputerSystemPackage | ConditionalExclusive | See subclause "Adaptation: ComputerSystemPackage".
SystemPackaging | CIM_SystemPackaging | ConditionalExclusive | See subclause "Adaptation: SystemPackaging".
SystemDevice | CIM_SystemDevice | Optional | See subclause "Adaptation: SystemDevice".
LogicalDevice | CIM_LogicalDevice | Conditional | See subclause "Adaptation: LogicalDevice".
Realizes | CIM_Realizes | Conditional | See subclause "Adaptation: Realizes".
AbstractPhysicalElement | CIM_PhysicalElement | See derived adaptations | See subclause "Adaptation: AbstractPhysicalElement".
AbstractConnectingElement | CIM_PhysicalElement | See derived adaptations | See subclause "Adaptation: AbstractConnectingElement".
AbstractPhysicalConnector | CIM_PhysicalConnector | See derived adaptations | See subclause "Adaptation: AbstractPhysicalConnector".
AbstractPhysicalComponent | CIM_PhysicalComponent | See derived adaptations | See subclause "Adaptation: AbstractPhysicalComponent".
AbstractPhysicalPackage | CIM_PhysicalPackage | See derived adaptations | See subclause "Adaptation: AbstractPhysicalPackage".
PhysicalPackage | CIM_PhysicalPackage | Mandatory | See subclause "Adaptation: PhysicalPackage".
PhysicalFrame | CIM_PhysicalFrame | Optional | See subclause "Adaptation: PhysicalFrame".
Chassis | CIM_Chassis | Optional | See subclause "Adaptation: Chassis".
SystemChassis | CIM_Chassis | Optional | See subclause "Adaptation: SystemChassis".
Rack | CIM_Rack | Optional | See subclause "Adaptation: Rack".
Card | CIM_Card | Optional | See subclause "Adaptation: Card".
PhysicalConnector | CIM_PhysicalConnector | Mandatory | See subclause "Adaptation: PhysicalConnector".
Slot | CIM_Slot | Optional | See subclause "Adaptation: Slot".
PhysicalComponent | CIM_PhysicalComponent | Mandatory | See subclause "Adaptation: PhysicalComponent".
Chip | CIM_Chip | Optional | See subclause "Adaptation: Chip".
PhysicalMemory | CIM_PhysicalMemory | Optional | See subclause "Adaptation: PhysicalMemory".
PhysicalAssetCapabilities | CIM_PhysicalAssetCapabilities | Conditional | See subclause "Adaptation: PhysicalAssetCapabilities".
ElementCapabilities | CIM_ElementCapabilities | Conditional | See subclause "Adaptation: ElementCapabilities".
ConfigurationCapacity | CIM_ConfigurationCapacity | Conditional | See subclause "Adaptation: ConfigurationCapacity".
ElementCapacityForPackage | CIM_ElementCapacity | Conditional | See subclause "Adaptation: ElementCapacityForPackage".
ElementCapacityForSystemChassis | CIM_ElementCapacity | Conditional | See subclause "Adaptation: ElementCapacityForSystemChassis".
Container | CIM_Container | Mandatory | See subclause "Adaptation: Container".
ElementInConnector | CIM_ElementInConnector | Optional | See subclause "Adaptation: ElementInConnector".
ConnectedTo | CIM_ConnectedTo | Optional | See subclause "Adaptation: ConnectedTo".
Indications and exceptions
This profile does not define any such adaptations.

The following table identifies the use cases and state descriptions defined in this profile.

Use cases and state descriptions
Name | Description
--- | ---
State description SystemChassis | See subclause "State description: SystemChassis".
State description FanPackage | See subclause "State description: FanPackage".
Use case FindScopingInstance1 | See subclause "Use case: FindScopingInstance1".
Use case FindScopingInstance2 | See subclause "Use case: FindScopingInstance2".
State description PhysicalTopology | See subclause "State description: PhysicalTopology".
State description PhysicalMemory | See subclause "State description: PhysicalMemory".
State description ConfigurationCapacity1 | See subclause "State description: ConfigurationCapacity1".
State description ConfigurationCapacity2 | See subclause "State description: ConfigurationCapacity2".
State description NetworkPortConnector | See subclause "State description: NetworkPortConnector".
Use case DeterminePartNumberOfComponent | See subclause "Use case: DeterminePartNumberOfComponent".
Use case GetPhysicalInventoryOfSystem | See subclause "Use case: GetPhysicalInventoryOfSystem".
Use case GetPhysicalInventoryOfSystemChassis | See subclause "Use case: GetPhysicalInventoryOfSystemChassis".
Use case DetermineSlotIsEmpty | See subclause "Use case: DetermineSlotIsEmpty".
Use case GetFanCapacityOfChassis | See subclause "Use case: GetFanCapacityOfChassis".
Use case GetMaxFanCapacityOfChassis | See subclause "Use case: GetMaxFanCapacityOfChassis".

# Description

Design Note: This description clause demonstrates how to define subclause headings in the profile, and how they line up with those headings that are created by the DSP8029 XSLT stylesheet.

## General

DMTF collaboration structure diagram

Todo: This subclause so far is a plain copy of the profile text and needs to be updated.

A Physical Element (see section 3.15) describes the physical properties, including the FRU information, of a managed element. The capabilities of the Physical Elements are described by the properties of the CIM_PhysicalAssetCapabilities class. The Physical Elements could be associated to the logical representation of the managed element through the CIM_Realizes association. The enclosures or chassis of the managed systems are represented by a CIM_PhysicalElement or CIM_Chassis instance that is associated to the CIM_System/CIM_ComputerSystem instance through the CIM_SystemPackaging/CIM_ComputerSystemPackage association and are referred to as a System Chassis (see section 3.17). Configuration capacity of the System Chassis is also represented within this profile by CIM_ConfigurationCapacity instances.

Physical Elements can be also arranged in a topology. The CIM_Container, CIM_ConnectedTo, and CIM_ElementInConnector associations are used to associate the Physical Elements and create the physical topology of the managed elements.

Figure 1 also represents the ecosystem of Physical Asset Profile classes, illustrating their relationship with classes of referencing profiles. The referencing profiles can identify the subclass of CIM_PhysicalElement to be used for representing the physical aspects of the managed element. For example, the referencing profiles that contain a CIM_LogicalDevice subclass can restrict the associated subclass of CIM_PhysicalPackage to CIM_PhysicalMemory for instantiation of the Physical Asset Profile. Such restrictions will be described in the referencing profiles.

The Physical Asset Profile is advertised through the CIM_RegisteredProfile instance.

The Physical Asset Profile can be instantiated to represent a combination of the following scenarios:

- the physical aspects of a managed system, such as the FRU information for the chassis (see section 7.6)
- the physical aspects of a specific managed element, such as the FRU information of a fan (see section 7.3)
- the physical hierarchy of a managed system, such as the relationship between chassis, slots, and packages (see section 7.8)
- the configuration capacity of a managed element, such as the minimum and maximum number of certain types of packages that the managed system can handle (see section 7.7)

## Relationship to logical elements

Physical elements represented by AbstractPhysicalElement instances can expose the relationship with the logical elements of which they represent a physical aspect and that are represented by LogicalDevice instances, if the LogicalElementRelation feature is implemented for the physical element. For details, see LogicalElementRelation.

## FRU information of physical elements

Physical elements represented by AbstractPhysicalElement instances can expose their FRU information if the FRUInformation feature is implemented for the physical element. For details, see FRUInformation.

## Plug compatibility of physical packages

Physical packages represented by PhysicalPackage instances and slots represented by Slot instances can expose their plug compatibility if the PackageSlotCompatibilityForPackage feature is implemented for the physical package and the PackageSlotCompatibilityForSlot feature is implemented for the slot.

## System chassis

Systems represented by System or ComputerSystem instances can expose their system chassis if the SystemChassisForSystem or the SystemChassisForComputerSystem feature is implemented for the system.

## Configuration capacity

Physical packages represented by PhysicalPackage instances (including the system itself) can expose their configuration capacity if the ConfigurationCapacity feature is implemented for the physical package. For details, see ConfigurationCapacity.

## Physical topology

The following aspects of physical topology can be exposed:

- Package containment hierarchy: The containment hierarchy of physical packages can be exposed if the PackageContainmentHierarchy feature is implemented. For details, see PackageContainmentHierarchy.
- Package to slot connections: The connections between physical packages and slots can be exposed if the PackageSlotConnection feature is implemented. For details, see PackageSlotConnection.
- Connections between connectors: The connections between physical connectors can be exposed if the ConnectorConnection feature is implemented. For details, see ConnectorConnection.

# Implementation

## Features

### Feature: FRUInformation

Implementing this feature provides support for exposing FRU information for a physical element that is represented by an AbstractPhysicalElement instance.

FRU information is represented by a combination of the values of the following properties of the AbstractPhysicalElement instance:

- Manufacturer
- Model
- PartNumber
- SerialNumber
- SKU

If the SKU property is non-NULL, it shall be used to convey the FRU number.

The requirement level for this feature is optional.

The implementation of this feature is not required for a physical element to expose its replaceability in the field (see FieldReplaceability feature), or to be replaceable.

This feature can be made available to clients at the granularity of AbstractPhysicalElement instances.

It can be concluded that the feature is available for a AbstractPhysicalElement instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalElement instance.

      derive: self.ElementCapabilities::Capabilities.FRUInfoSupported

Otherwise, it can be concluded that the feature is not available.

The following profile elements are conditional or conditional exclusive on the implementation of this feature:

- PhysicalAssetCapabilities adaptation.
- ElementCapabilities adaptation.
- Manufacturer property in AbstractPhysicalElement adaptation.
- Model property in AbstractPhysicalElement adaptation.
- SerialNumber property in AbstractPhysicalElement adaptation.
- PartNumber property in AbstractPhysicalElement adaptation.
- SKU property in AbstractPhysicalElement adaptation.

### Feature: FieldReplaceability

Implementing this feature provides support for exposing the ability for physical elements to be replaced in the field, via values TRUE or FALSE of the CanBeFRUed property of the AbstractPhysicalElement instance representing the physical element.

The requirement level for this feature is optional.

The implementation of this feature or replaceability in the field is not required for a physical element to expose its FRU information (see FRUInformation feature).

This feature can be made available to clients at the granularity of AbstractPhysicalElement instances.

It can be concluded that the feature is available for a AbstractPhysicalElement instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalElement instance.

      derive: self.CanBeFRUed.isNotNull()

Otherwise, it can be concluded that the feature is not available.

The following profile elements are conditional or conditional exclusive on the implementation of this feature:

- CanBeFRUed property in AbstractPhysicalElement adaptation.

### Feature: LogicalElementRelation

This feature provides support for exposing the relationship of physical elements to the logical elements of which they represent a physical aspect.

Design Note: The profile is not particularly clear as to whether physical and logical elements are two distinct managed object types, or different aspects of the same managed object type (and if so, what is that one managed object type). This MRP profile did not attempt to resolve that questions and lives with any ambiguities resulting from that.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalElement instances.

It can be concluded that the feature is available for a AbstractPhysicalElement instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalElement instance.

      derive: self.Realizes::Dependent->size() > 0

Otherwise, it can be concluded that the feature is not available.

The following profile elements are conditional or conditional exclusive on the implementation of this feature:

- LogicalDevice adaptation.
- Realizes adaptation.

### Feature: PackageSlotCompatibilityForPackage

Implementing this feature for a physical package represented by an PhysicalPackage instance and for a slot represented by a Slot instance provides support for indicating the compatibility of that physical package with that slot. Only if a physical package is compatible with a slot, it can be plugged into that slot.

Note that physical components represented by PhysicalComponent instances may be compatible with physical connectors represented by PhysicalConnector instances without being able to indicate that compatibility.

See the AbstractPhysicalPackage. VendorCompatibilityStrings and Slot. VendorCompatibilityStrings properties for a description of their format.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalPackage instances.

It can be concluded that the feature is available for a AbstractPhysicalPackage instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalPackage instance.

      derive: self.VendorCompatibilityStrings.isNotNull()

Otherwise, it can be concluded that the feature is not available.

### Feature: PackageSlotCompatibilityForSlot

Implementing this feature for a physical package represented by an PhysicalPackage instance and for a slot represented by a Slot instance provides support for indicating the compatibility of that physical package with that slot. Only if a physical package is compatible with a slot, it can be plugged into that slot.

Note that physical components represented by PhysicalComponent instances may be compatible with physical connectors represented by PhysicalConnector instances without being able to indicate that compatibility.

See the AbstractPhysicalPackage. VendorCompatibilityStrings and Slot. VendorCompatibilityStrings properties for a description of their format.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of Slot instances.

It can be concluded that the feature is available for a Slot instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A Slot instance.

      derive: self.VendorCompatibilityStrings.isNotNull()

Otherwise, it can be concluded that the feature is not available.

### Feature: SystemChassisForSystem

Implementing this feature for a system provides support for exposing the system chassis of the system, represented by a Chassis instance.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of System instances.

It can be concluded that the feature is available for a System instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A System instance.

      derive: self.SystemPackaging::Dependent->size() > 0

Otherwise, it can be concluded that the feature is not available.

### Feature: SystemChassisForComputerSystem

Implementing this feature for a system provides support for exposing the system chassis of the system, represented by a Chassis instance.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of ComputerSystem instances.

It can be concluded that the feature is available for a ComputerSystem instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A ComputerSystem instance.

      derive: self.ComputerSystemPackage::Dependent->size() > 0

Otherwise, it can be concluded that the feature is not available.

### Feature: ConfigurationCapacity

The implementation of this feature for a physical package provides support for exposing the configuration capacity of that physical package, including of a system chassis.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalPackage instances.

It can be concluded that the feature is available for a AbstractPhysicalPackage instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalPackage instance.

      derive: self.ElementCapacityForPackage::Capacity->size() > 0

Otherwise, it can be concluded that the feature is not available.

The following profile elements are conditional or conditional exclusive on the implementation of this feature:

- ConfigurationCapacity adaptation.
- ElementCapacityForPackage adaptation.
- ElementCapacityForSystemChassis adaptation.

### Feature: PackageContainmentHierarchy

This feature provides support for exposing the containment hierarchy of physical packages as follows:

- For any physical element that resides within a physical package, that relationship shall be represented by a Container instance.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalElement instances.

It can be concluded that the feature is available for a AbstractPhysicalElement instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalElement instance.

      derive: self.Container::PartComponent->size() > 0

Otherwise, it can be concluded that the feature is not available.

### Feature: PackageSlotConnection

This feature provides support for exposing the connections between physical packages and slots as follows:

- For any physical package that is is plugged in or connected to a slot, that relationship shall be represented by an ElementInConnector instance.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalPackage instances.

It can be concluded that the feature is available for a AbstractPhysicalPackage instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalPackage instance.

      derive: self.ElementInConnector::Antecedent->size() > 0

Otherwise, it can be concluded that the feature is not available.

### Feature: ConnectorConnection

Physical connectors may be connected to each other at a certain level of abstraction. For example, the ports of a non-switching network router may be considered connected at the abstraction level of electrical connections, while the ports of an IP-layer switch may be considered connected at the abstraction level of IP communication. The level of abstraction and whether each connector provides the exact same capabilities as one that is connected to it, is not modeled in this profile.

This feature provides support for exposing connections between physical connectors as follows:

- For any physical connector that is connected to another one, that relationship shall be represented by a ConnectedTo instance.

The requirement level for this feature is optional.

This feature can be made available to clients at the granularity of AbstractPhysicalConnector instances.

It can be concluded that the feature is available for a AbstractPhysicalConnector instance if:

- The following OCL derivation constraint evaluates to a Boolean value of True.

  OCL context: A AbstractPhysicalConnector instance.

      derive: self.ConnectedTo::Dependent->size() > 0

Otherwise, it can be concluded that the feature is not available.

## Adaptations

### Conventions

This profile defines operation requirements based on DSP0223.

For adaptations of ordinary classes and of associations the requirements for operations are defined in adaptation-specific subclauses of the "Adaptations" clause.

For association traversal operation requirements that are specified only in the elements table of an adaptation (i.e. without operation-specific subclauses), the names of the association adaptations to be traversed are listed in the elements table.

The default initialization requirement level for property requirements is optional.

The default modification requirement level for property requirements is optional.

This profile repeats the effective values of certain Boolean qualifiers as part of property, method parameter, or method return value requirements. The following convention is established: If the name of a qualifier is listed, its effective value is True; if the qualifier name is not listed, its effective value is False. The convention is applied in the following cases:

- In: indicates that the parameter is an input parameter
- Out: indicates that the parameter is an output parameter
- Key: indicates that the property is a key (that is, its value is part of the instance path)
- Required: indicates that the element value shall be non-Null
- Null OK: indicates explicitly that the element value may be Null for mandatory, conditional or conditional exclusive properties. This information is not specified as a qualifier in the schema but as an indicator in the profile

### Adaptation: AbstractSystem: CIM_System

This abstract adaptation provides a basis for derived adaptations representing specific types of systems.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

### Adaptation: ComputerSystem: CIM_ComputerSystem

This adaptation models managed systems.

Implementation of this adaptation is mutually exclusive with the System adaptation; the choice is determined by referencing profiles.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is conditional exclusive, with the following condition:

The following is NOT true:

- The System adaptation is implemented.

The following table identifies the element requirements for this adaptation.

ComputerSystem: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractSystem | Optional | See AbstractSystem.
Operations
Associators( ) for ComputerSystemPackage | Mandatory | See DSP0223.
AssociatorNames( ) for ComputerSystemPackage | Mandatory | See DSP0223.
References( ) for ComputerSystemPackage | Mandatory | See DSP0223.
ReferenceNames( ) for ComputerSystemPackage | Mandatory | See DSP0223.

### Adaptation: System: CIM_System

This adaptation models managed systems.

Implementation of this adaptation is mutually exclusive with the ComputerSystem adaptation; the choice is determined by referencing profiles.

The implementation type of this adaptation is instantiated ordinary adaptation.

A concrete subclass of the abstract schema class CIM_System needs to be implemented.

The requirement level for this adaptation is conditional exclusive, with the following condition:

The following is NOT true:

- The ComputerSystem adaptation is implemented.

The following table identifies the element requirements for this adaptation.

System: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractSystem | Optional | See AbstractSystem.
Operations
Associators( ) for SystemPackaging | Mandatory | See DSP0223.
AssociatorNames( ) for SystemPackaging | Mandatory | See DSP0223.
References( ) for SystemPackaging | Mandatory | See DSP0223.
ReferenceNames( ) for SystemPackaging | Mandatory | See DSP0223.

### Adaptation: ComputerSystemPackage: CIM_ComputerSystemPackage

#### General

This adaptation models the relationship between managed systems modeled with ComputerSystem and the system chassis of these managed systems modeled with SystemChassis.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional exclusive, with the following condition:

The ComputerSystem adaptation is implemented.

The following table identifies the element requirements for this adaptation.

ComputerSystemPackage: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Antecedent | Mandatory | Key, see subclause "Property: Antecedent".
Dependent | Mandatory | Key, see subclause "Property: Dependent".
PlatformGUID | Mandatory | See subclause "Property: PlatformGUID".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Antecedent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation SystemChassis.
- The multiplicity of [0 .. *] defined in the schema is constrained to [1 .. 1].

#### Property: Dependent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation ComputerSystem.
- The multiplicity of [0 .. *] defined in the schema is constrained to [0 .. 1].

#### Property: PlatformGUID

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a ComputerSystemPackage instance:

    inv: self.PlatformGUID.mrpMatchesPattern('^[0-9A-F]{32}$|0')

### Adaptation: SystemPackaging: CIM_SystemPackaging

#### General

This adaptation models the relationship between managed systems modeled with System and the system chassis of these managed systems modeled with SystemChassis.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional exclusive, with the following condition:

The System adaptation is implemented.

The following table identifies the element requirements for this adaptation.

SystemPackaging: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Antecedent | Mandatory | Key, see subclause "Property: Antecedent".
Dependent | Mandatory | Key, see subclause "Property: Dependent".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Antecedent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation SystemChassis.
- The multiplicity of [0 .. *] defined in the schema is constrained to [1 .. 1].

#### Property: Dependent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation System.
- The multiplicity of [0 .. *] defined in the schema is constrained to [0 .. 1].

### Adaptation: SystemDevice: CIM_SystemDevice

#### General

This adaptation models the relationship between managed systems and the logical elements on these systems.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

SystemDevice: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
GroupComponent | Mandatory | Key, see subclause "Property: GroupComponent".
PartComponent | Mandatory | Key, see subclause "Property: PartComponent".

#### Property: GroupComponent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractSystem.
- The multiplicity of [1 .. 1] defined in the schema is not further constrained.

#### Property: PartComponent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation LogicalDevice.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

### Adaptation: LogicalDevice: CIM_LogicalDevice

This adaptation models logical elements that are realized by a physical element.

The implementation type of this adaptation is instantiated ordinary adaptation.

A concrete subclass of the abstract schema class CIM_LogicalDevice needs to be implemented.

The requirement level for this adaptation is conditional, with the following condition:

The LogicalElementRelation feature is implemented.

The following table identifies the element requirements for this adaptation.

LogicalDevice: Element requirements
Element | Require​ment | Description
--- | --- | ---
Operations
Associators( ) for Realizes and SystemDevice | Mandatory | See DSP0223.
AssociatorNames( ) for Realizes and SystemDevice | Mandatory | See DSP0223.
References( ) for Realizes and SystemDevice | Mandatory | See DSP0223.
ReferenceNames( ) for Realizes and SystemDevice | Mandatory | See DSP0223.

### Adaptation: Realizes: CIM_Realizes

#### General

This adaptation models the relationship between physical elements and the logical elements realized by them.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The LogicalElementRelation feature is implemented.

The following table identifies the element requirements for this adaptation.

Realizes: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Antecedent | Mandatory | Key, see subclause "Property: Antecedent".
Dependent | Mandatory | Key, see subclause "Property: Dependent".

#### Property: Antecedent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalElement.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

#### Property: Dependent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation LogicalDevice.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

### Adaptation: AbstractPhysicalElement: CIM_PhysicalElement

#### General

This abstract adaptation provides a basis for derived adaptations by modeling properties and behaviours of physical elements that are common for more specific types of physical elements and provides a common end point for referencing associations.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

The following table identifies the element requirements for this adaptation.

AbstractPhysicalElement: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Manufacturer | Conditional | See subclause "Property: Manufacturer".
Model | Conditional | See subclause "Property: Model".
SerialNumber | Conditional | See subclause "Property: SerialNumber".
PartNumber | Conditional | See subclause "Property: PartNumber".
SKU | Conditional | See subclause "Property: SKU".
CanBeFRUed | Conditional | See subclause "Property: CanBeFRUed".
ElementName | Mandatory | See subclause "Property: ElementName".
Operations
Associators( ) for Container and others | Mandatory | See subclause "Operation: Associators( ) for Container".
AssociatorNames( ) for Container and others | Mandatory | See subclause "Operation: AssociatorNames( ) for Container".
References( ) for Container and others | Mandatory | See subclause "Operation: References( ) for Container".
ReferenceNames( ) for Container and others | Mandatory | See subclause "Operation: ReferenceNames( ) for Container".

#### Property: Manufacturer

The presentation requirement level for this property is conditional, with the following condition:

The FRUInformation feature is implemented.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.Manufacturer.mrpMatchesPattern('[^WSP]+')

Explanation:

Design Note: Clarify whether this pattern means "no whitespace".

#### Property: Model

The presentation requirement level for this property is conditional, with the following condition:

The FRUInformation feature is implemented.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.Model.mrpMatchesPattern('[^WSP]+')

Explanation:

Design Note: Clarify whether this pattern means "no whitespace".

#### Property: SerialNumber

The presentation requirement level for this property is conditional, with the following condition:

The FRUInformation feature is implemented.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.SerialNumber.mrpMatchesPattern('[^WSP]+')

Explanation:

Design Note: Clarify whether this pattern means "no whitespace".

#### Property: PartNumber

The presentation requirement level for this property is conditional, with the following condition:

The FRUInformation feature is implemented.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.PartNumber.mrpMatchesPattern('[^WSP]+')

Explanation:

Design Note: Clarify whether this pattern means "no whitespace".

#### Property: SKU

The presentation requirement level for this property is conditional, with the following condition:

The FRUInformation feature is implemented.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.SKU.mrpMatchesPattern('[^WSP]+')

Explanation:

Design Note: Clarify whether this pattern means "no whitespace".

#### Property: CanBeFRUed

The presentation requirement level for this property is conditional, with the following condition:

The FieldReplaceability feature is implemented.

#### Property: ElementName

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalElement instance:

    inv: self.ElementName.isNotNull()

#### Operation: Associators( ) for Container and others

For general requirements on the implementation of this operation, see DSP0223.

The requirement level for this operation is mandatory.

This operation requirement applies when traversing the following association adaptations:

- Container
- ElementCapabilities
- Realizes

#### Operation: AssociatorNames( ) for Container and others

For general requirements on the implementation of this operation, see DSP0223.

The requirement level for this operation is mandatory.

This operation requirement applies when traversing the following association adaptations:

- Container
- ElementCapabilities
- Realizes

#### Operation: References( ) for Container and others

For general requirements on the implementation of this operation, see DSP0223.

The requirement level for this operation is mandatory.

This operation requirement applies when traversing the following association adaptations:

- Container
- ElementCapabilities
- Realizes

#### Operation: ReferenceNames( ) for Container and others

For general requirements on the implementation of this operation, see DSP0223.

The requirement level for this operation is mandatory.

This operation requirement applies when traversing the following association adaptations:

- Container
- ElementCapabilities
- Realizes

### Adaptation: AbstractConnectingElement: CIM_PhysicalElement

This abstract adaptation provides a basis for derived adaptations by modeling properties and behaviours of connecting elements that are common for more specific types of connecting elements and provides a common end point for referencing associations.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

The following table identifies the element requirements for this adaptation.

AbstractConnectingElement: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalElement | Optional | See AbstractPhysicalElement.
Operations
Associators( ) for ElementInConnector | Mandatory | See DSP0223.
AssociatorNames( ) for ElementInConnector | Mandatory | See DSP0223.
References( ) for ElementInConnector | Mandatory | See DSP0223.
ReferenceNames( ) for ElementInConnector | Mandatory | See DSP0223.

### Adaptation: AbstractPhysicalConnector: CIM_PhysicalConnector

This abstract adaptation provides a basis for derived adaptations by modeling properties and behaviours of physical connectors that are common for more specific types of connectors and provides a common end point for referencing associations.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

The following table identifies the element requirements for this adaptation.

AbstractPhysicalConnector: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalComponent | Optional | See AbstractPhysicalComponent.
Properties
CreationClassName | Mandatory | Key, see schema definition.
Tag | Mandatory | Key, see schema definition.
ConnectorLayout | Mandatory | See schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

### Adaptation: AbstractPhysicalComponent: CIM_PhysicalComponent

This abstract adaptation provides a basis for derived adaptations by modeling properties and behaviours of physical components (i.e. physical elements that cannot be further decomposed) that are common for more specific types of components and provides a common end point for referencing associations.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

The following table identifies the element requirements for this adaptation.

AbstractPhysicalComponent: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractConnectingElement | Optional | See AbstractConnectingElement.
Properties
CreationClassName | Mandatory | Key, see schema definition.
Tag | Mandatory | Key, see schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

### Adaptation: AbstractPhysicalPackage: CIM_PhysicalPackage

#### General

This abstract adaptation provides a basis for derived adaptations by modeling properties and behaviours of physical packages (i.e. physical elements that have the ability to contain other physical elements) that are common for more specific types of packages and provides a common end point for referencing associations.

The implementation type of this adaptation is abstract ordinary adaptation.

The requirement level for this abstract adaptation is left to be defined in its derived adaptations.

The following table identifies the element requirements for this adaptation.

AbstractPhysicalPackage: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractConnectingElement | Optional | See AbstractConnectingElement.
Properties
CreationClassName | Mandatory | Key, see schema definition.
Tag | Mandatory | Key, see schema definition.
PackageType | Mandatory | See schema definition.
VendorCompatibilityStrings | Mandatory | See subclause "Property: VendorCompatibilityStrings".
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.
Associators( ) for Container and ElementCapacityForPackage | Mandatory | See DSP0223.
AssociatorNames( ) for Container and ElementCapacityForPackage | Mandatory | See DSP0223.
References( ) for Container and ElementCapacityForPackage | Mandatory | See DSP0223.
ReferenceNames( ) for Container and ElementCapacityForPackage | Mandatory | See DSP0223.

#### Property: VendorCompatibilityStrings

The presentation requirement level for this property is mandatory.

See feature PackageSlotCompatibilityForPackage.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a AbstractPhysicalPackage instance:

    inv: self.VendorCompatibilityStrings.mrpMatchesPattern('[^:]+(:[^:]+)+')

### Adaptation: PhysicalPackage: CIM_PhysicalPackage

This adaptation models physical packages for which no other sibling adaptation in this profile matches.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is mandatory.

The following table identifies the element requirements for this adaptation.

PhysicalPackage: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalPackage | Optional | See AbstractPhysicalPackage.

### Adaptation: PhysicalFrame: CIM_PhysicalFrame

This adaptation models physical packages that are frames.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

PhysicalFrame: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalPackage | Optional | See AbstractPhysicalPackage.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

### Adaptation: Chassis: CIM_Chassis

#### General

This adaptation models physical packages that are chassis'.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

Chassis: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalPackage | Optional | See AbstractPhysicalPackage.
Properties
PackageType | Mandatory | See subclause "Property: PackageType".
ChassisPackageType | Mandatory | See schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

#### Property: PackageType

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a Chassis instance:

    inv: self.PackageType = 3 /* Chassis/Frame */

### Adaptation: SystemChassis: CIM_Chassis

This adaptation models physical packages that are the chassis of the managed system (called a system chassis).

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

SystemChassis: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
Chassis | Optional | See Chassis.
Operations
Associators( ) for ComputerSystemPackage and others | Mandatory | See subclause "Operation: Associators( ) for ComputerSystemPackage".
AssociatorNames( ) for ComputerSystemPackage and others | Mandatory | See subclause "Operation: AssociatorNames( ) for ComputerSystemPackage".
References( ) for ComputerSystemPackage and others | Mandatory | See subclause "Operation: References( ) for ComputerSystemPackage".
ReferenceNames( ) for ComputerSystemPackage and others | Mandatory | See subclause "Operation: ReferenceNames( ) for ComputerSystemPackage".

### Adaptation: Rack: CIM_Rack

#### General

This adaptation models physical packages that are racks.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

Rack: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalPackage | Optional | See AbstractPhysicalPackage.
Properties
PackageType | Mandatory | See subclause "Property: PackageType".
TypeOfRack | Mandatory | See schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

#### Property: PackageType

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a Rack instance:

    inv: self.PackageType = 2 /* Rack */

### Adaptation: Card: CIM_Card

This adaptation models physical packages that are cards.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

Card: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalPackage | Optional | See AbstractPhysicalPackage.
Properties
HostingBoard | Mandatory | See schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

### Adaptation: PhysicalConnector: CIM_PhysicalConnector

This adaptation models physical connectors for which no other sibling adaptation in this profile matches.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is mandatory.

The following table identifies the element requirements for this adaptation.

PhysicalConnector: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalConnector | Optional | See AbstractPhysicalConnector.

### Adaptation: Slot: CIM_Slot

#### General

This adaptation models physical packages that are slots.
Slots have the optional ability to expose their plug compatibility, for details see feature PackageSlotCompatibilityForSlot.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

Slot: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalConnector | Optional | See AbstractPhysicalConnector.
Properties
ConnectorLayout | Mandatory | See schema definition.
VendorCompatibilityStrings | Mandatory | See subclause "Property: VendorCompatibilityStrings".
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

#### Property: VendorCompatibilityStrings

The presentation requirement level for this property is mandatory.

See feature PackageSlotCompatibilityForSlot.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a Slot instance:

    inv: self.VendorCompatibilityStrings.mrpMatchesPattern('[^:]+(:[^:]+)+')

### Adaptation: PhysicalComponent: CIM_PhysicalComponent

This adaptation models physical components for which no other sibling adaptation in this profile matches.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is mandatory.

The following table identifies the element requirements for this adaptation.

PhysicalComponent: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalComponent | Optional | See AbstractPhysicalComponent.

### Adaptation: Chip: CIM_Chip

This adaptation models physical components that are chips.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

Chip: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalComponent | Optional | See AbstractPhysicalComponent.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

### Adaptation: PhysicalMemory: CIM_PhysicalMemory

#### General

This adaptation models physical components that are memory chips.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

PhysicalMemory: Element requirements
Element | Require​ment | Description
--- | --- | ---
Base adaptations
AbstractPhysicalComponent | Optional | See AbstractPhysicalComponent.
Properties
FormFactor | Mandatory | See schema definition.
Speed | Mandatory | See subclause "Property: Speed".
Capacity | Mandatory | See schema definition.
BankLabel | Mandatory | See schema definition.
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.

#### Property: Speed

The presentation requirement level for this property is mandatory.

This property shall represent the speed of the memory chip in a unit of nanoseconds. If the speed of the memory chip is less than one nanosecond or unknown, this property shall have a value of 0. If the speed of the memory chip is variable over time, this property shall have a value of 2^32-1.

### Adaptation: PhysicalAssetCapabilities: CIM_PhysicalAssetCapabilities

#### General

This adaptation models the capability of physical elements to indicate whether they expose FRU data.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The FRUInformation feature is implemented.

The following table identifies the element requirements for this adaptation.

PhysicalAssetCapabilities: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
InstanceID | Mandatory | Key, see schema definition.
ElementName | Mandatory | Required, see schema definition.
FRUInfoSupported | Mandatory | See subclause "Property: FRUInfoSupported".
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.
Associators( ) for ElementCapabilities | Mandatory | See DSP0223.
AssociatorNames( ) for ElementCapabilities | Mandatory | See DSP0223.
References( ) for ElementCapabilities | Mandatory | See DSP0223.
ReferenceNames( ) for ElementCapabilities | Mandatory | See DSP0223.

#### Property: FRUInfoSupported

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a PhysicalAssetCapabilities instance:

    inv: if self.ElementCapabilities::Element.mrpIsFeatureSupported('FRUInformation')
    then self.FRUInfoSupported = true
    else self.FRUInfoSupported = false

Explanation:

If the FRUInformation feature is implemented for an AbstractPhysicalElement instance, the value of this property in the associated instance of this adaptation shall be True. Otherwise, the value of this property shall be False.

### Adaptation: ElementCapabilities: CIM_ElementCapabilities

#### General

Todo: Shall associate an instance of a subclass of CIM_PhysicalElement representing a physical element with the CIM_PhysicalAssetCapabilities instance representing the capabilities of that physical element.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The FRUInformation feature is implemented.

The following table identifies the element requirements for this adaptation.

ElementCapabilities: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
ManagedElement | Mandatory | Key, see subclause "Property: ManagedElement".
Capabilities | Mandatory | Key, see subclause "Property: Capabilities".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: ManagedElement

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalElement.
- The multiplicity of [1 .. *] defined in the schema is not further constrained.

#### Property: Capabilities

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation PhysicalAssetCapabilities.
- The multiplicity of [0 .. *] defined in the schema is constrained to [0 .. 1].

### Adaptation: ConfigurationCapacity: CIM_ConfigurationCapacity

#### General

Todo: Class adaptation CIM_ConfigurationCapacity advertises the possible configurations of a system chassis.

The implementation type of this adaptation is instantiated ordinary adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The ConfigurationCapacity feature is implemented.

For each unique value of the VendorCompatibilityStrings property in any Slot instances, a ConfigurationCapacity instance shall exist that has one or more array entry values in its VendorCompatibilityStrings array property that are equal to that unique value.

The following table identifies the element requirements for this adaptation.

ConfigurationCapacity: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Name | Mandatory | Key, see schema definition.
ElementName | Mandatory | See schema definition.
ObjectType | Mandatory | Key, see schema definition.
OtherTypeDescription | Mandatory | See subclause "Property: OtherTypeDescription".
MinimumCapacity | Optional | See subclause "Property: MinimumCapacity".
MaximumCapacity | Mandatory | See subclause "Property: MaximumCapacity".
Increment | Mandatory | See subclause "Property: Increment".
VendorCompatibilityStrings | Mandatory | See subclause "Property: VendorCompatibilityStrings".
Operations
GetInstance( ) | Mandatory | See DSP0223.
EnumerateInstances( ) | Mandatory | See DSP0223.
EnumerateInstanceNames( ) | Mandatory | See DSP0223.
Associators( ) for ElementCapacityForPackage and ElementCapacityForSystemChassis | Mandatory | See DSP0223.
AssociatorNames( ) for ElementCapacityForPackage and ElementCapacityForSystemChassis | Mandatory | See DSP0223.
References( ) for ElementCapacityForPackage and ElementCapacityForSystemChassis | Mandatory | See DSP0223.
ReferenceNames( ) for ElementCapacityForPackage and ElementCapacityForSystemChassis | Mandatory | See DSP0223.

#### Property: OtherTypeDescription

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a ConfigurationCapacity instance:

    inv: if self.ObjectType = 0 /* Other */
    then self.OtherTypeDescription != null
    else self.OtherTypeDescription = null

Explanation:

If the ObjectType property has a value of 0 (Other), this property shall be non-Null. Otherwise, it shall be Null.

#### Property: MinimumCapacity

The presentation requirement level for this property is optional.

This property should be implemented.

#### Property: MaximumCapacity

The presentation requirement level for this property is mandatory.

A value of 0 shall mean that the maximum capacity is unknown.

#### Property: Increment

The presentation requirement level for this property is mandatory.

A value of 0 shall mean that the increment is unknown.

#### Property: VendorCompatibilityStrings

The presentation requirement level for this property is mandatory.

See features PackageSlotCompatibilityForPackage and PackageSlotCompatibilityForSlot.

The implementation shall satisfy the following constraint for this property:

OCL constraint with context of a ConfigurationCapacity instance:

    inv: if self.VendorCompatibilityStrings.mrpMatchesPattern('[^:]+(:[^:]+)+')

### Adaptation: ElementCapacityForPackage: CIM_ElementCapacity

#### General

Todo: Shall associate an instance of a subclass of CIM_PhysicalPackage representing a physical package within the chassis, including the chassis itself, with the CIM_ConfigurationCapacity instance representing the configuration capacity of that element.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The ConfigurationCapacity feature is implemented.

The following table identifies the element requirements for this adaptation.

ElementCapacityForPackage: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Element | Mandatory | Key, see subclause "Property: Element".
Capacity | Mandatory | Key, see subclause "Property: Capacity".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Element

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalPackage.
- The multiplicity of [1 .. *] defined in the schema is constrained to [0 .. *].Profile Error: Reference "Element" defined in association class adaptation "ElementCapacityForPackage" constrains its minimum multiplicity to "0", which is invalid because it is less than the minimum multiplicity "1" defined in schema association class "CIM_ElementCapacity".

#### Property: Capacity

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation ConfigurationCapacity.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

### Adaptation: ElementCapacityForSystemChassis: CIM_ElementCapacity

#### General

Todo: Shall associate an instance of a subclass of CIM_PhysicalPackage representing a physical package within the chassis, including the chassis itself, with the CIM_ConfigurationCapacity instance representing the configuration capacity of that element.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is conditional, with the following condition:

The ConfigurationCapacity feature is implemented.

The following table identifies the element requirements for this adaptation.

ElementCapacityForSystemChassis: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Element | Mandatory | Key, see subclause "Property: Element".
Capacity | Mandatory | Key, see subclause "Property: Capacity".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Element

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation SystemChassis.
- The multiplicity of [1 .. *] defined in the schema is constrained to [1 .. 1].

#### Property: Capacity

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation ConfigurationCapacity.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

### Adaptation: Container: CIM_Container

#### General

Todo: Shall associate a physical package (represented by an instance of class adaptation CIM_PhysicalPackage) with the physical elements (represented by instances of class adaptation CIM_PhysicalElement) that reside within the package.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is mandatory.

The following table identifies the element requirements for this adaptation.

Container: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
GroupComponent | Mandatory | Key, see subclause "Property: GroupComponent".
PartComponent | Mandatory | Key, see subclause "Property: PartComponent".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: GroupComponent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalPackage.
- The multiplicity of [0 .. 1] defined in the schema is not further constrained.

#### Property: PartComponent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalElement.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

### Adaptation: ElementInConnector: CIM_ElementInConnector

#### General

Todo: Shall associate a CIM_PhysicalConnector or CIM_Slot instance (representing a connector or slot), with physical packages (represented by instances of class adaptation CIM_PhysicalPackage).

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

ElementInConnector: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Antecedent | Mandatory | Key, see subclause "Property: Antecedent".
Dependent | Mandatory | Key, see subclause "Property: Dependent".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Antecedent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalConnector.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

#### Property: Dependent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractConnectingElement.
- The multiplicity of [0 .. 1] defined in the schema is not further constrained.

### Adaptation: ConnectedTo: CIM_ConnectedTo

#### General

Todo: Shall associate the CIM_PhysicalConnector or CIM_Slot instances that represent connectors that are connected together.

The implementation type of this adaptation is instantiated association adaptation.

The requirement level for this adaptation is optional.

The following table identifies the element requirements for this adaptation.

ConnectedTo: Element requirements
Element | Require​ment | Description
--- | --- | ---
Properties
Antecedent | Mandatory | Key, see subclause "Property: Antecedent".
Dependent | Mandatory | Key, see subclause "Property: Dependent".
Operations
GetInstance( ) | Mandatory | See DSP0223.

#### Property: Antecedent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalConnector.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

#### Property: Dependent

The presentation requirement level for this property is mandatory.

The implementation shall satisfy the following constraints for this reference property:

- Referenced instances shall be of class adaptation AbstractPhysicalConnector.
- The multiplicity of [0 .. *] defined in the schema is not further constrained.

# Use cases and state descriptions

## State description: SystemChassis

The following figure shows a simple object diagram that represents a scenario that conforms to the requirements of this profile. In that scenario, there is a system chassis that is represented by a SystemChassis instance. The value 17 (Main System Chassis) of the ChassisPackageType property indicates that the represented chassis is a system chassis. As a system chassis, it represents its relationship with the managed system it hosts through a ComputerSystemPackage instance.

The Tag property of the systemchassis1 instance represents the asset tag of the chassis.

The FRUInfoSupported property of the PhysicalAssetCapabilities instance fancapabilities1 indicates by its value of TRUE that the systemchassis1 instance contains FRU information (see FRUInformation).

System chassis object diagram

## State description: FanPackage

The following figure shows a simple object diagram that represents a scenario that conforms to the requirements of this profile. In that scenario, there is a physical package that is a fan and that is represented by the PhysicalPackage instance fanpackage1. The logical aspect of the fan is represented by the LogicalDevice instance fan1 that is associated to the PhysicalPackage instance through Realizes.

The FRUInfoSupported property of the PhysicalAssetCapabilities instance fancapabilities1 indicates by its value of TRUE that the fanpackage1 instance contains FRU information (see FRUInformation).

Fan package object diagram

## Use case: FindScopingInstance1

This use case describes the flow to find the scoping instance of a PhysicalPackage instance.

Find scoping instance use case 1

This use case has the following preconditions:

- The LogicalElementRelation feature has been implemented for the PhysicalPackage instance.
- A PhysicalPackage instance is known.

The main flow for this use case consists of the following sequence of steps:

- Invoke the Associators( ) for Realizes operation on that PhysicalPackage instance. This will retrieve all LogicalDevice instances representing logical elements of the physical package represented by that PhysicalPackage instance.
- For any one of the returned LogicalDevice instances, determine its scoping instance as described in the Fan Profile. This will result in a ComputerSystem instance.
- Optional: The CIM_RegisteredProfile instance physassetprofile1 representing the implementation of this profile can be found from the scoping instance as described in the Profile Registration Profile.

## Use case: FindScopingInstance2

This use case describes the flow to find the scoping instance of a PhysicalPackage instance in a physical containment hierarchy.

Find scoping instance use case 2

This use case has the following preconditions:

- The SystemChassisForSystem feature has been implemented for the scoping instance System or the SystemChassisForComputerSystem feature has been implemented for the scoping instance ComputerSystem.
- A PhysicalPackage instance is known.

The main flow for this use case consists of the following sequence of steps:

- Because the PhysicalPackage instance package1 is referenced by the ElementInConnector. Dependent property, the client needs to traverse that association, resulting in the PhysicalConnector instance connector1.

- Because the PhysicalConnector instance connector1 is referenced by the Container. PartComponent property, the client needs to traverse that association, resulting in the Card instance card1.

  NOTE: To enable finding the scoping instance of connector2, the implementation has instantiated an instance of Container that references card1 and connector2. Merely instantiating the instance of ConnectedTo referencing connector2 will not conform to the scoping class method.

- Because the Card instance card1 is referenced by the Container. PartComponent property, the client needs to traverse that association, resulting in the Chassis instance systemchassis1.

- Because the Chassis instance systemchassis1 is referenced by ComputerSystemPackage, the client needs to traverse that association, resulting in the ComputerSystem instance system1, which is the scoping instance of the PhysicalPackage instance package1.

- Optional: The CIM_RegisteredProfile instance physassetprofile1 representing the implementation of this profile can be found from the scoping instance as described in the Profile Registration Profile.

## State description: PhysicalTopology

The following figure shows an object diagram that represents another possible instantiation of this profile that exposes information about the physical containment hierarchy.

The systemchassis1 instance represents the system chassis of the managed system represented by the system1 instance.

The fanpackage1 instance represents the physical package of the fan represented by the fan1 instance.

The physical topology of the system chassis represented by systemchassis1 contains a single level of hierarchy because the instances card1, slot1, chip1, pmem1, component1, connector1, and fanpackage1 are all directly associated to the systemchassis1 instance through instances of Container.

Physical topology object diagram

## State description: PhysicalMemory

The following figure shows an object diagram that represents another possible instantiation of this profile that exposes information about physical memory packaging.

The memory of the system represented by the system1 instance is represented by the memory1 instance.

The physical aspects of that memory is represented by the pmem1 instance.

The system chassis of the managed system represented by the system1 instance is represented by the systemchassis1 instance.

The system chassis represented by the systemchassis1 instance contains a slot represented by the slot1 instance, into which the memory package represented by the memorypkg1 instance is plugged.

The memory package represented by the memorypkg1 instance contains the physical component that is the memory chip, represented by the pmem1 instance.

Physical memory object diagram

## State description: ConfigurationCapacity1

The following figure shows an object diagram that represents another possible instantiation of this profile that exposes information about the configuration capacity of the managed system.

Todo: This description so far is a plain copy of the profile text and needs to be updated.

In this instantiation, the chassis1 has two slots: slot1 and slot2. The slots are compatible with any type of XYZ:HW:1235Fan packages, as advertised through the CIM_Slot.VendorCompatibilityStrings property. slot1 and package1, which is plugged into it, are compatible because the Delimited Substring matches for the VendorCompatibilityStrings property. slot2 and package2, which is plugged into it, are compatible because an element in the VendorCompatibilityStrings property of the CIM_Slot instance is a Delimited Substring of the element in the VendorCompatibilityStrings property of the CIM_PhysicalPackage instance. chassis1 also has a representation of its fan configuration capacity through capacity1. capacity1 indicates that chassis1 can have a maximum of two fans and should have at least one fan.

Configuration capacity 1 object diagram

## State description: ConfigurationCapacity2

The following figure shows an object diagram that represents another possible instantiation of this profile that exposes information about the configuration capacity of two cards.

Todo: This description so far is a plain copy of the profile text and needs to be updated.

In this instantiation, the chassis1 has two cards (card1 and card2) that hold processors. The configuration capacity for card1 is represented by capacity1 because they are associated through the instance of CIM_ElementCapacity. In the same way, card2's configuration capacity is represented by capacity2. Because the VendorCompatibilityStrings property value for capacity1 is equal to the VendorCompatibilityStrings property value for capacity2, the maximum number of compatible processors could be determined by adding the MaxCapacity property value of capacity1 to the MaxCapacity property value of capacity2. In this case, the chassis1 could contain a maximum of four processors.

Configuration capacity 2 object diagram

## State description: NetworkPortConnector

The following figure shows an object diagram that represents another possible instantiation of this profile that exposes information about the connector of a network card.

Todo: This description so far is a plain copy of the profile text and needs to be updated.

In this instance, chassis1 contains a network card, card1. card1 has an RJ45 connector, connector1. connector1 is the physical representation of nic1 network port within system1.

Network port connector object diagram

## Use case: DeterminePartNumberOfComponent

This use case describes the flow to determine the part number of a failing physical element.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  Select the CIM_PhysicalElement subclass instance that is associated through the CIM_Realizes association to the CIM_LogicalDevice component that has a HealthState or OperationalStatus property value indicating that the component is in a failure mode. Get the PartNumber property value for the selected CIM_PhysicalElement subclass instance.

## Use case: GetPhysicalInventoryOfSystem

This use case describes the flow to obtain the physical inventory for all devices within a system.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  Select the CIM_System instance representing the given system. Select all the CIM_LogicalDevice subclass instances that are associated with the CIM_System instance through the CIM_SystemDevice association, and select all the CIM_System instances associated through CIM_SystemComponent associations, and then follow the CIM_SystemDevice association to select all the CIM_LogicalDevice subclass instances. Get all the property values of the CIM_PhysicalElement subclass instances that are associated to the selected CIM_LogicalDevice subclass instances through the CIM_Realizes association and to the selected CIM_System instances through the CIM_SystemPackage association.

## Use case: GetPhysicalInventoryOfSystemChassis

This use case describes the flow to obtain the physical inventory for a system chassis.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  Get all the property values of the Physical Package instances that are associated through the CIM_SystemPackaging association with the CIM_System instance representing the given system.

## Use case: DetermineSlotIsEmpty

This use case describes the flow to determine whether a slot is empty.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  Select all the CIM_ElementInConnector instances that reference the CIM_Slot instance that represents the given slot. If no instances of CIM_ElementInConnector that reference the CIM_Slot instance exist, then the slot is empty; otherwise the slot is occupied by the physical package represented by the instance of CIM_PhysicalPackage referenced by the CIM_ElementInConnector association instance.

## Use case: GetFanCapacityOfChassis

This use case describes the flow to retrieve the fan capacity for a chassis.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  For the CIM_Chassis instance that represents the given chassis, select the associated instances of CIM_ConfigurationCapacity through the CIM_ElementCapacity associations. Select CIM_ConfigurationCapacity instances that have the CIM_ConfigurationCapacity.ObjectType property of 3 (Fan).

## Use case: GetMaxFanCapacityOfChassis

This use case describes the flow to retrieve the maximum capacity of the type of fan package within a chassis.

The main flow for this use case consists of the following single step:

- Todo: This description so far is a plain copy of the profile text and needs to be updated.

  The particular type of fan package is identified through the given string, which is an element of the VendorCompatibilityStrings array property of the Physical Package representing the fan package. Select all the instances of CIM_ConfigurationCapacity associated with the CIM_Chassis instance through instances of CIM_ElementCapacity where the VendorCompatibilityStrings array property of the instance of CIM_ConfigurationCapacity contains elements equal to the given string. Add all the values for the MaxCapacity property of the selected CIM_ConfigurationCapacity instances.

#
(informative)
Change log

Change log
Version | Date | Description
--- | --- | ---
1.0.0b | 2006-06-28 | DSP1011: Preliminary Standard
1.0.0 | 2007-11-12 | DSP1011: Final Standard
1.0.1 | 2008-06-09 | DSP1011: Incorporated errata submitted for the Final Standard.
1.0.2 | 2009-06-04 | DSP1011: DMTF Standard Release. Incorporated errata on CIM_PhysicalMemory.Speed property values for unknown or variable speeds.
1.0.3m | 2011-08-31 | XMP1011: Included as a sample profile into DSP2023

# Bibliography

This clause lists references that are helpful for the application of this document.

DMTF DSP1000, Management Profile Specification Template 1.1,
http://www.dmtf.org/standards/published_documents/DSP1000_1.1.pdf