Applying the CSDM guidelines to Service Portfolio Management
Summarize
Summary of Applying the CSDM Guidelines to Service Portfolio Management
The Common Service Data Model (CSDM) framework enhances Service Portfolio Management by integrating service-related data into a cohesive view. This alignment with services such as Digital Portfolio Management (DPM) helps streamline processes and ensures consistency across ServiceNow applications. Understanding the CSDM life-cycle fields is essential for effective service management.
Show less
Key Features
After activating the CSDM plugin, users can utilize CSDM life-cycle fields within Service Portfolio Management. These fields allow for a structured management of the service life cycle, providing clarity and uniformity across platforms. Key comparisons between traditional and CSDM life-cycle fields include:
- Pipeline | Requirements → Ideation | Under evaluation
- Catalog | Design → Design | Design
- Catalog | Operational → Operational | In-use
- Retired → End of life | Retired
Common terms within the CSDM include:
- Portfolio: A collection of services or products managed together.
- Service: A means of delivering value to customers.
- Service Catalog: A view of available products and services.
- Service Commitment: Delivery obligations between consumers and providers.
Key Outcomes
By applying CSDM guidelines, ServiceNow customers can expect improved service management through enhanced visibility, standardized processes, and more effective alignment with business objectives. This ultimately leads to better service delivery and greater operational efficiency.
Service data relates to each other using different applications in different ways. Service Portfolio Management references the Common Service Data Model (CSDM) framework to bring service-related data together in a single view.
CSDM life-cycle fields for business and technical services
After the CSDM activation plugin is installed [com.snc.cmdb.csdm.activation], you can use the CSDM life-cycle fields in Service Portfolio Management. To see the field names, navigate to , and set the view to Service Portfolio.
Using the CSDM life-cycle fields helps you manage the end-to-end life cycle of services and service offerings. The shared field names provide you with consistency and alignment as you use other ServiceNow applications. For more information about the CSDM, see First activation step — Map existing life cycle data to CSDM standards.
The following comparison shows the differences from the traditional Service Portfolio Management phase and status fields to the CSDM life-cycle stage and status fields.
| Service Portfolio Management Phase and Status field names | CSDM life-cycle Stage and life-cycle Status field names |
|---|---|
| Pipeline | Requirements | Ideation | Under evaluation |
| Pipeline | Definition | Ideation | Under evaluation |
| Pipeline | Analysis | Ideation | Under evaluation |
| Pipeline | Approved | Ideation | Under evaluation |
| Pipeline| Chartered | Design | Chartered |
| Catalog| Design | Design | Design |
| Catalog | Development | Design | Design |
| Catalog | Build/Test/Release | Deploy | Test |
| Catalog | Operational | Operational | In-use |
| Catalog | Retiring | Operational | Pending Retirement |
| Retired | Retired | End of life | Retired |
| Retired | Obsolete | End of life | Obsolete |
Common CSDM terms used in Service Portfolio Management and in DPM
| Term | Definition | Notes |
|---|---|---|
| Portfolio | Collection of services, products, projects, or applications. | Used to manage like items together for a business. Portfolios may be grouped by objective, capabilities, organization, like projects or services. |
| Business capability | High-level capability that an organization requires to execute its business model or fulfill its mission. | Typically described in the context of performing one or more specific tasks to achieve business outcomes. For example, demand management or financial planning. |
| Service | Means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. | Typically has three aspects:
ServiceNow provides three base service types:
Customers can extend the base types to align with the service types in their organization. |
| Business service | A service type that is published to business users and it typically underpins one or more business capabilities. | Typically orderable by business users. Business users are able to select the desired offering and service commitment levels via the ServiceNow Service Catalog. For example, procurement, shipping, and finance. |
| Technical service | A service type that is published to service owners and typically underpins a business or application service. | Typically orderable by service owners. Service owners are able to select the desired offering and service commitment levels via the Service Catalog. For example, computers, storage, and networks). |
| Application service | A service type that is a logical representation of a deployed application stack. | Examples of application services are hosting, data backup, and recovery. Note: There isn’t a 1-to-1 relationship between application and application services. |
| Application | Any deployed program, module, or group of programs that is designed to provide specific functionality on a computer infrastructure. | Defines behavior and has specific functionality associated with it. Applications are typically discoverable functionality, like Apache Web Server. |
| Business Application | Represents all software and infrastructure environments (dev, test, prod) configured to provide functionality. | Used to increase productivity and perform other business functions accurately. For example, Dell Online. |
| Service catalog | Provides a consumable view of available products, services, service commitment options, and offerings. | Helps manage what services a user may have access to. Also, catalogs are the initiation point for access to available services. For example, the IT services catalog. |
| Service offering | A stratification of a service into capability, availability, pricing, and packaging options. | Different levels of performance and features for a given service can be made available. For example, ITSM Standard and ITSM Pro. |
| Service commitment | Defines service delivery obligations agreed to between the consumer and the provider. | Often manifested in the form of contracts such as service level agreements, operational level agreements, and underpinning contracts. Service commitments include specific performance characteristics that differentiate one offering from another. |
| Configuration item (CI) | Physical and logical components of an infrastructure that are currently or soon will be under configuration management. | A single module such as a server, database, or router or a more complex item, such as a complete system. For example, a web server, database, or infrastructure. |
| Asset | An item whose financial value is tracked. | Many assets are CIs and vice versa, but that's not always the case. Assets have a life cycle with financial considerations, for example Microsoft Office 365. |
| Operating model | An abstract and ideally visual representation (model) of how an organization delivers value to its customers or beneficiaries. | Typically represents the various elements of how an organization operates. It usually incorporates strategy positions such as the innovation model, degree of intelligent automation, industry alignment, provider delivery models, and the business expectations of IT. |