PWS_BMF Mod Legacy SME Support 05.23.24.docx

Performance Work Statement Business Master File Modernization (BMF MOD) Program – Business Requirements and SME Support

Section C DESCRIPTION/ SPECIFICATIONS/WORK STATEMENT

C.1 INTRODUCTION AND BACKGROUND

C.1.1 Introduction

Under the Inflation Reduction Act (IRA) of 2022, the Internal Revenue Service (IRS) is committed to improving the taxpayer experience by modernizing core tax administration systems, IRS Information Technology (IT) infrastructure, operations, and cybersecurity. Taxpayers expect to access their sensitive financial information securely and easily, find and understand complex tax information from any device, and to resolve issues quickly, proactively, using a variety of self and assisted services. The IRS IT Modernization Plan positions IRS to transform taxpayer experience and meet these expectations. The current legacy computing infrastructure cannot keep pace with the desire for instantaneous data, real-time interactions, and other customer-centric services, and the cost to operate our current technology ecosystem continues to increase. Our ability to successfully modernize and maintain our IT foundation is critical to our ability to continue to deliver the IRS mission in a cost-effective way.

Applications Development (AD) and its IT delivery partners (i.e., Enterprise Services (ES), Enterprise Operations (EOps)) are responsible for modernization of the business taxpayer accounting and implementation of modernized data distribution platform. The IRS has increased their focus on the development and maintenance of modernized tax processing systems to enable additional business capabilities and improve stability, performance, operations and security. To support this effort, AD and its IT delivery partners (i.e., ES, EOps) will design, develop, deploy, and maintain enterprise level Business Master File modernized systems.

The Business Master File (BMF) modernization is one of multiple programs created to support the objectives of the IRS IT Modernization Plan. In support of a modernized BMF platform, AD and ES will leverage existing enterprise architecture strategies and objectives to establish a modern, secure, future-proof technology foundation that can rapidly scale.

The BMF Mod Managed Service PWS is to acquire contractor support services for to design and implement a modernized BMF platform and database in FedRamp High Cloud infrastructure based on IRS priorities. The contractor shall assist the Government in their effort to provide reliable and secure IT services and integrated business services support that meets or exceeds customer requirements and expectations.

C.1.2 Background

Business Master File (BMF) maintains tax accounts for Businesses and Exempt Organizations. This investment also includes reporting and extracting for all master files, as well as the processing necessary to accept data from multiple input systems.

BMF Masterfile Modernization (BMF Mod) Program Overview:

The IRS established the BMF Masterfile Modernization (BMF Mod) Program to achieve the modernization of business taxpayer accounting and implementation of a modernized data distribution platform. The BMF Mod solution concept aligns with the Modernized Tax Account Management target state architecture and will enable the IRS to accelerate the delivery of high-value features to business taxpayers by using reusable components and common platform services. BMF Mod will leverage a fully vendor-built delivery model, in which a contractor team shall be responsible for architecture, design, development, testing, security, and integration of the modern target-state solution within the scope of IRS outcomes and guardrails. Through this program, the IRS will implement the solution of a single integrated environment for managing business taxpayer accounts that will:

· Implement 21st century technology and services to enable the IRS BMF to provide digital services to the taxpayer and enable timelier taxpayer compliance

· Improve security and privacy of taxpayer information by eliminating identified weaknesses.

· Provide more timely and accurate responses to taxpayer inquiries and faster resolution by establishing an authoritative data source with daily processing capability.

· Increase the integrity and accuracy of taxpayer accounts which are the cornerstones of the US Financial System

· Improve the agility and flexibility of the IRS to respond to new legislative mandates and taxpayer expectation.

BMF Mod program is modernizing core business taxpayer accounting capabilities and establishing the BMF database as the modernized, authoritative datastore for business taxpayer account data in a scalable Big-Data, FedRamp high, Cloud platform. The BMF database will be developed as a centralized data hub to facilitate easier access to business account data, allowing self-service reporting and analytical tools. BMF Modernization will use common services to make BMF data more accessible, establish the analytical datastore, and enable self-service reporting. Downstream Consumers and User Migration will modify downstream systems to access modernized data formats and transition off BMF legacy applications and file formats. The BMF Mod program will modernize data distribution mechanisms to enable faster and easier data consumption by downstream consumers and users.

With contractor support being provided to the BMF Mod Program under this SOO, the IRS will implement the solution single integrated environment for managing business taxpayer accounts that shall:

· Retire and modernize legacy BMF applications, data files and databases.

· Replace the BMF Account Data Structures with a modern, secure, future-proof technology foundation that can rapidly scale.

· Conduct Business Tax Processing in a FedRamp high, cloud-based, data centric solution.

· Produce the minimal mandatory outputs necessary to Close the Accounting Cycle-

