Problem Management

Problem Management process is supported by a SM workflow cartridge that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.

Of course the preconfigured process (the workflow cartridge) is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the Workflow Engine guide may be useful.

IMPORTANT NOTE: the configuration below is only one of the possible configuration to deal with the problem management process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration.

Operational model

The preconfigured process has the objective to facilitate and support the resolution of problems or the provision of workarounds. At the core of the process configuration is the following operational model.

Problem Management operational model

The requester, typically a member of the service desk or a technical team requires to open a problem. This may happen reactively (as a consequence of dealing with an incident) or proactively (in order to avoid future incidents). The problem is opened on a service and the service manager takes in charge it in order to coordinate the initial classification, prioritization and analysis. In this phase a problem owner is assigned who will coordinate the following steps of the process where workarounds and solutions for the problem.

Roles

For this process, the following organizational roles are defined:

Organizational role	Description	itmSUITE® role mapping
Requester	Opens problems on behalf of himself/herself or for a third party	This role is assigned to members of service desk (users belonging to group "Service Desk") and to members of the technical teams (see Technical team member role).
Problem owner	Assigns the problem for analysis and resolution Watches over and monitors the problem along all its life cycle ensuring target service levels are achieved Activates escalation/ routing/ requests Manages all the communications with the requester Checks the implemented resolution and sets the problem to resolved Closes the problem	Role assigned by the service manager to himself/herself or to a technical team member.
Technical team member	He/she receives the notification on the assignment of an activity concerning a problem (e.g. conducting the analysis and finding a resolution or workaround for it) Carries out the assigned tasks Notices when completed or unable to complete	There are several technical teams predefined for different domains. The following table shows which users are members of each team. Domain Solution group Member users Application management "Application Management" "AppManager" "AppSpecialist" Personal devices management "Personal Management" "PersonalManager" "PersonalSpecialist" Network management "Network Management" "NetManager" "NetSpecialist" Server management "Server Management" "ServerManager" "ServerSpecialist"
Technical team manager	Receives the notification about the assignment of the problem to his/her team in order to find a resolution or workaround for it Assign the member of his/her team who should work on it (this can be done by setting the ticket worker or creating and assigning ticket activities) Watches over and monitors the work of his/her team	There are several technical teams predefined for different domains. The following table shows which users are set as solution group manager for each domain. Domain Solution group Solution group manager Application management "Application Management" User "AppManager". Personal devices management "Personal Management" User "Personal Manager". Network management "Network Management" User "NetManager". Server management "Server Management" User "ServerManager".
Service manager	Takes in charge and assigns the problem owner Monitors how the problems are evolving for the service(s) he/she is responsible for	This role is mapped on a system resource with user of user type "Project/Service Manager". There are different service managers configured for specific services. See Services section in this page for further information.

In some organizational contexts, the role of the service manager may be played by the manager of a dedicated problem management team, mapped on a specific group and the role of problem owner by a member of this team.

Process

As for all workflows, new problems can be created by using the self service portal, accessible by means of Self Service menu.

The following requests which trigger a new instance of the problem management process are configured and available to all organizational roles in the self service portal:

Self service topic	Self service category	Self service request	Authorized roles
"Applications"	"itmCLOUD"	"Problem" (open a problem)	Requesters and service managers.
"Personal Devices"	"Personal Computers"	"Problem" (open a problem)	Requesters and service managers.
"Personal Devices"	"Peripherals"	"Problem" (open a problem)	Requesters and service managers.
"Personal Devices"	"Telephony"	"Problem" (open a problem)	Requesters and service managers.
"Network"	"Networking Management"	"Problem" (open a problem)	Requesters and service managers.
"Technical Services"	"Server Management"	"Problem" (open a problem)	Requesters and service managers.

A problem may also be automatically opened during the execution of an incident management process by the resources dealing with it.

A workflow is configured to support the problem management process. The workflow is characterized by workflow statuses and workflow transitions. The figure below illustrates the process.

Problem management process.

The table below explains the meaning of each workflow status.

