2019_06_14_HDFS_Software_PWS.docx

PERFORMANCE WORK STATEMENT

Installation and Configuration of Highly Distributed File System Software (HDFS)

Department of Defense Education Activity 4800 Mark Center Drive Alexandria, VA 22350

PERFORMANCE WORK STATEMENT

FOR

Installation and Configuration of Highly Distributed File System Software

1. General Information and Scope of Work.

1.1 Agency: The Department of Defense Office of the Inspector General (DoD OIG) serves under the provisions of Public Law 95-452 as an independent and objective official responsible for conducting, supervising, monitoring and initiating audits, investigations and inspections relating to DoD programs and operations.

1.2 Background: The goal of the Data Analytics Program (DAP) is to increase the OIG’s ability to identify and focus oversight resources on high risk areas, i.e., health and safety concerns, fraud, waste, and abuse of DoD resources. This is accomplished through the use of computer-based analytical techniques that rely upon current software technology, availability of DoD source data, and subject matter experts (SME) to make recommendations that fix internal control problems, reduce or eliminate waste and inefficiencies, and arrest and refer those who engage in criminal activity for prosecution. Our immediate need is to support on-going projects and expand data analysis capabilities in order to accomplish a variety of data analytics functions with a scalable file system and analysis tool set.

1.3 Scope of work: The scope of this contract is constrained only as iterated below. Performance of tasks or work which is not specifically within the following constraints shall be considered outside of the scope of this contract. The Contractor shall:

1.4 Description of Services: The contractor shall provide all personnel, equipment, supplies and materials, transportation, tools, supervision, and other items and non-personal services necessary to provide integrated and optimized software for the existing OIG environment, as well as, services to ensure the software is properly supported throughout the period of performance and migrated to OIG assigned staff as discussed in this Performance Work Statement (PWS).

1.5 Period of Performance: A base year of 12 months after acceptance with two 12-month option periods.

2. Requirement (Objectives).

2.1 The objective of this PWS is to obtain contractor support to install and maintain COTS HDFS software at a Government facility (CONUS). The DODOIG requires an accessible Agency-wide analytics platform that provides an integrated environment for predictive and descriptive modeling, data mining, text analytics, forecasting, optimization, simulation, and experimental design.

The contractor shall provide the software, licensing, technical support, and maintenance for each instance of HDFS software and its components. The contractor shall be responsible for on-site service as required to support the successful completion of all tasks and objectives of the PWS and additional customer support that may be required for each instance of HDFS software and components licensed and installed.

2.1.1 Knowledge Transfer (Task 1)

2.1.1.1 The Contractor shall throughout the performance of installation, configuration, optimization, and validation of specified HDFS software transfer knowledge to ensure that OIG personnel receive the knowledge required to repeat all required tasks with minimal dependence on external support. This includes: basic training material such as manuals, walkthroughs, and web-based material (as long as the material can be accessed from our network). Deliverable: Technical Documentation

2.1.2 Project Management (Task 2)

2.1.2.1 The contractor shall maintain a Risk Register. The Risk Register will include all identified risks associated with the installation, configuration, optimization and validation of specified software. A risk is any issue identified by the contractor or the OIG which may delay or prevent the success of the installation, configuration, optimization and validation of specified software. All entries on the risk register will include at a minimum a definition of the risk, a priority rating (based on potential impact and timeline to mitigate or minimize the impact), the date the risk was identified, and the person who identified the risk. The OIG shall provide a format for the risk register shortly after contract award. Deliverable: Risk Register

2.1.2.2 The contractor shall coordinate with OIG to develop and maintain a Project Plan which outlines all tasks and milestones, including associated timelines and responsible personnel, (OIG staff and, or Contractor staff as applicable) which are required to successfully install, configure, optimize and validate specified software. Updates to the Project Plan which affect timelines for major milestones will be briefed to the COR as soon as the need for revision is identified. Deliverable: Project Plan

2.1.2.3 The Contractor shall conduct Regular Status briefings to address: work performed, upcoming work, any issues, unresolved risks and any other information which is current and relevant to the performance of the work outlined in this performance work statement. The schedule of delivery of these briefings may be adjusted as the COR deems is necessary; under normal circumstances OIG anticipates that in person bi-weekly progress meetings, weekly touch point telephone conversations, and monthly in person executive briefings will be sufficient. Exceptions shall be made requiring additional briefings as necessary in the event of critical issues which may affect the project schedule. Deliverable: Regular Status Briefings

