FD4364 EA Stnd Know - PWS v4 RFI Draft.pdf

Performance Work Statement IRS – ES – Enterprise Architecture

EA Fiscal Year 2025 Acquisition Strategy EA Standards and Knowledge Based Support

DRAFT Performance Work Statement

1. Introduction and Background

2. Scope

3. Key Personnel

4. Program Management

5. Orientation Briefing

5.1. Briefing Contents

6. Transition

6.1 Transition In

6.2 Transition Out

7. Transition to Support (T2S)

8. Standards and Technology Management (STM)

8.1 Information Technology Change Request Management Support

8.2 Enterprise Standards Management (ESM) Technology Portfolio

8.3 Enterprise Standards Management (ESM)

9. Knowledgebase Management (KBM)

9.1 EA Knowledge Management

9.2 EA Knowledgebase Content Update

9.3 EA Knowledgebase Infrastructure

10. Alfabet Implementation Support

10.1 EA Knowledgebase SharePoint

10.2 KBM Visualization, Dashboard and Reporting

11. Event-Driven Architecture (EDA)

11.1 Stand up EDA Platform

11.2 Platform Engineering

11.3 T-Cloud Integration

11.4 Support IRS Stakeholders and Use Cases (Baseline and Onboarding)

11.5 Roadmap & Execution

12. Performance Requirements Summary (PRS)

13. Deliverables

13.1 Shipping

13.2 Deliverable Format

13.3 Deliverable Quality

13.4 Review of Deliverables

13.5 Deliverable Schedule

14. Other Information and Special Conditions

14.1 Hours of Work

14.2 Place of Performance

14.3 Telework / Alternate Work Site

14.4 Period of Performance

Performance Work Statement (PWS) IRS – ES – Enterprise Architecture

EA Fiscal Year 2025 Acquisition Strategy EA Standards and Knowledge Based Support

1. Introduction and Background

The Internal Revenue Service (IRS) Enterprise Architecture (EA) Program serves a critical role in ensuring that IRS business strategies are guided by sound investments in Information Technology (IT). Enterprise Architecture (EA) is mandated by laws and Federal Office of Management & Budget (OMB) Directives. EA must be aligned with Capital Planning and Investment Control (CPIC) and the IRS Enterprise Lifecycle (ELC) processes. The Enterprise Architecture Office (EAO), as a strategic business partner, develops and delivers Solution Architecture and associated engineering services to projects and programs in direct support of their mission to the IRS, US Department of the Treasury (USDT), Office of Management and Budget (OMB), and other Federal and State Government organizations. This includes enforcing standards and developing sound engineering guidelines. The EA Program is managed within the Information Technology (IT) organization and led by the Director of Enterprise Architecture.

The EA Program is a business-facing and mission-driven program, engaging in a highly collaborative relationship with both the Business Operating Divisions (BODs)/Functional Operating Divisions (FODs) and other IT organizations. We strive for excellence in customer service and quantifiable mission results. We intend for this procurement to continue the current support for Standards and Technology Management (STM), Knowledgebase Management (KBM), Alfabet Implementation Support and Event-Driven Architecture (EDA) workstreams until the work is transitioned to applicable Government program offices. NOTE: Acronyms are used throughout this document, so a Table of Acronyms is provided on p. 31-33.

The mission of the IRS EA Program is to:

• Drive Improved Mission Results: The EA Program activities will contribute to the improved delivery of IRS’ services to its customers through proactive identification of standards, new architecture facets and industry standard technologies for new capabilities, functionalities, and refined business processes. The EA Program will comply with Federal mandates and continue to evolve and improve architecture guidance and compliance.

• Increase Efficiency and Reduce Cost: The EA Program will seek opportunities to minimize the cost of business and IT solutions, with an emphasis on sharing and reusing assets, and eliminating unnecessary duplication across IRS.

• Improve IT Investment Decision Making: The EA Program will apply architectural discipline and rigor in supporting investment decision-making to ensure that IT investments are aligned to business needs, technically sound, compliant with standards, and in the best interest of the IRS.

• Improve IRS-Treasury EA Coordination: The EA Program will work collaboratively with the Treasury EA program to improve alignment of objectives and plans and ensure compliance with OMB and Government Accountability Office (GAO) requirements.

• Improve IRS-wide EA Awareness and Governance: The EA Program will continually strive to improve stakeholder awareness of EA products and services and enhance EA governance efforts by actively demonstrating EA results. This includes collaborating with other IT organizations and BODs/FODs, proactive customer outreach, ongoing education, and an effective program to ensure EA information is readily available to all IRS customers and partners through a variety of communication channels.

• Improve and Innovate: The EA Program seeks to continually improve and innovate EA products and services. The EA program expects all team members to continually strive towards improving all aspects of the EAO program. The EA Program will improve stakeholder awareness and support and enhance governance efforts, through demonstration of EA results and impact, collaboration, outreach, education, and communication.

PERFORMANCE WORK OBJECTIVES

