Joint Collection Management Tools (JCMT), formerly known as Collection Management Support Tools(CMST), is the DOD Intelligence Information System (DODIIS) migration system for all-source collection management, combining IMINT, SIGINT, MASINT, and HUMINT tasking. This software-only package provides the tools for gathering, organizing, and tracking intelligence collection requirements for all disciplines, for seeking national, theater, and organic responses to these requirements, and for assessing asset capabilities and availabilities. Collection requirements are generated by warfighters and then allocated to Collection Management Authority (CMA). The CMA uses the Joint Collection Management Tool to provide an overview of the requirements database. JCMT assists the CMA in determining the appropriate collection platform or mix of assets required to perform the mission. The CMA's collection management system provides the reconnaissance feedback to the warfighters who originated the requests for information.The JCMT software package replaces all existing collection management software as the sole all-source collection requirements management software. JCMT integrates the following legacy systems:
It will be used by national, theater, and tactical organizations of all services. The JCMT will improve interoperability between all echelons, be compatible with the Joint Deployable Intelligence Support System, adhere to Department of Defense Intelligence Information System standards, and operate in accordance with DoD common operating environment standards.
The Military Intelligence Board (MIB) designated the Army’s Deputy Chief of Staff for Intelligence (DCSINT) as the DODIIS Executive Agent (DExA) and DIA as functional manager for this effort.
JCMT is the standard software product that will be used by all collection requirements managers within DoD. It provides tools for recording, organizing and tracking intelligence collection requirements for all intelligence disciplines. A key feature of JCMT is the automated support it provides to a collection manager to ascertain the status of requirements that have been forwarded to other organizations for action. This feedback mechanism is currently possible so long as organizations are willing to place their requirements registries on Intelink. More robust feedback mechanisms will be incorporated into JCMT with each succeeding release of software.
JCMT also provides automated support for a collection manager to review selected discipline reporting to determine whether existing data might satisfy the collection requirements. If acceptable data are not available, JCMT's various databases and platform/sensor models can be queried for data about asset capabilities and availabilities. This allows a collection manager to determine whether requirements can be satisfied by existing collection missions or whether new collection is required. JCMT also supports the collection manager to develop collection plans and generate tasking and request messages.
When intelligence information is returned from collection assets or preprocessors, JCMT can automatically correlate selected key words in these responses (e.g. BE number, place or unit name, etc.) with the requirements that generated them. In this way, the collection manager can evaluate the satisfaction of requirements and the effectiveness of collection activities.
JCMT parses over 30 collection management messages into its databases; it can also store any message type for user review. JCMT also accesses numerous technical references and national SIGINT and HUMINT standing requirements. Because of policy decisions, IMINT standing requirements are currently only accessible through the Requirements Management System (RMS). Direct access to the MASINT standing requirements will be added to JCMT later.
JCMT is intended to be used by collection managers at all echelons at which all-source collection requirements management takes place. Historically, collection requirements management at the national and theater level has been more single-discipline oriented than it has been at the tactical level. The consistent use of JCMT at all echelons will foster an all-source perspective which should better optimize asset utilization and customer satisfaction.
Collection managers at each echelon can use JCMT to track that organization's all-source collection requirements. These requirements need not be the same as those at higher or lower echelons although they probably would be similar. This decentralized concept is different from the centralized database concept used, for instance, by RMS or the MASINT Requirements Database System (MRDBS). If a site's requirements cannot be satisfied with organic collection assets, JCMT will assist the collection manager to generate collection requests to be sent to other organizations for action.
One of the key functions of JCMT is facilitating the flow of status or feedback information on outstanding requirements and on products which will satisfy those requirements. In order for this concept to fully function, though, all organizations whose actions affect the status of requirements must cooperate by making status changes available on a timely basis. The workflow concept to be added to JCMT, especially once it is enhanced to allow monitoring of tasks among multiple organizations, will support the feedback function. This near-real time feedback capability will facilitate dynamic retasking, a process that redirects collection towards high priority targets that are identified after missions have begun.
JCMT provides tools to assist the collection manager to allocate collection requirements to collection assets and to plan collection strategies. These tools include feasibility models, status matrices, look-ahead tools, schedule timelines, and track and coverage displays. Once the collection manager has determined which asset types are most appropriate, JCMT will assist him/her to generate tasking/requests appropriate for the requirement.
One of a collection manager's important duties is to synchronize requirements and supporting collection activities with friendly operations. JCMT will provide automated support for this activity in the future.
Functional oversight for JCMT is exercised by the Collection Requirements Management Board (CRMB) and its subordinate group, the Functional Control Board Working Group (FCBWG). The CRMB is chaired by DIA/CL and is comprised of representatives from all services and unified commands. Technical oversight is exercised by the DODIIS Management Board (DMB). Training issues are coordinated through the Joint Training Working Group (JTWG) chaired by DIA.
JCMT is a software-only product. Thus, each site is responsible for providing and maintaining its own hardware. The software currently operates on SUN-UNIX SPARC 10 or 20 platforms. After its operating system was upgraded to Solaris 2.5, JCMT was able to operate on other SUN platforms (e.g. SPARC 1000 or 2000). In addition, by the Summer of 1997, JCMT was also able to operate on Hewlett Packard 9000/700 series workstations runing HP-UX 9.X or 10.X. JCMT requires 128 MB of RAM and a 8.4 GB disk drive. Most of the disk space is allocated to the databases, including reference databases such as MIIDS/IDB (or its successor MIDB). The executables which require run-time libraries and the supporting program files take up 350 MB.
JCMT came into existence in early 1994. On 26 January 1994, the Military Intelligence Board (MIB) endorsed a proposal from the Defense Intelligence Agency (DIA) and the Department of the Army that there be a single automated collection management tool for the entire defense intelligence community. The MIB then designated the Army's Deputy Chief of Staff for Intelligence (DCSINT) as the DODIIS Executive Agent (DExA) and DIA as functional manager for this effort. The Army further assigned program management responsibility to the Program Executive Officer for Command, Control, and Communications Systems (PEO C3S), which established the JCMT Product Management Office under the Project Manager for Intelligence Fusion.On 28 October 1994, the Assistant Secretary of Defense for Command, Control, Communications and Intelligence (ASD(C3I)) approved the recommendations from the Intelligence Systems Board (ISB) Migration Panel that: 1) JCMT become the DOD Intelligence Information System (DODIIS) migration system for all-source collection management, and 2) the Army's Collection Management Support Tools (CMST) become the initial baseline for JCMT. Besides CMST, the legacy systems which JCMT was mandated to replace include:
JCMT Version 0.3, released in FY94 uses CMST Version 0.4 as a baseline. V0.4 is a DoDIIS CSE compliant version of the software and includes numerous functional enhancements over V0.3. V0.4 was installed at DODIIS CSE sites.
The migration concept called for all legacy systems to be retired by April 1997. With this in mind, PM JCMT devised an acquisition strategy with software development segmented into two major versions or capabilities packages (CP).
CP1 was released in July 1997 after it had undergone government acceptance testing at the factory, accreditation and technical testing at the Joint Integration Test Facility (JITF) and operational testing at CENTCOM, one of the beta sites. PM JCMT then began replacing the legacy systems with CP1.
CP2, the full operating capability version of JCMT will include all previous enhancements; to include graphical situation display and capabilities, many links to external assets and databases, as well as an intelligent tutoring system to facilitate JCMT initial and sustainment training. Developments for JCMT may include smart co-residency with Requirements Management Systems (RMS) when co-located. JCMT-only sites could have remote access to the RMS database. The SIGINT Data Server (SDS), formerly called the SIGINT On-line Mission Management System, sessions may become accessible through a JCMT SDS interface module, when developed. The interface module could allow RMS users access to SDS via the JCMT server. JCMT will receive a subset of the imagery database and accept messages in US Message Traffic Format and collection management specific formats.
As of mid-1997 JCMT resided at 41 sites of the 227 sites worldwide at which it was eventually to be installed. JCMT was delivered to sites in one of two ways:
PM JCMT sent its representatives directly to a site to conduct a site survey and install the software at that location according to the configuration desired by the site and the communications available. This method applied primarily to national and theater sites and selected tactical sites. In addition, the PM provided a team to conduct on-site training to last generally five days depending on the needs of the site. Training at legacy server sites lasted around two weeks. PM JCMT provided on-site training at initial installation and upon delivery of subsequent major releases. Interim software releases were delivered to sites via JWICS or on tape via the Defense Courier Service (DCS).
Installation of CP1 commenced in July 1997 and lasted approximately 12 months. Legacy server sites were replaced before the end of FY97.For the bulk of the tactical sites, PM JCMT provided a copy of the software to each service for incorporation into its service intelligence system. These systems are:
JCMT had also planned to incorporate JCMT into the Intelligence Analysis System (IAS), which the Marine Corps uses. However, because IAS will be incorporated in JMCIS (and to be called the Marine Air Ground Task Force (MAGTF) Command, Control, Communications, Computer, and Intelligence (C4I) Segment), Marines will be able to access JCMT functionality through JMCIS. The Coast Guard is also considering integrating JCMT into its Coast Guard Intelligence Support System (CGISS).
Representatives to the CRMB from the service headquarters indicated that they intended to deploy their service systems embedded with JCMT at least to:
In addition, most special operating forces of all services receive JCMT capabilities through JDISS.
The service is responsible to integrate JCMT, accredit and operationally evaluate the integrated product, and conduct training. PM JCMT will train the service trainers so that they can train JCMT in a manner best suited to that service. This applies on-site initial, and sustainment training. Each site or service is responsible for procuring and maintaining hardware and for acquiring COTS software licesnses.