<enter sponsor dept/bureau name>

<Enter project name>

Capacity Plan

<enter project code & name> Page 1 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

Document History
<The document history is a log of changes that are made to the document, who made the changes, and when.
For example, the initial creation of the document may contain the following: Version 0.1, Date 1/1/2004, Author
Charlie Brown, Status Initial creation. Subsequent updates to the document will be Version 0.2, 0.3, etc. The first
published version of the document should be Version 1.0.>

Version Date Author Status Section Revision Description

0.1 Initial Draft

1 First Published

<enter project code & name> Page 2 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

Table of Contents
1 PURPOSE OF THIS DOCUMENT ............................................................................... 4
2 GLOSSARY AND ACRONYMS ................................................................................... 5
3 INTRODUCTION .......................................................................................................... 6
4 SYSTEM INFORMATION............................................................................................. 7
5 NETWORK DIAGRAM ................................................................................................. 8
6 GENERAL CAPACITY PLAN DETAILS ...................................................................... 9
7 SERVER-SPECIFIC CAPACITY PLAN DETAILS ..................................................... 11

<enter project code & name> Page 3 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

1 Purpose of This Document

The intent of the Capacity Plan is to measure existing application requirements for technical
computing environment resources and services and to identify anticipated future system
resource and service requirements.

Capacity management planning will accomplish the following goals:

o Reduce the number of end-business processes suffering interruptions or outages
caused by inadequate IT capacity resources.
o Reduce the number of critical business processes not covered by a defined service
availability plan.
o Increase the percentage of critical IT resources with adequate capacity and
performance capability, taking account of peak loads.

The key performance indicators of successful capacity planning include:

o Reduced number of downtime incidents caused by insufficient capacity or processing
performance.
o Reduced time needed to resolve capacity problems.
o Decrease in the percentage of unplanned upgrades compared with the total number of
upgrades.
o Decrease in the frequency of capacity adjustments to meet changing demands.

<enter project code & name> Page 4 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

2 Glossary and Acronyms

Table: Terms and Acronyms Used in This Document
Acronym Definition
ARB Architecture Review Board
BIT Bureau of Information Technology
COTS Commercial Off The Shelf
OA Office of Administration
OA/OIT Standards Enterprise IT Standards
http://www.portal.state.pa.us/portal/server.pt?open=512&objID=416&
PageID=210791&mode=2
RAID Redundant Array of Inexpensive Disks
RFQ Request for Quote
SCD Shared Common Database

<enter project code & name> Page 5 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

3 Introduction
The capacity information contained within this document outlines the following:
o Current capacity requirements for a new or existing system, referred to as the capacity baseline;
o The quantity of excess capacity available based on existing infrastructure resources;
o Change in estimated capacity requirements based on usage trends, the anticipated
implementation of a new system or a new release/upgrade of an existing system.
This plan describes the following information so that appropriate system hardware/resources can be put
in place prior to when it will be required within the current 12-months. (For the purposes of quantifying
estimates of computing environment resource demands, each software program that will run
independently should be considered as a separate application)
1. Estimate increases or decreases in the number of end-users (to include county users,
application developers, technical support personnel, Agency end-users, etc.) that will be
accessing the Agency’s computing environment in using either existing applications or planned
new applications.
2. Estimate the increase or decrease in the percentage of CPU utilization, host, server or
workstation memory utilization, disk storage capacity consumption and or tape subsystem
usage that may occur as a result of changes being made to existing applications in production.
3. Estimate the increase in the percentage of CPU utilization, host, server or workstation memory
utilization, disk storage capacity consumption and or tape subsystem usage that may occur as a
result of new applications being put into production.
4. Estimate the increase or decrease in online transactions anticipated in response to changes
being made to existing applications in production, or for new applications to be placed into
production.
5. For new applications (batch or online) identify the time of day and frequency (daily, weekly,
quarterly, yearly) when these will be run, as well as the timing of any anticipated peak
application usage.
6. Description of anticipated changes to existing backup requirements.
7. Description of desired or required changes to existing availability requirements for existing
applications.

<enter project code & name> Page 6 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

4 System Information

System Name / ID:

Report Period: From: To:
System Background
Information:

<enter project code & name> Page 7 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

5 Network Diagram
<Please insert Network Diagram here.>