2.1.2.4 The Contractor shall provide for all project status briefings and meetings: agendas, minutes, action items and sequence plans as applicable. Deliverable: Agenda minutes and action items

2.1.3 Pre-Installation Walkthrough and Planning (Task 3)

2.1.3.1 The Contractor shall conduct and document meetings with the OIG as required in order to discuss key terms, risks and assumptions in preparation of the Contractor’s performance of services to: install, configure, test, optimize, and validate (through the performance of specified user tests), all specified HDFS software or third party software and services within the OIG’s computing environments. The Contractor shall be responsible for assessing the OIG computing environments in order to identify and prepare resolutions for, any issues or obstacles within the OIG computing environments that may impair the ability to successfully install, configure, optimize and validate of all specified HDFS software. The contractor shall evaluate the OIG’s current and projected utilization of the HDFS software as this will ensure the contractor provides accurate resource recommendations. Deliverable: Documented meeting notes

2.1.3.2 The Contractor shall, utilizing the information gathered during planning meetings, create a comprehensive Engineering Plan. The Engineering Plan will include technical descriptions of required resources, services which the HDFS software systems are dependent on, network communication ports, and include any other information which ISD Engineering may require. The Engineering Plan shall ensure that the system will utilize CAC authentication for users wherever user authentication is required. User authentication shall be required in order to access any data set in any manner. That is, users must authenticate before interacting with data in order to ensure that the appropriate level of access is possessed by a user for any data. The engineering plan shall be constructed to ensure that system users will be able to perform any advertised capability of the specified software. The Engineering plan includes a System Architecture Design. This document shall be approved by ISD personnel through the COR prior to implementing any changes any Information Systems. Any necessary modifications to the Engineering Plan shall also be approved by appropriate ISD Personnel. The contractor shall be provided by the OIG, an example of this document upon contract award. Deliverable: Engineering Plan

2.1.3.3 The Contractor shall consult with OIG as necessary, to develop a System Architecture Design. The System Architecture Design will ensure that the specified software, software subcomponents and hardware are appropriately configured to support the OIG’s current and desired analytic capabilities. The System Architecture will include the arrangement and relationships between all system components, for example servers, clients and other dependent and supporting information systems. Deliverable: System Architecture Design

2.1.3.4 The Contractor shall develop a detailed Installation and Configuration Procedure which will outline all required steps to install and configure all specified HDFS software. The Procedure will include screen capture images and instructions for each step required to install and configure all of the specified HDFS software. Deliverable: Installation and Configuration Procedure

2.1.3.4.1 If, during the course of the installation and configuration, it becomes necessary to deviate from this procedure, the procedure will be modified to reflect those necessary modifications.

2.1.3.5 The Contractor shall assist the OIG as necessary to ensure that the required computing resources are available and properly configured in order to ensure the successful installation, configuration, optimization and validation of the specified software. For resources which are specifically under the control of the OIG, the contractor will work with OIG to schedule the performance of necessary tasks. Deliverable: Computing Environment is prepared for installation.

2.1.4 Software, Installation and Configuration (Task 4)

2.1.4.1 The Contractor shall work with OIG personnel to install and appropriately configure all of the specified software (See Appendix B) into the OIG’s computing environments. The specified software will be installed in the NIPR environment during the base year of the contract. The specified software will also be installed in the SIPR environment during option year 1 of the contract. The contractor shall ensure that the installation and configuration is performed in accordance with the Installation and Configuration Procedure and the Engineering Plan.

Deliverable: Specified Software and Licenses Deliverable: A fully installed and configured COTS HDFS software as designed in the Engineering Plan.

Deliverable: Record of Installation tasks

2.1.4.2 The Contractor shall ensure the correct performance of all tasks necessary to install and configure the specified software in order to enable a user of any of the specified software to perform all advertised capabilities of that software. Demonstration of encryption of all software communication.

