iss draft pws.pdf

---DRAFT---

Blanket Purchase Agreement (BPA) Performance Work Statement (PWS)

“Infrastructure Shared Services (ISS)”

1.0 INTRODUCTION AND BACKGROUND

The Internal Revenue Service (IRS), Information Technology (IT), Enterprise Services Office (ES) is responsible for providing mission critical IT infrastructure support for the IRS. The ES Infrastructure Shared Services (ISS) Program provides support for Internet platforms, computer hardware, operating systems, enterprise software applications including middleware, networking and telecommunications, and data storage and management that are vital to IRS business operations. This blanket purchase agreement will support the needs of the Infrastructure Shared Services (ISS) Program within the Enterprise Services organization.

2.0 OBJECTIVE

The objective of this Performance Work Statement (PWS) is to obtain contractor support services for the ISS Program to provide comprehensive enterprise IT solutions for an integrated shared infrastructure.

3.0 SCOPE OF WORK AND DESCRIPTION OF TASKS

This Performance Work Statement (PWS) is Performance-Based Acquisition hybrid Firm Fixed Price (FFP) / Labor Hour (LH) with mission-oriented, event-driven performance measures and incentives.

Firm Fixed Priced (FFP) and Labor Hour (LH) Level of Effort (Hours) Summary

Base Opt

Period 1 Opt

Period 2 Opt

Period 3 Opt

Period 4

TOTAL

Firm Fixed Priced (FFP)

Task 1, Orientation Briefing (FFP) 320 320

Task 2, Knowledge Transfer / Transition-In (FFP) (Optional) 1,840 1,840

Task 3, Program / Project Management (FFP) 5,500 5,500 5,500 5,500 5,500 27,500

Task 5, Transition-Out (FFP) (Optional) 1,920 1,920

Labor Hour (LH)

Task 4, ISS Technical Support (LH) 162,459 162,459 162,459 162,459 162,459 812,295

TOTAL 172,039 167,959 167,959 167,959 167,959 843,875

The contractor shall support a wide range of programs, projects, and legislative mandates which includes:

American Recovery Plan

Tax Check Program (TCP)

Taxpayer First Act (TFA)

Inflation Reduction Act (IRA)

The contractor shall support the ISS Program by providing solutions engineering, systems integration and architecture support.

3.1 Task 1, ORIENTATION BRIEFING (FFP)

Within two weeks of award, the contractor shall conduct an orientation briefing for the Government. The intent of the briefing is to initiate the communication process between the Government and contractor by introducing key task award order participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of award requirements and objectives.

The orientation briefing shall be held at the Government's facility and both parties shall mutually agree upon the date and time.

The completion of this briefing shall result in the following:

1. The contractor and Government personnel who will perform work under this award order shall be introduced.

2. The Government will show the applicable facilities to the contractor, if the contractor will be performing work on the Government's site.

3. The Government may provide any Government Furnished Property (GFP) to the contractor at this time.

4. Any issues concerning the contractor clearances for contractor personnel shall be discussed.

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

6. The contractor shall provide the accounting period end dates to be used for the term of this award order.

DESIRED OUTCOMES - 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 the COR within 5 business days after Briefing. Contractor shall deliver Contractor Quality Control Plan (QCP) to the COR within 14 business days after the Briefing.

3.2 Task 2, KNOWLEDGE TRANSFER / TRANSITION-IN (FFP) (OPTIONAL)

The contractor shall conduct knowledge transfer and transition-in sessions as needed to ensure uninterrupted performance/service of the ISS with the IRS stakeholders and the current support contractor.

3.2.1 Knowledge Transfer

Knowledge Transfer is defined as the contractor acquiring and understanding the necessary documentation, information, and processes related to any work in progress. The contractor shall meet with the IRS Subject Matter Experts frequently to gather any tacit knowledge related to the Core Systems, Compliance Document Matching and Solutions Engineering/Enterprise Services tasks or programs in development. The government estimates this task will take approximately ninety (90) calendar days to complete from the start of the base period of performance.

The contractor shall appoint a knowledge transfer manager to oversee the transfer of knowledge and ensure all areas are accounted for. 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 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 will 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 to discuss the progress of the knowledge transfer. The contractor shall provide an updated MS Project Schedule and risk registry for review and discussion.

DESIRED OUTCOMES - 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.

3.2.2 Transition-In

The Transition-In task permits for an effective transition from incumbent(s) contractor to a new contractor. The Government estimates this task will take approximately 90 calendar days to complete from the contract award date. Successful transition can be defined by its capacity to maintain full continuity of operations, high productivity, and exemplary service quality. To ensure a successful, low-risk transition, the contractor shall develop a draft Transition-In Plan that outlines detailed tasks and milestones and provide it to the COR within 15 business days after award.

