Table of


Normally, the greatest challenge for commanders is to focus the intelligence effort, and to gain dissemination of intelligence to the right place in time for key decisions.

This manual provides the doctrinal framework for synchronizing the Intelligence System of Systems (ISOS), maximizing collection technologies in support of commanders.

The ISOS is a flexible and tailorable architecture of procedures, organizations, and equipment that supports the combat commander by meeting his intelligence needs. Key to this concept is the recognition that current and evolving collection, exploitation, and dissemination technologies provide commanders with an unprecedented capability to truly see the battlefield.

Collection Management

What Is It ?


For Example:

Desired End Effect:

Success Results In:

Consequences of Failure:

Collection Management Sub-Functions

CM includes three distinct sub-functions:

These sub-functions distinguish between internal and external relationships among collection managers, requesters, and collectors during CM operations. Figure 1-1 shows these functional relationships.

At division, corps, and echelons above corps (EAC) there are individual "managers" and sections responsible for each sub-fiction. At brigade, and echelons below brigade, the S2 performs RM and MM, and sometimes AM, himself--often simultaneously.

Requirements Management (RM)

Mission Management (MM)

Asset Management (AM)

Collection Management Process

The collection management process itself consists of the following six steps. Chapter 3 discusses these steps in detail.

The sub-functions of collection management overlap in these steps. Requirements development, report evaluation, and dissemination are the exclusive domain of RM. However, RM and MM both contribute to collection plan development and update. MM and AM both task collection and exploitation resources.

Chapter 3 of this manual discusses in detail each step in the collection management process. We intentionally address RM and MM as functions performed by separate individuals and sections to clearly delineate responsibility. At some echelons this may not be the case; sometimes, one individual or section performs both functions. Chapter 5 discusses who does what at each echelon.

Collection Management and Joint Operations

Joint doctrine (Joint Publication 2-01) divides collection management into two sub-functions: Collection requirements management (CRM) and collection operations management (COM). CRM corresponds directly to RM, with one exception--dissemination. Joint doctrine moves the responsibility for dissemination to COM, the joint equivalent of MM. Chapter 5 addresses conducting collection management in a joint, combined, or interagency environment.

Doctrine Versus Tactics, Techniques, and Procedures

Doctrine, at its broadest reach is descriptive, not prescriptive.

This manual does not serve as a definitive "desktop" handbook for collection managers. Collection management TTP may vary according to mission, organization, echelon, and theater. While we provide current collection, exploitation, dissemination system descriptions, collection "problem set" scenarios, and a representative example of tasking and request formats, the ISOS "revolution of coverage" continues. This, and the complexity of the various problems collection managers face, makes the inclusion of TTP to cover every situation impractical. Every collection manager must adapt the doctrine to his mission, available systems, echelon, and theater of operations.