2.144.2 Business Capacity Management

Manual Transmittal

October 08, 2019

Purpose

(1) To transmit revisions made to the Business Capacity Management (Bcap) process.

Material Changes

(1) The revisions include:

  • Added program controls (scope and objective)

Effect on Other Documents

IRM 2.144.4 Business Capacity Management Process dated September 2015 is superseded

Audience

The Business Capacity Management Process is applicable to all ACIO (Associate Chief Information Officer) areas with responsibility for Capacity management

Effective Date

(10-08-2019)


Sri Rao
Director, Solution Engineering Enterprise Services

Program Scope and Objectives

  1. Overview - This process is to provide guidance for support of Capacity Management.

  2. Purpose - Is to provide a high level overview to organizations that have responsibility to support capacity for the IRS and its businesses.

  3. Audience - To all organizations that have capacity management responsibilities.

  4. Policy Owner - The ACIO of Enterprise Services (ES).

  5. Program Owner -Will be the Director of Solutions Engineering (SE) located within the ES .

  6. Primary Stakeholders - Are all ACIO areas that have responsibility for Business Capacity planning.

  7. Program Goals - The program goal is to forecast and build the best capacity infrastructure to support the IRS mission
    .

Background

  1. A process is defined as “A set of related activities that accomplish a common goal”. The process definition laid out in this document further breaks down these Activities into Tasks, each of which have a complete set of attributes defined such as data and tool specifications and the role(s) responsible for executing the tasks. The document also includes process goal and objectives, metric, role definitions, policies and other process related attributes.
    This process was developed to align to the ITIL framework.

Process Description
  1. The Business capacity management is the funding, forecasting, designing and building the infrastructure to support he IRS mission

Goal
  1. The process goal describes a specific purpose or achievement toward which the efforts of the process are directed. Each process has a specific focus and when combined with the other processes, forms a comprehensive framework for delivering and managing services.
    The Goal of this process is to Deploy a cost efficient solution to support the IRS mission

    • The goal of Business Capacity Management is to ensure that the capacity of the IT services and the infrastructure is able to deliver the agreed service level targets in a cost effective and timely manner.

Objectives
  1. Process objectives describe material outcomes that are produced or achieved by the process. The following is a list of objectives for this process:
    The objective is to ensure the delivery of capacity is cost effective.

    • To ensure that SLA and capacity are developed correctly

Authority

  1. All proposed changes to this document should be submitted in writing, with supporting rationale, to the Solution Engineering, Front door email:*IT Engineering Customer Support

Roles and Responsibilities

  1. Each process defines at least one role. Each role is assigned to perform specific tasks within the process. The responsibilities of a role are confined to the specific process. They do not imply any functional standing within the hierarchy of an organization. For example, the process manager role does not imply the role is associated with or fulfilled by someone with functional management responsibilities within the organization. Within a specific process, there can be more than one individual associated with a specific role. Additionally, a single individual can assume more than one role within the process although typically not at the same time.

    [Identify process roles and provide a brief description in the table. See example below].

    Name Description
    Capacity Manager This manager will make sure that the analyst is performing their duties. Also to assign task in order to me the IRS Mission
    Capacity Analyst The analyst will have many rolls depending on what organization they are representing.
    Higher authority This is usually an executive that has the final word on the direction, when there is decision to be made.
    Operational Manager This is the manager who will make sure that the capacity is up an running to fulfill the business requirements
    Stakeholders Organizations that would have a say in how te capacity should be deployed
    Service Mangers When the service has been defined tis is the manager that will make sure that the IT capacity is meeting the desired goals.

