Part 2. Information Technology

Chapter 144. Capacity Management

Section 4. Component Capacity Management

2.144.4 Component Capacity Management

Manual Transmittal

August 06, 2019

Purpose

(1) This transmits revised IRM 2.144.4, Capacity Management, Component Capacity Management.

Material Changes

(1) The revisions include:

  • Added Internal Control Section

Effect on Other Documents

IRM 2.144.4 Component Capacity Management Process dated November 25, 2015 is superseded.

Audience

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

Effective Date

(08-06-2019)


Chief Information Officer

2.144.4.1 (08-06-2019)

Program Scope and Objectives

  1. Overview - This IRM is directed to organizations that will build, monitor, maintain, tune and upgrade components that support the businesses and their mission.

  2. Purpose - This to provide guidance to support the mission by efficiently maintaining the component infrastructure.

  3. Audience - This process is directed to all organizations that have responsibility to monitor and maintain the component environments.

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

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

  6. Primary Stakeholders - Will be organizations that have responsibility to maintain the IRS capacity infrastructure.

  7. Program Goal - To deliver and maintain the most cost effective and efficient capacity infrastructure( i.e., hardware, software, applications and operating systems, etc.) to the business stakeholders to help ensure their support of the IRS mission is met.
    .

2.144.4.1.1 (08-06-2019)

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, metrics, role definitions, policies and other process related attributes.

2.144.4.1.1.1 (08-06-2019)
Process Description

  1. The Component Capacity Management process translates business needs and plans into requirements for service and IT infrastructure, ensuring that the future business requirements for IT services are quantified, designed, planned and implemented in a timely fashion.

2.144.4.1.1.2 (08-06-2019)
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.
    [State the goal of your process]

    • To deliver and maintain the most cost effective and efficient capacity infrastructure( i.e., hardware, software, applications and operating systems, etc.) to the business stakeholders to help ensure their support of the IRS mission is met

2.144.4.1.1.3 (08-06-2019)
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:
    [List the objectives of your process].

    • To deliver and maintain the most cost effective and efficient capacity infrastructure( i.e., hardware, software, applications and operating systems, etc.) to the business stakeholders to help ensure their support of the IRS mission is met.

2.144.4.1.2 (08-06-2019)

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

2.144.4.1.3 (08-06-2019)

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.
     

    Name Description
    Capacity Manager

    • Ensures process procedures are followed

    • Represents interests of Capacity Management at meetings and functions

    • Receives and acquires Higher Authority support as needed

    • Verifies and adjusts parameters used in the planning process

    • Adds and reviews system life cycle performance design criteria and production acceptance tests

    • Recommends resource re-allocations

    • Ensures that the Capacity Plan is current and that it tracks business growth and trends
    Capacity Analyst

    • Produces Capacity Plan with a forecast far enough ahead to take account of changes in IT capacity that comply with business plans and IT plans

    • Documents the need for Hardware, Software, and Component upgrades or additional equipment, based on SLRs, cost constraints, reliability and availability

    • Produce regular management reports including current usage of Components, expected trends and forecasts

    • Responsible for Capacity Management documentation
    Higher Authority

    • Approve resources to meet capacity requirements

    • Review and recommend capacity improvement recommendations

    • Review summary performance information describing capacity

    • Act as the final point of escalation for capacity issues
    Operational Manager

    • Provide ongoing maintenance of Configuration Items (CI) which affects their operation and institute measures to keep them operating at peak performance

    • Assist in describing the service chains associated with service provisioning

    • Participate in discussions of capacity

    • Meeting Operational Level Objectives and explaining variances from targets.
    Business Stakeholders

    • Negotiate capacity targets and sign-off on targets in Operational and/or Service Level Agreements

    • Review capacity performance against target and participate in preparation and recommendation of any remedial actions

    • Participate in preparation and review of Capacity Plan

    • Provide information on capacity
    Service Manager

    • Ensures that services are operational

    • Reviews Capacity Plans
2.144.4.1.4 (08-06-2019)

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 Component 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 metrics 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 Component Capacity Management process will not be successful.
    Process:  
    Statement: Modifications to the Component 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:

    • EOPS will have many variety of tools to use in determining what they need to accomplish the task.
    Rationale: Technology and tools should be used to augment the process capabilities, not become an end themselves.
2.144.4.1.5 (08-06-2019)

Program Control

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