The Government will have 10 business days to review the draft Transition-In Plan and provide comments to the contractor. Government and contractor will then meet to discuss the comments after which the contractor shall incorporate the agreed-upon changes and deliver a final Transition-In Plan within 5 business days.

The contractor shall execute the approved Transition-In Plan and keep the Government fully informed of status throughout the transition-in period. During the Transition-In period, the incumbent is responsible for performance. This task shall be worked concurrently with Task 2, Knowledge Transfer task.

In addition to the transition actions in the approved Transition-In Plan/Checklist, the contractor shall perform the following activities during the transition-in period:

1. Transition management team leaders on-board immediately after the award.

2. Identify qualified personnel and submit security background investigation packages to the COR for clearance.

3. Submit requests for SmartIDs (badge IDs), laptops and network access.

4. Review and understand required IRS policy, requirements and procedures.

5. Complete mandatory security awareness briefings.

DESIRED OUTCOMES – All ISS Program projects and initiatives are transferred timely and completely from the incumbent contractor to the awardee contractor within 90 calendar days in accordance with the Transition-In Plan. The Government is continuously informed of transition-in status and there are no lapse or delays in ISS services and projects.

3.3 Task 3, PROGRAM / PROJECT MANAGEMENT SUPPORT (FFP)

The contractor shall provide program/project management support to successfully facilitate planning, management and execution of tasks associated with planned and awarded task orders under this BPA.

The contractor shall focus on managing/overseeing Cost, Schedule, and Scope. The contractor shall provide program and project management oversight for ISS in accordance the Internal Revenue Manual (IRM) 2.31.1, One Solution Delivery Life Cycle (OneSDLC).

The contractor shall:

1. Meet with COR bi-weekly to discuss ongoing task matters and resources to support the contract.

2. Support COR with contractor team on-boarding/off-boarding activities including:

a. Prepare security clearance packages for onboarding individual and submit to COR for processing.

b. Work with onboarding individual to resolve an issues that may arise.

c. Submit requests for network accounts and access roles.

d. Order equipment for team member (i.e., laptops, phones, etc.).

e. Request SMART ID badges.

f. Ensure mandatory security briefing are completed .

g. Prepare and submit Contractor Separation Checklist to COR for processing.

h. Collect equipment and SMART ID badges from separating individuals.

3. Ensure contractor employees are compliant with IRS security training requirements

4. Develop and baseline project schedules or project roadmaps with milestones.

5. Manage requirements and program risks.

6. Recommend the most effective use of resources for the completion of the activities.

7. Provide level of effort estimates/quotes for new work/initiatives/resources.

DESIRED OUTCOMES – The contractor shall manage the ISS Program to achieve programmatic integration of projects while focusing on business requirements and results. The contractor shall ensure quality, timely deliverables/work products/work papers, and program support.

3.3.1 Documentation

The contractor shall coordinate the document control process of preparing deliveries, maintaining document repositories, the Versioned Object Base (VOB), and tracking and reporting document status.

The contractor shall manage the workflow of contract deliverables and work products from authors (i.e., document preparers) to the IRS.

The contractor shall:

1. Ensure that documents are prepared and delivered in accordance with each project’s schedule and requirements.

2. Act as a liaison between the infrastructure documentation group and other contractor project management and technical teams.

3. Develop and monitor a document production schedule; identify and address any schedule dependencies with the author, Control Account Manager (CAM), and project manager.

4. Oversee the production and updates to infrastructure documentation and ensure that documents conform to the IRS IT standards and procedure which will be provided after award.

5. Ensure that documents are reviewed for accuracy prior to submission for acceptance.

6. Monitor, track and report the status of document deliverables and work products.

7. Coordinate the final preparation and packaging of deliverable documents, see attachment 2.

8. Prepare transmittal letters.

9. Ensure contractor documents signoff is completed.

10. Support inspections and audits.

. The contractor shall provide the following deliverables:

1. Monthly Contract Status Reports (MCSR) – The MCSR shall include status reports for all work in performance under the order. This report is due to the COR and project managers no later than the 7th day of each month.

2. Government Furnished Equipment (GFE) Reports - This inventory report shall track GFEs that have been provided to the contractor staff. The frequency and due date will be determined by the COR upon contract award but no less than monthly.

3. Monthly Spend Analysis Reports – This report shall include projected and expended/obligated financial data. This report is due to the COR no later than the 10th day of each month.

4. Acquisition Management Reviews (AMR) – The CO, COR, Acquisition Managers (AMs), Program Managers (PMs), IRS Leadership and the ISS Stakeholders shall meet annually to discuss the following:

a. The status of program milestones, schedule, deliverables, and other key items.

