2.152.2 Data Management Process Description

Manual Transmittal

November 22, 2019

Purpose

(1) This transmittal revised IRM 2.152.2 Data Engineering, Data Management Process Description .

Material Changes

(1) Revised the entire document with updated Integrated Process Management (IPM) Process Description and Procedure Templates adding Internal Control Section aligned with agency-wide KISAM system.

Effect on Other Documents

IRM 2.152.2 dated July 31, 2015 is superseded.

Audience

This process description is applicable to all projects following the Enterprise Life Cycle (ELC) and customers who request data management services through the Configuration Management, Change Management KISAM, the Work Request Management System (WRMS), or the OnLine 5081 Service.

Effective Date

(11-22-2019)


Chief Information Officer

Program Scope and Objectives

  1. Overview - The objectives of this Data Management Process which is one of major process of Data Engineering is provide a set of related activities that accomplish a common goal of Data Management. 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. Purpose - This IRM contains procedural steps for Data Management Process within IRS.

  3. Audience - This process description is applicable to all projects following the Enterprise Life Cycle (ELC) and customers who request data management services through the Change Management KISAM system, the Work Request Management System (WRMS), or the OnLine 5081 Service.

  4. Policy Owner -The ACIO Enterprise Services is responsible for overseeing all aspects of Data Management Process that operates IRS agency-wide Data Management Process.

  5. Program Owner -The Chief of Process Maturity Group under the Director of Enterprise Services, Solution Engineering Division is responsible for the administration, procedures, and updates related to the program IRM.

  6. Primary Stakeholders - The Chief of Data Engineering Group under Enterprise Services, Solution Engineering Division is the Primary Stakeholders of this IRM has input in the procedures.

  7. Program Goals - This IRM provides the fundamental knowledge and procedural guidance for employees who request the Data Management Services from Data Engineering Group. By following the processes and procedures of this IRM, employees will achieve a given purpose of data related projects.
    .

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.

Process Description
  1. The mission of Data Management is to define an enterprise-wide data environment to more easily and efficiently organize, identify, share, reuse, and correlate data that enables the business to consume information and maximize the value to the agency. This Data Management Process Description describes what happens within the process and provides an operational definition of the major components of the process. This description specifies in a complete, precise, and verifiable manner, the requirements, design, and behavior characteristics of Data Management process. The process description (PD) is a documented expression of a set of activities performed to achieve a given purpose. Tailoring of this process in order to meet the individual needs of each project is covered in the Tailoring Guidelines section of this document. For the purpose of this document, roles are provided to describe a set of responsibilities for performing a particular set of related activities. Roles and/or responsibilities should fit your business terminology.

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.
    This IRM provides the fundamental knowledge and procedural guidance for employees who request the Data Management Services from Data Engineering Group.

    • To achieve a given purpose and states the guidelines that all projects should follow regarding the Data Management process.

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:

    • Provide a standardized and institutionalized Data Management guidelines within IRS.

