Attach 1 - RIK-OTA-20-R-FINN.docx

Description Funding Opportunity Title: Fused Integrated Naval Network (FINN) Prototype

Announcement Type: Request for Project Proposals (RFPP)

Project Announcement Mission Thread Identification/Funding Opportunity Number: RIK-OTA-20-R-FINN

Due Date: Please note that SOSSEC, Inc. may have an earlier due date in their Consortium announcement than that indicated in this posting.

Anticipated Individual Awards: Single award is anticipated. However, the Government reserves the right to make multiple awards if it is in the Government’s best interests.

Types of Instruments that May be Awarded: Firm Fixed Price project level agreement.

ELIGIBILITY INFORMATION

Participation in this RFPP, and to receive an award under this PA, will require a membership in the SOSSEC Consortium. SOSSEC, Inc. is the Open Systems Acquisition Initiative (OSAI) awardee/recipient. Joining the SOSSEC Consortium is a very quick process. New members will be asked to review the Consortium membership agreement and pay a membership fee. The AF OTA is an Agreement between the Government (AFRL/RI) and SOSSEC, Inc. SOSSEC, Inc. acts as a mentor and intermediary, supporting companies that bid solutions. For further information about SOSSEC or how to join, please contact John Nunziato, (603) 458-5529, jnunziato@sossecinc.com or Linda Sasser, (603) 458-5529, lsasser@sossecinc.com

NOTE: The below paragraphs are only excerpts from the full Project Announcement. For the full Project Announcement, including any referenced attachments, please contact John Nunziato, SOSSEC, Inc., (603) 458-5529, jnunziato@sossecinc.com or Linda Sasser, (603) 458-5529, lsasser@sossecinc.com .

Introduction This Project Announcement (PA) is a one-step closed project announcement. This announcement is being issued to solicit proposals only at this time. Whitepapers will not be requested. Upon receipt of proposals, the Government will evaluate through a scientific review process in accordance with the Evaluation Criteria to determine which proposal(s) represent the best value to the Government and should be awarded.

Overview The Government seeks proposals to continue the existing, ongoing, and successful development and testing of their Fused Integrated Naval Network (FINN) airborne pods and supporting technology.

The current effort involves, and continues to require, a comprehensive familiarity with the installation, configuration, operation, securing, and maintenance pertaining to air-to-air and air-to-ground Tactical Data Links, commonly implemented communications systems, and general information technology in use by the US Department of Defense (DoD) today, as well as, familiarity and experience with the installation, configuration, operation, securing, maintenance, and information assurance accreditation of equipment pertaining to Internet Protocol networking over US Government Systems.

The end-state objective of the FINN effort is to produce an airborne prototype capability to be integrated onto the General Atomics MQ-9B. The prototype will provide a persistent Gateway that receives, bridges, translates, processes and distributes information between other FINN nodes and the end-user nodes connected to them. At a minimum, the prototype must be capable of cross-banding Internet Protocol (IP) and non-IP based data exchange between dissimilar users using both legacy and emerging communications technologies, enabling beyond-line-of-sight connectivity to a wide range of users, enabling real-time data format translation between users, and it will make available the capability to host Command and Control (C2) processes on-board the platform. Prototype to consist of the following waveforms: Link 16 (CMN-4), TTNT version 6.9 and 7.0, BE-CDL, iCDL, TSM-X (NSA Type-1 variant), and Next Generation Waveform (NGW). Minimally viable prototypes developed at each milestone are intended be used in live experimentation events. When a prototype has been determined by the Government to be at a minimally viable maturity for possible transition, a Technical Design Package (TDP) is to be developed for Government use.

Background The Marine Corps Warfighting Laboratory (MCWL) performs live-force experimentation for the purpose of assisting requirements developers to define and refine Service-level systems requirements, and, to assist in the development of future Service-level doctrine.

MCWL's primary customer is the USMC requirements development community located within the Marine Corps Combat Development Command (MCCDC). In order to help define and refine requirements for future capabilities, MCWL takes an “informed and reasonable approximation" approach to developing minimally viable prototypes capable of being placed in service level live force experimentation. As well as requirements refinement, the resulting data assists warfighters to visualize new concepts of operation that are required to be developed in order to best employ potential future capabilities before they formally receive that capability or something physically or conceptually similar.

The prototype FINN capability is an agile S&T development test bed engineered to be quickly modified with new and emerging technologies as necessary to participate in various service level live force experiments. It’s intended to provide minimally viable and functionally tested capabilities through spiral development over potentially multiple iterations. As a long term S&T project, it is not MCWL’s intent to restrain ourselves, nor our performers, to concepts or solutions that may or may not be valid tomorrow.

