RFQ 8384 Attch 1 PWS.pdf

RFQ 8384

8/16/2024

Attch 1

Performance Work Statement (PWS)

Compliance Data Warehouse (CDW) Data and Analytics

1.0 INTRODUCTION AND BACKGROUND

Recent advances in large-scale analytic computing technologies have the potential to radically improve business processes in the Internal Revenue Service (IRS). It is now possible to combine disparate, multi-structured, and distributed datasets to enable predicting the future behavior of taxpayers to precise treatment strategies, smart workload plans, and better targeted outreach. The Research, Applied Analytics, and Statistics (RAAS) organization is helping its business partners achieve these and other goals through an enterprise data ecosystem for research and analytics that enables knowledge discovery and actionable decisions from the vast amount of new and diverse datasets that are rapidly becoming available in nearly every area of tax administration.

To generate the greatest benefits from the vast resource of data available for enterprise analytics, a set of strategies is needed within RAAS to sponsor and advance data-intensive applications and large-scale data management and analysis. These strategies support the collection and integration of large, diverse data datasets from which decisions and discoveries are based; enable new capabilities in data-driven innovation; expand research collaboration through better sharing of data assets; accelerate the process of scientific discovery; and lead to new fields of research and inquiry that would otherwise be impossible.

As technologies for analytics mature, research initiatives increasingly rely on data- driven solutions to drive new discoveries for decision making. Investments are needed in resources for large-scale data collection, analysis, management, and for the privacy, security, and ethical issues of an enterprise data ecosystem for research. Prior investments in data and technology for research have been significant drivers of successes in risk discovery, behavioral insights, workload planning, and internal operations. More recent research-funded initiatives have resulted in the creation of improved ID theft models, refund fraud filters, tax gap estimates, burden measures, case selection algorithms, and a deeper understanding of the mechanisms that drive taxpayer behavior.

To address this challenge, RAAS must obtain services that will allow the IRS to adapt to and leverage data and analytical technology to create fundamentally new insights and capabilities. Contractor support is critically needed in areas that involve the collection of large, heterogenous, and multi-modal data in the IRS mainframe environment; the management of vast amounts of data for a full range of use patterns in advanced analytics; and the administration of systems and technology infrastructure in a Linux

Attch 1 environment to ensure a secure and well-functioning data and analytics ecosystem.

2.0 TASK ORDER OBJECTIVES

The objective of this Performance Work Statement (PWS) is to obtain contractor support for a coordinated set of requirements to manage vast amounts of data for analytics in the RAAS computing environment. This includes the collection of legacy data from the IRS mainframe environment and the administration and maturity of systems and databases used to host data and analytical software.

Mainframe Support

Over 50 data sources are collected, integrated, and standardized in the RAAS computing environment, an effort that makes thousands of database tables and over 275,000 database columns accessible to the IRS research and analytical community.

Many of these data sources originate in the IBM z/OS mainframe environment in formats that include ASCII, packed decimal, VSAM, and DB2. Some extract programs are written and maintained in Assembly Language.

RAAS has a requirement to support the continuation of mainframe extracts from all formats while simultaneously converting its Assembly Language programs to Java. This objective aims to mitigate the future risk of a skills gap in Assembly Language programming, provide greater flexibility in language abstraction for change management, and ensure continuity and stability in overall mainframe-based data Management.

System and Database Management

RAAS is the center of enterprise analytics in the IRS. Demand for data and analytical services continues to increase across all IRS business units, including requests for new data sources from the mainframe environment. While some source data is consumed in its raw state, e.g., large text files or special project data, most of the data collected by RAAS are still processed via Extract, Transform and Load (ETL) routines and loaded into SAP/Sybase IQ, analytic database. RAAS has a need for relational database support that involves ETL/T, account management, performance tuning, monitoring, and other activities detailed in the sub tasks below. In addition to relational database structures, RAAS is increasingly developing graph-relational models that utilize graph databases to facilitate the analysis of complex relationships between people, places, and things in the tax administration space. Knowledge and understanding with both relational database management systems and graph databases is required for this effort.

