Attachment 1 SOO.pdf

STATEMENT OF OBJECTIVES (SOO)

FOR

RESILIENT AND AGILE MISSION SYSTEMS (RAMS)

5 May 2020

1.0 OBJECTIVE

The objective of this effort is to prototype and demonstrate a TRL 6 next-generation mission systems architecture to empower advanced warfighting capability for current and future Air Force weapon systems.

2.0 SCOPE

The scope of the RAMS effort leverages current advances in open system architecture standards and approaches, commercial high-speed networking technologies, heterogeneous processing, precision timing, cybersecurity and cyber-resiliency, modeling and simulation, and advanced computing paradigms such as cloud infrastructure to enable advanced mission system capability.

3.0 BACKGROUND

The Air Force and DoD needs to rapidly and efficiently field advanced warfighting capability to maintain its technological advantage in highly contested and consistently changing environments. Fielding this capability needs to concentrate on Speed (reduce integration risk), Quality (meet needs, reduce defects), Focus (smaller working capabilities), and Collaboration (synchronize efforts across the enterprise). Today, fusion of multiple disciplines and domains is at odds with the organizational structure of the Air Force, which is generally aligned towards specific platforms/weapon systems in distinct domains. Over the last several years, AFRL/RYWA has demonstrated technical solutions related to platform architectures, open architecture standards, and cybersecurity and cyber-resiliency aimed at cutting across domains. However, technology is rapidly changing and AFRL seeks to be at the cutting-edge of this development. This effort seeks to build upon ongoing research and development within AFRL/RYWA in order to prototype a Resilient and Agile Mission Systems (RAMS) architecture for advanced, next-generation avionics. In addition to AFRL/RYWA technologies in the aforementioned areas of platform architectures, open architecture standards and cybersecurity/cyber-resiliency, this effort will leverage technological advances such as Cloud Computing, commercial sector technologies such as networking and processing, databases/data storage, data transfers, and emerging open standards/format/protocols. The resulting prototype will provide the platform infrastructure necessary to empower new mission system capability at the speed of relevance to meet the needs of next-generation avionics platforms.

4.0 TASKS/TECHNICAL REQUIREMENTS

4.1 Advanced Networking, Processing, and Timing

AFRL/RYWA has developed PlatformNxt, a next-generation avionics platform architecture. PlatformNxt provides the following properties to enable a new generation of advanced capabilities: 1) High-speed fiber-optic switched network fabric (called the Avionics Backplane Bus); 2) Extremely accurate time synchronized throughout the platform (sub 1 microsecond); 3) Dynamically configured, heterogeneous processing types including General Purpose Processing (GPP), Graphics Processing (GPU), and Field Programmable Gate Arrays (FPGA); 4) Built-in multi-layer cyber hardening and resiliency; and 5) Support for Open Mission Systems (OMS) standard compliance at the OMS Service, Subsystem, and Platform level, OMS data exchanges including messaging via the AFRL Critical Abstraction Layer Experimental (CAL-X) and Remote Direct Memory Access (RDMA) exchanges via approved data transfer protocols. PlatformNxt should be the point of departure for this task.

4.1.1 The contractor will identify advanced networking technology to support demonstration and prototyping of the RAMS architecture. Consideration will be given to emerging high-speed networking capability, which includes adaptation of commercial hardware to achieve network bandwidths speeds of 100-400Gb/s and beyond, as well as support for open standard hardware backplanes to accommodate bandwidths of 100-400 Gb/s and beyond; current and future high-speed data transports including but not limited to InfiniBand/Remote Direct Memory Access (RDMA), RDMA over Converged Ethernet (RoCE), VERBS, UDP, or other hardware-based technologies to achieve the desired speeds.

4.1.2 The contractor will identify current processing technology to support demonstration and prototyping of the RAMS architecture. Consideration will be given to emerging processing needs with emphasis on heterogeneous processing to include General-purpose, Graphics processing, Field-Programmable Gate Arrays (FPGAs), etc.

4.1.3 The contractor will identify novel approaches for providing precision timing or improving timing in a highly dynamic avionics architecture.

4.1.4 The contractor will work with the Government team to apply open standards for networking, processing, interfaces, backplanes, and chassis, and identify opportunities for applicability to the RAMS architecture. The contractor will monitor current and future open standards efforts within the Air Force and DoD for relevance to the RAMS architecture and apply these standards as appropriate.