Program Management and Review

  1. Policies outline a set of plans or courses of action that are intended to influence and determine decisions or actions of a process. Policies provide an element of governance over the process that provides alignment to business vision, mission and goals.

    Process Management  
    Statement: The Business Capacity Management process will have a single Process Owner and a separate Process Manager responsible for implementation and ensuring adherence to the process. The process will be reviewed regularly to ensure that it continues to support the business requirements of the enterprise. The process will be designed and developed based on ROI to the business. Process metric will be focused on providing relevant information as opposed to merely presenting raw data.
    People:  
    Statement: Roles and responsibilities for the process must be clearly defined and appropriately staffed with people having the required skills and training. The mission, goals, scope and importance of the process must be clearly and regularly communicated by upper management to the staff and business customers of IT. All IT staff (direct and indirect users of the process) shall be trained at the appropriate level to enable them to support the process.
    Rationale: It is imperative that people working in, supporting or interacting with the process in any manner understand what they are supposed to do. Without that understanding [Business Capacity Management will not be successful.
    Process:  
    Statement: Modifications to the Business Capacity Management] process must be approved by the Process Owner. The design of the process must include appropriate interfaces with other processes to facilitate data sharing, escalation and workflow. The process must be capable of providing data to support real-time requirements as well as historical/trending data for overall process improvement initiatives. The process must be fully documented, published and accessible to the various stakeholders of the process. The process will be reviewed on a periodic basis in order to ensure it continues to support organizational goals and objectives (continuous improvement). The process must include Inputs, Outputs, Controls, Metrics, Activities, Tasks, Roles and Responsibilities, Tool and Data requirements along with documented process flows. The process will be kept straight forward, rational, and easy to understand.
    Rationale: The process must meet operational and business requirements.
    Technology and Tools:  
    Statement: All tools selected must conform to the enterprise architectural standards and direction. Existing in-house tools and technology will be used wherever possible, new tools will only be entertained if they satisfy a business need that cannot be met by current in-house tools. The selection of supporting tools must be process driven and based on the requirements of the business. Selected tools must provide ease of deployment, customizing and use. Automated workflow, notification and escalation will be deployed wherever possible to minimize delays, ensure consistency, reduce manual intervention and ensure appropriate parties are made aware of issues requiring their attention.

    The tools used by this process are the following:
    Identify and list the technology and/or tools used in process.
    • Each organizational areas will have their own specific tools to perform the tasks needed to support this process

    Rationale: Technology and tools should be used to augment the process capabilities, not become an end themselves.

Program Control

  1. Activities involved in ensuring a process is predictable, stable, and consistently operating at the target level of performance.

Controls
  1. Process controls represent the policies and guiding principles on how the process will operate. Controls provide direction over the operation of processes and define constraints or boundaries within which the process must operate.

    [Identify and provide a brief description of your process controls. See example below].

    Name Description
    ELC Milestone reviews Enterprise lifecycle will provide guidance to projects as they deploy their IT applications.
    Change requests When changes are made to capacity this is where it will be tracked
    Procurement Procurements tracks initial orders to acquire capacity
    SDSR (design Specification report) Approved design reports showcase the approved designs that will support capacity
    Capacity management policy The policy is the directive that the IT CIO requires.
Metrics
  1. Metrics are used for the quantitative and periodic assessment of a process. They should be associated with targets that are set based on specific business objectives. Metrics provide information related to the goals and objectives of a process and are used to take corrective action when desired results are not being achieved and can be used to drive continual improvement of process effectiveness and efficiency.

  2. Management will regularly set targets for process performance, gather quantifiable data related to different functions of the [Process Name] process, and review that data in order to make informed decisions and take appropriate corrective action, if necessary. All Measurements will have a defined data dictionary, map to the organizational strategic goals, and be documented in a Process Measurement Plan. The Process Measurement Plan template is available in the IT PAL.

Tailoring Guidelines
  1. The tailoring guidelines identify the allowable variations of the IT organization’s standard process as needed for adjustments (adding, deleting, modifying) relative to specific operational or functional needs of another organization. Process tailoring is about roles and procedures, not the standard process or major activities defined in this process. All tailoring request, with supporting rationale, must be submitted in writing to and approved by the Business Capacity Management owner.
    Each Origination will maintain there own tailoring to address their adjustments

Terms/Definitions/Acronyms

  1. Terms/Definitions/Acronyms

Terms and Definitions
  1. Terms and Definitions

    [Enter terms and definitions identified in this document. See example below].

    Term Definition
    RACI The RACI model is based on the principle that people act in one of four ways when executing a task. It accounts for the fact that more than one role may be active in performing a specific task while clearly defining specific responsibilities for that role. While many roles may be involved in a task only one is Accountable for the results. The actions are: R Responsible for the action (may do the task) A Accountable for the action (including approval) C Required to be Consulted on the action I Required to be Informed of the action If a task does not have an Accountable role indicated then the Responsible role is assumed to be accountable for the task.
    Service level agreements Service level agreement is an agreement between the Business and the IT to achieve its goals
    Service level management Service management is the focus on aligning the needs of the business to its partners
    Service level requirements A statement from a customer to a service provider describing their service expectations.
