ITIL Capacity Management for the Newbie - GSE...

Commercial in Confidencewww.metron-athene.com

ITIL Capacity Management for the NewbieFor those new to system z

Charles Johnson – Principal Consultant


• ITIL Definition of Capacity Management• Capacity Management and ITIL activities• Difference between Capacity Management and

Performance Management?• How to be successful in Capacity Management• Talking with Business stakeholders • Creating a baseline and it’s effect on forecasting?• Different types of forecasts? • Examples of Capacity Management scenarios for

Mainframe

Agenda


Performance Management vs. Capacity Managementwww.metron-athene.com

• Performance Management： Alert problems

• Capacity Management： Prevent problems

Time

Response timeWorkload volumeResource usage

KPI, Threshold

Performance Management: Alert

Action： Proactive management Optimize before problem happened

＝＞ CapMan

Analyze： Provide root cause analysis and countermeasures＝＞ CapMan

Forecasting

Break Out

Steady

Incremental

？

Time


Capacity Managementwww.metron-athene.com

Business Index

Component Resource

L.O.B

Storage size

ResponseAvailability

# of UsersRevenue

CPU Usage

Forecasting required capacity according to Business plan

Monitor, Analyze Optimize, Upgrade, Increase

MaintainSLA

Business CapacityPredict future capacity requirements from the business demand

Service CapacityTo manage items in the input directly to service a component capacity management, improved management.

Component CapacityCapacity information of each component to monitor and to manage change in.

WorkloadManagement

ServiceManagement

ResourceManagement


Manage by KPI for YourRequirement • Prevent problem occurring (Proactive Management)

• Operate with optimized resources (Saving Cost)• Shorten MTTR if problem happened (Increase Availability)

Know Current Forecast the limit Understand whether the current

system is healthy or notResourceWorkload Well BalancedService

Know how much room remains

Find KPI to represent your system⇒Correlation

Set the threshold of the KPI⇒Trend Analysis & Modeling

Implement Capacity Management

Key Performance Indicatorswww.metron-athene.com


athene® ES/1 Forecasting

Commercial in Confidence


Quality of Service for Stakeholders

www.metron-athene.com


ForecastingQuality of Service to Stakeholder

Modeling Trend



athene® ES/1 Model Baseline – SYSACPU/CEC Modeling – Hardware & I/O



athene® ES/1 Model – Increase ProdOnl 5%CPU/CEC Modeling – Hardware & I/O



athene® ES/1 Model – Results CPU ChangeCPU/CEC Modeling – Hardware & I/O


Capacity Management - Activitieswww.metron-athene.com12

12/6/2016

Business

Service

Component

Capacity

Plan

Capacity Management Information System (CMIS)

Demand

ManagementModeling

Application

Sizing

Monitor

Analyze

Tune

Implement


“A model is a simplification of reality, built for a specific purpose”

Models


Modeling vs. Trending

• Trending– Easy to do – Scales well for multiple systems e.g. Windows , UNIX– Easy to alert on – No relationship to the performance (service) of a system or

application– Looks at just one metric

• Modeling– Relates service to utilization– View whole system interactions– ITIL recommends modeling– Moderate effort



Limitations occur when too much of too many types of data must be analysed and reported on repeatedly

Spreadsheet analysis

http://optimityanz.com/wp-content/uploads/2014/10/spreadsheet.png


Analytical Modeling Workflowwww.metron-athene.com

Modify Model and Predict Performance

Build and Calibrate the Model

Current Configuration

Measure and Compare with Predictions

Technical & Business InputsCurrent System

Describe the expected system

Technical & Business Inputs Expected System

Expected Configuration

Measure and Compare with Predictions

Actual Inputs

Actual Configuration


Modeling

• What questions will the model answer?• How accurate do the results need to be?• How long do you have to produce results?• What components need to be included?• What data is available and how can it be used?• What are the limitations and assumptions?

A model cannot answer all questions about a system

All modeling studies should have defined objectives and requirements


Modeling

A good modeling study requires a good understanding of the components involved

• Hardware• Software• Workloads

Business volumes- Planners, company reportsWorkload volumes- Users, logs, audit trailsService Levels- SLAs, users, monitors, logs, staffResource usage- System monitorsNew Systems- Development, users, other sites


Modeling

• Use the simplest modeling technique that will satisfy requirements

• Include more detail for components that are most likely to impact the system

• Make assumptions and abstractions where needed and justified• Remember that modeling tools are only as good as the analyst

using them

Understand: Requirements > System > Data


Modeling Steps

