PWS draft 2024 05 30.docx

PART I – DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 - INTRODUCTION AND BACKGROUND

Project Overview The goal of this procurement is to hire a vendor to continue the maintenance of the Project Tracking System (PTS) application and database. The Information Technology (IT) organization of the Internal Revenue Service (IRS) provides strategic planning and business management functions. These functions include planning, allocation, expenditure and monitoring of budgetary resources related to IT program management. PTS has been developed and implemented to provide a standardized, automated tool for program, contract, and budget management. Five prior years, the current year and two planning years data are stored in PTS. The IRS IT personnel are responsible for tracking spending plans, expenditures, program, and budget plans, and inputting the data into PTS. Funding requirements are created as Spending Plan Items (SPIs), approved/disapproved by management/executives and viewed by all PTS users within the IT organization. PTS is used to manage the entire IT budget and serves as a decision-making tool to facilitate IT resource allocation decisions by the CIO, other IT executives as well as business units.

System Overview

PTS is a system that operates as a web server dispatching services to a Microsoft SQL Server Database accessible through the IRS Intranet (IRS Firewall prevents Internet access to PTS) and supports approximately 500 users. The IRS owns and maintains the development, test, disaster recovery and production servers. The PTS software environment uses a multi-tier client-server approach (Presentation, Business Logic, and Database) to isolate the business logic, database logic, and Graphical User Interface (GUI) into independent tiers. The software environment is a user interface made up of a set of web pages viewed in the current IRS standard Internet browser (Microsoft Edge) and is isolated from the business logic of the system. PTS uses IRS Single Sign-On for authentication. A user's IRS ID is compared to a list of valid PTS user accounts to determine if login is possible.

Each business day, four interface files are loaded into PTS through the Electronic File Transfer Utility (EFTU). This is an automated nightly interface of files that provides financial data from the Integrated Financial System (IFS). PTS supports additional data uploads from other IRS systems through an Excel file upload process. The interface upload files provide Commitment, Obligation, Requisition data, contract data, etc. that automatically links to an SPI. Once linked, the user can track the expenditure of funds against the availability of approved spending. SPIs can be edited, duplicated, or deleted depending upon the status level (i.e., approved portfolio, unfunded, withdrawn, etc.). This information is stored in the database. PTS uses Business Objects as its reporting tool. All PTS data including the data imported from IFS is reportable through Business Objects. 18 universes supporting a variety of different views of the PTS data enable users to create, save, and schedule their own reports.

During the Execution year (i.e., current year), SPIs are locked down preventing modification to the accounting lines contained within the SPI. Accounting lines are modified through the creation of a Fund Center Change (FCC). Based on predetermined approval paths, the FCC is approved and requested amounts are moved from one accounting line to another between SPIs. Internal Order Code Requests are also managed by PTS to ensure that these 5-character and 8-character codes are properly managed between both PTS and IFS. Addition/deletions/changes to Internal Order Codes are managed through an approval workflow. Additionally, PTS manages all IT Unfunded Requests.

C.1.1 CURRENT HARDWARE AND SOFTWARE ENVIRONMENT

PTS is a Java web-based application that uses a Microsoft SQL server backend accessible through the IRS Intranet and resides in a virtual environment. The PTS hardware environment uses a three-tier client-server approach to isolate the business logic, database logic, and Graphical User Interface (GUI) into independent tiers. The software environment is a user interface made up of a set of web pages viewed in the current IRS standard Internet browser (IRS standard is Microsoft Edge) and is isolated from the business logic of the system. PTS uses IRS Single Sign-On for authentication. A user's IRS ID is compared to a list of valid PTS user accounts to determine if login is possible.

C.2 - TASK ORDER OBJECTIVES

The IRS programmatic objectives of this task order are to fulfill the following business process requirements to be supported by the Project Tracking System:

• Multi-Year Planning: Drives the development of budget years (BY and BY+1). Multi-year Planning allows IT leadership to view IT spending over a five-year horizon so that all future impact on a project on the overall IT portfolio can be analyzed.