EA is responsible for strengthening technology infrastructure across the enterprise. The EA team accomplishes this by defining the current and target Enterprise Architectures and developing a transition strategy to move the agency towards the target environment. EA defines how an enterprise-wide data environment will organize, identify, share, reuse, and correlate data. EA provides systems engineering services that promote standards-based, enterprise solutions and serves as the enterprise testing authority partnering with customers to improve the quality of information systems, products, and services. EA also provides meaningful metrics of IT performance and business impact. This contract agreement will support the needs of the Enterprise Architecture organization.

EA requires Contractor support to develop define, update, and communicate EA strategic plans and initiatives that meet objectives in support of internal and external stakeholders. The Contractor shall provide support and services in the following general areas:

• Standards and Technology Management (STM)

• Knowledgebase Management (KBM)

• Alfabet Implementation Support

• Event-Driven Architecture (EDA)

The Contractor shall produce Deliverables/Work Products that conform to, and integrate with, existing IRS standards and guidelines. The Contractor shall conform to all IRS Security and Disclosure policies.

DESCRIPTION OF TASKS

This Performance Work Statement (PWS) is for a Fixed Price Performance-Based Acquisition with mission-oriented, event-driven performance measures. The contractor will be required to achieve specific/measurable results, incentivized to find efficient ways to meet the desired performance level. Travel to IRS, Department of the Treasury, and other Government facilities and offsites may be required. Travel will be cost reimbursable and added as a separate contract line-item number (CLIN).

2. Scope

The IRS is continually striving to better meet management challenges inherent in the growing variety of interfaces, increasing Information Technologies (IT) capabilities, demanding security needs and rising expectations from internal customers. Faced with reprioritized budgets and growing demands for its services, the IRS is seeking innovative, creative, and cost-effective solutions that address the rising cost of IT consulting services.

EA requires Contractor support to assess and analyze IT initiatives driven by IRS delivery partners or stakeholders. The goal is to identify, connect, and recommend areas for collaboration, connection, and input to our core products and services proactively and expediently. Contractor support will help architect and design enterprise solutions, balance efficiency, and connect the tax ecosystem in a seamless and leading-edge manner. Doing this will require executive level engagement from the Contractor and frequent and direct collaboration with ES leadership.

This document provides requirements needed to support the establishment of a contract to obtain Solution Engineering and Enterprise Architecture support services including impact of system and product retirements on the IRS architecture, support for development and reporting of IT performance metrics, project and program management for EA led initiatives in direct support of their mission to the IRS, USDT, OMB and other Federal and state Government organizations.

3. Key Personnel

The offeror shall identify, in their proposal based on information provided in the table below, certain positions or roles and associated labor categories considered to be Key Positions. The Contractor shall submit the name and resume of the Contractor employee (certified by their respective manager) for each Key Position shown in the table below. Key Personnel may also be identified at the time individual Task Orders are awarded. Task Order key personnel will be identified when the PWS for the Task Order is issued.

Contractor employees identified as Key Personnel shall be dedicated to this project. If any changes in proposed Key Personnel become necessary during actual performance, the contractor shall provide written notification 60 days in advance. In the event of a sudden change in Key Personnel (death, incapacitation, immediate termination, etc.), the contractor shall provide written notice to the Contracting Officer (CO) within 3 calendar days of the event. For any substitution, the Contractor shall submit justification with a proposed substitute whose qualifications are equal to or greater than the person being replaced, along with a resume in sufficient detail to permit evaluation within 10 calendar days of notification of a substitution. The chart below depicts key personnel the Contractor will provide to support this contract. The “Additional Experience/ Job Requirements are a guide, and the Contractor must ensure resources are qualified to perform duties prescribed and directed by government program leads.

Position or Role Additional Experience/Job Requirements

Principal EA Advisor/ SME - Computer and Information Research Scientist

The Principal EA Advisor (SME - Computer and Information Research Scientist) should have 15+ years, or comparable, of demonstrated:

• Experience across various, successful government and private sector architecture enterprise systems, technology strategies, enterprise system developments and deployments, Cloud implementations, and business process re-engineering to support and execute against the EA’s core mission and IRS future state vision.

• Experience providing executive management consulting on corporate strategy focusing on enabling technology implementations and business process reengineering in support of legacy modernization and digital transformation.

• The Principal EA Advisor should have the knowledge and expertise to advise EA leadership and/or key members of the EA organization on best practices, industry trends, and innovation taking place in the public and private sectors.

Task Order Program Manager (PM)

The Program Manager will be responsible for overall management, performance and quality of the Team’s work and full authority to act on behalf of the contractor on all award matters relating to daily operations, contracts, and staffing. The Program Manager should have 15+ recent years, or comparable, of demonstrated experience.

• Experience across various successful government and industry architecture enterprise systems, technology strategies, enterprise system developments and deployments, Cloud implementations and business process re-engineering.

• Experience leading Enterprise Architecture teams in conducting multiple workstreams including, but not limited to current-state analyses, target-state visioning, IT Transition Management including transition state road mapping, prototyping, analysis of alternatives, architecture, and design artifact generation.