b. Contractor performance (e.g., metrics outlined in a quality assurance surveillance plan

(QASP)).

c. Issues and/or risks, if any, and develop appropriate plans of action as necessary.

d. Changes that have occurred since the last AMR that impact the contract, (e.g., budget, changes in resources; customer feedback).

DESIRED OUTCOMES – The contractor shall provide quality, timely reports and documentation within the agreed to schedule for each deliverable.

3.3.2 Quality Management

The contractor shall provide continuous quality assurance for activities defined for each project/task order. At a minimum, the contractor program manager shall meet bi-weekly with the COR to ensure that the project/task order customer’s requirements are delivered in terms of requirements, schedule and cost.

3.4 Task 4, ISS TECHNICAL SUPPORT (LH)

The contractor shall provide Architecture, Development and Engineering support services for the following software/systems/technologies:

1. Enterprise Data Platform (EDP)

2. Cloud Integration

3. Drupal

4. Platform Engineering (PLE)

5. Capacity Planning and Performance Engineering

6. Business Objects Enterprise (BOE) and Tableau

7. Greenplum Database Management System (DBMS)

8. Return Review Program (RRP)

9. Data Modeling and Data Design

10. International Business Machines (IBM) Rational Software Architect (RSA)

11. EnCase® eDiscovery

12. Authorization (Az) Framework

13. Enterprise Informatica Platform (EIP)

14. Databricks Platform

15. IRWorks (ServiceNow)

16. Customer Account Data Engine (CADE) 2

17. Individual Tax Processing Engine (ITPE)

DESIRED OUTCOMES – The contractor shall:

1. Provide systems analysis and design, solution concept, logical and physical engineering design, interface, XML Schema, performance and infrastructure design content delivery, and engineering analysis of alternatives.

2. Perform infrastructure capacity planning and analysis to ensure thorough objective evidence that the products recommended shall satisfy the requirements.

3. Security and infrastructure solutions are effectively deployed allowing modernization projects to successfully utilize the common shared infrastructure.

4. Establish common and unambiguous business, product, and functional requirements that are testable and allocated to a specific release package (RP).

5. Ensure the receiving organization is ready to support the infrastructure being transitioned.

6. Modernized systems meeting the business needs of the IRS, enabling interoperability, and complying with the Enterprise Architecture and IRS established engineering processes and procedures.

3.4.1 Configuration Management

The contractor shall support Configuration Management (CM) functions in accordance with IRM 2.150.1, Configuration Management Policy and IRM 2.150.2 Configuration Management (CM) Process.

CM functions include 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.

The contractor shall:

1. Track and document all configuration items included in baseline releases during design integration, testing, fielding and sustainment.

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

3. Update Implementation Packages accordingly.

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

5. Meet Government acceptance criteria for configuration management.

6. Service Desk Support for software application repairs/fixes

DESIRED OUTCOMES – Consistent configuration management that implements standard documentation and reporting methods and provides 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.

3.4.2 Change Management

The contractor shall support the ISS team in executing change management and change control processes that are compliant with IRM 2.125.1, Change Management Policy. The contractor shall describe how changes shall be initiated, analyzed, designed and handed off for implementation. The contractor shall support the ISS team in developing required systems documentation and change requests (CRs) for the IT Configuration Change Board (CCB).

DESIRED OUTCOMES – The contractor shall provide change management and change control processes that controls the lifecycle of all changes and enables beneficial changes to be made with minimum disruption to IT services as defined by each ISS project teams.

3.4.3 Performance

3.4.3.1 Performance Engineering

The contractor shall work with the ISS project teams to develop infrastructure performance requirements, including network requirements, and publish performance specifications for modernized infrastructure components.

The contractor shall document resulting performance specifications as part of the ISS infrastructure requirements as needed and directed by the ISS project team. The contractor shall analyze the system design, and model critical components as appropriate, to identify weaknesses and potential problem areas, including performance bottlenecks and interface problems in connections to external systems.

The contractor shall summarize performance analysis results and provide brief analytical approaches to ES Solution Engineering team. The contractor shall develop network engineering recommendations to improve network performance and reliability. The contractor shall use performance tools to identify and predict actual resource usage and provide alternatives for meeting network performance expectations.

The contractor shall support all the ISS applications/services and data management with the use of Commercial off the Shelf (COTS) test tool suites. If COTS test tool suites are not available, then the contractor may develop test tools for specific needs. Final test plans that are created during the performance unit testing in the Virtual Development Environment (VDE) shall be provided to the ISS project team upon completion of testing period.

3.4.3.2 Performance Monitoring and Tuning

