Incident Management Lecture
Introduction
- Presenter: Saya
- Topic: Incident Management and Major Incident Management (MIM)
- Purpose: Informative video for friends and colleagues
What is ITIL?
- Acronym: Information Technology Infrastructure Library
- Definition: Detailed practices framework within IT Service Management (ITSM)
- Goal: Align IT services with business needs
ITIL Life Cycles
- Service Strategy
- Service Design
- Service Transition
- Service Operation (Includes Incident Management)
- Continual Service Improvement
Service Operation
- Processes:
- Event Management
- Incident Management
- Problem Management
- Access Management
- Identity Management
Incident Management
Objective
- Goal: Minimize adverse business impact due to unplanned IT service interruptions
Definition of Incident
- Incident: Unplanned interruption to an IT service that causes degradation of service
Problem Management
- Problem: Underlying cause of an incident
- Types: Proactive and Reactive
Change Management
- Change: Any addition, modification, or deletion of an IT Configuration Item (CI)
Incident Management Workflow
- **Reporting: **
- Users call Service Desk or automated Event Management tools
- Event types: Informative, Warning, Exceptions
- Service Desk Process:
- Identify if it's an incident or service request
- Log, categorize, and prioritize the ticket
- Categorization:
- Hardware or software & urgency
- Reference to Service Catalog
- Prioritization:
- Based on impact and urgency
- Priority levels: P1 (Critical), P2, P3, P4 (Low), P5 (Planning)
- Initial Diagnosis:
- Troubleshoot functional and hierarchical escalations
- Major Incident Management (MIM):
- Check for Disaster Recovery (DR)
- Notify stakeholders
- Root Cause Analysis (RCA)
- Incident Resolution and Closure:
- Restore service
- Validate user satisfaction
- Official closure and documentation
Major Incident Management (MIM) Process
Key Elements
- Disaster Recovery
- Stakeholder Notification
- Root Cause Analysis (RCA)
- Plan of Action: Always have Plan A and Plan B
Butterfly Diagram (Butterfly Effect)
- Steps:
- Understand the issue
- Assess the impact (Critical, High, Medium, Low)
- Identify teams required
- Initial Investigation
- Troubleshooting
- Make a Plan (A & B)
- Execute the plan
- Validate the fix
- Closure (Document and finalize)
- Escalation Matrix: Functional and Hierarchical
Conclusion
- Importance of Communication: Establish authority on the call, be clear
- Tips:
- Give clear timelines
- Note down key points and summarize
- Include Plan B in all planning stages
Summary
- Key Points: Incident Management, ITIL framework, MIM process, Butterfly Diagram
- Tips: Establish yourself early on the call, use direct names, clear and effective communication
Note: Refer to the video for visual representation of the processes and diagrams.