4.2 Agile, Open System Infrastructure Development

AFRL/RYWA is leading Science and Technology (S&T) improvements for the Open Architecture Management Standards (OAMS), which includes Open Mission Systems (OMS) and the Unified Command and Control Interface (UCI) standards. AFRL/RYWA is leading and/or contributing to the evolution of these foundational open architecture standards to accommodate advances in avionics including low-latency, high-volume data exchanges, command and control of multi-function subsystems, CAL updates and enhancements, and experimentation, some of which are being applied to PlatformNxt. AFRL/RYWA has developed a software development kit which includes an OMS-compliant mission package with representative services and subsystems and a government-developed CAL, CAL-X.

4.2.1 The contractor will investigate current software and system architecture technologies, standards, and approaches to enable demonstration and prototyping of the RAMS architecture. Consideration will be given to emerging technologies including, but not limited to cloud computing, technologies to enable software-defined platforms, Development Security Operations (DevSecOps), technologies that enable rapid integration.

4.2.2 The contractor will identify applicable OA standards and investigate their applicability to enable rapid development, integration, and deployment of mission system capability within a mission systems architecture reference implementation. At a minimum, the RAMS architecture will be designed and developed in compliance with the OMS (v1.6) and UCI standards (V77.0)) to the highest compliance level possible, currently defined as Tier 3. Consideration will be given to maintaining OMS compliance, as well as opportunities to improve interoperability between OMS and other OA standards.

4.2.3 The contractor will work with the Government team to apply open architecture standards and identify opportunities for applicability to the RAMS architecture. The contractor will conduct interoperability studies to determine how the RAMS will accommodate other standards. Consideration should be given to the following, if different OA standards are: 1) compatible; 2) contain duplication; 3) and can be used together without conflict. As appropriate, the contractor will demonstrate the interoperability concepts within a laboratory environment including, but not limited to, modeling and simulation, and experimentation with the development of mission scenarios and testbeds, or technical reports.

4.3 Cybersecurity and Cyber-Resiliency

AFRL/RYWA is leading S&T efforts to identify and mitigate cyber vulnerabilities in current systems, develop techniques to make legacy platforms less susceptible to cyber attacks through cyber-hardening and cyber resiliency, as well as defense-in-depth strategies and countermeasures to provide protections at multiple layers of the system stack.

4.3.1 The contractor will identify and develop cybersecurity technologies to design-in cyber-resiliency and cyber-hardening of the RAMS architecture. Consideration will be given to prevention, detection, and adaptation strategies and techniques. The contractor will leverage and apply state-of-the-art commercial technologies as well as develop custom security technologies to protect RAMS architecture components and subsystems. These technologies may include hardware, software, and/or firmware protections.

4.3.2 The contractor will identify and develop technologies that reduce vulnerability of the RAMS architecture to cyber attack. Consideration will be given, but not limited to: a) Techniques and technologies to secure/authenticate communications via legacy and next- generation protocols (intra-platform and inter-platform); b) Technologies to prevent the introduction of malicious elements prior to fielding, between missions, and during missions; c) Technologies to securely integrate non-organic weapons, pods, roll-on-roll-off equipment, etc., without introducing cyber vulnerabilities to the platform; and d) Testing tools and techniques to identify and remove or mitigate vulnerabilities throughout the acquisition lifecycle. In general, technologies that aim to prevent the origination, introduction, and propagation of malware on avionics systems are of interest.

4.3.3 The contractor will work with the Government team to apply cybersecurity and cyber-resiliency methods and approaches as defined and/or in compliance with open standards and identify opportunities for applicability to the RAMS architecture, as well as integration of mission system capability with the RAMS architecture.

4.4 Resilient and Agile Mission System (RAMS) Architecture Implementation

4.4.1 The contractor will conduct systems engineering task to design, develop, and prototype a reference implementation for a mission system platform architecture to empower next-generation warfighting capability and advanced avionics needs. The RAMS architecture will have the following characteristics: 1) Support an OMS Tier 3 compliant mission package and platform; 2) Accommodate a variety of mission system capability (e.g., Radar, Communications, Electronic Warfare, Electro-Optical/Infrared (EO/IR), etc.); 3) Enable digital radio/radar frequency (RF) architecture with support for analog; 4) High-speed networking at speeds up to 100-400 GB/s and beyond; 5) Support for heterogeneous processing, as indicated in SOO para. 4.1.1; and 6) Provisions for cybersecurity and anti-tamper in compliance with the OAMS standards.