The contractor shall actively monitor and analyze fielded infrastructure components to find and correct weaknesses and potential problem areas. The contractor shall analyze performance statistics of the infrastructure components and suggest improvements. The contractor shall identify, isolate, propose and implement improvements to hardware, software, and communication problems, performance bottlenecks and interface problems in connections to external systems.

The contractor shall support the modernized infrastructure in the identification and resolution of performance issues. This shall include measurement, optimization reviews, tuning, benchmarking, event management, performance reporting, availability reporting, and auto event ticketing. The key to performance tuning is to isolate and identify performance bottlenecks, measure impact and engineer solutions to eliminate them. This requires experience with a wide variety of systems, including networks, routers, switches, firewalls, web servers, application servers, operating systems, databases, 3rd party software packages, and infrastructure custom code. Each of the performance tests can be run over and over, with the effects of different back-end configurations analyzed for its effect on performance.

3.4.4 Capacity

3.4.4.1 Modeling and Capacity Planning

The contractor shall develop a composite view of the infrastructure capacity upon request from the government.

An integrated modeled cross-tiered view from Integrated Master Schedule (IMS) and Release Architecture is a critical input for forecasting the demand for a release. The initial view must be constructed toward building sufficient infrastructure including the testing environments to support the current release year, and a forward-looking offset of 6 months to one year. Subsequent iterations of the demand forecast shall rely on a combination of the prioritized strategic plan, Integrated Master Schedule, and Release Architecture work for out releases, leveraging the architectural patterns of the Enterprise Architecture, to anticipate the yearly forward-looking capacity need at budget formulation time.

The contractor shall baseline the modernization system requirements of the IRS Wide Area Network (WAN) in terms of circuit allocations, utilization and latencies observed to include:

Develop a composite view of the IRS network model and model the new modernized applications;

Introduce network traffic on the WAN and predict future Network Capacity Requirements;

Analyze system design, model critical components to identify weaknesses or bottlenecks and develop change recommendations; and, Rationalize infrastructure needs against the patterns to effectively estimate the capacity that shall be needed years ahead of design.

The contractor shall provide an enterprise method of measurement collection, forecasting, server baseline and modeling, server capacity reporting, network baseline, application modeling, network capacity reporting, and periodic capacity plan as required.

The contractor shall support activities to develop Infrastructure Service Level Agreements (SLAs) with input from stakeholders. SLAs should be measurable, repeatable, and provide value to stakeholders.

Where feasible, the contractor shall leverage the Enterprise Systems Management (ESM) measurement resources to provide consistency across projects. The contractor shall report SLA attainment in monthly SLA reports to the COR/CO.

3.4.4.2 Database Management

The contractor shall provide support services for new and current database management systems (e.g., DB2, Oracle, Greenplum, Microsoft SQL Server, etc.). The contractor shall provide the following support services:

1. Additional direct access storage device (DASD) storage capacity engineering, installation, configuration, and testing support.

2. Additional backup capacity engineering, installation, configuration, and testing support.

3. For new platforms, Database software and services engineering, installation, configuration, and testing support.

4. Engineering for and allocation of raw database space(s).

5. Assisting IRS project team with the IRS Work Request (UWR) Process as needed. Policy and guidance for the IRS Work Request Process will be provided to contractor after the award.

3.4.5 Enhancements

3.4.5.1 Security Enhancements

The contractor shall provide and support recommendations for new security functionality that shall reduce project security risks to include calibrating the Xacta model to reflect the current infrastructure, periodically analyzing new security policies, procedures, guidance, and other documented security products to determine what functionality should be added to the Modernization Infrastructure to reduce security risks. The recommendations shall address the risks that would be mitigated as well as the costs and/or resources that would justify the recommendations.

3.4.5.2 Infrastructure Enhancements

The contractor shall provide and support recommendations for new modernization infrastructure functionality and use best practices that enhance infrastructure services, improve the overall return on investments to the IRS and reduce the IT total cost of ownership (TCO). This task includes periodically analyzing engineering analyses, impact analyses, and other documented products produced to determine what functionality should be added to the modernization infrastructure to minimize project-specific infrastructures. The focus shall be on addressing why the functionality should reside on the modernization infrastructure and not in the projects. The recommendations must address where the economics of cost and/or resources would justify the recommendations. Once the recommendations have been approved, this task would include engineering and implementing the approved recommendation.

The contractor shall evaluate the impact of new and existing technologies such as Gig-E, ATM, MPLS, VOIP, VPNs, PKI and develop reports discussing benefits of implementation. The contractor shall support IRS efforts to develop a roadmap for infrastructure enhancements and gather technology trends and best practices through research and studies and communicate findings.

The contractor shall recommend adjustments to the Enterprise Architecture based on technological advances and industry trends utilizing the modeling and performance information and establish recommendations on how the infrastructure can be enhanced to support the IRS customer base more effectively.

