OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Advanced Computing and Software 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 non-traditional capabilities where data can be represented in a structured natural language rather than extraneous languages like SQL, XML, JSON, RDF, and the like to democratize data such that custody is maintained by operators. DESCRIPTION: The Maritime Tactical Command and Control (MTC2) system is the Navy's next generation command and control platform providing modernized, robust, secure, integrated, and interoperable network-centric capabilities. MTC2 will replace the legacy planning, introduce new decision aid systems, and provide a Common Operational Picture (COP) in a geospatial display to visualize an operational environment to maintain Command and Control (C2) Situational Awareness (SA) and understanding in realtime. The Command and Control Acquisition Program Office, PMW 150, currently fields MTC2 supporting planning and decision analytics for developing a Joint Integrated Command and Control (JIC2) in support of Fires. Data is a warfighting asset. Converting data into information that informs warfighters is a critical enabler in the ability to fight and win. Achieving data dominance requires new thinking and methods to process and represent data in a way that quickly creates understanding. Data needs to evolve from standards-based schemas, which are Information Technology (IT) assets, to a dynamic representation expressed in a universal, human, and machine-readable schema-less form for all types of data, including Over-The-Horizon Targeting GOLD (OTH-Gold), AIS, Modernized Integrated Database (MIDB), Military Equipment and Parametrics Engineering Database (MEPED), Optimized Organizational Maintenance Activity/Naval Research & Development (OOMA/NARD), AEGIS Combat System, United States Marine Corps (USMC) and United States Army (USA) ground systems, and United States Navy (USN), USMC, USA, and United States Air Force (USAF) aircraft. Data must be a collection of facts, able to be individually disseminated across networks, and immutable when stored in repositories. MTC2 requires the development of a robust technology supporting both geospatial and non-geospatial data for not only display of the COP, but to also inform analytics. The current technology is extremely dated and only provides tracks on a map for viewing with some overlays. Modern, state-of-the-art technologies are providing greater depth, analysis, interpretation, and understanding for the warfighter. MTC2 also requires greater speed of analysis in support of Kill Chain requirements for greater assessment of the environment, positive Identification of threats, and predictive capability to meet growing threat challenges in theater. To meet these growing demands, the development of robust technologies for smart geospatial analytics and the use of modern and non-traditional low code/no code data analytics is needed. Key capabilities and use cases must include: Ability to represent any kind of data, associations, and structures in a restricted natural language A client application to be used by warfighting operators, with low and no-code customization Realtime fact routing and processing capability for applications including: o Near-realtime platform and weapons suitability determination o Track management and analysis including geo-fencing, routing and association between applications and services o Artificial Intelligence/Machine Learning (AI/ML) and graph-based analytics These analytics will feed into an Optimization stack supporting realtime decision aids and COP representation for the warfighter, headed by the Maritime Tactical Command and Control (MTC2) system. 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 32 U.S.C. 2004.20 et seq., National Industrial Security Program Executive Agent and Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Counterintelligence and Security Agency (DCSA) formerly Defense Security Service (DSS). The selected contractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances. This will allow contractor personnel to perform on advanced phases of this project as set forth by DCSA and NAVWAR 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 during the advanced phases of this contract IAW the National Industrial Security Program Operating Manual (NISPOM), which can be found at Title 32, Part 2004.20 of the Code of Federal Regulations. PHASE I: For a Direct to Phase II topic, the Government expects that the small business would have accomplished the following in a Phase I-type feasibility effort: developed a concept for a workable prototype or design to address, at a minimum, the basic requirements for enhanced language-oriented data for track management and data analytics. FEASIBILITY DOCUMENTATION: Offerors interested in proposing to this Direct to Phase II topic must include in their response Phase I feasibility documentation that substantiates the scientific and technical merit; proof that Phase I feasibility (described in Phase I above) has been met (i.e., the small business must have performed Phase I-type research and development related to the topic, but feasibility documentation must not be solely based on work performed under prior or ongoing federally funded SBIR/STTR work.); and describe the potential commercialization applications. The documentation provided must validate that the proposer has completed Phase I-type development of technology as stated above. Documentation should include all relevant information including, but not limited to: technical reports, test data, prototype designs/models, and performance goals/results. Work submitted within the feasibility documentation must have been substantially performed by the offeror and/or the principal investigator (PI). PHASE II: Develop a software prototype that is capable of ingesting various data sources and types, including textual and abstract such as Joint Message Handling System (JMHS) for textual and map representations for abstract data types; to include geospatial and non-geospatial; and evaluate the data with algorithms identified in Phase I or equivalent efforts. Ensure that the software prototype is deployable and used for concept validation, allowing users to interact under operational condition. Ensure that the prototype runs in a DEVSECOPS environment, gathering data from the users to feed into requirements for the Program of Record to validate concepts. Implement source data representations that can assess renderings, formulate understanding, and provide the information directly to the user. Investigate themes like fact-oriented formatting for incorporating attribute and computed values within filter criteria. Provide dynamic filtering and linkback to external data sources, and automated drill down and queries based on user history. This fact-oriented data format will be agnostic to the type of DB technologies used to repose the data (e.g., flat files, relational DBs, big data, noSQL, and graph datastores). Facts must include descriptive phrases that can be browsed as indexes (e.g., in a book), and as graphical views like trees or word clouds, to enable operators to discover and directly interact with the data. In other words, data itself should be a user-interface, allowing operators to dynamically enrich data by adding tags to facts or writing new facts, e.g., annotations descriptive of status, provenance, pedigree, validity, ontological references, or references back to the origination schema it was extracted from. 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: Conduct further testing of the prototype on experimentation venues, such as Trident Warrior. Integration will be conducted by NIWC Pacific/Atlantic engineers. Initially, the technology will reside in the C2X environment being developed and fielded for test and evaluation. Once testing is completed, integrate the technology into the existing MTC2 Configuration Management (CM) environment for inclusion in the MTC2 normal release update schedule to provide the warfighter the capability to have information analyzed continuously as the representation changes in the COP. The Enhanced Language Oriented Data for Track Management and Data analytics will provide significant increase in speed of understanding and will allow decisions to be more informed and analyzed to support the Kill Chain process. Commercially, these capabilities can be applied to current Geospatial Information Systems (GIS) and decision analytics to increase capability for industry use. REFERENCES: 1. NWP 3-56 COMPOSITE WARFARE: MARITIME OPERATIONS AT THE TACTICAL LEVEL OF WAR. https://apps.dtic.mil/dtic/tr/fulltext/u2/a575608.pdf 2. NTTP 3-32 Navy Tactics Techniques and Procedures. www.navybmr.com/study material/NTTP_3-32-1_MOC_(Apr_2013).pdf 3. NWP 3-32 MARITIME OPERATIONS AT THE OPERATIONAL LEVEL OF WAR. https://docplayer.net/44980043-Maritime-operations-at-the-operational-level-of-war-nwp-3-32.html 4. JP 3-32 COMMAND AND CONTROL FOR JOINT MARITIME OPERATIONS. https://fas.org/irp/doddir/dod/jp3_32ch1.pdf 5. JP 3.0 DOCTRINE FOR JOINT OPERATIONS. https://docplayer.net/17806770-Joint-publication-3-0-doctrine-for-joint-operations.html 6. National Industrial Security Program Executive Agent and Operating Manual (NISP), 32 U.S.C. 2004.20 et seq. (1993). https://www.ecfr.gov/current/title-32/subtitle-B/chapter-XX/part-2004 KEYWORDS: Geospatial; analytics; Artificial Intelligence; AI; Machine Learning; ML; Enhanced situational awareness; SA; comparative analysis; Common Operational Picture; COP; Maritime Operations