• Budget Formulation: Transforms multi-year strategic planning projections into a structured, enacted budget approved by Congress. Budget Formulation capabilities drive implementation of the IT budget by guiding the growth and development of out-year investment portfolios.

• Plan Development: Refines the formulated budget into an IT spending plan that meets the IRS strategic vision while remaining in alignment with anticipated funding levels. Plan Development capabilities support the creation of a spend plan that specifies how IT will execute approved funding, analyze historical spending, manage project dependencies, and track organizational and financial code changes.

• Budget Execution: Administers the IT spend plan to support the delivery of IT products and services to its customers and stakeholders. Budget Execution capabilities enable tactical executive decision-making by analyzing current year activities and tracking performance against strategic goals.

Table 1-2 defines the corresponding fiscal year for each of the above IT budget processes.

Table 1-2 -- IT Budget Processes:

and

BY+2

and PY+1 or CY+2

The IRS acquisition objectives of this award are to acquire the services of a contractor to provide:

· Maintenance of the existing PTS application and database which cannot be performed by the Financial Management Services (FMS) Division; the application currently contains data for Fiscal Year (FY) 2019 through 2026

· Advice as a member of the PTS Change Control Board (CCB)

· Development, testing and implementation of additional enhancements and defects as identified and approved by the CCB (such as PTS Graphical User Interface enhancements)

· Additional enhancements as identified by the CCB

· Technical support that cannot be performed by FMS

· Support for the interfaces with IRS’ Financial and Procurement systems of record; Integrated Financial System (IFS), and Procurement for Public Sector (PPS)

· Support for Single-Sign On using IRS Active Directory Federation Services (ADFS) interface

· Support mitigating risks identified in the Security Assessment & Authorization (SA&A) process that cannot be performed by FMS

· Technical support for the Business Objects (BO) reporting tool

· Maintenance and support for the PTS Computer Based Training (CBT) tool

· Support to Integrate with other IRS certified COTS products including SharePoint Online

C.3 - DESCRIPTION OF SUB-TASKS

This Performance Work Statement (PWS) is a Performance-Based Acquisition with mission-oriented, event-driven performance measures and incentives.

The Contractor shall provide technical services to continue maintenance of the application software. These services include requirements analysis, design, development, modification, testing and implementation. Management of the PTS application is governed by the Change Control Board (CCB) where requirements are approved/disapproved, and prioritized, i.e., improvements to execution and plan development modules, and addition/modification of screens. Technical support of the Business Objects reporting tool is also required. The Contractor shall provide knowledge transfer to IRS personnel for continued hardware/software support, as well as the supporting system and end-user documentation. Monthly status reports are required as well as meeting notes (i.e., weekly PTS meetings, monthly CCB meetings, additional presentations of new developments as necessary). The Contractor shall provide system support during core business hours. Systems development work shall be done in accordance with IRS cybersecurity established standards and guidelines, Section 508 accessibility guidelines, Capability Maturity Model Integration (CMMI) for Development Level 3, and Tier II standards.

FIRM FIXED PRICE (FFP) SUB-TASKS

C.3.1 SUB-TASK 1, ORIENTATION BRIEFING

Within five business days after contract award, the Contractor shall conduct an orientation briefing for the Government. The Government does not desire an elaborate orientation briefing, nor does it expect the Contractor to expend significant resources in preparation for this briefing. Rather, the intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task order participants, explaining their roles, reviewing communication ground rules, and assuring a common understanding of task order requirements and objectives.

The orientation briefing shall be held at the Government's facility 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 task order will 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 GFP to the Contractor for this requirement.

4. Any issues concerning the Contractor clearances for contractor personnel will 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 task order.

DESIRED OUTCOME:

The Contractor shall provide minutes of the Orientation Briefing to the Government within five business days after the meeting.

C.3.2 SUB-TASK 2, DEVELOP/MAINTAIN/ENHANCE THE PTS APPLICATION, AND PROVIDE SERVER SUPPORT

