CSDM implementation stages — Run

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of CSDM Implementation Stages — Run

    In the Run stage of the Common Service Data Model (CSDM) implementation, you establish the relationships between technology offerings and the businesses that use or sell them. This stage emphasizes the significance of understanding technology's impact on business operations through IT Service Management (ITSM).

    Show full answer Show less

    Key Features

    • Impact Assessment: Run-stage operations facilitate impact assessments for Incident Management and Change Management by identifying affected businesses based on existing relationships between Configuration Items (CIs) and impacted businesses.
    • Service Portfolio Management: Provides a foundation for Digital Portfolio Management (DPM), enabling service owners to monitor service trends, performance, and outages.
    • Subscription Identification: Populates the “Subscribe by” table on service offerings, identifying subscribers based on user, company, location, department, and group.
    • Logical CIs: Focuses on logical CIs, which are not created through Discovery but should be associated with product models to support product-centric management.

    Key Outcomes

    • Establishing a comprehensive business service portfolio that aligns with business objectives.
    • Utilizing the business service table to identify dependencies between business services and the underlying technology infrastructure.
    • Configuring business service offerings that define service commitments such as availability and pricing to meet specific technical needs.
    • Managing a request catalog to present available products and services for user self-service, enhancing overall service delivery.

    In the Run stage, you set up the relationship between a technology and the business that sells and/or consumes the technology.

    ITSM considerations during the Run stage

    When you use ITSM, you must understand the impact that a technology can have on your business. For example, your business may:
    • Consume the technology.
    • Sell the technology (as is the case with Customer Service Management).
    • Both sell the technology and consume it.

    Benefits of the operations that you perform in the Run stage

    • Run-stage operations ensure impact assessment for Incident Management and Change Management. Within an incident or change, you can identify the impacted business, assuming relationships exist between the selected CI and the impacted businesses.
    • Run-stage operations provide a foundation for using Service Portfolio Management in the Digital Portfolio Management (DPM). Service owners can monitor service portfolios and understand service-related information including service trends, improvement initiatives, service performance, and outage monitoring.
    • Run-stage operations provide a foundation for ITSM capabilities. This foundation populates the related “Subscribe by” table on a service offering to identify the business and subscribers affected. Business service offerings can identify subscribers by user, company, location, department, and group.

    Tables that you work on during the Run stage

    Tables that you work on during the Run stage.

    Note:
    Some of the classes that you implement in this stage are logical CIs. Logical CIs aren’t created through Discovery, so their Model ID values might not refer to product model (application model, service model, or software model) records. To help you to migrate to a product-centric management paradigm, each instance of a logical CI should be associated with a product model. See Auto-generate product models for logical CIs.
    Business service portfolio table [service_portfolio]
    Note:
    The Business service portfolio is not a CMDB table.

    A business service portfolio is not a CMDB table. A business service portfolio is a hierarchical collection of business services (products and services) that define a business objective.

    Business service table [cmdb_ci_service_business]

    The business service table is a base-system CMDB table. This table identifies a business objective that uses (and depends on) the infrastructure that technology uses.

    This dependency means that the business service must sell or consume that infrastructure.

    Business service offering table [service_offering] (service offering classified as a "business service")

    Business service offerings are the starting point for configuring Service Portfolio Management. Business service offerings consist of one or more service commitments. These service commitments uniquely define the level of service in terms of availability, scope, pricing, and other factors.

    The business service offering comes from the service. The business service offering is fine-tuned based on how the parent serves a specific technical need.

    Every business service should have at least one business service offering.

    Request catalog
    A catalog (sometimes called a request catalog or service request catalog) is a set of business and technical products, services, service commitment options, and offerings that users can order on a self-service basis. You can manage a catalog to present your available products and services to users as catalog items. Catalogs are described in detail in Service Catalog.