2.1.4.3 The Contractor shall transfer to OIG personnel all knowledge which is required to repeat all necessary installation and configuration steps. Deliverable: Technical Documentation as required for Knowledge Transfer

2.1.4.4 The Contractor shall update the Engineering Plan and Installation and Configuration Procedure as necessary. Changes to these documents shall be reviewed and approved by appropriate OCIO personnel.

Deliverable: Updated Installation and Configuration Procedure Deliverable: Updated Engineering Plan

2.1.4.5 The Contractor shall conduct a pre-installation briefing. This briefing shall include a walkthrough of the Installation and Configuration Procedure with all personnel present who are required for the successful completion of the Installation and Configuration Procedure.

2.1.4.6 Current OIG and DOD policies require the use of CAC (Common Access Card) authentication for all users accessing Information Systems. The Contractor shall ensure that all information systems and software is configured as necessary to ensure compliance with these policies. The Contractor shall ensure that the knowledge which is required to perform this configuration is transferred to appropriate OIG personnel. The Contractor shall ensure that the Installation and Configuration Procedure and the Engineering Plan document this configuration.

2.1.5 Testing (Task 5)

2.1.5.1 The installation of the HDFS Software shall be verified through functional testing which shall demonstrate that the software is capable of performing all advertised capability.

2.1.5.1.1 Any installation or configuration errors identified during the execution of a testing plan will be remediated. Demonstration of encryption of all HDFS Software communications:

2.1.5.1.2 Leverages Secure Sockets Layer (SSL) to facilitate secure HTTPS communication between all web clients and the HDFS Cluster.

2.1.5.1.3 A layer of encryption when data is in transit between HDFS Nodes.

2.1.5.1.4 A layer of encryption when data is in transit between the HDFS software Cluster and thick clients.

2.1.5.1.5 Demonstration of Single Sign On (SSO) using Common Access Cards (CAC)

2.1.5.1.6 Secure login using CAC credentials to HDFS web clients; prevention of non-privileged user accounts from logging into web clients.

2.1.5.1.7 Secure login using CAC credentials to HDFS thick clients

2.1.5.1.8 Secure login for Administrative Accounts to the HDFS software; prevention of non-privileged user accounts from logging into HDFS software and Administration functions.

2.1.5.2 The Contractor shall develop a Testing Plan. The Testing Plan is a list of steps to be performed which will confirm that all specified software has been installed and configured as required in order to enable a user of the specified software in the OIG computing environment to perform all of the advertised capabilities of the specified software. The COR shall approve the Installation Testing Plan prior to the performance of Installation Testing. It is not necessary that the Installation Testing Plan test all advertised capabilities, only that the tests, when successfully performed are sufficient to ensure that the advertised capabilities of the specified software can be performed. Deliverable: Testing Plan

2.1.5.3 The Contractor shall assist OIG personnel in completing all steps of the Installation Testing Plan under the supervision of the designated Subject Matter Expert and the COR. Deliverable: Performance of test plan

2.1.5.4 The results of the Testing shall be recorded by the contractor. Deliverable: Record of Test Results

2.1.5.5 In the event that any of the tests fail, the Contractor shall develop a Technical Remediation Plan which includes a technical explanation of why the test failed and the steps necessary to correct the installation and configuration in order to facilitate a successful test. The Contractor shall update, as applicable any parts of the Installation and Configuration Plan and the Engineering Plan. Deliverable: Technical Remediation Plan (if necessary)

2.1.5.6 The Contractor shall record all remedial actions which are necessary to facilitate successful performance of the Testing Plan. Deliverable: Record of Remedial Action (if necessary)

2.1.5.7 The Contractor shall perform a limited scope project in order to accomplish the objectives defined in this section. These objectives are intended to test the functionality and security which are provided to the OIG by the newly implemented HDFS software. Accomplishing these objectives are critical to successful adoption of the software by OIG.

2.1.6 Maintenance (Task 7)

2.1.6.1 The contractor shall provide standard maintenance during the PoP of the contract for all of the specified software including at a minimum: providing unlimited technical support for system users, data managers, and system administrators; providing updates to any specified software or required software subcomponent.

Performance Standards and Acceptable Quality Levels (Objective 1) The following applies to Objective 1:

2.1 Performance Standard (PS1) - Tasks will be completed by the required completion date Acceptable Quality Level (AQL 1) - 95 % of tasks will be completed by the required completion date. The remaining 5% shall be completed no later than 10 days after their due date.

3. Constraints.

3.1 Security requirements

3.1.1 Security Clearance requirement

3.1.1.1 This contract is UNCLASSIFIED and is designated as non-critical sensitive. The Contractor shall provide proof that personnel who will be performing work on site under this contract possess, at a minimum, an SECRET CLEARANCE at the time of award of the contract and shall maintain this minimum level of security for the duration of the contract. It is the contractor’s responsibility to ensure that all security requirements are followed in accordance with DoD 5200.2-R, Personnel Security Program.

3.1.1.2 Access to sensitive unclassified information is required in performance of this PWS. The performance of tasks identified in this PWS may require the contractor to have visibility of Personally Identifiable Information (PII), Privacy Act information, and other types of Unclassified Sensitive Information. The contractor shall implement security requirements as defined below and approved by the OIG.

3.1.1.3 The contractor shall ensure that all contractor personnel working on this project who will have visibility of Personally Identifiable Information (PII), Privacy Act information, and other types of Unclassified Sensitive Information, comply with the DoD Privacy Program and the Non-Disclosure Agreement. The DoD Privacy Program (32 CFR 310, Part 310/DoDD 5400.11) provision restricts contractor employees from disclosing PII from a system of records they operate on behalf of a DoD component, outside of DoD. All contractor personnel assigned tasks which require access to Personally Identifiable Information (PII), Privacy Act information, and other types of Unclassified Sensitive Information must complete and submit a Non-Disclosure Agreement to the COR prior to acquiring accessing such data. A copy of the applicable Non-Disclosure Agreements will be provided to the Contractor by the COR as needed. During the performance of the work of this PWS, various datasets to be worked with will be identified by the Government. The particular NDA, which would be required for a given dataset, will vary depending on which data is selected by the government.

3.1.1.4 The Contractor is responsible for ensuring that all persons working on the program are U. S. citizens. Therefore, Contractor personnel who currently hold dual citizenships and/or active foreign passports must report possession of a foreign passport to their Company security office and Facility Security Officer (FSO). Contractor personnel must report any use of a foreign passport to enter or exit the United States to the FSO. The FSO shall follow guidelines as set forth within the SECURITY EXECUTIVE AGENT DIRECTIVE 4 (SEAD 4). There is no guarantee that the individual will be permitted to perform on this program.

3.1.1.5 The Government reserves the right to have any contractor employee removed, whenever there is probable cause to believe, on the basis of all facts available, that such action is warranted in the interest of national security. This action shall be made whether or not the cause is deemed of sufficient severity to warrant action to terminate the contractor's Facility Clearance or individual security clearance. The Government also reserves the right to remove any contractor on the basis of alleged misconduct which may, in the opinion of the Contracting Officer, jeopardize the security of the project.

3.1.2 Building access

3.1.2.1 The place of performance is a controlled facility and requires all visitors to request access. All contractor personnel background investigations will be verified by OSEC prior to performance. For personnel needing sustained access to the facilities or access to OIG Information Systems (IS) in order to perform on the contract, the contractor shall submit a visit authorization letter (VAL) via the Joint Personnel Adjudication System (JPAS) to the Industrial Security Program Manager (ISPM) in the Office of Security (OSEC). The VAL shall be submitted a minimum of fourteen (14) days prior to the anticipated date on which facilities or IS access is required.

3.1.2.2 A CAC will be required for access to the facilities and Access to OIG Information Systems. All CACs issued to contractor personnel are government property and must be returned either upon departure from the program or at the conclusion of the contract (whichever comes first) to the Industrial Security Program Manager.

Industrial Security Program Manager:

Shari M. Spriggs Industrial Security Program Manager DoD, Office of Inspector General Office of Security 4800 Mark Center Drive, Room 9B24 Alexandria, VA 22350-1500 Direct: 703-604-2031 Mobile: 703-929-3805 Fax: 571-372-7434 Email: shari.spriggs@dodig.mil

a) Field Site Visits: The contractor is required to coordinate visits to DOD sites (other than OIG Facilities) in accordance with OIG policy. The Contractor shall prepare and submit site visit letters, to each site no less than ten (10) calendar days prior to the requested travel date.