The Contractor shall perform the full software development lifecycle for the PTS application supporting the development/maintenance/enhancement, including bug fixes, as directed by the CCB. This work shall cover the full scope of IT Budget business processes. The contractor shall ensure all technical work is consistent with the CMMI for Development Level 3 standard. The Contractor shall assist the IRS with Release Management. With each Release, the Contractor shall create test scripts for End-User testing, the Release transmittal and the Release script. The Contractor shall upload each new version to the Development server and then assist the IRS DBA/SA to upload it to the TEST server for End-User testing. After the Technology Support Team has tested and approved the changes, the Contractor will assist the DBA/SA with uploading the final version to the PRODUCTION, and DISASTER RECOVERY servers. In addition, the Contractor shall work to resolve server issues with the IRS DBA/SA which include identifying/solving problems with system performance and system/server crashes. Other activities include enhancement for connectivity, and report assistance with the Business Objects (BO) report tool and maintenance of the PTS BO universes, which includes ensuring the universes match the PTS data model based on updates in each PTS release. The Contractor shall configure and maintain PTS for operation on the IRS intranet.

The Contractor shall work the Release process. The application modifications/additions shall be delivered fully tested by the Contractor, and uploaded to the TEST servers which operate in a virtualized environment. After IRS End-Users have fully tested and approved the changes and the Contractor has corrected the errors, the Contractor shall assist the IRS DBA and SA with the Release upload to the PRODUCTION server and DISASTER RECOVERY servers. A minimum of five Releases and 80 change requests per Period of Performance (POP) is required unless directed otherwise by the CCB. Application issues causing PTS downtime should be resolved within one business day.

C.3.3 SUB-TASK 3, MAINTAIN/UPDATE PTS INTERFACES

Four automated interface files and two manual files are uploaded into PTS from the Procurement for Public Sector (PPS) and the Integrated Financial System (IFS). The Contractor shall modify PTS and/or the Interface files to support the Spending Plan and Execution requirements. When the incoming IFS Interface files change, the Contractor shall update the uploaded file, as well as the reporting tool (Business Objects Universes). When the interfaces fail, the Contractor shall work with the IFS team/DBA/SA/Technology Support Team to resolve problems to ensure the Interfaces are received correctly each morning. The IFS/PPS interfaces use standard IRS Electronic File Transfer Utilities (EFTU) and must meet all IRS security standards. The Contractor shall work with the Execution team to upload the correct files. All interface enhancements, changes, and additions will be approved/disapproved/prioritized through CCB approval process.

DESIRED OUTCOME:

Daily transfer of four (4) IFS/PPS interface files to PTS. Data is accessible and reportable using the BO report tool and is accurately displayed in PTS (in the IFS Expenditure module and on the SPIs). In addition, the Contractor shall work with Execution team to ensure the manual files are correctly uploaded.

C.3.4 SUB-TASK 4, COMPUTER BASED TRAINING (CBT) MODULE

The Contractor shall update the CBT module annually. This module provides an overview of PTS for new PTS users and is used as an introduction and supplement to hands on training to be conducted by IRS staff. Annually, the contractor will provide a list of recommended changes to the Technology Support Team, who will then select and approve a subset of changes for the CBT updates.

An annual update of the PTS CBT module with approved changes that can be displayed on IRS workstations.

C.3.5 SUB-TASK 5, DOCUMENTATION

The Contractor shall develop and maintain end-user and systems documentation to comply with the standards of the Enterprise Life Cycle (ELC) and the Security Accreditation & Authorization (SA&A) process.

This required documentation includes: Software Version Description (SVD), System Design Document (SDD), Silk Central Test Scripts, Business Systems Requirements Report (BSRR), Configuration Management (CM) Worksheet, Database Schema, End of Test Reports, ERD, Owner Manual, Requirements Traceability Verification Matrix (RTVM), PTS System Test Plan (STP), Data Dictionary, and 508 documents.

