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.
MDI connectivity, functionality, and architecture features directly supports integration and inter-working for generic sensor/platforms (non-combat, non GSSC/M) including AT/FP applications, early adoption and/or bridging of the legacy SQQ-34B with the up-coming 34C variant, and provides a platform for CVTSC and DSS integration IAW C3S goals. It also provides an efficient mechanism to import/export data to consumers such as the Fleet ASW command, Advanced Battle Station (ABS), Quiet Interlude Processing (QUIPS), and others.
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.
Technical Details
MDI was designed as part of an N-tier architectures, in which a software components are designed and organized in separate tiers: External Interface tier (EX_tier), Domain Server tier, Data Processing tier, and Representation tier.
Software components within EX_tier mostly interacts with external systems for data transfering
Software components within Domain Servers manages various data types: track, tactical decision aids (TDAs), contacts, detection reports, etc.
Software components within Data Processing tier performs various analyis and data processing tasks.
Software components within the Presentation tier display data
MDI software components are mostly in the EX_tier, and interact with software components in the Domain Server tier and the Data Processing tier.
MDI API
MDI contains 2 major API libraries: RMIRemote Method Innovation-based API, and web services-based API.
Using the RMI-based API, software developers implments a set of predefined interfaces that allow them to connect directly to various domain servers: Track Server for track data, TDA server for TDA data, etc.
MDI WS API contains software components that accept and process SOAP messages for the following functionalities: 1. Register as data producer 2. Subscribe for data 3. Query data
References
- NUWC Keyport MDI SRD/SDD document
- NUWC Keyport CV-TSC SARAD document
- FORCEnet. [[1]]