In TSCO, what causes systems to appear in the Newly Discovered, Unassigned, and Dismissed systems lists?

Version 6

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Capacity Optimization


    Capacity Optimization


    All TSCO versions


    In the TrueSight Capacity Optimization (TSCO) console under Workspace -> All Systems and Business Drivers there are four categories:

    1. Newly Discovered (listed in search results)
    3. Unassigned  (listed in search results)
    5. Dismissed  (not listed in search results)
    7. Unreachable  (not listed in search results enhancement request  QM002383468 created to list unreachable entities in search results)

    What causes systems to end up in those various categories?



    Systems will appear in the Newly Discovered systems list when they are newly imported by an ETL. They could me moved in the tree in two ways:

    1. Manually: using the wizard
    3. Automatically: using a Hierarchy Rules if one of the ETLs that import data for this systems have relationship information (OJBREL dataset)

    Systems end up in the Unassigned group when they have been deleted from a domain. In can happen in two ways:

    1. Manually: using button Delete
    3. Automatically: if a systems is managed by a Hierarchy Rule, if the ETL will not discovered it, it will be removed from the tree and moved in dismissed
       Note: if you are using one of the Generic ETL (like CSV parser or Database Extractor and selected the option Move all new entities in an Domain  ) the systems will be only moved from Newly Discovered under a Domain, but they will never automatically moved into Unassigned. You have to follow the manual step   

    The data collection is not stopped for systems in this node.
    Also, if a system is managed by a hierarchy, if the ETL will discovered back, it will moved again on the tree.


    Systems end up in Dismissed when they have been deleted from the Unassigned category.
    It can happen

    1. Manually: using button Delete
    3. Automatically: enabling the automatic purge. This feature is available from CO 10.7 (please see official documentation, page Enabling automatic dismissal and purging of systems and business drivers).

    New data are not imported for systems in the Dismissed, but the existing data hasn't yet been deleted from the CO data warehouse.

    To delete systems and purge data from the data warehouse, there are two options:

    1. Manually: using button Delete for a single system or button Clean up all dismissed objects to delete all
    3. Automatically: if you enable automatic purge

    After the systems have been removed from dismissed the data has really been deleted and there is no way to restore the data for those systems within BO itself (you'd need to re-import the data via a new ETL).


    Systems end up in Unreachable when they are still in active status but they haven't a parent node in the tree. Usually it happens when there is a problem with relationship management (ETL + Hierarchy rule). A list of unreachable entities can be retrieve using this sql command "select * from v_ent_def_unreacheable".


    See the Life cycle and status of entities and domains section in the TSCO product documentation for additional information regarding systems management.

    A note: this consideration are valid for system, business drivers and domains, excluding the automatic purge: this feature works only with systems and business drivers, but not with domains.

    Legacy ID:KA356596


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles