An example of the automatic propagation of impact notifications is shown in Automatically propagated impact notification scenario. In this example, the Trade Settlement BusinessProcess depends on a Trade Settlement Application.

Figure 1. Automatically propagated impact notification scenario

When viewing the Business Services map, remember that it shows dependent relationships through arrowed lines: The arrowed lines point from a business element to the element that the business element depends on. Impact notifications propagate in the direction opposite to that of the arrowed lines: The impact notifications propagate toa business element from the element that the business element depends on.

To aid in understanding, read the relationships in Automatically propagated impact notification scenario from top to bottom and left to right. For example, TradeAccntgFinCntr (Trade Accounting Financial Center) is served by Trade Netting, and Trade Netting is served by Trade Settlement.

When the Trade Settlement Application is Degraded (severity level 2, Major notification), the degradation causes Business Impact Manager to generate an impact notification for the Trade Settlement BusinessProcess.

Thus, Trade Settlement Application Degraded causes Trade Settlement Impacted. From Trade Settlement BusinessProcess, the impact notification propagates to any dependant business processes—that is, any business processes that Trade Settlement serves. These are the Trade Reconciliation and TradeAccntgFinCntr BusinessProcesses.

The Trade Reconciliation Impacted and TradeAccntgFinCntr Impacted notifications then propagate further to any business processes served by these processes: to the Trade Netting BusinessProcess from TradeAccntgFinCntr Impacted and, once again, to TradeAccntgFinCntr from Trade Reconciliation Impacted.

As a result, Business Impact Manager generates an impact notification for Trade Settlement, Trade Reconciliation, TradeAccntgFinCntr, and Trade Netting.