1. Introduction

This chapter describes the joint intelligence architecture that provides a multimedia communications network with interoperable systems that link the theater JICs, joint task force (JTF) JISEs, deployed intelligence elements, Service intelligence, and national intelligence organizations in a global grid.

2. C4I For The Warrior

The Department of Defense strategy for C4I is laid out in the Joint Staff/ J-6 developed C4I for the Warrior concept. This concept envisions a global communications and information grid into which all military information customers can plug interoperable systems. The joint intelligence architecture is an integral part of the C4I for the Warrior concept.

3. Joint Intelligence Architecture

a. Overview

• The joint intelligence architecture provides the means to interconnect collectors, producers, and customers in an information network. All intelligence made available to the network from any source is stored and communicated as data whether it is a text file, graphics, imagery, or formatted information. The data is stored on a standards compliant file server. The file server is the interface with the communications network.

• In keeping with the spirit of C4I for the Warrior, the joint intelligence architecture is a dynamic, flexible structure providing global access to an information grid that consists of all intelligence sources at all echelons. The architecture facilitates the capability of the Defense Intelligence community to focus on supporting the JFC and subordinate joint force components and to integrate support from non-Defense agencies and nongovernment organizations as needed. The joint intelligence architecture is configured to provide access to all intelligence sources from anywhere on the globe and to provide the baseline data that JFCs will need to support joint operations. This architecture conceptually describes equipment capabilities, information flow requirements, and responsibilities.

Figure VII-1. Intelligence Architecture Principles

• C4I Interoperability. The J-2 should ensure command elements' and supporting organizations' intelligence systems and communications are compatible for exchange of data, information, and intelligence products. If components' intelligence systems cannot receive or exchange intelligence data, the systems are not interoperable. Interoperability of systems also relates to intelligence data processing and related equipment.

• Intelligence Product Interoperability. Intelligence organizations producing joint intelligence should ensure that intelligence products are in a form, content, and language usable by all components of the joint force performing similar and related functions. For example, if one component requires maps with Military Grid Reference System (MGRS) (which also includes universal transverse mercator) coordinates while another cooperating component uses charts with geographic coordinates, location information should be expressed with both MGRS and geographic coordinates.

• Common Terminology and Symbols. Intelligence organizations should understand and use concepts, language, terminology, names, and symbols common to all joint force components.

• Standards. Factors that promote interoperability can be expressed in standards. Standards are sets of guidelines and criteria for continuity and similarity of data, protocols, formats, terminology, equipment, and signals that promote the exchange, understanding, and application of intelligence requirements and intelligence products among intelligence organizations and JFCs. Standards for interoperability should be developed and incorporated into intelligence systems, equipment, and procedures providing intelligence for joint operations. Standards need to be enforced in peacetime to facilitate transition to operations other than war or war.

• Effective Training and Exercises. Intelligence interoperability problems reduce the ability of a joint force to attain unity of effort. Thus, an important concept is to use realistic training, exercises, and rehearsals of operations to demonstrate, test, and evaluate the joint interoperability of intelligence systems and intelligence products.

• Data Bases. Ability of all echelons of the joint force to access archives and common data bases is key to successful intelligence operations.

• Organization. The joint architecture that provides the infrastructure for intelligence support is not hierarchical. Formal command and control relationships, however, exist as shown in Figure VII-2. This relationshi facilitates RFI management and optimizes complementary intelligence functions by echelon without obstructing the timely flow of critical intelligence up, down, or laterally. The national agencies maintain systems and organizations that respond directly, and provide intelligence, to any echelon for time-sensitive reporting (i.e., the TRAP broadcast). The formal flow for intelligence RFI up and down echelons is through the NMJIC.