Authority

  1. All proposed changes to this document must be submitted in writing, with supporting rationale, to the Chief, Enterprise Service, Solution Engineering, Process Maturity Group.

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.

    The following roles have been identified for this process:

    Name Description
    Change Initiator/Change Analyst (Project Office)
    • Create and submit Change Request or Work Request

    • Enters ELC process

    • Conducts data profiling; implements data quality check; develops balance control and validation

    • Submits an OnLine 5081 request for access the data system

    • Submits a Live Data Waiver request as required for user of SBU data

    • Consumes data through queries and generate required reports

    Infrastructure Executive Steering Committee (IESC) Provides governance for data technology platforms and funds data initiatives
    Solution Engineering Data Practice Group (Engineer/Analyst)
    • Determines scope and impact as related to ELDM

    • Determines data organization (OLTP/OLAP)

    • Advances ELC and achieves milestone approval

    • Reviews Data Management Process outputs

    • Aligns Project Data Model with ELDM

    • Determines impact on Data Warehouse environment

    • Certifies data contents

    • Identifies interfaces

    • Routes approved CRs to data platforms (e.g. EIP and BOE)

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 Data 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 Data Management Process will not be successful.
    Process:  
    Statement: Modifications to the Data 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, customization 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::
    • BusinessObejcts

    • Enterprise Informatica Platform

    • Greenplum Database

    • Tableau

    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.

    The process controls are the following:

    Name Description
    Data Implement Guide (DIG) Data implementation begins with vision and strategy activities and ends with system deployment. The Data Implementation Guide (DIG) provides guidance on how to document the flow of an information system's data throughout its life cycle: from acquiring, conversion, migration, storage to the time when it becomes obsolete and is deleted.
    Data Engineering Policy (Directive) Completion of Data Engineering Process The project will include in its engineering plan either by inclusion or reference, planning materials specifying how the following will be accomplished:
    • Execution Data Engineering Process

    • Obtaining needed resources to perform Data Engineering Process

    • Control of work products required by the Data Management Process

    • Engagement of stakeholders affected by the Data Management Process

    • Monitoring and Controlling of the Data Management Process

    • Collection of Data Management Process measures

    • Review of Data Management Process status with high level of management

    • Establishment of the Data Management Process within the project's defined processes

    • Submission of lesson learned and process improvement suggestions from the execution of Data Management Process

    Data Implementation Compliance Directive The Data Implementation Compliance Directive enforces the Implementing of the Data Implementation Guide (DIG).
    Scope All projects following the Enterprise Life Cycle (ELC) are required to perform Data Engineering Process and associated activities in accordance with this policy.
    Change Management Policies New KISAM Change Management Policies and procedures will consolidate all CCB into one Enterprise CCB
    Change Management Policies Change Management Policies and procedures.
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 Data 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.

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 Data Management Process owner.
    [Enter tailoring guideline instructions].

Terms/Definitions/Acronyms

  1. Terms/Definitions/Acronyms

Terms and Definitions
  1. Terms and Definitions
     

    Term Definition
    E300 The E300 is a subset of the E53, Capital Asset Plan, that summarizes the Business Case and outlines the benefits, costs, risks, and other OMB/Treasury requested data. It demonstrates an alignment with organizational objectives. It is used to determine if the effort should receive funding. The IRS submits the E300 to OMB to obtain funding approval for new major and existing major projects (Please see IRM 2.16.1.3.4.2). The E300 is updated during the life of the project based on the annual budget cycle.
    E53 The E53 is the Agency IT Investment Portfolio. It is submitted to request funds from OMB as part of the normal budgeting cycle and updated as required. All investments requiring OMB IT funding are listed on the E53.
    Enterprise Logical Data Model (ELDM) Enterprise Logical Data Model refers to an entity/relationship model in third normal form with fully attribute entities. It is a fully attributed entity relationship diagram (ERD), which shows each entity, its relationship to other entities and specifies the applicable business rules. An ELDM should focus only on business data. The value of logical data modeling has always been to establish the “single version of the truth” of an organization’s business functions.
    KISAM Knowledge Incident/Problem Service Asset Management Systemhttps://selfservice.web.irs.gov/webtier-9.52/ess.do
    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.
    WRMS The Work Request Management System is an ITIL-based COTS product for registering and managing demand requests for IT products and services.
Acronyms
  1. Acronyms

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

    Acronyms Description
    ELC Enterprise Life Cycle
    IPM Integrated Process Management or Integrated Production Model when uses for database environment
    ITIL Information Technology Infrastructure Library
    PAL Process Asset Library
    RACI Responsible, Accountable, Consulted and Informed
    RDBMS Relational Database Management System
    SBU Sensitive But Unclassified