• Experience managing projects with complex technical and organizational landscapes and demonstrated ability to facilitate close integration between business and technical aspects of projects; planning project stages and providing recommendations on business implications for each stage that are tied to enterprise strategy/objectives.

SME - Computer Systems Engineer/Architect

The SME - Computer Systems Engineer/Architect should possess specialized engineering and architecture experience gained across government and private sector clients in analyzing and developing implementation strategies for new technologies, application strategies, data strategies, security considerations, establishing engineering design patterns and guidance to build a common, forward-looking approach for IT modernization.

The Technical System Architect should have 15+ recent years, or comparable, of demonstrated experience.

• Experience redefining technical processes and architecture to build a common, forward-looking approach for a target state business architecture.

• Experience creating and supporting forums for industry leading technology adoptions opportunities and aligning new technology to immediate and future architecture priorities.

• Experience with Computer Systems Engineers/Architects to define, develop and integrate an architectural strategy and design initiatives to support a diverse Business and IT Portfolio.

Position or Role Additional Experience/Job Requirements

• Deep understanding and experience in executing Enterprise Architecture frameworks and solution design patterns.

EA SME – System Architect – Business

The Business System Architect should have hands-on technical experience providing enterprise architecture services, strategic planning and business IT alignment, program and project support to government and private sector clients. The Business System Architecture should have 15+ recent years, or comparable, of demonstrated experience:

• Experience redefining technical business processes and architecture to build a common, forward-looking approach for a target state business architecture and other architecture and engineering artifacts.

• Experience with Technical architects to define, develop and integrate an architectural strategy and design initiatives to support a diverse Business and IT Portfolio.

• Experience with eliciting requirements and creating business architecture analyses and visualizations.

4. Program Management

The Contractor shall provide program management support to develop, track, and maintain all work under the Task Order. This shall include developing and baselining project schedules or project roadmaps with milestones for deliverables; monitoring and tracking progress toward project milestones and providing updates for work efforts; implementing Agile workload management practices by leveraging Kanban boards and Agile ceremonies and managing Contractor resources based on workload and priority. The Contractor shall ensure that change management and strategic communications are integral capabilities of the Contractor’s program/project management activities.

The Contractor shall perform standard contract management activities, including managing the Contractor support staff assigned to this Task Order and ensuring all Contractor employees comply with the security and training requirements of the IRS.

The Contractor shall submit a biweekly status report of all significant accomplishments from the prior two weeks and work planned for the next two weeks. The status report will be discussed with the IRS at bi-weekly status meetings. Contractor team leads are expected to attend the bi-weekly meetings.

The Contractor shall maintain a team roster and submit when changes are made. The roster shall include the following for each resource:

Name Status of MBI and date MBI letter was issued (interim and final) If final, expiration date of memo Assigned workstream GFE Assignment (laptop barcode and SmartID number) Date training completed (SAT and SITS)