• Equipment
  • Figure VII-3 depicts the joint intelligence architecture as a network of integrated work stations, file servers, and communications links. These three elements must work together, compliant with common standards, to create the interoperable information environment required to support military operations. The network includes direct connectivity by some communications or communications relay link (landline, radio, satellite, and others as appropriate) and broadcast capability to support time-sensitive and "sensor-to-shooter" needs. The information grid concept allows data collected by whatever means to be communicated directly to a user or to a processing site or platform by the most efficient path, then passed on or through to the user as appropriate. A critical aspect of the information grid is its ability to make all intelligence, including direct collector-to-user information, accessible via standardized file servers to standards compliant work stations.

  • Some collected, unprocessed information can be transferred to a headquarters, regional, or field processing site directly via existing communications links that are outside the joint architecture. Such information is not useful prior to processing (e.g., encrypted information), or requires very high bandwidths that would overwhelm the communications links. In these instances, the information is first processed or selectively captured prior to transferring or making it available over the network (examples are certain raw SIGINT and some types of imagery or video).

    Figure VII-2. Formal Joint Intelligence Architecture

  • In Figure VII-3, collectors and producers process information before passing it on in the correct format to the standardized file servers. Where required, the data can be automatically passed to the standardized file servers without processing. Processing and communicating information collected by an unmanned aerial vehicle (UAV) provide a good example. Very high resolution video collected by the UAV can be viewed near real time at a downlink processing site, but communication of this video requires high bandwidth. The unprocessed video can be relayed directly by fiber-optic line or satellite to a JIC or headquarters element. At the same time, targeting information can be reported to tactical elements by voice communications or message. Selected video frames can be captured by JDISS and made available to all users over the joint architecture. Information processed by a headquarters element or JIC could, in turn, be transmitted or made available by Joint Worldwide Intelligence Communications System (JWICS) and/or JDISS. In this example, all the capabilities linked to and by the joint architecture are exercised including both pull and push. The information is made available for a variety of users needs and is included in products and reports that serve multiple purposes for the tactical users.

4. Connectivity

a. General. To maximize the utility of the architecture, systems must meet standards of connectivity using standard communications protocols and standard encryption devices that must be available at all echelons. The architecture has the flexibility to accommodate, not to replace, existing I&W and direct support systems. It is intended to overlay additional capabilities using existing communications carriers.

b. Joint Worldwide Intelligence Communications System and Joint Deployable Intelligence Support System. The joint intelligence architecture uses JWICS and JDISS as the joint standard and foundation for commonality among support systems. As shown in Figure VII-4, JWICS satisfies the requirement fo secure, high-speed, multimedia transmission services for intelligence information. JWICS incorporates advanced networking technologies that permit greater throughput and capacity, making possible the use of applications that take advantage of multimedia technologies including video teleconferencing. Each JWICS node can create, receive, transmit, and store video images as well as voice, text, graphics, and data. Information can be either broadcast or shared interactively among JWICS subscribers on a point-to-point or multipoint basis. The JWICS circuit can be managed via allocation of bandwidth, allowing simultaneous use of the link for multiple applications. JWICS is an integral part of the sensitive compartmented information portion of the Defense Information Systems Network.

Figure VII-4. Joint Worldwide Intelligence Communication System

• As shown in Figure VII-5, JDISS provides the standar workstation server software configuration. JDISS is the DODIIS reference model. The basic backbone for the dissemination of intelligence to and from deployed JDISS nodes is via the JWICS network. Where JWICS is not required or not available, JDISS has a versatile communications capability that can be connected to whatever circuit is available. The architecture optimizes flexibility to focus intelligence efforts efficiently and assure that support is maximized for a theater engaged in military operations.

• All-source ntelligence dissemination in support of joint operations at the national, theater, and subordinate joint force levels will be via JWICS and JDISS. These systems support the production, dissemination, and display of fused intelligence critical to theater battle management. The architecture provides access to data from national, theater and tactical intelligence organizations and sources primarily from a "push-pull" system. A "pull" concept will result in JFCs receiving only high-quality, relevant intelligence based on their mission and phase of the operation. The "pull" capability is designed to prevent communications circuit saturation. In addition, time-sensitive intelligence will be "pushed" to JFCs and components via dedicated broadcasts in response to preplanned EEI. ADP interoperability with force level systems will be accomplished by JDISS integration. Through JWICS connectivity, intelligence production at the national level can be shared in near real time with the JFC. Automated processing and seamless connectivity at all levels allow intelligence analysts at all levels access to imagery and multiple data bases while concurrently producing intelligence products in response to specific mission requirements. This up, down, and across echelon interface among strategic, operational, and tactical intelligence organizations is the backbone for joint intelligence dissemination.

