SOO_RTD2_FY18_draft_v5_NC.pdf

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 1 OF 9

RAPID TECHNOLOGY DEVELOPMENT AND DEMONSTRATIONS (RTD2)

STATEMENT OF OBJECTIVES (SOO)

17 DEC 2018

1.0 OBJECTIVE

The objective of the Rapid Technology Development and Demonstrations (RTD2) Program is to develop new and novel concepts for sensor systems and systems of sensor systems across multiple domains and spectrums that aid in Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) and battlespace awareness. The RTD2 program will assess and understand requirements; perform operationally relevant analysis;

perform technical analysis; assess advanced technologies; support ground and flight integration, demonstration, and tests; explore sensor system integration; research, develop, assess and understand new ways of Systems Engineering (SE) and integration; perform research, development, and analyses of these systems in operationally relevant environments, both through laboratory and real-world flight testing; assess advanced SE/Systems of Systems (SoS) technologies, including open architecture, adaptable interface, and system composition technologies.

2.0 BACKGROUND

Sensor research offers unique, complex problem sets that require technically feasible solutions with insight into operational systems integration. The research incorporates sensor system hardware and software, sensor fusion algorithms, PED, link development, and integration with supporting technologies. Modeling and simulation provide quantitative performance, however, DoD Systems have become increasingly complex over the years. This complexity requires new methods for systems engineering and new integration technology approaches. Additionally, more advanced threats continue to be developed, causing the DoD to respond at a more rapid pace.

These changing threat environments increase the need for flexibility and adaptability in the DoD systems, allowing the warfighter to better respond to the changing landscape. Traditional systems engineering, test, and demonstration approaches are not sufficient to meet these emerging needs.

AFRL/RYZ seeks to continue research, development, and demonstration of new and novel technologies to rapidly address the capability needs of the warfighter, enabling rapid sensor integration technologies, new ways of approaching systems engineering, ground demonstration, and flight tests.

3.0 TASKS AND TECHNICAL REQUIREMENTS

3.1 Sensor Integration Research, Development, Test & Analysis

This task area focuses on the understanding of requirements and then the research and

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 2 OF 9

development of sensor systems and technologies across multiple domains and/or cyber environments. This includes how sensors integrate with other sensors, from the full spectrum of mechanical, electrical, and software. Additionally, this area explores how individual sensors can interoperate together to perform mission needs as a full system of systems. This includes virtual design but also leads into physical integration of different components and ground testing and analysis. This task utilizes existing open architecture solutions, but also invites new integration solutions for all sensor phenomenology to enable rapid integration of sensors. This area couples systems engineering with novel new approaches for systems engineering and integration, through research, development and lab demonstration. The contractor shall have a working knowledge of SE core principles, Open Architectures (OA), Open Mission Systems (OMS), Sensor Open Systems Architecture (SOSA), integration, testing, and analysis of test results. The contractor shall utilize this expertise to provide research, development, and analysis in further developing these concepts and applying them to technology demonstrations. The contractor’s research shall support a wide range of research and analysis topics to include the following sub-tasks.

3.1.1 Open Adaptable Architecture Research, Development, and

Implementation

The contractor shall investigate existing and emerging architectures and standards that enable the development of open architecture and SoS solutions for manned and unmanned platforms. Activities in this research area may include configuration and execution of OMS based technologies, as well as development of new capabilities to demonstrate OMS concepts and principles which may include additional message sets, applications, utilities, tools, and documentation. Additionally, investigations of alternative open architectures and technologies that enable interoperability with, or in lieu of, OMS based technologies may be applicable. Other related activities in this research area may include assessing available COTS/GOTS ISR payloads and mission systems for integration suitability based on SWaP, sensor performance, metadata accuracy, overall functional capability, and interface requirements.

3.1.2 Tactical Research for Benefits of Transition of Technology

The contractor shall perform overall assessment of advanced technologies by analyzing global sensor research and development and evaluating emerging sensor concepts for military operational utility. The contractor shall conduct requirements analysis for new sensor concepts.

3.1.3 Lab Integration Demonstration and Testing

The contractor shall integrate technologies using newly developed methods for systems engineering in order to advance rapid integration of sensor technologies. The contractor shall work with any and all sensor and data types, allowing full integration without limits. The contractor shall develop viable test plans, execute, and produce test reports for ground demonstration testing.

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 3 OF 9