Related Resources

  1. ELC Artifacts.

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:
    Any Data Tools that come into the process.

    • BusinessObjects

    • Enterprise Informatica Platform

    • Greenplum Database

    • Tableau

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. Data Management Process Description Flow Diagram

    Figure 2.152.2-1

    This is an Image: 59989001.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:
     

    Name Description Supplier
    Change Request A Change Request for the service of 5 C’s from Data Management Process Change Initiator/Change Analyst
    Disposition Change Request Infrastructure Executive Steering Committee (IESC) would determine approve or deny the request Infrastructure Executive Steering Committee (IESC)
    On-Line 5081 Request A request for accessing the Data System Change Initiator/Change Analyst
    Data Platforms Solution Engineering Data Practice Group provides appropriate Data Platform to Project Office(s), such as: Enterprise Business Intelligence Platform (EBIP); Enterprise Informatica Platform (EIP) Solution Engineering Data Engineering Practice Group (Engineer/Analyst)
    Baseline and Milestone Updated for Primary Design The following documents should be started (baseline) or updated at the corresponding Enterprise Life Cycle (ELC) Phase & Milestone:
    • E300 and E53

    • Project Tailoring Plan

    • Project Management Plan

    • Business System Requirement (BSR) (Logical Data Model/Business Metadata)

    Solution Engineering Data Engineering Practice Group (Engineer/Analyst)
    Baseline and Milestone Updated for Detailed Design Baseline and Milestone Updated for Detailed Design The following documents should be started (baseline) or updated at the corresponding Enterprise Life Cycle (ELC) Phase & Milestone:
    • DSR (Physical Data Model/Technical Metadata)

    • ICD (Data Movement Metadata)

    Solution Engineering Data Engineering Practice Group (Engineer/Analyst)

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.
     

    Name Description Recipient
    Data Platforms Solution Engineering Data Practice Group provides appropriate Data Platform to Project Office(s), such as: Enterprise Business Intelligence Platform (EBIP); Enterprise Informatica Platform (EIP) Change Initiator/Change Analyst (Project Office)
    Disposition Data Collection Change Request (CR) Infrastructure Executive Steering Committee (IESC) determines if the Change Request is denied or approve Change Initiator/Change Analyst (Project Office)
    Required Reports Solution Engineering Data Practice Group provides all kinds of request reports from Project Office(s) Change Initiator/Change Analyst (Project Office)
    Baseline and Milestone Updated for Primary Design A completed Data Management design with the applied version controlled:
    • E300 and E53

    • Project Tailoring Plan

    • Project Management Plan

    • Business System Requirement (BSR

      1. Entities & Attributes (Logical Data Model)

      2. Business Metadata (Business Taxonomy)

      )

    Change Initiator/Change Analyst (Project Office)
    Baseline and Milestone Updated for Detailed Design A completed Data Management design with the applied version controlled:
    • Design Specification Report (DSR) (Physical Data Model/Technical Metadata)

      1. Tables & Columns (Physical Data Model)

      2. Technical Metadata (Technical Taxonomy)

    • Interface Control Document (ICD) (Data Movement Metadata)

      1. Schema; Service; Message Interchange Metadata (XML Taxonomy)

    IChange Initiator/Change Analyst (Project Office)

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
    Step 1 Data Collection To collect data that exist in databases (structured) and that exist outside databases (unstructured) from across the agency and external sources.
     
    • Change Initiator/Analyst (Project Office) creates and submits Data Collection Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineer/Analyst) determines the data source, and evaluates the Change Request against the IRS data strategy.

    • Infrastructure Executive Steering Committee (IESC) dispositions Data Collection Change Request (CR) if that required funding.

    • Change Initiator/Change Analyst enters Enterprise Life Cycle (ELC).

    • Change Initiator/Change Analyst submits ELC artifacts.

    • Solution Engineering Data Practice Group (Engineer/Analyst) reviews Data Collection processing outputs.

    • Solution Engineering Data Practice Group (Engineer/Analyst) aligns Project data model with Enterprise Logical Data Model (ELDM), and Standard Meta Model (Business Taxonomy and Technical Metadata).

    Step 2 Data Consolidation To manage data as follows: consolidate and condense disjointed data that can/should be homogenized and recognize which data is truly distinct so the relevant data is most easily identifiable and accessible.
     
    • Change Initiator/Analyst (Project Office) creates and submits Data Consolidation Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the scope of Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the data source, and evaluates the Change Request against the IRS data strategy.

    • Infrastructure Executive Steering Committee (IESC) dispositions Data Consolidation Change Request (CR) if that required funding.

    • Solution Engineering Data Practice Group (Engineer/Analyst) considers Change Request (CR) and determines the impact on the Data Warehouse environment.

    Step 3.0 Data Certification To certify that the designated sources, processes, and projects understand data quality, and govern the data assets.
     
    • Change Initiator/Analyst (Project Office) creates and submits Data Consolidation Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the scope of Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the data source, and evaluates the Change Request against the IRS data strategy.

    • Infrastructure Executive Steering Committee (IESC) dispositions Data Consolidation Change Request (CR) if that required funding.

    • Solution Engineering Data Practice Group (Engineer/Analyst) certifies data contents with an appropriate data Competency Center.

    • Solution Engineering Data Practice Group (Engineer/Analyst) assigns the responsibility of source data validation to Project Office/User.

    • Change Initiator/Analyst (Project Office/Change Requestor/User) conducts data profiling, implements data quality check, and develops balance & control and validation.

    Step 4.0 Data Connection To connect the data to each other as well as users to the data. Building out the metadata repository helps expose data element to the larger IRS audience
     
    • Change Initiator/Analyst (Project Office) creates and submits Data Consolidation Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the scope of Change Request (CR) or Work Request (WR).

    • Solution Engineering Data Practice Group (Engineering/Analyst) determines the data source, and evaluates the Change Request against the IRS data strategy.

    • Infrastructure Executive Steering Committee (IESC) dispositions Data Consolidation Change Request (CR) if that required funding.

    • Solution Engineering Data Practice Group (Engineer/Analyst) identifies interfaces.

    • Solution Engineering Data Practice Group (Engineer/Analyst) routes approved Change Request (CR) to appropriate data platform (e.g. Enterprise Informatica Platform (EIP) Integrated Services, BusinessObjects Enterprise (BOE)).

    Step 5.0 Data Consumption To consume data by presenting the data in the proper/desired state for the recipient to efficiently make the right decisions. This effectively turns data into information that then can be strategically used.
     
    • Change Initiator/Originator (Project Office) submits an OnLine 5081 request for accessing to the data system.

    • Project Office/User submits a Live Data Waiver request as required for users of SBU data.

    • OnLine 5081 Approval Group approves or denies the OnLine 5081 request.

    • Solution Engineering Data Practice Group (Engineer/Analyst) provides data environment for Change Initiator/Analyst (Project Office)to consume data.

    • Change Initiator/Analyst (Project Office) consumes data through queries and generating reports by using various data retrieval resources for data analysis.