Workflow status	Description
"Default"	A preliminary status which is displayed when a problem is created.
"Opened"	The problem has been recorded and activities to resolve it started.
"Requested"	The problem is confirmed and the service manager may start to analyse it and assigns the problem owner.
"Problem Assigned"	The problem is assigned a problem owner and the analysis activities plan is defined.
"Problem in Analysis"	The problem owner coordinates the analysis. The root cause is investigated and found. Workarounds may be found too. Finally a plan to implement the resolution is prepared.
"Problem in Resolution"	The plan to implement the problem resolution is executed. A change may be opened at this stage.
"Cancelled"	The problem is not confirmed and, therefore, cancelled.
"Resolved"	The problem is resolved, meaning that the plan to implement a resolution is positively concluded.
"Suspended"	The problem execution is temporarily suspended. In this status service levels calculation are suspended too.
"Major Problem Review"	In case of major problem, in this status a review is performed.
"Closed"	The problem closure has been confirmed. No other changes are possible.

And finally the table below explains the roles authorized to execute the workflow transitions.

Source status	Destination status	Authorized executors	Comment
"Default"	"Opened"	Requesters, technical team members, service managers.	See the self service portal configuration previously described.
"Opened"	"Requested"	Requester, service manager.
"Opened"	"Cancelled"	Requester, service manager.
"Requested"	"Opened"	Requester, service manager..
"Requested"	"Cancelled"	Requester, service manager.
"Requested"	"Suspended"	Service manager.
"Suspended"	"Requested"	Service manager.
"Problem Assigned"	"Problem in Analysis"	Problem owner, service manager.
"Problem Assigned"	"Suspended"	Problem owner, service manager.
"Suspended"	"Problem Assigned"	Problem owner, service manager.
"Problem Assigned"	"Cancelled"	Problem owner, service manager.
"Problem in Analysis"	"Suspended"	Problem owner, service manager.
"Suspended"	"Problem in Analysis"	Problem owner, service manager.
"Problem in Analysis"	"Problem in Resolution"	Problem owner, service manager.
"Problem in Resolution"	"Problem in Analysis"	Problem owner, service manager.
"Problem in Analysis"	"Cancelled"	Problem owner, service manager.
"Problem in Resolution"	"Cancelled"	Problem owner, service manager.
"Problem in Resolution"	"Resolved"	Problem owner, service manager.
"Problem in Resolution"	"Suspended"	Problem owner, service manager.
"Resolved"	"Major Problem Review"	Problem owner, service manager.	This workflow transition is available only if the field Major Problem is set to "Yes".
"Requested"	"Problem Assigned"	Service manager.
"Major Problem Review"	"Closed"	Problem owner, service manager.	Any related incident is set to closed (workflow status "Resolved" in incident management) and any related known error is unpublished (workflow status "Known Error Unpublished" in known error management).
"Suspended"	"Problem in Resolution"	Problem owner, service manager.
"Resolved"	"Closed"	Requester, problem owner, service manager.	Any related incident is set to closed (workflow status "Resolved" in incident management) and any related known error is unpublished (workflow status"Known Error Unpublished" in known error management).

Related processes

Several other IT Service Management processes are related to the problem management one. Some basic interfaces are provided. The tab Related Items of the problem and, in particular, the sub tab Tickets of it allows to view all the existing between the problem and other processes (managed through tickets).

Incident management

It is possible to create a problem from the incident management process or to relate an existing problem to an incident and vice versa.

Change management

It is possible to create a new change, managed via the change management process. The GENERATE CHANGE command allows to instantiate a new change by copying some problem information and by creating a relationship between the problem and the generated change.

Asset management and configuration management

It is possible to relate configuration items to a problem by using the tab Related Items and, in particular, the sub tab Configuration Items. The ASM and/or CMS modules features are made available here (e.g. view of configuration item details, configuration exploration or impact analysis).

Known error management

It is possible to create a new known error, managed via the known error management process. The GENERATE KE command allows to instantiate a new known error by copying some problem information and by creating a relationship between the problem and the generated knonw error.

Release and deployment management