The Contractor shall participate in periodic meetings with Government personnel (both on-site and via MS Teams to discuss status and new and developing issues that may affect Task Order performance.

The Contractor shall prepare and deliver in designated format (Word, Excel, PPT, PDF) a Monthly Status Report (MSR) identifying the deliverables and services (if no formal deliverable was provided) for the prior month. The work performed and reported on the MSR must be consistent with the services invoiced for the reporting period. If requested, the Contractor shall participate in monthly Project Status Review meetings, and other meetings relating to each Deliverable/Work Product. The MSR must be submitted within 10 days of the end of the month. The invoice can be submitted 5 business days after submission of the MSR.

The following supplemental information is required for each Deliverable/Work Product that is ordered:

a. Contractor Employee(s) responsible for the Deliverable/Work Product.

b. A high-level integrated master schedule that outlines the tasks, milestones, and timelines for task area or work product.

c. Status of Deliverable/Work Product (indicate whether it is on-hold and why, whether it was completed during the period, or is still in-progress).

d. Percentage of Completion for each individual CLIN ordered, for each month, and cumulatively for the year.

e. Any problems or issues encountered during the performance of a Subtask or

Deliverable/Work Product which have not yet been resolved, along with a suggested solution for each.

At the end of each reporting period, based on the delivery table, the Contractor shall provide a summary of work performed, including a list of deliverables, date delivered and/or SharePoint site where the deliverable is posted. The Contractor shall also include a self-assessment of the work performed during the prior period consistent with the format of the Contractor Performance Assessment Reporting System (CPARS).

The Government reserves the right to request specified report at any point during the performance of the order at the discretion of the Contracting Officer Representative. This ad hoc report, if desired, will only be requested once during the life of the Task Order and is in addition to the regularly scheduled Period of Performance Summary report.

Deliverables

a. Integrated Master Schedule (IMS).

b. Monthly Status Report due 10 days after end of each month.

c. Period of Performance Summary Report and Self-Assessment due last business day of the reporting period.

5. Orientation Briefing

Within two weeks of Task Order award, the Contractor shall conduct an orientation briefing for the Government. The Government does not desire an elaborate 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 Task Order participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of Task Order requirements and objectives.

The orientation briefing shall be held at the Government's facility or virtually, at the Government’s sole discretion; both parties shall mutually agree upon the date and time.

The completion of this briefing shall result in the following:

5.1. Briefing Contents

1. The Contractor and Government personnel who will perform work under this Task Order will be introduced.

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

3. The Government will address any issues concerning the Contractor clearances and Government Furnished Property requirements for Contractor personnel.

Deliverable

• Orientation Briefing (conducted within 2 weeks of award) and Meeting Minutes from meeting due 3 business days after the meeting.

6. Transition

6.1 Transition In

Transition-in is defined as the one-time “start-up” period at the initial award of the Task Order for on-boarding resources and transitioning support and knowledge from any incumbent Contractors and/or IRS personnel to the new awardee. The new awardee is tasked with acquiring and understanding the necessary documentation, information, and processes related to any work in progress. This effort includes meeting with the IRS Subject Matter Experts and/or outgoing Contractors frequently to gather any tacit knowledge related to the systems, projects, etc. in support of this Task Order. The Government estimates ramp-up may take up to 60 days. The Government may request additional support throughout the lifecycle of the Task Order as requirements are transitioned from existing agreements to this Task Order.

6.2 Transition Out

To minimize any decreases in productivity and to prevent possible negative impacts on additional services at the beginning and conclusion of the Task Order’s performance, if appropriate, a transition phase will start no later than ninety (90) days prior to its expiration date. The Contractor shall:

a. Have personnel on board during the phase in and out periods.

b. Remain responsible for the full performance of all efforts and cooperate fully with the staff and/or the new incumbent Contractor.

c. Fully cooperate in providing all documentation and data identified by the Government as Government owned information.

d. Return any Government information provided to the Contractor during associated Task Order performance.

All related work and products become the property of the Government, regardless of the ownership of the automation hardware or software used to create the products or services. All reports, charts, logs, and maps shall become the property of the Government upon completion or termination of each Task Order and shall be available for inspection by the Government upon request at any time during the Task Order period of performance.

Deliverables

All contract efforts are transferred timely and completely from the incumbent Contractor to the awardee Contractor. The Government is continuously informed of transition progress, there is no lapse in services provided, and there are no delays in scheduled performance. Key deliverables to be produced are:

• Transition Project Plan (tasks and timeline).

• Transition Presentation, Kickoff meeting and subsequent meetings with IRS Project

Manager, IRS SMES, and new Contractor.

• Final Work Summary Report (to include identification of any gaps)

• Document inventory and gap analysis.

• All editable and published versions of work products/documents are uploaded to

IRS EA SharePoint.

• Transfer knowledge of technical skills and lessons learned to IRS staff upon completion of deliverables and work products.

• Transfer knowledge of operations and maintenance processes and procedures.

• Support transition efforts to assist the Government with the transition of work from the Contractor to the Government or to a successor Contractor.

• Develop a Transition Plan that includes training material, current status report, planned activities, issues encountered and identified risks.

7. Transition to Support (T2S)

The transition to support process is an ongoing process throughout the life of the task and should be embedded in the work of each Task Order. This task includes the transition effort required to transition the Task Order at the end of the planned period of performance (OP4). The work shall include, but not be limited, to the following:

a. Knowledge transfer of technical skills and lessons learned to IRS staff and the incoming Contractor upon completion of deliverables and work products.

b. Operations and maintenance processes and procedures.

c. Transfer of complete documentation for all delivered functionalities. Deliverables shall be in soft copy and hard copy format (when appropriate) and shall be the sole property of the Federal Government. The format of deliverables will be provided in a format which will allow the Government to modify and update when/if necessary.

d. Knowledge transfer of configurable data including usernames and passwords and application settings.

Deliverables

• Develop and implement transition plan.

• Deliver knowledge transfer sessions.

• Complete configuration items are delivered and baselined.

• Bi-weekly status updates during the transition period.

8. Standards and Technology Management (STM)

STM is responsible for all Commercial-Off the-Shelf (COTS) based information technology approvals within the IRS Enterprise. STM identifies, implements, and enforces the technology standards that define the business initiatives affecting IT. The key standards component is the Enterprise Standards Profile (ESP) a comprehensive repository of all approved products allowed in the IRS and is the result of analysis for inbound and updated requests.

8.1 Information Technology Change Request Management Support

The EAO initiates, reviews, recommends and processes approximately 500 EA Change Requests (CR) annually to add, update, modify, or retire products in the Enterprise Standards Profile (ESP), a CM database. The EAO also provides the governance for the IT Change Control Board CCB (IT- CCB) in a technical and administrative capacity role. Specific tasks include, but are not limited to:

a. Review EA CRs within prescribed timeframes. Reviews include technical and architectural reviews and recommendations, along with the creation of the basis for decision-making and ESP artifact products.

b. Review an average of 35-50 CRs per month within the standard review time of 10 working days. If the request is urgent, the Contractor will need to complete the request in 2-5 days from the time of receipt at the respective stage in analysis.

c. Provide technical support to the EA CR review process and the Software Component (SWC) approval process by providing analysis for proposed changes to the ESP, monitoring process metrics and recommending process improvements. Additionally provide technical support for the review process for Cloud applications, Software as a Service (SaaS) and Platform as a Service (PaaS).

d. Conduct a monthly assessment of the EA CR process metrics and technical management of the ESP portfolio and make recommendations.

e. Assist in implementing any governance improvements.

f. Updating the ESP and/or providing updated artifacts for the ESP upon approval by the

IT Governance process.

g. Automate/maintain the EA SP CR process.

Deliverables

• Review of EA CRs within prescribed timeframes.

o Technical and architectural analysis of CR, impact and technical analysis, and CR recommendation.

o Recommendations for SWC/Cloud application approvals (estimate 5-10 reviews per month).

• Recommendations for process improvement (quarterly) including technical portfolio issues, linkage and/or metric deviation analysis.

• Manage intake and output of the IT CCB. Provide support for the IT CCB meetings including, meeting materials, CR updates Meeting minutes must be maintained in the IT CCB repository.

• Update the ESP with approved items upon approval by the IT CCB o Ensure ESP entries associated with the CRs are updated, maintained and quality controlled.

• Progress Reports – Bi-weekly Report and EA Director Updates/Briefing.

8.2 Enterprise Standards Management (ESM) Technology Portfolio

The IRS is faced with a growing number of duplicative, redundant, costly, and/or underutilized applications and tools. This inhibits IT’s ability to synchronize upgrades and the integration of new technology coherently to project technical architectural direction. A significant portion missing in the ESP are technical standards, software component tracking, and related/companion technologies/products proven by industry to work well together as standard stacks. This information needs to be aligned to milestones for upgrades as well as opportunities for new technology insertion.

The Contractor shall provide technical expertise and guidance to advise the IRS in the integration of an established government agency standards (or equivalent established baseline) to create design patterns and technology roadmaps/blueprints using the existing Enterprise Standards Management (ESM) framework. The ESM framework contains a sustainable methodology to integrate the IRS Modernization Plan, Target Enterprise Architecture as well as IRS’s IT Aged Hardware and Software data to the strategic goal in determining what to continue to invest in versus what to divest from. The ESM framework contains several portfolios including (but not limited to) application portfolio, infrastructure portfolio, standards portfolio (both IRS-type and Industry-type) and technology portfolio. The ESM methodology for each varies based on the requirements and benefits needed for each portfolio. The Contractor shall assist in developing artifacts and constructing the appropriate ELC path to ensure the resultant ESM operating model follows all prescribed regulations and appropriate guidance. While no formal tool has been selected yet to manage ESM, the Contractor will be expected to assist and support in the selection, configuration, and data migration of an ESM management tool.

Deliverables

• Portfolio disposition recommendations.

• Phased approach to Disposition:

o Phase 1: ESP Product Disposition/Recommendations by Category and Product.

o Phase 2: Enterprise Inventory Disposition/Recommendations to include ESP inclusion (CR Needed) or Remove from Enterprise.

o Support the data migration to the enterprise workflow solution.

• Recommend ESP Changes in support of ESM.

• TIGTA Audit Comparison of Installed S/W Inventory against ESP.

• Weekly status meetings.

• Product Process Recommendation updates (CQI of existing processes).

• Technology Cluster Reports (Dashboard) – reporting to drive identification and setting standards.

• Progress Reports – Monthly Report and EA Director Updates/Briefing.

8.3 Enterprise Standards Management (ESM)

ESM is an overarching process that governs the IRS’s product standards identification and management processes (from identification to recommendations for removal from the IRS network). ESM, in collaboration with other IT organizations, ensures that projects are compliant with IRS standards and any deviation requires that suggested departures go through a Change Request (CR) process. The key steps of ESM are standards identification, enforced compliance, communication, documented guidance development, and Technology Refresh Process. To accomplish these tasks:

a. The Contractor shall identify the industry standards and companion technologies associated with each FEA (Federal Enterprise Architecture) and ServiceNow Service Catalog category called clusters.

b. The Contractor shall identify products in the ESP that support standards and companion technologies.

c. The Contractor shall link these companion technologies/supported technologies and products. Companion technologies include IT industry/IRS adoption that are compatible.

d. The Contractor shall identify the industry standards that traverse more than one FEA category that link products together.

e. The Contractor shall produce suggestions and recommendations for standardization through comparison between the ESP, Technopedia, BigFix, CA SAM, ServiceNow, and IR Works – as available.

f. The Contractor shall aid in the identification of product custodians that manage products throughout their respective life cycles, e.g., emerging technologies through retirement and removals.

g. The Contractor shall produce a series of expanded standards criteria by which initial analysis can serve as the baseline and include a weighting strategy for assessment.

h. With tasks completed, the Contractor shall propose design patterns with the design pattern adoption benefits and design pattern adoption risks for each as well as any overall architecture risks, e.g., portability, scalability, proprietary.

i. The Contractor shall produce reports and metrics that outline results of identification, analysis, and recommendations.

Deliverables

• New Standards established in IRS by FEA/ServiceNow Service Catalog category

(monthly).

• New Standards linked to each ESP product (monthly).

• Companion Technologies and Supported Standards link to each product (monthly).

• Product categories linked to companion technologies and supported standards linked to each product (monthly).

• Reports and Metrics (bi-weekly).

• Advanced criteria for assessing FEA category standards.

• Recommendations for retirement/removal (monthly).

• Product custodian outreach, listing compilation, and entry in the ESP (bi-weekly).

9. Knowledgebase Management (KBM)

Knowledgebase Management (KBM) is responsible for organizing, maintaining, and publishing several core IRS Enterprise Architecture information sources. These include the As-Built Architecture (ABA), the Enterprise Standards Profile (ESP), the annual Enterprise Architecture website release, and the Enterprise Architecture Office SharePoint site. The KBM uses Unicom System Architect (SA) for maintaining and publishing ABA data to its website and a Data Collection Self-Service (DCSS) workflow-based web application tool. The KBM maintain SharePoint, Windows servers, and IIS, JBoss application servers and EA websites to manage data.

System Architect (SA) repository is an authoritative data source for ABA and used to publish ABA website. It is widely used in IRS and gets 6-7 thousand page hits every month by various IRS stakeholders. Many IRS organizations cannot do their functions without the ABA content. The main challenge using SA for ABA is that the data model is not machine discoverable. The solution, EA will be migrating to a new tool, Software AG Alfabet. This new tool will allow the IRS to expand the capabilities System Architect to provide full application portfolio management.

9.1 EA Knowledge Management

The EA Office requires analysis, design, and implementation support for an integrated metamodel of IRS enterprise architectural data. The IRS enterprise architectural data is a comprehensive view of IRS applications, business processes, technologies, and the investments implementing the IRS mission. This model is currently hosted in Unicom Rational System Architect, with connections to multiple IRS databases. The EA model currently contains 80+ objects representing the IRS IT environment, IRS six domains of change including application, data store, IRS technology item, Contractor technology item, business process, organization, location, and investment objects. The metamodel shall have machine discoverable interface so that it can interface with IRS tools and data sources.

The Contractor shall provide support to review, update, maintain EA data model to include relationships between IRS standards, business processes, locations, organizations, applications, data stores, and technologies. This will also include maintaining those relationships in Alfabet.

Currently, EA maintains two data models: As-Built-Architecture (ABA), to be replaced by SAG Alfabet) and Enterprise Standards Profile (ESP). The current ABA uses System Architect (SA) repository and its proprietary data model which contains more than 1200 applications, with more than 80 objects and more than 600 attributes. Alfabet will be expected to keep the current capabilities and enhance future capabilities. ESP has a data model that houses more than 5000 software products with a minimum of 70 attributes. The data in the ESP will be moving in phase to the enterprise workflow tool, ServiceNow. EA will maintain ownership of the data.