Acronyms
  1. Acronyms

    [Identify and list the acronyms and definitions identified in this document. See example below].

    Acronyms Description
    RACI Responsible, Accountable, Consulted and Informed
    CI Configuration Items
    ES Enterprise services
    ELC Enterprise life cycle
    IPM Integrated process management
    IRM Internal Revenue Manual
    IT Information technology
    ITIL Information technology information library
    ITSM Information technology service management
    OLA Operational level agreements
    IT PAL Process asset library
    PBA Patterns of business activity
    PD Process description
    RFC Request for change
    SLA Service level agreements
    SLM Service level management
    SLR Service level requirements

Related Resources

  1. MITRE Contract support, ITIL foundations. and the internet.

Training

  1. Process training involves training all stakeholders about key processes that are crucial for an organization to deliver business objectives. Training provides clarity to employees on a set of procedures that needs to be carried out as part of the process and the best possible way to do them. List below the training resources available for this process:
    [Identify and list training resources].

    • ELC Training

    • ELMS courses

    • ITIL Foundations training

    • Engineering overview

Process Workflow

  1. A process workflow consists of Activities and Tasks, Inputs and Outputs, Roles, and Flow Diagrams. It describes the tasks, procedural steps, organizations or people involved, required input and output information, and tools needed for each step of the process.

Main Process Diagram

  1. Business Capacity Process Flow Diagram

    Figure 2.144.2-1

    This is an Image: 61946001.gif
     

    Please click here for the text description of the image.

Inputs

  1. Process inputs are used as triggers to initiate the process and to produce the desired outputs. Users, stakeholders or other processes provide inputs. The following is a list of inputs for this process:

    [Complete process input table. See examples below].

    Name Description Supplier
    Business information Information about the business strategy, plans and requirements Business units
    Service & information technology components relationships Information about the services, the relationship to the business requirements, and infrastructure components needed. Business/EA/SE/AD
    Component performance and capacity Capacity and Performance specifications from the manufacturer or developer; detailing expected performance and thresholds. EA/SE/EOPS
    Performance information Current and historical performance and utilization information for IT services and IT infrastructure components. Testing/EOPS
    Configuration management Configuration data on the components, services and relationships EOPS/Business
    Workload/operational information Information about job schedules, operational tasks, and services dependencies Business/EOPS
    Patterns of business activity An analysis of the workload showing how this varies according to demand Business/EOPS
    Change Management Capacity Management is responsible for assessing the impact of all proposed changes on the performance of infrastructure and services being provided Testing/Business/EOPS
    Financial Information Information about the cost of providing a service. This will include, hardware, software, Component costs, and support and maintenance charges Business/S&P/SE/EOPS

Outputs

  1. Each process produces tangible outputs. These outputs can take the form of products or data and can be delivered to a user or stakeholder or they can be used as inputs to other processes. Outputs are measurable in terms of quantity and quality.

    [Complete process output table. See example below].

    Name Description Recipient
    Capacity Plan Any strategy or plans that lay out capacity needed to support stakeholders

Activities

  1. An activity is a major unit of work to be completed in achieving the objectives of the process. A process consists of a sequence of related activities that transforms inputs into outputs and performed by the roles defined in the process. Activities are measurable in terms of efficiency and effectiveness. Identify the activities in the process and provide a brief description. The activities must correspond with the high-level process flow diagram above.

    [Complete process activities table. See examples below].

    ID Name Description
    BCap 1.0 Plan the Business Capacity Management Strategy The IT Strategic Plan lays the foundation for the Capacity Management process. The plan reflects an understanding of how IRS IT Projects utilizes IT Enterprise resources to enable key processes. With an understanding of the interrelationships among IT processes Capacity Management will be in a good position to estimate capacity needs. Capacity Management expresses business requirements into capacity terminology i.e. services and component needs and aggregates them with the common Infrastructure in ways which identify commonalities and areas where resources might be efficiently shared without unacceptable risks.
    BCap 2.0 Negotiate Service Level Agreements and implement Changes Service Level Agreements (SLAs) should include details of the anticipated service throughputs and the performance requirements. The purpose of this step is to provide Service Level Management (SLM) with targets that have the ability to be monitored and upon which the service design has been based. Confidence that the service design will meet the Service Level Requirements (SLR) and provide the ability for future growth can be gained by using modeling. Capacity will assess, Agree and document new and updated requirements.
    BCap 3.0 Review Component Performance BCap ensures the monitoring of the utilization of underlying components. All of the collected data is recorded, analyzed, and reported. Therefore, the purpose of this step is to ensure that the performance of the solution(s) meet the business requirements.
    BCap 4.0 Develop the Capacity Plan The development and update of a Capacity Plan should occur at pre-defined intervals. It should be published annually, in line with the business or budget lifecycle, and completed before negotiations future budgets. The purpose of the Capacity Plan is to document what capacity is needed in the future and at what cost. Also, the Capacity Plan forecasts hardware upgrades or additional equipment needed to meet future service level objectives and includes information on sizing of any new systems proposed. The Capacity Plan documents cost constraints and availability or reliability requirements. The plan should discuss current utilization rates and service performance. It should be based upon business strategies and explicitly recognize business strategic and operational plans and forecasts in it’s estimates of future requirements. Recommendations should include estimates of necessary resources, relevant impacts, associated costs and benefits, etc.
    BCap 5.0 Review the Capacity Plan The purpose of Capacity Plan review is to periodically re-issue the updated plan to take into account changes in business plans, to report on the accuracy of forecasts and to make or refine recommendations.
    BCap 6.0 Review SLAs and Service Catalog Business Capacity Management assists SLM in understanding the Customers' Capacity requirements, for example in terms of required response times, expected throughput and pattern of usage, including the terminal population. The purpose of this Business Capacity Management step is to facilitate the SLA negotiation process by providing possible solutions to a number of scenarios. For example, if the terminal population is less than 20 then response times can be guaranteed to be less than two seconds. If more than 20 Users connect then extra network bandwidth is needed to guarantee the required response time.

