Class CIM_PhysicalElement
extends CIM_ManagedSystemElement

Subclasses of CIM_PhysicalElement define any component of a System that has a distinct physical identity. Instances of this class can be defined in terms of labels that can be physically attached to the object. All Processes, Files, and LogicalDevices are considered not to be PhysicalElements. For example, it is not possible to attach a label to a modem. It is only possible to attach a label to the card that implements the modem. The same card could also implement a LAN adapter. These are tangible Managed System Elements (usually actual hardware items) that have a physical manifestation of some sort. A Managed System Element is not necessarily a discrete component. For example, it is possible for a single Card (which is a type of Physical Element) to host more than one Logical Device. The card would be represented by a single Physical Element associated with multiple Logical Devices.

Class Hierarchy

CIM_ManagedElement
   |
   +--CIM_ManagedSystemElement
   |
   +--CIM_PhysicalElement

Direct Known Subclasses

CIM_PhysicalPackage
CIM_PhysicalFrame
CIM_Rack
CIM_Chassis
CIM_Card
CIM_SystemBusCard
CIM_StorageMediaLocation
CIM_Magazine
CIM_PhysicalComponent
CIM_Chip
CIM_PhysicalMemory
CIM_PhysicalMedia
CIM_PhysicalTape
CIM_PhysicalLink
CIM_PhysicalConnector
CIM_Slot

Class Qualifiers

NameData TypeValueScopeFlavors
AbstractbooleantrueTOSUBCLASS= falseOVERRIDABLE= false
DescriptionstringSubclasses of CIM_PhysicalElement define any component of a System that has a distinct physical identity. Instances of this class can be defined in terms of labels that can be physically attached to the object. All Processes, Files, and LogicalDevices are considered not to be PhysicalElements. For example, it is not possible to attach a label to a modem. It is only possible to attach a label to the card that implements the modem. The same card could also implement a LAN adapter. These are tangible Managed System Elements (usually actual hardware items) that have a physical manifestation of some sort. A Managed System Element is not necessarily a discrete component. For example, it is possible for a single Card (which is a type of Physical Element) to host more than one Logical Device. The card would be represented by a single Physical Element associated with multiple Logical Devices.None TRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
CreationClassNamestring
DescriptionstringCreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
ManufactureDatedatetime
DescriptionstringDate that this PhysicalElement was manufactured.None TRANSLATABLE= true
Manufacturerstring
DescriptionstringThe name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.None TRANSLATABLE= true
MaxLenuint32256None None
Modelstring
DescriptionstringThe name by which the PhysicalElement is generally known.None TRANSLATABLE= true
MaxLenuint3264None None
OtherIdentifyingInfostring
DescriptionstringOtherIdentifyingInfo captures additional data, beyond that of Tag information, that could be used to identify a PhysicalElement. One example is bar code data associated with an Element that also has an asset tag. Note that if only bar code data is available and is unique/able to be used as an Element key, this property would be NULL and the bar code data used as the class key, in the Tag property.None TRANSLATABLE= true
PartNumberstring
DescriptionstringThe part number assigned by the organization responsible for producing or manufacturing the PhysicalElement.None TRANSLATABLE= true
MaxLenuint32256None None
PoweredOnboolean
DescriptionstringBoolean indicating that the PhysicalElement is powered on (TRUE), or is currently off (FALSE).None TRANSLATABLE= true
SerialNumberstring
DescriptionstringA manufacturer-allocated number used to identify the PhysicalElement.None TRANSLATABLE= true
MaxLenuint3264None None
SKUstring
DescriptionstringThe stock keeping unit number for this PhysicalElement.None TRANSLATABLE= true
MaxLenuint3264None None
Tagstring
DescriptionstringAn arbitrary string that uniquely identifies the PhysicalElement and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for PhysicalElement is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
Versionstring
DescriptionstringA string indicating the version of the PhysicalElement.None TRANSLATABLE= true
MaxLenuint3264None None

Inherited Properties

NameData TypeClass Origin
CaptionstringCIM_ManagedElement
DescriptionstringCIM_ManagedElement
InstallDatedatetimeCIM_ManagedSystemElement
NamestringCIM_ManagedSystemElement
StatusstringCIM_ManagedSystemElement