Chapter1 Vector31

Joint Collection  Management Tools

The Combat Commanders’ Gateway to National Collection

by Robert L. McKinnon

Joint Collection Management Tools (JCMT) is the Department of Defense (DOD) migration system for all-source, intelligence collection management. Collection managers (CMs) in every Service and at each echelon from the Defense Intelligence Agency to Army divisions will use the system. (See Figure 1.) For the first time, it allows the collection managers at all echelons to—

The JCMT currently operates at the Top Secret/sensitive compart- mented information (TS/SCI) level.

Software Development

The Product Manager (PM) for JCMT has articulated a strategy that calls for development and delivery of the software in four phases  (Capabilities Packages) over a three-year period. These packages offer a collection requirements management application (CRMA), collection requirements management system (CRMS), support to the tactical echelons, and common operating environment compliance.

Collection Requirements Management. Fielding of the JCMT Capabilities Package 1.0 began in March 1998. The primary objective of this current release is to “roll forward” into JCMT the functionality of Defense Intelligence Agency’s (DIA) CRMA. The CRMA is a leg- acy system used by CMs at the national and theater levels working primarily with national signals, imagery, and human intelligence (SIGINT, IMINT, and HUMINT respectively) collectors. Its func- tionality includes a local require- ments registry, robust satellite-borne and atmospheric collector models, and the ability to cross reference, either manually or automatically, requirements, targets, messages, and more.

Collection Requirements Management System (CP 1.1). Delivery of CP 1.1 will begin in May 1999 at the sites that have not yet received CP 1.0. The primary objective of this release is to capture the task list methodology and workflow found in the National Air Intelligence Center’s (NAIC) Collection Requirements Management System (CRMS). This functionality will allow a JCMT collection requirements manager to assign and track various tasks, such as the generation of a requirement or the evaluation of raw reporting. Other improvements include changes to the system’s human-machine interface (HMI) in order to make JCMT as user-friendly as possible, initiatives to make the system compliant with DOD Year 2000 (Y2K) directives, and the development of “JCMT Lite.” This last initiative is primarily a JAVA-coded web- based effort to satisfy the needs of those CMs who are constrained in terms of communications bandwidth, such as Navy and Marine Corps CMs deployed at sea.


Support to the Combat Commander. This version (CP 1.2), of the software scheduled for fielding beginning in October 1999, will include several enhancements designed to assist the CM at tactical echelons in planning and executing collection operations. These enhancements include the addition of models for tactical ground- and sea-based collectors and the incorporation of an intelligence synchronization matrix (ISM) format. The models will allow the CM to assess more accurately the capability of a particular tactical asset to collect against a specific target while the ISM will facilitate the synchronization of collection activities with friendly operations in the battlespace area. A further enhancement includes an interface with the measurement and signals intelligence (MASINT) Requirements Database System (MRDBS). This will allow the user to access, generate, and monitor MASINT requirements in a manner similar to the way that JCMT users now manage HUMINT, SIGINT, and IMINT requirements.


Department Information Infrastructure Common Operating Environment (DII COE) Compliance. Capabilities Package 2.0 will be fielded beginning in September 2000. The major improvement planned for this release includes the improvement of JCMT’s compliance with DII COE standards. This will enhance the JCMT user’s ability to access remote requirements registries, target data- bases, and product and reports archives. Other improvements include the—

JCMT Fielding Concept

The Army will field the JCMT using a variety of methods depending on the Capabilities Package in question. An installation team from the JCMT Project Management Office (PMO) will issue CP 1.0 to non-tactical organizations. Commands that receive this initial installation will also receive forty hours of on-site instruction in the use of the software. Army tactical users will receive CP 1.0 through the All-Source Analysis System. “JCMT Central,” located in San Diego, California, will push subsequent releases to the user community via the Joint Worldwide Intelligence Communications System (JWICS). JCMT Central will also disseminate software patches and updates in a similar fashion to the—


The Future

Other enhancements under con- sideration include a collateral version of JCMT. This version will retain only that functionality necessary to create and monitor local collection requirements and support the management of non-national assets. Other enhancements may include the ability to manage collection requirements for commercial imaging satellites such as LANDSAT and System Probatoire d’Observation de la Terre (SPOT), and the ability to create “conditional tasking strategies.” This latter capability allows for automatically cross-cueing other collectors to a particular target’s location. (See Figure 2.) These enhancements ensure that JCMT will not only allow the CM to work more efficiently; they will also fundamentally change the way that we conduct collection management throughout the DOD.

Mr. Bob McKinnon was a SETA contractor supporting the PM-JCMT as a software trainer, systems evaluator, and writer. A former 98K (Signals Collection/Identification Analyst) and 97B (Counterintelligence Agent), he holds a Master of Arts degree in International Relations from Boston University. He has been a Senate Intern, a Paralegal, and an Intelligence Research Specialist with the Federal Bureau of Investigation National Drug Intelligence Center. Interested readers can contact Mr. Craig Manley via E-mail at [email protected] and telephonically at (703) 275-8152 or DSN 235-8152.