To meet current service levels for analytical computing, this effort will also require support for the advancing new Linux solutions in the RAAS computing environment.

Research analysts currently access and analyze data on multiple platforms with different analytical tools addressed in Section 3.11 Skill Requirements. The Government

Attch 1 will require contractor assistance to incrementally establish, test, and deploy these solutions to mature its heterogeneous environment.

3.0 SCOPE OF WORK AND DESCRIPTION OF TASKS

This PWS is Performance-Based Acquisition and is a Firm Fixed Price (FFP) with mission-oriented, event-driven performance measures and incentives.

The scope of this Performance Work Statement (PWS) encompasses Contractor support for RAAS mainframe data access and systems and database performance optimization.

Subtasks are as follow:

Sub-Task # Title Contract Type

1 Orientation Briefing FFP 2 Ramp-Up Knowledge Transfer / Transition-In (Optional) FFP

3 Period of Performance Summary Report FFP 4 Mainframe Data Extracts FFP 5 Linux Administration FFP 6 Advance Linux Environment Maturity FFP 7 Relational Database Management Support FFP 8 ETL and Support Documentation for Graph Database

Environment

FFP

9 Performance Enhancements for Graph Database Environment

FFP

10 Transition Out (Optional) FFP

3.1 SUB-TASK 1, ORIENTATION BRIEFING (FFP)

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

The orientation briefing shall be held at the Government's facility. 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

Attch 1 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 at this time.

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 - Initiate the communication process between the Government and Contractor and assure a common understanding of task order requirements and objectives. Contractor delivers Orientation Briefing Minutes to Contracting Officer’s Representative (COR) within 5 business days after Briefing. Contractor delivers Quality Control Plan to the COR within 60 business days after the Briefing.

3.2 SUB-TASK 2, RAMP-UP KNOWLEDGE / TRANSFER–IN (OPTIONAL) (FFP)

Ramp-Up Knowledge Transfer is defined as the Contractor acquiring and understanding the necessary documentation, information, and processes related to any work in progress. This task includes meeting with the IRS Subject Matter Experts frequently to gather any tacit knowledge related to the Core Systems, Compliance Document Matching and Solutions Engineering/Enterprise Services tasks or programs in development. The government estimates this task will take approximately four to six months to complete after award for the new awardee to achieve complete Ramp-up.

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 the first 15 business days after award. The KTP shall identify the Contractor resources and roles involved in the transfer process, provide a list of risks and mitigation strategies for the transfer, and contain a detailed resource balanced project schedule developed with Microsoft Project. The project schedule shall identify tasks, dependencies, deliverables, and milestones. The project schedule shall be at a sufficient level of detail to track progress on a bi-weekly basis, (i.e., all tasks will be detailed to a level such that no task has duration of more than 10 workdays).

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

The contractor shall meet with the IRS bi-weekly (twice a month) to discuss the progress of the knowledge transfer. The Contractor shall show an updated MS Project

Attch 1 schedule and discuss current risks or concerns.

DESIRED OUTCOME – The Contractor provides a Knowledge Transfer Plan that is accepted by the Government and successfully completes knowledge transfer in accordance with the plan.

3.2.1 Transition-In

The Transition-In task permits for an effective transition from the incumbent Contractor to a new Contractor and shall not exceed 60 calendar days from the contract award date (i.e.-Incumbent available to assist new awardee). 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 follow the approved Transition-In Plan submitted as part of their proposal 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 Sub-Task would be worked concurrently with Sub-Task 2, Ramp-Up/ Knowledge Transfer.

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

• Assign personnel and submit security papers promptly to get the background investigations done quickly and gain access to IRS’s network.

• Request access to tools and documentation.

• Review and understand all the technical and process documentation.

• Review and understand the existing data and system security policies in place.

• In support of this task, the Contractor shall be responsible for completing the following deliverables:

