Capacity Plan

` <Project or Solution Name>

U.S. Department of Housing and Urban Development

<Month, Year>

Capacity Plan

Solution Information
Information
Solution Name Solution Acronym Project Cost Accounting System (PCAS) Identifier Document Owner Project Sponsor Version/Release Number <Solution Name> <Solution Acronym> <PCAS Identifier> <Owner Name> <Sponsor Name> <Version/Release Number>

Document History
<Provide information on how the development and distribution of the Capacity Plan is controlled and tracked. Use the table below to provide the release number, date, author, and a brief description of the reason for creating the revised version.> Release No. Date Author Revision Description

Note to the Author

The control gate criteria for each of the seven phases of the Department of Housing and Urban Developments (HUD) Project Planning Management (PPM) Life Cycle require the completion of various artifacts. Each IT project, working in conjunction with the Office of the Chief Information Officer (OCIO), will capture decisions around PPM tailoring in the Project Process Agreement (PPA), which documents the reasons for using, combining or skipping specific artifacts applicable to the project. This document is a template for a Capacity Plan that is to be completed during the Definition Phase, the second phase of the PPM Life Cycle. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project: Blue italicized text enclosed in angle brackets (<text>) provides instructions to the document author or indicates a field that should be replaced with information specific to a particular project. Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to a specific project. These are offered only as suggestions to assist in developing project documents; they are not mandatory formats.

Version 1.1 5/26/2011

Page i

Capacity Plan

Capacity Plan Authorization Memorandum

I have carefully assessed the Capacity Plan for <Project Name>. This document has been completed in accordance with the requirements of the HUD Project Planning and Management (PPM) Life Cycle. MANAGEMENT CERTIFICATION - Please check the appropriate statement. ______ The document is accepted.

______ The document is accepted pending the changes noted.

______ The document is not accepted.

We fully accept the content within this project artifact and associated tasks. ______________________________ NAME Business Project Manager ______________________________ NAME Project Sponsor _______________________________ NAME Technical Review Sub-Committee _______________________________ NAME Investment Review Sub-Committee (if applicable) _______________________________ NAME Customer Care Committee (if applicable) _______________________________ NAME Executive Investment Board (if applicable) _____________________ DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

_____________________ DATE

Version 1.1 5/26/2011

Page ii

Capacity Plan

Contents
1. 2. 3. Purpose ................................................................................................................................................ 1 Analysis of Capacity .............................................................................................................................. 2 Findings Summary ................................................................................................................................ 3

Appendix A: References ................................................................................................................................ 4 Appendix B: Key Terms ................................................................................................................................. 5

Version 1.1 5/26/2011

Page iii

Capacity Plan

1. Purpose
The Capacity Plan is an important part of infrastructure and deployment planning. A Capacity Plan supports the goal of optimum and cost effective provisioning of organizational resources and services by matching them to business demands. It helps identify and reduce inefficiencies associated with either under-utilized resources or unmet customer demand and to provide satisfactory service levels in a costefficient manner. The plan helps ensure that all infrastructure components are capable of performing all required functions, that components will perform as efficiently as possible and accommodate reasonable growth without being overly wasteful. Capacity requirements can vary greatly from times of peak demand to times of limited demand. As a result there may be drastic differences in the resources required to maintain normal operations during periods of peak demand. When planning for what levels of capacity will be supported, it is important to understand and weigh the costs, benefits, and risks of delivering, or not delivering, a certain level of capacity. The intended audience of the <Project Name> Capacity Plan is all project stakeholders including the Project Sponsor, Integrated Project Team (IPT), and the project team.

Version 1.1 5/26/2011

Page 1

Capacity Plan

2. Analysis of Capacity
<Define the capacity requirements by considering what work will be performed by the system. Consider the following: system performance requirements, expected volume of information to be processed and stored, the quantity of work, and the agreed upon measurement of system performance, testing considerations, and agreed upon service level requirements. Conduct an analysis of the current capacity and validate the capabilities of the existing resources (CPU, memory, hard drives, etc.). Describe plans for growth and/or upgrades and how they will be addressed and managed. Consider not only the requirements for additional hardware, software, building materials, and space but also where financial funding for these things will come from, additional resource allocation requirements, staffing, training, other expenditures, etc. Remember to consider future requirements. Expand upon this section by adding/removing additional scenarios if necessary.> Capacity Type
<Describe the capacity requirement analyzed. Enter details on current & future capacity requirements.>

Current Capacity Analysis

<Describe currently available capacity.>

Planned/Expected Growth and Recommendations

<Describe how future growth expectations have been identified and analyzed. Outline recommendations for managing and addressing this expected growth.>

Table 1 - Analysis of Capacity

Version 1.1 5/26/2011

Page 2

Capacity Plan

3. Findings Summary
<If applicable, describe historical capacity growth patterns. Explain how future expected capacity requirements have been identified and analyzed. Outline recommendations for managing and addressing expected growth. Insert a table/illustration, or provide a reference to where it is stored, that shows the different recommendations to address each of the capacity scenarios illustrated above. Describe how expected growth will be monitored and managed. Below is a basic example of a table that may be used to illustrate one approach for monitoring and managing future capacity. The approach used to illustrate these requirements may differ from project to project.> Area/Item Monitored Capacity Requirements % Increase Needed Per <time period>
<Enter projected increases over intervals of time.>

Capacity Threshold(s)

Threshold Response Strategy (Action to Be Take Upon Reaching Threshold)

<Enter response strategies to varying threshold limits. Threshold is defined as the level at which an event or change occurs.>

<Hard Drive Storage>

<Enter capacity requirements and measures.>

<Enter acceptable capacity threshold(s).>

<Number of Project Staff> <Ratio of Quality Assurance Staff to Development Staff> Table 2 - Findings Summary

Version 1.1 5/26/2011

Page 3

Capacity Plan

Appendix A: References
<Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.> Table 3 below summarizes the documents referenced in this document. Document Name
<Document Name and Version Number>

Description
<Document description>

Location
<URL to where document is located>

Table 3 - Appendix A: References

Version 1.1 5/26/2011

Page 4

Capacity Plan

Appendix B: Key Terms

Table 4 below provides definitions and explanations for terms and acronyms relevant to the content presented within this document. Term
<Insert Term>

Definition
<Provide definition of term and acronyms used in this document.>

Table 4 - Appendix B: Key Terms

Version 1.1 5/26/2011

Page 5