· Provide downstream consumers with a modern and secure method to access taxpayer data.

· Develop a repository that stores multiple representations of business taxpayer data to enable improved analytics.

· Provide downstream consumers with the means to conduct self-service reporting and analytics.

· Create reusable common services that perform account management functions.

· Migrate Users to leverage new data formats and services.

To assess the requisite capabilities, IRS conducted a series of vision and strategy working sessions. These sessions involved a multitude of stakeholders across Information Technology and Business. The resulting modernization strategy was based on the following five (5) factors:

a) Business Priorities

b) Architecture Principles and Design

c) Requirements and Assumptions

d) Form and Data Complexity

e) Process Complexity

C.1.2.1 Program Objectives

The objectives of the BMF Modernization Managed Services PWS include modernizing BMF business tax processing, enhancing data quality, and aligning the modernization efforts from third parties and government institutions. These primary objectives are to be considered for all work supported by the BMF Mod Managed Services PWS.

· Design and setup a Cloud infrastructure can be scaled up or down based on the Business Masterfile processing and Data Storage needs.

· Cloud infrastructure should provide the flexibility to choose the services and tools that meet the application processing and data storage requirements.

· High levels of reliability and uptime, which can help IRS to ensure that their services are always available to provide better service to the taxpayers.

· Cloud infrastructure should have robust security features and compliance certifications, to protect the data and meet both Cyber and FISMA requirements.

· Develop and deploy a relational and Analytical Database for BMF Modernization initiatives in FedRAMP high Cloud infrastructure as a managed database-as-a-service (DBaaS) for BMF transactions and Reporting purposes in a format mutually agreed by Contractor and the IRS.

Table 2 below lists the major BMF Mod Managed Services PWS objectives:

• Create MongoDB or any Massive Parallel Processing Databases in FedRAMP high Cloud environment for BMF transaction and Analytical purposes.

• More effective operational and analytical use of BMF Account aligned with the IRS data strategy

• Taxpayers and third-party business partners will be able to correct erroneous or incomplete information prior to downstream processes

• Use of Cloud and Open-Source tools found in the Enterprise Standards Profile (ESP) are encouraged. The ESP is the authoritative repository for IRS approved products and standards. Projects can select from pre-approved technology products and standards.

• Scalability: Cloud infrastructure can be scaled up or down based on the IRS needs. This allows organizations to handle sudden spikes in traffic or demand without having to invest in additional hardware.

• Flexibility: Cloud infrastructure provides organizations with the flexibility to choose the services and tools that meet their specific requirements. This allows organizations to customize their infrastructure to meet their unique needs.

• Reliability: Cloud providers offer high levels of reliability and uptime, which can help organizations ensure that their services are always available to their customers.

• Security: Cloud providers offer robust security features and compliance certifications, which can help organizations protect their data and meet regulatory requirements.

C.1.2.2 Transition Strategy Constraints

Modernization of end-to-end processing of BMF is too large and complex an effort to implement in a single release. In addition, BMF business tax processing must be available in each filing season with no breaks. Planning for this project is based on the assumptions and imposed constraints identified below. Assumptions and constraints are sources for candidate risks.

a) IRS may retain legacy applications for a limited time as a contingency to reduce risk.

b) Key decisions on scope and technical direction will be made by ES and AD project leads or escalated for decision to the Associate Chief Information Office (ACIO) or Contract Tracking & Oversight (CTO) levels.

c) A strategy for new technology insertion will be developed as technology is evolving and current technology may become obsolete as the BMF Mod effort progresses.

d) All organizations impacted by these changes will be ready to receive the updated systems and integrate the change.

e) Improve impact to downstream consumers of BMF to be more responsive to their workflow processes based on their consumption patterns.

f) IRS will meet its taxpayer digital experience modernization goals, while it incrementally modernizes components of the legacy BMF footprint.

All risks that affect cost, schedule and/or scope are managed according to IRS risk processes and are tracked in the Item Tracking Reporting and Control (ITRAC) system or other approved risk tracking system. The contractor’s Risk Management Plan (RMP) shall describe the processes, techniques, and tools to track, manage, and control project risks.

BMF Modernized processing shall also address changing IRS priorities and legislative initiatives. To mitigate risks introduced by these constraints, IR modernization will be accomplished based on current IRS priorities. Individual Task Orders and Optional Task Orders will provide the overall guidance, vision, business, and technical requirements for the scope of work to be performed. PWS Task Orders below define business and technical requirements for current IRS priorities..

The BMF Mod PWS will support the transition of legacy applications to a modern system and software architecture where feasible. Until the final End State is achieved, the end-to-end solution will leverage both modernized and legacy applications.

C.1.2.4 Notional Target State

