<<Project Name>>

Capacity Plan
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
345+(5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO ARRANTIES! E"PRESS OR
IMP#IE$! IN T%IS $OC&MENT'
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
345+(5+3(-
Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 6apacit" 0lan
Author
6reation 1ate
8ast 9pdated
345+(5+3(-
Table of Contents
$ummar"..........................................................................................................................
:b;ecti%es........................................................................................................................
9ser 0rofile......................................................................................................................
9sage $cenarios...............................................................................................................
$cenario (...................................................................................................................-
$cenario +...................................................................................................................-
Task ) 8oad <atri........................................................................................................-
=pected Growth............................................................................................................-
$"stem Reser%es.............................................................................................................>
6omponent 6apacit"......................................................................................................>
Bottlenecks.....................................................................................................................>
Growth and ,nter%ention $trateg"..................................................................................>
<onitoring and <etrics..................................................................................................*
Total $olution.............................................................................................................*
6omponent (..............................................................................................................*
6omponent +..............................................................................................................*
Thresholds for ,nter%ention............................................................................................*
,nter%ention 0lan............................................................................................................*
345+(5+3(- 3
%Intro(uction to t)e Template
$escription* The Capacit &lan outlines the strateg for '( assessing overall solution
and component performance and 2( using this information to develop the plan for
component ac)uisition, configuration, and upgrade.
+usti,ication* &lanning for capacit ensures that the business re)uirements are
efficientl and effectivel met b the infrastructure and application elements of the
solution. *t provides management with +'( a clear statement of the capacities of all the
resources and services re)uired to operate the solution, +2( an assessment of current
capacities, +,( a list of resources and services to be upgraded and to be ac)uired,
and +-( a pro.ection of resource and services capacities re)uired b the solution in
the future.
/Team Role Primary* Pro-ram Mana-ement is responsible for ensuring that the
plan is completed and has acceptable )ualit, as well as incorporating it into the
Master &ro.ect &lan and 0perations &lan1 $e.elopment provides content to the plan
in its responsibilit for ensuring that the solution will scale to meet capacit
re)uirements.
Team Role Secon(ary* All other roles are responsible for reviewing the plan2s
content to ensure it satisfies the re)uirements for their functional area.34
345+(5+3(-
Summary
%$escription* &rovide an overall summar of the contents of this document.
+usti,ication* #ome pro.ect participants ma need to know onl the highlights of the
plan, and summari5ing creates that user view. *t also enables the full reader to know
the essence of the document before the e6amine the details.4
<<Begin tet here!!
O/jecti.es
%$escription* The 0b.ectives section describes the ke ob.ectives of the capacit
management process. This information ma be derived from information about the
current operational environment as well as business re)uirements and functional
specifications.
+usti,ication* *dentifing the ob.ectives signals to the customer that Microsoft has
carefull considered the present operational situation, the business re)uirements,
and the solution and created an appropriate capacit management approach.4
<<Begin tet here!!
&ser Pro,ile
%$escription* "ser profiles describe users of a proposed solution and certain
important user characteristics such as fre)uenc of solution use and competence in
using a solution. "sers can be identified in groups +or classes(, usuall stated in
terms of their functional areas. *nformation technolog users include help desk,
database administration, etc. Business users include accounting, warehousing,
procurement, etc.
+usti,ication* 7escribing the users and their important characteristics assists in
forming the scenarios that are relevant to capacit.4
<<Begin tet here!!
&sa-e Scenarios
%$escription* "sage scenarios +also called use cases( define the se)uences of tasks
users perform and their interactions with solution functions to help them to perform
the tasks. This section should define the scenarios performed b the users in each
functional area.
+usti,ication* *dentifing and describing uage scenarios provides details that enable
the estimation of capacit loads and other factors.4
<<Begin tet here!!
345+(5+3(- +
Scenario 1
%$escription* The #cenario ' section describes a scenario and its characteristics
that provide input to estimating loads, growth, and impacts.4
<<Begin tet here!!
Scenario 2
%$escription* The #cenario 2 section describes a scenario and its characteristics
that provide input to estimating loads, growth, and impacts.4
<<Begin tet here!!
Tas0 1 #oa( Matri2
%$escription* The Task 8 9oad Matri6 illustrates the different kinds of loads that each
usage scenario places on the sstem. Measure for both server and client
configurations as appropriate to the capacit:planning scenario.4
$cenario
8oad
$cenario ( $cenario + $cenario . $cenario - $cenario >
'ard 1ri%e
RA<
Transactions
Bandwidth
609
0rinters (b"
t"pe)
$canners
,nterfacing
s"stems
$oftware
:ther
<<Begin tet here!!
E2pecte( 3ro4t)
%$escription* The ;6pected <rowth section describes the growth pattern for the
scenarios as a function of time.4
<<Begin tet here!!
Net4or0 Tra,,ic Impact
%$escription* The =etwork Traffic *mpact section estimates the impact of the solution
on network traffic including volume, tpe, and pattern +time of da, seasonal, etc(.4
<<Begin tet here!!
345+(5+3(- .
System Reser.es
%$escription* The #stem >eserves section defines the reserve capacit of all
sstem components re)uired b the solution including networking, servers, clients,
and applications.4
<<Begin tet here!!
Component Capacity
%$escription* The Component Capacit section identifies the solution2s components
+human, e)uipment, software, facilities, etc.( and defines the components2 current
capacities. ?ou ma record this information in a table that establishes the breakdown
of the solution2s various functional components and records relevant measurement
parameters for the sstem2s known capacit limits.4
?unction
Areas
6omponents 6onfiguration <easurement 6apacit" 6omments
1ata
transmission
links
8A7
@A7
0rotocols and
transport
:perating
s"stems
'ardware
Application
software
1omain5$ite
models
<<Begin tet here!!
5ottlenec0s
%$escription* The Bottlenecks section identifies and describes an areas of the
solution that ma represent functional bottlenecks.4
<<Begin tet here!!
3ro4t) an( Inter.ention Strate-y
%$escription* The growth and *ntervention #trateg section describes the manner in
which the solution is envisioned to add additional capacit such as@
*ncremental vs. replacement
345+(5+3(- -
Aori5ontal vs. vertical +e.g. more bo6es vs. bigger bo6es(
&arallel vs. hub spoke
=ew technolog4
<<Begin tet here!!
Monitorin- an( Metrics
%$escription* The Monitoring and Metrics section describes the monitoring methods,
techni)ues, and tools that will be used to evaluate solution and component
performance and provides metrics for planning intervention. This information should
be provided for each ma.or component at the solution level.4
Total Solution
<<Begin tet here!!
Component 1
<<Begin tet here!!
Component 2
<<Begin tet here!!
T)res)ol(s ,or Inter.ention
%$escription* The Thresholds for *ntervention section identifies, describes, and
)uantifies thresholds for triggering intervention b changing component
configuration.4
<<Begin tet here!!
Inter.ention Plan
%$escription* The *ntervention &lan section describes specific plans to follow in order
to preserve performance. This ma include details such as network traffic impact,
volume, tpe, pattern +time of da, seasonal, etc(, impact on users, sstem reserves,
networking, servers, clients, applications, monitoring, pro.ection of use, thresholds,
improvement strateg +e.g. incremental vs. replacement(, and prioriti5ation.4
<<Begin tet here!!
345+(5+3(- >