This documentation supports the 9.1.04 version and its patches of BMC Atrium Core. The documentation for version 9.1 to 9.1 Service Pack 3 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Building a service model

The main purpose of creating or publishing a service model to Infrastructure Management is to be able to see how CI failures propagate and impact the upstream services.

This information is then used to visualize the impact to a service and to automatically open Intelligent Incidents that contain information about the failed or failing IT components and services it impacts for further prioritizataion and faster troubleshooting.

A service model is a collection of components (also known as configuration items (CIs)) that represents a business service. A business service can have one or more business processes. Each business process can contain several functional applications, each of which can have multiple IT CIs. A service model will contain the processes, show how the CIs are interconnected.

The best service models are enterprise-specific, achieving the organization’s business availability goals. The IT environment, its organization, and its operational constraints vary significantly among enterprises.

A cost-effective strategy when you begin the process of building a service model is to select one critical business process/service, decompose it to identify all aspects of the service, and build a complete service model for that part of your enterprise.

A Infrastructure Management user can create a service model either directly in the Infrastructure Management's Administration Console, or using the BMC Impact Model Designer tool, which is part of the BMC Atrium solution, if BMC CMDB integration is used for service model creation.

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