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
FORCEnet Definition
/ref> in accordance with the Navy Open architecture computing environment (OACE) specifications, with an emphasis on Service-oriented Architecture
In software engineering, service-oriented architecture (SOA) is an architectural style that focuses on discrete services instead of a monolithic design. SOA is a good choice for system integration. By consequence, it is also applied in the field ...
(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
An aircraft carrier is a warship that serves as a seagoing airbase, equipped with a full-length flight deck and hangar facilities for supporting, arming, deploying and recovering carrier-based aircraft, shipborne aircraft. Typically it is the ...
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 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 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: RMI-based API and web services-based API.
References
* NUWC Keyport MDI SRD/SDD document
* NUWC Keyport CV-TSC SARAD document
* FORCEnet
{{refend
Equipment of the United States Navy