Prior to each CCB meeting, the Contractor shall provide to the COR a Discrepancy Report Summary (DR)/ Engineering Change Proposal (ECP) Summary Report to track programming changes and discrepancies. The CCB shall reprioritize the ECPs and DRs for future work accomplishments. Prior to the start of the User Acceptance Testing (UAT) and Functional Integration Testing (FIT), the Contractor shall provide test scripts in Microsoft Excel or a format determined by the COR. Three weeks after each Release, the required documents in accordance with the IRS Enterprise Life Cycle (ELC) shall be provided to the COR in a digital format. Copies may be uploaded to an IRS SharePoint folder. The User Manual shall be updated whenever a software release significantly changes system functionality.

The contractor shall also provide a softcopy of the source code after each application upgrade.

DESIRED OUTCOMES:

Updated documents and source code listed above shall be provided to the COR after each Release.

C.3.6 SUB-TASK 6, MONTHLY STATUS REPORTS, WEEKLY PROGRAM MANAGEMENT REVIEW MEETINGS, MONTHLY CCB MEETINGS, AND ADDITIONAL MEETINGS AS NEEDED

The Contractor shall prepare and submit to the COR a Contract Performance Report (CPR) each month describing the amount of work scheduled and achieved to date and the actual costs associated with that work. All tasks supporting a single deliverable or work product, regardless of the owner/supplier of each task, shall be organized together and rolled up to a single element and summary level task in the project schedule. This report will document work completed since the last reporting period. This report will provide the ongoing status of all tasks performed during the reporting period. The monthly status report will contain the following information at a minimum:

· Report Date

· Period of Performance covered by the Status Report

· Cumulative and Reporting period totals for Labor, and software application or other functional area

· Software application or other functional area of work accomplished during the reporting period

· Issues/Problems – for every issue/problem, a description of the proposed solution and estimated time to resolve

· Description of work planned for next reporting period including significant milestones and work products

The Contractor’s Project Manager shall attend weekly Program Management Review meetings with the IRS to discuss immediate issues or concerns relative to the PTS (On-line or in-office). These shall include but not limited to ECP progress/issues, personnel changes and critical schedule or milestone changes.

The PTS CCB shall meet (on-line or at the IRS site) monthly or more frequently if needed, to identify/establish a prioritization of changes/corrections to PTS stated in ECP’s prepared by the Contractor to approve or recommend technical solutions. Required attendees of the CCB are the Contractor Project Manager, IRS Project Manager, the COR, and FMS Support Services staff (representing functional areas), Budget Execution staff, and Plan Development staff.

DESIRED OUTCOME:

The Monthly Status Report shall be delivered no later than COB on the 5th Government business day of the month following the reporting period. This report will be provided in electronic format (MS Word 2016).

The Contractor shall attend weekly Program Management Review meetings with the IRS to discuss immediate concerns or issues (i.e., ECP progress/issues, personnel changes and critical schedule or milestone changes). The Contractor shall provider an agenda prior to the meeting and meeting minutes after the meeting.

In addition, the Contractor shall attend monthly CCB meetings. Documents such as the Engineering Change Proposals (ECPs), and Discrepancy Reports (DRs), shall be provided to the IRS Project Manager and COR prior to each CCB meeting. The Contractor shall also provide additional presentations to management, FMS, or Business Units outside of IT as needed. Electronic versions of presentation minutes for each of the above meetings shall be e-mailed to the COR and IRS Project Manager.

C.3.7 SUB-TASK 7, TRANSITION PLAN

The Contractor shall submit a transition plan describing how they will assume the responsibilities of PTS support from the incumbent contractor within 30 days of contract award. The transition plan shall describe how contractor staff will learn about the PTS application, its interfaces, and the IT budgeting processes within 30 days of contract award.

DESIRED OUTCOME:

Contractor staff will be able to leverage prior Federal IT budgeting experience and experience with budgeting systems of similar size and scope to support the PTS after the transition period with a high degree of effectiveness. The ideal transition plan will minimize the interruption of IRS or incumbent contractor normal business operations. The Transition Plan shall be delivered during the base year only.

C.3.8 SUB-TASK 8, TRANSITION TO SUPPORT (T2S)

