Professional Documents
Culture Documents
Beginners Guide To Itil - Help or Hindrance?: Management and Infrastructure SIG Meeting
Beginners Guide To Itil - Help or Hindrance?: Management and Infrastructure SIG Meeting
Beginners Guide To Itil - Help or Hindrance?: Management and Infrastructure SIG Meeting
associates
Beginners Guide to
ITIL
- help or hindrance?
Can it help me?
What are the pitfalls?
Dennis Adams
4th October 2006
Introduction
• What is ITIL ?
• What do we mean by a “Process Approach” to the world as a
different way of looking at how we work together ?
BUSINESS SERVICE
IT SERVICE
DELIVERY
SERVICE
SUPPORT
Align IT services with the
needs of the Business
Improve the Quality of the
Service
Reduce the long-term costs
Think in terms of PROCESSES rather than SKILLS
Functional Organization
Process Approach
DEVELOPMENT PRODUCTION
Initiate
Initiate Document
Document the
the Configuration
Configuration
Infrastructures
Infrastructures Changes
Changes
Build
Build Identify
Identify root-cause
root-cause of Problems
Resolve
Resolve Customer
Customer Incidents
Test
Service
Service Desk
Desk // Help
Help Desk
Desk
Deploy
The ITIL Library of Process Books
ICT
ICT Infrastructure
Infrastructure Security
Security Management
Management
Management
Management
Application Management
Service Support
Planning
Planning to
to Implement
Implement
Service Management
“CORE
“CORE ITIL” Main
Main Volumes Supplementary
Supplementary Volumes
Key: ITIL” Volumes Volumes
The Core ITIL Books: IT Service Management
• Service Desk
Capacity Management
• Availability Management
• Incident Management
• IT ServiceManagement
Problem Continuity Management.
Resource
Utilisation
Business Strategy
Service Monitoring
Level Business Planning
Thresholds
Analysis
Tuning
Service
IT Strategy
Level Implementation
Exceptions
IT
Business
Resource
Plan
Utilisation
Exceptions
Ensuring we can meet our SLAs
Some Best Practices in the ITIL Library
• How to get the best benefit from a SERVICE DESK
– Single point of contact, Monitoring and escalation on behalf of customers.
• A systematic way of managing INCIDENTS:
– Log / Classify / Investigate / Diagnose / Resolution
• Being Pro-Active: PROBLEM MANAGEMENT
– Root Cause Analysis, Kepner & Tregoe Analysis, Ishikawa diagrams.
• Keeping track of IT Assets: CONFIGURATION MANAGEMENT
• Stopping dangerous changes: CHANGE & RELEASE MANAGEMENT
– Impact Analysis and Authorisation before Changes
• Being Customer-Focused: SERVICE LEVEL MANAGEMENT
• Bean-Counting: FINANCIAL MANAGEMENT
– Charge-back to reflect the cost to the Business.
• CAPACITY: Prediction instead of Panic
• AVAILABILITY
– Design for continual up-time
• DR and BCP: IT SERVICE CONTINUITY
– Risk Assessment and Planning
Why implement ITIL-based processes?
Service
ServiceDesk
Desk
Incident
Incident
Problem
Problem
Change
Change
Release
Release
Configuration
Configuration
Configuration
ConfigurationManagement
Management Database
Database (CMDB)
(CMDB)
…or MORE LIKE THIS ?
Service
ServiceDesk
Desk
Incident
Incident
Problem
Problem
Change
Change
Release
Release
Configuration
Configuration
Configuration
ConfigurationManagement
Management Database
Database(CMDB)
(CMDB)
.. Just Some parts of a theoretical CMDB
HARDWARE
Specification USERS INCIDENTS CHANGES
SOFTWARE
Location Applications Applications Applications
Licenses
Owner Contracts Hardware Users
Versions
Financials Incidents Resolutions Equipment
Software
APPLICATIONS
SLA
O/S Users RELEASES
Applications KNOWN
Equipment Hardware ERRORS Applications
Users
Contracts Incidents
INFRASTRUCT
URE
SOFTWARE PROBLEMS BCP
e.g. Oracle SERVICES AVAILABILITY Incidents DOCS
Applications STATISTICS Resolutions
NETWORK
Linkages
Dependancies DEFINITIVE SOFTWARE LIBRARY DEFINITIVE HARDWARE STORE
Case Study: Understanding Applications and Machines
More Questions ?
Dennis Adams
associates
Dennis Adams
http://www.dennisadams.net 4th October 2006