b) Network Access: Before access to the DoD OIG network is granted to contractor personnel, the following information shall be provided to the COR:

User Agreement: A signed copy of the DoD OIG User Agreement and provide the agreements to the COR no later than 20 days after being approved to work on the contract;

i. Annual Information Assurance Training: A certificate of completion for Annual Information Assurance Training and provide the certificates of completion to the COR no later than December 31 of each year or 20 days after being approved to work on the contract. The web link to the Information Assurance training is http://iase.disa.mil/eta/iaav10/index.htm;

ii. Personally Identifiable Information (PII) Training: A certificate of completion for Personally Identifiable Information (PII) Training and provide the certificates of completion to the COR no later than 20 days after being approved to work on the contract. The web link to the PII training is http://iase.disa.mil/eta/pii/pii_module/pii_module/index.html. The contractor is required to safeguard PII in accordance with the Privacy Act of 1974, 5 U.S.C. § 552a, and DoD privacy policy in effect during the period of performance. The DoD OIG must be informed within 24 hours if DoD PII data is compromised, lost, or stolen. Depending on the nature of information compromised, lost, or stolen, the Government has the right to invoke appropriate disciplinary action which may include civil and criminal penalties as outlined in DoD Regulation 5400.11-R, May 14, 2007.

iii. Anti-terrorism Training. All contractors are required to complete the Anti-terrorism Training and provide the certificates of completion to the COR no less than 20 days after being approved to work on this requirement. The purpose of this training is to increase awareness of terrorism and to improve the contractor’s ability to apply personal protective measures. The web link to the Anti-terrorism training is: https://atlevel1.dtic.mil/at/.

iv. Other Training: The Contractor may be required to work with data that the OIG requires demonstration of a general level of understanding prior to accessing, such as Personally Identifiable Information (PII), Health Insurance Portability and Accountability Act (HIPAA) information, or Law Enforcement Sensitive information. For those Contractors that will be accessing this type of information, they shall complete OIG specified training, or provide proof that they have attended similar training within 1-year, prior to accessing that information.

v. Accessing and Safeguarding Data: It is DoD policy to provide adequate security for all unclassified DoD information on non-DoD information systems in accordance with Directive-Type Memorandum (DTM) 08-027. Unclassified DoD information may NOT be disseminated by the contractor. Some OIG data which the contracted personnel may encounter is Law Enforcement Sensitive or otherwise have specific requirements for access. The Contractor will be informed of those requirements if the OIG determines that the contractor will have to meet additional requirements not listed here. An example of this might be a Non-Disclosure Agreement.

1. Key control: N/A

2. Lock Combinations: N/A

vi. Special Qualifications:

Anti-terrorism Training. All contractor employees are required to complete the Anti-terrorism Training and provide the certificates of completion to the COR no less than 20 days after being approved to work on the contract. The purpose of this training is to increase awareness of terrorism and to improve the contractor’s ability to apply personal protective measures. The web link to the Anti-terrorism training is: https://atlevel1.dtic.mil/at/.

3.2 Hours of Operation: The Contractor is responsible for providing services, between the hours of 0700 and 1800 Monday through Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. OIG shall provide for the Contractor a means of determining whether or not the facilities are open.

Recognized Holidays: The contractor is not required to perform services on these days.

3.3 Place of Performance: The work to be performed under this contract will be primarily performed at 4800 Mark Center Drive, Alexandria, VA 22311 and Montgomery, AL. All work shall be performed within the DoD OIG facilities with no exceptions.

3.3.1 Facilities: The Government will provide the necessary workspace for contractor staff, based on availability, to provide the support outlined in this PWS to include desk space, telephones, computers and other items necessary to maintain an office environment.

3.3.2 Utilities: All utilities in the Government facilities will be available for the contractor’s use during performance of the duties outlined in this PWS. The contractor shall instruct employees to use conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