The contractor shall also define plans to upgrade IRS network infrastructure technology in manageable phases. The upgrade is imperative to support the continuously evolving and demanding enterprise applications’ requirements.

The contractor shall code and test all non-Commercial Off the Shelf (COTS) infrastructure software for the modernized infrastructure system functionality required for each release to include the current production environment Application Programming Interfaces (APIs). The contractor shall integrate COTS modernized infrastructure system functionality in a release level test. The contractor shall update existing infrastructure application software as needed to meet Enterprise Architecture guidelines.

3.4.6 Requirements

3.4.6.1 Requirements Development

The contractor shall support the ISS Program teams with requirements development to ensure that requirements relate to infrastructure requirements and are consistently developed. The purpose of requirements development is to produce and analyze customer, infrastructure, and infrastructure component requirements. The requirements development work includes three specific goals. a) develop customer requirements b) develop infrastructure requirements and c) analyze and validate the requirements.

3.4.6.2 Requirements Management

The contractor shall support requirements management to ensure that all requirements are accurately documented, tracked, communicated and verified to meet ISS Program objectives.

3.4.7 Customer Support/Services

3.4.7.1 Customer Support

The contractor shall support those activities required to proactively provide information, awareness, and education to current and potential users of the modernized Infrastructure. These activities shall disseminate information about current infrastructure capabilities and solicit additional potential users of the infrastructure.

3.4.7.2 Support and Maintenance

The contractor shall provide Support & Maintenance (S&M) for applications and platforms hosted within the ISS Program. Support and Maintenance ensure that an application or platform remains functional, reliable, and up-to-date after its initial deployment.

1. Provide direct support to end-users, addressing basic issues and queries.

2. Document and tracking user-reported issues.

3. Troubleshoot technical issues.

4. Make necessary adjustments to system settings and configurations.

5. Provide guidance and training to users on effective system use.

6. Involve subject matter experts to solve highly complex or uncommon problems.

7. Manage escalations and liaisons with vendors or developers for resolution.

8. Perform regular system checks to prevent issues before they occur.

9. Install updates and security patches.

10. Address performance issues and optimizing system efficiency.

11. Update system(s) to accommodate new hardware, software, or regulatory requirements.

12. Implement new features and improvements to enhance system functionality and user experience.

3.4.8 Engineering

3.4.8.1 Technical Quality Assurance

The contractor shall establish and support a comprehensive Technical Quality Assurance process to ensure that software products or IT systems on ISS meet specified requirements and is free of defects.

The process should encompass various techniques and methodologies to test, verify, and validate the quality of software products.

1. Recommend best practice efficiencies relating to the technical improvement of the infrastructure products, publication of those products, and the review process associated with the revisions.

2. Provide support to ensure that the current, as well as future Infrastructure requirements are properly applied to designs and implementations.

3. Provide support to ensure that the ISS Program will meet long term modernization goals, including efficient total costs of ownership and operation across all business system processing.

3.4.8.2 Integrated Infrastructure Project Planning

The contractor shall establish an integrated infrastructure project planning process to ensure that project planning is integrated into release plans for infrastructure and coordinated with the release management function. The purpose of integrated infrastructure project planning is to establish and maintain plans that define integrated infrastructure project activities. The contractor shall establish and maintain the methodology for performing infrastructure project planning.

3.4.8.3 Project Monitoring and Control

The contractor shall provide project management support so that the ISS Program projects are monitored and controlled, and action can be initiated to solve problems that occur with deviations from the integrated infrastructure project plan.

3.4.8.4 Planning for Disaster Recovery, Business Continuity, Backup and Recovery

The contractor shall provide support for disaster recovery, business continuity, and backup and recovery planning for the ISS Program in conjunction with the IRS Disaster Recovery Team and ISS technical project teams. Infrastructure Business Continuity includes the ability for the ISS Program to support IRS operations by providing processing and communication services necessary to continue operations of essential business applications within the timeframes mandated by law. Backup and recovery of essential data includes no, or minimal loss of data based on business application’s requirements and security and privacy regulations necessary to continue essential business applications within the timeframes mandated by law.

The results of planning and support activities shall be consistent with the IRS disaster recovery policy and IRS EA guidance.

3.4.9 Earned Value Management System Reporting Requirements