4.4.2 The contractor will incorporate continuous integration/continuous deployment concepts for development, integration, and deployment of the RAMS architecture in accordance with DoD initiatives such as DevStar.

4.4.3 The contractor will incorporate concepts and approaches that leverage the DoD’s Digital Engineering initiative, including modeling and simulation, to the greatest extent possible.

4.4.4 The contractor will identify requirements for tools to enhance RAMS architecture development, prototyping, airworthiness approval, and sustainment. The contractor will develop new tools, upgrade existing tools that may apply, and integrate these tools to realize an integrated tool environment to support RAMS architecture development and adoption. Tools under consideration include, but are not limited, automated compliance verification, platform architecture tools, data collection tools, metric identification, machine learning, integrity/validation, and artificial intelligence.

4.4.5 The contractor will develop, extend, and modify test code as required to ensure a high level of software quality using repeatable results. This includes, but is not limited to, automated testing frameworks, code quality scanning, configuration management techniques, and test case generation.

4.4.6 The contractor will document applicable tools and techniques. Documentation includes, but is not limited, to user guides, development guides, UML diagrams and other AF policy required documents as appropriate.

4.4.7 Research and development (R&D) tasks may result in changes to open architecture (OA) standards and documentation. As required, the contractor will prepare and submit changes to the OA standards and documentation in accordance with the change processes defined by the standards being modified. The government will approve all proposed changes, as well as the artifacts associated with the changes, prior to submission.

4.5 Collaborative Integration and Experimentation

4.5.1 Release Demonstration Events. The contractor will conduct or participate in collaborative demonstrations of the RAMS architecture using realistic completed capabilities and tools that include established/configured scenarios. These events may require software/hardware builds/documentation and testing prior to demonstration.

4.5.2 Advanced Prototyping. The contractor will design and evolve advanced concepts through prototypes as needed to demonstrate the research under these tasks. This includes, but is not limited to, data transports, dissemination and exploitation tools, modeling and simulation tools, data collection tools, metric identification, machine learning, integrity/validation, automation, and artificial intelligence.

4.5.3 Relevant Mission Scenario. The contractor will establish and maintain a scenario and demonstration to illustrate the resultant benefits of these capabilities and tasks.

4.5.4 Third-party Integration. The contractor will organize and participate in third-party software/subsystem integration with the established test beds within AFRL/RYWA, as needed, to demonstrate the relevant open architecture concepts.

4.5.5 Develop and Operate Research Networks and Platforms. The contractor will develop, operate, and maintain research networks as necessary for tool prototype design, development, and evaluation.

4.5.6 Adhere to Security Standards. The contractor will ensure the networks adhere to applicable security standards and meet requirements as designed in prototype and as required by AF policy.

4.5.7 Integration of Software. The contractor will design, develop, integrate and test software for research and development on the identified research networks to ensure the networks compatibility and readiness to complete this effort.

4.5.8 Update or Improve Performance. The contractor will provide materials, replacement components, and parts in a timely manner in an effort to prevent or eliminate malfunctions, enhance or update capabilities, or improve performance requirements.

4.5.9 Ensure Quality and Accreditation of Research Networks. The contractor will perform system backups, commercial software upgrades, and prepare or update computer security certification and accreditation packages as appropriate to ensure the networks compatibility and readiness to complete this effort.

4.5.10 Configuration of Networks and Platforms. The contractor will plan, execute, and manage all tasks required to configure the research networks and platforms for evaluation of identified advanced technologies to ensure the networks compatibility and readiness to complete this effort.

4.5.11 Enhance Research Platforms. The contractor will purchase, develop in-house, or construct any additional hardware, firmware, or software required for successful completion of this effort. This includes, but is not limited to, complying with all requirements for properly processing all acquired, developed, or constructed hardware, firmware, and software.

4.5.12 Testing and Data Collection. Once configured, the contractor will execute all tests, collect and store associated data, and perform post data processing as requested.

4.5.13 Documentation of Research Networks and Platforms. The contractor will document and record network descriptions, layouts, and features as appropriate for the type of network or platform under consideration.

