Professional Documents
Culture Documents
Capacity Management Process Guide: September 2012
Capacity Management Process Guide: September 2012
Capacity Management Process Guide: September 2012
Process Guide
Version 1.0
September 2012
2012
This is a controlled document. Unauthorised access, copying and replication are prohibited.
This document must not be copied in whole or in parts by any means, without the written
authorisation of the Head, Enterprise Quality Management, WI.
II
DOCUMENT RELEASE NOTICE
This Capacity Management Process Guide, Version 1.0, is released for use in Sanmar
group, Wipro Infotech (WI) with effect from 7th Nov 2013.
Softcopy of the latest version of the document is available in the Process Document
Repository.
(Quality Manager)
III
[CAPACITY MANAGEMENT PROCESS GUIDE] Sanmar Group
Abbreviations
Table of Contents
ABBREVIATIONS................................................................................................................................. 2
Purpose
The document details the implementation and the execution of the Capacity Management process.
The guide is based on the best practices described in the Information Technology Infrastructure
Library (ITIL) framework.
Target Audience
The target audience for this document includes all Capacity Management process roles, Service Desk
Agents and Managers, other service management process owners mainly Incident Manager,
Availability Manager, Service Level Manager, Financial Manager, IT Service Continuity Manager,
Application Development and Maintenance staff involved in Capacity Management, and Customers’
IT representatives.
LIST OF FIGURES
LIST OF TABLES
When to upgrade
Ideally this is not too early, resulting in expensive over-capacity, nor too late, resulting in
bottle-necks, inconsistent performance and ultimately customer dissatisfaction and lost
business opportunities
What to upgrade
This could be an upgrade of existing infrastructure like more memory, new storage devices,
greater bandwidth or new technology implementation depending upon the requirement
How much to upgrade
The forecasting and planning elements of Capacity Management feed into budgetary
lifecycles, ensuring planned investment meeting the need
Policy
The Capacity policy is formulated based on the following three sub-processes of the Capacity
Management process
Business Capacity Management: This sub-process is responsible for ensuring that the
future business requirements for IT Services are considered, planned and implemented in a
timely fashion.
Service Capacity Management: This sub-process is responsible for understanding the
Performance and Capacity of IT Services. The Resources used by each IT Service and the
pattern of usage over time are collected, recorded, and analysed for use in the Capacity Plan.
Resource Capacity Management: This sub-process is responsible for ensuring that all
components within the IT Infrastructure are monitored and measured, and that the collected
data is recorded, analysed and reported.
Capacity Management policy is the guiding principles for creating, deploying and managing the
Capacity Management Process. Following are the policies on which this Capacity Management
Process is designed.
1. Installation / augmentation of any new capacity affecting service availability will be agreed
with various stakeholders through Change Management Process.
2. Any preventive maintenance activity to improve the performance or to alleviate capacity
problems can only be implemented against an approved change request as per standard
change control process.
3. The Capacity Manager should prepare / update the Capacity Plan once in a quarter and
share the same with necessary stakeholders.
4. Capacity plan will be used to track and progress the action items to ensure the agreed
capacity and performance requirements are met.
5. Capacity Management should adhere to the existing security policy and procedure.
6. Procurement of new capacity needs to be requested via contract or procurement processes
in place
7. Augmentation / Installation of any new capacity should adhere to the server build standards
in place.
8. The Capacity Management process should consider both proactive and reactive Capacity
Management, while emphasising on the proactive approach.
Entry Criteria
The following condition may trigger Capacity management process
Service breaches, capacity or performance events and alerts, including threshold events
Periodic revision of current capacity and performance and the review of forecasts, reports and
plans
New and changed services requiring additional capacity
Periodic trending and modelling
Review and revision of business and IT plans and strategies
Review and revision of designs and strategies
Review and revision of SLAs, OLAs, contracts or any other agreements
Wipro Infotech
REV 1.0 Capacity Management – Overview Service Management
Capacity Manager
Install Capacity
1.0 2.0
Identify Capacity Manage
Requirements Demand
4.0
Identify and
Implement
Capacity
Capacity Analyst
3.0
Other SM process
Monitor, Record
for Customer
and Report
Satisfaction
Capacity
Process Organisation
An indicative service delivery organisation structure showing position and composition of Capacity
Management team is illustrated in the following figure. In a large account involving multiple Domains,
a dedicated fulltime Capacity Manager is required. For medium and small accounts, such a role can
be combined with Domain lead.
Service Delivery
Owner
Capacity
Team Member Team Member Team Member
Analyst
Capacity Manager
Responsible for
Produces Capacity Plans in line with the organisation's business planning cycle, identifying
Capacity requirements early enough to take account of procurement lead times
Documents the need for any increase or reduction in hardware based on SLRs and cost
constraints
Produces regular management reports which include current usage of resources, trends and
forecasts
Sizes all proposed new systems to determine the computer and network resources required,
to determine hardware utilisation, performance service levels and cost implications
Assesses new technology and its relevance to the organisation in terms of performance and
cost
Carries out performance testing of new systems
Reports on performance against targets contained in SLAs
Recommends tuning of systems and makes recommendations to IT management on the
design and use of systems to help ensure optimum use of all hardware and operating system
software resources
Recommends resolutions to performance-related Incidents and Problems
Ensures requirements for reliability and Availability are taken into account in all Capacity
planning and sizing activity
Participates in the CAB for assessing and authorising Changes
Capacity Analyst
Responsible for
Collect the performance data and reports them to Management
Analyses the performance data and identifies the performance issues proactively
Helps in creating the capacity plans
Analyses the capacity requirements coming from multiple channels
RACI Chart
Legend R = Responsible for a particular action, but not necessarily the authority
:
A = Accountable for the action. There is only one person accountable for any
given action.
C = Consulted before the action (but not necessarily require approval)
N = Not Applicable
A
Identify future business demand and determine associated capacity (and performance)
requirements
Assess capacity (and performance) impact of future demand and impact of changes in
business functionality
Incorporate capacity (and performance) requirements in the process of designing, testing and
introducing new services
The steps involved in Identification of Capacity requirements are illustrated in the following figure.
Wipro Infotech
REV 1.0 Capacity Management – Identification of Capacity Requirements Service Management
Sanmar IT
New Capacity
requirement
Capacity Manager
Refer CMS
Update CMS
Service Management
System
Manage Demand
This activities under Demand Management includes
Wipro Infotech
<Process
REV 1.0 Name> Capacity Management – Manage Demand Service Management
Sanmar IT
2.3
Present Solution Solution
Agreement
Negotiation
Solution
Capacity Manager
2.4
Implement
Solution
Refer CMS
Service Management
System
Update CMS
Refer to the Appendix “Capacity requirements” for various focus areas that should to be considered
for collecting and analysing capacity utilization.
The steps involved in monitoring, recording and reporting of capacity are illustrated in the following
figure.
Wipro Infotech
REV 1.0 Capacity Management – Monitor, Record and Capacity Service Management
4.0
3.4
Management
Reporting
Capacity Analyst
4.0
Refer CMS
Service Management
Refer CMS
System
The steps involved in identification and implement Capacity are illustrated in the following figure.
Wipro Infotech
REV 1.0 Capacity Management – Identify and Implement Capacity Service Management
Capacity Manager
4.1
Perform Service
Outage Analysis 4.4 4.5
Install Additional Update Capacity
4.2 4.3 Capacity Plan
Identify Additional Perform
Capacity Preventive
requirements Maintenance
Capacity
Analyst
Refer CMS
Service Management
System
Update CMS
Capacity Database CMDB
Verification
Exit criteria
The process is considered complete once:
The Capacity Management Information System (CMIS) holds the information needed by all
sub-processes within Capacity Management.
The Capacity Plan used by all areas of the business and IT management and is acted on by
the IT service provider and senior management of the organization to plan the capacity of the
IT infrastructure
Service performance information and reports are used by many other processes.
Workload analysis and reports are used by IT Operations to assess and implement changes in
conjunction with Capacity Management to schedule or reschedule when service run.
Forecasts and predictive reports used by all areas to analyse, predict and forecast particular
business and IT scenarios and their potential solutions.
Adherence to Policies
Ensure the adherence to all process policies. For example:
All capacity related issues should be recorded in a management system.
Process Assessment
Following are the key points to assess the Capacity Management process in the organization
Assumptions made
Capacity Requirements
Platform1 Platform2 Platform3 Platform4
Cost
Hardware: Software: Tools: Others
Current
Total Current Average Time to
Server Used
File system Capacity Free Space Growth Rate Expire
Name Space
(GB) (GB) (GB/Month) (Weeks)
(GB)
Current
Total Current Average Time to
Server Used
Device ID Capacity Free Space Growth Rate Expire
Name Space
(GB) (GB) (GB/Month) (Weeks)
(GB)
Frequency of
Area Indicator Definition Formula
Measurement
Capacity Management
Response time =
To calculate SUM (CPU +
response time of Memory + Bus +
Response Time system I/O + Disk + LAN) Quarterly
Throughput = Sum
To calculate of all transaction /
throughput of Square root (CPU
Throughput system Power x Quetime) Quarterly
Performance =
Response time +
Throughput
To calculate Performance
performance of 'increase' trend in
Performance system quarterly report Quarterly
(Number incidents
with 'category'
To identify the specific to capacity
Incidents due to incidents due to issues/ total no of
capacity issues capacity issues incidents) * 100 Quarterly
(Number of
unplanned
To reduce purchases /
Unplanned unplanned Number of planned
panic buying purchase purchase )* 100
Number of systems
covered in previous
monthly report +
Systems To cover all critical Number of systems
covered under systems under covered in Current
monitoring monitoring monthly report Monthly
(Number of reports
Provides details on generated / Total
Production of timely production no of reports
capacity reports of capacity reports scheduled) * 100 Quarterly
Resource Provides details on (Number of Quarterly
forecast report timely production forecast reports
of capacity generated / Total
forecast reports no of forecast
reports scheduled)
* 100
(Number of
Provides details of systems covered
systems and for monitoring /
services under Total no of systems
Monitor system monitoring planned) * 100 Monthly
capacity plan
sample.docx