Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book

Incident Management

Incident Management refers to the process responsible for managing the life cycle of all Incidents, where an Incident is an unplanned interruption to an IT service or a reduction in the quality of an IT service. Failure of a CI (any component that needs to be managed to deliver an IT service, including IT services, hardware, software, buildings, people, and formal documentation such as process documentation and SLAs) that has not yet impacted service is also an Incident. The primary objective of Incident Management is to return the IT service to users as quickly as possible. For more information, see Chapter 10, which covers Incident Management in detail.

Incident Management is the process of managing deviations from normal service, restoring normal service operation quickly with minimum business disruption, and getting individual Users back up and running. Incident Management utilizes Configuration Management data to enable efficient and effective resolution of Incidents and to identify where Change releases have caused Incidents.

The goal of Incident Management is to restore normal service operation as quickly as possible with minimum disruption to the business and to ensure that the best achievable levels of availability and service are maintained.

Objectives of Incident Management include the following:

  • Restoring normal service as quickly as possible.
  • Minimizing the negative impact of Incidents on the business.
  • Ensuring that Incidents are processed consistently and that none are lost
  • Directing support resources where most required.
  • Providing information that allows support processes to be optimized, the number of Incidents to be reduced, and management planning to be carried out.

Table 3.5 presents Incident Management key terminology.

Table 3.5. Key Terminology in Incident Management




Any event that is not part of the standard operation of a service and that causes, or may cause, an interruption to, or a reduction in, the quality of that service.


An unknown error, the underlying cause of one or more Incidents.

Known Error

A Problem for which a root cause and permanent fix or workaround are identified but where the fix has not been implemented.


A temporary fix or technique that eliminates the customer's reliance on the faulty service component.


The likely effect on the business service, often equal to the extent of distortion of agreed or expected service levels.


The speed of resolution required, based on impact and the business needs of the customer.


This is the relative sequence of resolution required, based on impact and urgency, and other relevant factors such as resource availability, and calculated based on impact and urgency.


The mechanism that assists with timely resolution of an Incident. There are two types: functional escalation (transfer of an Incident between n-tier support departments) and hierarchical escalation (calling on management to assist in handling of an Incident).

Incident Management helps IT professionals, teams, and organizations achieve a critical outcome: minimizing the business disruption of Incidents by getting individual "hands on the keyboard"—users back up and running and restoring service as quickly as possible.

Because resources are to be allocated to the Incident Management process, the value of that process to the business has to be determined so that the resources allocated can be justified. To determine the value an organization places on Incident Management, consider the following:

  • What mechanisms are in place to reduce the business disruption of incidents and help ensure user satisfaction, especially when multiple Incidents arrive at the same time?
  • Who handles Incidents when they arrive, and what does good handling look like as measured by impact on user satisfaction? What are expected service levels and resolve times, and how do you ensure performance is satisfactory?
  • How do you ensure quick, consistent resolution of Incidents and keep Incidents from getting lost?
  • How can you organize around Incidents in a way that fosters the productivity of both users and IT analysts?
  • How do you minimize the impact of Incidents on service quality, either by preventing them in the first place or minimizing their impact when they do occur?
  • Who are the stakeholders of Incident Management? What is their stake?

The value of Incident Management should drive all further discussions and decisions on scope, priority, resources allocated to, and automation of the Incident Management process with Service Manager.

Reporting is a means of understanding and managing the performance of the Incident Management process. Although Service Manager includes out-of-the-box reporting functionality for Incident Management, you can look to MOF and ITIL for further guidance and what to report, when, and why (including the KPIs that are important to Incident Management). This includes first-call fix rate, the number of Incidents raised based on a Change, number of escalated Incidents, number of Incidents not meeting SLA targets, and Operations Manager alert to Incident ticket ratio.

Figure 3.1 shows the activities in the Incident Management process.

Figure 3.1

Figure 3.1 Incident Management process activities.

Incident Management roles include the following:

  • The incident manager, who owns the results of the Incident Management process
  • The service desk manager, who owns the results of the service desk function
  • IT managers and analysts in first, second, and third-tier support groups, including specialist support groups and external suppliers
  • The problem manager, for major Incident handling

Table 3.6 shows inputs and outputs of the Incident Management process.

Table 3.6. Inputs and Outputs in Incident Management



Incident details (from the service desk, networks, or computer operations)

Updated Incident records, including resolution/workarounds.

Configuration details from the CMDB

RFC for Incident resolution.

Response from Incident matching against Problems and Known Errors

Update, resolved, and closed Incidents. Communication to customers.

Resolution details

Management information (reports): service reports, incident statistics, audit reports.

Response or result of RFC to effect resolution for Incident(s)

Update, resolved, and closed Incidents. Communication to customers.

The following key questions must be answered to drive decisions when implementing the Incident Management process with Service Manager:

  • What is the value of Incident Management to the business?
  • Which Incidents are within scope for the process, and what target resolution times have you identified?
  • What values should be assigned to Incident record fields/drop-down (enumeration) list values?
  • What are your Incident escalation procedures, and how do they relate to the Escalated tick box and Assigned to field in the Incident form?
  • What Incident prioritization scheme will you use?
  • How will you use the Incident process in conjunction with Problem, Change, and Configuration Management? What are the expected interfaces?
  • What roles and responsibilities will be assigned for the Incident Management processes, and to whom?
  • Will auto-ticketing be used (for example, for events trapped by Configuration Manager's Desired Configuration Management [DCM] or Operations Manager alerts)?
  • What requirements do you have for automatic escalation or flexible routing of Incidents?
  • Will the Self-Service portal and email ticketing be used to reduce inbound call volume?
  • What requirement do you have for automated, rule-based Incident notification?
  • Which metrics will you track, and which reports will you produce as a basis for managing performance? Will custom reports be required?
  • Who needs to be informed and when throughout the life cycle of an Incident?
  • What role will announcements and knowledge articles play in the Incident Management process?
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020