2.120.1 Engineering Policy

Manual Transmittal

July 23, 2020

Purpose

(1) This transmits revised IRM 2.120.1 Engineering, Policy Statements.

Material Changes

(1) The Engineering Policy has been updated to include the updated list of mandated processes as follows:

  • IRM 2.120.1.1.3 Replaced “Completion of Engineering Plan” with “Engineering Planning Process”.

  • IRM 2.120.1.1.3 Replaced “Technical Solution process” with “Solution Design process”.

  • IRM 2.120.1.1.3 Deleted “Product Integration process” per obsoleted IRM.

  • IRM 2.120.1.1.3 Deleted “Design Coordination process” per obsoleted IRM.

  • IRM 2.120.1.1.3 Deleted “Performance Engineering process” per obsoleted IRM.

  • IRM 2.120.1.1.3 Added “Hardware Analysis and Design/System Configuration Validation process”.

  • IRM 2.120.1.1.3 Added “Data Management process”.

  • IRM 2.120.1.1.3 Added “Naming Data Elements process”.

  • IRM 2.120.1.1.3 Added “Interface Design process”.

  • IRM 2.120.1.1.3 Added “Engineering ELC (Enterprise Life Cycle) Documentation process”.

Effect on Other Documents

This supersedes IRM 2.120.1, dated November 05, 2019.

Audience

This Policy is applicable to all Information Technology (IT) Application and Infrastructure projects, contractors, and other stakeholders having responsibility for developing IT Processes.

Effective Date

(07-23-2020)


Nancy Sieger
Acting Chief Information Officer

Program Scope and Objectives

  1. Overview - This policy is to establish the organizational policy for planning and performing the Engineering Process for the development and integration of information technology based systems within the IRS environment.

  2. Purpose - The purpose of this policy is to ensure an enterprise-wide Engineering processes for the development and integration of information technology-based system within the IRS.

  3. Audience - This policy is applicable to all Information Technology (IT) organizations, contractors, and other stakeholders having responsibility for developing IT systems.

  4. Policy Owner - Enterprise Services (ES) Associate Chief Information Officer (ACIO) is responsible for overseeing all aspects of our systems that operate the nation’s tax infrastructure.

  5. Program Owner - Solution Engineering (SE), which is under Information Technology, Enterprise Services (ES).

  6. Primary Stakeholders - Application Development (AD), Cybersecurity, Enterprise Operations (EOps), Solution Engineering (SE), Enterprise Architecture (EA), User and Network Services (UNS)

  7. Program Goals - This IRM has been created to ensure an enterprise-wide approach to the development and integration of information technology-based system within the IRS.

Background

  1. The list of mandated processes are updated.

Purpose
  1. The purpose of this policy is to establish the organizational policy for planning and performing the Engineering processes for the development and integration of information technology based systems within the IRS environment.

Scope
  1. All Information Technology (IT) projects are required to perform the Engineering Process and associated activities in accordance with this policy.

Authority

  1. Enterprise Services is responsible for the development, implementation, and maintenance, of this policy. Approval of this policy, including updates, rests with the Solution Engineering of Enterprise Services. All proposed changes to this policy must be submitted to Enterprise Services.

Mandate

  1. Applicability
    All IT projects will follow the Engineering Planning (EP), Solution Design (SD), Hardware Analysis and Design/System Configuration Validation (HAD/SCV), Data Management (DM), Naming Data Elements, and Interface Design (ID) Processes ensuring all work products defined by those processes are produced.

  2. Engineering Planning process
    The Engineering Planning Process outlines what Engineering related work needs to be specified in the Engineering Plan.

  3. Solution Design process
    The Solution Design process shall be used to select and design solution, solution components to the requirements, and to perform the integration of system components into complete solutions.

  4. Hardware Analysis and Design/System Configuration Validation process
    The process analyzes and translates requirements into a Physical design and then uses that to generate a Government Equipment List – which is a list of hardware and software components and configuration attributes necessary to fulfill the project requirements.

  5. Data Management process
    Data Management is one of the major processes of Data Engineering. Data Management includes 5 core components which are Collect, Consolidate, Certify, Connect, and Consume. These 5 C's are the cornerstone of Data Management.

  6. Naming Data Element(s)/Object(s) process
    The goal of Naming Data Element(s)/Object(s) process is to support the business goal for data naming standardization by ensuring that the "Enterprise Data Standards and Guidelines (EDSG)" are followed service wide. Naming Data Element(s)/Object(s) will be divided into parts: one is Naming Business Data Element(s)/Object(s), and the other is Naming Technical Data Element(s)/Object(s).

  7. Interface Design process
    The Interface Design defines an agreement on conditions and responsibilities at the boundary point, and second by providing a unifying, end-to-end view of the interface process.

  8. Engineering ELC (Enterprise Life Cycle) Documentation process
    The process that documents, reviews, and approves the ELC Engineering documents – Engineering Plan, Simplified Design Specification Report, Interface Control Document(s), and Government Equipment List.