The notional target state architecture maximizes the business value of the BMF Modernization by aligning to the Modernized Tax Account Management target state architecture and EA target state roadmap. The target state architecture pattern within the solution concept will enable accelerated development of future business capabilities through reusable services. The target state solution will be hosted in the cloud and seek to utilize cloud-native and managed services. BMF Mod PWS requirements follow the enterprise Modernization Plan direction of a modern system and software architecture to achieve enterprise IRS goals.

C.1.2.4.1 Business Process – Notional Target State

The Notional target state architecture moves from outdated technology to modern system and application architecture technology that can provide increased responsiveness to changing business and compliance needs.

Figure XX – BMF Notional Target State

C.1.2.4.2 Data – Notional Target State

The notional target state architecture will include a consolidated BMF enterprise data platform, which is hosted in a FedRamp Hight Cloud Infrastructure and the authoritative source of all the BMF Modernized Account Data. The data that will be stored on the modernized BMF data platform are the Account Data that are either modernized through the modernization process or converted from the legacy Files from Mainframe. The Notional Target State architecture will include the capability for the downstream consumers to access and use the data at will. Modernized services concerning Data Certification, and Compliance will be developed. Data distribution reporting will also be enhanced, such that information will become more accessible based on the user role and purpose. Access to data shall be governed by appropriate levels of system authentication and authorization methods and follow entity proofing standards. Perfection of data on BMF Data Platform, such as Artificial Intelligence, design thinking must be considered where appropriate to assist development, expansion, and maintenance of AD data, infrastructure, and tools for providing metrics and data analytics to enable data-driven decisions and support Big Data cloud readiness.

C.2 SCOPE OF WORK AND DESCRIPTION OF TASKS

The BMF Mod program has a continued need for (IT) support services. The purpose of this PWS is to provide a full range of contractor support services for Program/Project Management, Architecture/Engineering, Modernization Strategies, Development, Testing, and O&M related to the execution of the BMF current and future state infrastructure requirements. IRS IT will be the primary user of the contract to provide the full range of business tax processing support services for BMF Modernization related project and program level support.

The support required encompasses a specific set of services from local microcomputer applications to large-scale integrated legacy systems and newly developed systems. Services are required across virtually all software languages and hardware platforms. When applicable, care must be taken to coordinate with functional experts who are responsible to assure appropriate systems integration and compatibility.

2.1 TASK AREA 1, PROJECT AND PROGRAM MANAGEMENT SUPPORT

2.1.1 SUB-TASK 1- ORIENTATION BRIEFING

Within one week 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 award requirements and objectives.

The orientation briefing will be held at the Government’s facility or virtually and both parties will mutually agree upon the date and time.

The completion of this briefing shall result in the following:

· The Contractor and Government personnel who will perform work under this award will be introduced.

· The Government may provide information on how to obtain any GFP that will be issued to the contractor.

· Any issues concerning the Contractor clearances for Contractor personnel will be discussed.

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

· The Contractor shall provide the accounting period end dates to be used for the term of this award.

DESIRED OUTCOME - The objective of the briefing is to initiate the communication process between the Government and Contractor to assure a common understanding of award requirements and objectives. Contractor shall deliver Orientation Briefing Minutes to COR within 5 business days after Briefing. Contractor delivers Quality Assurance Surveillance Plan (QASP) to the COR within 30 business days after the Briefing.

2.1.2 SUB-TASK 2 - RAMP-UP KNOWLEDGE TRANSFER/TRANSITION-IN

Ramp-Up Knowledge Transfer is defined by the Contractor acquiring and understanding the necessary documentation, information, and processes related to any work in progress. This task includes meeting with the IRS Subject Matter Experts frequently to gather any tacit knowledge related to the Business Master File Modernization (BMF MOD) Program tasks. The government estimates this task will take approximately three months to complete after award.

The Contractor shall appoint a knowledge transfer manager to oversee the transfer of knowledge and ensure all areas are addressed. If desired, this can be the Project Manager (PM) or Project Scheduler. Prior to the transfer of knowledge, the Contractor shall develop a draft Knowledge Transfer Plan (KTP) and present it to the Government within the first 15 business days after award. The KTP shall identify the Contractor resources and roles involved in the transfer process, provide a list of risks and mitigation strategies for the transfer, and contain a detailed resource balanced project schedule developed with Microsoft Project. The project schedule shall identify tasks, dependencies, deliverables, and milestones. The project schedule shall be at a sufficient level of detail to track progress on a bi-weekly basis, (i.e., all tasks will be detailed to a level such that no task has duration of more than ten workdays).

The Government shall have 10 business days to review the draft KTP plan and provide comments to the Contractor. Government and Contractor representatives will then meet to discuss the comments after which the Contractor shall incorporate the agreed-upon changes and deliver a final KTP within 5 business days of the government’s feedback.

