I_5 Attachment 3 - DRAFT PWS Enterprise Systems Unisys Support 2-24-2022.docx

Internal Revenue Service, Performance Work Statement Enterprise Systems Unisys Support

Performance Work Statement Enterprise Systems Unisys Support

Performance Work Statement Enterprise Systems - Unisys Support

Project: IT-ENTEPRISE-SYSTEMS-UNISYS-SUPPORT

Section 1.0 – Intentionally Blank

2.0 INTRODUCTION AND BACKGROUND

INTRODUCTION

The Internal Revenue Service (IRS) mission is to provide America’s taxpayers with top-quality service by helping them to understand and to meet their tax responsibilities and while enforcing the law with integrity and fairness to all.

Enterprise Systems – Unisys Support (ESUS) is a PROCUREMENT that will effectively acquire Enterprise Mainframe Infrastructure Modernization and Enhancement (EMIME) and Operations & Maintenance (O&M) support for the IRS.

The ESUS PROCUREMENT will service IRS Organizations to include Treasury with IT Enterprise Operations (EOps) – Enterprise Server Division (ESD) as the principal user. ESUS Task Orders will support new Enterprise Mainframe Infrastructure Modernization and Enhancement (EMIME) efforts and new/existing Operations & Maintenance (O&M) IT Services for IRS IT operating environments. Vendor support is required for a wide range of design, development, implementation, operations, and maintenance tasks.

In conclusion, The ESUS program requires vendor expertise to provide end to-end support with Unisys mainframes and technologies for the delivery of IT capabilities. The ESUS foundation may expand in the future as innovations are introduced.

BACKGROUND

The IRS Information Technology (IT) mission is to deliver IT services and solutions that drive effective tax administration while ensuring public confidence. The scope of effort spans across the IT ACIO-EOps ESD area for the period of performance.

· Enterprise Operations (EOps) supports the mainframe and server environment by providing efficient, cost-effective, secure, and highly reliable server and mainframe services for all IRS business entities and taxpayers.

Through Agile and cost-effective solutions, such as cloud migrations, platform standardization, common services, modernization, and infrastructure retirement, ESUS will lead the way to a world class modernized, efficient, end user-oriented and legislative responsive system.

3.0 OBJECTIVES

The Contractor shall support the objectives for ESUS by developing, modernizing, and maintaining IT capabilities with a full range of services and infrastructure.

3.1 The scope of work for this requirement is set forth as a collection of task areas necessary for successful project planning, management, and execution. This PROCUREMENT does not support the issuance of task orders exclusively for Project Management Support. For this PROCUREMENT, Project Management Support is defined as internal support to each respective task order. The task order areas are as follows:

Task Area 1: Project and Program Management Support Task Area 2: Enterprise Mainframe Infrastructure Modernization & Enhancement (EMIME) Support Task Area 3: Sustainment - Operations & Maintenance (O&M) Support Task Area 4: Services Management Support Task Area 5: Transition Support Task Area 6: Surge Support

3.1.1 Adherence to Regulations and Policies. All work performed shall be in conformance with all Government regulations and policies including the Federal Acquisition Regulation (FAR), Department of the Treasury Acquisition Regulation (DTAR) and other agency supplemental regulations and policies as appropriate.

3.1.2 The contractor shall provide support services regardless of the selected engineering lifecycle path, methodology or approach for development and delivery of program capabilities. IRS development paths may include Agile, Waterfall, Iterative, Commercial-Off the-Shelf (COTS), Managed Services, or other IRS approved paths.

Capability development and delivery may be accomplished by using traditional, largely sequential or waterfall-based approaches, as well as more iterative and incremental approaches that include leveraging Agile and Development Operations (DevOps) principles, methodologies, practices and tools. The contractor shall assist the IRS in defining, managing, and executing strategies that result in the delivery of high-value, high-quality IT services and capabilities to meet both existing and emerging IRS business needs.

4.0 SCOPE OF WORK AND DESCRIPTION OF TASKS

The scope of this PWS encompasses Contractor support for EOps and IRS IT activities including, but not limited to, Unisys mainframe support, project management, customer consultation/coordination, enterprise infrastructure design, requirements specification analysis, planning, application development, Enterprise Life Cycle (ELC) processes and documentation, and similar complex services in support of IRS IT missions, cybersecurity, and future studies such as cloud, architecture, and infrastructure.

The IRS mission requires a Contractor that demonstrates expertise in areas such as Unisys mainframe support, enterprise infrastructure, program and project planning, applications, databases, associated utilities for service-wide communications, program management and administration. In addition, the contractors shall demonstrate performance measurements, cost reporting, and recommended solutions based on understanding of IRS’s information architecture, infrastructure, and organization.