Deliverable Purpose Transition-in Checklist The Transition-in Checklist provides a vehicle to verify completion of the necessary transition-in activities. The Transition-in Checklist shall be developed by the Contractor and shall include all necessary activities to ensure an effective transition from incumbent Contractor to a new Contractor were performed.

The Transition-in Checklist shall be signed by both, the Contractor and the COR after completion of the task.

Attch 1

3.3 SUB-TASK 3, PERIOD OF PERFORMANCE SUMMARY REPORT (FFP)

The contractor shall 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 (CO). 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 Period of Performance Summary Report.

3.4 SUB-TASK 4, MAINFRAME DATA EXTRACTS (FFP)

The Contractor shall work on a small team to create, schedule, submit, and maintain data extract programs in the IRS z/OS mainframe environment. Data source formats will be in ASCII, packed decimal, VSAM, or DB2 and may have varying internal data structures. For example, ASCII and packed decimal data may exist in files that are hierarchical or varying length. The Contractor shall use either Assembly Language or Java as the programming language.

Data extracts from IRS source systems shall be performed on a timetable specified by the government. Typical examples of extract frequencies include weekly, monthly, quarterly, or ad-hoc. In addition to performing data extracts, the Contractor shall assist with transferring extracts over the IRS network to the RAAS computing environment.

Both the IRS mainframe and RAAS computing environments are co-located at the Enterprise Computing Center at Martinsburg, WV.

DESIRED OUTCOME – The contractor shall create and execute data extract programs or processes in the z/OS mainframe environment to ensure the timely release of data to RAAS customers and stakeholders who perform analytics and reporting.

3.5 SUB-TASK 5, LINUX ADMINISTRATION (FFP)

The Contractor shall provide system administration support for Linux servers in the RAAS computing environment. Specific sub-tasks shall involve one or more of the following:

• Administer basic Linux operating system tasks for one or more servers.

• Install, test, and maintain new OS patches, system software, and software for analytics, including these software products: SAS, STATA, R, RStudio, RShiny, Python, Anaconda, Jupyter Notebooks, and Kubernetes.

• Create accounts, analyze system logs, manage incident response, ensure system high-availability (five-nines), and optimize system performance.

• Document changes to system processes, configuration, and other change management procedures.

Desired Outcome - The contractor shall administer basic Linux operating system tasks for one or more servers in the RAAS computing environment to support new and ongoing user-focused analytic operations.

3.6 SUB-TASK 6, ADVANCE LINUX ENVIRONMENT MATURITY (FFP)

The Contractor shall assist in advancing the program and process maturity of Linux servers in the RAAS computing environment. Specific sub-tasks shall involve one or more of the following:

• Create and deploy Docker containers and Kubernetes orchestration for open-source analytical tools, e.g., R, RStudio, RShiny, Python, Anaconda, Jupyter Notebooks, TensorFlow, PyTorch, RAPIDS, DASH, etc.

• Install, configure, and deploy Lightweight Directory Access Protocol (LDAP) services to create centralized authentication across heterogeneous platforms.

The RAAS computing environment is in the early stages of deploying the above solutions to strengthen system administration in its analytical computing environment, which includes multiple open sources tools. The Government is seeking assistance to incrementally develop, test, and deploy these solutions to better manage its heterogeneous environment.

DESIRED OUTCOME - The contractor shall add maturity to the RAAS analytical computing environment through services and solutions that will enable greater technical and administrative efficiencies, lower the cost of manual or redundant processing, enhance security, and reduce cycle times for basic tasks.

3.7 SUB-TASK 7, RELATIONAL DATABASE MANAGEMENT SUPPORT (FFP)

The Contractor shall manage extract, transform, and load (ETL) processes for a SAP/Sybase IQ database and support programs and processes to load, update, and release data to IRS data analysts on a schedule that is determined by the Government.

Core requirements of this sub-task are defined as follows:

• Create and maintain SQL scripts, stored procedures, and other program logic to create, update, and delete data. Design and implement schema changes, manage indexes, and alter data objects to optimize performance.