The current FINN prototype is built with in an AFRL AgilePod 30L shell and currently integrates the following waveforms: Boeing’s Directional Networking Waveform (DNW), Link-16, and Tactical Targeting Network Technology version 6.9. In December 2019, the existing prototype was successfully flown and tested over the course of 5 days at Marine Corps Air Station (MCAS) Yuma Arizona on a surrogate aircraft.

The next iterations to be developed will temporarily utilize two 26 inch AFRL designed “Manufacturing Interchangeability Study, Pod B, Manufacturer I” (MISBI) pods. AFRL will provide the MISBI pod Technical Design Package (TDP) to the MCWL to be produced by the awardee of this effort exclusively as part of this effort on or about September 15, 2020. Once produced, airworthiness certification and platform integration with the MQ-9B will be required. The MISBI Pods are expected to be utilized as until such a time that the US Air Force’s 26 AgilePod Design is certified and made available for production. The 26 AgilePod TDP is not expected to be available until FY 2022.

In addition to the previously mentioned waveforms, it will also include: Type 1 variant of TrellisWare Tactical Scalable MANET-X (TSM-X), Intelligence Broadcast System (IBS), Bandwidth-Efficient Common Data Link (BE-CDL), and TTNT 7.0. Additionally, the DNW system previously used will be replaced with equipment from the Office of Naval Research which will enable a new capability known as Next-Generation Waveform (NGW). NGW hardware that is capable of being integrated into an airborne platform is not expected to be delivered until Fall 2021.

As well as waveforms and their required radios, the FINN capability integrates multiple different types of Internet Protocol (IP) networking equipment, High Assurance Internet Protocol Encryptor (HAIPE) security devices and various data processing hardware and Command and Control (C2) software, as well as system monitoring and control software. The MQ-9B is USAF Open Mission Standard (OMS) compliant. The FINN pod solution should also be OMS compliant to the greatest extent possible.

1.0 Requirements (all references to Contractor in the below have the equivalent meaning as vendor or Project-Level Performer (PLP))

1.1 Systems Engineering and Program Management

1.1.1 Program Management

The Program Management activity consists of the technical, business planning and scheduling, organization, direction, and financial control to ensure the successful development, integration, build, test, and demonstration of the deliverable product.

Program management tasks shall include, but not limited to:

· Program Planning and Control

· Contract Management

· Subcontracts Management

· Financial Management

· Meetings and Reviews

· Configuration and Data Management (including Change Management)

· Risk Management

· Quality Management

1.1.2 Program Management Reporting

The Contractor shall support monthly status meetings to examine the position of the program in relation to the desired objectives. The Contractor shall report progress to plan and address any problems or open items. The monthly status meetings to be held via teleconference or in person, estimate 6 at contractor’s facility, 6 at customer’s facility and the rest via teleconference.

Program status items may include:

· Technical interchange, technical achievements, trade studies, technical performance measures

· Accomplishments, upcoming activities, key milestones

· Schedule status

· Problem identification and recovery/corrective action plans

· Staffing and resources status

· Risk and opportunity and

· Change status of all changes being tracked and implemented

The Contractor shall generate a Monthly Status Report (CDRL FINN-01) and support a monthly program update teleconference. The Contractor shall support informal status teleconferences, as required.

1.1.3 Integrated Master Schedule (IMS) Reporting

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) to track progress toward achieving each milestones. The Contractor shall provide a monthly IMS update that reflects the development, integration and test tasks. The IMS will address all phases of this program. The Contractor shall develop and maintain a schedule to track progress toward achieving selected milestones. Schedule status shall be included in the monthly status report (CDRL FINN-01).

1.1.4 Cost Reporting

The Contractor shall include financial data, actuals, invoiced to date, Estimate to Complete (ETC), Estimate at Completion (EAC) in the monthly status report (CDRL FINN-01)

1.1.5 Systems Engineering Management

The Contractor shall perform systems engineering management to technically manage all assigned requirements, development, integration, testing and demonstration efforts. The Contractor shall utilize appropriate systems engineering practices and tools to track design iteration and characterization and maintain design integrity.

1.1.6 Configuration Management

The Contractor shall implement Configuration Management process through established company procedures using standard DoD practices as guidance. All responsibility for furnishing collected or generated data for configuration management rests with the Contractor.

1.1.7 Data Management

Using internal policies and procedures for Data Management (DM), the Contractor shall implement an appropriate DM process that meets contractual requirements and industry standards for control of the deliverables. The Contract shall prepare and deliver the documents specified in the Contractual Data Requirements List (CDRL) in Table 4. The deliverables will be submitted via electronic CDRLs in the format specified in Table 4.

