Unmanned Maritime Autonomy Architecture (UMAA) Compliant Software

INTRODUCTION This Request For Information (RFI) is issued by the Department of the Navy, Naval Sea Systems Command, Program Office Executive Office Unmanned and Small Combatants, Unmanned Maritime System Office (PMS 406). PMS 406 is continuing development of the autonomy software services and the componentization of those service definitions in SysML using a model-based systems engineering (MBSE) methodology. Capturing the Unmanned Maritime Autonomy Architecture (UMAA) compliant component definitions within an MBSE environment will enable the integration of components into a modeled Unmanned Vehicle (UxV) architecture, and traceability to autonomy capabilities that are refined by user stories, use cases, or other requirements analysis tools. The intent is to develop a standard MBSE product that can be delivered as a part of the UMAA standard to increase the understanding of capability delivery, gaps, and overlaps. Components are defined such that they facilitate scalable modularity of payload or autonomy implementations through development of common service-oriented interfaces and scope of function. The Government's intent is that a component is the Lowest Replaceable Unit (LRU) of autonomy software. The goal is to reduce UxV lifecycle costs, by improving the ability to conduct technology insertion, refresh, and integration for critical maritime autonomy components. Well-defined components and their associated specification should enhance UxV mission competency by accelerating development, certification, and integration of targeted capabilities. The Government is requesting feedback on the current identified components and service interfaces for both USV and UUV operations. The use cases defined in the MBSE model are a representation of both basic USV and UUV capabilities and provide initial traceability to components which is not a total USV and UUV platforms representation. The initial MBSE model, a summary table of the defined components and service interfaces, and component definition documents generated from the MBSE model have been provided via this RFI. When component definitions are combined with specific performance requirements and metrics, the result is an autonomy software component specification. The Government intends to use software component specifications to compete UMAA compliant individual autonomy components, capabilities, and/or operational activities to industry. REQUEST FOR INFORMATION The Navy is requesting feedback regarding UMAA compliant software component definitions and their service interfaces, to include identifying areas that require additional development for USVs and UUVs. One goal is to have commonality across domains to promote component re-use. The response to this RFI shall include: Feedback on the component definitions and service interfaces, to include any omitted components and services interfaces. Feedback on the appropriate resolution of component(s), given that a component should be the LRU (i.e. should the component(s) be further decomposed or should components be combined?). Description of your existing capabilities and if they use a modular open system architecture, such as UMAA. Include information on if your existing capabilities map to the defined component descriptions and service interfaces. Description of the extent to which your organization uses MBSE tools to capture and document design information as part of its digital engineering process. The complete RFI posting contains controlled technical data that cannot be posted to the Government Point of Entry. Respondents should contact the listed NAVSEA Contracting Officer and Contract Specialist via e-mail for questions and additional information marked as Distribution D (i.e., distribution authorized to Department of Defense and U.S. DoD contractors only). This email should include, at a minimum, the following: A request for access to the - Industry Feedback on UMAA Components reference documents; Company name, address, and ZIP code; Company cage code; Cognizant Defense Security Service (DSS) Security Office name, address, and Zip code; Company Website; Two points of contact with name, title, phone number, and e-mail address; and A completed Terms of Use Agreement, which is included as an attachment to this RFI. INSTRUCTIONS Any responses, questions and/or comments/feedback to the Component Definitions and MBSE model are encouraged. All responses should be UNCLASSIFIED. Requested format for submissions are a white paper similar narrative (company's format) and optional SysML model (limited to containing populated versions of provided templates only using company's style guide). Document-based portions of submissions shall be type-written for clarity in Microsoft Word or searchable Adobe Acrobat Portable Document Format (PDF) and no more than 20 (twenty) pages. Preferred model-based portions of the submissions shall be submitted in native Cameo Systems Modeler/NoMagic format (.mdzip) or respondent's format choice. This RFI response feedback, questions and/or comments are due via email no later than 30 calendar days from receipt of the GFI to the Contract Specialist, Lee Ryan at lee.f.ryan.civ@us.navy.mil and the Contracting Officer, Daniel Magrino at daniel.k.magrino.civ@us.navy.mil. DISCLAIMER AND IMPORTANT NOTES: Respondents are advised that Booz Allen Hamilton, Johns Hopkins University Applied Physics Laboratory, and Applied Research Laboratory Pennsylvania State University (the contractors) may assist the Government in its review of responses received under this notice. Respondents shall provide notification on its cover page if the respondent does not consent to the disclosure of materials submitted in response to this notice to the aforementioned contractors. Unless otherwise noted on the cover page by the respondent, submitting materials in response to this notice constitutes consent that the Government may disclose such materials to the aforementioned contractors, and that the aforementioned contractors may access such materials, for the purposes of reviewing the materials in support of Government requirements. This notice is not a request for proposals and is not to be construed as a commitment by the Government to issue a solicitation; it does not constitute a solicitation or a promise to issue a solicitation in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Further, the Navy is not at this time seeking proposals and will not accept unsolicited proposals. This notice does not obligate the Government to award a contract or otherwise pay for the information provided in response. The technical data provided for this RFI is preliminary and does not reflect approved Government specifications. The Government will not reimburse the cost of any submission or other expense in response to this RFI - the entire cost of any submission or other expense will be at the sole expense of the source submitting the information. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. Respondents will not be notified of the results of this notice. The information obtained from submitted responses may be used in development of a future solicitation. Failure to respond to this RFI does not preclude participation in any future solicitation, if any is issued. If a solicitation is issued, it will be synopsized on the System for Award Management (SAM) website at https://www.sam.gov. The information provided in this RFI is subject to change and is not binding on the Government. It is the responsibility of potential respondents to monitor these sites for additional information pertaining to this requirement. The information requested by this RFI will be used within the U.S. Navy to facilitate decision making and may be used in the development of the acquisition strategy and any future RFPs. The Government reserves the right to use information provided by respondents for any purpose deemed necessary and legally appropriate. Any information provided by industry to the Government as a result of this RFI is voluntary. Proprietary information, if any, must be clearly marked. To aid the Government in its review and evaluation, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. Respondents shall mark any data included in its submissions that they do not want disclosed to the public for any purpose.