Build > Calibrate (debug) > Validate > Utilize > Document


Modeling Steps

Standard uses for systems models

• Determine system capacity• Find system bottlenecks• Examine system behavior

Analysis performed with the model is used to answer questions and examine system behavior


Modeling Results

• List requirements• Defined terms, measures, and statistics• Explain assumptions• Data sources• Simple charts• Conclusions

Present finding in an easy to understand fashion


Model Documentation

• Objective of the study• Inputs and outputs• Internal details of the model• Calibration and validation details• Relevant information learned• Reason for using model type and technique• Analysis details

Create additional content as needed


Modeling Failures

• Insufficient data• Model does not accurately represent system• Does not answer right questions• Not completed in timely manner• Not credible• Lack of management support

Why modeling studies fail


Business Index

Component Resource

L.O.B

Storage size

ResponseAvailability

# of UsersRevenue

CPU Usage

Forecasting required capacity according to Business plan

Monitor, Analyze Optimize, Upgrade, Increase

MaintainSLA

Business Capacity→Predict future capacity

requirements from the business demand

Service Capacity→To manage items in the input

directly to service a component capacity management, improved management.

Component Capacity→Capacity information of each

component to monitor and to manage change in.

WorkloadManagement

ServiceManagement

ResourceManagement

ITIL Capacity Management


Capacity Reporting – Technical vs. Services

• Gathering the necessary data

• Roadblocks encountered

• Weaving technical and services data effectively



Gathering the necessary data

• Business objectives

• Current performance data

• Data center forecasts

• Lines of Business



Roadblocks Encountered

• Business objectives not defined

• Performance data not consistent

• Lines of Business reluctance to provide information

• Lack of credibility in Capacity Planning process



Effective Service Levels – Managing KPIs

• What are KPIs?

• How to determine KPIs?

• Types of KPI reporting methods?



Key Performance Indicator

• Measurements, agreed to beforehand, that reflect the critical success factors of an organization

• Not necessarily one metric, can be a relationship

• Key Performance Indicators Must Be Quantifiable

• Reflected in a scorecard

Commercial in Confidence


Key Performance Indicators

Business

Services

Component

Demand Management

System Measurements - DATA

Aggregate to Transactions

Aggregate to Applications

KPIs, CSF, QOS


Demand Management – Providing knowledge

• How does Demand Management fit into Capacity Reporting?

• Data needs for effective Demand Management reporting



Goal

“Work with the Capacity process to ensure value is created by balancing the available capacity with the demands of the business”


What is the Story?

• What is happening in the current environment

• Concise information

• Display forecasts– Trends– Models

• Gather further information

www.metron-athene.com34


Types of Data required

• Technical data– Current – History

• Business metrics– Current– Forecast

• Key Performance Indicators

• Threshold levels



Different Capacity Plans for different audiences

• “C” level executives– Information concise– Elevator talk– Information to the point / summary and findings first– Do I need to spend more money?– Leave detail reports in pocket

• Business owners– What are the trends for my area?– How does it affect my area ?– What do I need to budget for?

• Technical– Show me the details– Show me the trends



Different presentation mediums

• Dashboards / Web portals– More suited for technical staff and business users– Different look for each area

• Word documents– More suited for “C” level executives– Upfront summary is critical– Historical document

• PowerPoint documents– Used for different types of presentations– Good for discussion groups– What is left out?



Display of different presentation types



Management OverviewApplications



Application Summary

Estimating

Accounting

Reporting

Mid-Tier

Banking

Arrival 2Arrival 1 Arrival 3 Final Comments

* Scaled horizontally

Breakpoint 15K users; Load balancing utilized across servers, Load balancing utilized across servers, incremental infrastructure

Load balancing utilized across servers, incremental infrastructure

Load balancing utilized across servers, incremental infrastructure

Breakpoint 7500 users, incremental infrastructure


Application Summary

Call Center

Arrival 2Arrival 1 Arrival 3 Final Comments

Infrastructure data patterns indicate spikes to be monitored and assessed in next model

I/O bottleneck; new architecture

I/O bottleneck; investigation in progress

I/0 bottleneck; investigation in progress

Warehouse

Data Mart

Sales History


Dashboard



Dashboard – Overview Scorecard Detailwww.metron-athene.com43


Modeling Scenario



Model – oracleq000 10% growth – server changewww.metron-athene.com45


Model – Linux server change & disk changewww.metron-athene.com46

ITIL Capacity Management for the Newbie - GSE...

Documents

Transcript of ITIL Capacity Management for the Newbie - GSE...