Incident Management Procedures

Card Set Information

Author:
josie9574
ID:
66806
Filename:
Incident Management Procedures
Updated:
2011-02-16 16:25:44
Tags:
IIM incident
Folders:

Description:
Terms, Acronyms, Procedures for Incident Management
Show Answers:

Home > Flashcards > Print Preview

The flashcards below were created by user josie9574 on FreezingBlue Flashcards. What would you like to do?


  1. ACD
    Automated Call Distributor
  2. CAB
    Change Advisory Board
  3. CC
    CompuCom
  4. CI
    Configuration Items
  5. CMDB
    Configuration Management Database
  6. IT
    Information Technology
  7. MIC
    Major Incident Coordination
  8. MIC
    Major Incident Coordination
  9. PE
    Onsite Program Executive
  10. QA
    Quality Assurance
  11. RCA
    Root Cause Analyses
  12. SD
    Service Desk
  13. SLA
    Service Level Agreement
  14. SLR
    Service Level Report
  15. SME
    Subject Matter Experts
  16. WI
    Work Instruction Document
  17. Incident
    An incident is an unplanned interruption to an IT Service or a reduction in the Quality of an IT Service. Failure of a Configuration Item that has not yet impacted Service is also an Incident. For example Failure of one disk from a mirror set.
  18. Incident Management
    Incident Management is the Process responsible for managing the Lifecycle of all Incidents. The primary Objective of Incident Management is to return the IT Service to Users as quickly as possible
  19. Known Error
    A known error is a problem that has a documented root cause and a workaround. Known errors are created and managed throughout their lifecycle by problem management. Known errors may also be identified by development or by hardware/software suppliers.
  20. Known Error Database
    This is a database containing all known error records. This database is created by problem management and used by incident and problem management
  21. Level 1 Support
    A level of service characterized by initial client contact at a Service Desk with an attempt to resolve an incident based on personal knowledge or information from a knowledgebase or documentation, collection of client and information in a tracking system.
  22. Level 2 Support
    A level of service characterized by the escalation of an incident to the next level for resolution by a more experienced associate or technician where Level 1 Support efforts have been completed. If Level 2 Support is unable to resolve the incident or procedures indicate escalation to Level 3 Support, the actions taken are documented and the incident escalated to Level 3 Support. If Level 2 Support resolves the incident, actions taken and resolution of the incident are documented in the tracking system.
  23. Level 3 Support
    A level of service characterized by the escalation of an incident for resolution by the most expert associate or technician where Level 2 Support efforts have failed to provide a resolution. The actions taken and resolution of the incident are documented in the tracking system.
  24. Major Incident
    The highest Category of Impact for an Incident. A Major Incident results in significant disruption to the Business.
  25. Problem
    A Problem is the cause of one or more Incidents. The cause is not usually known at the time a Problem Record is created, and the Problem Management Process is responsible for further investigation.
  26. Problem Management
    Problem Management is the Process responsible for managing the Lifecycle of all Problems. The primary Objectives of Problem Management are to prevent Incidents from happening, and to minimize the Impact of Incidents that cannot be prevented.
  27. Service Desk
    The Service Desk is the single Point of Contact between the Service Provider and the Users. A typical Service Desk manages Incidents and Service Requests, and also handles communication with the Users.
  28. Service Level Agreement
    An SLA is an Agreement between an IT Service Provider and a Customer. The SLA describes the IT Service, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers.
  29. Service Request (SR)
    A Service Request is a request from a User for information, or advice, or for a Standard Change or for Access to an IT Service. For example to reset a password, or to provide standard IT Services for a new User. Service Requests are usually handled by a Service Desk, and do not require an RFC to be submitted.
  30. Request for Change (RFC)
    Form, or screen, used to record details of a request for Change to any CI within an infrastructure or to procedures and items associated with the infrastructure

What would you like to do?

Home > Flashcards > Print Preview