The contractor shall meet with the IRS bi-weekly (twice a month) to discuss the progress of the knowledge transfer. The Contractor shall show an updated MS Project Schedule and discuss any risks or concerns at this time.

DESIRED OUTCOME - The Contractor shall provide a Knowledge Transfer Plan that is accepted by the Government and successfully completes knowledge transfer in accordance with the plan and no later than three months after Government acceptance of the Knowledge Transfer plan.

2.1.3 SUB-TASK 3 - PROJECT AND PROGRAM MANAGEMENT SUPPORT

The contractor shall provide effective project management of all program activities to achieve desired cost, schedule, and technical performance and maintain customer satisfaction. The contractor shall complete tasks and provide the work products and deliverables based upon the agreed upon schedule with the expected level of detail and quality. The Program Management approach should achieve the expected IRS business outcomes in accordance with business requirement needs and goals for the BMF Mod program and should deliver end-to-end operations, providing the IRS with the lowest risk solution.

The program management (contract level) functions shall include but not be limited to having a broad and progressive knowledge of IT industry functions; business administration; contractual functions; human resources; and software development project management. This personnel solution shall also incorporate the coordination with all tasks under the direction of the Government Program/Project Manager.

The contractor shall institute and maintain a management structure to respond to and negotiate task requirements and associated levels of effort (LOEs) and skillsets. The contractor shall also maintain access to resources that can be called upon to fulfill task requirements under this contract.

DESIRD OUTCOMES: The Contractor shall perform all Program Management services associated with this task in accordance with IRS requirements outlined in the SOO. The Contractor shall submit all associated work products and deliverables associated with this task to the IRS timely and within the acceptable level of quality

2.2 TASK AREA 2, DEVELOPMENT, MODERNIZATION & ENHANCEMENT (DME) SUPPORT

Contractor shall work as part of an integrated IRS-led team, under the BMF MOD program. Contractor will provide continued programming development and legacy system support for Business Master File and its modernization activities. Contractor will also participate in meetings, perform research, resolve issues, and prepare presentations, input to ELC technical documentation and other communications as needed information and receive large data batches directly from the authoritative sources.

The contractor shall provide support to Masterfile area and its up and downstream subordinate areas to ensure accomplishment of the IRS’s goals. Support under this task may include but be not limited to the following:

2.2.1 ALC-to-Java Support

· Develop custom tool to decompose and map the business rules and requirements imbedded in current ALC code, PRPs.

· Provide support in ALC to Java efforts for projects developing or delivering solutions to be used for the conversion of ALC code to an interim language or through to Java code. This includes but is not limited to SME expertise to decompose and map the business rules and requirements imbedded in current ALC code, PRPs.

· Provide support in conducting Prototypes and or Proofs of Concept for any automated, semi-automated or manual solution for converting ALC code to any target language.

· Provide support in conducting assessments across the existing ALC code to determine the complexity of the existing code to assist Corporate Domain in the assessing and planning of implementation of ALC conversion projects.

2.2.2 CADE 2 TS2 Support

· Provide SME support to the Corporate Domain to assist other AD Domains in the transition of the CADE2 database throughout the TS2 phase.

· Provide programming support to assist in the implementation of legislative updates and or other changes based on policy or business decisions.

· Provide technical expertise to the Corporate Domain in the review of the CADE2 TS2 implementation. Provide support to business to validate requirements.

· Provide support in conducting performance testing on the target system.

· Provide development support in data modeling.

· Provide ETL support, reviewing and assessing technical solutions as it impacts Master File processing.

· Provide leadership in performing technical reviews of roadmaps, logical designs.

DESIRED OUTCOMES

Timely and accurately deliver program code changes based on documented release work request and break/fix problems identified by tickets and/or data review; Timely and accurately process daily transmittals including management approval and transmittal execution. Functional requirements are interpreted throughout the project and technical guidance is provided during the life cycle. Supports IMF modernization efforts converting IMF Legacy programs to an object-oriented program (such as Java) IRS identified staff receives the knowledge needed to maintain current IMF Systems Programs. Successful contract transition with no breaks in level of support; IRS-identified staff are able to maintain and assume responsibility of the relinquished material.

2.3 TASK AREA 3, ENTERPRISE SERVICES

The contractor shall provide effective provide support for BMF MOD program, in conjunction with the BMF MOD Program’s Requirements management Support, to analyze the requirements and collaborate with key IRS stakeholder groups to plan, prioritize, and implement the ECM Portfolio’s solutions’/products’ DVSs. Specifically, the Contractor shall provide the following support services:

2.3.2 IMF & BMF Requirements Management Support