Procedure

  1. Procedure

Step 1.0: Data Collection
  1. To Collect structured and unstructured data from across the agency and external to the agency. By leveraging the additional data captured with e-filing and modernized residual paper processing, more data can be shared for matching and targeting the best case. Data can be collected in forms of documents, records, models, emails, processes, RDBMS, business rules, or transaction systems. There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    Task1.1 Create and submit Change Request through KISAMhttps://kisamservice.web.irs.gov/webtier-9.52/index.do or Work Requesthttp://wrms.web.irs.gov/itg/dashboard/app/portal/PageView.jsp to Solution Engineering Front Door *IT Engineering Customer Support or *IT Engineering XML ChangeManagement to get Data Collection service

    The purpose of this process step is that Change Initiator/Analyst (Project Office) creates and submits Data Collection Change Request or Work Request to Solution Engineering Data Engineering Group
    Change Initiator/Analyst (Project Office) R Change Initiator/Analyst (Project Office) creates and submits Data Collection change request.
    Task 1.2 Determine scope and impact of Change Request or Work Request

    This task is to determine the scope and impact of Change Request or Work Request with respect to IRS Data Collection as related to the Enterprise Logical Data Model (ELDM)
    Solution Engineering/Data Engineering Group (Engineer /Analyst) R Ensure change or work request follows the Data Engineering Guidelines
    Task 1.3 Determine the data source, and evaluate the Change Request or Work Request against the IRS data strategy
    • Determine the authoritative data source

    • Determine data organization (OLTP/OLAP)

    • Determine feasibility of Data Collection Change Request (CR)

    • Evaluate Data Collection Change Request (CR) against IRS Data Strategy



    The purpose of this process step is to determine the authoritative data source, data organization (OLTP/OLAP), feasibility of Data Collection, and evaluate Data Collection CR against IRS Data Strategy
    Solution Engineering/Data Engineering Group (Engineer /Analyst) R The Solution Engineering Data Engineering Group is responsible for evaluating the change request against the IRS data strategy
    Task 1.4 Disposition Change Request or Work Request requiring funding

    Infrastructure Executive Steering Committee (IESC) disposition change request and ensure project has funding to support change request. Infrastructure Executive Steering Committee (IESC) approves or rejects CA (Project) CR request. Solution Engineering Data Practice Group returns rejected Change Request or Work Request back to Change Initiator/Analyst (Project Office) for further modification, or determines data source, feasibility and enforce IRS Data Strategy
    Infrastructure Executive Steering Committee (IESC)


    Solution Engineering/Data Engineering Group (Engineer /Analyst)
    A


    R
    Infrastructure Executive Steering Committee (IESC) reviews the change request, and determine to reject or approve the request


    Forward change or work request to Infrastructure Executive Steering Committee (IESC) for decision
    Task 1.5 Enter Enterprise Life Cycle (ELC)
    • Follow ELC Guidance

    • Advance through ELC and achieve Milestone Approval



    The purpose of this process step is that Change Initiator/Analyst (Project Office) enters Enterprise Life Cycle to manage and implement business change through system initiatives.
    Change Initiator/Change Analyst R Change Initiator/Change Analyst should be started (baseline) or updated at the corresponding Enterprise Life Cycle (ELC) Phase & Milestone
    Task 1.6 Submit ELC Artifacts
    • Entities & Attributes (Logical Data Model) Business Metadata (Business Taxonomy)



    Detail Design: Design Specification Report (DSR) (Physical Data Model/Technical Metadata)
    • Tables & Columns (Physical Data Model)

    • Technical Metadata (Technical Taxonomy) Interface Control Document (ICD) (Data Movement Metadata)

    • Schema; Service; Message Interchange Metadata (XML Taxonomy)



    Change Initiator/Analyst (Project Office) send a completed Data Management design with the applied version controlled. Primary Design: E300 and E53, Project Tailoring Plan, Project Management Plan, and Business System Requirement (BSR)
    Change Initiator/Change Analyst R Change Initiator/Change Analyst submits ELC artifacts to Solution Engineering Data Engineering Group(Engineer/Analyst)
    Task 1.7 Review Data Collection Processing Outputs - Primary Design: E300 and E53 Project Tailoring Plan, Project Management Plan, Business System Requirement (BSR)
    • Entities & Attributes (Logical Data Model)



    Business Metadata (Business Taxonomy) Detail Design: Design Specification Report (DSR) (Physical Data Model/Technical Metadata)
    • Tables & Columns (Physical Data Model)

    • Technical Metadata (Technical Taxonomy)



    Interface Control Document (ICD) (Data Movement Metadata)
    • Schema; Service; Message Interchange Metadata (XML Taxonomy)



    The purpose of this process step is to ensure that ELC artifacts including Data Collection Outputs for Solution Engineering review.
    Solution Engineering/Data Engineering Group (Engineer /Analyst) R Review the ELC artifacts which are submitted by Change Initiator/Change Analyst
    Task 1.8 Align Project’s data model with Enterprise Logical Data Model (ELDM), Standard Meta Model (Business Taxonomy and Technical metadata)
    • Collaborate with Change Initiator/Originator (Project Office)

    • Solution Engineering together with Project Office work to harmonize outputs until aligned with Enterprise Logical Data Model (ELDM)

    • Solution Engineering together with Project Office work to harmonize outputs until aligned with Standard Meta Model (Business Taxonomy and Technical metadata)

    • Determine if this Change Request or Work Request is only for this step or if there is a need to go to the next Data Consolidation step.



    The purpose of this process step is to ensure that the data model of Project Office aligned with Enterprise Logical Data Model (ELDM), Standard Meta Model (Taxonomy)
    Solution Engineering/Data Engineering Group (Engineer /Analyst)


    Change Initiator/Change Analyst
    R


    C
    Collaborate and work together with Change Initiator/Originator to harmonize the ELC requested artifacts


    Work with Solution Engineering/Data Engineering Group to harmonize ELC artifacts until align with Enterprise Logical Data Model, and Meta Model.

     