As the federal agency that collects taxes and administers internal revenue laws, the Internal Revenue Service (IRS) is required to administer the tax provisions included in all legislation. The Contractor will provide services to support current tax code IT enterprise infrastructure and build new enterprise infrastructure that does not exist in tax administration today.

The contractor will be responsible for operating & maintaining systems and upgrading key enterprise IT Systems designed to carry out legislative changes.

DESCRIPTION OF TASK AREAS

The contractor will provide expertise, knowledge, and skills relating to Unisys mainframe operations & maintenance, system hardware and software maintenance engineering support to deliver performance in accordance with the Performance Work Statement (PWS).

The activities and responsibilities of the contractor will include those identified under the task areas listed below. Specific activities and deliverables shall be fully defined in individual task orders.

4.1 Task Area 1, ESUS Project/ Program Management Support

The contractor shall provide project/program management (PJM/PGJM) support services to successfully facilitate planning, management and execution of tasks associated with planned and awarded task orders under this procurement. This support consists of activities and artifacts consistent with the IRS Enterprise Lifecycle path. These artifacts may include:

· Regularly updated (weekly) dashboard of ESUS activity data to include on-boarding of new contractors, performance monitoring and reporting

· Regularly updated (weekly) dashboard of Task Order activity data to include performance monitoring and reporting to support the following:

· Intakes

· Requirements

· Delivery partner integration for key initiatives

· Ensure tracking, reporting, and execution of task order intakes, in process, and completed activities

· Continuous process improvement and communications to achieve and maintain effective service delivery and alignment recommendations.

· An annual, planning baseline of activities and criteria to assist the Government in planning for orders transitioning in or out of the procurement.

· Quarterly Program and Fiscal Reviews of the ESUS task order activity.

Representative Activities shall include:

· On a bi-weekly basis, meet with COR to discuss ongoing task matters and resources to support contract.

· Review and approved subcontractor invoices.

· Review and sign off on all new requirements

· Coordinate with COR to get SMART ID badges and minimum background investigations (MBIs) renewals for all team members.

· Create Tracker, forecasting and invoice reports

· Review and audit ESUS Task Order (TO) process documentation.

· Provide Enterprise Life Cycle (ELC) support to include ensuring Capability Maturity Model Integration CMMI guidelines are met, and all data is recorded and archived based on task order needs.

· Prepare and submit Status Reports

· Provide timesheet reports via Excel workbook

· Develop an Integrated program schedule and work breakdown structure (WBS)

· Financial project tracking reporting

· Review, comment, and coordinate responses to draft deliverables.

· Develop and manage IT project specific schedules.

· Create, manage, and maintain the program Integrated Master Schedule (IMS).

· Provide schedule analysis, including critical path analysis.

· Provide updates for project issues and action items in a weekly status report to AD managers.

· Meetings will include, but not limited to:

· Bi-weekly Meetings with CORs to discuss invoicing, subtask assignments, projections, etc.

· Status Meetings with project leads

· Develop, update, and document all processes in use on the program, and facilitate regular reviews and updates to ensure currency and accuracy.

· Address and document or update the for existing programs:

· The critical success factors, associated metrics, technical performance measures and criteria.

· The methods by which validation will occur in accordance with IRS guidelines.

· Implement a test plan(s) that conform to IRS test procedures. The primary objective of the system test is to validate that the Unisys mainframe meets the specified requirements of the customer and will perform satisfactorily in the customer’s environment.

· Prepare Task Order Status Report (TOSRs) for all subtasks and Government Furnished Equipment (GFE) inventory and Burn Rate report.

· Address RACF (Resource Access Controls Facilities) Violation Reports.

· Develop invoice reconciliation reports

DESIRED OUTCOMES – Provide technical capability to support multiple enterprise infrastructure team efforts and the goals of the Program.

· Successfully support the project management office with required documentation by agreed upon scheduled due dates.

· Project/Program management support activities are effective and completed on schedule and in accordance with the business requirements.

· Program control, billing functions, scheduling and quality management is provided to ensure successful management of all ESUS tasks.

· Labor mix is controlled in an efficient and effective manner, maintaining personnel with skillsets to meet task orders desired outcomes, and maintain a minimum personnel turnover below 50% except to add to the Government’s new or updated requirements.

4.2 Task Area 2, Enterprise Mainframe Infrastructure, Mainframe Modernization and Enhancement (EMIME) Support

The contractor shall support and advise technical enterprise infrastructure activities across EOps ESD for key initiatives. The contractor shall provide EMIME strategic and tactical planning, coordination, and technical expertise support as it relates to the following:

· Current Unisys Mainframe Operating Environment (Test/Development/Test/Production/Disaster Recovery) hardware, software, subsystems, and components

· Modernization Systems

· IRS business requirements and processes

· Configuration Management activities

· Integrated and Project Scheduling

· EOps security tasks

· Section 508 Compliance and Accessibility Testing

· Creation & maintenance of End-User support materials