The transition to support process shall include, but not be limited to the following:

· Knowledge transfer of technical skills and lessons learned to IRS staff upon completion of deliverables and work products.

· Operations and maintenance processes and procedures. The Contract shall recommend enhancements to system administrator functionality as part of the CCB to allow Government to better manage the PTS application.

· A complete copy of the source code and complete documentation produced during the tenure of the contract. In addition, any deliverables including, but not limited to, requirements documentation, screenshots, mockups, database queries in a softcopy format 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 configurable data including maintenance of the Single Sign-On functionality and application settings.

· Any software tools and applications developed to support and maintain the PTS application.

The Contractor shall assist the IRS employees to acquire the knowledge, skills and to enable them to answer PTS customer questions about technical release, system updates or system functionality according to the above listed bullets. Source code and all above listed documentation shall be provided to the IRS.

C.3.9 SUB-TASK 9, PROVIDE SYSTEM HELP DESK SUPPORT FOR THE IRS TECHNOLOGY SUPPORT TEAM

On a “call back basis” the Contractor shall provide a central point of contact for system and End-User related problems during core business hours (8:00 am to 4:00 pm M-F EST). System issues include system crashes which require coordination with the IRS DBA/SA to bring PTS back up as well as assistance identifying the root cause for the crash. End-user related problems such as data discrepancies may require Contractor assistance when the Technology Support Team is unable to resolve the problem. All problems will be submitted in writing via email to the Contractor by a member of the IRS Technology Support Team and will be issues or problems that the IRS Technology Support Team is unable to correct or address.

Contractor responses/solutions to problems will be received by the Technology Support Team within five (5) hours (during a business day) and will be technically correct. Application crashes will be resolved within one (1) business day and solutions to system problems will be provided to the IRS Technology Support Team. The Technology Support Team will be able to respond to the End-User.

C.3.10 SUB-TASK 10, PERIOD OF PERFORMANCE SUMMARY REPORT

Provide a summary of work performed, including a list of deliverables, at the end of each Base and Optional Period of Performance.

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

DESIRED OUTCOME:

The Contractor shall provide the Summary Report at the end of the Base Period and each Period of Performance.

C.3.11 SKILL REQUIREMENTS

Continued support is required for the development/update of the PTS application. The Contractor personnel must have the ability, knowledge and skills to provide support for development, maintenance, testing, implementation, training, documentation, security compliance, 508 compliance and CMMI Level 3 appraisal. Additional enhancements are required to provide the functionality necessary to support the growing IT community. Extensive knowledge of the following IRS business processes is required: IRS program management, budget execution, budget planning (i.e., Portfolio and Investment Process (PIP)). Knowledge of the Integrated Financial System (IFS) execution accounting data is essential to support the creation and upload of the Journal Voucher (JV), the Fund Code Change (FCC) requests, IT Unfunded Requests, and the Internal Order Code (IOC) requests from PTS into IFS. The JV upload creates the Plan Year Budget in IFS which on October 1, transitions to the Execution Year budget. This fiscal year transition from planning year data to execution year data is critical and requires thorough analysis and accurate manipulation of accounting code data. These uploads keep IFS and PTS in sync. Also essential is detailed knowledge of the shopping cart data in the PPS (Procurement for Public Sector) system to support the daily upload of a Requisition Pipeline file. A thorough understanding of the four (4) interface files from IFS (daily), and a working knowledge of the BO (Business Objects) reporting tool is also essential. Comprehensive knowledge of these systems and interface files, as well as knowledge of the IRS IT technical and program management environments, is both unique and critical for the continuity of the PTS system and on-going development.

Extensive experience with the techniques, tools, and algorithms is essential which form the core of the analytical capabilities of the PTS. The techniques employed on PTS for the continued support of the system are:

· Development of the logical accounting model which associates Commitment Accounting based expenditures with project and program planning information

· Knowledge of ADFS and SAML to support PTS Single Sign-On

· Development of User and Group role-based access limitations and account management related to project and planning information

