I_1_b PWS.pdf

General Common Enterprise Services (CES) and Technical and Program Support Services

Performance Work Statement (PWS)

Technology Strategy Management (TSM)

Enterprise Services (ES)

Internal Revenue Service (IRS)

January2025

4. INTRODUCTION AND BACKGROUND

TSM is a division in the ES organization of the IRS. It is responsible for strengthening technology infrastructure across the enterprise. The ES team accomplishes this by defining the current and target enterprise architectures and developing a transition strategy to move the agency towards the target environment. ES is focused on technology strategy management, architecture, solution engineering and system testing. ES sets enterprise technology direction by translating business priorities into an effective enterprise technical framework, setting architecture guidance, and establishing technology standards. The ES organization actively works with IRS business units and information technology (IT) suppliers to collaboratively define and institutionalize the enterprise level processes and standards needed to successfully deliver IT solutions and to comply with cross - cutting internal and external IT mandates and requests.

The Contractor shall provide integration and governance, technical expertise, conduct analysis / assessments, provide recommendations, guidance, identify and / or deliver technical accelerators and enablers in the areas of business and platform common services. This includes architecture, engineering, security, technical advisory, strategic planning, design, development, program and project management, One Solution Delivery Lifecycle (OneSDLC) support, Cost Model delivery and implementation guidance and support to the CES Program.

4.0 Key Federal Drivers Influencing General Common Enterprise Services (CES) and Technical and Program Support Services

Policy and Guidance Drivers Description IRS Publication 1075 Because of the diverse purposes that authorized disclosures may be made to an agency and the division of responsibilities among different components of an agency, Federal Taxpayer Information (FTI) may be received and used by several quasi -independent units within the agency’s organizational structure. Where there is such a dispersal of FTI, the agency must centralize safeguarding responsibilities to the greatest extent practical and establish and maintain uniform safeguard standards consistent with IRS guidelines

IRS Strategic Plan FY21 - 26 Strategy 4.1.2: Streamline processes through more efficient governance, procurement, and collaboration.

Strategy 4.2.2: Enhance operational agility by adopting advanced technologies and leveraging common platforms across business

IRS Integrated Modernization Business Plan (IT Mod Plan)

We will improve operational efficiencies by reducing system complexities, and increasing standardization across the enterprise

Treasury Directive 81-01 (5.B.5) To help ensure interoperability both within and external to Treasury, to maintain the security of Treasury’s IT platforms, and to best enable future transitions to centralized shared services, the Deputy Assistant Secretary for Information Systems (DASIS) shall identify and develop standards for Treasury - wide adoption

Treasury Executive Office of Asset Forfeiture FY 21 Publication (fiscal 13)

The data strategy also promotes interoperability among data sources, helps to reduce duplication, build common and shared solutions, and improve data quality

National Institute of Standards Technology (NIST). The NIST Design Repository Project Publication, p. 2

As design becomes increasingly knowledge - intensive and collaborative, the need for computational design frameworks to support the representation and use of knowledge among distributed designers becomes more critical. In addition to sharing and exchanging information, pressure to reduce product development times has resulted in an increased focus on methods for representing and storing engineering artifact knowledge in a way that facilitates its retrieval and subsequent reuse

Government Accountability Office (GAO) Highlights, January 2023

Provide a modernized and unified human capital experience that is expected to provide the IRS workforce with a single interface for operational support services;

and consolidate processes and workflows to reduce redundancies and eliminate manual entry

Figure1-1 Policy and Guidance Drivers

1.2 General Common Enterprise Services (CES) and Technical and Program Support Services Program ES defines how an enterprise - wide data environment will organize, identify, share, reuse, and correlate data. ES provides architecture and engineering, development services that promote standards - based, enterprise solutions, partnering with customers to improve the quality of information systems, products, and services. Common Services is of the central pillars for achieving the modernization of IRS systems and achieving the target state holistic architecture.

CES will enable a loosely coupled modular architecture, promote standardized access to data, and define shared reusable services that will be leveraged across the enterprise. Successful implementation of Common Services will provide enterprise operational efficiencies and unlock future innovation at the IRS.

The Inflation Reduction Act (IRA) outlines the primary source of funding for the CES to support the modernization of IRS systems and taxpayer services. As part of the IRS’ Strategic Operating Plan (SOP), the IRS has identified modernizing IT operations as one of the key components to deliver on modernization. To meet this goal, IRS is developing standardized, agile solutions that leverage emerging technologies, while decommissioning and replacing legacy systems. CES is an integral component of this effort.

The CES will enable IT to transition IRS data, applications, and services to leverage loosely coupled, reusable services that will reduce fixed investment, minimize the risks of aging hardware, and improve scalability and elasticity, and support long - term and emergent business requirements for enterprise IT orchestration and service management.

1.3 Technology Strategy Management Office Support

