SPARTA_PWS__v6.pdf.pdf

PR: FD2060-18-32291 PWS REVISION: 0 1

Distribution Statement: D

Performance Work Statement (PWS) for

System Performance and Real Time Analysis (SPARTA) Engineering Services

February 2018

RELEASED BY:

AFLCMC/WNY

235 Byron Street, Suite 19A Robins Air Force Base, Georgia 31098-1670

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and United States DoD Contractors only to protect technical, operational or information data, or information from automatic dissemination under the international exchange program or by other means; determination date: 12 July 2014. This protection covers publications required solely for official use or strictly for administrative or operational purposes.

Refer other requests for this document to AFLCMC/WNY RFCM EW Program Office, Air Force Life Cycle Management Center, Robins Air Force Base, Georgia 31098.

Destruction Notice - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

PR: FD2060-18-32291 PWS REVISION: 0 2

Table of Contents

1.0 Description of Services

1.1 Objective(s)

1.2 Benefit to United States Air Force (USAF)

1.3 Background

2.0 Description of Effort

2.1 Tasks

3.1 Contractor Responsibility

3.2 Government Furnished Information

3.3 Reporting of Government Information

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

3.4.2 Reporting Loss of Government Property

3.4.3 Return or Retention of Government Property

4.0 Period and Place of Performance

4.0.1 Contract/Order Period of Performance

4.0.2 Place of Performance

4.1 Contract Data Requirements List(s) (CDRL)

4.1.1 Quality of CDRL Deliverable

4.1.2 Receipt of CDRL Deliverable

5.0 General Information

5.0.1 Packaging

5.0.2 Travel

5.0.3 Continuation of Mission-Essential Services During a Crisis

5.1 Security Requirements

5.1.1 Security Regulations

5.1.2 Operations Security (OPSEC)

5.1.3 Communications Security (COMSEC)

5.1.4 Security Clearance

5.1.5 Security Incident or Violation

5.1.6 Access to Government System(s)

5.2.7 Access to Government Facility or Military Installation

5.2.8 Access to Robins Air Force Base (AFB)

PR: FD2060-18-32291 PWS REVISION: 0 3

5.3 Common Access Card (CAC)

5.4 Agency Affirmative Procurement Programs

5.5 Safety Requirements

5.5.1 Contractor Compliance

5.5.2 Mishap Notification/Investigation

5.5.3 Safety and Health Plan/Program

5.6 Inspection of Services

5.7 Invoicing/Payment and Receipt/Acceptance

5.8 Quality Management System (QMS)

5.9 Trafficking in Persons

5.10 Appendices

5.10.1 Appendix A, Reference(s)

PR: FD2060-18-32291 PWS REVISION: 0 4

1.0 Description of Services

1.1 Objective(s)

This Performance Work Statement (PWS) describes the services required to provide Developmental Test (DT) support and analysis for the Radio Frequency Countermeasures (RFCM) program.

1.2 Benefit to United States Air Force (USAF)

This acquisition will benefit the USAF by providing advanced real time electronic warfare countermeasures analyses for the AC/MC 130J United States Special Operations Command (USSOCOM) RFCM integrated product team.

1.3 Background

The Government is conducting market research to identify potential sources that possess the expertise, capabilities, and experience to provide electronic counter measures analysis of the RFCM system performance during DT using SPARTA software developed by Southwest Research Institute (SWRI). The RFCM System is a fully integrated single-system Electronic Warfare (EW) suite for the AFSOC AC/MC-130J aircraft. The system provides detection avoidance navigation/threat avoidance navigation and terminal defense for the aircraft. Specifically, the SPARTA software requirements include the following developmental testing support for the RFCM System: setting up a SPARTA software package for specific RFCM test scenarios, developing models/expected results/tolerances for RFCM testing, running SPARTA analysis software against data sets provided by the RFCM team, and generating electronic countermeasure reports/graphs. The RFCM government team requires SPARTA software to provide accurate fidelity of real time electronic countermeasure analyses.

2.0 Description of Effort

