This documentation supports the 23.3 version of BMC Helix ITSM.To view an earlier version, select the version from the Product version menu.

Loading BMC Asset Management data

Loading Asset Management data is mainly comprised of loading CIs, attributes, CI relationships, and reconciliation.

CI and inventory attribute dataload process

Once CI data is loaded successfully to the CMDB forms then attribute data is loaded to the AST:Attributes form. During validation, CI data in the CMDB forms is reconciled with the attribute data through the AST:LoadAttributes staging form. Once validation is successful, CI data is promoted to the BMC.ASSET production dataset and AST:LoadAttributes data is promoted to the AST:Attributes form.

Related topics

Completing-steps

Creating-and-managing-data-load-jobs

Usage of the CI Name field as a unique identifier

The CI Name field is a required field for loading CIs and CI relationships. The CI Name field is also the unique identifier for importing asset data. Transformations are built using CI Name as the unique key field.

You must ensure that you have a unique set of CI Name records. If a CI Name is found, this record will be updated during the Load step.

Warning

When you import data from multiple external sources, you must ensure that CI Name integrity is maintained to prevent any erroneous updates from occurring.

Reconciliation rules for supported CIs

As part of the process for reconciling data, CIs go through a merge phase that follows standard merge rules. These rules define precedence values for the supported CIs listed in the table below and ensure that the fields listed below are merged with the production CIs. For more information about the standard merge rules, see the BMC Helix CMDB online documentation.

CI

Fields

Computer System

  • CI Name
  • Serial Number
  • Domain
  • Hostname

Product

Model/Version

Operating System

CI Name

Processor

CI Name

Business Service

CI Name

Loading asset CI relationships

Before you load asset CI relationships data, you should be aware of the following rules:

  • The required CIs should already exist in your system before you load CI relationships. 
  • You should always load data using the BMC.ITSM.CI.DATA dataset in the Load step for your jobs. For more information, see Configuring-an-Atrium-Integrator-job-for-a-Load-step. 

The following CI relationship types are supported out-of-the-box:

Proper name

Normalized name

Relationship type class

Application System Services

APPLICATIONSYSTEMSERVICES

BMC.CORE:BMC_APPLICATIONSYSTEMSERVICES

Component

COMPONENT

BMC.CORE:BMC_COMPONENT

Dependency

DEPENDENCY

BMC.CORE:BMC_DEPENDENCY

Element Location

ELEMENTLOCATION

BMC.CORE:BMC_ELEMENTLOCATION

Hosted Access Point

HOSTEDACCESSPOINT

BMC.CORE:BMC_HOSTEDACCESSPOINT

Hosted Service

HOSTEDSERVICE

BMC.CORE:BMC_HOSTEDSERVICE

Hosted System Components

HOSTEDSYSTEMCOMPONENTS

BMC.CORE:BMC_HOSTEDSYSTEMCOMPONENTS

In IP Subnet

INIPSUBNET

BMC.CORE:BMC_INIPSUBNET

In Segment

BMC_InSegment

BMC.CORE:BMC_INSEGMENT

Inventory Bulk Items

INVENTORYBULKITEMS

BMC.CORE:BMC_INVENTORYBULKITEMS

Inventory Computer Systems

INVENTORYCOMPUTERSYSTEMS

BMC.CORE:BMC_INVENTORYCOMPUTERSYSTEMS

Inventory System Components

INVENTORYSYSTEMCOMPONENTS

BMC.CORE:BMC_INVENTORYSYSTEMCOMPONENTS

IP Subnets in Collection

IPSUBNETINCOLLECTION

BMC.CORE:BMC_IPSUBNETINCOLLECTION

LNs In Collection

LNSINCOLLECTION

BMC.CORE:BMC_LNSINCOLLECTION

Member Of Collection

MEMBEROFCOLLECTION

BMC.CORE:BMC_MEMBEROFCOLLECTION

Segments in Collection

SEGMENTSINCOLLECTION

BMC.CORE:BMC_SEGMENTINCOLLECTION

Account On System

ACCOUNTONSYSTEM

BMC.CORE:BMC_ACCOUNTONSYSTEM

All Related

ALLRELATED

BMC.CORE:BMC_BASERELATIONSHIP

Inventory Equipments

INVENTORYEQUIPMENTS

BMC.CORE:BMC_INVENTORYEQUIPMENT

Settings Of

BMC_SettingsOf

BMC.CORE:BMC_SETTINGSOF

Impact

BMC_Impact

BMC.CORE:BMC_IMPACT

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*