· Development of dynamic table editing capability for maintenance of reference data

· Development of a web-based technique to input data from Microsoft Excel Files into the PTS database and output data from the PTS database to Microsoft Excel

· Skill and expertise in JAVA programming using the Spring Framework and the Wildfly Application Server

· Development of web pages using the Bootstrap Framework

· Multiple applications of techniques to constantly update results displayed on the screens to reflect the latest data stored in the database (All updates for real time)

· Skill and expertise in SQL for the development of the Relational Data Model at the core of PTS

· Application implementation using Transaction Management techniques.

· Implementation of all techniques in a SEI CMMI Level 3 appraised environment

The Contractor shall demonstrate skills required to perform the work on the applications systems specified. Skills include programming in languages used in the specified applications, systems testing, documentation, and training.

C.3.13 LABOR HOUR ESTIMATES

The Government estimates that a range of 6,500 to 7,000 labor hours will be expended under the one (12) month Base Period and each proposed twelve (12) month Option Period.

C.4 - PERFORMANCE REQUIREMENTS, STANDARDS AND SURVEILLANCE

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

C.4.1 - PERFORMANCE REQUIREMENTS

Performance requirements include the Desired Outcomes and Required Services and are defined by the Government. Attachment 1 defines the desired outcomes as successfully completing specified Sub-tasks including all deliverables, work products and support as indicated in Attachment 2. This aligns the Contractor’s objectives with the Government objectives, which are to successfully complete the Sub-tasks and deliver value-added products and services to the end users.

C.4.2 - PERFORMANCE STANDARDS

Performance Standards have been identified in Attachment 1 for each of the Subtasks.

C.4.3 - SURVEILLANCE

The surveillance process has two interrelated parts: The Monitoring Method identified in Attachment 1 and the Quality Assurance Surveillance Plan (QASP) included as Attachment 3. The Contractor shall establish and maintain a complete Quality Control Plan (QCP) in accordance with Section 7 of the QASP (Attachment 3). This links the Government and Contractor’s quality assurance efforts into an integrated package with shared objectives.

C.5 - GOVERNMENT-FURNISHED PROPERTY (GFP)

GFP (to include material, equipment, and/or information) may be provided in the performance of this task order. See also H.11, H.12 and H.27 of the contract. The following GFP will be provided to the contractor:

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

C.6 GOVERNMENT-FURNISHED INFORMATION

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

INFORMATION ITEMS

Documentation listed in Sub-Task C.3.5

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

C.7 - TRAVEL– Not Applicable

C.8 - REPORTS

Reports shall be at the following level (check only one):

|X| Task Order (least detailed)

|_| Sub-Task (more detailed)

C.9 - ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

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

Internal Revenue Service IR Federal Building 1111 Constitution Avenue, N.W Washington, D.C. 20224

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

PART II - ADDITIONAL REQUIREMENTS

D.1 - PACKAGING AND MARKING

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

Section E INSPECTION AND ACCEPTANCE

E.1 INSPECTION

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

E.2 - GENERAL ACCEPTANCE CRITERIA

The general quality measures as set forth below will be applied to each work product received from the contractor under this task order.

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

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

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

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

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

· The IRS will inspect Deliverables for conformance as specified in this Section of the delivery order. Upon receipt of any Deliverables, the IRS will have five (5) federal business days to review, comment, and accept or reject Deliverables. Any rejection will state the basis for the rejection; include a specific reference to the delivery order paragraph or section with which the deliverable does not conform and identify the corrective action or rework that is considered to be required.

· Any rework required due to rejection will be at no cost to the government.

· Rework required shall be completed within three (3) federal business days after notification from the IRS. When the Contractor returns the reworked Deliverable, the IRS will re-inspect the deliverable within five (5) federal business days of receipt for verification that written deficiencies have been addressed and incorporated, as necessary.

· Work Products are provided to demonstrate sufficient progress toward a required product, service or deliverable. Work Products are not subject to a formal deliverable review process. All Work Products will be made available in accordance with the due date(s) approved by the CCB. The Government may provide comments to the Contractor within five (5) federal business days after receipt of Work Products.

