AJP27
AJP27
AJP27
NATO STANDARD
AJP-2.7
Published by the
NATO STANDARDIZATION OFFICE (NSO)
© NATO/OTAN
NATO UNCLASSIFIED
NATO UNCLASSIFIED
INTENTIONALLY BLANK
NATO UNCLASSIFIED
NATO UNCLASSIFIED
NORTH ATLANTIC TREATY ORGANIZATION (NATO)
[Date]
1. The enclosed Allied Joint Publication AJP-2.7, Edition A, Version 1 ALLIED JOINT
DOCTRINE FOR JOINT INTELLIGENCE, SURVEILLANCE AND RECONNAISSANCE,
which has been approved by the nations in the Military Committee Joint Standardization
Board, is promulgated herewith. The agreement of nations to use this publication is
recorded in STANAG 7107.
2. AJP-2.7, Edition A, Version 1 is effective upon receipt and supersedes AJP-2.7 which
shall be destroyed in accordance with the local procedure for the destruction of documents.
Edvardas MAŽEIKIS
Major General, LTUAF
Director, NATO Standardization Office
NATO UNCLASSIFIED
NATO UNCLASSIFIED
INTENTIONALLY BLANK
NATO UNCLASSIFIED
NATO UNCLASSIFIED
I Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
INTENTIONALLY BLANK
II Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
RECORD OF RESERVATIONS
Note: The reservations listed on this page include only those that were recorded at time
of promulgation and may not be complete. Refer to the NATO Standardization Document
Database for the complete list of existing reservations.
INTENTIONALLY BLANK
IV Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
Note: The reservations listed on this page include only those that were recorded at time
of promulgation and may not be complete. Refer to the NATO Standardization Document
Database for the complete list of existing reservations.
V Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
VI Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
The policy and guidance for this joint publication is derived from the Military Committee’s
NATO Joint Intelligence, Surveillance and Reconnaissance (JISR) Concept.1 This document
captures the overarching concept that establishes the basis on which NATO and national
assets combine to support NATO. The aim of the concept is to steer the traditional activities
of intelligence, surveillance and reconnaissance (ISR) areas into a joint streamlined
synchronization and integration of intelligence and operations.
This publication should be read in conjunction with AJP-2.1, Intelligence Procedures. AJP-2.1
which describes the generic procedures, interdependencies and considerations required to
conduct intelligence operations in support of peacetime and crisis operations.
JISR capabilities and activities need to satisfy the broadening scope of information and
intelligence requirements for planning, preparation, execution of operations, and mission
review by NATO at the strategic, operational and tactical levels and in all phases of operations.
Commanders, staff and operators benefit from sharing information and intelligence derived
from JISR capabilities because it enables informed, timely and accurate decision making.
NATO and Nations bear the responsibility to gather and disseminate data, information and
intelligence to maintain situational awareness. Nations invest individually and collectively in a
wide range of collection capabilities to provide the Alliance with effective joint intelligence,
surveillance and reconnaissance support. Collection assets include NATO systems,
multinational, national, partner and commercial sensors, platforms and equipment. Nations
may declare use of their JISR capabilities to support NATO defence and operations planning
or to be allocated to NATO-led operations.
The Alliance, therefore, requires agreed upon JISR doctrine and procedures to facilitate the
integration of all available capabilities, ensure their efficient and effective employment and
establish a truly “Joint” ISR capability. JISR capabilities and activities need to be embedded
in a robust architecture consisting of the organizations, processes and systems connecting
the taskers, controllers, collectors, exploiters, analysts, databases, applications, producers
and requesters of data, information and intelligence and operational data in a joint
environment.
1
MC 0582 NATO Joint Intelligence, Surveillance and Reconnaissance (JISR) Concept
CHAPTER 1 OVERVIEW
1.1 Introduction 1-1
1.2 Purpose 1-1
1.3 Scope 1-1
1.4 Terminology 1-2
1.5. Related Document 1-3
LEXICON
Part I - ACRONYMS AND ABBREVIATIONS LEX-1
Part II - TERMS AND DEFINITIONS B-1
TABLE OF FIGURES
Figure 1.1 - AJP-2.7 within the NATO Allied Joint Doctrine Architecture 1-4
Figure 2.1 - Relationship of the JISR Process to the Intelligence and Operations Cycles 2-2
Figure 3.4 - The Ad hoc and Dynamic JISR Tasking Process Error! Bookmark not
defined.0
IX Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
X Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
INTENTIONALLY BLANK
XI Edition A Version 1
RATIFICATION DRAFT 1
NATO UNCLASSIFIED
NATO UNCLASSIFIED
OVERVIEW
1.1 Introduction
1. Joint Intelligence, Surveillance and Reconnaissance (JISR) is a set of intelligence and
operations capabilities, to synchronize and integrate the planning and operation of all
collection capabilities with the processing, exploitation, and dissemination of the resulting
information in direct support of the planning, preparation and execution of operations. 2
3. JISR supports the full spectrum of NATO operations ranging from combat operations
to humanitarian assistance
1.2 Purpose
1. The purpose of Allied joint publication 2.7 (AJP-2.7) is to establish Allied joint doctrine
to guide commanders, staffs and forces engaged in JISR operations within the NATO alliance.
This publication documents the principles, fundamentals and essential staff procedures
necessary to successfully plan, direct and execute JISR operations that ensure timely and
effective decision making.
2. This publication provides a framework for the coordination and tasking of JISR
capabilities to ensure that JISR results are disseminated with the appropriate classification to
the right person, at the right time, in the right format, in direct support of current and future
operations and the operational planning process. JISR results should be responsive to the
needs of the commander and staffs, with the commander’s priority intelligence requirements
(PIR) 3 serving as the “steering wheel” for JISR operations.4
3. This document provides guidance to commanders and staffs for the effective
management of JISR capabilities within the JISR process, which requires close coordination
between the commander, the intelligence staff, the operations staff and other staff elements
contributing to the JISR effort. Intelligence Requirements Management and Collection
Management (IRM&CM)5 are management staff functions inside the intelligence cycle, which
are crucial to the JISR process providing the rationale and priority for any information or
intelligence requirements. AJP-2.1 Intelligence Procedures provides more detail on IRM and
CM processes. Timely and close coordination between staff elements is needed for the
optimized tasking of JISR assets
2 Allied Joint Publication (AJP)-2(A), (2014). This term and definitions modifies an existing NATO Agreed term
and/or definition and will be processed for NATO Agreed status.
3 AJP-2(A), (2014), Chapter 5.2.4.
4 AJP-3(B), Chapter 4, Section III.
5 AJP-2(A), (2014), Chapter 5.
2. The main objective within the JISR process is to satisfy information and intelligence
requirements with limited JISR capabilities. JISR capabilities may include NATO-owned JISR
capabilities and JISR capabilities owned by the Nations, which can be assigned to NATO
commanders or kept under national control. Therefore, effective coordination and efficient
employment of these capabilities are paramount.
4. AJP-2.7 serves as the foundation for other Allied publications as well as evolving
subordinate publications such as the Allied intelligence publication (AIntP-14) JISR
Procedures in Support of NATO Operations.
1.4 Terminology
1. AJP-2.7 uses one set of terms consistently throughout the document and aligns itself
with the terminology from AAP-06 whenever possible.6 In addition to the definition of JISR and
the NATO approved definitions of intelligence, surveillance and reconnaissance, additional
terms are necessary to aid in understanding and implementing the JISR concept. To ensure
consistency in describing JISR operations, processes and capabilities, AJP-2.7 uses the terms
and definitions below:
6 All statements and terminology regarding JISR are not intended to convey any legal connotation or status.
Instead, it should assist NATO commanders and staffs in understanding and describing their operational
environment and planning and executing JISR operations.
7 AJP-2(A), (2014), Chapter 3.7.
14 This term is only used for this publication and has not been NATO approved.
15 MC 0582/1 (2013), Annex B, 11.
Figure 1.1 - AJP-2.7 within the NATO Allied Joint Doctrine Architecture
INTENTIONALLY BLANK
JISR FUNDAMENTALS
2.1 Introduction
1. JISR operations are initiated with a validated CR and aim to satisfy CRs across all
echelons of command in an efficient and timely manner. Toward that end, intelligence and
operations staffs coordinate, synchronize, prioritise and deconflict multidisciplinary JISR
collection capabilities and all associated processing and exploitation capabilities.
2. JISR supports the collection phase of the intelligence cycle,16 and contributes to
fulfilling the collection requirements of commanders and their staff necessary to plan,
execute and assess operations.
3. The JISR process, in addition to supporting joint operations, also provides direct
tailored support to land, maritime, air, space and special operations forces requirements.
JISR results support the production of all-source intelligence, which contributes to advance
planning and crisis response planning processes17 and the execution of operations.
5. The JISR process supports the intelligence staff and the operations staff with the
respective results to meet the commander’s objectives. Each level of the involved staffs in
the JISR process interacts with the levels above and below, and among units, agencies, and
organizations on the same level. The further up the chain of command, the broader the
perspective and scope of responsibility; the lower, the more specific the function and narrow
the scope. The process demands constant collaboration and communication between
requesters and the intelligence and operations staffs to maximize the efficiency and
effectiveness of available capabilities.
6. Within the priorities set by the commander, JISR provides the framework to
synchronize and integrate intelligence and operations requirements into CRs. This
framework allows JISR capabilities to be effectively integrated within the overall scheme of
manoeuvre.
7. The JISR process is the means through which CRs are satisfied and consists of five
steps: Task, Collect, Process, Exploit and Disseminate. The implementation of these five
steps normally relies on a federated and collective effort from all levels of command, across
components, and possibly supported by national and/or out-of-the-theatre capabilities. The
basic JISR framework and the relationship of the JISR process to the intelligence and
operations cycles through synchronization and integration are depicted in Figure 2.1.
16 AJP-2(A) (2014), Chapter 4. JISR does not replace intelligence activities; rather they are part of the
integrated process of producing intelligence. See AJP-2(A) for a full description of the intelligence cycle.
17 AJP-5(E) (2013), Section III, 0110.
Figure 2.1 – The Relationship of the JISR Process to the Intelligence and Operations
Cycles
2. JISR Synchronization.18 The JISR process is strongly interlinked with the direction
and collection stages of the intelligence cycle. The direction and collection stages of the
18
Used only in this publication to introduce the relevance of a permanent dialogue between intelligence and JISR staff elements to ensure
effective and efficient fulfillment of all intelligence and collection requirements.
3. JISR synchronization begins after validating and prioritizing IRs and confirming
intelligence gaps through Intelligence Requirements Management (IRM). JISR
synchronization identifies the best means of collection, based on time, location, availability
and the type of information required to satisfy information or intelligence requirements
concerning the joint operating environment.
7. During the tasking step of the JISR process, the operations staff, responsible for
tasking and controlling JISR assets, integrates the JISR tasks developed by the CM into
mission planning. This enables the actual execution of collection, reconnaissance and
surveillance missions and their seamless integration within the overall joint operations.
Moreover, JISR mission integration is not limited to deliberate planning aspects and
becomes even more demanding when satisfying emerging CRs through ad hoc or dynamic
collection operations, when missions are already underway.
8. Through the coordinated and deliberate efforts of the IRM&CM elements and the
operations staff, JISR is integrated into the operational process to ensure that the JISR
assets have the required capabilities to satisfy the assigned CR. JISR integration provides
commanders a flexible means to maintain up to real-time situational awareness (SA) and
decision advantage in a dynamic environment.
10. Joint. The “J” in the term “JISR” stands for “Joint,” which describes the activities,
operations and organizations in which elements of at least two services participate.
19
Used in this publication to introduce the relevance of a permanent dialogue between operations and intelligence staff elements
supporting the JISR process to ensure effective and efficient mission tasking and control of JISR capabilities in space, time and purpose.
20 AJP-2(A) (2015), Chapter 3.9.
11. Intelligence The “I” in the term “JISR” stands for “intelligence” and refers to all
intelligence collection disciplines or collection capabilities/assets and the results these
disciplines/capabilities/assets can deliver to the commander and/or staff elements.
Intelligence collection disciplines include:
12. Surveillance. The “S” in the term “JISR” stands for “surveillance”. Surveillance is
defined as the systematic observation of aerospace, surface or subsurface areas, places,
persons or things, by visual, aural, electronic, photographic or other means. Surveillance is
designed to provide Indications and Warning (I&W) of adversary initiative and threats and
to detect changes in adversary activities. It can provide early warning of activity over a wide
area, or can focus upon a particular location, facility, activity or actor within the operating
environment.
13. Reconnaissance. The “R” in the term “JISR” stands for “reconnaissance”.
Reconnaissance is defined as a mission undertaken to obtain, by visual observation or other
detection methods, information about the activities and resources of an adversary or
potential adversary, or to secure data concerning the meteorological, hydrographic, or
geographic characteristics of a particular area.21 It is a focused method of collecting
information about specific locations, facilities or people. Reconnaissance tasks are not
confined by specific reconnaissance units, but may be undertaken by other force elements
in the course of their duties. Reconnaissance enables the collection of specific information
within the joint operations area, against known and potential adversaries and non-aligned
actors in support of current and future operations. Reconnaissance must be focused in time
and space to answer specific requirements. It collects results through visual observation or
21
This term and definition modifies an existing NATO Agreed term and/or definition and will be processed for
NATO Agreed status.
3. Responsive. JISR capabilities must be responsive, timely and flexible to satisfy the
needs of the requester. The JISR process must dynamically respond to evolving situations,
new information and revised requirements at all times. The right mix and numbers of JISR
capabilities with associated PED resources will provide the commander with the agility to
respond effectively. This can be achieved through layering of assets and cross-cueing
between assets of differing capabilities. JISR results should be delivered at the right time as
specified in the CR. The collected data, information or intelligence will be of limited or no
value if it is not available when needed. The JISR process should be responsive across the
joint operations area (JOA) to requests and tasks from all levels of command. JISR assets
typically tasked at the component command level must be able to integrate with and provide
direct support to tactical units. Conversely, tactical units and assets may be required to
support operational and strategic requirements.
6. Reliable. In order to give commanders and their staff confidence in JISR results,
JISR capabilities need to provide measures of credibility and probability on the collected
data and information. PED elements will need to provide timely results contributing to
accurate situational awareness and understanding allowing commanders to maintain the
decision-advantage.
7. Accurate. JISR results must answer the information requirements in the most
accurate way possible. Therefore, accuracy needs to be maintained continuously
throughout every step of the JISR process, from tasking through collection, processing,
exploitation and dissemination. This is to ensure the provision of objective, clear, unbiased
and undistorted JISR results for subsequent multi and all-source intelligence analysis, as
well as to prevent reliance on single-source confirmation or circular reporting.
a. IRM&CM22
(1) IRM&CM coordination is critical to ensure intelligence and information
requirements are satisfied. The term “IRM&CM” combines two distinct
functions in one term. Depending on the headquarters’ command
echelon, intelligence staff resources, and standard operating
procedures, IRM&CM can be conducted by establishing separate IRM
and CM functions or by combining the two functions into a single
(2) IRM&CM functions synchronize the JISR process with the intelligence
cycle. IRM&CM elements ensure that information and intelligence
requirements are properly articulated and answered and that all
available collection capabilities and assets are focused and prioritized.
The IRM&CM function is a component of the intelligence staff within
each organization’s headquarters.
(2) IRM plans for the satisfaction of standing and emerging intelligence
IRs as well as requests for information (RFIs)23 from higher, lower and
adjacent levels. During the operational planning phase, the IRM
element develops the ICP24 based on the commander’s PIRs. The
ICP is the typical planning tool to assist in producing, completing and
monitoring intelligence requirements. The IRM element uses the ICP
to integrate standing and emerging intelligence requirements for a
given headquarters and indicates how each requirement is to be
satisfied (e.g. identifying organizations, services, commands, or JISR
assets or intelligence disciplines). The ICP serves as a basis for the
deliberate planning, tasking and requesting of collection activities
using available assets or requesting information from various
sources.
(3) Once the IR is received, the IRM element validates and prioritizes them
and determines whether the information to answer them is already
available or if further action must to be taken, including collection.
Available results to the RFI will be disseminated directly to the requester
by the IRM staff. An analytical review by the intelligence staff’s analysts
might be requested prior to disseminating available results. IRs, which
cannot be satisfied by available information or intelligence, can be
passed on to the CM element or further processed as an RFI to IRM staff
in higher, lower or adjacent formations.
23 A RFI is used when a commander does not have sufficient dedicated collection capability, or the intelligence
staff are unable to answer a question through retrieval from existing data, intelligence, research or other
means.
24 AJP-2(A) (2014), Chapter 5.3.
(2) CM supports IRM in satisfying the intelligence and operations staff’s CRs.
These CRs are derived from the ICP (standing or emerging) or have
emerged through RFIs. CM encompasses activities related to the
execution and coordination of the five step JISR process, the coordination
of CM execution between headquarters and other organizations and the
assessment of the CM function. Within the CM function, the CRM and
COM authorities to collect, request and execute the JISR process are
established by the collection management authority (CMA).25
(4) CMA must work in coordination with subject matter experts and liaison
officers (LOs). LOs are responsible for bringing knowledge of their
component’s JISR capabilities to the joint operating environment. LOs
must work with the CM element with CRM and COM authorities to
(2) CRM starts once CRs are validated. CRM core activities encompass
the prioritization of CRs, the development of related JISR tasks, and
the distribution of JISR tasks to JISR capabilities whether dedicated or
assigned to NATO commanders or kept under national control. The
JISR task will be given to the appropriate theatre assets over which
the CM element has authority. If the JISR task cannot be fulfilled by
dedicated assets, the CM staff will generate a tasking request to be
included in the Collection Requirement List (CRL). All tasking requests
will be coordinated through the Joint Collection Management Board 27
(JCMB).28
(5) In specific NATO operations, the Joint Task Force (JTF) commander
will appoint a Theatre Collection Manager (TCM)29 who executes CRM
as a collective and joint function for a given operation and who is
supported by subordinate tactical commands.
(2) Based on the JISR tasks, COM starts with mission integration where
the approved CTL/ad hoc/dynamic JISR tasks are integrated with the
operations staff into operations and missions planning. It results in
developing strategies for collection and then issuing precise mission
orders by the operations staff to assigned JISR assets. The key tasks
of the COM authority involves managing the collection operation;
performing the processing and exploitation of collected data,
information and single source intelligence, and disseminating JISR
results. The monitoring of planned activities is essentially conducted
at each level of command. Similar to CRM, COM is performed at
different levels of command and requires coordination at a higher level
(e.g. at the operational level by the TCM for a given NATO operation),
particularly for handling dynamic situations that may necessitate the
reallocation of JISR assets.
JISR PROCESS
3.1 Introduction
1. The JISR process is a framework through which a single CR is satisfied by a JISR
asset and consists of five steps: Task, Collect, Process, Exploit and Disseminate
(TCPED). These steps apply at all levels of command, across components, for any type of
mission and in all operating environments.
2. The JISR process provides commanders and their staff with specific data, information
and results to address a CR. The JISR process supports both current operational needs
and, ultimately, the production of both multi-source and all-source intelligence.30
3. In order to provide timely, relevant, and accurate results to all levels of command,
JISR operations require coordination, de-confliction, and prioritization through JISR
synchronization31 and integration activities to ensure the most effective and efficient use of
capabilities. Within the JISR process, JISR synchronization activities require CM element
and intelligence staff coordination while integration activities require CM element and
operations staff coordination.
a. Step 1 - Task
2 Once ISR capabilities and assets are made available to the commander,32 the first step
of the JISR process is tasking, which is conducted by the CM element through the CRM and
COM authority and with the clear articulation of CRs based on the commander’s validated
intelligence and operational priorities. When articulating CRs, requesters should consider
the following:
to task the assigned asset. It forms an integral part of a military organization and is listed in the unit’s order of
battle.
3. JISR tasking is the initial step of the JISR process. It is initiated with the clear articulation
of CRs and consists of developing collection, exploitation and dissemination
guidance/directives/orders to coordinate and control JISR operations and assets. JISR
tasking is to be coordinated among all levels of command in order to enable mutual support
between services/component commands and to make the most efficient use of available
collection and exploitation capabilities. JISR tasking encompasses deliberate planning
aspects as well as ad hoc or dynamic tasking of emerging CRs. JISR tasking is planned
through CRM and its outputs are executed through COM.
4. Through mission integration, JISR tasking includes converting JISR tasks into orders and
passing these orders to the JISR capabilities placed under NATO commanders’ OPCON.
Each order should contain direction and guidance for processing, exploitation, and
dissemination of the collected data and information to enable the successful
accomplishment of the mission.
5. Because of limited availability of JISR assets, tasking should only occur when the
requested information is not readily available in any data/information repository. When
selecting the appropriate JISR asset to meet a CR, the CM element should consider the
following:
b. Step 2 – Collect
(1) This step in the JISR process consists of the actual gathering of data
and information by JISR capabilities and assets. Collection
encompasses the detailed scheduling of JISR tasks to available JISR
assets and the execution of those tasks by JISR capabilities.
(2) JISR assets collect the requested data and information and make
it available for further processing. The CM element needs to consider
all intelligence collection disciplines, JISR capabilities and assets to
satisfy a valid CR.
(1) This step in the JISR process is the conversion of collected data and
information into appropriate readable or useable formats that enable
further exploitation, storage or dissemination.
d. Step 4 – Exploit
(1) Within this step of the JISR process, processed data and information is
further exploited. The time required to conduct exploitation varies
depending on the characteristics of the collection assets. Some JISR
assets accomplish processing and exploitation automatically and
nearly simultaneously with the collection, while other collection assets
may require substantially more time.
(2) There can exist different levels of exploitation for each JISR capability
or asset.The levels range from rapid and preliminary assessment of
collected JISR data or information up to more time consuming in-depth
assessment via reach-back capabilities. The different levels of
exploitation are dependent on the specifications and characteristics of
the JISR capability or asset and its supporting organization and
personnel (near sensor, in-theatre, in reach-back).
(3) The initial level of exploitation is the rapid and preliminary assessment
of collected JISR data or information and forwarding the results
immediately to the commander and/or requester, often in NRT, in
support of current operations. This type of exploitation is usually
conducted by the sensor operator or exploiter associated with the
sensor system or collection capability, but can also be undertaken by
other exploiters having NRT access to collected sensor data. The
exploited data and information are transmitted for further exploitation
within the JISR process and/or the intelligence cycle.
(5) A more in-depth assessment involves using data and information from
multiple JISR assets inside a specific intelligence collection discipline
or JISR capability combined with archived information. This level of
exploitation often requires tools, processing power, and/or additional
specific expertise. It can be time consuming and may be conducted in
the JOA or via reach-back capabilities.
e. Step 5 – Disseminate
(1) The dissemination step within the JISR process involves the timely
provision of JISR results to those who need it, in the requested format,
and through the communication means as specified by the JISR task.
Effective dissemination management is needed to ensure requesters
have access to the disseminated JISR results that are posted,
published, or transmitted.
2. JISR tasking can be deliberate, ad hoc, or dynamic. Relative to planning and mission
execution times, the three types of tasking are depicted in Figure 3.2.
Types of Tasking
3. Deliberate tasking occurs during the standard mission planning process and is
concluded with an approved CTL and the mission order finalisation by the
operations staff. Ad hoc tasking is the process for integrating emerging and urgent
CRs in an already released CTL and prior to mission execution. Dynamic tasking
allows the integration of emerging CRs requiring immediate satisfaction into current
collection operations.
a. The deliberate JISR tasking process begins with validated CRs articulated by
the CM element, based on the ICP, as the main planning tool, with standing
IRs, emerging IRs, RFIs and ISR requests. If the IRM element has confirmed
that the information/intelligence is not available, a CR can be developed. The
CM element would then convert the IR into a CR. Deliberate tasking ends with
the CTL release after approval at the JCMB
b. With the decision to collect, the CM element, who has the CRM authority,
has to determine, if the ISR assets assigned at considered level of command
can fulfill the CRs. If CRs cannot be satisfied by available ISR assets, the CM
element must request collection support from higher and/or adjacent
commands and organizations. In the event JISR assets are available at the
considered level of command, JISR tasks are developed and integrated
directly into mission planning for collection mission tasking.
c. If the sufficient NATO- owned assets are not available and CRs cannot be fulfilled at a
given level of command, Nations-owned assets will be requested by including the CRs
into the CRL. CRs requiring operational level management are consolidated and
d. The CTL is the authoritative collection management document for the theatre. The CTL
is consistent with the joint forces commander’s overall mission priorities, the theatre
collection priorities and provides a list of approved and prioritized JISR CRs, JISR tasks
and as required dynamic re-tasking priorities. The CRs are developed for specific
intelligence collection disciplines (e.g. IMINT, HUMINT, MASINT, OSINT and SIGINT)
as well as collection capabilities/assets. The CTL specifies which intelligence collection
discipline or collection capabilities/assets should be used to collect to assist CM staff
with allocating resources to JISR tasks. The CTL may be published and disseminated
daily in accordance with the operation and/or exercise battle rhythm.
e. Collection decisions demand prioritized requirements due to time constraints and the
finite number of collection, processing, and exploitation capabilities available. This
ensures that limited assets and/or resources are directed against the most critical
requirements.
f. As JISR operations must be coordinated between the different service components and
intelligence and operations staffs, a JCMB is established for this purpose and consists
of the respective intelligence and operations staff members. The JCMB, led by the TCM,
produces and approves the CTL, resolves potential areas of conflict and assigns
execution responsibilities to deconflict and synchronize collection activities. The JCMB
issues priority guidance across the service components to ensure that the overall JISR
effort is coordinated, prioritized, appropriately balanced, and focused on the
commander’s objectives.
g. Based on COM authority, JISR tasks are coordinated with the operations staff for
mission integration, the issuance of orders to the ISR asset for execution of the
collection mission and to ensure the collected data or information will be processed,
exploited, and disseminated. The CM element needs to develop good working
relationships with the originating requester to clearly understand the requirement to
avoid any negative or delaying impacts on execution. The staff must determine the
appropriate method of collection. For example, if IMINT is the appropriate capability to
answer the requirement, the CR must be tailored for imagery collection. Likewise,
SIGINT CRs must be tailored for the appropriate sensors. Additional information may
be required from the requester in order to develop the CR to optimize collection and
maximizing the chances of a successful first time collect.
h. The TCM, or CMA at other levels of command, requires visibility on all validated CRs
generated by subordinate formations and units, to at least two levels below. Although
subordinate formations and units may be able to fulfill their own requirements with their
dedicated ISR assets, they must forward their declared CRs up the chain of command
so that the higher headquarters can coordinate and optimize the use of all available ISR
i. CM element also develops synchronized planning for the PED of the collected data or
information. The CTL and the associated PED plan provides details of the tasks to be
assigned to dedicated and subordinate JISR collection and production units to meet the
CRs. The plan must include details indicating where and how JISR results are to be
conveyed to the requestor, including any release caveats. Contact information for the
requestor and probable JISR collection and production units are also included in the
plan. This plan should specify how JISR assets and capabilities amongst the coalition
are best utilized where collected JISR data or information from one JISR asset and
capability can be appropriately exploited using the PED resources from another JISR
asset and capability either NATO-owned or Nations-owned. Generally, the CRM
authority transitions to the COM authority when the CTL and the associated PED
tasking are passed for mission integration and coordination with ongoing and planned
missions and operations.
j. COM authority starts with mission integration, which corresponds to the timely
collaboration of the intelligence-operations staffs to identify, plan and task ISR assets
achieving the CRs and related JISR tasks. This is where the operations staff integrates
the JISR tasks into mission planning,33 taking in consideration other tactical activities,
in particular addressing air, ground, or maritime battle space management, as well as
force protection aspects associated with the execution details of the JISR task. This
encompasses at the service component levels, mission planning (future plans), mission
tasking (future operations and orders) and the preparation of the mission at the unit
level.
l. The CM element, with the COM authority, manages the different needs of the
subordinate commands, JISR capabilities and assets, completes the tasking step,
conducts the collection step and manages the process, exploit and dissemination steps.
In addition, the CM element also maintains SA on JISR missions being performed and
responds to dynamically changing situations that may necessitate reallocating JISR
assets. Each order must therefore contain detailed instructions sufficient to enable the
successful accomplishment of the mission.
m. The key responsibilities within the COM authority are to manage the operation of JISR
assets across the CPED steps. In addition, the CM staff will assess to what extent JISR
assets have satisfied the CRs. This assessment is accomplished through a combination
of measures of performance (MOP)34 and measures of effectiveness (MOE)35 to
5. Ad hoc JISR tasking. Ad hoc tasking occurs when urgent CRs emerge and there is
still time to adjust an already issued order prior to scheduled execution. CM staff must
quickly validate and prioritize ad hoc requirements to determine which original JISR task
can be cancelled or modified with the least negative affect and then determine how to satisfy
the affected requirements at a later stage. As changes are made to deliberate and planned
tasking, the JISR original requesters must be notified of any modifications or cancellations
due to ad hoc priorities. In addition, modifications to deliberate and planned tasking will
result in the re-prioritization of PED resources.
7. Dynamic JISR tasking. Dynamic tasking occurs when the importance and urgency
of an emerging CR demands immediate attention and redirection of an already collecting
JISR asset. After expeditiously validating the request, a dynamic JISR task is developed by
the IRM&CM staff and next integrated and managed by the COM staff controlling the JISR
assets. Together with the IRM&CM staff, the COM staff will decide which asset and
collection task will be redirected to satisfy the dynamic request. The IRM&CM staff will later
assess the implications of the redirection and determine how to best satisfy the requirements
that were impacted by the tasking. As with ad hoc tasking, dynamic tasking will also result
in the re-prioritization of PED resources.
8. Requesters submit ad hoc and dynamic tasking requests after the deliberate tasking
process has occurred, in an emerging or changing situation and when the CTL is already
produced and endorsed in the JCMB. The ad hoc and dynamic types of requests are
validated and processed by the IRM element, given a higher priority and immediately
forwarded directly to CM element, where the CRs are categorized as either ad hoc or
dynamic taskings. Figure 3.4 illustrates the ad hoc and dynamic JISR tasking process
9. When assets are available and can fulfill the prioritized CR, the ISR task will be
developed by the CM element with CRM authority and forwarded directly to the operations
staff to integrate it into mission planning or integrate it into already prepared and ongoing
missions. For ad hoc JISR tasking, this is accomplished while the operation is being
planned, but has not yet been executed. For dynamic JISR tasking, this is accomplished
once the mission is executed, but with sufficient time to be integrated into the mission as an
additional task.
4.1 Introduction
1. JISR planning is an integral part of the operations planning process (OPP) and must
be included at the onset of all planning activities. NATO missions often require a wide range
of JISR capabilities to obtain optimal JISR results to support operations and missions. This
necessitates having the capabilities, assets, skills, connectivity, tools, and interoperability to
meet information and operational requirements, ensuring a federation of networked-enabled
capabilities and collaborative processes. Having the right capabilities and number of assets
coupled with a comprehensive JISR architecture will provide the commander with the agility
to respond to a constantly evolving environment.
3. NATO’s adversaries will likely implement measures aimed at denying and defeating
NATO JISR capabilities. Commanders should take into account during the planning process
that NATO’s JISR sources, methods, activities, and capabilities should be protected with
effective operational security practices, information security measures, and robust counter-
intelligence.
4. When NATO becomes involved in any type of operation, staffs at all levels of
command need to define, develop and articulate the requirements for JISR assets and
capabilities, C2, personnel and the CIS required for data exchange.
36 The CJSOR is the document/tool that contains the (generic) forces requirements of a commander for a
specific operation. The CJSOR, including preliminary deployment information, must be developed in parallel
with the operational CONOPS. For further information refer to the ACO Comprehensive Operations Planning
Directive (COPD) V2.0, (2013).
2. For any operation, there will be a finite number of traditional intelligence collection
and traditional reconnaissance and surveillance assets, but there are many more potential
non-traditional JISR assets that could be used to fulfil the requirements. Non-traditional JISR
assets are not assigned to a specific JISR task, but can contribute to the intelligence picture
as part of their routine operation. Commanders and staffs need to consider asset availability
in the early stages of planning operations.
3. JISR aims for the integration and harmonization of NATO and national collection
assets at all levels. The data and information collected from one asset may be
complemented by outputs from other types of assets and other results or products to satisfy
information and intelligence requirements. JISR collection capabilities and assets can
operate in all domains and can be characterized as:
4. Commanders need to understand that their requirements will likely exceed the
availability of JISR assets. Consequently, there is a need to prioritize the requirements
based on mission objectives to optimize the use of available capabilities. Commanders must
also weigh JISR capabilities and limitations and especially the time the information is of
value against the mission objectives.
5. During the OPP of a NATO operation, the IRM element develops and maintains
operation-specific PIRs, specific intelligence requirements (SIRs) and essential elements of
information (EEIs)37 as the core elements of the ICP at all levels of command. The CM
element then prioritizes, coordinates determines the scope and quantity of CRs expected
for the operation. This estimate is used to identify the collection, processing and exploitation
capabilities required to support the commander during the operation.
6. JISR requirements contribute to the overall theatre CJSOR and force generation
process. In response to the CJSOR, participating Nations may decide to provide JISR
collection and/or PED capabilities to NATO operations while defining context, constraints
and restrictions for their employment. The commander, with delegated COM authority, is
usually given OPCON over the provided capabilities.
37 For more information on PIRs, SIRs, and EEIs refer to AJP-2 and AJP-2.1.
c. Relevant. JISR education and training opportunities must keep pace with
changes that occur in doctrine, organization, equipment and current operational
needs.
2. The design, establishment and management of JISR architectures for all NATO
operations are based on the following principles and criteria:
d. Compatible. The JISR architecture will be compatible with both current and
future technical constraints and standards, notably for sufficient network connectivity
and appropriate broadband links.
3. An effective architecture must enable the best possible support to ensure adequate
and timely decision making. Therefore, the architecture must allow JISR resources to be
managed and employed in a collaborative manner. This requires federated relationships
using networked capabilities and collaborative processes to effectively support operations
and fulfil commanders’ requirements by ensuring persistence and agility under changing
conditions.
5. In addition, effective JISR requires the capability to store, share and archive JISR
results in compliance with technical and operational standards based on NATO-accepted
formats and procedures. Information Exchange Requirements (IERs)38 for national units and
systems, IER interfaces and standards must be addressed early in the planning process.
7. There must be close communication between intelligence staffs and operations staffs
at the initial stage of the OPP to ensure the JISR architecture is sufficient and optimally
located to enable access to services, applications and databases.
8. Each JISR capability or asset should be fully integrated into the JISR architecture.
JISR assets must have the ability to be responsive to every level of joint C2 (tactical,
operational and strategic) and contribute to the satisfaction of information requirements
ranging from those of tactical commanders to strategic objectives. Assigned PED
capabilities (NATO or national) must be enabled to process and exploit data from theatre
JISR assets and share the results with intelligence elements and requesters at any level to
allow for fusion and support decision-making processes.
9. The respective portions of the OPLAN and concept of operations (CONOPS) will
describe the JISR architecture and the CIS structure necessary for JISR operations. It will
also explain interoperability between JISR-related data sources and the tools used by the
relevant commanders, staffs, units and assets. The architecture will be heavily influenced
by IERs across the operation and between NATO and national headquarters, units and JISR
assets. Defining the JISR architecture in the appropriate planning documents will ensure
visibility within the operations, planning and communications communities and will help
identify and address potential shortfalls. JISR architecture will, at a minimum, include the
following criteria:
38 IERs define the need for information exchange between two parties that support a given process. IERs are
pivotal inputs to the CIS planning process ensuring that all relevant C2 services required in support of the
mission are identified, and adequate planning and provision of C2 services can be achieved. For more
information, refer to AJP-6 (2011) Communication and Information Systems.
f. Dissemination of JISR NRT inputs, raw JISR data, information and JISR
results.
10. Although the basic concept of the JISR architecture is represented in the OPLAN or
CONOPS, further refinement of the architecture will continue for the duration of the
operation.
LEXICON
actor
A person or organization, including state and non-state entities, within the international
system with the capability or desire to influence others in pursuit of its interest and
objectives.
[This term is a new term and definition and will be processed for NATO Agreed status]
analysis
In intelligence usage, a step in the processing phase of the intelligence cycle in which
information is subjected to review in order to identify significant facts for subsequent
interpretation.
[AAP-06, 2015]
NATO Agreed
assigned
To place units or personnel in an organization where such placement is relatively
permanent, and/or where such organization controls and administers the units or personnel
for the primary function, or greater portion of the functions, of the unit or personnel.
[AAP-06, 2015]
NATO Agreed
assigned asset
JISR assets that are under OPCON by the respective level of command, which conducts
the JISR process and is able to task the organic asset. These assets form an integral part
of a military organization and are listed in the unit’s order of battle.
[This term and definition are only applicable in this publication]
collection management
In intelligence usage, the process of converting intelligence requirements into collection
requirements, establishing, tasking or coordinating with appropriate collection sources or
agencies, monitoring results and re- tasking, as required.
[AAP-06, 2015]
NATO Agreed
collection requirement
A validated information requirement, for which the requested information is not already
element
Personnel of the intelligence staff, responsible for conducting specific JISR related activities
and functions.
[This term and definition are only applicable in this publication]
Not NATO Agreed
information
Unprocessed data of every description, which may be used in the production of intelligence.
[AAP-06, 2015]
NATO Agreed
integration
In intelligence usage, a step in the processing phase of the Intelligence cycle whereby
analysed information and/or Intelligence is selected and combined into a pattern in the
course of the production of further intelligence.
[AAP-06, 2015]
NATO Agreed
intelligence
The product resulting from the directed collection and processing of information regarding
the environment and the capabilities and intentions of actors, in order to identify threats and
offer opportunities for exploitation by decision-makers.
[AJP-2, 2015]
NATO Agreed
intelligence cycle
The sequence of activities whereby information is obtained, assembled, converted into
intelligence and made available to users. This sequence comprises the following four
phases:
intelligence requirements
Intelligence requirements provide the rationale and priority for any intelligence activity as
well as providing the detail to allow the intelligence staff to answer the requirement in the
most effective manner. Intelligence requirements should cover the broad scope of
information on the political, military, economic, social, infrastructural and informational
(PMESII) spectrum. The military spectrum will be covered by the commander’s critical
information requirement (CCIRs). Military types of intelligence requirements are: priority
information requirements (PIR), specific intelligence requirement (SIR), essential elements
of information (EEI).
[AJP-2]
intelligence staff
Those personnel who are involved in the direction, collection, production and dissemination
of intelligence through the conduct of the intelligence process.
[AJP-2]
joint
Adjective used to describe activities, operations and organizations in which elements of at
least two services participate.
[AAP-06, 2015]
NATO Agreed
reconnaissance
A mission undertaken to obtain, by visual observation or other detection methods,
information about the activities and resources of an enemy or potential enemy, or to secure
data concerning the meteorological, hydrographical or geographic characteristics of a
particular area.
[AAP-06, 2015]
NATO Agreed
security
The condition achieved when designated information, materiel, personnel, activities and
installations are protected against espionage, sabotage, subversion, terrorism and damage,
as well as against loss or unauthorized disclosure.
[AAP-06, 2015]
NATO Agreed
sensor
An equipment which detects, and may indicate, and/or record objects and activities by
means of energy or particles emitted, reflected, or modified by objects.
[AAP-06, 2015]
NATO Agreed
source
In intelligence usage, a person from whom or thing from which information can be obtained.
[AAP-06, 2015]
NATO Agreed
surveillance
39 AJP-2.
40 This term is a new term and definition and will be processed for NATO Agreed status.
AJP-2.7(A)(1)
NATO UNCLASSIFIED