text: Intelligence Staff Support
  COLLECTION MANAGEMENT FUNCTIONS
  The collection management functions—requirements management, mission management, and
  execution management—provide a useful way of viewing collection management as a whole. They also
  provide a potential means of structuring the collection management team and filling positions. These
  functions divide those processes and tasks associated with collection management to assist the collection
  management team in collaborating with and synchronizing information collection across the staff, various
  echelons, and other units and organizations.
  Army and joint doctrine have their own doctrinal models for the collection management functions. The
  Army developed its model (except for execution management) based on its tactical-level point of view; the
  joint force developed an operational-level model. Similar to the intelligence process, each model represents
  a framework that guides thought; they are not prescriptive. Units can use either the Army or joint model
  based on whichever is most useful to their needs. (See ATP 2-01.)
  A Tactical-Level Model
  Collection management teams consider the commander’s information collection guidance, information
  requirements (which become intelligence requirements), IPOE outputs, and intelligence analysis in the
  context of friendly operations in order to develop an effective collection management plan. During collection
  management, the three functions effectively divide the collection management effort, ensuring its success.
  (See figure 5-3.)
  Figure 5-3. Collection management using the Army tactical-level model
  An Operational-Level Model
  JP 2-0 describes the distinct functions of collection requirements management (CRM), collection
  operations management (COM), and collection orchestration in a joint intelligence context and provides some
  useful and detailed techniques associated with these functions. Units can adapt this joint operational-level
  model to Army operations with some modifications. For example, units can use this model at higher echelons
  during inherently joint operations or during operations that require significant interactions with a joint
  headquarters.