N211-074 TITLE: Efficient Data Management to Improve Navy Maintenance and Ship Operational Readiness
RT&L FOCUS AREA(S): Cybersecurity
TECHNOLOGY AREA(S): Information Systems
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 section 3.5 of 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 an efficient and secure data management software application to use Condition Based Maintenance (CBM) and Reliability Centered Maintenance (RCM) to sustain, maintain and modernize ships, aircraft carriers, and submarines.
DESCRIPTION: The Navy operates ships that are technologically advanced and dependent on the effective application of information. The Navy needs a data analytics system that provides real-time ship performance and component-level data to affordably sustain the Fleet. Integrating the two initiatives of monitoring ship performance and securely transmitting ship performance data promises to transform the conduct of maintenance and the relationship of the ship and the shipyard.
Comprehensive understanding of a ship’s current material condition is critical to maintenance performance. Traditionally, shipyard personnel assess the ship’s material condition through ship visits and ship checks, ship system logs, the Consolidated Ships Maintenance Plan, previous work packages of the ship and other ships in its class, along with other sources of maintenance information. Visits are performed during the planning phase through scheduled ship visits, and just prior to start of a planned maintenance availability. However, as a preparatory method for planning an availability, this is insufficient for preparing the shipyard when execution of the work package reveals unanticipated maintenance problems, which increases costs and delays in schedule.
The Navy needs a secure data management system to share performance data between ships at sea and shipyards. Ships, aircraft carriers, and submarines operating at sea produce a tremendous amount of information. CBM, as a predictive concept, utilizes engineered maintenance standards based on objective historical conditions and predicted failure windows in order to determine when a component is due for maintenance. There is a concern that CBM has gone too far and disrupted the shipyard’s ability to properly plan for large maintenance availabilities. In a data-managed environment, ship CBM and RCM parameters could technically flag ship system components based on performance criteria, generate lists of system and component status, generate prioritized task lists and automated work packages, and based on actual conditions, work lists could be generated and assigned to either the ship’s force or the shipyard. Where CBM and RCM is automated, maintenance in a continuum and planning for large maintenance availabilities could focus on delivering capability to the ship, modernizing systems, structures and conducting major upgrades and alterations.
The Navy is currently testing the Enterprise Remote Monitoring (ERM) System to monitor ship systems and components while at sea. In effect, it will function as a sensor that monitors and collects vital performance data on a ship’s hull, mechanical and electrical systems and components. When hosted in such a way as to securely transmit data, in effect, the operators are connected with the maintainers for continuous maintenance support anytime and anywhere. This specific effort looks to leverage the ERM by establishing an architecture option for a software solution or suite of software that orchestrates the movement and processing of the data in such a manner that it can be scaled to advance capabilities.
The secure sharing of performance data through the ERM between a naval shipyard and a ship will deliver enhanced capability, resources and life cycle support enabling the integration of advances in technology, and a continuous planning process that aligns the current material condition of the ship with the capabilities of the shipyard. In a future state, the Navy could expand its planning and execution capabilities through simulation in a digital environment using all available information to create an instance-based digital twin of the ship, enabled by its digital thread, a record of its life cycle support, and sustainment activities. A digital twin for a ship can help the shipyard community identify, plan, track and test its repair needs in advance of an availability.
The production solution should be able to meet security requirements consistent with the DoD Risk Management Framework at the appropriate level. See NIST SP 800-53 for detail requirements. If a cloud solution is used, the system must also meet the requirements of the DoD Cloud Computing Security Requirements Guide at Impact Level 4. It is not necessary to demonstrate compliance during the prototype effort; however, details of compliance capability should be provided in the deployment plan.
PHASE I: Define and develop a concept for secure sharing of ship performance data between naval shipyards and ships, aircraft carriers, and submarines using the Navy’s ERM System. The Phase I Option, if exercised, would include the initial layout and capabilities description to build a prototype in Phase II. Phase I testing should align with industry standards and best practices to ensure that investments drive value to the predictive maintenance community.
PHASE II: Based on the results of Phase I efforts and the Phase II Statement of Work (SOW), develop a prototype for testing and evaluating the primary source data from a naval vessel and transmitted to a naval shipyard. This source data is expected to be sensitive and or classified, varied in type, and centrally available for further analysis, model building and visualizations to determine ship material condition and optimize planning activities for an upcoming major availability. Data interoperability and portability testing could include reports showing how historical source data matches the transmitted data for expected results, and demonstrate capability to efficiently implement business process and/or spatial data models for at least one identified system or asset as a starting point for replicating the physical world.
PHASE III DUAL USE APPLICATIONS: Assist the Navy in transitioning the technology for Navy use by working closely with the Naval Research Lab (NRL), NAVSEA, PEO Ships, Submarines and Carriers, and the naval shipyards. Implement the prototype for a secure means of sharing component and ship system performance data. Scale the technology to meet the demands of the Navy and so it can collaborate the dual use nature of the data construct with Transportation and Logistics, Energy, Manufacturing, and Telecommunications industries who use predictive maintenance or remote asset monitoring.
KEYWORDS: Secure Data Management/Sharing; Condition Based Maintenance; Reliability Centered Maintenance; Digital Twin; Digital Threading; Ship maintenance information design.
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the overall DoD 21.1 SBIR BAA. Please see the official DoD Topic website at rt.cto.mil/rtl-small-business-resources/sbir-sttr/ for any updates.
The DoD issued its 21.1 SBIR BAA pre-release on December 8, 2020, which opens to receive proposals on January 14, 2021, and closes February 18, 2021 at 12:00 p.m. ET.
Direct Contact with Topic Authors: During the pre-release period (Dec 8, 2020 to January 13, 2021) 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 January 14, 2021 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, 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. Topic Q&A will close to new questions on February 4, 2021 at 12:00 p.m. ET
Note: Questions should be limited to specific information related to improving the understanding of a particular topic’s requirements. Proposing firms may not ask for advice or guidance on solution approach and you may not submit additional material to the topic author. If information provided during an exchange with the topic author is deemed necessary for proposal preparation, that information will be made available to all parties through SITIS. After the pre-release period, questions must be asked through the SITIS on-line system.
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.