· Cybersecurity scanning and testing support

· Automation

Representative Activities shall include:

· Support legislative mandates and critical system changes by using current as well as cutting-edge technology including, but not limited to, Cloud Computing, DevOps, commercial platforms, and support of contingency operations.

· Design, develop, deploy, and implement new infrastructure interfaces/data sources that do not currently exist to ensure data received/data delivered can be interpreted/translated/accepted.

· Design, develop, deploy, and implement new functionality based on business requirements not currently existing to ensure data received/data delivered can be interpreted/translated/accepted.

· Analyze, modify, and modernize legacy software programs by developing original Unisys Assembly Language, COBOL, IRS Local Code (modifications to the Unisys mainframe OS 2200 and other Unisys commercial-off-the-shelf (COTS) products required for ECCS Unisys processing) applications.

· Develop and document Unisys mainframe operating environment hardware and software requirements, and perform other necessary analytical, hardware and software engineering, and/or development life cycle tasks.

· Support thought leadership, information sharing and data driven/executive decision-making; as well as contribute to IRS initiatives such as, but not limited to, resiliency and continuity.

· Identify and present common or leading practices from federal and commercial enterprise infrastructure and/or consulting organizations that may serve as solutions to the Unisys mainframe requirements.

· Use current best practices and/or develop innovative techniques to provide continuous improvement to support EOps initiatives, processes, and practices.

· Support IRS Unisys mainframe services coordination between EOps ESD and other departments throughout the IRS.

· Conduct requirements analysis, definition and decomposition activities as required.

· Maintain constant communication and coordination with the Government to ensure the requirements are clear and understood.

· Create, maintain, and revise design documentation and business rules or processes.

· Provide services, including project management, system processes and capabilities, daily, weekly, monthly, and annual load processing, requirements management and security support.

· Develop processes to support applications or components after delivery to correct defects, maintain performance and compatibility with other elements in the technical environment.

· Support system fault, defect or bug fixing and the associated regression testing to ensure critical defects have been corrected prior to deployment.

· Provide analysis, design, and development services to gradually retire identified stovepipe legacy projects and convert business required functions to modernized capabilities based on the IRS Strategic Plan and IT Modernization Plan.

· Provide analytical and technical support for Unisys mainframe operating environments to include support for annual updates to the configuration management database (CMDB), drafting, reviewing, revising ELC and Capability Maturity Model Integration (CMMI) Level 3 required artifacts, support for annual Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA), including collecting and authoring required documentation, resolving issues identified by auditors, attending CCB meetings and addressing issues identified by CCB that impact IRS Systems.

· Provide impact assessments of proposed changes to established baselines, testing strategies, and captured metrics.

· Development of new or updated Unisys mainframe hardware and software components in response to work requests, change requests, or support of technical assessments, problem management and resolution of production defects.

· Development of scripts and related artifacts for movement of data between tiers.

· Conduct unit, integration, and regression testing for Unisys mainframe changes, creating test data, and conducting and documenting development of manual automated test cases, and support Government acceptance testing.

· Correct any problems uncovered during Enterprise Systems Testing (EST) efforts.

· Support post-implementation analyses to determine if Unisys mainframe implementation goals have been achieved.

· Successfully complete the development, integration, test and deployment of programs and any future legislative initiatives.

· Support in requirements and user story development, decomposition, and planning.

· Participate in joint reviews to refine the Product Backlog.

· Utilize tools that support use of agile methodology to include visualization of product portfolio, product backlogs, iterative planning and performance reporting and monitoring.

DESIRED OUTCOME – The Contractor shall increase quality and sustainability of Unisys mainframe IT solutions and support with no degradation of functionality, or performance from the current levels. The Contractor shall provide Development, Modernization and Enhancement practices and controls that allow programs to effectively establish and maintain control of the following:

· Program status

· Execution

· Costs

· Schedule The Contractor shall successfully complete the deployment of scheduled releases to include receiving milestone exit approval for deployment. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances delivery as measured by portfolio-wide efficiencies, visibility into infrastructure-level development to include velocity and testing.

4.3 Task Area 3, Sustainment – Operations and Maintenance (O&M) Support The contractor shall provide sustainment, operations, and maintenance support to the IRS EOps Unisys mainframe operating environments. Support shall include O&M services under the following areas, which are, but not limited to:

· Unisys Software, Hardware, Subsystems, and Component Support

· Third Party Software, Hardware, Subsystems, and Components Support

· Unisys Database Support

· Unisys Communications and Network Software Support

· Production Status Support

· Disaster Recovery Support

· Product End-of-Life including but not limited to activities such as decommissioning support, and disposal

· Section 508 Compliance and Accessibility Testing

· COTS Software (SW) License and Maintenance Services

· COTS Hardware (HW) License and Maintenance Services

· Creation & Maintenance of End-User support materials