• Design efficient data models from a logical design based on business requirements and available use patterns. Identify entity relationships, referential integrity constraints, and primary key structures. Perform analysis of tradeoffs

Attch 1 between alternative schemas.

• Create and maintain documentation that includes file specifications, schema, core record layouts, programs, business requirements, test plans, and other artifacts used in the administration, creation, and execution of database operations.

Knowledge of, or familiarity with, SAP Data Services and the ability to parse Extensible Markup Language (XML) files is desirable, but not a requirement. The Contractor shall work on a team that includes Government employees and other contractors to perform this work.

DESIRED OUTCOME – The contractor shall provide database support that includes ETL/T, account management, performance tuning, monitoring, and other activities detailed above.

3.8 SUB-TASK 8, DATA EXTRACTION, TRANSFORMATION & LOADING (ETL) AND

SUPPORT DOCUMENTATION FOR GRAPH DATABASE ENVIRONMENT (FFP)

The contractor shall:

1. Maintain and improve processes to ensure that all data in Compliance Data Warehouse Knowledge Graph (CKGE) environment is updated in sync with CDW data update schedule.

2. Lead assessment and documentation of graph data models and ensure their reliability to ontological references, which can require working with stakeholders and other teams and leveraging application of existing tools.

3. Automate CKGE ETL and other processes so that they can run with little or no human intervention.

4. Monitor data release management actions to manage issues as they arise and identify risks and mitigation responses that that could impact customers or stakeholders of data analytics.

5. Collaborate with other Compliance Data Warehouse Knowledge Graph Environment (CKGE) teams and database administrators for source datasets as required to test the accuracy and proper formatting of data.

6. Document ETL processes and scripts consistent with industry best practices and government guidelines.

The CKGE databases are populated with data drawn from multiple sources found within Data Management Division (DMD’s) Compliance Data Warehouse (CDW), a large analytical computing environment. Most source datasets are currently updated monthly, while approximately 10 percent are updated weekly. CKGE databases are updated at the same cadence of the source dataset updates. The source datasets may experience changes including additions of or modification to existing variables. These changes are most likely to occur at the beginning of the calendar year and will be communicated to the database administrators.

Attch 1

The CKGE databases reside in Graph database (GraphGrid) infrastructure and have existing extraction, transformation, and loading (ETL) processes employing SQL, Cypher, Python, and Bash. Enhancement and modification work to leverage Python, Java, Spark and GraphGrid for ETL processes in in progress.

Below are metrics from the current ETL process which may provide additional context regarding the project details:

• Number of source datasets (from CDW): 103

• Number of ETL scripts: 110

• Number of resulting data files loaded into CKGE: 99

DESIRED OUTCOME 3.8.1 – The contractor shall provide Data Updates:

• Data tested for accuracy, completeness, and adherence to ontological references.

• Data loaded to applicable systems for release to CKGE environment.

• Performance issues managed to resolution.

• Increase automation of ETL and other processes there by decreasing the need for manual execution and human monitoring and intervention.

• Mature and evolve existing processes to generate project or program efficiencies.

• Proactively communicate to resolve issues and mitigate risks during data release cycles.

• Risks and corresponding mitigation actions and escalation plans identified and documented.

DESIRED OUTCOME 3.8.2 – The contractor shall process documentation: ETL scripts and comments loaded into government code repository (including but not limited to GITLAB) server directories, and/or Microsoft SharePoint resources, with submission of official CDW Change Controls, including record counts, cycle dates, and other details as specified by DMD management.

3.6 SUB-TASK 9, PERFORMANCE ENHANCEMENTS FOR GRAPH DATABASE

ENVIRONMENT (FFP)

The contractor shall provide:

1. Continuously review and analyze the documentation and data feeds for accuracy and determine optimal structure for the CKGE environment.

Attch 1

2. Document findings and recommend changes to address data quality issues such as missing values, duplication, erroneous values, inconsistent formats, inconsistent data types, and other anomalies.

