Dell OpenManage Client Instrumentation Version 8.1 : Reference Guide : Page 74

The Reference Guide contains the

file:///T|/htdocs/SOFTWARE/smcliins/cli81/en/refgd/index.html[10/19/2012 10:01:19 AM]

25 = IEEE 1394 Controller

26 = Partitionable Unit

27 = Base Partitionable Unit

28 = Power

29 = Cooling Capacity

30 = Ethernet Switch Port

31 = Logical Disk

32 = Storage Volume

33 = Ethernet Connection

.. = DMTF reserved

0x8000..0xFFFF = Vendor Reserved

DCIM_AssetAcquisition

CostCenter Identifying information for the accounting unit withinthe purchasing company that authorized the purchase.

ElementName

The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query.

Note: The name does not have to be unique within a namespace.

InstallationDate Date the system was put into service by the purchasing company.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the

following "preferred" algorithm:

Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the

InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to

ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.

<LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting

InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.

For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.

PurchaseCost

The Purchase Cost field accepts whole numbers only.Entering commas, decimal points, or dollar signsresults in an error message.

Value expressed incurrency unit that was paid for the system, for example, 25000.

Possible values are:

0..32767 = DMTF Reserved

32768..65535 = Vendor Reserved

PurchaseDate Date the transaction for acquiring the system was completed.

ReferenceToDeliverySlip

Identifying information for the waybill or delivery slip, such as a waybill number.

Possible values are:

0..32767 = DMTF Reserved

32768..65535 = Vendor Reserved

ReferenceToPONumber

Number of the purchase order that authorized buying the system.

Possible values are:

0..32767 = DMTF Reserved

32768..65535 = Vendor Reserved

DCIM_AssetExtendedWarrantyInformation

Cost

Displays the total cost of the warranty service on a system.

Possible values are:

0..32767 = DMTF Reserved

32768..65535 = Vendor Reserved

ElementName

The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query.

Note: The name does not have to be unique within a namespace.

EndDate Displays the date that extended warranty service ends.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the

following "preferred" algorithm:

Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the

InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to

ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.

<LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting

InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.

For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.

ProviderName Displays the name of the business that is providing warranty service to the system owner.

StartDate Displays the date that extended warranty service begins.This date usually follows the standard warranty service.

DCIM_AssetOwnerInformation

ElementName

The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query.

Note: The name does not have to be unique within a namespace.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the

following "preferred" algorithm:

Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the

InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to

ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.

<LocalID> is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting

InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.

For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.

InsuranceCompany The company that insures the system against theft or other loss.

OwnerName The individual or business entity that holds legal title to the system.