Mission Data Interface: Difference between revisions

Revision as of 06:26, 11 August 2019

Latest revision as of 03:50, 16 April 2025

(2 intermediate revisions by 2 users not shown)

Line 1:

'''Mission Data Interface''' ('''MDI''') is a framework designed by the US Navy to allow mission data to be exchanged between systems within a [[Battlegroup (army)|battle group]]. MDI implements the FORCEnet (Fn) Functional Concept<ref>[http://forcenet.navy.mil/fn-definition.htm FORCEnet Definition<!-- Bot generated title -->]{{dead link|date=February 2018April 2025|bot=InternetArchiveBot medic}}{{cbignore|fix-attemptedbot=yes medic}}</ref> in accordance with the Navy [[Open architecture computing environment]] (OACE) specifications, with an emphasis on [[Service-oriented architecture|Service-oriented Architecture]] (SOA) design.

== History ==

Mission Data Interface (MDI) is a spin-off project from the [[Aircraft Carrier Tactical Support System]] (CVTSC) system -– which is installed on all current deployed US [[aircraft carrier]]s. MDI was originally intended to extend the CVTSC/SSDS interfaces to share mission data with other remote battle group and theater-level (WAN internet scale) participants configured with the MDI capability. Mission data are all data generated during a mission, including electrical notes, commands, and even operator views. These data can be share among all systems within the [[Battlespace|battle space]] in [[Near real time|near real-time]]; as well as recorded for post-mission analysis and training. The proposal to establish the MDI project was submitted to [[Naval Undersea Warfare Center]] (NUWC) Keyport management sometime in late 2004. The project was approved by IWS5 Program Office and work started sometime in 2005.

MDI contains 2 major API libraries: [[Remote Method Innovation|RMI]]-based API and web services-based API.{{cn|date=August 2019}}

== References ==