1386
2-17. Information collection is a continuous feed of relevant information that facilitates the commander’s 1387
situational awareness, and enables him to make better decisions. Information collection involves the entire staff.
1388
The CAB S-3 is the chief integrator of the information collection process. The S-2 assists the S-3, along with 1389
the rest of the staff. The CAB XO supervises synchronization of the information collection plan and its 1390
subsequent execution of the following collection tasks, which are described in detail in FM 3-55:
1391
Plan requirements and assess collection.
1392
Task and direct collection.
1393
Execute collection.
1394
P
LANR
EQUIREMENTS ANDA
SSESSC
OLLECTION 13952-18. The CAB commander and staff develop information requirements to answer uncertainties about the 1396
enemy or other conditions of the operational environment that could influence planning or execution. The staff 1397
develops information requirement (IR) during mission analysis and war gaming as part of the MDMP. One 1398
result of the MDMP is linking the situation and event templates with named areas of interest (NAIs) and 1399
targeted area of interest (TAIs), both of which are linked to DPs for the commander. The commander approves 1400
selected IR as his CCIR for his decision points (DPs).These NAIs, TAIs, and DPs are expressed on the Decision 1401
Support Tool (DST). DSTs link the information the commander needs to know with the geographic location 1402
where the information can be found, and the time the information is likely to be available (based on the event 1403
template). The CAB subsequently receives specific information requirements from the ABCT. (See Figure 2-1.) 1404
Finally, DSTs could have specific RFIs from subordinates and adjacent units. Placed together, these IR drive 1405
information collection operations.
1406
1407
Figure 2-1. Information requirements 1408
2-19. Regardless of the source, each IR should specify—
1409
WHAT (activity or indicator).
1410
WHERE (NAI or TAI).
1411
WHEN (time that the indicator is expected to occur and the latest time the information is of value 1412
[LTIOV]).
1413
WHY (justification - what decision is the PIR linked to).
1414
WHO (who needs the results).
1415
2-20. As the staff gathers all of the IRs and PIRs, they sort the requirements to eliminate redundancies,,and 1416
prioritize them to assist in allocating resources. The commander then re-evaluates each requirement and 1417
finalizes his CCIR. This is a continuous process; as a given CCIR is answered or the operational situation 1418
changes, other CCIRs usually are generated.
1419
2-21. Ideally, each IR is detailed and specific enough to facilitate collection. Once the commander approves the 1420
IR, he breaks the IR down into indicators. He then develops specific information requirements to ask very 1421
specific questions about indicators. Finally, the commander tasks these indicators to collectors and, taken 1422
together, they answer the larger question. For example: one of the CAB commander’s PIR is “Will the enemy 1423
regiment attack through avenue of approach 2 with battalions abreast, or from the march?” This is a broad 1424
question and many indicators could lead to its answer. Specific information requirements to support this PIR 1425
might include:
1426
Will enemy units of 3-5 combat vehicles enter NAIs 11, 12, and 13 between 130400MAR and 1427
130700MAR?
1428
Will enemy battalion #2 move from its assembly area at NAI 7 prior to 130230MAR?
1429
Identification of second enemy battalion (over 40 BMP2s) in NAI 11, 12, or 13.
1430
D
ETERMINEI
NITIALCCIR
S ANDEEFI
1431
2-22. Determining initial CCIRs and EEFI is the most important prerequisite for information collection 1432
planning. The staff refines the list of requirements they derive from the initial analysis of information available 1433
and from intelligence gaps identified during IPB. They base this list on higher headquarters tasks, commander’s 1434
guidance, staff assessments, and subordinate and adjacent unit requests for information. (Refer to FM 3-55 for 1435
more information.) 1436
2-23. The staff then nominates these requirements to the commander to be CCIRs and EEFI. Commanders 1437
alone decide what information is critical based on their experience, the mission, the higher commander’s intent, 1438
and input from the staff. The CCIRs are the primary focus for information collection activities.
1439
D
EVELOP THEI
NITIALI
NFORMATIONC
OLLECTIONP
LAN 14402-24. The initial information plan is crucial to begin or adjust the collection effort to help answer requirements 1441
necessary to develop effective plans. The initial information collection plan sets information collection in 1442
motion. (A sample information collection matrix, formatted under the targeting method of decide, detect, 1443
deliver, and assess (D3A) is depicted in Figure 2-2.) Staffs may issue it as part of a warning order, a 1444
fragmentary order, or an operation order. As more information becomes available, staffs incorporate it into a 1445
complete information plan to the operation order.
1446
2-25. At this point in the MDMP, the initial information plan has to be generic because the staffs still must 1447
develop friendly COAs. The basis for the plan is the commander’s initial information collection guidance, the 1448
primary information gaps identified by the staff during mission analysis, recommendations from the targeting 1449
meeting (see paragraph 8-43 for more information on targeting), and the enemy situational template developed.
1450
1451
Figure 2-2. Information collection matrix 1452
P
ERFORMR
ISKA
SSESSMENT 14532-26. The commander must consider whether the gathering of CCIR is worth the risk of compromising EEFI.
1454
This is often the case during surveillance of the maneuver objective. Commander emphasis on EEFI might 1455
cause conflicts with the information collection plan. This requires that the commander make a tactical risk 1456
assessment, and may cause him to change his CCIR or adjust his assigned sensor.
1457
2-27. By the nature of their missions, information collection assets must be placed where they might be lost to 1458
enemy action. The commander makes the decision whether the intelligence to be gained outweighs the risk to 1459
the information collection asset.
1460
D
EVELOP THEF
INALI
NFORMATIONC
OLLECTIONP
LAN 14612-28. Once the CAB chooses an asset to collect information for an IR, planners turn the special information 1462
requirements into a task for a subordinate unit. This task is a directive statement that tailors the reporting criteria 1463
to the collection capabilities of the tasked unit. The Information collection plan is developed through these asset 1464
tasking. Below are two examples:
1465
Example 1, mixing reconnaissance management:
1466
A special information requirement could ask, “Is the enemy artillery battalion (over 12 2S-1s) 1467
located in NAI 8 between 040800 and 052000MAR?”
1468
An information collection task to a scout team might state, “Report the presence of 2S-1 artillery 1469
systems in NAI 8 between 040800 and 052000MAR. LTIOV: 052200MAR.”
1470
An information collection task to a UAS team might state, “Report movement in NAI 8 between 1471
040800 and 052000MAR. LTIOV: 052200MAR.”
1472
Example 2, mixing reconnaissance management:
1473
A special information requirement could ask, “Is the Gordian insurgency using the mosque in 1474
NAI 5?”
1475
An information collection task to an Infantry patrol might state, “Report the presence of males in 1476
NAI 5 outside normal prayer hours (0545, 1215, 1430, 1700, 1930) between 011200 and 1477
071200NOV. LTIOV: 071400NOV.”
1478
An information collection task to a Prophet team might state, “Report any radio transmissions in 1479
NAI 5 between 011200 and 071200NOV. LTIOV: 071400NOV.”
1480
2-29. Units prioritize information management tasks for each specific asset. For example, an information 1481
collection task that is the number one priority for an UAS might be lower in priority for a scout team. Figure 2-3 1482
depicts an information collection tasking matrix.
1483
1484
Figure 2-3. Information collection tasking matrix 1485