E.3 - SPECIFIC DELIVERABLE ACCEPTANCE CRITERIA

Sub Task 1: ORIENTATION

Government review of deliverables and acceptance criteria

Sub Task 2: DEVELOP/MAINTAIN/ENHANCE THE PTS APPLICATION, AND PROVIDE SERVER SUPPORT

Sub Task 3: MAINTAIN/UPDATE PTS INTERFACES

Sub Task 4: COMPUTER BASED TRAINING (CBT) MODULE

Sub Task 5: DOCUMENTATION

Sub Task 6: MONTHLY STATUS REPORTS, WEEKLY PROGRAM MANAGEMENT REVIEW MEETINGS, MONTHLY CCB MEETINGS, AND ADDITIONAL MEETINGS AS NEEDED

The Contractor shall attend weekly Program Management Review meeting and monthly CCB meetings. Requirements documented such as Engineering Change Proposals (ECPs), and Discrepancy Reports (DRs), shall be provided to the IRS Project Manager and COR prior to each CCB meeting. The Contractor shall also provide additional presentations to management, FMS, or Business Units outside of IT as needed. Electronic versions of presentation minutes for each of the above meetings shall be e-mailed to the COR and IRS Project Manager.

Sub Task 7: TRANSITION PLAN

Sub Task 8: TRANSITION TO SUPPORT (T2S)

Sub Task 9: PROVIDE SYSTEM HELP DESK SUPPORT FOR THE IRS TECHNOLOGY SUPPORT TEAM

Sub Task 10: PERIOD OF PERFORMANCE SUMMARY REPORT

Sub Task 11: SKILL REQUIREMENTS

E.4 - REVIEW OF DELIVERABLES

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

b) 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.

c) 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.

F.1 - ORDER PERIOD OF PERFORMANCE

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

F.2 - PLACE OF PERFORMANCE

|X| 100% Contractor’s site, with reasonable access to government site (contractor personnel can travel to government site for meetings within twenty-four hours’ notice and at reasonable travel costs.)

F.3 - SHIP TO

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.

F.4 - DELIVERABLES

Unless otherwise requested in writing by the COR, work products shall be produced using Microsoft Office 2016 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.

SECTION G: LIST OF ATTACHMENTS

Attachment 1 - Performance Requirements, Standards, Surveillance and Incentives Attachment 2 – Deliverables and Work Products Attachment 3 - Quality Assurance Surveillance Plan (QASP) Attachment 4 – High Level Project Schedule

Attachment 1 Performance Requirements, Standards, Surveillance and Incentives This Attachment describes the desired outcomes, performance requirements, standards, surveillance methods, and incentives for this task order. The Table below is divided into 11 discrete subtasks (as applicable): It is intended to align Contractor’s goals and objectives with the IRS program goals and objectives as follows:

This is specific to the program/project PWS, below are examples:

1. Gain continuity and a stable knowledge base to leverage expertise and to significantly streamline project and program management processes to efficiently and effectively manage projects in the Investment Portfolio.

1. Move projects through the system development life cycle with the required program management oversight as MITS systems are integrated into larger enterprise efforts.

The Tables below reflects the guidance and methods for determining metrics, Acceptable Quality Levels, and incentives/disincentives for this PWS.

The elements of Documentation Quality, as used herein, are defined below.

The Contractor shall provide all information in accordance with the required IRS standards and guidelines as stated in Section C of this PWS task order.

All Deliverables, Documents, and Services shall satisfy program and project requirements, and comply with IRS CMMI standards, existing IRS standards and guidelines, and integrate with IRS, security requirements and Section 508.

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

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

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

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

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

All deliverables considered “Unacceptable” and not in accordance with the elements of Documentation Quality as stated below will be returned to the contractor for rework, correction and updates. The Contractor shall re-submit the deliverables to the Government within (5) five business days at No Additional Charge to the Government.

Sub-task 1: Orientation Briefing