· Network Support

· Cybersecurity scanning and testing support

· Automation Services

Representative activities shall include:

· Provide O&M services for Unisys mainframe system processes and capabilities by daily, weekly, monthly, and annual load processing, requirements management and security support.

· Develop processes to support the current IRS Unisys mainframe operating environment to correct defects, maintain performance and maintain compatibility with other elements in the technical environment.

· Support bug fixing and the associated regression testing to ensure known critical defects have been corrected prior to deployment.

· Provide analysis, design, and development services to gradually retire identified stovepipe legacy projects and convert business required functions to modernized capabilities based on the IRS Strategic Plan.

· Provide analytical and technical support for Unisys mainframe operating environments during operations and maintenance, to include:

· Impact assessments of proposed changes to established baselines, testing strategies, and captured metrics.

· Development of new or updated components in response to work requests, change requests, production defects technical assessments, problem management and resolution of product defects.

· Development and maintenance of scripts and related artifacts for movement of data between tiers.

· Conducting unit, integration, and regression testing for infrastructure changes, creating test data, and conducting and documenting development manual and automated test cases, and support of Government acceptance testing.

· Correct any problems uncovered during EST efforts.

· Support post-implementation analyses to determine if implementation goals have been met, reports distributed, and key stakeholders appraised.

· Support the IRS’s established Configuration Control Board (CCB) for controlling the functional and allocated baselines and the development configuration.

· Adhere to the IRS Enterprise Lifecycle (ELC), Internal Revenue Manuals (IRMs), applicable agency and Government regulations and guidance.

· Legislative Mandates support.

Desired Outcome: Sustainment Operations to include O&M and related efforts are adequately supported, ensuring minimization and mitigation of program risks and deficiencies. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances delivery as measured by portfolio-wide efficiencies, visibility into infrastructure-level development to include velocity and testing.

4.4 Task Area 4, Service Management

The contractor shall support Configuration Management (CM) functions including Unified Work Request (UWR) activities, Engineering Review Board (ERB) activities, Change Control Board (CCB) activities, business rule changes, configuration identification, configuration control, configuration status accounting and configuration audits.

Representative activities shall include:

· Track and document all configuration items included in baseline releases during

· Design integration, testing, fielding and sustainment.

· Provide CM, quality assurance, and sustainment of all documentation.

· Update Implementation Packages accordingly.

· Develop Audit Plans and Reports, prepare and perform Audit Checklist activities.

· Meet Government acceptance criteria for configuration management.

· Service Desk Support for hardware and software repairs/fixes

Desired Outcome: Consistent configuration management that implements standard documentation and reporting methods and provide a single logical view of all IT components and connections needed to effectively deliver IT services to customers. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances code delivery as measured by portfolio-wide efficiencies, visibility into application-level development to include velocity and testing.

4.5 Task Area 5, Transition Services

The contractor must provide transition services defined as transition-in and transition-out needed to accomplish knowledge transfer and ramp up activities to develop, operate and manage the IRS IT programs. It is imperative that the incoming contractor works with the incumbent contractor(s) to ensure a smooth transition with minimal disruption to services and support for the Program Office, internal and external stakeholders, and delivery partners. The purpose of the transition is to transfer expert knowledge, data and artifacts that are used to support the programs from the incumbent contractor to the successor contractor or to the Government efficiently.

Representative activities shall include but not be limited to:

· 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 reports

· Planned activities, issues encountered and identified risks.

· Transfer complete documentation for all delivered functionalities. Deliverables shall be in softcopy and hardcopy format 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.

· Knowledge transfer of all configurable data including application settings, integrations, and interfaces.

Desired Outcome: All task order efforts are transitioned timely, seamlessly, and completely from the incumbent contractor to the successor contractor and/or Government personnel without a lapse in services provided or delays in scheduled performance.

4.6 Task Area 6, Surge Support

The Contractor shall be capable of providing surge support during the base or any option period, for unplanned, in-scope work. In the event the Government determines that an increased quantity of support is required for the task areas defined in the PWS, the Government reserves the right to exercise the Surge Option unilaterally on both Firm Fixed Price and/or Labor Hour Support basis.

Representative surge activities will be defined at the Task Order Level

Desired Outcome: The contractor will be able to rapidly respond to Government requirements of unplanned, in-scope work with the appropriate teams & qualified resources capable of delivering capabilities across all task areas. The contractor must have experience with Information Technology Infrastructure Library (ITIL) to provide Metrics leadership support that enhances delivery as measured by portfolio-wide efficiencies, visibility into infrastructure-level development to include velocity and testing.

5.0 SKILL REQUIREMENTS

In addition to any pre-defined labor categories, which are anticipated as necessary to fulfill the Government’s requirements, the Contractor is expected to provide expertise, knowledge, and skills relating to Unisys mainframes, software development, component testing (both functional and integration testing), modernization, enhancements, project management, developmental upgrades, and hardware maintenance of the Unisys mainframe systems services.

