Mission Data Interface: Difference between revisions

Revision as of 21:42, 30 September 2009

Revision as of 21:38, 2 October 2009

Line 1:

{{orphan|date=September 2009}}

{{deadend|date=September 2009}}

'''Mission Data Interface''' ('''MDI''') is a framework designed by the US Navy to allow mission data to be exchanged between systems within a [[battle group]]. MDI implements the FORCEnet (Fn) Functional Concept<ref>[http://forcenet.navy.mil/fn-definition.htm FORCEnet Definition<!-- Bot generated title -->]</ref> in accordance with the Navy [[Open architecture|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 carrierscarrier]]s. MDI was originally intended to extends the CVTSC/SSDS interaces 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 Navy 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 API ==