Model Based Systems Engineering for Tactical Data Link Systems

Navy SBIR 20.2 - Topic N202-135

Naval Information Warfare Systems Command (NAVWAR) - Mr. Shadi Azoum [email protected]

Opens: June 3, 2020 - Closes: July 2, 2020 (12:00 pm ET)



N202-135       TITLE: Model Based Systems Engineering for Tactical Data Link Systems


RT&L FOCUS AREA(S): Microelectronics, General Warfighting Requirements (GWR)

TECHNOLOGY AREA(S): Information Systems, Materials, Electronics


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 and demonstrate ability to identify, aggregate, and analyze distinct data types and formats to enhance the decision-making process during the technology assessment and trade-offs, design, development, testing, and qualification phases of tactical data link systems using Model Based Systems Engineering (MBSE).


DESCRIPTION: The goal of this SBIR topic is to develop a Systems Modeling Language (SysML) digital twin system model of the Multi-Functional Information Distribution System (MIDS) Joint Tactical Radio System (JTRS) terminal configurations. The MIDS Program Office (MPO) is interested in significantly improving and expanding its engineering support infrastructure to enable deployment of more efficient, agile, and resilient tactical data links systems models to expedite capability to the fleet. The MPO intends to implement a Model-Based System Engineering approach for all engineering activities that uses models as an integral part of the technical baseline including requirements generation and validation, analysis, technology trade-offs, design,� implementation, and verification of a capability, system,� product and/or technology throughout the acquisition lifecycle. A model-based system will enable unprecedented levels of systems understanding that can be achieved through integrated analytics, tied to a model-centric technical baseline and will support new DoD acquisition initiatives to expedite warfighting capabilities to the fleet [Refs 1, 2, 3].


Implementing this type of capability would expedite correlation of relevant technical data, software, information, knowledge and technology trade-offs to enhance tactical data link development. This environment would provide substantial acceleration of development of solutions and technology transition resulting in reduced time and significant cost reduction of critical capabilities to the warfighter.


Work produced in Phase II will likely 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 and Security Agency (DCSA). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order 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 IAW DoD 5220.22-M during the advanced phases of this contract. NAVWAR will process the DD254 to support the contractor for personnel and facility certification for secure access.


PHASE I: Define solution(s) to develop digital twin system model of the MIDS JTRS terminal configuration. Outline model elements, including characterizing behavior, structure, requirements, and parametrics, that further refine trades in developing tactical data link systems. Solution must specify data storage and computational requirements and will identify existing DoD capabilities that may contribute to the desired end-state capability, identify capability gaps and establish a methodology to deliver needed capability. Information absorption and temporal requirements will be baselined during Phase I. Propose model simulations are strongly encouraged and could take several forms such as augmentations/plug-ins to existing SySML tools. Partnership with MIDS prime vendors is encouraged to help understanding of MIDS design and potential models they use. Partnership with NAVWAR 5.0 Digital Engineering Transformation Division is encouraged. Phase I will be UNCLASSIFIED, and the contractor will not require access to any classified data. Develop a Phase II plan.


PHASE II: Develop a prototype model based on the learning of Phase I effort. Validate and demonstrate the proposed data analytic capability leveraging existing DoD tactical data link infrastructure. Demonstrate the prototype system using MBSE tools identified in Phase I. Include, at a minimum, demonstration of a prototype tool or methodology on a small system(s) application that is representative of a portion of the tactical data link infrastructure, and documentation describing anticipated use of the tool. Ensure model adherence to SysML and Unified Architecture Framework (UAF) specifications, as well as eXtensible Markup Language (XML) Metadata Interchange (XMI) Standard, is desired. Endstate should ensure model can be used to inform tactical data link analysis including (but not limited to) requirements, impact, trade-off, behavior, interoperability or data flow.


The expected TRL for this project is 5 to 6. Partnership with MIDS prime vendors is encouraged, but not required. Partnership with NAVWAR 5.0 Digital Engineering Transformation Division is encouraged.

It is likely that the work under this Phase II effort will be classified (see Description section for details). Though Phase II work may become classified, the proposal for Phase II work will be UNCLASSIFIED. If the selected Phase II contractor does not have the required certification for classified work, the related DON program office will work with the contractor to facilitate certification of related personnel and facility.


PHASE III DUAL USE APPLICATIONS: Mature the model and extend use to multiple data link centric platforms within the Navy and private sector. Support or license the final product (s) and transition to the Government. The technology will have application throughout government and industry. Performers from component developers (e.g., Intel, Texas Instrument, etc.) to system integrators (e.g., LM, Boeing, BAE, etc.) could use these models to reduce costs in data link development. Partnership with prime vendors is encouraged, but not required. Navy seeks selected vendor to support transitioning of MBSE solution(s) across the Services.



1. Shortell, Thomas M., editor. �INCOSE Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities 4th Ed.�


2. Office of the Deputy Assistant Secretary of Defense for Systems Engineering. �Best Practices for Using Systems Engineering Standards on Contracts for DoD Acquisition Programs.� April 2017.


3. Kobryn, P., Tuegel, E., Zweber, J., and Kolonay, R. �Digital Thread and Twin for Systems Engineering: EMD to Disposal.� 55th AIAA Aerospace Sciences Meeting, 9-13 January 2017, p. 11. Wang, Gang, et al. "Big data analytics in logistics and supply chain management: Certain investigations for research and applications." International Journal of Production Economics 176, 2016, pp, 98-110.


KEYWORDS: Model Based Systems Engineering, MBSE, SysML, Digital Twin, Tactical Data Links, MIDS, XMI



The Navy Topic above is an "unofficial" copy from the overall DoD 20.2 SBIR BAA. Please see the official DoD DSIP Topic website at for any updates. The DoD issued its 20.2 SBIR BAA on May 6, 2020, which opens to receive proposals on June 3, 2020, and closes July 2, 2020 at 12:00 noon ET.

Direct Contact with Topic Authors. During the pre-release period (May 6 to June 2, 2020) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic.

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 (SBIR/STTR Interactive Topic Information System). After the pre-release period, questions must be asked through the SITIS on-line system as described below.

SITIS Q&A System. Once DoD begins accepting proposals on June 3, 2020 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. However, proposers may submit written questions through SITIS at, 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 to find topics by keyword across all DoD Components participating in this BAA.

Help: If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at 703-214-1333 or via email at [email protected]