MIDB is a DOD migration system. The DoD is in the process of establishing a simplified baseline of the best, common information systems across the business functions of the Department. These migration systems represent a stage of process improvement designed at achieving a common set of automated processes and practices in DoD. MIDB expanded upon the basic order of battle, equipment and facility holdings of the Integrated Data Base (IDB) to include several legacy systems:
This project also provides, for the first time, a common database architecture between the national database MIDB and the service tactical systems of the Navy’s Joint Maritime Command Information System (JMCIS), Air Force’s CIS and the Marine Corps’ Intelligence Analysis System (IAS) taking migration to a higher plateau. MIDB is also providing segmented software for compliance with the Defense Information Infrastructure Common Operating Environment (DII COE), and integration of the Joint Mapping Tool Kit (JMTK) mapping migration system.
MIDB is migrating away from a mainframe environment as Version 1.0 was fielded, and the IDB mainframe was shutdown with the release of Version 2.0. Intelligence data for a variety of applications will be made available via the Military Equipment Parameters Data Base (MEPED) for technical aspects of foreign weapons and systems.
The first step in the transitioning eXtended Integrated Data Base (XIDB) to MIDB was a merger of the data base schemas and functionality of XIDB and the Military Intelligence Information Processing System (MIIPS). This initial version of MIDB includes the intelligence production and data exchange capabilities of XIDB and data retrieval functions from MIIPS. However, this version of MIDB lacks the complete suite of required capabilities. Therefore, MIDB Version 2.0 is planned to address these legacy system shortfalls.
MIDB is the core military intelligence data system, consisting of several distributed databases and applications. Among the major tasks of the MIDB is the integration of various types of intelligence data (such as text, images and maps) in a representation that is transparent to the analyst. Current implementations force analysts to query disparate databases to form a comprehensive overview. With MIDB analysts would access the full range of information from a single the desktop interface.
The Common Object Request Broker Architecture (CORBA) is a set of commercial specifications produced by the Object Management Group, a consortium of industry, government and academic hardware and software interests. CORBA specifications are consistent with the current DoD Technical Architecture Framework for Information Management (TAFIM) standards framework. CORBA-based applications are defined by objects that can alternate between client and server roles. CORBA is hardware, operating system and programming language independent; interoperable, and interchangeable. The intelligence community is adopting a TAFIM-based SQL implementation by specifying common schema for common entities in different databases, each with unique SQL scripts. CORBA integrates such legacy systems by creating object wrappers that seamlessly integrate these various data formats while hiding the details from client applications.
One example of this integration is the Modernized Integrated Database Imagery Product Archive / Imagery Product Library for the Global Command and Control System [MIG] at the Air Force's Defense Information Systems Agency's Pentagon facility. The MIG provides near real-time display of the locations of friendly, neutral, and enemy ground, maritime, and air units on a map on a GCCS terminal with applicable overlay enhancements. Commanders are able to see representations of the data and can support mission execution without requesting situational information.
Typical MIDB products and outputs include:
However, a range of MIDB implementation questions remain unresolved. The 2.0 design has raised some concerns among developers, particularly with the issue of system performance.
GCCS-M Intel capabilities will be affected by the recent DIA-MIDB Category changes. Particularly, Defensive Missile Order of Battle cat codes will be changed. GCCS-M applications that access, display, and disseminate MIDB data must be changed to properly and accurately handle this change. SPAWAR has developed and thoroughly tested the fix to these applications and is in the process of distributing to current GCCS-M users. Not applying this change will result in an inability to process MIDB updates and exchange threat data among GCCS-M users and systems it interfaces with, e.g., TAMPS. The GCCS-M Common build for fleet release in the summer of 1999 included the modifications necessary to accommodate DIA Cat Code Changes (MIDB MacBeth version) to be consistent with the Air Force TBMCS or Y2K-remediated CTAPS 5.2.3, both of which require the MIDB updates.