A release may include the solution of one or more problems even if this may happen rarely (more frequently a release includes changes generated to resolve problems and related to them, The relationship between a release and and problems is more frequently created working from the release. In any case, this can be done from the tickets tab Related Items and, in particular, the sub tab Configuration Items by using the ADD EXISTING or SELF SERVICE commands.

Services

Different services are configured for different problem domain areas as illustrated in the following table.

Incidents domain areas	Service	Service manager
Application management	Only one application, and the related service ("itmCLOUD") is configured.	The user "servicemanager" is configured as service manager.
Personal devices management	"Personal Device Management".	The user "personalmanager" is configured as service manager.
Network management	"Network Management"	The user "netmanager" is configured as service manager.
Server management	"Server Management"	The user "servermanager" is configured as service manager.

Management information

Many management information are available as fields in the problem management configured form. The following table illustrates the intended use of key information and its behaviour. NOTE: information are available (visible) and can be modified according to a specific configuration which is meant to be suitable for the organizational roles involved in the process.

Information group or tab	Field	Purpose	Comments
General Information	Ticket Op Status	To show the operational status of the problem, see workflow statuses in Process section of this page.	Status changes are performed by means of the Save&Next command.
General Information	Request Name	To show the SRCS request invoked
General Information	Short Description	To provide a short description of the problem.	Always visible.
General Information	Requester	To identify the name of the requester (who has requested the problem).	A list is presented, influenced by.... TBC
General Information	Creation Date	To show the date and time the problem was created.	This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information	Edit Date	To show the date and time the problem was last updated.	This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information	Creation User	To show the user who created the problem.	This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information	Edit User	To show the user who updated the problem last.	This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
Ticket Classification	Project/Service	To show the service (or project) to which the problem is related.	This is automatically set at open time and can't be modified.
Ticket Classification	Ticket Type	To show the type of workflow executed.	This is automatically set at open time and can't be modified.
Ticket Classification	Problem type	To enter the information whether the problem is reactive (opened as a consequence of one or more incidents) or proactive (opened to avoid potential incidents).
Ticket Classification	Problem Classification	To set the problem classification information (domain).This is used for statistic reasons.	The classification information initially provided can be changed.
Ticket Classification	Major Problem	To show if the problem has to be considered major or not.	This impacts the need of a final review (if major) or not.
Prioritisation & Planning	Required Solution Date	To provide the date of solution requested by the Requester.	This is normally set for reactive problems, according to the related incidents priorities and status.
Prioritisation & Planning	User Priority	To provide the priority given to the problem by the Requester.	A four level scale is set but it can be changed.
Prioritisation & Planning	Ticket Urgency	To define the urgency for the resolution.	A three level scale is set but it can be changed.
Prioritisation & Planning	Ticket Impact	To define the impact on the business of the problem.	A four level scale is set but it can be changed.
Prioritisation & Planning	Ticket Priority	To view the calculated priority of the problem.	The priority is automatically set based on Ticket Urgency and Ticket Impact. The driving matrix can be configured.
Prioritisation & Planning	Forecast Solution Date	To set the forecasted resolution date and time for the problem.
Ownership and Groups	Master SG	To define the supervising team.	This is set by the service manager and mandatory from the Ticket Op Status "Problem Assigned". The team may change during the problem life cycle.
Ownership and Groups	Solution Group	To define the team to which the problem is assigned for analysis and/or resolution.	This is set by the service manager and mandatory from the Ticket Op Status "Problem Assigned". The team may change during the problem life cycle.
Ownership and Groups	Owner	To define who is the problem owner who should monitor the lifecycle of the problem.	This is set by the service manager and mandatory from the Ticket Op Status "Problem Assigned". He/she can be changed by the service manager and the Owner him/herseilf.
Ownership and Groups	Ticket Worker	To set the resource who shall work in order to analyse and/or resolve the problem.	If the analysis is performed by the problem owner, the Ticket Worker is normally not set. He/she is a member of the team defined in the Solution Group field.However setting him/her is not mandatory. Alternatively, it is possible to assign specific tasks to resources by using the Ticket Activities tab.
Ticket Details	Description	To provide a more detailed description of the problem.	An auto tracking field is used enabling to view the user who has updated.
Ticket Details	Analysis	To provide the analysis of the cause(s) of the problem.	This field is only visible to service desk and technical team members. An auto tracking field is used enabling to view the user who has updated.
Ticket Details	Solution	To describe the solution applicable to the problem.	This field is only visible to service desk and technical team members. An auto tracking field is used enabling to view the user who has updated.
Ticket Details	Comments	To provide comments helpful for the analysis and/or resolution of the problem or for future memory (e.g. continual improvement)..	This field is only visible to service desk and technical team members. An auto tracking field is used enabling to view the user who has updated.
Ticket Details	Comments for Requester	To provide comments to the requester of the problem.	An auto tracking field is used enabling to view the user who has updated. This field is not the only way to interact with the requester. To this aim messages, manage via the Messages tab, can be very useful

Fields can be mandatory to save the incident in some workflow statuses. These fields are highlighted with a red asterisk.

Views

The following views are made available in the Tickets area of the home page:

View	Content	Requester	Problem owner	Technical team	Service manager
Problems resolved	Problems in statuses "Resolved", "Major Problem Review".	X
Problems requested	Problems in status "Requested".				X
Problems owned	Problems in status "Problem Assigned", "Problem in Analysis", "Problem in Resolution", "Resolved" and "Major Problem Review" where Owner is the logged resource.		X
Problems routed to my team	Problems in status "Problem Assigned", "Problem in Analysis", "Problem in Resolution" where Solution Group is the solution group to which the logged resource belongs to.			X
Problems assigned to me	Problems in status "Problem Assigned", "Problem in Analysis", "Problem in Resolution" where the Ticket Worker is the logged resource.			X
Problems suspended	Problems in status "Suspended".		X		X
Major problems to review	Problems in status "Major Problem Review".		X		X

Additionally, the following views are made available in the Problem menu for all the organizational roles:

View	Content
Problems active	Problems in status "Requested", "Problem Assigned", "Problem in Analysis", "Problem in Resolution", "Resolved" and "Major Problem Review".
Problems suspended	Problems in status "Suspended
Problems closed	Problems in status "Closed"
Problems cancelled	Problems in status "Cancelled"

Notifications

The following notifications are configured:

Trigger	Recipients	Purpose
An incident is opened	Solution group members of "Service Desk"	Alert that there is an incident to manage.
An incident is taken in charge	The incident creator	Alert that someone has started to work on the incident.
An incident is resolved	The incident creator	Alert that the incident is resolved.
A solution group is assigned or changed for the incident	Solution group manager	Alert that there is a resource to allocate to manage the incident.
A ticket worker is assigned	The assigned ticket worker	Alert that there is work to be done.
An incident is suspended	The incident creator	Alert that the incident is suspended.
An incident is closed	Solution group members of "Service Desk"	Alert that the incident has been closed.
An incident is cancelled	The incident creator	Alert that the incident has been cancelled.

Reporting

A set of standard reports are made available for the incident management process. It is not required to have the REP module to use them, however the module is required if new or changed reports are needed. The available reports are placed under Incident/Reporting menu.

The following table lists the reports available by default and their visibility:

Report name	Content	Access
Incident per priority - trend	An histogram showing the incident volumes per priority monthly trend.	Service desk and technical team members.
Incident per priority - volume	A pie containing the split of incidents per priority.	Service desk and technical team members.
Incident per service - trend	An histogram showing the incident volumes per service monthly trend.	Service desk and technical team members.
Incident per service - volume	A pie containing the split of incidents per service.	Service desk and technical team members.
Incident per service/priority - volume	An histogram showing the incidents volume per service and priority.	Service desk and technical team members.
Incident - in charge time	A pie showing the percentage of incidents respecting the target defined for the take "In charge time"* objective (the time elapsed from the "Opened" to the "In Charge" workflow status.	Service desk and technical team members.
Incident per priority - resolution time	An histogram showing, per priority, the percentage of incidents respecting the target defined for the "Resolution time"* objective (the time elapsed from the "In Charge" to the "Resolved" workflow status.	Service desk and technical team members.

* "In charge time" and "Resolution time" objectives are defined within the OCE module.

A basic form of reporting is also provided by views. Views basically allow to list incidents and their attributes but may also be configured to calculates sums, averages on some of them. The available views are illustrated in the dedicated section of this page.

Examples of use

In this section some examples of use of the configured incident management process are given.

If you get lost, any time use the EXPLORE WORKFLOW command of the incident management form. This enables to view the status of the workflow as shown in the figure below. By clicking on a relationship between workflow statuses, roles and users enabled to perform it are presented.

Explore Workflow window

NOTE: the EXPLORE WORKFLOW command is available only if the ticket is first saved.

For more information on how to use any workflows, including incident management, please refer to the workflow execution guide.

Create a new incident as a final user

1. Login as "finaluser" user
2. Activate the Self Service menu
3. Choose a self service topic, self service category and finally "Incident" as self service request (this determines the creation of a new incident)
4. Fill the incident form, at least with mandatory form and save with the SAVE command

You have now saved the incident, take note of the ticket number for further reference or use.

Take in charge an incident as service desk member

1. Login as "sdspecialist" (therefore a service desk member)
2. Open the the desired incident; you can do it quickly either by
   • Access the views in the Tickets window of the home page and pick an incident among those listed in workflow status "Opened"
   • Access the Incident/Incident active menu and pick an incident in workflow status "Opened" among those listed
   • Insert the reference number of an incident in workflow status "Opened" in Quick Search, after selecting the search context "Ticket"
3. Take in charge the incident by
   • Pressing the SAVE & NEXT command
   • Choose the "1. Take In Charge" workflow transition
   • Fill the incident form and save with the SAVE command

The incident is now in workflow status "In Charge".

Resolve an incident as service desk member

1. Login as "sdspecialist" (therefore a service desk member)
2. Open the the desired incident; you can do it quickly either by
   • Access the views in the Tickets window of the home page and pick an incident among those listed in workflow status "In Charge"
   • Access the Incident/Incident active menu and pick an incident in workflow status "In Charge" among those listed
   • Insert the reference number of an incident in workflow status"In Charge" in Quick Search, after selecting the search context "Ticket"
3. Update incident information (at least fill mandatory fields for resolution, Analysis and Solution)
4. Set the incident in "Resolved" workflow status
   • Press the SAVE & NEXT command
   • Choose the "1. Resolve" workflow transition and press the APPLY & SAVE command

The incident is now in workflow status"Resolved".

Route an incident to a technical team

1. Login as "sdspecialist" (therefore as a service desk member)
2. Open the the desired incident; you can do it quickly either by
   • Access the views in the Tickets window of the home page and pick an incident among those listed in workflow status"In Charge"
   • Access the Incident/Incident active menu and pick an incident among those listed in workflow status "In Charge"
   • Insert the reference number of an incident in workflow status "In Charge" in Quick Search, after selecting the search context "Ticket"
3. Update Solution Group field with the technical team you want to assign
4. Save with the SAVE command

At step 3, you might also want to set a specific member among those of the select technical team by defining the Ticket Worker.

Take in charge an incident as a technical team member

1. Login as a technical team member (for available logins, refer to the Role section of this page)
2. Open the the desired incident; you can do it quickly either by
   • Access the views in the Tickets window of the home page and pick an incident among those listed in workflow status "In Charge"
   • Access the Incident/Incident active menu and pick an incident among those listed in workflow status "In Charge"
   • Insert the reference number of an incident in workflow status "In charge" in Quick Search, after selecting the search context "Ticket"
3. Press SET ME AS TICKET WORKER command
4. Press SAVE command

Close an incident as a final user

1. Login as "finaluser"
2. Open the the desired incident; you can do it quickly either by
   • Access the "Incident resolved" view in the Tickets window of the home page and pick an incident among those listed
   • Insert the reference number of an incident in workflow status"Resolved" in Quick Search, after selecting the search context "Ticket"
3. Close the incident by
   • Pressing the SAVE & NEXT command
   • Choose the "1. Close" workflow transition

The incident is now in workflow status "Closed".