1.1.8 Risk Management

The Contractor shall perform risk management in accordance with the Contractor’s project management system. Risks are to be reported at the monthly reviews to include the identification, management, mitigation and disposition of risks and opportunities.

1.1.9 Quality Assurance

The Contractor will design, build, and test deliverables utilizing existing Contractor product assurance and quality assurance standards appropriate for a laboratory prototype system.

1.1.10 Security

This effort is to be executed as a Top Secret (TS) Sensitive Compartmented Information (SCI) level program (as required) in accordance with DD254 and program direction.

1.1.11 Travel

The Contractor shall perform travel as necessary to support the program as defined in these requirements. Estimated travel is in Table 2.

1.2 Engineering Development

The Contractor shall perform the following activities and deliver, where specified, the following hardware and documentation.

1.2.1 Systems Engineering

The Contractor shall conduct the following systems engineering efforts including preliminary and final design, system engineering trade-offs, and other system engineering support required in the FINN system prototype development.

The Contractor shall develop and deliver a Technical Report-Study and Test Plans in support of Demonstrations and Post Demonstration reports as identified in Table 4.

1.2.2 Develop FINN Management System (FMS) to integrate applications into the FINN payload. Applications to include network routing, pod control, health cross-banding, monitoring, data translations, Electronic Circuit Breaker Unit (ECBU) control and track data link management.

1.2.3 Generate system, software, and hardware requirements documentation. Tasks will include support for Information Assurance and Risk Management Framework requirements.

1.2.4 Prototype Development

1.2.4.1 Development of Aircraft PODS

The Contractor shall develop and fabricate pods for the mounting of FINN communication system equipment on MQ-9B aircraft. The pod design engineering effort shall ensure FINN system equipment Size Weight and Power (SWAP) and packaging needs are met, as well as antenna and radio performance requirements satisfied to meet FINN link availability and range performance.

The Contractor shall develop and fabricate pods for the networking and interoperability of FINN communication system equipment with the networking of sensors and communications systems of the MQ-9B aircraft. The MQ-9B is USAF Open Mission Standard (OMS) compliant. The FINN pod solution should also be OMS compliant to the greatest extent possible.

Produce two additional FINN Pod system set prototypes beyond the first article set. Equipment designated as Controlled Cryptographic Items (CCI) will be provided as Government Furnished Property (GFP)(Reference Attachment No. 3).

1.2.4.2 Development of Ground Node

The Contractor shall develop a ground node(s) to assist in testing of the payload. Ground node(s) may have duplicate radios from the pod, ability to control the payload and collect data during the development tests.

1.2.4.3 Test Aircraft

The Contractor shall provide surrogate aircraft to support each development test requirements. This will include confirmation that the selected aircraft is mechanically and electrically compatible with the FINN pod. The surrogate aircraft must meet all FAA and appropriate safety requirements. The Contractor shall coordinate selection and scheduling of an appropriate bed down location for the surrogate aircraft and all required ground equipment.

The Contractor shall obtain the necessary Frequency/Spectrum Clearances required for each Development test. The Contractor shall obtain the necessary airspace reservations for each Development test. The Contractor shall prepare and deliver the required documentation to support any required appropriate Flight Safety and Test Readiness Review. The Contractor shall ensure efficient operation, test and evaluation of the FINN payload and all ground nodes.

2.0 Developmental Tests

2.1 Flight Developmental Tests

The Contractor shall prepare test plan, receive appropriate safety of flight approval and spectrum approval for each development test event. The Developmental tests shall be conducted in accordance with the requirements below. The Contractor shall provide a test plans (CDRL FINN-03, CDRL FINN-05), quick report (FINN-06) and final test report (FINN-07) for each Development Test as identified in Table 4.

2.1.1 Design, build and integrate the two pod FINN Pod system that can be ultimately certified on MQ-9B. The FINN system shall consist of two pods and be designed to be mounted on the MQ-9B to deliver 360-degree coverage of from Electronically Steerable Arrays (ESA) located in the front and rear of each pod to support NGW. The Contractor shall include additional functionality agreed upon from the FMS study, to include data routing, network management, and security architectures as required. Conduct DT- 4 to fly a FINN 2-Pod configuration at the Marine Corps Weapons and Tactics Instructor Course (WTI) in the April/May 2021 time frame on a surrogate aircraft.

2.1.2 Support demonstration test DT-5 and tests of the FINN Payload. Assume test to be located on the west coast with 2 FINN pods on a surrogate aircraft with same radios and waveforms as in DT-4. The Contractor shall include additional functionality agreed upon from the FMS study, to include finalizing data routing, network management, and security architectures as required.