<enter project code & name> Page 8 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

6 General Capacity Plan Details

ID # Description Baseline Current Usage Existing Forecasted Change

(If this is a new application, Excess from Baseline
use this column to forecast Capacity (Within the next 12
initial requirements) months)
Date: __/__/__
1. Estimate the increase (+) or
decrease (-) in number of end
users (include county users,
application developers,
technical support personnel,
Agency end-users, etc.)
2. What percent of the users are
remote users?
3. How many remote sites must
this application be available
to? What are the locations of
the remote sites?
4. How many business partner
extranet sites are utilized?
5. What is the anticipated system
“burst” percentage? Describe
the “Forecast” as a multiple of
normal performance levels.
(i.e. maximum concurrent
users requiring maximum
bandwidth)
6. What is the estimated number
of on-line transactions per
day?
7. How many Internet-based
services will be provided with
this application? (i.e WWW
access, Web site, VPN, email,
etc.)
8. What additional throughput
capacity is required to handle
encryption and/or other
security requirements?
9. What, if any, ports must be
open for clients to access this
application across a firewall?
10. What types of transactions are
involved?
11. Identify the interfaces that will
potentially increase cross
platform or application traffic.
12. Will the system have batch
requirements and if so what
time impact is predicted?

<enter project code & name> Page 9 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

ID # Description Baseline Current Usage Existing Forecasted Change

(If this is a new application, Excess from Baseline
use this column to forecast Capacity (Within the next 12
initial requirements) months)
Date: __/__/__
13. Are there significant changes
anticipated related to the
nature of this application in
terms of how the application
will be used? Any other
performance improvements
such as query changes,
process flow changes, etc.
14. What middleware is involved?
15. What are the facility
requirements needed to
support the application?
(Safety and security capacity,
electrical capacity, room size,
environment, etc.)
16. How many servers are
currently supporting this
application? What is the
estimated excess capacity
remaining within the current
server configuration?
17. What personnel & skills are
required to support the
application?

<enter project code & name> Page 10 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

7 Server-Specific Capacity Plan Details

Server:
ID Description Baseline Current Usage Existing Forecasted Change
# (If this is a new application, Excess from Baseline
use this column to forecast Capacity (Within the next 12
initial requirements) months)
Date: __/__/__
1. What is the required amount of
bandwidth per client? Please
respond with Low, Medium, or
High.
2. What software is required to
support the application?
(Databases, compilers,
operating systems, utilities, etc.)
3. What are the tape recall
requirements in the event of a
disaster? Define in terms of
“HCIS”: H-highly critical, C-
Critical, I-important, S-suspend.
Please refer to ITB I.2.4.
Establishing Alternate
Processing Sites for
Commonwealth Agencies for
more information. Is there
sufficient infrastructure in place
to support the designation?
4. How much bandwidth do users
consume during peak usage?
(Describe the use of the system
including number of
transactions and file size)
5. How much bandwidth do users
consume during off-peak
usage? (Describe the use of the
system including number of
transactions and file size)
6. What is the required server
CPU utilization capacity?
(Forecast increase / decrease
as a +/- percentage %)
7. Estimate the required disk
space. (Estimate baseline in
units of gigabytes. Forecast
increase / decrease as a +/-
percentage %)
8. What are the memory
requirements for the
application?

<enter project code & name> Page 11 of 12 Printed: 12/19/2019

Capacity Plan v X.X
 <enter sponsor dept/bureau name>

ID Description Baseline Current Usage Existing Forecasted Change

# (If this is a new application, Excess from Baseline
use this column to forecast Capacity (Within the next 12
initial requirements) months)
Date: __/__/__
9. What are the data storage
requirements for the application
(within the transactional
system)? For example, is there
a data warehouse? Can data
be purged periodically?
10. Are there any fault tolerance
requirements? If so, please
describe these requirements.
(i.e. disk redundancy, fault-
tolerant server components,
fault tolerant communication
channels)
11. What are the system back-up
requirements?
12. Does the system comply with
the existing DOH backup
retention standards (6 months)?
13. Estimate the amount of data
required to be captured on tape
(In order to calculate tape
capacity required for system
backups.)

<enter project code & name> Page 12 of 12 Printed: 12/19/2019

Capacity Plan v X.X