UCMDB Support Tip: How to Create and Manage Downtimes for CIs. UCMDB BSM RTSM Integration

When determining which CIs may need downtimes, take into consideration what kind of impact the CIs you selected will have.

To understand the downtime impact model, please refer to the BSMDowntime_topology TQL in the RTSM Modeling Studio.

By default, BSMDowntime_topology TQL is hidden. To view this TQL in the Modeling Studio go to Admin > RTSM > RTSM Admministration > Administration > Package Manager > Tools > User Preferences > General Show hidden queries and set the value to True.


You can only select CIs from the following CI types:

  • Node
  • Running_software
  • Business_application
  • Ci_collection
  • Infrastructure_service
  • Business_service

To determine which actions should be applied to which CIs. The options for what happens during downtime are:

  • Take no actions
  • Suppress alerts and close events
  • Enforce downtime on KPI calculations; suppress alerts and close events
  • Enforce downtime on Reports and KPI calculations, suppress alerts and  close events
  • Stop monitoring (BPM and SiteScope); enforce downtime on Reports & KPI calculations’ suppress alerts and close events (affects all related SLAs)

For further details please reference to BSM Platform Administration Guide Chapter 20: Downtime Management.