Cross-Functional Flow Diagram
  1. Data Collection Cross-Functional Flow Diagram

    Figure 2.152.2-2

    This is an Image: 59989002.gif
     

    Please click here for the text description of the image.

Step 2.0: Data Consolidation
  1. Data Consolidations: To manage data as follows: consolidate and condense disjoint data that can/should be homogenized and recognize which data is truly distinct to the relevant data is most easily identifiable and accessible. There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    Task 2.1 Create and submit Change Request through KISAMhttps://kisamservice.web.irs.gov/webtier-9.52/index.do or Work Requesthttp://wrms.web.irs.gov/itg/dashboard/app/portal/PageView.jsp to Solution Engineering Front Door *IT Engineering Customer Support or *IT Engineering XML ChangeManagement to get Data Consolidation
    service
    Determine if need to go to Data Collection step, if so, go to Data Collection Step


    The purpose of this task is Change Initiator/Analyst (Project Office) creates Data Consolidation Change Request or Work Request
    Change Initiator/Analyst (Project Office) R Change Initiator/Analyst (Project Office) creates and submits Data Consolidation Change Request or Work Request
    Task 2.2 Determine the scope of Change Request or Work Request
    • Determine before processing this step if the work needed includes the Data Collection Activity

    • Determine the scope and impact of Change Request or Work Request with the respect to IRS Data Consolidation as related to the Enterprise Logical Data Model (ELDM)

    Solution Engineering/Data Engineering Group (Engineer /Analyst) R Ensure change or work request follows the Data Engineering Guidelines
    Task 2.3 Determine the data source, and evaluate the Change Request against the IRS data strategy
    • Determine the authoritative data source

    • Determine data organization (OLTP/OLAP)

    • Determine feasibility of Data Collection Change Request (CR)

    • Evaluate Data Collection Change Request (CR) against IRS Data Strategy

    Solution Engineering/Data Engineering Group (Engineer /Analyst) R The Solution Engineering Data Engineering Group is responsible for evaluating the change request against the IRS data strategy
    Task 2.4 Disposition change request requiring funding.

    Infrastructure Executive Steering Committee (IESC) disposition change request and ensure project has funding to support change request
    Infrastructure Executive Steering Committee (IESC)


    Solution Engineering/Data Engineering Group (Engineer /Analyst)
    A


    R
    Infrastructure Executive Steering Committee (IESC) reviews the change request, and determine to reject or approve the request


    Forward change or work request to Infrastructure Executive Steering Committee (IESC) for decision
    Task 2.5 Consider the Data Consolidation Change Request or Work Request, and determine the impact on the data warehouse environment
    • Determine the impact on the data warehouse environment

    • Determine if this Change Request or Word Request is only for this step or if there is a need to go to the next Data Certification step

    Solution Engineering Data Practice Group (Engineer/Analyst) R Solution Engineering Data Practice Group (Engineer/Analyst) would consider the Change Request, and determine the impact on the data warehouse environment