3. Work with stakeholders and other CKGE teams to identify and implement opportunities for enhancements to the data feeds.

4. Make approved changes and document approved changes in a format consistent with guidelines to be provided by the Government.

The CKGE must be able to adapt to additional customer requirements. All requests presented to RAAS management will be reviewed, and if accepted, the necessary changes will be discussed and coordinated with all CKGE support teams. These changes will likely include the addition of new data sources and the increase in update frequency of existing data. These additions are not anticipated to extend scope of work.

The ETL process lends itself to scalability and the team can leverage efficiencies resulting from improvements to the ETL process.

DESIRED OUTCOME – The contractor shall provide a Monthly Enhancement Report in Microsoft Word, which presents findings and provides recommendations for data structure and data quality improvement or correction. The report shall describe any modifications planned or made to process, issues with the data feeds, and any risks identified with corresponding mitigation actions and escalation plans.

3.10 SUB-TASK 10, Transition Out (OPTIONAL) (FFP)

At the end of this task order, 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 period shall not exceed 60 calendar days.

The Contractor shall:

• Minimize transition impact to the user community.

• Ensure no breaks in service availability.

• Maintain existing service quality and performance levels.

• Ensure a transparent and seamless transition.

• Maintain support and meet delivery milestones of ongoing projects.

• 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 be responsible for completing the following

Attch 1 deliverables:

Deliverable Purpose Transition-Out Plan The Contractor shall develop, document, and provide a

Transition-Out Plan no later than 180 calendar days after the date of award, or earlier if directed by the Contracting Officer, and shall be updated annually. The Contractor’s Transition- Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent 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.11 SKILL REQUIREMENTS

The contractor shall provide resources with the following experience, expertise, and skillsets to work on the following systems, hardware and software across sub-tasks described above:

Extensive experience and familiarity with IRS data file structures and formats, IRS business processes, RAAS systems architecture, RAAS network topology, and different analytical tools. IBM Mainframe z/OS, RedHat Linux, ETL/T processes, SAP/Sybase IQ relational database, Open Native Graph DB (ONgDB), R, RStudio, Python, RShiney, Anaconda, Jupyter Notebooks, TensorFlow, PyTorch, RAPIDS, DASH R, Python, Bash, DASH R, SAS, STATA, and Spark languages, Java, Spark and GraphGrid for ETL processes, services such as Docker containers, Kubernetes, reverse proxy servers, and centralize authentication via LDAP will be required to meet current service levels for analytical computing.

Specialized experience shall also include expertise in these areas: Storage area networks, graph databases, Docker containers, Kubernetes, reverse proxy servers, and centralize authentication via LDAP and open-source environment management and optimization. The Government will require contractor assistance to incrementally establish, test, and deploy these solutions to mature its heterogeneous environment.

This effort will also require support for the advancing new Linux solutions in the RAAS computing environment.

3.12 LABOR HOUR ESTIMATES FOR FIRM FIXED PRICE (FFP) SUB-TASKS

For FFP Sub-Tasks described in the PWS Section as indicated in the table below. The Government estimates that the range of labor hours will be expended under the base

Attch 1 period and each of the option periods.

Effort

Base Period

Option Period

Option Period

Option Period

Sub-Task 1 20 - 40 20 - 40 20 - 40 20 - 40 Sub-Task 2 475-575 475-575 475-575 475-575 Sub-Task 3 20 - 40 20 - 40 20 - 40 20 - 40 Sub-Task 4 1600-1700 1600-1700 1600-1700 1600-1700 Sub-Task 5 1900-2000 1900-2000 1900-2000 1900-2000 Sub-Task 6 1200-1300 1200-1300 1200-1300 1200-1300 Sub-Task 7 3000-3200 3000-3200 3000-3200 3000-3200 Sub-Task 8 3000-3200 3000-3200 3000-3200 3000-3200 Sub-Task 9 1475-1575 1475-1575 1475-1575 1475-1575 Sub-Task 10 1475-1575 1475-1575 1475-1575 1475-1575

