Process Apps Overview

The Service Manager solutions contain the following process apps:

Solution Process Apps
Serena Service Manager

Incident Management focuses on restoring normal service operations as quickly as possible to minimize the impact of incidents on business operations, thus ensuring that the best possible levels of service quality and availability are maintained.

Problem Management analyzes the root cause of incidents, prevents their recurrence, and limits the impact of problems that cannot be prevented. Problem management includes the Workarounds auxiliary table, where information about workarounds is stored.

Change Management helps ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to controlled IT infrastructure. This minimizes the number and impact of any related incidents upon service after changes are implemented.

Configuration Management System (CMS) oversees the life of the Configuration Items (CIs) by enabling the fundamental elements of identification, change management, status accounting, and audits. CMS components include the Configuration Items table, where all CIs and CI baselines are stored, the "BaselineWorkflows" orchestration where CI baselines are processed, and the Relationships auxiliary table where the relationships between CIs, RFCs, Problems, and Incidents are stored.

Serena Request Center

Service Request addresses requests from users by providing a request channel, gathering or supplying information, and fulfilling the request.

Knowledge Management manages knowledge base articles and announcements. It provides the ability to submit new knowledge base articles, specify whether articles are public or private, and monitor changes to existing articles.

Starter Pack Forms - IT provide pre-built forms for commonly used IT services, such as password change requests and software installations.

The following illustration shows the Service Request and Serena Service Manager process components and how they work together:

image

A typical integration flow follows:
  1. Configuration items (CIs) are entered and stored in the Configuration Management System.
  2. Users or IT Service Desk staff submit a request, which can lead to the creation of an incident.
  3. After the incident is assigned, a CI can be selected, which creates a link between the incident and the CI.
  4. If the incident needs to be escalated for root cause analysis, a problem can be submitted based on the incident.
  5. Problems can lead to entries in the Workarounds table that document workarounds for problems, and resolutions to known errors.
  6. A Request for Change (RFC), which is a formal proposal for a change to the IT infrastructure, may be required.
  7. An RFC may require an update to a CI and a new CI baseline.

The following topics describe the Service Manager process apps in detail.