4.6 Independent Assessment, Verification, and Validation

An important part of the RAMS effort is the ability to integrate different mission system capability across potentially multiple instantiations of the RAMS prototype architecture. In order to achieve this goal, AFRL/RYWA is seeking a contractor to fulfill an independent verification and validation partner to ensure that envisioned mission system capability can be rapidly and efficiently integrated within multiple prototype RAMS architecture implementations. The contractor may contribute relevant mission systems capability for integration within the prototype architecture implementation and the collaborative experimentation, Tasks 4.4 and 4.5 of this SOO, especially when related to verification, validation, and analysis of proposed methods or processes.

4.6.1 The contractor will conduct feasibility studies to assess the viability of proposed technical solutions for the RAMS prototype architecture. The studies will encompass all aspects of the RAMS architecture, including but not limited to hardware, processing, software architecture, architecture standards, and cybersecurity approaches.

4.6.2 The contractor will incorporate concepts and approaches that leverage the DoD’s Digital Engineering initiative, including modeling and simulation, to the greatest extent possible.

4.6.3 In cooperation with the Government, the contractor will ensure that different instantiations of the RAMS prototype architecture implementation support portability of mission software capability to the maximum extent possible.

4.6.4 At the discretion of the Government, the contractor will participate in development and design meetings related to the RAMS effort.

4.7 Associate Contract Agreements

4.7.1 The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the Resilient and Agile Mission Systems program, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

4.7.2 Provide a copy of such agreement to the Contracting Officer for review before execution of the document by the cooperating contractors.

4.7.3 ACAs will include the following general information:

Identify the associate contractors and their relationships.

Identify the program involved and the relevant Government contracts of the associate contractors Describe the associate contractor interfaces by general subject matter Specify the categories of information to be exchanged or support to be provided Include the expiration date (or event) of the ACA.

Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

4.7.4 The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor

4.7.5 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government

4.7.6 All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

4.7.7 The following contractors are associate contractors with whom agreements are required.

Contractor Address Program/Contract Number

5.0 MANAGEMENT

5.1 Program Administrative and Financial Functions. The contractor will follow program management processes to administer the program (functionally and financially) including, at a minimum, scheduling and tracking milestones and activities; managing subcontracts and Contract Data Requirements Lists (CDRLs);

reporting program technical, schedule, and cost status; planning, forecasting, and recommending funding or funding changes; and documenting technical breakthroughs or discoveries.

5.2 Management at Various Facilities. The contractor will support R&D on site (i.e., at a government facility) and off site (i.e., at the contractor’s facility), as appropriate.

5.3 Risk Management. The contractor will maintain a risk management process throughout the program identifying, analyzing, assessing, mitigating, and monitoring technical, schedule, and cost risks which will be included as part of the monthly status report.

6.0 DELIVERABLES

Data will be delivered in accordance with the CDRLs, DD Form 1423-1. The contractor will document all technical work accomplished and information gained during the performance of this acquisition. This documentation will include all pertinent observations, the nature of any problems, positive and negative results, design criteria established (where applicable), procedures followed, processes developed, lessons learned, and so forth. The contractor will document the details of all technical work to permit full understanding of the techniques and procedures used in evolving the technology or processes developed.

Separate design, engineering, or process specifications delivered during this acquisition will be cross-referenced to permit a full understanding of the total acquisition. Final software and hardware (including source code, firmware, libraries, and executables) developed on this effort will be delivered, with unlimited rights and with software in a format acceptable to both parties, at the end of the technical period of performance.

7.0 TECHNICAL REVIEWS

The contractor will hold a kickoff meeting at AFRL within 30 days after contract award. The contractor will host quarterly program management reviews and conduct ad hoc reviews as required with the government, stakeholders, and associate contractors. The contractor will involve required contractors, subcontractors, AFRL, and other research personnel as appropriate.

8.0 SECURITY

