How component status computation works

The cell computes component status automatically as new conditions occur, such as the reception of a direct impact event, or a status change on a provider component that results in a state change on an inbound relationship.

To compute component status, the cell uses the status computation model assigned to a CI. The cell obtains the name of the status computation model to use from StatusComputationModel slot  of the instance..

Based on the type of condition that triggered the status computation, the cell selects the appropriate function to use from the status computation model. It also obtains the algorithm to use with the function to calculate the appropriate status for the component. Then, the cell calculates the new component status.

Status computation functions

The following functions perform status computation:

  • self_function
  • impact_function
  • consolidate_function

The following table lists the functions, their inputs, and the type of computed status that each function calculates:

 Status computation functions and computed component statuses






Computes the self_status from direct events

Severities of direct events associated with the component



Computes the impact status from status propagated by provider components

Status values propagated by inbound relationships



Computes the component's computed_status from impact_status and self_status, or both, or from the no_alert_status of the status computation model

The impact status and the self-status


All the functions return a status value in the range of the MC_SM_COMPONENT_STATUS enumeration.

Only the cell maintains the real-time status of components. Component status is not reflected in the BMC Atrium CMDB.

The CI's status is set to computed_status except when you set the component to manual status, in which case, the CI's status is set to manual_status.

Was this page helpful? Yes No Submitting... Thank you