Cross-Functional Flow Diagram
  1. Data Consolidation Cross-Functional Flow Diagram

    Figure 2.152.2-3

    This is an Image: 59989003.gif
     

    Please click here for the text description of the image.

Step 3.0: Data Certification
  1. Data Certification Certifies the designated sources, processes, projects and understand the data quality. The higher the quality of the data the Agency has, the more accurate scores can be produced. More accurate scores lead to more effective issue detection and case selection. Certification enables the governance of complete, consistent, comprehensible, correct, and authoritative sources by establishing operational metrics. There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    Task 3.1 Create and submit Change Request through KISAMhttps://kisamservice.web.irs.gov/webtier-9.52/index.do or Work Requesthttp://wrms.web.irs.gov/itg/dashboard/app/portal/PageView.jsp to Solution Engineering Front Door *IT Engineering Customer Support or *IT Engineering XML ChangeManagement to get Data Certification service

    Determine if need to go to Data Collection, or Data Consolidation Step, if so, go to each step


    The purposde of this task is Change Initiator/Analyst (Project Office) creates Data Certification Change Request or Work Request
    Change Initiator/Analyst (Project Office) R Change Initiator/Analyst (Project Office) creates and submits Data Certification Change Request or Work Request
    Task 3.2 Determine the scope of Change Request or Work Request
     
    • Determine, before processing this step, if other Data Management activities such as: Data Collection or/and Data Consolidation are needed.

    • Determine the scope and impact of Change Request or Work Request with the respect to IRS Data Certification as related to the Enterprise Logical Data Model (ELDM)

    Solution Engineering/Data Engineering Group (Engineer /Analyst) R Ensure change or work request follows the Data Engineering Guidelines
    Task 3.3 Determine the data source, and evaluate the Change Request against the IRS data strategy
    • Determine the authoritative data source

    • Determine data organization (OLTP/OLAP)

    • Determine feasibility of Data Certification Change Request (CR)

    • Evaluate Data Certification Change Request (CR) against IRS Data Strategy

    Solution Engineering/Data Engineering Group (Engineer /Analyst) R The Solution Engineering Data Engineering Group is responsible for evaluating the change request against the IRS data strategy
    Task 3.4 Disposition change request requiring funding.

    Infrastructure Executive Steering Committee (IESC) disposition Change Request or Work Request and ensure project has funding to support change request
    Infrastructure Executive Steering Committee (IESC)


    Solution Engineering/Data Engineering Group (Engineer /Analyst)
    A


    R
    Infrastructure Executive Steering Committee (IESC) reviews the change request, and determine to reject or approve the request


    Forward change or work request to Infrastructure Executive Steering Committee (IESC) for decision
    Task 3.5 Certify the data content with appropriate data Competency Center Based on data content, Solution Engineering Data Practice Group(Engineer/Analyst) would send to different Competency Center to validate Solution Engineering/Data Engineering Group (Engineer /Analyst) R Solution Engineering Practice Group (Engineer/Analyst) would certify data content to with competency center
    Task 3.6 Assign the responsibility of source data validation to the Project Office
    • send data validation back to Project Office

    • determine if this Change Request is only for this step or go to the next Data Management step(s)

    Solution Engineering/Data Engineering Group (Engineer /Analyst)



    Change Initiator/Change Analyst
    R



    I
    After certifying data content, Solution Engineering Data Practice Group (Engineer/Analyst) would assign the responsibility to project office



    Change Initiator/Change Analyst accepts the feedback from Solution Engineering Data Practice Group (Engineer/Analyst) that the data have been validated
    Task 3.7 Execute the following data validation:
    • Conduct data profiling

    • Implement data quality check

    • Develop balance &; control and validation

    Change Initiator/Change Analyst R After data validation, Change Initiator/Originator would do validation and quality check