Labor categories: Project Manager, Mainframe Programmer Assembly Language/Java Project Manager, Mainframe Programmer Java, Database Developer ETL and Graph System Administrator Linux, and Mainframe Programmer Assembly Language/Java

Note: This is based on historical information. Offerors shall propose their own solution including labor, to these sub-task requirements.

4.0 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. Section

3.0 of this PWS defines the Government’s Required Services and Desired Outcomes for each sub-task included in this Task Order.

4.1 PERFORMANCE REQUIREMENTS and STANDARDS

The performance requirements, standards, desired outcomes, and acceptable quality levels (AQL’s) for required services, tasks and deliverables are defined by the Government in the Quality Assurance Surveillance Plan (QASP). 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.

4.2 SURVEILLANCE

The surveillance process has two interrelated parts: The monitoring methods identified in the Quality Assurance Surveillance Plan (QASP) and the Contractor established Quality Control Plan (QCP) in accordance with Section 8 of the QASP. This links the

Attch 1

Government and Contractor’s quality assurance efforts into an integrated package with shared objectives.

5.0 GOVERNMENT-FURNISHED PROPERTY (GFP)

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

ITEMS QUANTITY

Contractor Identification Badge 7 Contractor Building Access/Proximity Card 0 Laptop Computer with Local Area Network Access 7 Office Space (Desk, Chair, Standard Office Equipment) 7 Microsoft: Word, Excel, PowerPoint, Project Access 7 Telephone With VMS 7

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

6.0 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

Required Security Briefings The Government shall furnish all the data to the Contractor for the performance of this SOW.

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

7.0 TRAVEL

No travel will be required for this effort.

8.0 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

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

77 K Street, NE, Third Floor; Washington, DC 20002

9.0 INSPECTION AND ACCEPTANCE

Attch 1

9.1 INSPECTION

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. Inspection will be at the same place as performance and delivery, unless otherwise specified.

9.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 contract and any resulting task orders awarded.

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

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

• Specifications Validity - All work products must satisfy the requirements of the

Government as specified herein.

• Format - work products shall be submitted in hard copy (where applicable) and in media defined in the PWS/SOW. The work product format may be different in each task 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 task order, or submitted in accordance with a later, scheduled date determined by the CO.

9.3 SPECIFIC DELIVERABLE ACCEPTANCE CRITERIA

Deliverable No. Specific Deliverable Criteria Sub-Task 1, Orientation Briefing 9.2 Standard acceptance criteria apply to this deliverable.

Sub-Task 2, Ramp-up Knowledge / Transfer In (Optional)

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 3, Period of Performance Summary Report

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 4, Mainframe Data Extracts 9.2 Standard acceptance criteria apply to this deliverable.

Sub-Task 5, Linux Administration 9.2 Standard acceptance criteria apply to this deliverable.

Attch 1

Sub-Task 6, Advanced Linux Environment Maturity

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 7, Relational Database Management Support

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 8, ETL and Support Documentation for Graph Database Environment

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 9, Performance Enhancement for Graph Database Environment

9.2 Standard acceptance criteria apply to this

deliverable.

Sub-Task 10, Transition Out (Optional) 9.2 Standard acceptance criteria apply to this deliverable.

9.4 REVIEW OF DELIVERABLES

The Government will perform an initial review of deliverables, and if problems are encountered during the review, the contractor must correct them. If necessary, a meeting may be convened to resolve any differences. The contractor shall make all required changes to achieve an acceptable deliverable. The Government will perform its review within 15 calendar days from receipt of the deliverable or as otherwise specified in each task order. 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 incorporate the comments properly and consistently in the final product.

10.0 ORDER PERIOD OF PERFORMANCE

The period of performance for any resultant order will include one 12-month base period and three 12-month option periods.

10.1 PLACE OF PERFORMANCE

