Identification and documentation of business processes - Documentation for BMC CMDB 19.02

The purpose of decomposing a business service is to identify and document business processes, identify the IT (technical) services that support them, and identify IT components and assets that provide the technical services. Business processes are determined at a high level and can include other processes, such as Marketing and Sales. This document focuses on how business services are impacted and supported by IT.

For example, the online banking division of Calbro Services might identify a business service as the ability of customers to transfer funds, a common service for an online banking company. A technical service that supports this service is the maintenance of the network on which the servers that facilitate the fund transfer communicate. The supporting IT assets are the servers, databases, and related hardware and software systems that facilitate the fund-transfer service.

The following figure depicts a scenario in which the application server resides on a virtual machine (VM), which, in turn is running on a server capable of hosting several VMs. The system is set up so that, if one VM fails, another VM resumes the process without interruption. The fund-transfer business service depends on everything in the gray box, which IT provides and supports.

 Example of a business service and the supporting IT assets

The fund-transfer service is only one business service provided by Calbro Services. The service model created by Calbro Services is a collection of service components, each of which represents a business service. Each component can contain several functional applications, each of which can have multiple IT components. A service model shows how the components are interconnected and shows how component failures can impact other services. See Example of a service model.

Best practices

When decomposing a business service, consider the following best practices:

  • To find IT services and the components that support them, look at service level agreements and operational level agreements.
  • Determine the entry point to each service model, the highest object in the model. The entry point depends on who is consuming the model. Working from here down to the bottom of a service model makes sure that you operate from the perspective of the business.

Identifying business services

To identify business services, start by gathering information from such sources as business unit managers, business process managers, and staff personnel knowledgeable about the business services. Company organization charts might be helpful in identifying the relevant people. 
The process involves interviewing the managers and identifying the following information:

Identifying technical services

To identify technical services, consult IT managers and staff. Disaster recovery plans, help desk documents, and purchase orders might be useful in identifying IT components and the business processes that they support.

The process involves identifying the list of IT assets (components). Interview the IT management and staff, or use an asset database or CMDB as resources:

As you build your model, use whatever tools you have to depict the dependencies between business services and technical services. Use graphical and spreadsheet software if you do not have a solution such as BMC Impact Solutions. The following table shows a portion of a spreadsheet depicting a few business services and their relationships.

 Portion of a sample business service model spreadsheet 

Business serviceBusiness functionsBusiness processesTechnical servicesIT component
24/7 online bankingTransfer fundsOperational efficiencyAdministrative software and hardwareSoftware applications, application servers, virtual machines, databases
Pay bills
Discount equity servicesExecute trades
Manage customer relationsFront office salesResponse managementIncident tracking softwareApplication server
Customer supportSupport service requestsFTPServer: FTP
SprintServer: Walrus
Sales LogixDatabase: SALLOG Applications: Sales Logix User group: Tech Support dept Servers: Antelope

Planning a service model

Service model design considerations

You Might Also Like