Documente Academic
Documente Profesional
Documente Cultură
Abstract
ITIL Version 3 has recently been launched to much fanfare with its
structure a radical re-design from ITIL Version 2.
In this session the changes within ITIL Version 3 that impacts on the
Capacity Management process will be covered in detail.
Agenda
Introduction
ITIL V2 Structure
ITIL V2 Capacity Management
ITIL V2 and the Application Lifecycle Model
ITIL V3 Structure
ITIL V3 and the Application Lifecycle Model
ITIL V3 Capacity Management
Conclusion
ITIL V2 Structure
T
T Planning to Implement Service Management h
h e
e
Service Management T
B e
Service ICT
u The Business Support c
Infrastructure
s Perspective h
Service Management
i Delivery
n
Software
n Asset
Security o
Management
e Management l
s o
s Application Management g
y
Figure Crown Copyright 2001
Availability Problem
Management Management
Financial Configuration
Management Management
Service Capacity
Management (BCM) Iterative
Activities
Demand Storage of
Management Capacity
Resource Capacity Modelling Management
Management (BCM) Application Data
Sizing
Production of the
CDB
Capacity Plan
Tuning
Implementation Analysis
Monitoring
Resource
SLM
Resource utilisation
SLM exception
utilisation exception
thresholds Capacity reports
thresholds reports
Management
Database
(CDB)
Figure Crown Copyright 2001
Need to Review if Review Provide Review Provide Business-as-Demand Assess all Plan for de-
produce an require- design for design perform- capacity usual capacity software commissioning
approximate ments are perform- guidance ance assurance managementManagement
release requirements
cost of system to achievable ance to avoid testing assessment ensuring systems changes to including any
meet specified within problems, perform- Modelling
results for that transient can meet the transient capacity
performance budget costs and
scalability
ance anti-
patterns
any
problems
capacity
require-ments Capacity Plan
demands upon
them based on
application
to ensure
required for
migration to new
can be met current and future they will not platform
Iterative
work Application
affect
Application Sizing Activities Sizing
system
Performance
Monitoring
Business-
focussed
activities
Tools
Capacity
Supporting Database
activity
Missing Capacity
activities
Database
ITIL V3 Structure
Five separate core books to represent the service lifecycle:
Service Strategy
Service Design
Service Transition
Service Operation
Continual Service Improvement
Service Lifecycle
ITIL V3 Model
Service
Operation Service
Service
Strategy Design
Continual Service
Continual Service
Improvement
Improvement
ITIL
Service
Transition
Dont Panic!
The processes you are working with today will continue to be part of the refreshed ITIL. You
will notice, however, that the Service Support (SS) and Service Delivery (SD) processes will be
integrated into a service lifecycle. This will better reflect how service management is applied in
everyday practice and so implementation of them is likely to become easier.
Sounds OK so far
A significant portion of the current version of ITIL will be refined and included in ITIL V3. This
includes the parts that are still widely practised and usable in the IT service management
community.
There does lead to the concern that ITIL version 3 is very general, as ITIL
version 2 was.
End-of-life
Changes
Live
Provide capacity
Roll-out
Transition
Service
Capacitas 2002-2008
Testing
Review perform-ance
testing results for any
2E1 ITIL V3 Capacity Management: A practitioners review
problems
Coding
Provide design guidance
to avoid perform-ance anti-
Development
patterns
Review design for
Design
Service Design
perform-ance problems,
costs and scalability
UKCMG TEC 2008 20th May 2008
Require
Review if require-ments
are achievable within
budget
Feasibility
Need to produce an
Concept
approximate cost of system
to meet specified
performance
UKCMG TEC 2008 20th May 2008
2E1 ITIL V3 Capacity Management: A practitioners review
Service Strategy
Defines the overall strategy for providing IT services
Very high-level book written by Accenture consultant & an academic
from Carnegie Mellon
Interesting reading but leans heavily towards theory
Uses systems theory to define the business and its relationship to IT
Heavy focus on business capacity and its close coupling to IT capacity
Recognition of relation between Demand, Capacity and Cost (section
4.3.2.3)
Includes a recognition of the efficacy of Demand Modelling (Poorly
managed service demand is a source of cost and risk. see section
5.1.2.2) and Demand Management (section 5.5)
A cynic could regard it as a publication from the Heathrow Business
School, but it is worth reading, though not easy to follow
Service Design
The goal of the capacity management process has changed only slightly. It
was:
Service Design
Location of largest single section on Capacity Management (section
4.3, P79-97)
Unfortunately much of this material is unchanged from V2, including
the anecdotes and some diagrams
Introduces new acronyms:
Patterns of business activity (PBA)
Levels of Service (LOS)
Service Level Packages (SLPs)
Capacity Management Information System (CMIS)
Business, Service and Resource Capacity Management now becomes
Business, Service and Component Capacity Management
Seems very disjointed and haphazard with no cohesive structure
Not clear whether Production of Capacity Plan is here or Service
Operation, or both
Service Design
Demand pattern
Business Service
Pattern of Process Process Capacity
Business Management
Activity Plan
Service Belt
Delivery schedule
Demand
Management
Figure Crown Copyright 2007
Service Design
Outputs of Capacity Management:
Capacity Management Information System (CMIS)
The Capacity Plan
Service performance information and reports
Workload analysis and reports
Ad-hoc capacity and performance reports
Forecasts and predictive reports
Thresholds, alerts and events
Key Performance Indicators:
Accurate business forecasts
Knowledge of current and future technologies
Ability to demonstrate cost-effectiveness
Ability to plan and implement the appropriate IT capacity to match
business needs
Service Design
Finally a recognition that CMIS (formerly CDB) may not be one single
database
CMIS Contains:
Business data
Service data
Component utilisation data
Financial data (!)
Risks associated with Capacity Management include:
Lack of commitment from the business
Lack of information from business on future plans
Lack of commitment to resourcing and budget
Too much focus on technology (CCM) and not enough on
services (SCM) or the business (BCM)
Reports too bulky or technical and not appropriate
Service Transition
Capacity Management has an important relationship to change
management:
Capacity and Demand Management is a critical aspect of
Change Management.
Capacity Management has an important role in assessing
proposed changes not only individual changes but the total
impact of changes on service capacity.
Changes arising from Capacity Management, including those
set out in the capacity plan, will be initiated as RFCs through
the change process.
Recognition of relation between Stress and Load Testing and Capacity
Management
Lots of individual mentions of capacity, but no single section
Service Operation
Uses the following example of extremely proactive:
Anticipate capacity problems and spend money on preventing
these even when the scenario is unlikely to happen
Discusses Capacity Managements close interface to Incident
Management in several places
Section on Capacity Management (4.6.4: P.73-P.75) covers:
Capacity and performance monitoring
Handling capacity- or performance-related incidents
Capacity and performance trends
Storage of Capacity Management data
Demand Management
Workload Management
Modelling and applications sizing
Capacity Planning (now states that Service Operation has a
role in this)
Conclusions
ITIL Version 3 is a major change to the ITIL process set and will create
considerable challenges for those already adopting or using ITIL V2
Major work was undertaken to mentor, author and review the new material via
a formal structured procurement process
The new structure is an improvement, representing the service lifecycle better
than version 2 of ITIL
Version 2 content has been utilised by being integrated into the new structure
in most appropriate places
The tendering process has created lifecycle domains or towers that are not
being authored by any recognised capacity management expert
Capacity Management content is not substantially improved although some
new material is included it seems less coordinated (26 pages in total although
some is old and some sections replicated)
There is some good material but as it is not concise, concentrated or coherent it
may require the whole documentation set to be read just to understand
Capacity Management
Overall a missed opportunity
Capacitas 2002-2008 2E1-34