Post on 10-May-2018
<Project Name> Capacity Plan
Capacity Plan Bureau of Information Systems
<Project Name>
document.docx Page 1 of 18
<Project Name> Capacity Plan
REVISION HISTORYDate Version Description Author
<dd/mm/yy> <x.x> <details> <name>
document.docx Page 2 of 18
<Project Name> Capacity Plan
TABLE OF CONTENTS
1. Release Specific Questions 4
2. Application User Base 5
3. Transaction Volume (Production Only) 6
4. Business Intelligence Metrics (Production Only) 7
5. System Resources (All Environments) 8
6. Data Warehouse Databases (All Environments) 9
7. Operational Data Store (All Environments) 10
8. File Storage (All Environments) 11
9. Network Bandwidth (Production Only) 16
10. DGS Print Service (Production Only) 17
11. Enterprise Service Usage (Production Only) 18
document.docx Page 3 of 18
<Project Name> Capacity Plan
1. RELEASE SPECIFIC QUESTIONS
The capacity reporting should be based on a review of the Critical Business Process (CBP); previously referred to as a Unit of Work. This review should focus on key business drivers, workload, and workload characterization (transactions, batch jobs). The capacity report should be based on changes or additions to this base as well as any anticipated environmental (i.e. new software products). This requirement applies equally to transactional application, business intelligence, enterprise service, and COTS products. Use the following format for the Capacity Report:
Release-Specific Questions
Area Description Comments
FunctionalityAre there any significant changes to the nature of this application in terms of how it will be used (e.g. workflow changes, new or modified queries, etc.)?
Batch ProcessWill there be changes to the application’s batch requirements? If so, what is the estimated impact to the existing batch process?
Interfaces and Services
Identify any new or expanded interfaces or service usage that could potentially increase cross platform application traffic and result in new usage of external applications.
Information Lifecycle Management (ILM)
Has an ILM strategy been defined for this application? If so, please describe. If not, please explain why not.
New SoftwareAre any new COTS products required? If so, please identify the product(s).
document.docx Page 4 of 18
<Project Name> Capacity Plan
2. APPLICATION USER BASE
Application User Base (Production Only)
Area Description Current Environment Change Expected
Application User Base
Describe total application user base including business unit affiliation where possible.
Describe when application is expected to be available (i.e. time of day and day of week) and list peak usage period.
List concurrent DB sessions (ODP)
document.docx Page 5 of 18
<Project Name> Capacity Plan
3. TRANSACTION VOLUME (PRODUCTION ONLY)
Transaction Volume (Production Only)
Area Description
Transaction Name
(add or delete rows as required)
Current Consumption
(Daily)
Expected Increase (Daily)
Transaction Volume
Is there any anticipated change in transaction volume or new transactions (where transaction is defined as a Critical Business Process or Unit of Work)?
document.docx Page 6 of 18
<Project Name> Capacity Plan
4. BUSINESS INTELLIGENCE METRICS (PRODUCTION ONLY)
Business Intelligence Metrics (Production Only)
Area Description Current Expected Increase for Report Period
Estimated number for the Report
Period
Data Warehouse Metrics
Cognos – Number of Users 0
Cognos – Number of Reports
0
Cognos - Number of Cubes 0
Cognos – Number and Size of Output Versions
0
Cognos – Number of Dashboard Pages
0
Informatica - Number of ETL Processes
0
ODS Metrics
Cognos – Number of Users 0
Cognos – Number of Reports
0
Cognos - Number of Cubes 0
Cognos – Number and Size of Output Versions
0
Cognos – Number of Dashboard Pages
0
Informatica - Number of ETL Processes
0
document.docx Page 7 of 18
<Project Name> Capacity Plan
5. SYSTEM RESOURCES (ALL ENVIRONMENTS)
System Resources (All Environments)
Area Description Comments
System Resources
Will there be changes to the application that may require additional processing capacity. If so, please estimate the percentage increase.
Development
Integration Test
System Acceptance Test
Test for Production
Training
Production
document.docx Page 8 of 18
<Project Name> Capacity Plan
6. DATA WAREHOUSE DATABASES (ALL ENVIRONMENTS)
Data Warehouse Database (All Environments)
Area Description Current Size Expected Increase for Report Period
Estimated Total Size
Data Warehouse Database
Will there be any growth to the current size of the data warehouse database?
Development
Integration Test
System Acceptance Test
Load Test
Test for Production
Training
Production
document.docx Page 9 of 18
<Project Name> Capacity Plan
7. OPERATIONAL DATA STORE (ALL ENVIRONMENTS)
Operational Data Store (ODS) (All Environments)
Area Description Current Size Expected Increase for Report Period
Estimated Total Size
Operational Data Store
(ODS) Database
Will there be any growth to the current size of the operational data store database?
Development
Integration Test
System Acceptance Test
Load Test
Test for Production
Training
Production
document.docx Page 10 of 18
<Project Name> Capacity Plan
8. FILE STORAGE (ALL ENVIRONMENTS)
File System Storage (All Environments)
Area DescriptionServer Type (Web, Utility, Report)
(add or delete rows as required)
Current Size
Change Expected
File System Storage
(i.e. Non-Database)
Will there be any growth to the size of non-database server storage (e.g. application code, input files, log files, reports, etc.).
Development
Web Server
PWISDEVWEB02
Utility Server N/A
Report Server
PWISHBGCOG16
PWISSATRPT02
PWISDEVSRS10
FSWS
PWISDEVSOA10
Data Warehouse Servers
SOA Server
PWISDEVSOA10
iRep
Integration Test
Web Server
document.docx Page 11 of 18
<Project Name> Capacity Plan
File System Storage (All Environments)
Area DescriptionServer Type (Web, Utility, Report)
(add or delete rows as required)
Current Size
Change Expected
PWISHBGINT04
Utility Server PWISINTAPP15
Report Server
PWISINTSRS15
FSWS
PWISDEVSOA10
Data Warehouse Servers
SOA Server
PWISDEVSOA10
iRep
Web Server
PWISSATWEB17
PWISSATWEB18
Utility Server
PWISSATAPP21
Report Server
PWISSATSRS25
PWISHBGCOG26
document.docx Page 12 of 18
<Project Name> Capacity Plan
File System Storage (All Environments)
Area DescriptionServer Type (Web, Utility, Report)
(add or delete rows as required)
Current Size
Change Expected
PWISHBGCOG27
PWISSATRPT02
FSWS
PWISSATSOA20
PWISSATSOA21
Data Warehouse Server
SOA Servers
PWISSATSOA20
PWISSATSOA21
iRep
Test for Production
Web Server
PWISTFPWEB20
Utility Server
PWISTFPAPP23
Report Server
PWISTFPSRS20
FSWS
PWISSATSOA20
PWISSATSOA21
iRep
document.docx Page 13 of 18
<Project Name> Capacity Plan
File System Storage (All Environments)
Area DescriptionServer Type (Web, Utility, Report)
(add or delete rows as required)
Current Size
Change Expected
Data Warehouse Servers
Web Service Servers
Training
Web Server
PWISTRNWEB01
Utility Server
PWISSATAPP21
Report Server
PWISTRNSRS29
FSWS
PWISSATSOA20
PWISSATSOA21
iRep
Data Warehouse Servers
SOA Servers PWISSATSOA20
PWISSATSOA21
Production
Web Server
PWISPRDWEB35
document.docx Page 14 of 18
<Project Name> Capacity Plan
File System Storage (All Environments)
Area DescriptionServer Type (Web, Utility, Report)
(add or delete rows as required)
Current Size
Change Expected
PWISPRDWEB39
Utility Server
PWISPRDAPP30
Report Server
PWISPRDRPT30
PWISPRDSRS31
FSWS
PWISPRDFSW30
iRep
Data Warehouse Servers
Web Services Servers
document.docx Page 15 of 18
<Project Name> Capacity Plan
9. NETWORK BANDWIDTH (PRODUCTION ONLY)
Network Bandwidth (Production Only)
Area Description Firewall ZoneCurrent
SizeChange Expected
Network Bandwidth
Will there be a major growth to the amount of Network Bandwidth (e.g. additional bandwidth over just normal web traffic, such as extensive binary image data).
User Zone
App Zone
Perimeter Zone
document.docx Page 16 of 18
<Project Name> Capacity Plan
10. DGS PRINT SERVICE (PRODUCTION ONLY)
DGS Print Services (Production Only)
Area Description DGS Constraints Current Usage Change Expected
DGS Print Services
Will there be changes to the usage of DGS print services?
Bandwidth / Transfer Size
Transfer Time / Duration
Mail Insertion (Gunther, Pitney Bowes)
document.docx Page 17 of 18
<Project Name> Capacity Plan
11. ENTERPRISE SERVICE USAGE (PRODUCTION ONLY)
Enterprise Service Usage (Production Only)
Area Description Enterprise Service Current Usage Change Expected
Enterprise Service Usage
Will there be any changes to the usage of existing enterprise services?
MCI.NET
MPI.NET
ELN
Provider Search Service
Submit Application Service
Enterprise Rate Service
Enterprise Correspondence Services
Rules Engine Services (Corticon)
Reporting Services (SSRS)
Address Validation / Geo-Specific Services
Self Registration Service
Authentication / Authorizations (CA Products)
document.docx Page 18 of 18