Deliverables

• Implement EA metamodel using a modeling tool that can integrate with ServiceNow.

• Document data dictionary, data model, configurations, and associated artifacts.

• Communicate with stakeholders that includes planning, briefings, and model demonstrations.

• Collect, integrate, and maintain enterprise data in the Alfabet repository.

• Upgrade and extend data model for new ServiceNow capabilities.

• Fully integrate the capabilities of Software Alphabet to include Enterprise

Architecture, Enterprise Architecture Roadmap, and full application portfolio management.

9.2 EA Knowledgebase Content Update

The EA Office requires collaborative collection, analysis, maintenance, and publication of enterprise data to the EA Portal, the training website, the EA web site, the As-Built Architecture (ABA) web site, and the Enterprise Standards Profile (ESP) web site.

The Contractor shall provide analyst support for the continuous analysis, review, collection, and update of EA knowledgebase content. This support shall include reviewing and maintaining the relationships between IRS investments, standards, business processes, locations, organizations, applications, data stores, and technologies. The Contractor shall provide maintenance and technical support to upgrade ABA publishing processes and website with the upgrade of System Architect and integration points with ServiceNow.

Deliverables

• 60 major changes/updates per month in aggregate in support of the EA Portal, the As-Built Architecture (ABA) web site, and the Enterprise Standards Profile (ESP) web site.