TSM provides executive leadership in shaping and implementing the overall IT agency strategy while identifying high - return technological investments for potential use within IRS. The TSM organization plays a unique, differentiated role in IT and promote integration management as a function that helps translate strategies to the execution level. The TSM Program Management Office (PMO) operates as a “prime integrator” of IT delivery partners in the organization across the enterprise. TSM is comprised of five (5) groups and three (3) Sub - groups: Enterprise Infrastructure Currency (EIC), Infrastructure Platform Strategy and Services (IPSS), Large

Program Implementation Services (LPIS), Managed Technology Shared Services (MTSS) and Common Services & Integration (CS&I).

The General CES and Technical and Program Support Services Program is a high visibility program that is directed by IRS IT-CIO, IT-ES-Associate Chief Information Officer (ACIO) and IT-ES-TSM Director. The PMO reports daily to the ES-TSM Director, weekly to the ES-ACIO and monthly to the IRS’ Chief Information Officer (CIO) on the progress of the program. The program strategy needs to be agile to support the rapid needs of program deliveries.

4.4 Executive Board

The Enterprise Services Governance Board (ESGB) will be chartered to govern and approve the Program milestone exits and approving the Integrated Master Schedule (IMS) to baseline IMS.

2.0 OBJECTIVES

The IRS requires support to enable the delivery of enterprise - wide IT services. These services include the below key areas:

• Enterprise Architecture Design & Modernization Solutions

• Application Development

• CES Portfolio Management

• Technical assessment, planning, and execution

• System configuration, monitoring, and deployment

• Program management and training

• Deliver OneSDLC artifacts for the program

• Stakeholder and Communication Management

• Operational Support for maintaining / configuring CES owned platforms (ECP, EKS)

• Platform Setup, Platform Health Checks (ECP, EKS)

• Platform Financial Analysis

• Onboarding Support

• Technical Integration

• White Papers and Points of View (POVs) as needed.

Outlined below are the systems, architecture, processes, and software critical to the work required under the PWS. The Contractor shall provide highly qualified personnel with the capability, experience, and understanding of the below elements essential to this work. The personnel supporting this effort are expected to be subject matter experts (SMEs) in the capabilities IRS seeks to achieve and maintain and be prepared to deliver services and deliverables that meet or exceed acceptable quality levels (AQLs) outlined within this PWS and the attached Quality Assurance Surveillance Plan (QASP).

• Redhat Linux and Windows Operating Systems

• Customer Relationship Management (CRM) Tools (e.g., ServiceNow)

• Engineering Lifecycle Management (ELM) Requirements Management (RM) tools / applications (e.g., Doors Next)

• Open-Source Stack such as Apache Foundation, Java Script, Node.JS, Angular, Graph DB, Elastic Search, Hadoop etc.

• Java, Python, C, REST, JavaScript Object Notation (JSON), XML, YAML

• Oracle, SQL, SQL Server, Greenplum Databases; OLTP, OLAP, MPP Database Technologies, GraphQL, Springboot, NoSQL (e.g., MongoDB), Snowflake, Databricks and PostGreSQL Databases

• GitHub, Gitlab, Openshift.

• Big Data Analytics and Machine Learning technologies such as R, SAS, Tableau

• Application Programming Interface (API) Platform Integration (e.g., Software AG webMethods).

• Event Driven Architecture (SQS / SNS, Kafka & similar), API Gateway, catalog and specifications, Microservices Adoption, containerization (Kubernetes, Docker, or similar), etc.

• Build Automation Tools such as Maven and Gradle

• Familiar with Zero trust architecture or security model

• Agile Scrum Methodology

• Project and Program Management Methodologies

• Microsoft Office Products to include Project and PowerPoint

• Primavera Portfolio Management (Prosight)

• Jira

• Service Mesh (ISTIO)

• Data Model, Data Architecture, OneSDLC and process pipeline, Performance Tuning, software

/ applications (Informatica, BOE, Tableau, Greenplum etc.)

• DevSecOps, automated testing, and integration with security systems

• Cloud environments such as Azure Cloud, Google Cloud, Amazon Web Services (AWS) EC2, AWS EKS, and cloud native languages (LAMDA, etc.)

• Familiarity with Enterprise Architecture framework and / or methodology

The period of performance of this Task Order (TO) shall be for one base year only from the date of award.

The IRS enterprise application systems reside on - premises and the cloud. On - premises applications are required to move to the cloud in the future.

3.0 SCOPE OF WORK AND DESCRIPTION OF OVERARCHING TASKS

The Contractor shall support the planning and execution of the IRS CES Technical Integration and Governance, as well as Architecture, Engineering, Development, and Implementation projects, while efficiently managing cross program dependencies. Accomplishing this will require executive level engagement from the Contractor and frequent and direct collaboration with ES leadership.

The Contractor shall coordinate with IRS employees and other contractor’s resources on the following tasks:

3.1 Task Area 1. Program Management Support

Program Management is a subset of Portfolio Management that is aligned to business goals.