The contractor shall provide expertise in development support of large complex data processing systems. Masterfile expertise is highly preferred. The contractor’s expertise and development support will include, but not be limited to the following activities:

· Provide analysis and programming support for Masterfile modernization efforts. Resources with the knowledge in Java should be brought in as needed to support the IMF and BMF Modernization efforts toward DevOps and Agile software engineering.

· It includes all support towards converting Legacy programs currently in O&M (coded in ALC, COBOL or C/C++) to Java (or other) as per guidance of the Enterprise Services for fulfilling the outlined target architecture.

· Supports the implementation and maintenance of modernized programs in Tier 2 environments.

· Provide support in knowledge transfer to designated Government personnel in developing the skill set necessary to maintain the implemented applications.

· Use existing requirements documents, code analysis tools, and code inspection to conduct logic harvesting, which includes producing testable and understandable requirements for inclusion in the requirements repository.

DESIRD OUTCOMES: The Contractor shall perform all requirement management support associated with this task in accordance with IRS requirements outlined in the PWS. Decompose and map the business rules and requirements imbedded in current ALC code, PRPs. When applicable, support modernization and transformation efforts toward DevOps and Agile software engineering by converting Legacy programs to an object-oriented program (such as Java).

3.1 SKILL REQUIREMENTS

The contractor will work on the following systems, hardware, and software:

1. ALC

2. Mainframe

3. JAVA development

4. ELC

5. SQL and Database development

6. JSON, XML

7. MongoDB

8. Spring Boot

9. Microservices

10. RESTFul Services

11. Rationale Suite

12. SharePoint

13. AWS/Azure Cloud

14. FedRamp High Compliance

15. PaaS

16. SaaS

17. IaaS

18. Microsoft Office Suite

19. Microsoft Project

20. Microsoft Visio

The contractor shall also demonstrate specialized experience that includes expertise in these areas:

a) Business Analysis disciplines

b) Process Re-engineering and flow development

c) Project Management with Agile/Scrum

d) Requirements Development

e) System Architecture in new and legacy products and systems

f) Transition Management

g) Systems, Data, Platform and Performance Engineering

4.1 GOVERNMENT-FURNISHED INFORMATION

GFI (to include manuals, notes, memos, instruction materials and other information) may be provided in the performance of this task order. The following GFI will be provided to the contractor upon task order award.

IRM 2.16.1, Enterprise Life Cycle (ELC) (2019-11-26)

IRM 2.5.1, Systems Development (2006-09-01)

IRM 10.8.6, Information Technology (IT), Application Security and Development (2018-11-18)

Upon completion of any resultant GSA order, disposition of GFP shall be in accordance with FAR 52.245-1.

5. ASSUMPTIONS AND CONSTRAINTS

Modernization of end-to-end processing of BMF is too large and complex an effort to implement in a single release. In addition, BMF business tax processing must be available in each filing season with no breaks. Planning for this project is based on the assumptions and imposed constraints identified below. Assumptions and constraints are sources for candidate risks.

5.1 ASSUMPTIONS

· A strategy for new technology insertion will be developed as technology is evolving and current technology may become obsolete as the BMF Modernization effort progresses.

· All organizations impacted by these changes will be ready to receive the updated systems and integrate the change.

· Improve impact to downstream consumers of BMF to be more responsive to their workflow processes based on their consumption patterns.

· IRS will meet its taxpayer digital experience modernization goal, while it incrementally modernizes components of the legacy BMF footprint.

· The BMF Modernization PWS will support the transition of legacy applications to a modern system and software architecture where feasible. Until the final End State is achieved, the end-to-end solution will leverage both modernized and legacy applications.

· Product vision, target-state architecture/design, and cybersecurity standards/expectations will be provided by IRS and specific business/technical requirements shall be elicited by the contractor.

· All risks that affect cost, schedule and/or scope are managed according through IRS risk processes and are tracked in the Item Tracking Reporting and Control (ITRAC) system or other approved risk tracking system. The IRS Risk Management Plan (RMP) (See IRS IRM Part 2.5.1) describes the processes, techniques, and tools that will be used to track, manage, and control project risks.

5.2 CONSTRAINTS

The Contractor shall comply with the following constraints, standards, and guidance (which may be provided upon request) for all efforts under this PWS:

· IRS must retain legacy applications for a limited time as a contingency to reduce risk and Tax processing data validation. Any data discrepancies between legacy and modernized solution will be addressed by the vendor.

· Key decisions on scope and technical direction will be made by IRS Enterprise Services (ES) and IRS Application Development (AD) project leads or escalated for decision to the Associate Chief Information Office (ACIO) or Contract Tracking & Oversight (CTO) levels. Any project scope changes will he handled by Contracting Officer Representative (COR). Due to the level of review and process there will be a substantial delay in regard to the timeline of decisions that can take up to 2 weeks for a decision.

