<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Mission_Data_Interface</id>
	<title>Mission Data Interface - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Mission_Data_Interface"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Mission_Data_Interface&amp;action=history"/>
	<updated>2026-05-12T20:57:29Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://debianws.lexgopc.com/wiki143/index.php?title=Mission_Data_Interface&amp;diff=6339496&amp;oldid=prev</id>
		<title>imported&gt;GreenC bot: Rescued 1 archive link; reformat 1 link. Wayback Medic 2.5 per WP:URLREQ#navy.mil</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Mission_Data_Interface&amp;diff=6339496&amp;oldid=prev"/>
		<updated>2025-04-16T03:50:02Z</updated>

		<summary type="html">&lt;p&gt;Rescued 1 archive link; reformat 1 link. &lt;a href=&quot;/wiki143/index.php?title=User:GreenC/WaybackMedic_2.5&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;User:GreenC/WaybackMedic 2.5 (page does not exist)&quot;&gt;Wayback Medic 2.5&lt;/a&gt; per &lt;a href=&quot;/wiki143/index.php?title=WP:URLREQ&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;WP:URLREQ (page does not exist)&quot;&gt;WP:URLREQ#navy.mil&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;Mission Data Interface&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;&amp;#039;MDI&amp;#039;&amp;#039;&amp;#039;) 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&amp;lt;ref&amp;gt;[http://forcenet.navy.mil/fn-definition.htm FORCEnet Definition&amp;lt;!-- Bot generated title --&amp;gt;]{{dead link|date=April 2025|bot=medic}}{{cbignore|bot=medic}}&amp;lt;/ref&amp;gt; in accordance with the Navy [[Open architecture computing environment]] (OACE) specifications, with an emphasis on [[Service-oriented architecture|Service-oriented Architecture]] (SOA) design.&lt;br /&gt;
&lt;br /&gt;
== History ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
MDI contains 2 major API libraries: [[Remote Method Innovation|RMI]]-based API and web services-based API.{{cn|date=August 2019}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
{{refbegin}}&lt;br /&gt;
* NUWC Keyport MDI SRD/SDD document&lt;br /&gt;
* NUWC Keyport CV-TSC SARAD document&lt;br /&gt;
* FORCEnet. [https://web.archive.org/web/20081111175149/http://forcenet.navy.mil/]&lt;br /&gt;
{{refend}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--Categories--&amp;gt;&lt;br /&gt;
[[Category:Equipment of the United States Navy]]&lt;/div&gt;</summary>
		<author><name>imported&gt;GreenC bot</name></author>
	</entry>
</feed>