Therefore, all Contractor effort should align to higher level business goals (i.e., support Portfolio Management objectives). Program Management is aligned to strategic objectives with a focus on multiple projects, resources, and capacity. The Contractor shall provide necessary program management and administrative support to carry out the objectives of the TO successfully, provide periodic executive briefings, meeting minutes, quad charts, work requests, report the progress on key metrics, and manage time and resources for timely and cost - effective deliverables.

The Contractor shall provide and maintain program management expertise and shall use proven and mature program management practices and processes to effectively manage resources to meet the delivery expectations on time and budget while executing IRS General CES and Technical and Program Support Services. The Contractor shall support each program workstream with project planning and management, milestone status tracking and reviews, risk, and issue identification, tracking and resolution and participation in program and release level activities. Program support shall align with the IRS - selected OneSDLC development path, methodology, and delivery approach.

Program Management support shall include the following but not limited to:

• Obtain Platform Software / Platform as a Service (PaaS) licenses to be consumed as "Pay - As

- You - Go" mode.

• Develop and update and maintain project management plan, risk management plan, issues tracker, communication plans, maintain processes and operating procedures and Contingency Management as required.

• Record and communicate dependencies, constraints, risks, impediments to program leadership in a timely manner and track them to either resolution or mitigation.

• Support project and program planning and tailoring to refine application of paths, methodologies, and approaches to fit program needs.

• Provide coaching support to assist in IRS adoption and execution of incremental development and delivery approaches including, Agile and DevOps.

• Draft, review, and update project and program management documentation in accordance with IRS guidelines.

• Develop and maintain to include IMS, quad charts, road maps, automation strategy, automation SOP, lessons learned and executive briefs.

• Monitor, track, review, and update project status, and provide analysis to ensure that all impacts are identified early in the project planning.

• Develop and maintain a configurable set of project guidance, documents, and plans to be tailored to each program.

• Facilitate lessons learned reviews with continuous development, documentation, communication, and application of lessons learned.

• Provide necessary project management and admin support to carry out objectives of the TO successfully.

• Create executive material and provide weekly and on - demand executive briefings, report progress on key metrics, deliver documents in timely manner and record documents at the IRS specified repository.

• Identify, record and address program risks, issues, concerns, and action items according to IRS standards and Internal Revenue Manual (IRM).

• Facilitate and support demo sessions, meetings and working sessions with leaderships, and stakeholders to include road map, Integrated Master Schedule (IMS), Implementation Plan, automation, integration, testing, risk, issues, concerns, and executive briefs.

