FA8650-17-S-1050-SOO.pdf

Attachment 1 23 FEB 2017

FA8650-17-S-1050

Statement of Objectives (SOO) Passive Radar Illumination Selection Manager (PRISM)

1.0 Background

The US warfighter requires all-weather situational awareness of both air and ground targets.

This is traditionally provided by radar. As the operational environment becomes more hostile, however, the radar transmitter can become a beacon, giving away the presence and location of the platform. Passive radar becomes an attractive option for providing situational awareness without own-ship transmission.

2.0 Objective

The 63-month PRISM effort has three objectives. The first objective is to design an ISM algorithm which will connect to a government-supplied front-end ES subsystem and control a government-supplied back-end radar collection subsystem. The algorithm shall be implemented such that it operates in real time, taking in the emitter reports from the front end as well as user goals and commanding the back end such that available illuminators are exploited to meet user needs.

The second objective is to develop a technology improvement plan to extend ISM capability.

The development which is the first PRISM objective will culminate in a ground-based demonstration. Thus emitter dynamics will be primarily driven by those emitters provided by the test range which can be turned on and off and have their waveform characteristics varied by the testing staff. The technology improvement plan will provide technical analysis supporting a description of a development path leading to an ISM suitable for current and future operational platforms. Insights obtained on requirements of the front-end and back-end subsystems shall also be documented as part of the planning exercise.

The third objective is to begin addressing modifications and enhancements to the ISM developed as part of the first objective to address operation on current and future operational platforms, as identified in the second objective. The Government anticipates that within the technical response to this announcement the offeror will be able to anticipate additional work required toward an operational system, and to propose such work as part of the initial award within the funding constraints of Section 8. A deeper understanding of required capabilities is expected to be identified in the course of satisfying the first two objectives. Based on availability of additional funding, contract enhancements are possible.

3.0 Scope

The PRISM effort will research, design, and document an ISM subsystem, integrate that subsystem into a ground-based end-to-end PMM system, demonstrate the real-time functionality of the ISM, develop a technical improvement plan leading to an ISM suitable to current and future platforms, and enhance the initial ISM in preparation for testing with current and future platforms.

The PRISM performer(s) shall participate in system design discussions with the Government about the design of the front end and back end pieces of the PMM system, and will have input into the Interface Control Documents (ICDs) describing the interface of these subsystems with the ISM subsystem.

4.0 Specific Objectives

As a continuation of the objectives listed under paragraph 2.0, Objective, the focus of PRISM is to develop and demonstrate an ISM operating in real time within an integrated, ground-based PMM system, to develop a technology improvement plan showing further developments required to make the ISM suitable for current and future platforms, and to implement those enhancements in preparation for integration and testing with current and future platforms. The bulk of the technical emphasis should be on the development, implementation, test, and demonstration of the

ISM.

Participation in various technical reviews throughout the ISM program to examine the design and key processing functions, and participation in ISM Requirement and Functional reviews is required. Participation in preliminary, subsystem, and critical design reviews to assess the maturation of key processing and implementation components within the ISM is expected. The ISM will be integrated into a Government-hosted end-to-end PMM system.

4.1 Objective 1 – ISM Development

The first objective is to design an ISM algorithm which will connect to a government-supplied front-end ES subsystem and control a government-supplied back-end radar collection subsystem.

The algorithm shall be implemented such that it operates in real time, taking in the emitter reports from the front end as well as user goals and commanding the back end such that available illuminators are exploited to meet user needs.

While the ISM developed under the PRISM effort will be demonstrated as part of a stationary ground receive system, the ultimate application will be systems in the current or future Defense inventory. To the largest extent possible, the ISM will be designed in a manner consistent with airborne operation.

Output Objective: An Illuminator Selection Manager (ISM) algorithm, with real-time implementation, performing the ISM function as part of a ground-based, Government-owned complete PMM system

4.2 Objective 2 – Path to Airborne System

In addition to developing, implementing, testing, and demonstrating an ISM in an end-to-end ground-based PMM system, PRISM performers will provide a technology improvement plan for the additional development required to achieve an airborne system. The plan shall be backed up with analysis motivating the improvement plan. Requirements for the front-end ES subsystem and back-end surveillance subsystem will be included as part of the technology improvement plan and associated documentation.

Output Objective: Documented development path showing additional requirements to achieve an airborne ISM system and requirements for the other PMM subsystems, motivated by technical analysis.

4.3 Objective 3 – Development toward an Operational System

The Government anticipates the initial award(s) to include some funding to begin modifying the ISM for insertion into current and/or future platforms. This work shall involve development in areas identified in Objective 2, and shall increase the capability of the ISM as required to meet operational needs.

Section 4.1 stated that the ISM shall be designed to the greatest extent possible to be suitable not just for a ground-based demonstration but also for insertion into a current or future operational platform. Objective 3 provides an opportunity for the offeror to identify ways their proposed approach may fall short of being ready for transition. The Government anticipates that within the technical response to this announcement the offeror will be able to anticipate additional work required toward an operational system, and to propose such work as part of the initial award within the funding constraints of Section 8.

