Mission Data Interface

This is a Wikipedia user page.
This is not an encyclopedia article or the talk page for an encyclopedia article. If you find this page on any site other than Wikipedia, you are viewing a mirror site. Be aware that the page may be outdated and that the user whom this page is about may have no personal affiliation with any site other than Wikipedia. The original page is located at https://en.wikipedia.org/wiki/Mission_Data_Interface.

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^[1] in accordance with the Navy Open Architecture Computing Environment (OACE) specifications, with an emphasis on 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 carriers. 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 battle space in 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

MDI contains 2 major API libraries: RMIRemote Method Innovation-based API, and web services-based API.

underconstruction

References

NUWC Keyport MDI SRD/SDD document
NUWC Keyport CV-TSC SARAD document
FORCEnet. [[1]]

^ http://forcenet.navy.mil/fn-definition.htm

[1] ttp://forcenet.navy.mil/fn-definition.htm

[1]