· All BMF Mod project requirements must adhere Requirements Engineering Program Office (REPO) Guidelines and standards.

· Tools to be used in the performance of the work under the Task Order must be on the approved Enterprise Standards Profile (ESP) Standard Products List. Tools not on the list cannot be used until they go through the ESP approval process and are added to the list. This ESP approval processes will take 6-8 weeks for COTS product review and analysis. Software included in the ESP must be updated to align with technology shifts; this initiative is referred to as N/N-1:

· (‘N’) – The latest major release of a product that is commercially available from the vendor

· (‘N-1’) – The previous major release of a vendor product. This release is still within the product support period, but is not the most current released version of the product

· Development and Testing will be performed in IRS environments.

· IRS and contractor will define clear integration boundaries and responsibilities between systems and Contractors; full integration test shall occur in IRS environments prior to deployment.

· Contractor personnel shall create and socialize technical documentation (e.g., solution architecture, engineering design, API specs, security plan) with appropriate stakeholders. Final versions of technical documentations shall require IRS stakeholders’ approval.

· Contractor shall follow IRS DevOps process using existing IRS Source Code Control.

· Contractor shall follow IRS OneSDLC process to establish and maintain prevalent Milestone Review process.

· Contractor shall establish and maintain Knowledge Articles, Developers Guides, and Lessons Learned.

6. GOVERNMENT-FURNISHED PROPERTY (GFP)

GFP (to include material, equipment, and/or information) may be provided in the performance of this award order. The following GFP will be provided to the contractor:

At the end of this award order, disposition of GFP shall be in accordance with FAR 52.245.1.

7. GOVERNMENT-FURNISHED INFORMATION

GFI (to include manuals, notes, memos, instruction materials and other information) may be provided in the performance of this task order. The following GFI will be provided to the contractor upon award order.

INFORMATION ITEMS

Computer Operator Handbook (COH)

Program Requirements Package (PRP)

Schemas

Project Schedules

Sanitized taxpayer data

OMB and NIST Guidelines

OMB Enterprise Architecture Requirements

At the end of this award order, disposition of GFI shall be in accordance with FAR 52.245.5.

8. TRAVEL

No travel required.

9. ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

The work can be performed at contractor site; however, the primary location for the technical oversight team will be at New Carrollton’s NCFB. For key personnel, the vendor shall provide a matrix with location identified.

Primary Executive and program oversight team Location

NCFB

Service 5000 Ellin Road Lanham, MD 20706

Alternate Locations Enterprise Computing Center 250 Murall Drive Martinsburg, WV 25430

10. INSPECTION AND ACCEPTANCE

10.1 INSPECTION

The Contractor shall ensure that all deliverables are clearly marked with the order number and visible on all shipping/service documents, containers, and invoices.

Inspection will be at the same place as performance and delivery, unless otherwise specified.

10.2 GENERAL ACCEPTANCE CRITERIA

The general quality measures as set forth below will be applied to each work product received from the contractor under this award and any resulting orders awarded.

Accuracy - work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

Clarity - work products shall be clear and concise; engineering terms shall be used, as appropriate. All diagrams shall be easy to understand and relevant to the supporting narrative.

Specifications Validity - All work products must satisfy the requirements of the Government as specified herein.

Format - work products shall be submitted in hard copy (where applicable) and in media defined in the PWS. The work product format may be different in each award order. Hard copy formats shall follow Department of the Treasury and IRS Directives and shall be consistent with other similar efforts. All text and diagrammatic files shall be editable by the Government.

Timeliness - work products shall be submitted on or before the due date specified in the award order, or submitted in accordance with a later, scheduled date determined by the CO.

11. REVIEW OF DELIVERABLES

· The Government will perform an initial review of deliverables, and if problems are encountered during the review, the contractor must correct them. If necessary, a meeting may be convened to resolve any differences. The contractor shall make all required changes to achieve an acceptable deliverable. The Government will perform its review within approximately 15 calendar days from receipt of the deliverable or as otherwise specified in each award.

· When the review of a deliverable results in necessary modifications, the Government will, in accordance with the approved award schedule, provide the necessary documentation to correct the deliverable. It will then be the responsibility of the contractor to incorporate the comments properly and consistently in the final product.

· These procedures shall not be construed to constitute a waiver on the part of the Government of its rights under FAR Subpart 49.4, entitled “Termination for Default”, nor of any other rights or remedies provided by law or under this contract.

12. REVIEW PERFORMANCE REQUIREMENTS, STANDARDS AND SURVEILLANCE

The Government believes there is value in incorporating Performance-Based Service Acquisition (PBSA) methodology with an outcomes-based focus for this work.