2.144.4.1.5.1 (08-06-2019)
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
    Capacity Management Policy Business Capacity Management is a required activity mandated by the IRS CTO
    Scope Business Capacity Management process is limited to all ACIO areas with responsibility for Capacity Management
    Process Metric Business Capacity Process Monitors will continuously verify to what degree the Business Capacity Management Process is being used.
2.144.4.1.5.2 (08-06-2019)
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 [Component Capacity Management] 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.

2.144.4.1.5.3 (08-06-2019)
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 [Component Capacity Management process owner.
    [Enter tailoring guideline instructions].

2.144.4.1.6 (08-06-2019)

Terms/Definitions/Acronyms

  1. Terms/Definitions/Acronyms

2.144.4.1.6.1 (08-06-2019)
Terms and Definitions

  1. Terms and Definitions

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

    Term Definition
    Business Capacity Management A strategic capacity management process done when decisions to expand or contract the infrastructure are made due to expected changes in demand by the business (addition of new applications, new infrastructure, etc.).
    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 Agreement A service-level agreement is part of a service contract where the level of service is formally defined. In practice, the contracted delivery time (of the service) or performance.
    Service level management A set of practices for IT service management (ITSM) that focus on aligning it services with the needs of the business
    Service Level Requirements A statement from a customer to a service provider describing their service expectations. It includes the requirements of the customer from the service provider
2.144.4.1.6.2 (08-06-2019)
Acronyms

  1. Acronyms

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

    Acronyms Description
    CCap Component Capacity Management
    CI Configuration Item
    CMMI Capability Maturity Model Integration
    CMIS Capacity Management Information system
    ES Enterprise Services
    IPM Integrated Process Management
    IRM Internal Revenue Manual
    IRS Internal Revenue Service
    IT Information Technology
    ITIL Information Technology Infrastructure Library
    ITSM Information Technology Service Management
    PAL Process Asset Library
    PBA Patterns of Business Activity
    PD Process Description
    PMI Project Management Institute
    RACI Responsible, Accountable, Consulted and Informed
    ROI Return on Investment
    SLA Service Level Agreement
    SLM Service Level Management
    SLR Service Level Requirements
2.144.4.1.7 (08-06-2019)

Related Resources

  1. Internet, ITIL Framework, ITIL WIKI, Mitre support staff.

2.144.4.1.8 (08-06-2019)

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:

    • Capacity Management, ELMS course #5775

2.144.4.2 (08-06-2019)

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.

2.144.4.2.1 (08-06-2019)

Main Process Diagram

  1. Component Capacity Management Process Flow Diagram

    Figure 2.144.4-1

    This is an Image: 62038001.gif
     

    Please click here for the text description of the image.

2.144.4.2.2 (08-06-2019)

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. Organization's Business Groups
    Service & Information Technology (IT) Component Relationships Information about the Services, the relationship to the business requirements, and infrastructure components needed. Business and IT Strategies, Service Strategy, IT plans and current budgets
    Component Performance and Capacity Information Capacity and Performance specifications from the manufacturer or developer; detailing expected performance and thresholds. Manufacturers and Suppliers
    Service Performance Issues Capacity related Incidents and Problems plus service level breaches. Incident and Problem Management processes
    Service Information Details of the Service Level Requirements, Service Level Agreements and data about the performance and utilization of the Services. SLM process
    Financial Information Information about the cost of providing a service. This will include, hardware, software, Component costs, and support and maintenance charges. Financial Management process
    Change Information (Request for Change) Capacity Management is responsible for assessing the impact of all proposed changes on the performance of infrastructure and services being provided. Change Management process
    Performance Information Current and historical performance and utilization information for IT services and IT infrastructure components. Capacity Management Information System (CMIS)
    Configuration Management System (CMIS) Information Configuration data on the components, services and relationships. Configuration Management System (CMIS)
    Workload / Operational Information Information about job schedules, operational tasks, and services dependencies. IT Operations team
    Patterns of Business Activity (PBA) An analysis of the workload showing how this varies according to demand. Demand Management
2.144.4.2.3 (08-06-2019)

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
    Components Performance, Information and Reports Reports on the performance of Components using data in the CMIS.

    • Capacity Manager

    • Business Stakeholders

    • Operational Manager
    Workload Analysis and Reports Reports providing information about workloads that can be used for modeling, application sizing, and capacity planning.

    • Capacity Manager

    • Operational Manager

    • Business Stakeholders
    Ad Hoc Capacity and Performance Reports Performance and Utilization reports generated on an as needed basis, typically in response to capacity issues.

    • Capacity Manager

    • Operational Manager

    • Business Stakeholders
    Forecasts and Predictive Reports Reports used to plan capacity changes and operatively identify potential capacity issues.

    • Capacity Manager

    • Operational Manager

    • Business Stakeholders
2.144.4.2.4 (08-06-2019)

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.
     

    ID Name Description
    CCap 1.0 Monitoring The purpose of this process step is to ensure the optimum use of the hardware and software components, that all agreed service levels can be achieved, and that business volumes are as expected
    CCap 2.0 Maintenance and Analysis The purpose of this process step is to determine the necessary changes to the configuration needed to implement the recommendations using the configuration management process, as needed
    CCap 3.0 Maintenance and Tuning The purpose of this process step is to determine the necessary changes to the configuration needed to implement the recommendations using the configuration management process, as needed.
    CCap 4.0 Component Upgrades The purpose of this process step is to introduce to the live operation services, any changes that have been identified by the monitoring and analysis activities. The implementation of any changes arising from these activities must be undertaken through a strict, formal Change Management process.
    CCap 5.0 Component Demand Management The purpose of this process step is to influence the demand for components and their use. A good Capacity forecast for components will anticipate and plan for peak demand. Demand Management is achieved by assigning resources according to priorities.
    CCap 6.0 Maintain the Capacity Management Information System The purpose of this process step is to ensure capacity management and performance information is easily available to stakeholders through a central repository or database. The database is used to collect much of the data input listed throughout this Component Capacity Management process description..
2.144.4.2.5 (08-06-2019)

Procedure

  1. Procedure

2.144.4.2.5.1 (08-06-2019)
CCap 1.0 Monitoring

  1. The tasks and roles for each activity are the following for this process are the following: There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    CCap 1.1 Monitor individual hardware components

    • Capacity Analyst

    • R

    		 Determined by local Capacity areas
    CCap 1.2 Monitor individual software components

    • Capacity Analyst

    • R

    		 Determined by local Capacity areas
    CCap 1.3 Collect data for the components on which monitoring is installed and activated

    • Capacity Analyst

    • R

    		 Determined by local Capacity areas
    CCap 1.4 Record the data and post to the CMIS

    • Capacity Analyst

    • R

    		 Determined by local Capacity areas

     

2.144.4.2.5.1.1 (08-06-2019)
Monitoring Cross Functional Flow Diagram

  1. Monitoring Cross Functional Flow Diagram

    Figure 2.144.4-2

    This is an Image: 62038002.gif
     

    Please click here for the text description of the image.

2.144.4.2.5.2 (08-06-2019)
CCap 2.0 Maintenance and Analysis

  1. Figure 2.144.4-3

    ID Task Name and Description Role RACI Duties
    CCap 2.1 Review the recommendations and instruct their implementation

    • Capacity Manager

    • Operations Manager

    • R

    • C

    		 Determined by local Capacity areas
    CCap 2.2 Develop any needed instructions for operations

    • Capacity Analyst

    • Capacity Manger

    • R

    • A

    		 Determined by local Capacity areas
    CCap 2.3 Determine adjustments needed to the components configuration

    • Capacity Analysts

    • R

    		 Determined by local Capacity areas
    CCap 2.4 Assign work items

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 2.5 Adjust the components following the CM Process

    • Operations Manger

    • R

    		 Determined by local Capacity areas
    CCap 2.6 Verify the adjustments

    • Capacity Manager

    • Operations Manager

    • R

    • C

    		 Determined by local Capacity areas
    CCap 2.7 Notify monitoring function of changes

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 2.8 Document actions taken and store in the CMIS

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
2.144.4.2.5.2.1 (08-06-2019)
Maintenance and Analysis Cross Functional Flow Diagram

  1. Maintenance and Analysis Cross Functional Flow Diagram

    Figure 2.144.4-4

    This is an Image: 62038003.gif
     

    Please click here for the text description of the image.

2.144.4.2.5.3 (08-06-2019)
CCap 3.0 Maintenance and Tuning

  1. Figure 2.144.4-5

    ID Task Name and Description Role RACI Duties
    CCap 3.1 Review the recommendations and instruct their implementation

    • Capacity Manager

    • Capacity Analyst

    • Operations Manager

    • R

    • C

    • C

    		 Determined by local Capacity areas
    CCap 3.2 Develop any needed instructions for operations

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 3.3 Determine adjustments needed to the components configuration

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 3.4 Assign work items

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 3.5 Adjust the components following the CM Process

    • Operations Manager

    • R

    		 Determined by local Capacity areas
    CCap 3.6 Verify the adjustments

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 3.7 Notify monitoring function of changes

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 3.8 Document actions taken and store in the CMIS

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
2.144.4.2.5.3.1 (08-06-2019)
Maintenance and Tuning Cross Functional Flow Diagram

  1. Maintenance and Tuning Cross Functional Flow Diagram

    Figure 2.144.4-6

    This is an Image: 62038004.gif
     

    Please click here for the text description of the image.

2.144.4.2.5.4 (08-06-2019)
CCap 4.0 Component Upgrade

  1. Figure 2.144.4-7

    ID Task Name and Description Role RACI Duties
    CCap 4.1 Review the recommendations and instruct their implementation

    • Capacity Manager

    • Capacity Analyst

    • Operations Manager

    • R

    • C

    • C

    		 Determined by local Capacity areas
    CCap 4.2 Develop any needed instructions for operations

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 4.3 Determine adjustments needed to the components configuration

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 4.4 Assign work items

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 4.5 Adjust the components following the CM Process

    • Operations Manager

    • R

    		 Determined by local Capacity areas
    CCap 4.6 Upgrade the components following the CM Process

    • Operations Manager

    • Capacity Manager

    • R

    • C

    		 Determined by local Capacity areas
    CCap 4.7 Verify the success of the upgrade

    • Capacity Manger

    • Capacity Analysts

    • Operations Manager

    • R

    • C

    • C

    		 Determined by local Capacity areas
    CCap 4.8 Notify monitoring function of changes

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 4.9 Document actions taken and store in the CMIS

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
2.144.4.2.5.4.1 (08-06-2019)
Component Upgrade Cross Functional Flow Diagram

  1. Component Upgrade Cross Functional Flow Diagram

    Figure 2.144.4-8

    This is an Image: 62038005.gif
     

    Please click here for the text description of the image.

2.144.4.2.5.5 (08-06-2019)
CCap 5.0 Component Demand Management

  1. Figure 2.144.4-9

    ID Task Name and Description Role RACI Duties
    CCap 5.1 Review the recommendations and instruct their implementation

    • Capacity Manger

    • Capacity Analysts

    • Operations Manager

    • R

    • C

    • C

    		 Determined by local Capacity areas
    CCap 5.2 Adjust the operational scheduling of workloads

    • Capacity Manger

    • Capacity Analysts

    • Operations Manager

    • C

    • C

    • R

    		 Determined by local Capacity areas
    CCap 5.3 Allocate components according to recommendations following the CM Process

    • Capacity Manger

    • Capacity Analysts

    • Operations Manager

    • C

    • C

    • R

    		 Determined by local Capacity areas
    CCap 5.4 Verify the success of the change

    • Capacity Manger

    • Capacity Analysts

    • Operations Manager

    • R

    • C

    • C

    		 Determined by local Capacity areas
    CCap 5.5 Notify monitoring function of changes

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
    CCap 5.6 Document actions taken and store in the CMIS

    • Capacity Manger

    • R

    		 Determined by local Capacity areas
2.144.4.2.5.5.1 (08-06-2019)
Component Demand Management Cross Functional Flow Diagram

  1. Component Demand Management Cross Functional Flow Diagram

    Figure 2.144.4-10

    This is an Image: 62038006.gif
     

    Please click here for the text description of the image.

2.144.4.2.5.6 (08-06-2019)
CCap 6.0 Maintain Capacity Management Information System

  1. Figure 2.144.4-11

    ID Task Name and Description Role RACI Duties
    CCap 6.1 Perform Administrative/Maintenance actions, as required

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 6.2 Facilitate data entry and retrieval

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 6.3 Maintain data that has been entered into the system

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 6.4 Support other systems that need the data

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
    CCap 6.5 Ensure reports are available to stakeholders and easily attainable

    • Capacity Manager

    • Capacity Analyst

    • R

    • C

    		 Determined by local Capacity areas
2.144.4.2.5.6.1 (08-06-2019)
Maintain Capacity Management Information System Cross Functional Flow Diagram

  1. Maintain Capacity Management Information System Cross Functional Flow Diagram

    Figure 2.144.4-12

    This is an Image: 62038007.gif
     

    Please click here for the text description of the image.