N231-055 TITLE: Centralized Automated Fault Monitoring
OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Autonomy;Networked C3
The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.
OBJECTIVE: Develop a centralized automated fault monitoring system capable of integrating sensor and fault data across ship systems to provide a holistic view of current faults across various ship systems to enable fault management, response, and understanding of the impact on mission readiness.
DESCRIPTION: Current technology informs ship watchstanders of faults and alarms from various control systems throughout the ship. However, watchstanders must interpret multiple alarms and determine the impact to ship systems, the ship as a whole, and the impact to overall mission effectiveness. A fault monitoring capability to aggregate system data into a user interface, allowing for complete ship fault monitoring, will reduce the burden on the crew and provide increased situation awareness to the watchstander.
PMS 515, FFG 62 Constellation Class Program Office, seeks a centralized automated fault monitoring capability to integrate numerous ship systems providing data and alarm inputs in order to improve the crew�s situational awareness of overall ship status and mission effectiveness. By aggregating all faults into one common structure and platform level system, the cognitive load on the operator can be decreased and the ability to make data-driven decisions based on complex information will be greatly improved.
The centralized automated fault monitoring system will receive various ship systems� fault data and sensor outputs and convert them into a human-readable and intuitive User Experience (UX) to provide an aggregate viewpoint of the overall ship system and platform health. This will enable operators to visualize the mission impact of various faults and alarms on ship control systems (e.g., up/down, failure mode, performance). The centralized automated fault monitoring system should categorize and prioritize alarm information with the goal of displaying compiling, automating, and reducing burdens on the watchstanders to assist with understanding the influence a component alarm has on the overall mission effectiveness of the system.
The centralized automated fault monitoring system must be capable of collecting, integrating, and displaying data from all ship control systems and must include an interface to support data export. This will enable data analysis by watchstanders in real time as well as evaluation by the Program Office, In-Service Engineering Agents (ISEAs)s, and subject matter experts. The system will also inform maintenance and logistical requirements. Proposers should develop a solution that is Modular Open Systems Approach (MOSA) compliant to allow for cross-platform compatibility and future capability improvements. Because of the unique and specific nature of the multiple FFG 62 subsystems, of which data will be collected, there are currently no commercial solutions to allow for subsystem data integration and/or data exportation. Testing will be iterative throughout the phases in order to test accurate data consolidation, user experience, and secure cyber footprint. This solution must have the ability to achieve Navy accreditation and certification in order to be installed on an operational vessel in accordance with the latest guidance including, but not limited to, Authorization to Operate and Risk Management Framework policies.
Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. Owned and Operated with no Foreign Influence as defined by DOD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Counterintelligence Security Agency (DCSA), formerly the Defense Security Service (DSS). The selected contractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this contract as set forth by DCSA and NAVSEA in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material IAW DoD 5220.22-M during the advance phases of this contract.
All DoD Information Systems (IS) and Platform Information Technology (PIT) systems will be categorized in accordance with Committee on National Security Systems Instruction (CNSSI) 1253, implemented using a corresponding set of security controls from National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, and evaluated using assessment procedures from NIST SP 800-53A and DoD-specific (KS) (Information Assurance Technical Authority (IATA) Standards and Tools).
The Contractor shall support the Assessment and Authorization (A&A) of the system. The Contractor shall support the government�s efforts to obtain an Authorization to Operate (ATO) in accordance with DoDI 8500.01 Cybersecurity, DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT), NIST SP 800-53, NAVSEA 9400.2-M (October 2016), and business rules set by the NAVSEA Echelon II and the Functional Authorizing Official (FAO). The Contractor shall design the tool to their proposed RMF Security Controls necessary to obtain A&A. The Contractor shall provide technical support and design material for RMF assessment and authorization in accordance with NAVSEA Instruction 9400.2-M by delivering OQE and documentation to support assessment and authorization package development.
Contractor Information Systems Security Requirements. The Contractor shall implement the security requirements set forth in the clause entitled DFARS 252.204-7012, "Safeguarding Covered Defense Information and Cyber Incident Reporting," and National Institute of Standards and Technology (NIST) Special Publication 800-171.
PHASE I: Develop a concept for an automated fault monitoring system that integrates data from numerous ship systems with an ability to assess the faults and alarms� impact to the ship�s mission readiness. The concept must show that it can feasibly meet the requirements of the Description. Feasibility shall be established through modeling and simulation of concept.
The Phase I Option, if exercised, will include the initial design specifications and capabilities description to build a prototype solution in Phase II.
PHASE II: Based on the results of Phase I and the Phase II Statement of Work (SOW), generate system architecture diagrams that provide a high-level, and detailed system design as well as develop a comprehensive automated fault monitoring prototype that is capable of demonstrating the implementation and integration into the ship systems� environment for testing and evaluation. Demonstrate the technology�s accuracy, repeatability, and functionality, adhering to the requirements outlined in the Description. Perform a system demonstration in a simulated environment. Prepare a Phase III development plan to transition the technology to Navy use.
It is probable that the work under this effort will be classified under Phase II (see Description section for details).
PHASE III DUAL USE APPLICATIONS: Support the Navy in transitioning the technology to Navy use and support further refinement and testing of the centralized automated fault monitoring system�s functionality following successful prototype development and demonstration. Testing will be accomplished by real-time demonstration of the developed capability with operational users in order to gauge successful metrics for accuracy, readability, and implementation of data feeds into a singular location/user interface and mission impact analysis. Support the Navy for test and validation to certify and qualify the system for Navy use.
This solution has applicability across the Navy on most if not all platforms with complex/automated ship control systems. This technology has the potential to increase both mission effectiveness and readiness of the Navy�s Fleet. This capability can be applied to commercial applications with multiple diverse and complex systems, including aviation and commercial maritime operations.
1. Zeng, Zhiwei, Heng Zhang, and Qiang Miao. "Analytical Model Based Fault Diagnosis of Complex System: A Review." 2021 International Conference on Sensing, Measurement & Data Analytics in the era of Artificial Intelligence (ICSMD). IEEE, 2021. https://ieeexplore.ieee.org/document/9670860
2. Salahshoor, Karim, Mohsen Mosallaei, and Mohammadreza Bayat. "Centralized and decentralized process and sensor fault monitoring using data fusion based on adaptive extended Kalman filter algorithm." Measurement 41.10 (2008): 1059-1076. https://www.academia.edu/24261328/Centralized_and_decentralized_process_and_sensor_fault_monitoring_using_data_fusion_based_on_adaptive_extended_Kalman_filter_algorithm
KEYWORDS: Fault monitoring; automated fault impact assessment; integrated alarm data; network fault management; centralized system data; multi-sensor data fusion
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 23.1 SBIR BAA. Please see the official DoD Topic website at www.defensesbirsttr.mil/SBIR-STTR/Opportunities/#announcements for any updates.
The DoD issued its Navy 23.1 SBIR Topics pre-release on January 11, 2023 which opens to receive proposals on February 8, 2023, and closes March 8, 2023 (12:00pm ET).
Direct Contact with Topic Authors: During the pre-release period (January 11, 2023 thru February 7, 2023) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on February 8, 2023 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period.
SITIS Q&A System: After the pre-release period, and until February 22, 2023, (at 12:00 PM ET), proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/, login and follow instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
Topics Search Engine: Visit the DoD Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoD Components participating in this BAA.
|2/21/23||Q.||Do we assume that the data from these instruments will somehow have digital data (ex. API or data feed) that our solution can plug into? or are they analog?|
|A.||It is assumed that the data will be digital via data feed/API.|
|2/7/23||Q.||Who is the prime integrator with whom we would work?|
|A.||The shipbuilder is Fincantieri Marinette Marine.
|2/7/23||Q.||Will all control systems have repeater/control stations in one central location (i.e., engineering, combat, etc)?|
|A.||It�s envisioned that there would likely be a small number of central locations.
|2/7/23||Q.||May we have sample data to examine?If not, may we have a list of data types relating to the operation of planned systems?|
|A.||We can provide some information on data types during Phase I.
|2/7/23||Q.||May we have a list of control systems planned for the Constellation Class FFG? If not, may we have a rough number and types of control systems that will be used?|
|A.||I don�t know if I understand this question fully. HM&E equipment will be managed by Machinery Centralized Control System. The combat system is Aegis Combat System. The C4I network is CANES.