13. PERFORMANCE REQUIREMENTS

Performance requirements include the Desired Outcomes and Required Services and are defined by the Government. This aligns the Contractor’s objectives with the Government objectives, which are to successfully complete the tasks and deliver value-added products and services to the end users.

14. PERFORMANCE AWARD ORDER REQUIREMENTS

The services and solutions delivered will be subject to the oversight of an IRS enterprise level governance structure and processes. The contractor shall warrant all work under this TO, taking necessary steps and precautions to perform the work to IRS’ satisfaction. The contractor shall be responsible for the professional quality, technical assurance, timely completion and coordination of all documentation and other goods/services furnished by the contractor under this TO. The contractor shall perform all work diligently, carefully, and in a good and workmanlike manner; shall furnish all necessary labor, supervision, machinery, equipment, materials, and supplies, shall at its sole expense obtain and maintain all permits and licenses required by public authorities, including those of IRS required in its governmental capacity, in connection with performance of the work.

The contractor shall be fully responsible for all work performed by subcontractors. Moreover, the contractor warrants that it possesses the knowledge, skill, experience, and financial capability required to perform and provide all Business Master File Modernization program related services. The contractor warrants that ETCS shall be performed in a skillful and respectful manner, and that the quality of all such services shall equal or exceed prevailing industry standards for the provision of such services. Furthermore, the contractor warrants that when fully implemented, shall be configured, and shall perform in accordance with the specifications applicable in the PWS.

The Contractor warrants and undertakes that any ETCS deliverables will be free from defects in material and workmanship and will conform to any specifications or requirements in the PWS. The contractor warrants that if any deliverable(s) fails to meet any such specifications or requirements or is otherwise nonconforming, the contractor will, at its own cost and expense and within 10 days of its receipt of written notice of such failure, either correct such deficiency or provide a plan acceptable to IRS for correcting such deficiency.

All deliverables will be subject to an inspection and acceptance by IRS. Each product shall include a warranty as specified in FAR Clause 52.246-17. In addition to FAR Clause 52.246-17, the following additional requirements apply:

· Users shall have highly reliable and maintainable products and system solutions to interoperate with the described environment.

· Components shall be maintainable by the user without voiding the warranty coverage.

· Components, which are expandable, shall be expandable by the user without voiding the warranty coverage provided the IRS adheres to standard commercial practices in accomplishing the additions.

The contractor warrants that any software provided will substantially conform to the specifications contained in the PWS for 90 days following delivery of the software. The system warranty shall ensure the full operational use of the system. The system warranty shall begin at the time the final system is approved by an authorized Government representative. The system warranty shall provide fault diagnosis, hardware and software repair, replacement, or redesign.

15. DELIVERIES OR PERFORMANCE

15.1 AWARD PERIOD OF PERFORMANCE

The period of performance of this award order shall be a base period of twelve (12) months from date of award, plus four (4) 12-month option periods.

15.2 DELIVERABLES

All contractor deliverables or work products shall remain categorized as "Official Use Only.” The release of any portion must be authorized in writing by the government.

“The contractor shall adhere to Section 508 of the Rehabilitation Act of 1973, which requires access to the Federal Government electronic and information technology.

The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. Federal agencies must ensure that this technology is accessible to employees and members of the public with disabilities. http://www.section508.gov/.

Each Electronic and Information technology product or service furnished under this PWS shall comply with the Electronic and Information Technology (EIT) Accessibility Standards (29 U.S.C. 87794(d)).

For every EIT product or service accepted under this award by the Government that does not comply with (29 U.S.C. 87794(d)), the contractor shall at the discretion of the Government, make every effort to replace or upgrade it with a compliant equivalent product or service, if commercially available and cost neutral, on either the planned refresh cycle of the product or service, or on the order renewal date, whichever shall occur first.”

Please note all Section 508 clauses are in attached.

15. DATA RIGHTS

Data rights refer to the Government’s exclusive license rights in two categories of valuable intellectual property, technical data and computer software delivered by vendors under this contract. The Federal Acquisition Regulations (FAR) prescribe policies, procedures and clauses Review all Security, Data Rights, and Compliance Clause and Provisions included within the RFTOQ and Federal Acquisition Regulations (FAR) data rights clause pertaining to data rights for civilian agencies.

Technical data (TD) includes any recorded information of a technical nature (e.g., product design or maintenance data, computer databases, and computer software documentation). Computer software includes executable code, source code, code listings, design details, processes, flow charts, and related material that would enable the software to be reproduced, recreated, or recompiled. All deliverables under the contract are the property of the U.S. Government for which IRS shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest. Any Contractor rights in the data or deliverables must be identified as required by FAR 52.227-11 through FAR 52.227-20.