The Contractor staff shall have the ability to support the maintenance and enhancements of existing Unisys mainframes which include future design approaches using the IRS iterative development methodology. Contractor resources shall be able to provide expert design and implementation solutions for enhancements during application/system design sessions and the subsequent update to technical design documents as requested by the government.

The Contractor will work on the following systems, hardware and software, and shall possess or describe how it will obtain and provide specialized resources with experience listed, but not limited, to the following:

· Unisys Dorado

· Unisys ClearPath OS 2200

· Unisys Executive Control Language (ECL)

· Unisys Interactive Processing Facility (IPF)

· Unisys Message Queuing (MQ)

· Unisys CMplus

· Unisys Meta-Assembler (MASM)

· Unisys Compiling System (UCS) PLUS

· Unisys @PAS

· Unisys @PADS

· Unisys COBOL

· Unisys Symbolic Stream Generator (SSG)

· Unisys Data Management Systems (DMS)

· Unisys Relational Data Management Systems (RDMS)

· Unisys Universal Database System (UDS) suite of products (UDSC, DMS, RDMS, UREP, & SFS)

· Unisys communication interfaces (ATIS, CIFS, CITA, COMAPI, CPCOMM, CPCOMMOS, DDP, EOM, ICI, SILAS, & WebSphere MQ)

· Brocade

· Dell/EMC DLm

· Dell/EMC VMAX

· ASP.Net

· C and C++

· Java

· VB.NET (.Net Framework)

· Windows Server 2012 & 2019

· SQL Server 2019

· TeamQuest

· SightLine

· SMA OpCon

· IPv6 Internet Protocol

· InfoConnect

· Standard PC software:

· Microsoft WORD

· Microsoft Excel

· Microsoft Project

· Microsoft ACCESS

· Microsoft PowerPoint

· Microsoft Outlook

· Microsoft VISIO

· Knowledge Incident/Problem Service Asset Management (KISAM)

· Expert knowledge of Unisys OS 2200 Series Software and third-party software developed for Unisys users. This includes, but is not limited to, the following: COBOL (UCOB/ACOB), Unisys Collector (MAP), the Linking System (LINK), Transaction Processing (TIP), File Administration System (FAS), Meta-Assembler (MASM).

· Expert knowledge of MASM and PLS is required. Also required, is a working knowledge in other languages used in Consolidation customized code (e.g., ALN, VTH utilities) and skills/experience in the diagnosis of programming errors resulting from this customized code.

The contractor must have experience and knowledge with federal agencies services such as:

· Information Technology Infrastructure Library (ITIL)

· Performance/capacity planning and engineering

· Database design and development

· Unisys Mainframe systems engineering and development with particular regard to the IRS' Tier 1 Mainframe Operating Environment

· Web technology

· Federal financial policy and procedure, specifically IRS financial policy and procedure

· IRMs

· IRS Software Development Life Cycle

· IRS interface processes

· IRS system security procedures specifically with regard to Unisys mainframes

· Designing applications and systems using AWS and Azure Cloud Infrastructure

· Software Design and Data Modeling

· Infrastructure Architecture Expertise including industry research, architectural studies, and alternatives of analysis experience.

· Managing shared infrastructure services

· Architecting solutions for Cloud Based Services such as ServiceNow

· Enterprise Lifecycle (ELC)

6.0 SECTION 508 OF THE REHABILITATION ACT

This PROCUREMENT will be applicable to Section 508 Compliance, under Section 508 of the Rehabilitation Act Amendments of 1998, and the Architectural and Transportation Barriers Compliance Board’s Electronic and Information Technology (EIT) Accessibility Standards at 36 Code of Federal Regulations Part 1194. Federal agencies, when developing, procuring, maintaining, or using EIT are required to ensure that EIT products and/or services provide access to both Federal employees and members of the public with disabilities. Federal employees and members of the public with disabilities must have access to and use of information and data comparable to those without disabilities.

The contractor shall provide products or product support services that supports 100% Section 508 compliance at the time of delivery. The Agency’s requirement is that all products delivered under this PROCUREMENT shall fully meet Section 508 requirements within the term of the Task Orders.

The contracting officer shall apply the applicable Internal Revenue Service’s Acquisition Procedures (IRSAP) to comply in this PROCUREMENT.

6.1 IR1052.239-9000 Section 508 Information, Documentation and Support (Dec 2019)

In accordance with 36 CFR, Appendix C to Part 1194, the information and communication technology (ICT) products and product support services documentation furnished in performance of this contract shall be provided at no additional cost. The contractor shall provide information, documentation, and support relative to the supplies and services as described in the statement of work, performance work statement or statement of objectives (select one). The following technical standards and provisions have been determined to be applicable to this contract:

_X__ Chapter 6: Support Documentation and Services _X__ 601 General _X__ 601.1 _X__ 602 Support Documentation _X__ 602.1 _X__ 602.2 _X__ 602.3 _X__ 602.4 _X__ 603 Support Services _X__ 603.1 _X__ 603.2 _X__ 603.3 (End of clause)

6.2 IR1052.239.9002 Section 508 Services (Dec 2019)

All contracts, solicitations, purchase orders, delivery orders and interagency agreements that contain a requirement of services which will result in the delivery of a new or updated information and communication technology (ICT) item/product must conform to the applicable provisions of the appropriate technical standards in 36 CFR, Appendix C to Part 1194, and functional performance criteria in 36 CFR Chapter 3, unless an agency exception to this requirement exists at E202 General Exceptions.

The following technical standards and provisions have been determined to be applicable to this contract:

_X__ Chapter 4: Hardware _X__ 401 General _X__ 401.1 _X__ 402 Closed Functionality _X__ 402.1 _X__ 402.2(1-6) _X__ 402.3 ___ 402.4 ___ 402.5 _X__ 403 Biometrics _X__ 403.1 _X__ 404 Preservation of Information Provided for Accessibility _X__ 404.1 _X__ 405 Privacy _X__ 405.1 _X__ 406 Standard Connections _X__ 406.1 _X__ 407 Operable Parts _X__ 407.1 _X__ 407.2 _X__ 407.3 _X__ 407.4 _X__ 407.5 _X__ 407.6 _X__ 407.7 _X__ 407.8 ___ 408 Display Screens ___ 408.1 ___ 408.2 ___ 408.3 _X__ 409 Status Indictors _X__ 409.1 _X__ 410 Color Coding _X__ 410.1 _X__ 411 Audible Signals _X__ 411.1 ___ 412 ICT with Two-Way Communication ___ 412.1 ___ 412.2 ___ 412.3 ___ 412.4 ___ 412.5 ___ 412.6 ___ 412.7 ___412.8 ___ 413 Closed Caption Processing Technologies ___ 413.1 ___ 414 Audio Description Processing Technologies ___ 414.1 ___ 415 User Controls for Captions and Audio Descriptions ___ 415.1 _X__ Chapter 5: Software _X__ 501 General _X__ 501.1 _X__ 502 Interoperability with Assistive Technology _X__ 502.1 _X__ 502.2 _X__ 502.3 _X__ 502.4(A-G) _X__ 503 Applications _X__ 503.1 _X__ 503.2 _X__ 503.3 _X__ 503.4 _X__ 504 Authoring Tools _X__ 504.1 _X__ 504.2 _X__ 504.3 _X__ 504.4 _X__ Chapter 7: Referenced Standards _X__ 701 General _X__ 701.1 _X__ 702 Incorporation by Reference _X__ 702.1 ___ 702.2 _X__ 702.3 _X__ 702.4 ___ 702.5 _X__ 702.6 ___ 702.7 ___ 702.8 ___ 702.9 _X__ 702.10

The standards do not require the installation of specific accessibility-related software or the attachment of an assistive technology device, but merely require that the ICT be compatible with such software and devices so that it can be made accessible if so, required by the agency in the future.

The following functional performance criteria (36 CFR Chapter 3) apply to this contract.

_X__ Chapter 3: Functional Performance Criteria _X__ 301 General _X__ 301.1 _X__ 302 Functional Performance Criteria _X__ 302.1 _X__ 302.2 _X__ 302.3 _X__ 302.4 _X__ 302.5 _X__ 302.6 _X__ 302.7 _X__ 302.8 _X__ 302.9 (End of clause)

6.3 IRSAP IR1052.239-9003 SECTION 508 ACCESSIBILITY OF INFORMATION AND

COMMUNICATION TECHNOLOGY (100% COMPLIANCE) (DEC 2019)

Each information and communication technology (ICT) product or service furnished under this contract shall comply with the Information and Communication Technology Accessibility Standards (36 CFR, Appendix C to Part 1194). If the Contracting Officer determines any furnished products or services are not in compliance with the contract, the Contracting Officer will apply the remedies described under FAR 52.246-2, Inspection of Supplies – Fixed Price or FAR 52.246-4, Inspection of Services – Fixed Price.

The following technical standards and provisions have been determined to be applicable to this contract:

___ Chapter 4: Hardware ___ 401 General ___ 401.1 ___ 402 Closed Functionality ___ 402.1 ___ 402.2(1-6) ___ 402.3 ___ 402.4 ___ 402.5 ___ 403 Biometrics ___ 403.1 ___ 404 Preservation of Information Provided for Accessibility ___ 404.1 ___ 405 Privacy ___ 405.1 ___ 406 Standard Connections ___ 406.1 ___ 407 Operable Parts ___ 407.1 ___ 407.2 ___ 407.3 ___ 407.4 ___ 407.5 ___ 407.6 ___ 407.7 ___ 407.8 ___ 408 Display Screens ___ 408.1 ___ 408.2 ___ 408.3 ___ 409 Status Indictors ___ 409.1 ___ 410 Color Coding ___ 410.1 ___ 411 Audible Signals ___ 411.1 ___ 412 ICT with Two-Way Communication ___ 412.1 ___ 412.2 ___ 412.3 ___ 412.4 ___ 412.5 ___ 412.6 ___ 412.7 ___ 412.8 ___ 413 Closed Caption Processing Technologies ___ 413.1 ___ 414 Audio Description Processing Technologies ___ 414.1 ___ 415 User Controls for Captions and Audio Descriptions ___ 415.1 _X__ Chapter 5: Software _X__ 501 General _X__ 501.1 _X__ 502 Interoperability with Assistive Technology _X__ 502.1 _X__ 502.2 _X__ 502.3 _X__ 502.4(A-G) _X__ 503 Applications _X__ 503.1 _X__ 503.2 _X__ 503.3 _X__ 503.4 _X__ 504 Authoring Tools _X__ 504.1 _X__ 504.2 _X__ 504.3 _X__ 504.4 _X__ Chapter 7: Referenced Standards _X__ 701 General _X__ 701.1 X___ 702 Incorporation by Reference __X_ 702.1 ___ 702.2 _X__ 702.3 __X_ 702.4 ___ 702.5 ___ 702.6 ___ 702.7 ___ 702.8 ___ 702.9 _X__ 702.10

The standards do not require the installation of specific accessibility-related software or the attachment of an assistive technology device, but merely require that the ICT be compatible with such software and devices so that it can be made accessible if so required by the agency in the future.

The following functional performance criteria (36 CFR Chapter 3) apply to this contract.

_X__ Chapter 3: Functional Performance Criteria _X__ 301 General _X__ 301.1 _X__ 302 Functional Performance Criteria _X__ 302.1 _X__ 302.2 _X__ 302.3 _X__ 302.4 _X__ 302.5 _X__ 302.6 _X__

302.7 _X__ 302.8 ___ 302.9 (End of Clause)

7.0 DELIVERABLES

PROCUREMENT Kickoff Meeting

7.1 Within five (5) business days of award, the contractor shall conduct an orientation briefing for the Government. The orientation briefing shall be held at the Government’s facility or via teleconference. The intent of this meeting is to initiate the communication process between the IRS and the contractor by introducing key participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of PROCUREMENT requirements and objectives.

The meeting shall include: An introduction of those in attendance, discussion of the successful contractor’s approach and plan for scope of work and Point of Contact that will be responsible for direction and coordination with government regarding changes, concerns, and/or updates to their overall PROCUREMENT management. The contractor shall provide meeting notes (inclusive of any follow-up actions) to the Government within five (5) business days after the meeting.

7.2 Table 1: In support of this PROCUREMENT, the following deliverables will flow down to Task Orders (as applicable) and should not be considered all inclusive

7.2.1 Task Order Level Deliverables

All task orders issued under the PROCUREMENT will have task order specific 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 deliverables and work products will be provided in electronic format and shall comply with all applicable standards of Section 508 of the Rehabilitation Act. Table 1 (above) defines deliverables at a high level and should not be considered all inclusive. Each Task Order will identify the specific deliverables, due dates, or frequency. The format and content requirements will be mutually developed and agreed upon among the IRS Program or Project Manager (PM), the contractor and the Contracting Officer’s Representative (COR).

7.2.2 Task Order Kickoff Meeting

The Government may, at its discretion, require Kickoff meetings at the Task Order level. If a Task Order Kickoff meeting is required, the parameters and scope of the meeting will be set forth in the Task Order.

7.2.3 Quality Control Plan (QCP)

The contractor shall prepare a Quality Control Plan (QCP) for the work to be conducted under this PROCUREMENT. The purpose of the QCP is to outline a strategy and identify mechanisms for ensuring that all products and services meet quality standards for completeness, accuracy, and timeliness. In the plan, contractors must describe the quality control methods they would employ to ensure that the requirements of the PROCUREMENT and its task orders are provided as specified. Contractors must state how they would manage the program and perform functions such as configuration management, the application of industry standards, and use of best practices, version control, security monitoring, preventive maintenance, and training for personnel. Additionally, contractors should describe what monitoring techniques (e.g., inspection regimen, customer input, audits) they would use to ensure the effectiveness of such activities. The QCP shall describe the methods for identifying and preventing problems before the level of performance becomes unacceptable. The plan shall be provided in electronic format and shall comply with all applicable standards of 36 CFR §1194 – Section 508 of the Rehabilitation Act of 1973, as amended.

