Navigating the Digital Landscape: The Power of CSDM and CMDB

Organizations often develop and maintain their digital product and service architecture within dedicated architecture repositories, document stores, or web pages, typically in the form of diagrams. While this information might serve certain use cases, such as new product design, it lacks the depth and visibility offered by a CMDB that encompasses all events throughout the digital product lifecycle.

The Role of CMDB in Digital Product Lifecycle Management

The CMDB is the digital foundation of an organization. The centralized architecture representation within a CMDB allows for better management of teams and roles associated with each component of the digital product or the digital product itself. With accurate and up-to-date information readily accessible within component details, events like incidents and requests can be swiftly assigned to the appropriate team. 

The most effective CMDBs are business-aware, enabling stakeholders to understand the business impact of each component. For instance, they can determine which digital product or business service a server supports.

Introducing CSDM: A Common Language for Enhanced Collaboration

CSDM, or the Common Service Data Model, provides guidance on how to categorize and record various items within an organization’s CMDB. These items encompass both physical components like cloud resources, switches, and routers, as well as software entities and logical components such as digital products and services.

The Common Service/Product Data Model (CSDM) sets the standard for data entities and the relationships among them, ensuring that information pertaining to products and services can be effectively utilized by all business units in the context of various business processes. By fostering a unified language among individuals, processes, and technologies, CSDM facilitates seamless sharing and enrichment of data across the entire spectrum of Product/Service Development and Operations.

CSDM creates one single language between people, processes, and technology that allows seamless sharing and enrichment of data across the entire spectrum of Product/Service Development and Operations. This integration provides end-to-end visibility into the architecture of digital products, enabling real-time correlation of events with product components across the CSDM.

Use Cases: How CSDM/CMDB Benefits Various Stakeholders

From consumers to technical service owners, CSDM/CMDB offers a multitude of benefits across different stakeholders.

  • Consumer Perspective:
    • Understand the offerings, service levels, and associated costs of products and services.
    • Receive timely communications when a consumed product/service is impacted by an incident or a planned maintenance window.
  • Product Owner’s Perspective:
    View dependencies of products/services when planning changes.
  • Business Relationship Manager’s Perspective:
    View dependencies of products/services when planning changes.
  • Technical Service Owner’s Perspective:
    • Determine service impacts and identify incident root causes by leveraging product architecture/composition. 
    • Identify product/service consumers and communicate service impacts to them.
    • Prioritize events with insight into how they relate to products/services.
    • Understand the total cost of a product/service, considering all underpinning components and associated events.

Real-World Example: E-Commerce Bookstore Architecture

Let us take the following example of a digital product and its simplified architecture.

In ServiceNow, the E-Commerce Bookstore is defined as follows:

  1. Product model that identifies products developed by agile teams, ensuring that all epics, features, and stories are aligned with a specific product model.
  2. Once the product is deployed to production or other environments, and eventually released to users, it is defined as a Business Service Offering under the product model of the developed product. 

Users subscribe to the product, enabling real-time calculation of the number of impacted users in the event of incidents with the product or service. Incident prioritization is then based on the number of impacted users.


The user submitting the incident or the support agent can select the suspected configuration item from among the components which comprise the architecture of the digital product displaying symptoms.

The architecture visualization is accessible from each incident, problem, change, and other events.

Once a suspected failed component is selected, the assignment group list is populated with the support and change groups recorder in the item itself. 

Streamlining Incident Management with CSDM and CMDB

Efficient incident management and change processes are critical for ensuring operational excellence. With CSDM and CMDB, organizations can streamline incident management by allowing users to select suspected configuration items from the digital product architecture, thus facilitating quick resolution.

There is no need to define the support and other teams individually for each component. Instead, teams are defined for the technical service offerings and are then inherited by all components within those offerings. For instance, organizations often appoint an internal team responsible for many components of the same type, such as iPads used in the bookstores of one region, while contracting support vendors to provide field support. 

The internal support team and the vendor support team are defined within a single technical service offering.  A query is written to maintain dynamically a group of all iPads in the region, which is subsequently added to the technical service offering. All iPads automatically inherit the support groups from the technical service offering configuration.

If an incident is assigned to the change group, which corresponds to the agile product implementation/development team, the team can add agile backlog/user story information to the incident and incorporate it as a user story into their backlog. The E-commerce Blue team functions as an agile team responsible for developing the MarketPlace platform. Their backlog encompasses both new features and incidents. 

Embracing the Future of Digital Product Management

The combination of CSDM and CMDB offers a powerful solution for managing digital product architecture and enhancing operational efficiency. By standardizing data entities, fostering collaboration, and providing end-to-end visibility, organizations can effectively navigate the complexities of the digital landscape and deliver exceptional products and services to their customers.

If you’re looking to streamline your digital product architecture and optimize incident management processes, look no further. Our ITCE team is here to guide you through the implementation of CSDM and CMDB solutions. With our extensive experience, we can help transform your organization’s approach to managing digital digital products and services. Contact us at businessdev@itce.com to learn more about how we can support your journey towards efficient digital product architecture management.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close