3.1.4 Understand requirements

Understand integration requirements at a high level and be able to translate to a detailed technical level

3.1.5 Interface with other DoD organizations

The contractor shall consult with DoD operators and organizations to understand current and future warfighter requirements. The contractor shall analyze existing documents, such as lessons learned, after-action reports, and vision documents to identify operational gaps.

3.1.6 Consider Sensor Requirements and Systems Integration

The contractor shall research Air Force strategic planning documents and develop a core set of simulation scenarios. The contractor shall identify Interface Control Documents (ICDs), data flows, processing platform requirements, Size, Weight, and Power (SWaP) constraints, and operating profile.

3.1.7 Plan and Conduct Analyses for Sensor Technology Selection

The contractor shall perform overall assessment of advanced technologies by analyzing global sensor research and development and evaluating emerging sensor concepts for military operational utility. The contractor shall conduct requirements analysis for new sensor concepts.

3.1.8 Evolve Concepts for Sensor Systems

The contractor shall analyze sensor system requirements to maintain appropriate Preplanned Product Improvement (P3I) flexibility and modify CONOPS and Tactic, Techniques, and Procedures (TTPs) for the evolving operational environment. The contractor shall analyze specified sensor systems for applicability to layered sensor and multi-INT fusion environments. The contractor shall analyze sensor compatibility to various threat environments.

3.1.9 Technical Analysis

The contractor shall plan and conduct technical analyses on specified sensor systems.

The contractor shall prioritize requirements, elicit and evolve performance metrics (KPPs), and create measures for requirements satisfaction (MOPs and MOEs).

3.1.10 Analyze Specific Technologies, System Hardware, and Software

The contractor shall review the sensor developer’s documentation and data, and assess sensor Technology Readiness Level (TRL).

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 4 OF 9

3.1.11 Analyze Sensor Fusion Algorithms

The contractor shall review the algorithm developer’s documentation and data, and assess algorithm TRL.

3.1.12 Analyze PED and Data Link Development with Other Supporting Technologies

The contractor shall review the developer’s documentation and data, and assess TRL.

3.1.13 Run Modeling and Simulation with Multiple Scenarios

The contractor shall determine appropriate tools and facilities for modeling and simulation. The contractor shall determine equipment configuration, setup, interconnections, and protocols. The contractor shall determine operation requirements, such as SWaP, stimuli, HW/SW, and security.

3.1.14 Assess Advanced Technologies

The contractor shall obtain sensor data from simulations, operations, or testing to assess technologies.

3.1.15 Assess Sensor Performance in the Context of Operational Missions, Technical Viability, and Life Cycle Costs

The contractor shall estimate end-to-end sensor performance and effectiveness in operational missions. The contractor shall evaluate technical viability of deploying, installing, operating, and sustaining sensor systems. The contractor shall estimate sensor system life-cycle costs.

3.1.16 Systems Engineering

The contractor shall use a disciplined systems engineering approach tailored to suit the nature of individual sensor technologies. The contractor’s systems engineering approach shall provide an integrated analysis program, combining the results from operational and technical analyses.

3.2 Advanced Prototype Integration and Demonstrations / Flight Tests

The objective of this task area is to perform novel systems engineering and rapidly integrate technology solutions and advanced prototype components developed in the previous areas and to conduct advanced technology demonstrations to mature technologies and develop lessons learned. This task seeks to complete development and

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 5 OF 9

integration and evaluate the technology prototypes under realistic operating scenarios to the maximum extent possible to assess these technologies and reduce integration risk.

Plans, processes, and measures of effectiveness must be defined and executed in order to illustrate the capability, determine the maturity, and quantify the benefit to ensure ease of integration and reduced risk. Component prototypes resulting from the aforementioned task areas shall be integrated and demonstrable in a realistic operating environment. This environment can include ground system integration lab testing and also go up to flight testing in relevant environments. The contractor shall have previous experience in integration and flight test. The contractor shall develop, implement, and conduct these Advanced Prototype Demonstrations in an operationally relevant environment including:

ground tests, flight tests, distributed tests, and integrated simulations and testing.

3.2.1 Integration of Technologies

The contractor shall perform integration of new and previously existing technologies using sound systems engineering processes, and leveraging open and adaptable architectures. The contractor shall develop and implement new methods to integrate end prototype technologies. The contractor shall document the integration practices of these technologies.

