Use > Run > Problem Management > Learn more about problems > Problem Management input and output

Problem Management input and output

This table describes how problems are created and the possible output of the Problem Management process.

Input sources Output
  • Notification from a supplier or product manager that a problem exists. For example, a notification from a development team or a supplier of a known error in a database.

  • Potential security breaches in products that you deploy in the IT environment. For example, products from suppliers or security analysts.

  • Incident Management

    • Incidents classified as problem candidates.

    • Trend analysis and review of closed incidents that were resolved with a workaround.

    • Incident trend and summary reports.

    • Incidents with unknown causes or incidents that are likely to recur (from incident Management).

    • Incidents that reveal an underlying problem. For example, an application error or defect.

  • Change Management

    • RFC and change request status, approval and closure.

  • Configuration Management

    • Configuration details and service model relationships.

  • Event Management

    • Trend analysis and review of events. For example, event performance.

    • Error logs.

  • Security Management

    • Notification that potential security breaches require intervention.

  • Problems

  • Known errors

  • Workarounds

  • Problem reports
    (for example, status updates, trends, and performance)

Note Those who are affected, or those who are required to support the affected services, need to receive information about workarounds, permanent fixes, and problem progress.

Related topics