The QCP shall be provided within thirty (30) days of PROCUREMENT award. Any proposed changes to the QCP after it has been accepted by the IRS shall require written concurrence from the CO.

7.2.4 Subcontracting Arrangement

Enterprise Services – Unisys Support (ESUS) PROCUREMENT awardee are required to always have an updated Small Business Participation Plan.

7.3 Inspection/Acceptance

Inspection of work performed by the contractor will be done utilizing the monitoring methods outline in the QASP. All services provided will be subject to inspection and signed acceptance by the government’s designated personnel. Performance records may be evaluated by the government and performance reviews may be conducted under the monitoring methods to address deficiencies. Contractor shall correct and/or make good, rejected work and deficiencies by the COR (or delegated official), without additional cost to the government.

7.3.1 Submission of Deliverables

Any deliverables that do not comply with the acceptance criteria outlined in the PROCUREMENT, the Task Order or the QASP shall be considered rejected. The COR shall provide written feedback on deliverables within ten (10) business days. The contractor shall provide revisions within five (5) business days of receipt of the COR’s feedback. The number of days allotted to the contactor for re-submission of deliverables may be adjusted if agreed upon by both parties. If the vendor has not been notified of any discrepancies within ten (10) business days after submission of the deliverable or successful completion of a task, the deliverable or task shall be considered accepted. Unless otherwise specified in the Task Order, all deliverables/ work products shall be provided no later than 4:00 p.m. EST on the applicable due date(s).

7.4 Documentation Requirements

The contactor shall provide all documentation in Section 508 compliant electronic format and hard copy. The Government will have the right to request suppression of hard copy deliverables in cases where security and privacy concerns are a factor, or to reduce paperwork burden. All deliverables resulting from work executed under this contact shall convey to the government. In addition to the requirements set forth in the QASP and the Task Order, all documentation shall be provided in accordance with the criteria set forth below:

· Completeness – The document demonstrates sufficient level of detail to show understanding of the requirements, technology and design, customers and operating environment.

· Feasibility - The document defines information, which is formatted properly, contains valid information in support of this task order and provides a deliverable within time constraints.

· Understandability - The document is to be clean, clearly written, all printed words are legible, and the outline is easy to follow. All diagrams are easy to understand and relevant to the supporting narrative.

· Accuracy – The document is accurate in presentation exhibiting clear and concise information, technical content, and adherence to accepted elements of style, operational content, and consistent within itself and with other documents.

· Practicality - The document provides information and guidance that is practical for implementation within the IRS environment and appropriate given the subject organization’s level of maturity.

8.0 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

The Quality Assurance Surveillance Plan (QASP) at Attachment 1 will provide a means for evaluating the contractor's performance to ensure that the Government receives the level of service required to achieve the objectives of this procurement. Under this plan, the contractor's performance will be assessed against established standards and quality levels to determine if the IRS is receiving the quality of services set forth in the performance work statement.

In addition, the contractor shall establish and maintain a complete QCP in accordance with Section 7.2.3. This links the Government and contractor’s quality assurance efforts into an integrated package with shared objectives.

The Performance Requirements Summary (PRS) Matrix below sets forth the performance standards, acceptable quality levels and the methods of surveillance for the identified products and services to be provided under this contract.

Table 2: Performance Requirements Summary Matrix

COR and/or IRS

PM.

100% of all Documentation delivered on Schedule and in accordance with the PWS and were 100% Section 508 compliant.

98% of all Documentation delivered on Schedule and in accordance with the PWS and were 100 % Section 508 compliant

100% review by

Contractor services always provide desired outcomes in accordance with Task Area 1 of the PWS.

Contractor will provide the desired outcomes in accordance with Task Area 1 of the

PWS.

100% review by COR and/or IRS

PM.

Task Area 2, EMIME

100% of all Documentation delivered on Schedule and in accordance with the PWS and were 100% Section 508 compliant.

98% of all Documentation delivered on Schedule and in accordance with the PWS and were 100 % Section 508 compliant

100% review by COR and/or IRS PM.

Contract labor mix is controlled in efficient and effective manner

Actual TO labor resource mix is maintained within 20% of originally awarded TO resource mix

Routine Inspection of TO Performance, Performance/Cost Reports, Payment Invoices, etc.

Task Area 3, O&M

Task Area 4, Service Management 100% Deliverables completed on schedule and in accordance with the PWS requirements with no re-work required.

98% Deliverables completed on Schedule and in accordance with the PWS requirements with no re-work required.

100% review by

100% of all Documentation delivered on Schedule and in accordance with the PWS and were 100% Section 508 compliant.

98% of all Documentation delivered on Schedule and in accordance with the PWS and were 100 % Section 508 compliant

100% review by

Contractor services always provide desired outcomes in accordance with the

PWS.

COR and/or IRS

PM.

Task Area 5, Transition Activities