A deeper understanding of required capabilities are expected to be identified in the course of satisfying the first two objectives. Based on availability of additional funding, contract enhancements are possible.

Output Objective: Modified ISM algorithm as required to bring the Objective 1 demonstration ISM closer to meeting specific operational needs as outlined in the Objective 2 improvement plan.

4.4 Program Timeline

As discussed below in Section 6.0, initial work should accomplish Objectives 1 and 2 in 36 months. Objective 3 can cover an additional 24 months, for a total technical effort of 60 months.

As discussed below in Section 8.0, initial funding is anticipated to be $5M for Objectives 1 and 2, and $2M for Objective 3. Two awards are anticipated, nominally for $3.5M each. Based on availability of additional funding, contract enhancements are possible.

5.0 Contract Objectives/Data Deliverables

Deliver:

CDRL Deliverable Name A001 Scientific and Technical Reports, Final Report DI-MISC-80711A/T A002 Funds and Man-Hour Expenditure Report (FMER) (Monthly) FI-FNCL-80331A/T A003 Contracts Funds Status Report (Quarterly) DI-MGMT-81468/T A004 Status Report (Monthly) DI-MGMT-80368A/T A005 Presentation Material (As Required) DI-ADMN-81373/T A006 Computer Software Product DI-IPSC-81488/T A007 System/Subsystem Design Description (SSDD) DI-IPSC-81432A/T

Deliverables, such as any software (to include source code and executables) and hardware to be developed during performance, are specified in the SOO, Technical Objectives, and Paragraph 4.

The Government desires delivery with Unlimited Rights.

6.0 Period of Performance

The technical period of performance for this effort is 60 months. Objectives 1 and 2 (ISM development and test, and technology improvement plan) should be accomplished in 36 months.

An additional 24 months is allocated for Objective 3. Three months are allocated for preparation and review of the final report, resulting in an overall period of performance of 63 months.

7.0 Management

Allow the selected contractors flexibility to manage cost, schedule, and performance of this contracted effort.

8.0 Funding Constraint

FY17 FY18 FY19 FY20 FY21 TOTAL

AFRL $2,900,000 $ 925,000 $1,175,000 $1,315,000 $ 685,000 $ 7,000,000

External $ 900,000 $ 900,000 $1,200,000 $6,685,000 $7,930,000 $17,615,000

TOTAL $3,800,000 $1,825,000 $2,375,000 $8,000,000 $8,615,000 $24,615,000

The Government anticipates awarding two contracts, nominally each with a value of $3.5M.

Each effort is expected to accomplish Objectives 1 and 2 for a cost of no more than $2.5M.

Remaining funds are to pursue Objective 3. If additional funds become available, contract enhancements are possible.

The above cost constraint/funding profile is an estimate only and will not be a contractual obligation for funding. All funding is subject to change due to Government discretion and availability.

9.0 Security

The contractor shall provide security up to and including SECRET/NOFORN and be within compliance of the Radar Technology Security Classification Guides.

See BAA Attachment 4, DD-254, and dated 18 NOV 2016.

10.0 Additional information

10.1 A limited distribution Statement of Objectives (SOO) can be requested via email to Alan Kerrick (Alan.Kerrick@us.af.mil) or Jonathan Buck (Jonathan.Buck.1@us.af.mil). Requests for the annex should include at a minimum, the company name and address, and the technical point of contact (POC) name, phone number, and email address.

10.2 The Government anticipates that most of the development work under this contract will be conducted at the SECRET level.

10.3 Responses may be classified up to SECRET. Classified responses must be coordinated with AFRL/RYMR (Alan Kerrick (937-713-4350) or Jonathan Buck (937-713-8232)). All responses must follow Radar Technology Security Classification Guide, dated 26 March 1996 (revised 25 October 2005) to respond to the BAA.

11.0 OPSEC

General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Information List (CIL) will be provided upon request by RYOY Information Protection Office.

While working on the government installation, OPSEC guidance will be provided by the RYOY Information Protection Office.

12.0 Safety

The following requirements must be incorporated into the contract:

1. Must comply with all federal, state, and local safety and environmental regulations.

2. Requires an approved Safety Plan IAW AFI 91-202 AFRL Supplement 1 before any experiment may be conducted. Must comply with all Air Force safety and environmental regulations.

3. Must comply with system safety requirements contained in MIL-STD 882E, Section 4 “General Requirements” for any deliverable systems or hardware. Must identify safety-critical components of those systems or hardware, and software interfaces with those components. Must test and verify the safety-critical hardware and software for safety acceptance.

13.0 Associate Contractor Agreements

Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that specify requirements for them to share information, data, technical knowledge, expertise or resources. The contracting officer may require ADAs when contractors working on separate government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.