· The agency obtains an “unlimited rights” license in noncommercial technical data, noncommercial computer software and noncommercial computer software documentation.

· The Government acquires the unlimited rights in all the data pertaining to BMF Mod, technical data, software code, component, architecture, process developed, functional code, licenses acquired using the Government funds etc.

As such, the objective is to have a product that is fully owned by the government, free of any proprietary dependencies, interfaces, or restrictions for use.

Acronyms

SB/SE

SC

SOI/RAAS

TIO

Page image1.png image2.svg Legend View Structure / Elements Business Area System Grouping System Enterprise Elements i.e., Common Services, EDP/AAP, and ODS boxes Data Flow Annotations Cloud – Landing Zone TBD Cloud Vendor Managed Software-as-a-Service TCloud / WC2 Functionality Transitioning to Modern Systems X Retired New Active Database / Data Store Data Common Service System Input / Output Legacy Intake RSPCC Paper Intake ISRP AIR ICMM G2G AMMPS SCRIPS Notices Integrated Taxpayer Experience Digital Services Validation and Perfection IRS Employees / Contractors ATFR AOIC ALSENTITY CATRS AIS ASFR WHCS E-Trak SS8 FUTA2 LDC ECM Exam Appeals Other Systems (CC, OPR etc.) ICS ACS IDRS AIMS RGS/CEAS ECS LWIS FUTA1 DEPDB SNAP SWETRS SAAS From GMF, GUF, NAP, MeF, Master Files, & EDP YK1 NRP To RGS / CEAS CDE CDW Manual Handoff to ECM for Exam Processing ACV To CDR LB&I Datamart / DCS2 IFSV LB&I 1446-6 ASTARS/OCI FPLP NFTRAC To CCS, ECM, EDP Enterprise Anomaly Detection (EAD) From Operational Data Stores, ECM and Internal Ops IDEA CIMIS AFTRAK LCA Common Services Operational Data Stores M-TRDB CADE 2 DB TRDB PT & WR DB DMF FATCA DB DEP DB IRMF REF/FOF DB TIF PMF IMF ANMF EPMF BMF CDR CPP (Common Perfection Process) AVS GMF / SCCF ERS GUF EFPPS TRO RTF CFOL CADE 2 Marketplace CADE 2 EPMF ANMF BMF IMF To CCS IMS AMS-1 IVES Chat Bot Live Voice Live Chat Secure Messaging Callback ICCE Webapps Seamless Experience EFTPS Treasury Criminal Investigation To ETRDB To Digital Enablement Platform ICCE Phones To CPP, GMF / SCCF Voice Bot NAP NAP used for verification by many systems IPM RRP Collections Determinations Digital Phone Payments From Operational Data Stores From BMF,ODS Collections Exam From CPP, EDP From SCRIPS From Operational Data Stores Digitalization IRIS Modern Intake Digital Enablement Platform OLNR NRPS CCS To DNL, NDS, Local Print Checks coming in from IRS Offices Info. Returns Tax Returns Tax/Info. Returns Scanning as Service Extraction as Service 1040 V - Coded, Lockbox Paper Returns, Correspondence, Remittances and Acknowledgments IVES Fax Paper Returns, Correspondence, Remittances and Acknowledgments IRs NOTCON EEFax As-Received DB, FBP, ECM, ERA… ERA Tax Ret. IRDB Dynamic UI (Web Forms) To Downstream Systems FBP To EDP, ECM ICM To EDP, ECM To NOTCON SERP AEF NDS ICCE TDS From ODS, EDP, Common Services, Seamless Experience To NAP, IDRS, NDS To AUR, CDW, ICS, and Printing SOR TIN Generation (ATIN, ITIN, EIN) Agent Desktop Contact Center To ECM, IRS Employees and Contractors From Omni-Channel CAPS FMIS IFS RRACS Financial Mgmt PTRAK JobSwap HRC BPMS WCMS ITRAC ServiceNow BEARS IT Mgmt BriefBank CASE MIS GDI RS Asset Mgmt Legal HR Mgmt Ent. Strat TL-CATS ServiceNow MeF IRPS Automated Dialer BBTS AUR IRDM Refunds / Payments Credit Registration / Search / Claim Submission BOLA IOLA DNL ITA/ITLA TPA Unauthenticated / Authenticated Doc Upload Case Management Compliance Tax Account Management Intake Customer Service Internal Operations As-Received Bus. Tax Return Info. Return Tax Account IT-Ops IT-Portfolio Data Preparation & Exploratory Analysis Employee Model Training & Validation Trustworthy AI Services & Deployment Model Creation &Testing AAP Data Mesh Data Virtualization Data Integration Data Visualization Procurement Raw Landing Zone Data Staging Zone Refined Data Zone Case TXP Interaction Ind.