8.1 Program Security Requirements. In order for individuals to work on classified portions of this effort, the contractor will ensure that all individuals are U.S. citizens, understanding that they may be required to have SCI DCID 6/4 Top Secret Eligibility based on a SSBI/SBPR. The contractor will require that all SCI and SAP work be conducted within an accredited Special Access Program Facility (SAPF) and/or a Sensitive Compartmented Information Facility (SCIF). The government will outline specific security details and requirements. The contractor will ensure that all classified efforts comply with National Industrial Security Program Operating Manual (NISPOM) and other regulations/policies that may apply to this contract, such as Joint Air Force-Army- Navy (JAFAN) 6/0 (Revision 1); DoD Directive 5205.07 (Volumes 1–4); Air Force Manual (AFMAN) 16-703 V3;

SAF/AAZ Memorandum “Air Force Special Access Programs Nomination Process (SAPNP)” (30 Sep 2013);

Under Secretary of Defense for Intelligence (USD(I)) Memorandum, “Special Access Programs Nomination Process” (20 May 2013); JAFAN 6/3 Implementation Guide, Version 1 (Sep 2006); DoD Security Assistance Policy Coordinating Office (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 (ICDs) 704 and 705; other applicable SCI regulations and policies; other applicable Security Classification Guides (SCGs); and other applicable regulations/policies and subsequent revisions. Access to Joint Worldwide Intelligence Communications System (JWICS) is authorized for performance of SCI work, users shall be briefed NATO SECRET IAW the NISPOM, Para 10-706, prior to access).

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) and the RY OPSEC Plan will be provided upon request by AFRL/RYOY Information Protection Office.

While working on the government installation, OPSEC guidance and OPSEC training will be provided by AFRL/RYOY Information Protection Office. This training will ensure contractors are familiar with RY’s CIL and RY’s OPSEC Plan as it pertains to their contract. The contractor shall apply OPSEC in their management of their current program IAW AFI 10-701 Operations Security and WPAFB Supplement to AFI-10-701.

8.3 Security Training. The contractor will participate in the U.S. Government’s (USG’s) in-house and web-based security training program under the terms of the contract. The USG will provide the contractor with access to the online system. The contractor will take specialized security training as deemed applicable by

USG.

8.4 Security Duties. The contractor will be required to perform normal services under this contract between the hours of 0600-1800 excluding Federal Holidays. The contractor shall perform the following security tasks incidental to R&D efforts: End of day security; open, operate and close classified facilities; activate and deactivate alarms which requires access to alarm codes and alarm panel; facilitate access to classified information which will require combinations to locks for safes and doors during normal workhours and extended duty days. This may also include, at the discretion of the government, responsibility for performing after-hours alarm response which may require 24/7 building access in accordance with AF and DoD requirements. The government maintains the overall responsibility for all security related activities and is incumbent upon the contractor to officially communicate to the government these objectives and requirements have been appropriately completed in a timely and efficient manner.

8.5 Program Protection Plan. All DoD contractors (including subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract where critical program information (CPI) has been identified to protect the CPI to the standards articulated in the Program Protection Plan and in accordance with DoDI 5200.39. Upon contract award, all identified DoD contractors (including subcontractors) shall acknowledge and meet the requirements stated by the Program Manager for the protection of CPI. The DoD contractor must immediately notify the U.S. Government upon the discovery of any nonconformance with CPI protection. Applicable PPPs include, but are not limited to, the following:

“Standards Management Program Protection Plan”, Open Architecture Management Office, Air Force Lifecycle Management Center (AFLCMC), Wright-Patterson AFB OH, dated 1 Jan 2019; PlatformNxt (PNxt) Program Protection Plan (PPP), AFRL/RY, dated 10 May 2018.

9.0 SAFETY

The contractor will comply with all Air Force, federal, state, and local safety and environmental regulations.

The contractor will develop and have an approved Safety Plan (AFI 91-202 AFRL Sup 1) before any experiment may be conducted outside of a laboratory environment. The contractor will comply with safety requirements contained in MIL-STD 882E, Section 4, “General Requirements,” for any deliverable system or hardware. The contractor will identify safety-critical components of those systems or hardware and software interfaces with those components. The contractor will test and verify the safety-critical hardware and software for safety acceptance.

10.0 BASE SUPPORT

AFRL/RYWA will provide the contractor with laboratory space, equipment (on a non-interference basis), and computer/network access for conducting this effort, if proposed. Area B, Bldg. 620, AFRL/RYWA Laboratories including Mission Systems Open Architecture Science and Technology (MOAST) and Avionics Vulnerability Assessment, Mitigation, and Protection (AVAMP).