Functionalities > Service Modeling

Service Modeling

Note Service Modeling is supported on UCMDB 10.22 (or later) with Content Pack 18 (or later).

Service Modeling enables you to model the infrastructure of a business service. A service can be regarded as a perspective-based view on a particular CI. When the discovery process runs, relationships between a CI and its owner and a CI and its stakeholders are found, triggering additional rounds (also referred to as "hops") of discovery for those related CIs.

Note  

  • The link for a consumer-provider relationship between CIs is indicated with a blue line; otherwise the link is indicated with a black line. Also, all the incoming and outgoing links for a selected CI are represented with bolded lines.
  • Starting with UCMDB Browser 4.10 (or later) and UCMDB 10.30 (or later), previously created models in the UCMDB UI and UCMDB Browser can now be opened from Service Modeling. This includes Instance Based Models, Pattern Based Models, models created in the Service Discovery module in UCMDB UI, and models created through Assisted Modeling. The Discovery and Save Layer actions are disabled for these models.

You can model services, as well as run discovery and troubleshoot the discovery process. New service models are based on CI types that have the SERVICE_MODEL qualifier in UCMDB. After running discovery, you are able to view the discovered CIs in the context of that business service.

When you create a new service model in the UCMDB Browser, a discovery activity and a perspective-based view with the same name are created in UCMDB, based on the Service_template perspective. In addition, when you create a template-based model, the view also contains the specific perspective that you select when you create the model.

You can also access the Assisted Modeling feature in the UCMDB Browser through the Service Modeling module. For more information, see Assisted Modeling.

Note  

  • To enable a user to access the Service Modeling module in the UCMDB Browser, in the Roles Manager in UCMDB, click the General Actions tab and add the Service Modeling permission (in the Data Flow Management Actions group) to the selected role.
  • To enable a user to create service models, assign Create permission for at least one CI type that has the SERVICE_MODEL qualifier assigned to it.
  • Users who have only View permission for a CI (and not Edit permission) will view the topology map in read-only mode.
  • To enable access for a user to access a particular view, in the Roles Manager in UCMDB, click the Browser CI Access Control tab and assign View permission to that view.
  • To enable a user to run discovery in the Service Modeling module starting from a URL, in the Roles Manager in UCMDB, click the General Actions tab and add the Run Discovery and Integrations permission (in the Data Flow Management Actions group) to the selected role.

For more information about models, see the Universal CMDB Modeling Guide.

The Service Modeling module is divided into two sections:

  1. Service Modeling Dashboard

    The Service Modeling dashboard displays existing service models. The last service model displayed automatically opens when you open the Service Modeling module.

    The Service Modeling Dashboard displays a thumbnail for each service model, grouped by the state at which the model was deployed. You can hide the service models from a specific group simply by clicking the group's name. Each thumbnail includes:

    • The name of the service model.
    • The CI type on which the service model is based.
    • The owner, if one exists for the service. If no owner exists, you can select one on the map by clicking .

    • An icon showing the business criticality, indicating the relative importance of the service to the business.

  2. Service Modeling Left Panel

    In the left panel you can do one of the following:

    • Create a service model.
    • Start assisted modeling. For more information, see Assisted Modeling.
    • Search for a service model by name.
    • Filter the discovered models by owner.
    • Expand or collapse the service models in the dashboard according to their state at which the model was deployed.