text: Execution
  6-13. The IO officer monitors IRCs and keeps the G-3 (S-3) informed on overall IO status. The IO officer
  also recommends to the G-3 (S-3) changes to IRC taskings for inclusion in fragmentary orders, as warranted.
  ASSESSING DURING EXECUTION
  6-14. Assessment precedes and guides the other activities of the operations process. It involves continuous
  monitoring of the current situation and evaluation of the current situation against the desired end state to
  determine progress and make decisions and adjustments.
  6-15. The IO officer compiles information from all CPs, the G-2 (S-2), and higher headquarters to maintain
  a continuous IO assessment in the IO estimate. The primary objective of assessment is to determine whether
  IO is achieving planned effects. As the situation changes, the IO officer and G-3 (S-3) make sure IO remains
  fully synchronized with the overall operation.
  6-16. Assessment is continuous; it precedes and guides every operations process activity and concludes each
  operation or phase of an operation. During planning, the commander and staff determine those IO objectives
  to be assessed, measures of performance and effectiveness, and the means of obtaining the information
  necessary to determine effectiveness. During orders production, the IO officer uses this information to
  prepare the IO portion of the overall assessment plan. During execution, the IO officer uses established
  measures of performance and effectiveness, as well as baselines and indicators, to assess IO objectives.
  MONITORING IO
  6-17. The IO officer monitors IRCs to determine progress towards achieving the IO objectives. Once
  execution begins, the IO officer monitors the threat and friendly situations to track IRC task accomplishment,
  determine the effects of IO during each phase of the operation, and detect and track any unintended
  consequences.
  6-18. Monitoring the execution of defend-weighted tasks is done at the main CP because it is the focal point
  for intelligence analysis and production, and because the headquarters mission command nodes are monitored
  there. The IO officer works closely with the intelligence cell, G-2 (S-2), and IO working group representatives
  to provide a running assessment of the effectiveness of threat information efforts and keeps the G-3 (S-3)
  and various integrating cells informed.
  6-19. With G-2 (S-2), G-3 (S-3), and fire support representatives, the IO officer monitors attack-weighted
  IO execution in the tactical CP and the main CP. For example, during combined arms maneuver, the IO
  officer is concerned with attacking threat command and control nodes with airborne and ground-based
  jammers, fire support, attack helicopters, and tactical air. After preplanned IO-related HPTs have been struck,
  the strike's effectiveness is assessed. Effective IO support of current operations depends on how rapidly the
  tactical CP can perform the targeting cycle to strike targets of opportunity. The G-3 (S-3) representative in
  the tactical CP keeps the main CP informed of current operations, including IO.
  6-20. To organize and portray IO execution, the IO officer and working group use several tools, to include:
  * IO synchronization matrix.
  * Decision support template.
  * High-payoff target list.
  * Critical asset list and defended asset list.
  6-21. IO officer and working group use either the synchronization matrix from the IO appendix or an extract
  containing current and near-term IO objectives and IRC tasks, depending on the complexity of the operation.
  The synchronization matrix is used to monitor progress and results of IO objectives and IRC tasks and keep
  IO execution focused on contributing to the overall operation. The decision support template produced by
  the G-3 (S-3) is used by the IO officer to monitor progress of IO in relation to decision points and any
  branches or sequels. The IO officer maintains a list or graphic (for example, a link and node diagram) that
  tracks the status of IO-related HPTs identified during planning. The IO officer uses the critical asset list and
  defended asset list to monitor the status of critical friendly information nodes and the status of critical systems
  supporting IO, for example: electronic warfare systems, military information support operations (MISO)
  assets, and deep attack assets.