100% Government’s site: 77 k Street, NE, third floor, Washington, DC 20002 0% Contractor’s site, with reasonable access to government site (contractor personnel can travel to government site for meetings within two hours’ notice and at reasonable travel costs.)

10.2 DELIVERABLES

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. If it is required that deliverable(s) be submitted in media storage form all devices must be scanned and certified as virus free. Unless otherwise specified 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.

Attch 1

10.3 RAMP-UP PERIOD

Work under this PWS may require a ramp-up period at the initial start of the period of performance for the Contractor to recruit and hire personnel specifically for this PWS. If needed, the ramp-up period specifics shall be identified in the Contractor’s proposal.

Note: Refer to “Ramp-up Knowledge/ Transfer In” Sub-Task.

11.0 TASK ORDER ADMINISTRATION DATA

11.1 IDENTIFICATION OF GOVERNMENT TASK ORDER PERSONNEL

The COR designation will be identified by the CO’s written designation memo.

12.0 KEY PERSONNEL

Contractor employees identified as Key Personnel shall be dedicated to this project. If any changes in proposed key personnel become necessary during actual performance, the contractor shall provide written notification 60 days in advance. In the event of a sudden change in key personnel (death, incapacitation, immediate termination, etc.), the contractor shall provide written notice to the CO within 3 calendar days of the event.

For any substitution, the contractor shall submit justification with a proposed substitute whose qualifications are equal to or greater than the person being replaced, along with a 1-to-2-page introductory summary, in sufficient detail to permit evaluation within 10 calendar days of notification of a substitution.

Key Position Labor Category Mainframe programmer – Assembly Language/Java

Applications Programmer

Mainframe programmer - Java

Applications System Analyst/Programmer - Intermediate

Database developer (ETL) Database Analyst/Programmer – Intermediate Database developer (ETL and graph database)

Database Analyst/Programmer – Senior

Database developer (Graph Database)

Database Analyst/Programmer - Intermediate

System Administrator - Linux Systems Administrator – Intermediate Project Manager Project Manager

The Contractor shall submit the resumes (certified by their respective manger) of the contractor employee(s) that will fill the position(s) identified in the table above.

13.0 PERFORMANCE REQUIRED BEYOND STANDARD WORKDAY

If needed, performance may be required beyond the standard workday. The standard workday is defined as any eight hours of productive labor during the core business

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

14.0 SECURITY

The Contractor Officer will ensure contractor personnel compliance with IRS HSPD-12 PIV Procedures Manual. This manual will be provided to the awardee.

14.1 PERFORMANCE AT GOVERNMENT SITES

If any of this effort is performed at specified government facilities, the contractor shall abide by Department of the Treasury Directive (TD) 71-10 regarding provisions for authorized entrance and exit at these facilities.

14.2 IDENTIFICATION/ BADGES

The applicable contractor employees shall not begin working under this PWS until all security forms have been properly completed and submitted. All contractor employees shall be required to wear identification badges when working in government facilities.

14.3 PERSONNEL REMOVAL AND REPLACEMENT

The applicable contractor employees are subject to investigation by the government.

Applicable contractor employees who undergo contractor clearances that reveal, but are not limited to, the following, may be unacceptable under this contract: conviction of a felony, a crime of violence or a serious misdemeanor, a record of arrests for continuing offenses, or failure to file or pay federal income tax. The government reserves the right to determine if a contractor employee assigned to a task shall continue with the task.

The contractor shall agree to remove the person assigned within 1 business day of official notification by the government and provide a replacement within 5 business days. New hires or substitutions of personnel are subject to the contractor clearance requirement.

15.0 DELIVERABLES/ WORK PRODUCTS

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

“The contractor shall adhere to Section 508 of the Rehabilitation Act of 1973, which requires access to the Federal Government electronic and information technology. The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. Federal agencies must ensure that this technology is accessible to employees and members of the public with disabilities.

http://www.section508.gov/.

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

Attachment(s):

1. Quality Assurance Surveillance Plan