2.1.3 Support demonstration DT-6 and tests of the FINN Payload. Assume test to be located on the west coast with 2 FINN pods on a surrogate aircraft and same radios and waveforms as in DT-4 with additional NGW capability. The Contractor shall include additional functionality agreed upon from the FMS study, to include finalizing data routing, network management, and security architectures as required.

2.2 Developmental Test Efforts

2.2.1 Coordinate and execute flight safety certification and airborne compatibility testing of the FINN Pods on the MQ-9B (please include in separately priced milestone).

2.2.2 Production and support of one additional FINN prototypes to support testing of two FINN nodes operating together (please include in separately priced milestone).

2.2.3 Create the FINN Pod Technical Data Package (TDP). The TDP must accurately depict the final product. TDP data includes, but is not limited to, Computer Aided Design (CAD) data, CAD models, fabrication and installation drawings and Master Bill of Materials (BOM) in Contractor format. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s) (please include in separately priced milestone).

2.2.4 Create, and deliver electronically, New Equipment Training (NET) material intended to be used as part of user training in preparation for testing events. Materials should address both operation and maintenance of the system at an organizational/ tactical level and include materials appropriate for both instructors and students (please include in separately priced milestone).

3.0 Flight Test and Evaluation

3.1 Design Reviews. Conduct a design review or a series of design reviews during the course of the project. The number of reviews, their exact timing, and the topics to be covered will be program dependent and shall be determined by the Marine Corps Warfighting Laboratory’s C4ISR Branch Head and/or his designated representative but will generally be aligned to complement each milestone.

3.1.1 Submit the review agenda to the Government for review and approval at least 15 days prior to the desired review date. Review topics shall include at a minimum technical objectives and success criteria, test article description, vehicle modifications, safety systems, airworthiness of vehicle(s) and subsystems, preliminary test plans and schedules, and instrumentation system requirements.

3.2 Test Plan and Support to the AFRL Safety Review Board (SRB) and Technical Review Board (TRB). Submit the draft test plan (IAW AFRLMAN 99-103, Attachment A5.4 format) to the Government prior to testing for review and approval. AFRL must approve the test plan prior to testing, including taxi tests. Support the SRB and TRB-by, either attending the reviews or participating via telecom. The decision of the type of PLP support to the reviews is made by the AOTR and TRB and SRB chairmen. (See CDRL, FINN-05) Flt Test Plan (draft at least 8 weeks and the final at least 5 weeks prior to testing)

3.3 Support to AF Mishap Investigations. Adhere to AFRLMAN 99-103 in the event of a mishap (defined as an unplanned event, or a series of events, that result in damage to DoD property, occupational illness to DoD military or civilian personnel, injury to DoD military personnel on- or off-duty, injury to on-duty civilian personnel; damage to public or private property or injury and illness to non-DoD personnel caused by DoD operations). This includes, but is not limited to, immediate access to all test data, test-related documents, and vehicle documentation including, but not limited to, video, pictures, witness statements, onboard recorded data, telemetered data, vehicle systems checks, and vehicle or system squawk sheets. If an AFRL representative is not present during the mishap, notify the AFRL AOTR of the mishap as soon as practicable after the mishap has been debriefed at the test location but no later than eight (8) hours immediately following the mishap. If the AFRL AOTR cannot be reached in person, execute the notification procedures as specified on the AFRL Form 29. In the event of a mishap, the data and information collected must be protected until guidance is provided by a cognizant Government representative. It is recommended that the PLP have an established safety representative, through whom communication will occur and the data and information collected will be transmitted to the Government.

3.4 PLP Identified Lessons Learned. Provide lessons learned at the completion of the program about the formation, conduct, and reporting of the flight test program to include the design, development, and testing phases to the government using AFRL Form 20, Lessons Learned. However, if the lesson learned is safety related, notify the government immediately.

Period of Performance:

The total period of performance is estimated to be 24 months from effective date of award.

Data Rights: Unlimited Rights Preferred, Government Purpose Rights Acceptable. Other rights may be considered on a case-by-case basis.

Funding: Total funding for this PA is approximately $14,585,000.00, which includes the SOSSEC fee. There is also the potential to make awards up to any dollar value.

A single award is anticipated under this announcement. The Government reserves the right to make multiple awards if it is in the Government’s best interests.

The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

Contact Information Primary Point of Contact

· John Nunziato

· jnunziato@sossecinc.com

· Phone Number 603-458-5529 Secondary Point of Contact

· Linda Sasser

· lsasser@sossecinc.com

· Phone Number 603-458-5529