• Coordinate with program stakeholders to include Enterprise Operations (EOps, Applications Development (AD) and Cyber to conduct program management activities.

• Respond to work request(s) issued under this contract to address unforeseen circumstances, as needed for the program to achieve its stated goals and objectives.

• Review and validate all analysis and recommendations with stakeholders and incorporate review feedback, where applicable, in the final recommendations to the Government across all tasks. The Contractor shall fully substantiate the recommendations / solutions proposed with any required ancillary materials. All feedback from stakeholders will be included with the recommendations.

• Where applicable, the Contractor shall, through the program leadership, make recommendations, design, develop, document, implement recommended solutions and best practices that have been reviewed and accepted by the Government. The Contractor shall not implement any solution until Government approval has been obtained in writing.

Desired Outcome: Development and application of program management practices and controls that allow the program to effectively establish and maintain control of program status, execution, risks, costs, and schedule. The Contractor shall obtain Authorization to Operate (ATO) for the Platform and implement all the IRS compliance requirements to obtain the ATO including Cybersecurity requirements of System Security Packages, Enterprise Security Audit Trails, 508 approvals, Privacy approvals, Network Connectivity, One SDLC and all necessary Cyber and IRS controls.

3.2 Task Area 2. Project Management Support

Project Management is a subset of Program Management and is aligned to delivery of a tool / product / service with a focus on scope, schedules, and cost management. The Contractor shall provide necessary project management and administrative support to carry out the objectives of the TO successfully, provide periodic executive briefings, meeting minutes, quad charts, work requests, report the progress on key metrics, and manage time and resources for timely and cost -effective deliverables. The objective of this task area is to establish and maintain an Agile PMO framework that supports the successful implementation and execution of Agile methodologies across all projects within the program. The goal is to use agile methods to demonstrate incremental delivery, governance, risk management, communication, and collaboration.

The Contractor shall support the project with project planning and management, milestone status monitoring and reviews, risk and issue identification, tracking, and resolution, in addition to participation in program and release level activities.

Project Management support shall include the following but not limited to:

• Develop and record the schedule for deliverables and activities.

• Conduct and facilitate meetings, workshops, architecture design sessions, provide timely meeting minutes, and capture action items.

• Provide project planning and management, milestone schedule and status tracking, and reviews.

• Participate in program and release level activities.

• Provide coaching support to assist in IRS adoption and execution of incremental development and delivery approaches including, but not limited to, Agile and DevOps.

• Produce weekly, monthly, and ad hoc reports on the progress and status of the effort:

o Monthly Status Reports (MSRs) are due no later than the seventh (7th) calendar day of the new work month. The IRS and the Contractor shall agree to a format within 14 federal Government business days of award of the TO. All electronic submissions of the monthly status reports shall be provided using Microsoft Office products in accordance with Section 508 compliance requirements. The IRS anticipates no more than two (2) ad hoc reports will be requested during the period of performance.

o The Contractor shall coordinate monthly meetings with the Government Task Lead (GTL), to be fulfilled by a conference call. The Contractor shall be prepared to present the MSR which shall be shared with all meeting attendees at least three (3) federal Government business days prior to the meeting.

o The Contractor shall provide the IRS detailed monthly invoices for the services being billed in the prior period. At a minimum, the invoice report must detail: Dollar amount billed to the IRS by Contract Line - Item Number (CLIN), task, labor category (LCAT), and service incident, and the dollar amount exercised versus overall TO period total amount obligated.

• Provide periodic executive / stakeholder briefings on progress.

• Facilitate buy - in from executives.

• Conduct bi - weekly integrated project team (IPT) meetings, weekly action items, IMS, stakeholder coordination, quad chart reviews, and internal and external risk forums.

• Coordinate with program stakeholders to include EOps, AD, and Cyber to conduct project management activities.

• Store and maintain developed or updated documents on the IRS CES and Technical and

Program Support Services SharePoint site.

• Kick - Off / Orientation Briefing Within fourteen (14) calendar days following task order (TO) award, the Contractor shall conduct a kick - off / orientation briefing for the Government. The Government does not desire an elaborate kick - off / orientation briefing, nor does it expect the Contractor to expend significant resources in preparation for this briefing. Rather, the intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key TO participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of TO requirements and objectives. The kick - off / orientation briefing shall be held at the Government's facility or virtually and both parties shall mutually agree upon the date and time.

The completion of this briefing shall result in the following:

o The Contractor and Government personnel who will perform work under this TO will be introduced.

o The Contractor shall demonstrate confirmation of their understanding of the work to be accomplished under this PWS.

o The Government will address any issues concerning Contractor clearances and Government Furnished Property (GFP) and Government Furnished Information (GFI) requirements for Contractor personnel.

o The Government and Contractor will agree on the work that can be performed until all revalidations and clearances are completed.

The Contractor shall provide the Government all material to be presented at the orientation briefing. This includes any PowerPoint slides, handouts, and any ancillary support materials.

The draft of materials is due no later than two (2) federal Government business days prior to the planned briefing. The Contractor shall take meeting minutes for the orientation briefing.

Desired Outcome:

The Contractor shall initiate the communication process between the Government and Contractor to assure a common understanding of award requirements and objectives and provide the following deliverables:

• The Contractor shall provide a variety of IT Project and Program Management Support to ensure that applicable complex projects are managed in accordance with IT and Institutional Infrastructure Program and Project Management Requirements. This required support includes, but is not limited to, providing interpretation of NPR 7120.7 requirements, creating project documentation, reviewing, and analyzing documentation, preparing reports, supporting various reviews and decision points, project tracking and scheduling, and portfolio management.

• Enterprise Dependency Management The Contractor shall manage cross program dependencies through tracking of on -time delivery of Common Services (e.g., IMS).

Deliverable Frequency / Due Date Technical POC / Reviewer

Orientation Briefing Materials No Later Than (NLT) two (2) federal Government business days prior to the planned briefing.

Government Program Manager (GPM), Contracting Officer’s Representative (COR), and / or other identified Government officials.

Meeting minutes Two (2) federal Government business days following the meeting.

GPM, COR, and / or other identified Government official

Quality Control Plan (QCP) Within sixty (60) calendar days of Orientation briefing.

COR

Deliverable Frequency / Due Date Technical POC / Reviewer

Update IMS Tracking System

Weekly Designated GTL and / or

GPM

• Common Services Delivery Model o The Contractor shall define, implement, and manage enterprise delivery framework to deliver extensive and complex set of common services, fostering collaboration and promoting reuse.

o The Contractor shall implement Operating Model to coordinate with IT Executive lead, Domain Leads, and programs / initiatives to manage and deliver the vision for enterprise common services.

Deliverable Frequency Technical POC / Reviewer

Bi - Weekly QUAD Chart Reporting Bi - Weekly Designated GTL and / or GPM

• Reporting and Communications. The Contractor shall:

o Provide periodic executive briefings, reporting progress on key metrics, Transformation and Strategy Office (TSO) / Strategic Implementation Management System (SIMs) reporting, managing resources and time for timely, cost - effective deliverables.

o Identify the communication approaches, vehicles and frequencies and tailor content for different types of audiences.

o Through white papers, briefings, POVs, inform IRS IT Leadership of CES efforts, and co-developed with input / guidance across all IRS Associate / ACIO areas as applicable.

o Stay abreast of all technology roadmaps internal and external to the IRS and align within the CES holistic architecture and platform design authority efforts.

Deliverable Frequency Technical POC / Reviewer

Executive Briefings

Weekly Designated GTL and / or GPM

White Papers, Point of Views Periodically Designated GTL and / or GPM

• IT Program Coordination The Contractor shall enable cross domain collaboration of processes and resources to break down development silos and ensure alignment with the Holistic Architecture vision and eliminate duplication of services.

• Platform Financial Analysis The Contractor shall collect and analyze CES platform usage, track and monitor the operational cost using any existing model(s), build a new model if necessary or modify existing model. The Contractor shall also monitor the license usage and requirements This could involve coordinating with different groups internal and external to the IRS to collect the required data and information.

Also, the Contractor shall document the usage of the Model and future updates required as the CES tenant base increases.

Bi - Weekly Status Reporting Bi - Weekly Designated GTL and / or GPM

• Overarching Status Reports The Contractor shall be responsible for ensuring the visibility of all work being completed under this requirement and the quality of all services and deliverables. This will be accomplished through the submission of various reports and data outlined within the PWS, and the Government verification that all services and deliverables meet contractual standards through scheduled and unscheduled quality assurance surveillance as further defined in the Government’s QASP.

• Automated Data / Report Access In addition to the reports and data delivered under various tasks of the PWS, the Contractor shall provide a real-time data / report solution for Government use. The solution shall allow the Government to export data, reports, as well as project schedules. The Contractor shall maintain the solution (e.g., dashboard, portal, etc.) throughout the lifetime of the TO and shall be responsible for the accuracy and currency of all data.

Data / Report Solution:

Automated solution allowing Government access

An initial solution recommendation shall be provided NLT sixty (60) calendar days following contract award.

A final functional solution shall be in place no later than ten (10) calendar days following any Government review feedback.

Designated GTL and / or GPM

• Weekly Manning Roster. The Government is required to track the security status of all Contractor personnel throughout the life of the TO. To facilitate this Government security requirement, the Contractor shall submit a weekly roster of personnel assigned to the TO. The team roster shall identify all personnel supporting the TO, including their on - boarding status, investigation status (interim / final), GFE barcodes, and any requests for GFE / Government Furnished Information (GFI) / applications. All requests for new applications made through the Business Entitlement Access Request System (BEARS) / IRWorks systems must be approved by the PM via email before the request is input into the appropriate system. Requests that are not preapproved will be denied by the COR.

Manning Report: Manning roster for Contractor personnel supporting services

Weekly by first (1st) federal business day of each week.

Designated GTL and / or GPM

• MSR. The Contractor shall deliver MSRs outlining the progress of services against TO standards and AQLs. These reports shall consolidate information provided under several areas of the PWS into a single distinct deliverable that captures monthly progress by reporting status against outcomes against project schedule expectations. MSRs shall describe the accomplishments for the month (activities and deliverables). The MSR is separate from any report substantiating costs and Invoice Processing Platform (IPP) invoicing. The MSR shall be submitted no later than the fifth (5th) federal business day of each month.

Progress Report: Monthly progress summary

Monthly by the fifth (5th) federal Government business day of each month.

Designated GTL and / or GPM

• Scheduled Meetings. The Contractor shall meet with the IRS twice a month to discuss the progress of existing and planned work. The Contractor shall show an updated MS Project Schedule and discuss any risks or concerns at this time. The Contractor shall identify any schedule and / or performance risks and any mitigation plans, as applicable, to reduce any identified risks. The Contractor shall take notes during each scheduled meeting and transmit the meeting minutes to the Government no later than the following federal business day.

Deliverable Frequency / Due Date Technical POC / Reviewer

Schedule: MS Project Schedule Submitted twice a month, due NLT than two (2) hours prior to the scheduled meeting.

Designated GTL and / or

GPM

Minutes: Post - meeting minutes containing list of attendees, topics of discussion, and any due outs identified

Submitted no later than the first (1st) federal business day following the meeting.

Designated GTL and / or

GPM

• Assessment and Recommendation Report

The Contractor shall provide a consolidated assessment report that captures analysis findings and recommendations as outlined in the PWS. The report format and organization shall be finalized following the initial kickoff meeting.

Report: Consolidated analysis and recommendations

Submitted twice a month, due NLT than two (2) hours prior to the scheduled meeting.

Designated GTL and / or

3.3 Task Area 3. Operational Support

The Contractor shall provide necessary support to develop, configure, upgrade, automate, and maintain all system components that impact a successful functionality of the Program. The Contractor shall support receiving software / hardware appliances in the IRS facilities to include Memphis and Martinsburg; design, install, configure, upgrade, automate, maintain, and transition the system and tools, software / hardware appliances, and conduct any operational support required to assist the Program. The Contractor shall coordinate and assist EOps by providing operational support.

Operational Support shall include the following but not limited to:

• Capture and analyze the business, functional and technical requirements for:

o The Document AI use case and how they will be deployed on Cloud Platform.

o Standard Looker analytics dashboard to analyze performance.

• Create a Feature List consisting of documented User Stories collected during the business process workshops into a project management tool (e.g. Asana).

• Design cloud infrastructure components for alignment with advanced security features.

• Develop an initial draft of the Technical Design Document (TDD) that includes the proposed solution design including:

o Security and Authentication o Technical architecture o Personas o Entity Relationship Diagrams o Workflow Components

• Develop a test plan that includes functional and failover tests for in - scope components including:

o Scenario based testing o Load testing o Functional testing o Malicious case testing

• Manually identifying metadata to be extracted from documents and building bounding boxes which will enable the model for training.

o Develop solution to annotate key - value pairs.

• Develop Cybersecurity artifacts (IE System Security Plan and diagrams)

• Provide, maintain, and upgrade all cloud - hosted hardware, infrastructure, and appliances necessary for delivery of capabilities in accordance with all applicable IRS and Federal policies, guidelines, and directives.

• Common Enterprise Services Architecture, Engineering Implementation Support

Analysis and Recommendations Continuous Integration / Continuous Delivery (eCI / CD) based on DevSecOps best practices that aligns and complies with the enterprise eCI / CD requirements, monitoring, logging, and analytics).