The government will provide In-Phase Quadrature (I/Q) data collection files that represent radar and ECM responses for RFCM test scenarios to be analyzed. Data will be provided via classified media. Every test scenario will either include (a) description/model of the expected ECM or (b) trusted collection that contains an ECM response that will be used to generate limits. These limits will then be used to compare test results for other data collections for this test scenario. The prime objective is for the contractor to highlight all of the areas where the ECM response went outside of the expected tolerances in order for the government to do further investigation or document problems with the SUT.

2.1 Tasks

2.1.1. The contractor shall import I/Q formatted binary files that contain radar and Electronic counter measures baseband I/Q sample data.

2.1.2. The contractor shall provide advanced electronic countermeasure (ECM) analysis for multiple false target (MFT) techniques.

2.1.3. The contractor shall separate and analyze false targets independently.

2.1.4. The contractor shall analyze up to 20 false targets in parallel.

2.1.5. The contractor shall perform required advanced analysis of each false target includes range, velocity, amplitude, amplitude modulation (modulation rate and duty cycle), pulse width, blanking, and percent jamming characteristics. The contractor shall ensure all frequency analyses have frequency accuracy better than 150 Hz.

PR: FD2060-18-32291 PWS REVISION: 0 5

2.1.6. The contractor shall analyze all pulses with PWS of 100 ns or more.

2.1.7. The contractor shall perform analysis on pulsed and CW signals.

2.1.8. The contractor shall model expected ECM results for each false target. Government will provide expected ECM characteristics and allowable tolerances for each false target.

2.1.9. The contractor shall generate interactive graphs that plot actual results (range, velocity, etc.)

versus allowable limits. Interactive graphs must have zoom and pan capabilities.

2.1.10. The contractor shall display data and limits for each false target on separate graph layers so that false targets can be turned off and on.

2.1.11. The contactor shall evaluate results versus limits and display all failing data points in red.

2.1.12. The contractor must be able to process I/Q data representing an instantaneous bandwidth (IBW) up to 125 MHz with collection times up to 30 seconds.

The contractor will provide a final engineering report containing all ECM analysis, models, results, graphs and data produced by the tasks above. Additionally the contractor will provide all digital analysis products, models, and software developed under this contract in a Software Test Report (CDRL A001 Software Test Report).

2.2 Services Summary

Performance Objective PWS

Reference Performance Threshold

Quality of CDRL deliverable

2.1 There shall be no more than one rejection of any

deliverable. The Government will reject a deliverable if 1 or more technical errors or 2 or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 3 business days of notification of Government rejection.

3.1 Contractor Responsibility

The Contractor shall be responsible for Government information in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Furnished Information

Government furnished information to be provided includes I/Q data collection files that represent radar and ECM responses for RFCM test scenarios to be analyzed. Data will be provided on classified CD/DVD.

3.3 Reporting of Government Information

The Contractor shall create and maintain records of all Government property accountable to the contract/order.

The Contractor shall record receipt and return of Government-Furnished Information (GFI) in the Item Unique Identification (IUID) Registry. Government property shall be listed as a GFP attachment and is created as a fillable document at http://dodprocurementtoolbox.com/.

http://dodprocurementtoolbox.com/

PR: FD2060-18-32291 PWS REVISION: 0 6

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property

“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing.

Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property

The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access To eTools and report to the RFCM IPT.

3.4.3 Return or Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Period and Place of Performance

4.0.1 Contract/Order Period of Performance

The period of performance for the contract/order is 27 March 2018 to 31 October 2018.

4.0.2 Place of Performance

These services will be performed at the contractor’s facility, 609 Russell Parkway Warner Robins, GA 31088-6031 or Robins AFB, GA.

4.1 Contract Data Requirements List(s) (CDRL)

Document Identifier

Data Acquisition Document No. Title PWS Reference(s)

A001 DI-IPSC-81440A Software Test Report 2.1

4.1.1 Quality of CDRL Deliverable

