Change and Problem Management Overview

SysAid Change Management and Problem Management help you turn complex, multi-step IT processes into standardized workflows. Change Management gives every change in your organization a predefined, repeatable process with built-in approvals. Problem Management helps you identify the root cause behind recurring incidents and resolve it in a structured way. And with SysAid Copilot, prebuilt AI agents work alongside your team to score change risk, detect problems hiding in your incidents, and keep both processes moving.

This article explains the core concepts, terms, and user roles behind both modules. When you're ready to start working with changes and problems, see Workflows.

Change Management

Change is a constant in every organization, and without a framework it quickly creates disorder. Change Management provides that framework: a standard procedure that every change of a given type follows, every time.

Consider what happens when your organization upgrades a production server. Before the work begins, someone must assess the risk and impact, schedule a maintenance window, notify affected users, and back up the data. The upgrade itself often involves several teams, the steps have a set order, and key decisions require approval. Who authorizes the downtime? Who signs off on the rollback plan? Change Management ensures the same procedure is followed for every server upgrade, and SysAid Change Management gives you the tools to build a template for this process, and for every other change your organization faces.

SysAid Change Management is modeled on the Change Management principles of the ITIL standard, so your change processes follow globally recognized IT best practices out of the box.

Problem Management

The ITIL standard distinguishes between two types of issues:

• Incidents are self-contained issues with a one-time fix, such as a jammed printer or a failed router that needs replacing.

• Problems are the underlying root cause of one or more incidents. They are more complex, tend to generate related incidents, and can take longer to diagnose and resolve.

A few examples of problems:

• The internet drops randomly throughout the day, generating separate incident reports about chat, browsers, and VoIP phones. All of these incidents share one root cause.

• A server periodically stops responding. Each affected user reports a different unresponsive application, but every one of those applications is hosted on the same server.

• An incident is resolved successfully but recurs the next day.

Because problems generate multiple incident reports and can take days to diagnose, ITIL defines a separate framework for handling them: related incidents are attached to the problem, the problem is analyzed, and a solution is developed through a standard problem-solving process. SysAid Problem Management is built around this framework.

AI-powered change and problem management

One of the biggest advantages of managing changes and problems in Spaces is SysAid Copilot. SysAid includes prebuilt AI agents that take on the analytical heavy lifting of Change and Problem Management, helping your team make faster, more consistent decisions.

Here's a sample of what they can do for your changes:

• Assisted Change Risk Scoring assesses a change against six key risk factors based on ITIL best practices and returns a clear risk score.

• Change Failure Risk Prediction predicts the probability that a change will fail, trigger an incident, or require a rollback, with contributing factors and recommendations.

• Change Risk Classifier classifies a change as Minor, Significant, or Major and applies the matching approval logic.

And for your problems:

• Detect Problem from Incidents analyzes open incidents, clusters similar issues, and recommends linking them to an existing problem or creating a new one.

• Create Problem with Related Incidents creates a new problem with an AI-generated title, description, and category, and automatically links the relevant incidents.

• Problem Analysis Assistant runs structured root cause analysis using Fishbone and 5 Whys methodologies and posts the findings to the record.

These are only some of the prebuilt AI agents that can support your change and problem processes. For the full list and how to activate them, see Prebuilt AI Agents Overview.

Key terms

User roles and permissions

Three Admin permissions relate to Change and Problem Management:

• Change Manager

• Create Changes/Problems

• View other Admins' action items

Permissions are configured per Admin under Settings > Administration > User Management > Service Pros (Admins). For more information, see Managing Agent and Admin Permissions.

These permissions create four types of participants:

Change Managers
Admins with the Change Manager permission build and oversee the full change and problem process. They can edit request, change, and problem templates, edit all action items (including those not assigned to them), create new changes and problems, and add ad hoc action items directly on a service record.

Admins who can create changes and problems
Admins with the Create Changes/Problems permission can create new changes and problems and edit the service record's fields outside the workflow. This permission does not include editing change or problem templates, and these Admins can only work on action items assigned to them. They are also typically responsible for closing changes and problems.

Regular Admins
Any Admin can participate in a change or problem through action items assigned to them. For example, a server upgrade template might include an action item for backing up the server's data; the Admin who completes it doesn't need any special permission. Regular Admins have read-only access to the rest of the service record, and can only view other Admins' action items if they have the View other Admins' action items permission.

End Users
End Users view and work on action items assigned to them from the Self-Service Portal, and can approve, deny, complete, or reopen a change directly from an email notification. When assigning an action item to an End User, you can allow them to download a PDF with the full change details. This is useful for End Users who are members of the CAB, such as a CFO.

Permissions summary

Next steps

Once you're ready to build your own process, see Setting Up Change and Problem Management, which walks you through the full setup, from planning and permissions to running your first change.

To see a complete change in action, read Example of a Change from Start to Finish.