• Use industry best practices to document standard operating procedures (SOP), FAQ and associated artifacts.

• Collect data using DCSS from data owners and other data sources. Extract, transform, and load data to a SA repository/Alfabet and databases. Knowledge and application of Java is required.

• Communicate with stakeholders that includes planning, briefings, and model demonstrations.

• Analysis to respond to TIGTA and Congressional inquiries.

• Reporting for data calls to OMB, GAO, IRS executive leadership, Commissioner’s

Office.

• EA input to quarterly Operations (Ops) Reviews and ES reviews.

• Configure publishing tool (currently System Architect/Alfabet) and publish reports on websites.

• Bi-Weekly status reports.

• Reporting on the status of selected change requests and/or data calls.

9.3 EA Knowledgebase Infrastructure

The EA is supported by several disparate IT information systems, including the EA Portals (SharePoint), the EA websites (IIS Server, JBoss), the As-Built Architecture (ABA) SA publishing or Tableau dashboard, ABA Data Collection Self-Service (DCSS)/Alfabet web application (Java, Ajax/REST, SQL Server 2014 plus, JBoss, IIS, Web Frontend), the Enterprise Standards Profile (ESP), application and the Change Request Tracking Systems. The EA Portal supports 100+ people in the EAO and hosts over 100 GB of content in 1569 folders holding 11,007 files. The ABA environment includes over 15,000 files on the web site and 5+ GB of content in 100+ tables with and hosted on IIS Server. The ESP environment includes .Net framework, Web Frontend, Java, IIS webservers and stored procedures hosted on SQL Server. The data can be accessed using webservices including REST API. Specific tasks and skills include, but are not limited to:

a. Technical knowledge and skills necessary to maintain and enhance the existing IRS infrastructure and support the EAO’s effort to improve usability and accessibility of EA information.

b. Technical knowledge and skills to redesign the infrastructure for these information systems into an integrated whole and into a future solution that incorporates new technologies being introduced into the IRS IT environment, including Java, Apache Tomcat, JBoss, Web Frontend, SharePoint 2010 wiki, future versions of IBM Rational Suite, or other similar products.

c. Technical knowledge of SAG Alfabet and skills to redesign the infrastructure for these information systems into an integrated solution that incorporates new technologies being introduced into the IRS IT environment, including Java, Apache Tomcat, JBoss, Web Frontend, SharePoint 2010 wiki, future versions of IBM Rational Suite, or other similar products.

d. Specific tasks include:

• Technical support to create, review, update, maintain EA data model to include relationships between IRS standards, business processes, locations, organizations, applications, data stores, and technologies.

• Technical support for data extraction from existing tools and artifacts, transforming the data and migrating to the new tool.

• Technical support for data extraction from existing tools and artifacts, transforming the data and migrating to the new tool.

10. Alfabet Implementation Support

IRS selected Software AG Alfabet (referred to as Alfabet) to implement an integrated strategic IT portfolio management solution to significantly improve portfolio-based planning, management and analytics while reducing O&M costs through retirement of existing systems, applications, and products. This tool will provide IRS IT with a comprehensive service-based toolkit that will enable EA to drive the enterprise toward a rationalized and cost-effective inventory. IRS Enterprise requires an integrated view of all IRS inventory and finance data and a comprehensive portfolio-based decision-making for IT modernization across all IT platforms.

Alfabet is an integrated tool for achieving Enterprise Architecture and modernization objectives by optimizing solution processes, speeding up inventory cycle times, improving EA Planning, and allowing stakeholder access to a single source of truth.

The Contractor will leverage Alfabet and ARIS tools to mature IT inventory investments through rationalization of investments and accelerating modernization. (ARIS is a supplemental module included here in the Alfabet Implementation package and specifically focuses on Business Process modeling and analysis.) The Contractor is expected to:

a. Maintain the implementation requirements backlog, roadmap, Minimum Viable Product (MVP), release and iteration plan.

b. Augment canned and repeatable reports, analytics, and dashboards to mature broader EA Portfolio Management capabilities.

c. Coordinate Data Discovery efforts and automate systems owner information collection;

provide guidance and coaching support to pilot teams and power users to leverage Alfabet for their workstream to build Target State, Solution Models, and Roadmaps; integrate capabilities, processes, Target EA, and alignment metadata for depicting layered elements of the architecture framework.

d. Provide Integration guidance for the ServiceNow interface, data share (Master Product Lists and/or Technopedia Sync), and coordinate with ServiceNow/ITSM Team to integrate additional systems inventories and groom them according to Alfabet needs.

e. Provide Data /Table mappings with the ESP/ServiceNow for enabling ease of access and cross variable analysis between systems inventory and product lists.

f. Provide guidance for access rights upon request in coordination with IT team(s) providing oversight.

g. Provide interface and training to enable self-serve analysis and custom reporting in accordance with EA service model.

h. Provide integrated KPI analysis as defined by EA Leadership and Domain Architecture Leads.

i. Provide tailored analysis and dashboards specific to EA and partner requests.

j. Provide alternative visualizations, reports, and directed access for unique role-based use cases as needed.

k. Provide automated notification, and impact assessments for targeted systems, components, and other aged infrastructure.

l. Provide expertise in the implementation of AI capabilities inherent in Alfabet in the form of intelligent, plain language query Bots to construct ad hoc queries (AlfaBots)

Deliverables

• Functioning Alfabet and ARIS tools with As-Built-Architecture (ABA) data migrated and groomed for use in analysis.

• Functioning Alfabet and ARIS tools with Enterprise Standards Profile (ESP) data migrated and groomed for use in analysis.

• Documented and integrations of additional data sources, e.g., Enterprise Operations (EOps) asset management stores, financial systems, and relationships across the enterprise to provide a ‘single pane of glass’ for use in decision making and assessment of technical viability.

