Use case to view a service model from the Central Server
Assume that Calbro Systems has created a discrete service model on a BMC ProactiveNet Child Server. The service model has been promoted and published to the Child Server and can be viewed from the BMC ProactiveNet Central Server.
Assume that a database storage problem leads to a critical impact of the landline service database. If you view the service model in the Operations Console of the BMC ProactiveNet Central Server, not only the landline service database CI (impacting CI) but all its parent CIs are also impacted as illustrated below. That is, the impact is propagated from the impacting CI to all its parent CIs (impacted CIs).
Impacted discrete model
Consider the same scenario for a distributed service model. That is, the landline systems CI is the impacting CI and the impact is propagated to the parent CIs. The following figure illustrates the impacted distributed service model:
Impacted distributed model
You can view details about the CIs on the Related CIs area of the Details Notebook pane. Select a particular CI and click the Details Notebook pane to view its ID, cell details, details of its status and so on. For example, the Details Notebook pane of the discrete service model scenario would resemble the following figure: 
For more information about the Details Notebook pane, see Viewing-the-Details-notebook.
Fixing an impacting CI
To fix an impacting CI, perform the following steps:
- Right-click the impacting CI that is published on the BMC ProactiveNet Child Server, and click Menu > Launch > Events View - Child Console.
The events view in the Operations Console of the BMC ProactiveNet Child Server to which the impacting CI belongs is displayed. - Select the wrench icon for the impacting event and select Probable Cause Analysis. You can use this feature to analyze the cause of the impact and take necessary steps to fix it. For more information about probable cause analysis, see the BMC ProactiveNet User Guide.
After fixing the impacting event, in the Operations Console of the BMC ProactiveNet Central Server, you can see that not only the impacting event but its parent CIs are also fixed.