Cross-Functional Flow Diagram
  1. Data Certification Cross-Functional Flow Diagram

    Figure 2.152.2-4

    This is an Image: 59989004.gif
     

    Please click here for the text description of the image.

Step 4.0: Data Connection
  1. Data Connection: Connect the data to each other as well as users to the data. Building out the metadata repository helps expose data elements to a larger audience. Increasing data accessibility across the agency helps to gain the ability to measure ROI and compliance impact across the end to end process. There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    Task 4.1 Create and submit Change Request through KISAMhttps://kisamservice.web.irs.gov/webtier-9.52/index.do or Work Requesthttp://wrms.web.irs.gov/itg/dashboard/app/portal/PageView.jsp to Solution Engineering Front Door *IT Engineering Customer Support or *IT Engineering XML ChangeManagement to get Data Connection service

    Determine if need to do Data Collection, or Data Consolidation, or Data Certification Step, if so, go to each step


    The purpose of this task is Change Initiator/Analyst (Project Office) creates Data Connection Change Request or Work Request
    Change Initiator/Analyst (Project Office) R Change Initiator/Analyst (Project Office) creates and submits Data Connection Change Request or Work Request
    Task 4.2 Determine the scope of Change Request or Work Request
    • Determine the scope and impact of Change Request or Work Request with the respect to IRS Data Consolidation as related to the Enterprise Logical Data Model (ELDM)

    .


    This task is to determine the scope and impact of Change Request with respect to IRS Data Connection as related to the Enterprise Logical Data Model (ELDM)
    Solution Engineering/Data Engineering Group (Engineer /Analyst) R Ensure change or work request follows the Data Engineering Guidelines
    Task 4.3 Determine the data source, and evaluate the Change Request against the IRS data strategy
    • Determine the authoritative data source

    • Determine data organization (OLTP/OLAP)

    • Determine feasibility of Data Certification Change Request (CR)

    • Evaluate Data Certification Change Request (CR) against IRS Data Strategy

    Solution Engineering/Data Engineering Group (Engineer /Analyst) R The Solution Engineering Data Engineering Group is responsible for evaluating the change request against the IRS data strategy
    Task 4.4 Disposition change request requiring funding.

    Infrastructure Executive Steering Committee (IESC) disposition change request and ensure project has funding to support change request
    Infrastructure Executive Steering Committee (IESC)


    Solution Engineering/Data Engineering Group (Engineer /Analyst)
    A


    R
    Infrastructure Executive Steering Committee (IESC) reviews the change request, and determine to reject or approve the request


    Forward change or work request to Infrastructure Executive Steering Committee (IESC) for decision
    Task 4.5 Identify Interface Solution Engineering Data Practice Group (Engineer/Analyst) R Solution Engineering Data Practice Group (Engineer/Analyst) identifies Interface
    Task 4.6 Route approved Change Request or Work Request to appropriate data platforms (e.g. Enterprise Informatica
    • Provide Computer Operator Handbooks (COH) for data platforms

    • Evaluate schema certification metrics using Standard Data Names (Business, Physical & XML Platform)

    • Determine if this Change Request or Work Request is only for this step or go to the next step

    Solution Engineering Data Practice Group (Engineer/Analyst) R Solution Engineering Data Practice Group (Engineer/Analyst) routes approved Change Request to appropriate data platforms
Cross-Functional Flow Diagram
  1. Data Connection Cross-Functional Flow Diagram

    Figure 2.152.2-5

    This is an Image: 59989005.gif
     

    Please click here for the text description of the image.

Step 5.0: Data Consumption
  1. Data Consumption: Present the data in the proper/desired state for the recipient to efficiently make the right decision. Data is effectively turned into information, used to innovate new methods/discoveries, streamline and automate retrieval processes through renovations, and intent individuals through motivation. Tools of data consumption focus on visual representations of dashboards, scorecards, queries, reporting tools, OLAP, or data mining. There can only be 1 Role that is Responsible for a Task.

    ID Task Name and Description Role RACI Duties
    Task 5.1 Submit an OnLine 5081 request for access to the data system Change Initiator/Change Analyst R Change Initiator/Change Analyst submit an OnLine 5081 request for access to the data system
    Task 5.2 Submit a Live Data Waiver request as required for users of SBU data Change Initiator/Change Analyst R Change Initiator/Change Analyst submit a Live Data Waiver request as required for users of SBU data
    Task 5.3 Approve or deny the OnLine 5081 request. If deny, end step; otherwise, if Data Collection required, go to Data Collection ; otherwise, if Data Consolidation required, go to Data Consolidation; otherwise, if Data Certification required, go to Data Certification; otherwise if Data Connection Required, go to Data Connection OnLine 5081 System Administrator or Manager R OnLine 5081 System Administrator or Manager dispositions OnLine 5081 request
    Task 5.4 Provide data environment for Project/User to consume data Solution Engineering Data Practice Group (Engineer/Analyst) R Solution Engineering Data Practice Group (Engineer/Analyst) provides data consumption environment
    Task 5.5 Consume data through queries and generating reports by using various data retrieval resources for data analytic Change Initiator/Change Analyst R Consume data through queries
Cross-Functional Flow Diagram
  1. Data Consumption Cross-Functional Flow Diagram

    Figure 2.152.2-6

    This is an Image: 59989006.gif
     

    Please click here for the text description of the image.