• Portfolio analytics interfaces and dashboards.

• Dynamic digital interfaces for modeling target architecture and solution architectures.

• Systems inventory integration and automated updates to include notices to systems owners.

• EA teams adoption of tool in daily workflows.

• Technical support to create, review, update, maintain EA data model to include relationships between IRS standards, business processes, locations, organizations, applications, data stores, and technologies.

• Technical support for data extraction from existing tools and artifacts, transforming the data and migrating to the new tool.

• Integration of Knowledgebase with technical repositories and other portfolio rationalization efforts. Design and implementation of web-enabled Self-Service solution for users to update Knowledgebase data.

• Design and implementation of Data Analytics and Visualization derived from many authoritative data sources.

Other Deliverables

• EA Portal website support and maintenance website to be reimagined to include complete picture of EA Services as well as integration with EA SharePoint Site. Site should be applicable and concise - and content should be refreshed on a Quarterly cycle.

• Alfabet website with database development and maintenance.

• Data driven web development using Java, Java API support, Web services support to data repositories.

• Tableau support for visualization and data reporting.

• ESP website and database development and maintenance.

• Change Request Tracking Systems Metamodel maintained in System Architect and other IRS stakeholders as requested.

• Windows server configuration, JBoss and IIS server configurations.

• ServiceNow CR tracking request.

10.1 EA Knowledgebase SharePoint

The EA office currently has eight (8) SharePoint site collections and will continue to grow as EA Knowledgebase content grows. The Contractor shall provide support for EA SharePoint sites maintenance and building SharePoint solutions and other similar tasks.

Deliverables

• EA SharePoint site support and maintenance (ongoing need).

• Generate SharePoint Access and Permissions log (monthly).

• Create and support for development of new EA SharePoint sites, up to two (2) new sites per quarter.

• Up to two (2) non-trivial updates per day to SharePoint sites.

• SharePoint Metrics (monthly).

10.2 KBM Visualization, Dashboard and Reporting

The EA office is required to maintain Knowledgebase Management visualization, dashboards and, reports for Knowledgebase data using Tableau, office automation and reporting tools and scripting languages. Tableau is currently used for data visualization. SharePoint sites and EA websites are used for data reports. Specific tasks include:

a. Create, update, and maintain EA knowledgebase management visualization, dashboard, and reports. A standardized reporting and visualization shall have interfaces and capabilities to create integrated information for planning, analyzing and portfolio management.

b. Provide research, operational, and meeting support including performance metrics, trending analysis, meeting artifacts, and outreach to other areas in the IRS-IT domain.

Deliverables

• Generate reports of integrated knowledgebase data.

• Provide monthly visualization, dashboard, and reports.

• Support ACIO/DCIO Briefings.

• Support Monthly EA Director Presentations.

• Provide Data Analytics.

• Documentation supporting the work.

Other examples of deliverables may include:

• Implement EA metamodel using a modeling tool.

• Document data dictionary, data model, configurations, and associated artifacts

• Communicate with stakeholders that includes planning, briefings, and model demonstrations.

• Upgrade and extend data model for new capabilities.

• Provide import, export capabilities including connecting to other data sources and

API support.

• Migrate, integrate, and maintain enterprise data in the repositories from ABA, ESP, DCSS, SA, Tableau, MS Office suite and others.

• Configure publishing tool and publish reports.

• Data integration process set up and implementation.

• Report generation, support, and maintenance.

• Dashboard creation, support, and maintenance.

• Data analytics, support, and maintenance.

11. Event-Driven Architecture (EDA)

Event-Driven Architecture support will focus on operationalizing the EDA Platform (Standup Activities, Integrations, and Documentation), Platform Engineering (EDA Frameworks and Specifications), and Support to IRS Stakeholder and Use Cases (e.g., EDA Adoption & Onboarding) where support further expands functionality, capabilities, and scale in support of IRS business, technical, and modernizations initiatives.

11.1 Stand up EDA Platform

The Contractor will prioritize and support the stand up of the EDA Platform and associated capabilities in the Treasury and/or IRS infrastructure environment, which includes the completion, submission, review, and updating of artifacts for various IRS processes used to approve and establish the EDA Platform environments (Dev, Test, Pre-Production, and Production) and technology products (i.e., Confluent Kafka). In addition to standing up the platform, the Contractor EDA team will work to iteratively enhance EDA Platform functionality and capabilities to continuously meet event demand, scaling needs, service-level agreements, and the expansion of identified and yet to be identified use cases. The Contractor will support a multi-tenet model to broaden Platform availability and will develop billing and cost modeling used to plan for future needs and funding.

Event Driven Architecture (EDA) Platform Stand-Up:

• Enterprise Event Backbone servicing Fan-out / Streaming / Routing Patterns for all

Enterprise / Integration events including sourcing and syncing across IRS ecosystem.

• Domain Event Bus servicing Pub-Sub Patterns for individual domains to support loosely coupled and flexible systems / interconnected services communicating through domain / technical events.

•…