3.4 Key Personnel: The key personnel specified in this contract are considered to be essential to work performance. At least 30 days prior to diverting any of the specified individuals to other programs or contracts (or as soon as possible, if an individual must be replaced, for example, as a result of leaving the employ of the Contractor), the Contractor shall notify the Contracting Officer and shall submit comprehensive justification for the diversion or replacement request (including proposed substitutions for key personnel) to permit evaluation by the Government of the impact on performance under this contract. The Contractor shall not divert or otherwise replace any key personnel without the written consent of the Contracting Officer. The Government may modify the contract to add or delete key personnel at the request of the contractor or Government.

The Contractor shall provide a Contract Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 0700 and 1800, Monday thru Friday except Federal holidays or when the Government facility is closed for administrative reasons.

All contract personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

3.5 Travel: It is anticipated that the Contractor may be required to travel within the CONUS during the performance of this contract. Travel is a reimbursable expense and travel arrangements and costs shall be in accordance with the Joint Travel Regulations (JTR) and limitation of funds specified in this contract. All travel in performance under this contract shall be approved in advance and in writing by the appointed DoD OIG Contracting Officer Representative (COR). Under urgent circumstances, advance telephonic/verbal approval by the DoD OIG COR will be acceptable, with the understanding that the written approval request shall be provided within thirty (30) calendar days of verbal approval.

3.6 Other Direct Cost

No other direct costs permitted on this contract.

4. Government-Furnished Resources.

4.1.1 Personnel: The Contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

4.1.2 Facilities: The Government will furnish the necessary workspace for the contractor personnel to provide services outlined in this PWS as required.

4.1.3 Utilities: All utilities in the facility will be available for the contractor’s use in performance of duties outlined in this PWS. The Contractor shall instruct contractor personnel in utilities conservation practices. The Contractor shall be responsible for operating under conditions that preclude the waste of utilities.

4.1.4 Equipment: The Government will provide appropriate access to IT resources such as servers and workstations, and typical office equipment such as printers, copiers, etc. as required by the Government in order to ensure the timely and efficient completion of the Contractors work.

· NIPR: 16 Physical Servers (Small Form Factor Nodes, approximately 64GB RAM, 3.6TB Hard Drive Disk Space, 16 Cores with 32 Processors, 2 sockets per node);

· SIPR: 16 Physical Servers (Small Form Factor Nodes, approximately 64GB RAM, 3.6TB Hard Drive Disk Space, 16 Cores with 32 Processors, 2 sockets per node);

· Red Hat Enterprise Linux (RHEL) Operating System software (version 7.2 or higher) across the entire cluster.

· Connection to DoD OIG NIPR Network through remote access including named administrative accounts for contracted personnel OR assigned DoD OIG system administrator to facilitate the installation/configuration.

· An assigned DoD OIG system administrator to facilitate requests for all required Public Key Infrastructure (PKI) and Certificate Authorities.

4.1.5 Materials: The Government will provide standard operating procedures and policies, network topology diagrams, and standard forms.

In performance of this contract, the Contractor shall furnish all supplies, equipment, facilities and services required that were not already provided by the Government to perform work under this contract and are not listed under Section 3 of this PWS.

5. Contract Administration.

General:

Invoice Instructions: In accordance with DFARS 252.232-7003, Electronic Submission of Payment Request, please submit all invoices using the Wide Area Work Flow (WAWF) online database system. To become a registered user, go to https://wawf.eb.mil. Additionally, training for WAWF, may be obtained by visiting http://wawftraining.com/.

Contracting Officer Representative (COR):

The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

Contracting Officer Representative:

TBD

6. Contract Deliverables.

Technical Exhibit 1 – Summary Schedule of Deliverables:

This table contains a summary of deliverables contained within this PWS. Full definitions of deliverables are contained in the information above.

Section 2.1.1

Section 2.1.2

Section 2.1.3

Section 2.1.4

Section 2.1.5

Section 2.1.6

7. Performance Requirement Summary (PRS).

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Technical Exhibit 2 - Performance Requirements Summary

Objective

7.1 Quality Control Plan