Desired Outcomes: The intent of the briefing is to initiate the communication process between the Government and Contractor by introducing key task order participants, explaining their roles, reviewing communication ground rules and assuring a common understanding of task order requirements and objectives.

Required Services: The Contractor will identify and introduce their proposed personnel who will perform work under this PWS. The Government will identify their personnel and will show the Contractor the Government site where the work is to be performed. Government Furnished Property will be discussed and distributed. Any issues concerning contractor clearances will be discussed. The Contractor personnel shall take meeting minutes and maintain a “Sign-In” Sheet for meeting attendees. Both the meeting minutes and “Sign-In” sheet shall be provided to the Government within five (5) business days after completion of the Orientation Briefing. At the meeting conclusion, the Contractor shall demonstrate a full understanding of the work to be accomplished under this PWS.

Performance Standard

Acceptable Quality Level (AQL)

Monitoring Method

Incentive/Disincentive

Deliver Orientation Briefing

Prepare Sign-In Sheet and have Meeting Participants Complete.

Take Meeting Notes.

Provide copy of Briefing Slide/notes presented at briefing along with names, telephone numbers and addresses (physical and e-mail) for key task participants as well as roles for both the Contractor and Program Office.

The Contractor attended the briefing and delivered the required services and information on the date specified in the task order as stated in Section C.3.1 of the PWS.

The Contractor identified and introduced their proposed personnel who will perform work under this PWS.

Contractor clearance issues were discussed, and the Contractor demonstrated a full understanding of the work to be accomplished and demonstrated an urgency to have his personnel available to start working as soon as possible.

The Contractor delivered the meeting minutes and “Sign-In” sheet to the Government within five (5) business days after completion of the Orientation Briefing.

If all desired outcomes are met as outlined in Section C.3.1, the Briefing will be rated as “Acceptable” by the Government.

The Government Program Manager and the COR shall attend the briefing on the date specified in the task order as stated in Section C.3.1 of the PWS and document validation of attendees. The Contractor shall take meeting minutes and create a sign-in sheet to document attendees, activities, and action items.

Meeting minutes will be evaluated against the elements of Documentation Quality as stated in Attachment 1.

This briefing is a one-time only occurrence.

For all deliverables meeting the AQLs stated in this PWS for this Subtask, “Positive” customer feedback will be reported to the Contractor by summarizing the past year’s surveillance activities under the Contractor Performance Assessment Reporting System (CPARS) administered by the Naval Sea Systems Command (NAVSEA).

Deliverables which do not meet the AQL’s stated in this PWS for Subtask 1, “Negative” customer feedback will be reported to the Contractor by summarizing the past year’s surveillance activities under the Contractor Performance Assessment Reporting System (CPARS) administered by the Naval Sea Systems Command (NAVSEA).

Sub-task 2: Develop/Maintain/Enhance the PTS Application, and Provide Server Support

Desired Outcomes: The Contractor shall work the Release process. The application modifications/additions shall be delivered fully tested by the Contractor, and uploaded to the TEST servers which operate in a virtualized environment. After IRS users have fully tested and approved the changes and the Contractor has corrected errors, the Contractor shall assist the IRS DBA and SA with the Release upload to the PRODUCTION server and DISASTER RECOVERY servers. A minimum of five (5) Releases and 80 change requests per Period of Performance (POP) is required unless directed otherwise by the CCB. Application issues causing PTS downtime should be resolved within one (1) business day.

Required Services: With each Release, the Contractor shall analyze, program, test, and upload to the DEVELOPMENT server, changes approved by the CCB. Next, the Contractor shall create test scripts for End-User testing, the Release transmittal and the Release script. The Contractor shall assist the IRS DBA and SA with uploading the new version to the TEST, PRODUCTION, and DISASTER RECOVERY servers. In addition, the Contractor shall assist the IRS DBA/SA identify/solve problems with system performance as well as work with DBA/SA to resolve server crashes.

Monitoring Method

Incentive/Disincentive

When errors are found during testing, the Contractor will make programming corrections and the Technology Support Team will then retest the corrections.