The Contractor shall provide recommendations for logging and monitoring configurations and analytic processes. The recommendations should outline at a minimum the below elements.

All logs will comply with existing Enterprise Security Audit Trails (ESAT) and archive requirements:

o AWS logs recommendations (CloudWatch & CloudTrail logs) and how to monitor service effectively and accurately, capture / store API activity, and any audit changes.

o Tools to be utilized. The priority of tool selection should be for existing ES tools outlined under Attachment A – ES Existing Tools (if applicable).

o ESAT Logs (e.g., Splunk) The initial analysis and recommendations shall be submitted as part of the consolidated analysis and recommendation report. This information shall be submitted within forty - five

(45) days of TO award, or forty - five (45) days following MBI clearance, whichever is later.

The Contractor shall monthly reevaluate the initial recommendations and solutions and submit any additional recommendations for additions and / or changes with the monthly status report.

Assessment Report:

See consolidated report per PWS

Initial – NLT forty -five (45) calendar days following contract award, or forty - five

(45) days following MBI clearance, whichever is later.

Subsequent submissions shall align with the published ES milestone charts.

Designated Government Technical Lead (GTL) and / or o Capacity Planning / Analysis and Performance Tests and Tuning The Contractor shall provide an analysis of enterprise architecture capacity and identify future resources that will be required. The analysis should indicate the area, the current state, and the future state requirement that would require additional / changed capacity. The assessment shall contain sufficient data and supporting information to substantiate the analysis and recommendations. The supporting data will reflect all components on platform.

