MASINT was first formalized as a subcommittee under the DCI SIGINT Committee. In 1986 the Director of Central Intelligence (DCI) declared MASINT a separate, formal intelligence discipline and established the MASINT Committee. In 1993 DCID 2/11 and DoD Instruction 5105.58 created the Central MASINT Office (CMO) under the Defense Intelligence Agency (DIA), largely funded through DIA's General Defense Intelligence Program (GDIP). In 1998 the DCI further strengthened the management of MASINT by recasting CMO as the Central MASINT Organization (still "CMO"). The new CMO had greater responsibility, as evidenced by the DCI's Strategic Objectives for MASINT, but was still embedded in DIA without the requisite budget oversight and authority necessary to truly manage an intelligence discipline. In 2003 the Director, DIA merged CMO and other elements of DIA into a new Directorate of MASINT and Technical Collection.
Historically, the MASINT discipline has gone through three eras:
Desire: CMO, agencies and the Services worked to "operationalize" MASINT. CMO established the MASLO's at the Commands. Everyone shifted scarce resources to focus on SMO capabilities. MASINT practitioners developed new techniques, procedures and algorithms. We got close to the operator - to understand their real needs, figure out how they operated, and work to get them the answers they needed, tailored in the way they were needed, in the timeframe they needed them.
Computer Speed/Communications Bandwidth: Operators needed answers fast. The MASINT Community's S&TI systems worked at PhD thesis speed. It took a lot of number crunching to get an answer. The MASINT data sets were huge and up until now there hadn't been a need (nor the real capability) to communicate these data sets from one side of the world to the other in anything approaching near-real-time. As desktops achieved capabilities of older mainframes and high-end workstations and communications went from 9.6 kbaud to T-1 speeds and beyond - and the right algorithms were put into place - it finally became possible to put timely, relev MASINT answers in the hands of operators. Increased data storage densities contributed equally to operationalization of MASINT.People: Getting MASINT to the warfighter required an increased number of practitioners. As MASINT demonstrated its value in some of the closing conflicts of the 90s, the "success catastrophe" led to greater and greater demand for product. The Army's National-to-Theater initiative is a very successful example of growing the cadre of MASINT practitioners.
During the SMO Era CMO was the central figure for the MASINT Community. This era of centralized management for MASINT was probably critical to the refocusing of the S&TI capability to SMO (while retaining the capability to do much of the strategic and RoW mission). It is interesting to note that during this era, there was almost no investment in any major new capability. What funding was available in the base and slightly augmented R&D programs throughout the community was reprogrammed or redirected to accomplish what was done. It was arguably not accomplished fast enough, or robust enough, or consistently enough. MASINT is even today not as interoperable or accessible as users desire. But it ultimately did happen, in large part due to the heroic efforts of a small number of people.Notice and Consent Banner:
Use of this DoD computer system, authorized or unauthorized, constitutes consent to monitoring of this system. Unauthorized use may subject you to criminal prosecution. Evidence of unauthorized use collected during monitoring may be used for administrative, criminal, or other adverse action. Use of this system constitutes consent to monitoring for these purposes.
The appearance of hyperlinks does not constitute endorsement by the U.S. Air Force or the information,products, or services contained therein. For other than authorized activities such as military exchanges and morale, welfare and recreation sites, the U.S. Air Force does not exercise any editorial control over the information you may find at these locations. Such links are provided consistent with the stated purpose of this DoD Web site.
Content Owners
The content owner of this web page is the AFIT/PA, Air Force Institute of Technology, Public Affairs Office.
Email: pa@afit.edu