Figure VII-5. The Joint Deployable Intelligence Support System

5. The Joint Intelligence Center/Joint Intelligence Support Elements

Secretary of Defense memorandum, 15 March 1991, "Strengthening Defense Intelligence," inter alia, established the JIC as the primary intelligence organization providing support to joint warfighting at all levels. The JIC concept fuses the main support capabilities of all Service, Combat Support Agency, and combat units into a one stop shopping center for intelligence support. Although in reality, a particular JIC cannot be expected to completely satisfy every RFI; it can coordinate support from other intelligence organizations above and below its echelon. A subordinate joint force is supported by a JISE, a tailored subset of a theater JIC.

Figure VII-6. Representative Joint Intelligence Center

Figure VII-7 JIC/JISE Personnel Augmentation Sources.

a. All JICs/JISEs provide intelligence support to operational forces and perform common functions. Figure VII-6 provides a representative JIC organization wherein all major joint intelligence functional areas and liaison relationships are presented. As shown, the JIC is the principal J-2 organization supporting joint operations.

b. The JIC/JISE is, by deign, scalable and can expand to meet the needs of the JFC. During noncrisis periods, JIC manning is normally retained at the minimum level required to perform essential functions such as I&W, current intelligence, collection management, delegated general military intelligence production, and support to the commander. As crises develop, JICs at each echelon bring together personnel and equipment needed to manage intelligence support requirements. JISEs are established to meet the particular needs of subordinate joint forces. Collection, production, and dissemination resources are focused on the crisis. Liaison with intelligence production agencies and communications staffs identifies critical shortfalls, and action to correct deficiencies is accomplished. Because the JIC is the focal point for intelligence support to joint operations, augmentation personnel are drawn from many sources, including Reserves, as shown in Figure VII-7.

c. At the national level, the NMJIC is the focal point for all defense intelligence activities in support of joint operations. Combatant commands have JICs focused on their geographic or functional responsibilities. A subordinate joint force, when established, also normally forms a JISE as the focus for intelligence in support of the joint force commander, joint staff, and components.

d. Functions. The JIC/JISE allows for efficient access to the entire DOD intelligence infrastructure in support of joint operations. JICs/JISEs perform common functions although the degree to which they engage in specific functions varies according to command missions. The command's J-2 and JIC/JISE are normally collocated, and it is the prerogative of command to define JIC functions and responsibilities, particularly with respect to the J-2 staff. In many cases, a responsibility may be shared between the J-2 staff and JIC/JISE. For example, the J-2 staff may be responsible for setting forth collection requirements, while the JIC may have the duties of implementing those requirements and managing their fulfillment.