Recommendations shall be based on proof of concept and utilize IRS data and any applicable guidelines and regulations.

The initial analysis and recommendations shall be submitted as part of the consolidated analysis and recommendation report. This information shall be submitted within forty - five

(45) days of contract award, or forty - five (45) days following MBI clearance, whichever is later. The Contractor shall monthly re - evaluate the initial recommendations and solutions and submit any additional recommendations for additions and / or changes with the MSR.

Deliverable Frequency / Due Date Technical POC / Reviewer

Capacity Planning:

Capacity planning and tuning report with supporting data

Supporting data shall include as a minimum:

- KPI Metrics

- Performance Measures

- Capacity Forecast

Initially: No later than forty - five

(45) days following contract award or MBI clearance, whichever is later.

Following initial submission, the document shall be maintained throughout the life of the TO and changes shall be submitted at the bi-monthly meetings identified per the

PWS.

Designated GTL and / or GPM o Tools The Contractor shall outline the tools necessary for development based upon the initial analysis completed per PWS. The utilization of existing IRS tools shall be prioritized.

The initial analysis and recommendations shall be submitted as part of the consolidated analysis and recommendation report per PWS. This information shall be submitted within thirty (30) calendar days of TO award, or thirty (30) calendar days following MBI clearance, whichever is later. The Contractor shall, monthly, re - evaluate the initial recommendations and solutions and submit any additional recommendations for additions and / or changes with the

MSR.

Deliverable Frequency / Due Date Technical POC / Reviewer

Recommendations: Required Tools

Initial – NLT thirty (30) calendar days following contract award.

Following initial submission, future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS.

o The Contractor shall analyze existing network architecture designs and processes and provide recommendations for effectively designing and implementing architect solutions.

The below elements shall be included, as a minimum, in the assessment and recommendations.

- Analysis of any architectural gaps or areas which require correction. The analysis shall provide recommendations to correct the gaps and ensure Government visibility on any reoccurring gaps.