The Contractor shall comply with FAR 52.234-4 Earned Value Management System (EVMS) and Treasury EVM policy regarding ANSI/EIA STD -748A. Compliance includes documenting in the business proposal, a description of the EVM System (EVMS) to be used; in sufficient detail to enable independent assessment of the Contractor’s understanding and conformity with the requirements of the ANSI/EIA-748-A standard. The EVMS description will address all salient factors, including the key EVM measures and metrics and how the EVMS integrates with general cost accounting and budgeting systems. It will also address criteria used to determine applicability and means of verifying and monitoring flow down requirements to fully integrate subcontractor EVM data with the Contractor’s EVMS. Copies of referenced Treasury and IRS EVM policies and guidance will be provided as Government Furnished Information (GFI).

The contractor shall:

1. Provide for the completion of an IBR, or, as appropriate, (for subcontracts with DME less than $20 million, an IBR (Core) that meets the Government standard and that the Contractor provide periodic reporting of the EVM data.

2. Define the authorized work elements for the program. A work breakdown structure (WBS), tailored for effective internal management control, is commonly used in this process.

3. Establish and maintain a time-phased budget baseline, at the control account level, against which program performance can be measured. Initial budgets established for performance measurement will be based on either internal management goals or the external customer negotiated target cost including estimates for authorized but vaguely defined work. Budget for far-term efforts may be held in higher-level accounts until an appropriate time for allocation at the control account level. On government contracts, if an over-target baseline is used for performance measurement reporting purposes, prior notification must be provided to the customer.

DESIRED OUTCOMES – Implementation and adoption of Performance-based acquisition management practices and processes, including integration of program scope, schedule and cost objectives, establishment of a baseline plan for accomplishment of program objectives, and use of earned value techniques for performance measurement during execution of the program. A performance-based acquisition (as defined in the Federal Acquisition Regulation 37.102) or an acquisition with a defined quality assurance plan that includes performance standards/measures should be the basis for monitoring the contractor

3.5 Task 5, TRANSITION OUT (FFP) (OPTIONAL)

At the end of this award, the contractor shall provide transition-out services (refer to Federal Acquisition Regulation (FAR) Clause 52.237-3 Continuity of Services). The contractor shall facilitate the transition of contracted activities and services to the Cybersecurity Program personnel and to a follow-on contractor in accordance with the Government Approved Transition-Out Plan. The Transition Out period shall not exceed ninety (90) calendar days.

The contractor shall:

1. Minimize transition impact to the user community.

2. Ensure no breaks in service availability.

3. Maintain existing service quality and performance levels.

4. Ensure a transparent and seamless transition.

5. Maintain support and meet delivery milestones of ongoing projects.

6. Ensure that the IT security posture during transition is maintained at current levels without creating gaps and/or vulnerabilities.

In support of this task, the contractor shall develop and provide a draft Transition-Out Plan no later than one hundred eighty (180) calendar days after the date of award, or earlier if directed by the Government.

The Government shall have 10 business days to review the draft Transition-Out Plan and provide comments to the contractor. Contractor shall incorporate the agreed-upon changes and deliver a final KTP within 5 business days of the Government’s feedback. The contractor shall update the Transition- Out Plan annually.

The contractor’s Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent(s) to the incoming contractor and Cybersecurity personnel. The contractor shall identify transition activities, schedules, and milestones for the turnover of work (e.g., operations, maintenance, engineering, training, asset management, and logistics functions) and identify how it will coordinate with the incoming contractor(s) and Cybersecurity personnel to transfer knowledge.

3.6 Task 6, TRAVEL (OPTIONAL)

Travel and per diem will be reimbursed at actual cost in accordance with the limitations set forth in FAR 31.205-46 and the General Services Administration’s Federal Travel Regulations. Profit shall not be applied to the travel costs. Local travel may be required for on-site meetings; Local travel will not be reimbursed.

The following is an estimate of travel costs associated with the performance of all tasks that may be issued under this PWS: $50,000 (approximately $10,000 for the Base Year and $10,000 for each of the One-Year Option Periods.

The contractor shall provide a travel voucher statement for all local travel. The voucher will ensure verification of costs incurred for local travel under the award is both allowable and reasonable and in accordance with the regulation FAR 31.205.46.

The contractor shall attach the voucher and receipts to the monthly invoice. For any trip to be authorized, the COR must approve such travel in writing and in advance. Failure to acquire pre-approval may result in non-local travel charges by the contractor being denied.

4.0 REQUIRED SKILLS AND TECHNICAL EXPERTISE

BPA performance will require the contractor to work with technologies including the following:

IBM WebSphere, Database 2 (DB2), MQ Series, Rational Suite, Endpoint Management, etc.

Oracle Database, Solaris including the Sun Cluster Environment, E-Business Suite, etc.

Microsoft Windows, Azure, SQL Server, Internet Information Services (IIS), .NET,etc.

ServiceNow Platform

F5 Load Balancer

SiteMinder

Enterprise Informatica Platform (EIP)

Authorization (Az) Framework

Drupal Platform

Documentum

Red Hat Linux, JBoss Enterprise Application Platform, etc.

Greenplum Massive Parallel Processing (MPP)

MongoDB

PostgreSQL Data

Ephesoft OC

Tivoli Management Framework

Alteon WebSystems Products

Quest Authentication Service Single Sign-on

Business Objects Enterprise (BOE) and Tableau

Jira

Customer Relationship Management Software (e.g., Salesforce, Pega, Mulesoft, etc.)

Short Message Service Platform (SMSP)

Common-Services

EnCase® Endpoint Investigator (EI) and EnCase® eDiscovery (eD)

Amazon Web Services (AWS)

Databricks Platform

Application Messaging and Data Access Services (AMDAS)

Tier 1 Mainframe o OS/MVS and associated job control and common utilities o Unisys and associated job control and common utilities o Qprocessor / MQ Series o zOS

Tier 2 Unix/Linux environments with associated scripting and common utilities

Tier 3 o WinTel platforms and associated user and administrative utilities o WINDOWS [to include Windows 7, Server 2008]

Network servers

Languages o SAS o REXX o SQL o COBOL o ABAP o 24x7 script (JAL) o SAP script o Shell script (BOURNE, C, KORN) o Java o C/C++/C# o MVS ALC o Python o Javascript

5.0 DELIVERABLES

The contractor shall produce Work Products/Deliverables that conform to and integrate with, existing IRS standards and guidelines. The contractor is expected to clearly articulate through documents, presentations, customer technical reviews and other engagements the results and recommendations of the Enterprise Architecture Office (EAO). The contractor must ensure that all work products/ deliverables are of high quality and require minimal government intervention to comply with style and formatting requirements of the Service. The contractor shall conform to all IRS Security and Disclosure policies.

Unless otherwise specified below, all deliverables/ work products shall be provided to the COR no later than 4:00 p.m. local time on the date(s) specified in the order. The contractor shall ensure that all deliverables are clearly marked with the contract number and award number and visible on all shipping/service documents, containers, and invoices.

The Government believes there is value in incorporating Performance-Based Service Acquisition (PBSA) methodology with an outcomes-based focus for this work. Attachment 1 defines the Government’s Desired Outcomes, Required Services, Performance Standards, Acceptable Quality Levels and Monitoring Methods for each task area included in this Task Order.

5.1 DELIVERABLE FORMAT

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.

Unless otherwise requested in writing by the COR, work products shall be produced using Microsoft Office 2010 or later Professional products and delivered in accordance with the deliverable schedule at Attachment 2. If it is required that deliverable(s) be submitted in media storage form all devices must be scanned and certified as virus free. The contractor shall post deliverables directly to the IRS SharePoint site.

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 contract 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.

Work and work products, including email communications, shall only be accomplished on IRS issued desktop or laptop computers.

5.2 DELIVERABLE QUALITY

The general quality measures as set forth below will be applied to each deliverable/work product received from the contractor under any task order issued under the Blanket Purchase Agreement.

1. Accuracy – Deliverables/Work Products shall be accurate in presentation and technical content and shall adhere to accepted elements of style.

2. Clarity – Deliverables/Work Products shall be clear and concise; the appropriate terms shall be used; will be easy to understand and relevant to the support required by the individual performance work statement(s) (PWS). Reports and documentation produced under each Task Order must be clearly written and understood by the COR and IRS Subject Matter Experts (SME) prior to acceptance of the Deliverables/Work Products.

3. Specification Validity – Deliverables/Work Products must satisfy the technical and/or functional requirements of the Government, as specified in the PWS/task order to produce the Desired Outcomes stated in Section C.

4. File Editing – All text and any diagrammatic files shall be editable by the Government.

5. Format – Deliverables/Work Products shall be submitted in the format stated in the PWS unless otherwise directed by the Contracting Officer.

6. Timeliness – Deliverables/Work Products shall be submitted on or before the due date specified in the task order.

7. Operability – Software and other Deliverables/Work Products created for a Task Order must operate without faults, to produce the Desired Outcomes, prior to their acceptance by the Government.

8. Functionality – Software and other Deliverables/Work Products created under a Task Order must function in such a way as to produce the stated Desired Outcomes for each activity.

9. Compliance – Deliverables/Work Products shall be in conformance with all standards and regulations noted in the PWS.

10. Accuracy and Validity – Data produced by software and procedures developed under a Task Order, as well as all reports and documentation, must be accurate and valid prior to acceptance.

11. Completeness – Deliverables/Work Products must be submitted as fully completed end products, prior to COR acceptance

5.3 REVIEW OF DELIVERABLES

1. 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 will 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 task order.

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

3. 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.

6.0 GOVERNMENT-FURNISHED PROPERTY (GFP)

Government furnished property (to include material, equipment, and/or information) shall be provided in the performance of this award. The GFP may consist of the following:

ITEMS QUANTITY

Contractor Identification Badge TBD Contractor Building Access/Proximity Card TBD Laptops with Local Area Network Access TBD Microsoft: Word, Excel, PowerPoint, Project, Access TBD Telephone With VMS TBD

Disposition of GFP shall be in accordance with FAR 52.245-1.

7.0 GOVERNMENT-FURNISHED INFORMATION (GFI)

Government furnished information (to include manuals, notes, memos, instruction materials, and other information) may be provided during the performance of this award. The contractor shall be responsible for safeguarding all equipment, information and property provided for contractor use to include, but not limited to:

INFORMATION ITEMS

Internal Revenue Manuals (IRM) IRS IT Standard Operating Procedures and Policy Systems Documentation (Design, Architecture, Configuration, etc.)

IRS Templates and Forms

Disposition of GFI shall be in accordance with FAR 52.245-5.

8.0 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

The contractor is allowed limited access to the government's facilities, as specified below:

Internal Revenue Service – New Carrollton Federal Building 5000 Ellin Road Lanham, Maryland 20706

Internal Revenue Service – Martinsburg Computing Center 1250 Edwin Miller Blvd Suite 100 Martinsburg, West Virginia 25404

Internal Revenue Service – Memphis Computing Center 5391-5399 Getwell Road Memphis, Tennessee 38118

9.0 OTHER INFORMATION AND SPECIAL CONDITIONS

9.1 PERIOD OF PERFORMANCE

The period of performance for any resultant award will include a one (1) 12-month base year period and four (4) 12-month option year periods.

Base Period: January 1, 2025 – December 31, 2025 Option Period 01: January 1, 2026 – December 31, 2026 Option Period 02: January 1, 2027 – December 31, 2027 Option Period 03: January 1, 2028 – December 31, 2028 Option Period 04: January 1, 2029 – December 31, 2029

9.2 PLACE of PERFORMANCE

The primary place of performance shall be the contractor’s site, with reasonable access to New Carrollton Federal Building and, if required the IRS Headquarters in Washington DC. Contractor personnel must be able to travel to the New Carrollton Federal Building for meetings within two hours’ notice. The IRS will make every attempt to provide space for contractor employees at the NCFB facility, however, there is no guarantee permanent office space will be available for contractor employees.

The Government’s facilities are listed below.

Internal Revenue Service New Carrollton Federal Building (NCFB) 5000 Ellin Road

New Carrollton, MD

Internal Revenue Service National Office 1111 Constitution Avenue, NW Washington, D.C.

Access to other sites may be provided on an as needed basis, with prior coordination.

The contractor may travel to other IRS locations such as the Enterprise Computing Center in Martinsburg, WV or Memphis, TN, but the contractor will be notified in advance to ensure adequate travel costs are available.

9.3 HOURS OF WORK

If needed, performance may be required beyond the standard workday. The standard work day is defined as any eight hours of productive labor during the core business hours of 7:00 A.M. through 5:00 P.M., Monday through Friday. Should performance outside of the standard workday become necessary, the CO will notify the contractor in writing.

9.4 TELEWORK/ ALTERNATE WORK SITE

Use of an alternate work site for performance (other than contractor’s primary office) is subject to approval of the IRS Program Manager and COR. Approval to work at an alternate work site (such as home) on an IRS contract is not guaranteed. The operational needs of the IRS are paramount as well as the security and safety of the IRS data and equipment. All alternate work sites must comply with the Company’s telework policies and IRS security procedures. The alternate work site must ensure adequate security measures are in place to protect the equipment and information housed or stored on assigned computers. Failure to comply with security procedures and regulations is grounds for removal from the contract.

Contractor employees are responsible for obtaining their Government Furnished Equipment (GFE) from the NCFB unless other arrangements are made in advance. Assigned GFE may include a laptop and a SmartID card. The contractor employee is expected to report to the IRS site for needed repairs and/or system upgrades and return the equipment to NCFB at the completion of the task order or when the equipment is no longer needed. Travel is not authorized to obtain the government furnished property and/or information (GFP/GFI) needed to perform work under this contract.

10.0 SECURITY

Contractor personnel shall be in compliance with:

1. Title III of the E-Government Act of 2002 (Public Law 107-347), also known as the Federal Information Security Management Act of 2002 (FISMA)

2. Federal Information Security Modernization Act of 2014 (FISMA 2014)

3. Privacy Act of 1974

4. IRS HSPD-12 PIV Procedures Manual

5. Internal Revenue Manual (IRM) 10.8.1, Information Technology (IT) Security, Policy and Guidance.