As configuration items are discovered and imported into Maximo IT as actual configuration
items, further reduction of the amount of data can take place.
About this task
The discovery process collects a large amount of data about a large number of
configuration items (CIs). As the discovered CIs are processed to become authorized CIs that you
will manage, Maximo IT processes refine the data to include only the information
that you want to manage.
This refinement takes place in each step along the path from discovered CIs to
authorized CIs:
Procedure
- In your initial configuration of the discovery and data transfer process, you can
use the CI Types application to choose the types of CIs that you want to import. Other configuration
items will still be present in the discovered data in the TADDM database, but they will not be moved to the Maximo
database within Maximo IT.
- When you configure Integration Composer, you can specify the number of levels of
CI data that you want moved from TADDM to Maximo IT. If you are not interested in the CIs that are many
levels down the hierarchy, you can exclude them from becoming actual CIs. You can specify a default
depth as well as individual depth values for each top-level CI type. You can also specify that
certain types of CIs should never be imported.
These first two steps give you the opportunity to decide how much of the discovered
CI data in the TADDM database becomes actual CI data in the Maximo database.
The actual CIs are always a proper subset of the discovered CIs; no additional CIs, attributes, or
other data are added to the actual CIs.
If you are importing IDML data directly, without using TADDM, filtering settings are not used. You must control the
actual CIs that are imported by controlling the contents of the IDML files.
- The final step in refining the CI data is in the creation of authorized CIs from
actual CIs. When you promote an actual CI to create an authorized CI, you can specify which child
CIs and which attributes to include. At the same time, if you wish, you can add some attributes
which are not discovered to your authorized CI. Thus the authorized CIs might or might not be a
proper subset of the actual CIs. Before you promote actual CIs to authorized CIs, you will define an
authorized CI space that specifies which data to include.