- Analysis of existing technical guardrails, identification of weaknesses of existing guardrails and providing solutions / recommendations to improve or correct existing guardrails. Where new guardrails are required, the Contractor shall justify the need and purpose for additional guardrails.

The initial analysis and recommendations shall be submitted within forty - five (45) calendar days of TO award or forty - five (45) calendar days following MBI clearance, whichever is later. The analysis shall be included as part of the consolidated analysis and recommendation report. The Contractor shall monthly reevaluate the initial recommendations and solutions and submit any additional recommendations for additions and / or changes with the MSR.

Deliverable Frequency / Due Date Technical POC / Reviewer

Recommendations: Architecture designs and processes

Initial – NLT forty - five

(45) calendar days following contract award, or forty-five

(45) days following MBI clearance, whichever is later.

Following initial submission, future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS.

o The Contractor shall analyze existing technical documentation, guides, regulatory frameworks, and internal IRS processes to identify methods to streamline processes, clarify / improve /create guideline documentation, or otherwise improve the effectiveness of existing and planned architecture. The below items shall be included as part of this analysis:

- Researching and analyzing existing intake forms required for Application Onboarding.

- Standard and Guidelines for CES Microservice Architecture, services to be deployed on API Gateway and Data Access Services on Enterprise Data Platform (EDP) and other data sources across the IRS.

- Processes for onboarding services and how and what they will get access to the repository.

- Government approved software project management and comprehension tools (i.e.

Maven, Gradle, Ansible, Gitlab / GitHub and / or Jenkins) for life cycle process for project dependencies and configuration builds.

The initial analysis and recommendations shall be submitted within sixty (60) days of TO award or sixty (60) days of obtaining MBI clearance, whichever is later. This analysis will be submitted as part of the consolidated analysis and recommendation report. The

Contractor shall monthly re - evaluate the initial recommendations and solutions and submit any additional recommendations for additions and / or changes with the MSR.

Deliverable Frequency / Due Date Technical POC / Reviewer

Recommendations: Technical documentation, guides, and frameworks.

Initial – NLT sixty (60) calendar days following TO award.

Following initial submission, future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS.

o OneSDLC Artifacts / Documentation The Contractor shall initiate and create, evaluate, and update if needed, OneSDLC artifacts for the delivery cycles, populate, and maintain a repository of information that enables the Government to complete compliance artifacts for OneSDLC. The repository of information should include a master document that aligns and maps the information captured in the repository to OneSDLC compliance artifacts and shall outline what must be completed for each OneSDLC artifact.

OneSDLC Documentation:

Documentation and tracking related to OneSDLC submission requirements.

Initial – Initiated NLT sixty

(60) calendar days following contract award.

o Applications Development The Contractor shall support CES program in developing applications for CES tenants as needed. As part of Applications development, the Contractor shall be involved in gathering functional & non-functional requirements, designing, prototyping, coding, testing, ongoing improvements / enhancements and debugging of the developed applications.

Requirements Documentation Fifteen (15) calendar days after gathering of requirements.

Designated GTL and / or

GPM

Design Documentation Within five (5) federal government business days of completing Design Documentation

Prototype (As needed) Within agreed upon number of calendar days after gathering requirements

Designated GTL and / or

GPM

Coding As agreed between IRS and Contractor

Designated GTL and / or

GPM

Testing As agreed between IRS and Contractor

Designated GTL and / or

GPM

Application Improvements / Enhancements (As needed)

As agreed between IRS and Contractor

Designated GTL and / or

GPM

Debugging (As needed) As agreed between IRS and Contractor o Data Architecture and Data Migration The Contractor shall analyze the current state and target state data models and architecture of the applications that are being migrated to the modernized platforms (e.g., SaaS, PaaS, etc.), and provide support with data mapping and recommending data migration strategy. The Contractor shall also support by supplying high - level data migration strategy plan and detailed runbook.

Deliverable Frequency / Due Date Technical POC / Reviewer

Assessment of current state and target state data model and architecture

As agreed between IRS and Contractor.

Designated GTL and / or

GPM

Data Mapping As agreed between IRS and Contractor.

Designated GTL and / or

GPM

Data Migration Strategy As agreed between IRS and Contractors

Designated GTL and / or

GPM

Runbook As agreed between IRS and Contractor.

• System Engineering Services The system engineering services is a DevSecOps resource. The Contractor shall test, validate, and verify the pipelines and ensure they are working properly. The tasks outlined below support this requirement. The Contractor shall ensure system availability throughout the life of the TO. This will be accomplished through the areas below.

o Systems configuration / management. The Contractor shall ensure that systems are configured to align with all applicable guidelines. The Contractor shall provide continuous testing of system configuration to validate that all applicable controls and configurations match required guidelines. The results of the testing shall be submitted with the MSR no later than sixty (60) calendar days following TO award, or sixty (60) days following MBI clearance, whichever is later.

Deliverable Frequency / Due Date Technical POC / Reviewer

Report:

System Availability Analysis

Initial – NLT sixty (60) calendar days following contract award or obtaining of