Procedure

  1. Procedure

BCap 1.0 Business Capacity Management
  1. The tasks and roles for each activity are the following for this process are the following:

    ID Task Name and Description Role RACI
    BCap 1.1 Review existing Capacity
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.2 Review approved RFC(s)
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.3 Analyze Business Information
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.4 Analyze Service Performance Issues
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.5 Analyze Service Information
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.6 Analyze Financial Information
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.7 Analyze Performance Information
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.8 Analyze CMIS Information
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.9 Analyze Patterns of Business Activity
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.10 Forecast Capacity demands
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 1.11 Store Capacity Plan and supporting material in CMIS
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

BCap 2.0 Negotiate Service Level Agreements and Implement Change
  1. Figure 2.144.2-2

    ID Task Name and Description Role RACI
    BCap 2.1 Review Capacity Plan review results
    • Capacity Manager

    • Capacity Analyst

    • Operations Manager

    • R

    • C

    • I

    BCap 2.2 Review SLA Performance
    • Capacity Manager

    • Capacity Analyst

    • Operations Manger

    • R

    • C

    • C

    BCap 2.3 Conduct impact analysis of recommended SLA changes, and conduct modeling.
    • Capacity Manager

    • Capacity Analyst

    • Operations Manger

    • R

    • C

    • I

    BCap 2.4 Review recommendations for SLA changes with SLM
    • Capacity Manager

    • Capacity Analyst

    • Operations Manger

    • R

    • C

    • I

    BCap 2.5 Store artifacts in the CMIS as necessary
    • Capacity Manager

    • Capacity Analyst

    • Operations Manger

    • R

    • C

    • I

BCap 3.0 Review Component Performance
  1. Figure 2.144.2-3

    ID Task Name and Description Role RACI
    BCap 3.1 Review Capacity Plan review results
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 3.2 Review SLA
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 3.3 Review component performance, capacity information and reports
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 3.4 Develop recommendations for changes to components
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    BCap 3.5 Store artifacts in the CMIS as necessary
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

BCap 4.0 Develop Capacity Plan
  1. ID Task Name and Description Role RACI
    BCap 4.1 Produce or revise the capacity plan
    • Capacity Manager

    • Capacity Analyst

    • R

    • C

BCap 5.0 Review the Capacity Plan
  1. Figure 2.144.2-4

    ID Task Name and Description Role RACI
    BCap 5.1 Review the Capacity Plan
    • Capacity Manager

    • Operation manager

    • Business Stakeholder

    • R

    • I

    • C

    BCap 5.2 Approve the Capacity Plan
    • Higher Authority

    • R

    BCap 5.3 Baseline the Capacity Plan
    • Capacity Manager

    • R

BCap 6.0 Review SLA’s and Service Catalog
  1. Figure 2.144.2-5

    ID Task Name and Description Role RACI
    BCap 6.1 Review SLAs
    • Capacity Manager

    • Operation manager

    • Capacity Analyst

    • Business Stakeholder

    • R

    • C

    • C

    • C

    BCap 6.2 Record review results
    • Capacity Manager

    • R

    BCap 6.3 Store review artifacts in the CMIS as necessary
    • Capacity Manager

    • Capacity Analyst

    • R

    • C