Quality Control Plan: The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to ensure that services are performed in accordance with the PWS. The Contractor’s QCP is the means by which the Contractor assures that the work complies with the requirement of the contract. The QCP is to be delivered within 30 days after contract award. The quality control program shall be delivered to the Contracting Officer Representative (COR) within 30 calendar days of the DOA. The COR shall review and approve the quality control program within 15 calendar days after submission by the contractor, or provide comments showing additional information required. The contractor shall then address all COR comments and provide additional requested information to the COR within 15 calendar days from receipt. The review and correction timeframe for the deliverable shall not exceed 30 calendar days from the date of the initial receipt by the COR. After acceptance of the quality control plan, the contractor shall receive the COR’s acceptance in writing of any proposed change to his quality control system.

7.2 Quality Assurance Surveillance Plan (QASP)

The Government will utilize a QASP to monitor the contractor’s performance on the contract. The QASP is a living document and can change at any time during the life of the contract. As such, the Government reserves the right to unilaterally edit the QASP at the Government’s discretion.

Appendix A: Acronyms and Definitions. Alphabetical list of definitions of key words used or acronyms.

Definitions:

ADVERTISED CAPABILITY. The term “advertised capability” is defined as any feature or function which HDFS SOFTWARE claims that the specified software is capable of performing. These claims may be written in HDFS SOFTWARE advertisements. These claims are specific and unique to particular versions of the specified software. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

CONTRACTING OFFICER (KO). A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured/physical things such as meeting minutes or reports.

IDEAL PERFORMANCE LEVELS. The response time of a software system as defined by benchmark testing for a given amount of resources under optimal circumstances.

KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards. (Or those actions taken by the government to assure services meet the requirements of the Performance Work Statement.)

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

QUALITY CONTROL PROGRAM. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

SERVICE INTERRUPTION. A service interruption is any event which prevents or impairs a user’s or administrator’s ability to interact with the system.

SPECIFIED SOFTWARE. See the list of specified software in Section: 7.2. This phrase also refers to any required software subcomponents.

SUBCONTRACTOR. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

SYSTEM. The collection of licensed Software applications (server or client) and hardware (physical or virtual).WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

WORK WEEK. Monday through Friday, unless specified otherwise.

Acronyms:

Appendix B: Salient Characteristics

· Commercial Off-The-Shelf Software (COTS) that can simultaneously distribute data, queries, statistical, and other advanced procedures across multiple servers (nodes) for processing. This is commonly known as a Highly Distributed File System or HDFS.

· Out-of-the-box configuration for Single Sign On (SSO) using two-factor authentication using smart cards (known within DoD as the Common Access Card or CAC).

· Include Apache Spark and/or a Data Science toolset (or similar) that can deploy advanced statistical and Natural Language Processing (NLP) across the file system.

· HDFS solution must operate with a high degree of fault tolerance and incrementally scale processing capability with additional nodes to add to the overall capacity of the entire system.

· Physical HDFS deployment onsite at OIG Headquarters (Mark Center, Alexandria, VA) and within a DISA-hosted Data Center to align with our IT department’s strategic plan.

Our Planned Environment:

· NIPR: 16 Physical Servers (Small Form Factor Nodes, approximately 64GB RAM, 3.6TB Hard Drive Disk Space, 16 Cores with 32 Processors, 2 sockets per node);

· SIPR: 16 Physical Servers (Small Form Factor Nodes, approximately 64GB RAM, 3.6TB Hard Drive Disk Space, 16 Cores with 32 Processors, 2 sockets per node);

· Red Hat Enterprise Linux (RHEL) Operating System software (version 5.5 or higher) across the entire cluster.

· Contractor shall provide the following software subscriptions (1 Year) for each NIPR (in the base year) and SIPR Install (in option year 1):

· HDFS software subscriptions for 16 nodes (12 Production + 4 Development)

· RStudio Pro (includes Python). Server, unlimited users.

· HDFS Tools such as SPARK, Workbench, etc. for at least 10 users.

· Contractor shall provide the following services for NIPR environment only:

· Installation & configuration of all software including single sign-on using DOD Common Access Card at headquarters (Alexandria, VA) and remote facility (Montgomery Alabama).

· Documentation of installation and configuration.

· Documentation of project migration functioning using new tools.

· Contractor shall provide the following services for SIPR environment only:

· Installation & configuration of all software including single sign-on using DOD Common Access Card at headquarters (Alexandria, VA) and remote facility (Montgomery Alabama).

· Documentation of installation and configuration.

· Documentation of project migration functioning using new tools.