• National Level. The NMJIC is the channel through which the JFC's intelligence and CI needs, normally routed through the combatant commander, are tasked to appropriate national agencies (see Joint Pub 2-02, "National Intelligence Support to Joint Operations," for details of national agencies such as CIA, NSA, CIO, DMA, and NRO). The NMJIC serves as the Joint Staff/J-2 focal point for management and tasking of JFC national RFI (see Joint Pub 2-02, "National Intelligence Support to Joint Operations," for RFI management details). The NMJIC will expand as necessary, establishing a Working Group, Intelligence Task Force, or in the case of a major crisis like Operation DESERT STORM, a contingency NMJIC.
  • The NMJIC serves the Washington, D.C. community, combatant commands, Services, and coalition partners and llies. It is the DOD single point of entry for RFI and for accomplishing these intelligence functions: (1) global I&W, (2) current intelligence, (3) situation summaries, (4) estimates, (5) special assessments, (6) national targeting support, (7) joint TECHINT support through a technical operational intelligence representative, and (8) national data bases. The NMJIC participates in targeting and developing national-level target lists as described in Joint Pub 2-01.1, "JTTP for Intelligence Support to Targeting." The NMJIC supports the theater as requested in BDA. The Joint Staff/J-2 will resolve tasking and production priority conflicts among competing combatant commanders, if required. (See Joint Pub 2-02, "National Intelligence Support to Joint Operations," for NMJIC concept of operations.)

  • The NMJIC has access to all DIA resources and is linked by automation to the Operational Intelligence Crisis Center (OICC) located in the National Military Intelligence Production Center (NMIPC), Bolling AFB, Washington, D.C. The OICC is the focal point for the NMJIC at the NMIPC, and it manages crisis-related military intelligence production and, as appropriate, DIA imagery resources at the Washington Navy Yard. The OICC has access to DIA analytical expertise, including military capabilities, S&T intelligence, estimative intelligence, military production and geography, intelligence data bases, and operational support and targeting requirements for national, theater, and tactical units.

  • The national support structure (Figure VII-8) als includes a DCI task force established to focus CIA support for military operations. The DCI task force is made up of representatives from Defense and combat support agencies. Also, NMJIC can access the Department of State. NMJIC serves as the subordinate joint force or theater JIC point of contact for interaction with this DCI task force.

  • Requirements for national collection and support in collection coordination are handled by the Defense Collection Coordination Center collocated with the NMJIC.

  • DIA coordinates through the combatant command/J-2 augmentation to the subordinate joint force/J-2 for captured materiel and document exploitation. The support is usually tailored to the crisis situation and can range from a liaison officer to the subordinate joint force/J-2 to a robust joint staff element with a fully-staffed JCMEC and Document Exploitation team.

  Figure VII-8 National Support Structure

• Theater/Regional Level. The National Military Strategy describes the JIC as "the principal element for ensuring effective intelligence support for combatant commanders in chiefs and theater forces." Not all combatant commanders have JICs assigned to their commands, but they do receive general support from at least one regional JIC. Theater JICs are organized in accordance with geographic combatant commander prerogatives but normally perform the general functions described in Chapter VI, "Intelligence Functions for Joint Operations," and can expand or contract based on command intelligence and CI support requirements (see Chapter VI of this publication, "Intelligence Functions for Joint Operations," Joint Pub 2-02, "National Intelligence Support to Joint Operations," and specific combatant command intelligence TTPs publications for details). The "normal" regional JIC is the single source for RFI processing and validation, in theater intelligence analysis, production, and dissemination. Regardless of configuration, all JICs have the mission of planning, training and providing direct support to deploying JTFs. JFCs should refer all RFI to the regional or theater JIC that has geographic responsibility for the intended AOR as soon as the mission has been identified.

• Subordinate Joint Force. When a JSE is required to support a forward-deployed subordinate joint force, personnel augmentation and C4I equipment and procedures can be tailored and deployed to fit the operating environment based on identified subordinate joint force requirements. The subordinate joint force JISE, with the intelligence staff, manages collection, analysis, and fusion of intelligence and dissemination up and down echelon of intelligence and products for the JOA. The JISE, through the J-2, as the focus for intelligence support to joint operations, is the hub of intelligence activity in the JOA and is responsible for providing the joint force commander, joint staff, and components with the complete air, space, ground, and maritime adversary situation by integrating and adding to the adversary situations developed by the combatant commanders' intelligence organization. A NIST made up of DIA, NSA, CIA, and other intelligence resources requested by the subordinate joint force J-2 can deploy to support the subordinate joint force JISE. If the geographic combatant commander desires, the NIST can function as a core JISE. The core JISE capability can be further enhanced by national deployable intelligence capabilities that can be requested to expand a subordinate joint force JISE or to augment theater capabilities. CIO and NRO personnel may augment the subordinate joint force JISE, as required. The level of support required by the theater, and the employment of the capabilities, is determined by the geographic combatant commander. Once determined by the geographic combatant commander, requirements are addressed by the Joint Staff J-2 for the combatant commander's J-2 through consultation with the Military Intelligence Board in Washington, D.C.

07-16-1996; 14:52:12