Transaction data from different data sources is loaded into CA CMDB. Each data source uses its own subset of identifying characteristics and may not fully identify the target CIs for the transactions. Because of this inconsistency, more CI Transactions may exist in CA CMDB than are valid.
The following is an example of CI transaction ambiguity:
Example: Ambiguous CI Transactions
The following CI transaction resides in the TWA:
The following CIs reside in CA CMDB:
Due to shared identifying characteristics, Server1 transaction is ambiguous with Server2, Server3, and Server4 in CA CMDB.
Every CI Transaction has an ambiguity index associated with it. The ambiguity index is approximately the number of existing CIs that match on any of the identifying attributes, minus one, specified in the CI transaction. The greater the index, the greater the number of other CIs that match on the transaction identifiers, and therefore the greater the probability that CI data was entered inconsistently and the possibility that additional CIs are incorrectly created. CI Transactions with an ambiguity index of zero have identifying attributes that are unique across all CIs or have a target CI specified and are therefore unambiguous.
Example: Calculate the Ambiguity Index
The following CI transactions reside in the TWA:
The following CIs reside in CA CMDB:
The first transaction (Server1) ambiguity is 0 because there is an exact match with the Server1 CIs identifying attributes. The only possible target CI to this transaction is Server1 CI.
The second transaction (Server2) is ambiguous with Server1 CI and Server2 CI.
The ambiguity index for Server2 transaction consists of the following components:
Based on shared CI identifying characteristics, the ambiguity index for server2 transaction is (1-1) + (2-1) + (2-1) = 2
|
Copyright © 2013 CA.
All rights reserved.
|
|