3.2.2 Ground Demonstrations / Tests

The contractor shall capture technology/test requirements for laboratory and ground demonstrations, tests, or exercises. The contractor shall identify test platforms and environments applicable to test objectives. The contractor shall draft and coordinate documents for each test (Federal Aviation Regulation (FAR), test cards, checklists).

The contractor shall participate in periodic meetings (Configuration Control Board (CCB), Test Planning Working Group (TPWG), Safety Readiness Board (SRB), Test Readiness Board (TRB) and perform relevant actions as required. The contractor shall coordinate with any and all pertinent stakeholders and partners at the Government’s direction. The contractor shall document test reports.

3.2.3 Flight Tests

The contractor shall coordinate flight operations and specific test approvals with proper officials. The contractor shall capture technology/test requirements for flight demonstrations, tests, or exercises. The contractor shall identify test platforms. The contractor shall draft and coordinate documents for each test (FAR, test cards, checklists). The contractor shall participate in periodic meetings (CCB, TPWG, SRB, TRB) and perform relevant actions as required. The contractor shall procure materials to collect, store, and retrieve sensory data and air/ground truth data. The contractor shall secure airworthiness and coordinate test ranges and collection targets. The contractor shall supply airworthy aircraft. The contractor shall coordinate airspace, FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 6 OF 9 flight plans, permits, and frequency clearance with respective authorities. The contractor shall determine equipment configuration, setup, interconnections, and protocols, and integrate the system under test into a System Integration Laboratory and/or aircraft. The contractor shall hold TRRs and FRRs as required. The contractor shall perform ground and flight activities to include aircraft preflight checks, sensor initialization and checks, instrumentation checks, and aircraft launch and recovery.

The contractor shall execute all steps described in test cards and checklists.

3.2.4 Testing In Multi-Domain Environments

The contractor shall have the ability to develop, plan, and implement distributed tests over multi-domain environments and loosely coupled networks.

3.2.6 Integrated Simulations and Testing

The objective of this task area is to perform platform integrated simulation and testing in an environment with representative architectures, hardware interfaces, and services to provide a specified level of confidence to on-board interoperability. The contractor shall develop, implement, conduct, & provide analysis for integrated simulation and testing events.

3.3 System Maturation.

Perform system transition activities to include the following:

3.3.1 (O&M) Objectives include developing software updates and maintenance for integration into operational systems. Provide modeling and simulation tools, and database updates.

3.3.2 (Procurement) Objectives include developing transition plans, performing and executing assessments, data collections, and/or modeling and simulation activities for application of technology to production unit/systems(s).

3.3.3 (Other) Objectives include system deployment participation, technical troubleshooting, required equipment upgrades, training, and technological input as needed.

4.0 PROGRAM MANAGEMENT

The contractor shall exercise program administrative and financial functions during the course of this effort. These functions shall include: scheduling and tracking activities/milestones;

subcontractor management; reporting program status and identifying risks, problems, and mitigation strategies; ensuring deliveries; planning, forecasting, recommending budgeting, FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 7 OF 9 budgeting changes, and follow-on efforts; and documenting technical breakthroughs or discoveries. The contractor shall support conducting research and development both on-site (i.e., at a Government facility) and off-site (i.e., at the contractor’s facility) as appropriate for each task order.

5.0 PERIOD OF PERFORMANCE

The technical effort shall be a 57 month effort plus 3 months for contract close out and collection of any final report(s).

6.0 FUNDING PROFILE

FY19 FY20 FY21 FY21 FY23 FY24 Total 3,000,000 9,600,000 15,700,000 15,900,000 15,900,000 3,100,000 3600 0 900,000 800,000 800,000 800,000 500,000 3400 3,000,000 $10,500,000 $16,500,000 $16,700,000 $16,700,000 3,600,000 $67,000,000

7.0 DELIVERABLES

The government desires all data, models and software acquired under this effort be delivered without restriction as to its use or future distribution, unless subject to licensing restriction imposed by a third party. The government desires that the contractor acquire software and data with unrestricted rights/licensing as directed by the Government whenever possible, and shall assist the Government, as needed in making the cost/benefit tradeoffs associated with acquiring said rights/licensing. The government desires all data, models and software developed under this contract be delivered to the Government with unlimited rights.

a) Data Items:

i. A001 SCIENTIFIC AND TECHNICAL REPORTS

ii. A002 FUNDS AND MAN-HOUR EXPENDITURE REPORT

iii. A004 STATUS REPORT

iv. A005 SCIENTIFIC AND TECHNICAL REPORTS

v. A006 PRESENTATION MATERIAL

vi. A007 TEST PLAN

vii. A008 TEST PLAN

viii. A009 SYSTEM/SUBSYSTEM SPECIFICATION (SSS)

ix. A010 SOFTWARE TEST PLAN (STP)

x. A011 SOFTWARE DESIGN DESCRIPTION (SDD)

xi. A012 SOFTWARE TEST REPORT (STR)

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 8 OF 9

xii. A013 COMMERCIAL OFF-THE-SHELF (COTS) MANUAL AND

ASSOCIATED SUPPLEMENTAL DATA

xiii. A014 COMPUTER SOFTWARE PRODUCT

b) Software: The contractor shall procure COTS software if not available through government channels and required for the performance of this program. The contractor shall deliver all software developed under this contract with unlimited data rights

c) Hardware: The contractor shall procure materials if they are not available through government channels and are required for the performance of this program. Unique Identification (UID) does not apply.

d) Other: None at this time

8.0 SECURITY

8.1 Program Security Requirements

Individuals must be US citizens and may be required to have SCI DCID 6/4 Top Secret Eligibility based on a SSBI/SBPR to work classified efforts. Any/all SCI and/or SAP work will be required to be conducted within an accredited Special Access Program Facility (SAPF) and/or a Sensitive Compartmented Information Facility (SCIF). Specific security details and requirements will be outlined within future task orders. All classified efforts must be in compliance with National Industrial Security Program Operating Manual (NISPOM). Other regulations/policies that may apply to this contract are JAFAN 6/0 (Revision 1); DoD Directive 5205.07 (Vol 1-4); AFMAN 16-703 V3; SAF/AAZ Memorandum” Air Force Special Access Programs Nomination Process (SAPNP)” (30 Sep 2013); USD(I) Memorandum, Special Access Programs Nomination Process (20 May 2013); JAFAN 6/3 Implementation Guide, Version 1 (Sep 2006); DoD SAPCO Memorandum, Transition to the Risk Management Framework (RMF) (18 Dec 2013);

Joint Special Access Program Implementation Guide (JSIG) (9 Oct 2013); Intelligence Community Directives (ICD) 704 and 705; other applicable SCI regulations/policy; other applicable Security Classification Guides (SCG); and other applicable regulations/policy and subsequent revisions.

8.2 Operational Security (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 AFRL/ RYOY Information Protection Office. While working on the government installation, OPSEC guidance will be provided by AFRL/RYOY Information Protection Office.

FA8650-19-S-1110 CALL 1 ATTACHMENT 1 PAGE 9 OF 9

8.3 Information Security/Information Assurance (INFOSEC/IA)

The contractor shall apply subject matter expertise to manage the unique multi-level security information and networking requirements of the various SE and SoS Research & Analysis, Advanced Technology Demonstrations, and Integrated Technology Assessments task areas referenced above. This subject matter expertise should also include detailed knowledge and demonstrated applications of the RMF process.

9.0 BASE SUPPORT

Work performance is expected to be required at Sensors Directorate, 2241 Avionics Circle, Wright-Patterson Air Force Base, OH 45433. Some work performance may be required at contractor facilities. Travel in support of flight test and integration activities is expected. The contractor shall provide 8 individuals to perform work at Sensors Directorate.

10.0 GOVERNMENT FURNISHED EQUIPMENT (GFE) / GOVERNMENT FURNISHED

PROPERTY (GFP) / GOVERNMENT FURNISHED INFORMATION (GFI)

10.1 Government-Furnished Equipment (GFE) / Government-Furnished Property

(GFP)

All physical GFP/GFE will remain in government facilities. The contractor shall perform all work on-base and will not be responsible for GFP/GFE requirements.

10.2 Government-Furnished Information

The government shall provide the following items of GFI to the contractor for performance of work. The contractor shall take all appropriate measures to protect this GFI as mandated by <insert reference>

- Latest Pursuer software revision and database

- Blue Guardian Open Mission Systems (OMS) sensors adapters