Data Fusion System

SUMMARYThis is a Request for Information (RFI) for planning purposes, as part of a market survey led by Navy Program Management, AIR (PMA) 265 for F/A-18 and EA-18G.  It is NOT a Request for Proposals. NO SOLICITATION DOCUMENTS EXIST AT THIS TIME.The PMA has identified a need for a modern Data Fusion System (DFS) that incorporates the latest data fusion algorithms, modular and open architecture, and ability to grow scope into future technologies.The Navy is interested in information on DFS that have at least government purpose rights and capable of integrating with Navy aircraft. The DFS should enhance situational awareness and shorten the time it takes to find, fix, track, target, engage, and assess time sensitive targets when compared to DFS from a decade or two ago. This RFI is intended to determine the existence of such systems and learn the maturity of these systems in military applications.CONSTRAINTSThe following constraints should be kept in mind when responding, as they will

apply for any future integration effort:Area                                      Constraint                                                                            - Amplifying InformationSOFTWARE                        Need to achieve operational use within calendar year 2027FUNCTIONALITY               Compatible with sensors and communication messages                          -Can be modified, but should have basis for receiving Navy air wing sensor and communicationsFUNCTIONALITY               Compatible with Navy aircraft communication links     -                            -Can be modified, but should have basis for sending and receiving information to and from other military systemsFUNCTIONALITY             Compatible with existing displays and Crew Vehicle Interfaces (CVI)          - Can be modified, but should have basis for sending and receiving information to and from other military systemsHARDWARE                        Able to be hosted on Navy fighter aircraft                                             - Ability to meet all functions/performance: (a) with minimal impact SWAP-C and processing resources of host platform (Threshold); within existing SWAP-C and processing resources of host platform (OBJ)CONTENT OF RFI RESPONSESystem Design/ArchitectureDiscuss how the DFS functionality is allocated to subsystems/sensors within the platform. Provide DFS architecture diagrams showing interfaces and dependencies.Detail the data sources and sensor data that the DFS can exploit. For example, track level kinematics, pulse level in quadrature (IQ), radio frequency (RF) parametrics, etc.  This should include kinematic, parametric and ID inputs and future growth for additional sensor inputs.Describe the data maintained per track fileInclude whether the DFS ingests track-level data, observation-level data, or both?Describe the architecture of the DFS with respect to:Modularity,Open Systems, etc.What common reference architecture do you have experience with (e.g., Open Mission Systems (OMS) standard)?Do you have Model Based System Engineering (MBSE) experience (e.g., SysML), and if so, describe?Explain the hardware/networking requirements (e.g., data size/rates, data buses, processing resources, memory).Discuss the ability to conduct distributed processing (e.g., data fusion for each sensor and allowing combined data fusion products at possibly another processing location).Explain how the DFS works in Air, Surface, and Ground environments.Explain how the DFS can be customized based on individual mission requirements (e.g., mission planning).Discuss how the DFS handles realistic sources (e.g., uncertainties, sensor starvation, false alarms, clutter).Explain how the DFS handles 2D or other non-3D kinematic measurements and track files.CommonalityDiscuss how data fusion products are shared and networking solutions among multiple participants.Include which datalinks the DFS supports.Discuss current or potential future system commonality among Navy, cross-service, and/or blue force participants.System IntegrationHas the DFS ever been integrated into a larger system (e.g., a mission system)? If so, discuss how it was achieved.Discuss whether the DFS is able to input, process, store, and/or output data at multiple DoD levels of security.If so, discuss how any cross-domain solutions, secure key management, encryption, were certified and integrated into the host platform.User Interface, Crew-system InteractionHow does the DFS integrate with and provide information via a crew vehicle interface?Provide graphics to show the user interface.Explain how/where the operator(s) can interact with the system and its decision-making.Explain any inclusion of Combat ID (CID) and/or Rules of Engagement (ROE).Were studies performed on reduction to aircrew workload and improved battlespace situational awareness?If so, provide Measure of Effectiveness or Measure of Performance used to assessTesting/ValidationProvide domains and scenarios where the DFS has been used/evaluated.Discuss scenarios that stressed the DFS, and performance resultsExplain how the DFS has been tested and evaluated, to include methodology and ideology behind metrics used. Include results of the testing.Describe modeling and simulation (M&S) capabilities used for testing and evaluation.Discuss any automated test capabilities as pertaining to:Unit, sub-system, and system testingMonte Carlo testingRegression testingResource ManagementAre there mechanisms within the DFS to support sensor prioritization logic? If so, please describe.Are there mechanisms within the DFS to support target prioritization schema/algorithms? If so, please describe.Are there mechanisms within the DFS to support single-platform and multi-platform resource management? If so, please describe.SECURITY AND SUBMISSION INFORMATIONThe Government anticipates a comprehensive response to this RFI may contain CLASSIFIED information. To the extent practical, responses should be UNCLASSIFIED, complemented by CLASSIFIED appendices as required. Parties interested in responding to the RFI must have a cover letter with the following additional data:CAGE codeRespondent business size status (large or small) for NAICS code 541511POC name and telephone number to contact for any necessary clarification, to receive additional information, for additional data required by the analysis, and for information on any necessary non-disclosure agreementsAnswers to the following questions:An UNCLASSIFIED description of the concept(s) for meeting the top level required system capabilities listed at the beginning of this RFIDescribe your company's ability to manage, secure and transmit information up to the level of classification requiredCompanies are to adhere to the National Industrial Security Program Operating Manual (NISPOM) procedures for the transmittal of classified responses. Company responses should clearly indicate the system(s) / technology area(s) addressed and include a one-page cover letter, and a three page (maximum) executive summary, with no limit on the detailed content. Companies are not limited to a single response.  Submissions are required no later than 30 days from RFI publication; any submissions after the 30 days may be considered upon notice to Mr. Hageman of intent of submission within the 30 day window. Unclassified data submissions shall be submitted either through email to Mr. Hageman or DoD SAFE [https://safe.apps.mil].  If submitters do not have a CAC to access the DoD SAFE site, they shall inform Mr. Hageman via email of their desire to submit via DoD SAFE and Mr. Hageman will send a Request for Drop-off via DoD SAFE to the submitter’s email address.  More information on DoD SAFE can be found at: https://public.cyber.mil/dcs/faqs/#toggle-id-2.Mr. Hageman's telephone is (240) 561-2527 and his email is nicholas.a.hageman.civ@us.navy.mil. Classified appendices (up to TS/SAR) shall be in compliance with current DoD directives and procedures.Address inquiries regarding submission of classified information to Michael Barnard (301) 757-7371 or Andrew Duley (301) 757-7370. DO NOT SEND ANY CLASSIFIED INFORMATION VIA UNCLASSIFIED EMAIL.As stated above, this is NOT a request for Proposal. THIS SYNOPSIS IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT, NOR WILL THE GOVERNMENT PAY FOR ANY INFORMATION SOLICITED OR PROVIDED.ADDITIONAL INFORMATIONThis RFI is an exchange of information between Government and Industry. It is the first step of an iterative process aimed at understanding the existence of DFS that can meet the need of the PMA. Additional RFIs requesting further detail may be issued in the future to continue the Government's informational exchange with Industry. Though government rights are preferred, information received as a result of this request that is sensitive and/or propriety to the responding company will be protected as such. Any proprietary information received in response to this request will be properly protected from any unauthorized disclosures; however it is incumbent upon the respondent to appropriately mark all submissions. The Government will not use any proprietary information submitted to establish the capability, requirements, approach, or solution so as to not inadvertently restrict competition. In order to complete its review, the Navy Program Office must be able to share the information within the Government and any responses marked in a manner that will not permit such internal Government review may be returned without being assessed/considered.POINTS OF CONTACTQuestions may be directed to the POC, Mr. Nick Hageman at (240) 561-2527 or via email to nicholas.a.hageman.civ@us.navy.mil or Ms. Marion Bronson-Cruce at (301) 757-6068 or via email to marion.e.bronson-cruce.civ@us.navy.mil at Responses to questions from interested parties will be answered as applicable.