---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Problem Management use case

# Problem Management use case {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Problem Management use case

Problem Management in ServiceNow is designed to prevent problems and the incidents they cause, eliminate recurring incidents, and minimize the impact of incidents that cannot be avoided.
It enables you to capture and track information about affected configuration items (CIs) classified as assets, helping maintain records of updates, repairs, swaps, or retirements.
This systematic tracking allows you to monitor asset location, usage, and changes within your organization.
Show full answer Show less  
When a CI causes a problem, Problem Management utilizes the dependency view to identify other CIs impacted by the issue, allowing you to associate these affected CIs with the problem record and understand how dependent relationships influence the problem.

## Key Features

* **CMDB Integration with CSDM Framework:** Enhances Problem Management by providing insights into the impact on services and service offerings, enabling dynamic routing of problems and identification of impacted services.
* **Use of CSDM Data Elements:**
  * **Subscriptions:** Related lists on service offerings identify users, groups, departments, companies, or locations that have access and might be impacted by outages.
  * **Business Service Offerings:** Help determine business approvers based on approval groups and business criticality.
  * **Technology Management Offerings:** Provide technical approvers and assignment groups for problem resolution.
  * **Service Instances:** Distinguish between production and non-production environments (DEV, QA, UAT, etc.) to filter relevant contexts.
  * **Environment Attribute:** Recommended over the legacy usedfor attribute to specify environment details of service offerings.

## Key Outcomes

* The CSDM framework offers context on which CIs may be involved in a problem, aiding impact analysis and root cause determination.
* By populating the Configuration Item attribute on the Problem form, you can specify the affected CI or service.
* Optional use of Service and Service Offering attributes (requiring additional configuration) can help narrow down relevant configuration items.
* The Affected CI related list supports identifying other CIs contributing to the problem.  
The Problem Management use case is described in this section.

Problem Management is used to prevent problems and the occurrence of resulting
incidents. It also aims at eliminating recurring incidents and minimizing the impact of incidents
that cannot be prevented. With Problem Management, you can capture information on
affected configuration items (CIs), with type as asset, in a problem to keep a record of the
updated, repaired, swapped, or retired configuration items. By keeping track of the assets, you
can identify the location of the assets, their usage and when the assets were changed. Using Problem Management, you to monitor and manage the assets in your company using a systematic
approach.

If a configuration item (CI) has resulted in a problem, use the dependency view to identify
other configuration items (CIs) affected by the CI that caused the problem. You can then
associate affected configuration items (CIs) with a problem record to find out how the problem
affects other CIs with dependent relationships.

## Key features of the Problem Management use case {#pm-use-case-example__section_gs5_mqv_jvb}

The CMDB, when used by the CSDM framework, provides value to Problem Management in the following ways:

* Understand the impact of the problem on services and service offerings.
* Dynamically route problems.
* Identify one or more impacted services to address the problem.
{#pm-use-case-example__ul_zzc_rqv_jvb}  

<br />

The CSDM data elements used in Problem Management are:

1. Subscription: Related lists on service offerings that identify who has access to the offering and thus might be impacted in an outage. A problem can identify impact using the subscribed by tables. The related lists are as follows:
   * Service Subscriptions by Company \[service_subscribe_company\]
   * Service Subscriptions by Department \[service_subscribe_department\]
   * Service Subscriptions by Group \[service_subscribe_sys_user_grp\]
   * Service Subscriptions by Location \[service_subscribe_location\]
   * Service Subscriptions by User \[service_subscribe_sys_user\]
   {#pm-use-case-example__ul_dbw_rf4_hvb}
2. Business service offering might be used by problems to provide the business approver based on approval_group and business_criticality. A business service may have multiple offerings, each with a different criticality.
3. Technology management offerings might be used by problems to provide the technical approver approval_group and technical assignment group on the attribute assignment_group.
4. Service instance may be used to provide prod and non-prod (DEV, QA, UAT, and so on) environments. Non-prod environments may be filtered out if desired. The legacy used_for attribute maps to the environment attribute. You should use the environment attribute.  
   Note:  
   Some service offerings may identify the environment of the offering as well.
{#pm-use-case-example__ol_cbw_rf4_hvb}

## Results of the Problem Management use case {#pm-use-case-example__section_dsj_ldw_jvb}

The CSDM framework provides Problem Management context for
problems on what CIs may be involved.  
To determine the impact and root cause, compete the following steps:

1. Populate the Configuration Item attribute on the Problem form, configuration_item, with the CI item or service affected.
2. (Optional) Use the Service and Service Offering attributes on the Problem form to help narrow down the list of configuration items to choose from. This feature is not available with the base system and needs additional configuration.
3. (Optional) Use the Affected CI related list to identify the CIs that may have caused the problem.
{#pm-use-case-example__ol_opf_5fw_jvb}