There shall be no more than one rejection of any deliverable. There shall be no more than 2 total rejection(s) of deliverables. The Government will reject a deliverable if 1 or more technical errors or 2 or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A

PR: FD2060-18-32291 PWS REVISION: 0 7

minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 3 business days of notification of Government rejection.

4.1.2 Receipt of CDRL Deliverable

CDRL deliverables may be submitted directly to the government member(s) identified on the CDRL. There shall be no more than 0 late submission(s) of deliverables during the period of performance. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

5.0 General Information

5.0.1 Packaging

The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

5.0.2 Travel

Travel requests for contractor/subcontractor personnel shall be submitted for approval to the Contracting Officer prior to costs being incurred and a minimum of 5 business days in advance of departure.

5.0.3 Continuation of Mission-Essential Services During a Crisis The government Integrated product team has determined these services are not mission-essential and will not continue in the event of a crisis.

5.1 Security Requirements

5.1.1 Security Regulations

The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: RFCM Security Classification Guide (SCG) & DD Form 254.

The contractor shall be responsible for obtaining employee security clearances to the access level required for proper accomplishment of contract requirements. The Contractor’s inability to obtain proper employee security clearances shall not constitute an excusable delay in contract performance. The contractor shall obtain and/or maintain clearance of their facility by Defense Security Services (DSS) to receive and generate classified information and hardware through the level(s) specified by DD Form 254. The contractor shall have or obtain a DoD Activity Address Code (DoDAAC) capable of receiving classified hardware and data.

5.1.2 Operations Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

PR: FD2060-18-32291 PWS REVISION: 0 8

5.1.3 Communications Security (COMSEC)

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22-M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.1.4 Security Clearance

The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the SECRET level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.

5.1.5 Security Incident or Violation

The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.

5.1.6 Access to Government System(s)

The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.7 Access to Government Facility or Military Installation

The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.8 Access to Robins Air Force Base (AFB)

The Contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The Contractor shall provide the PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.

5.3 Common Access Card (CAC)

5.3.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

PR: FD2060-18-32291 PWS REVISION: 0 9

5.3.2 The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy.

The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.4 Agency Affirmative Procurement Programs

This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Compliance

The Contractor shall comply with Government Safety and Health regulations including, Public Law 91-596 as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).

5.5.2 Mishap Notification/Investigation

The Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel;

and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. The Contractor shall ensure the Safety Office and the PCO are notified of mishaps. The Contractor shall contact the MFT (COR, if available, or another MFT member) by telephone within 24 business hours.

The Contractor shall cooperate with Government safety investigations.

5.5.3 Safety and Health Plan/Program

The Contractor shall submit a Safety and Health Plan to the MFT or as indicated by CDRL instructions. The Contractor shall establish and maintain a safety program in accordance with the contract/order, applicable Government regulations and the Safety and Health Plan.

5.6 Inspection of Services

In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Invoicing/Payment and Receipt/Acceptance

The Contractor shall submit/process payment requests and receipt/acceptance documents via iRAPT.

5.8 Quality Management System (QMS)

The Contractor shall ensure the quality of services through a quality and/or inspection system.

5.9 Trafficking in Persons

The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons.

PR: FD2060-18-32291 PWS REVISION: 0 10

Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip

5.10 Appendices

5.10.1 Appendix A, Reference(s)

Publication Title of Publication Date of Publication Sections(s) that Apply

DoD 5220.22-M

National Industrial Security Program Operating Manual

(NISPOM).

February 28, 2006 Change 1 - March 28, 2013

DoDD 4715.1E

Environment, Safety, and Occupational Health (ESOH) March 19, 2005

DoDD) 5205.02E

DoD Operations Security (OPSEC) Program June 20, 2012

DoD Manual 5205.02-M

DoD Operations Security (OPSEC) Program Manual November 3, 2008

Public Law 91- 596 as amended by Public Law 101-

Occupational Safety and Health Act of 1970 December 29, 1970 as amended through January 1, 2004

6.0 Contract Data Requirements List (CDRL)

A001 Software Test Report (PWS 2.1) http://www.state.gov/j/tip