MBI.

Following initial submission, future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS.

o System Availability Analysis. The systems analyzed and maintained by the Contractor are critical to the ES mission. The Contractor shall ensure the systems are available 24 / 7 / 365 and shall immediately notify the Government of any potential issue which could impact system availability.

The Contractor shall report on system availability and provide notification of any non-available time. Where downtime is identified, the Contractor shall provide analysis of any root causes, recommend solutions, and execute any solutions approved by the Government.

The Contractor shall maintain system availability logs, if not otherwise electronically generated, and provide this system availability data during all scheduled meetings.

In addition to the monitoring of system availability, the Contractor shall analyze and report the performance of the system against baseline performance data. The Contractor shall maintain the performance measurements, if not otherwise electronically traced, through development and maintenance of logs.

Deliverable Frequency / Due Date Technical POC / Reviewer

Report:

System Availability Analysis

Initial – NLT sixty (60) calendar days following contract award or obtaining of

MBI.

Following initial submission, future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS

Designated GTL and / or GPM o Upgrade Analysis. Existing systems must be maintained, and preparations made for future upgrades and enhancements needed to deliver improved Capability, Operational excellence, Security, Cost optimization, Capacity, Load, Security, Performance, and Scalability. The Contractor shall provide continuous analysis of existing systems to identify required updates and changes needed to meet future state operations. The analysis will identify such areas as services, development, hardware / software, and infrastructure changes needed. The analysis will show gaps / shortfalls to meeting required updates as well as recommended corrections.

Following the installation of any upgrades, or the installation of new hardware / software, the Contractor shall conduct required inspections and analysis to determine the compliance of upgrades and / or new equipment / software with all applicable standards.

The Contractor shall follow existing processes for the evaluation and provide the Government with a written report showing the compliance of upgrades with existing guidelines.

Deliverable Frequency / Due Date Technical POC / Reviewer

Report:

System Upgrade Analysis

Initial – NLT sixty (60) calendar days following contract award or obtaining of MBI, whichever is later.

future analysis and recommendations shall be presented at the bi - monthly meetings identified in the

PWS

Designated GTL and / or GPM

Report:

Upgrade / installation

Completion / compliance

Initial – NLT fifteen (15) calendar days following the completion of any upgrade.

A summary of all upgrade inspection and results will be provided during the bi-monthly meetings identified in the PWS.

Designated GTL and / or GPM

• The Contractor shall provide necessary support to develop, configure, upgrade, automate, and maintain all system components that impact a successful functionality of CES owned platforms and environments (e.g., MuleSoft, ECP, EKS, etc.). Just as Infrastructure building blocks and their specifications are important for meeting or exceeding non - functional requirements in the operational environment, operational processes, such as event, incident and problem management, production configuration, change, release, and deployment management, are also key for non - functional requirements.

3.4 Task Area 4. Strategy Support

Provide necessary support to develop, update, and document the Program strategy to include alternative options and the impacts for modernizing a comprehensive list of technology capabilities, design patterns and reference implementations to enhance reusing existing patterns and standardized solutions leading to easier governance and audits. Conduct analysis, presentation, and documentation on the alternative options for General CES and Technical and Program Support Services strategy to support developing design patterns and reference architectures for all capabilities and assets. The General CES and Technical and Program Support Services strategy shall also address any relevant emerging legislative requirements.

The Contractor shall provide to build up a technically robust General CES and Technical and Program Support Services that addresses crucial operational needs and establishes a systematic and transparent decision - making framework by providing a structured and detailed approach to developing architectural patterns, creating guidance for capabilities in the system, and interpreting processes and technical details.

Strategy support shall include the following but not limited to:

• Provide strategy and technical support for the application and integration of tools needed for program execution including tools for program management, development, and automation.

• Leverage technology strategy. Develop a view of the existing technologies, usage patterns, guidelines, and inventory of assets then document the technology strategy vision.

• Develop reference architecture for all capabilities and assets to create blueprints encompassing the entire structure and components of General CES and Technical and Program Support Services

• Develop and expand design patterns to include all assets and capabilities. Expand the foundation capabilities to all the other technology capabilities and patterns.

• Implement full lifecycle automation using ServiceNow to streamline usage and enable organization - wide adoption.

• Establish lifecycle management and capability ownership and assign ownership of different capabilities and functionalities.

Desired Outcome: An interconnected coherent landscape for an overview of all General CES and Technical and Program Support Services components and resources to ensure efficiency and accountability.

3.5 Task Area 5. Technical Integration

The IRS requires Contractor - support to integrate between CES platforms and other systems (e.g., legacy systems, legacy data sources, modernized systems, low - code / no - code platforms, etc.)

the IRS ecosystem for seamless and automated communication. The Contractor shall provide technical integration services to implement General CES and Technical and Program Support Services for IRS Enterprise, and continuous monitoring, management, and response to anticipate and mitigate associated impacts to successful delivery.