Military Intelligence Integrated Data System (MIIDS)
The Intelligence Database [IDB] resides on the MIIDS architecture and supports general MI production. 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. DIA is the proponent agency for MIIDS and IDB.
In CONUS, the US Army Forces Command (FORSCOM) Automated Intelligence Support Activity (FAISA) at Fort Bragg, NC, had access to the MIIDS and IDB by tactical users of the ASAS. They maintained a complete copy of DIAs MIIDS and IDB and update file transactions in order to support the tactical user.
Obtaining MIIDS. There were three methods of obtaining MIIDS base loads and updates.
- The tactical unit downloads MIIDS and IDB data sets using file transfer protocol (FTP) via DSNET3 communications to user's host on a SCI LAN in an accredited sensitive compartmented information facility (SCIF).
- FAISA downloads MIIDS and IDB data sets to produce an optical disk, which is couriered to the tactical unit via Defense Courier Service and is put into the unit's ASAS IDP optical drive.
- FAISA downloads MIIDS and IDB data sets to optical disk, and they are couriered to the tactical unit by two cleared personnel from the requesting unit.
The initial ASAS Block I software does not allow for direct access from ASAS to the FAISA System to accomplish file transfer of MIIDS and IDB files. To get to the data, the unit will need an intermediate host on the LAN that will do the job. In most cases, field service support personnel will accomplish all the file transfers for the unit.
IDB File Types. There were two types of IDB files on the FAISA System:
- Base loads. To populate the ASAS ASCDB, the tactical unit must first submit a request for an IDB base load to FAISA, specifying country codes (in priority). There are 20 base load files required for each country to make a full set of data set files needed to build the database. Users will need to download all files for a particular country.
- Updates. The updates are also in a different file format than the IDB base load files. They are in transaction file format. For each update, the ASAS needs four transaction files. FAISA produces the updates by country codes for the unit to download.
Sources and Methods
Created by John Pike
Maintained by Steven Aftergood
Updated Wednesday, January 26, 2000 8:33:57 AM