TACTICAL STRATEGY:
1.Take over from outgoing unit and review int ops & threat/non kinetic/cultural data..battle handoff
2.Confirm what we think we know.
3.Assess locals data..threat..own vulnerability..compare with battle handoff info
4.Report changes
5.ID Int Requirement and Prioritize
6.State Cdrs Intent
7.Conduct population centric and area study and life pattern ..int pltns embedded in patrols tasked
8.Answer Int Requirements...int pltns tasked
9.ID potential targets..nominate white grey black..lists
10.Develop Target Packs
11.Confirm Targets.
///COA SELECTION//
12.Execute Kinetic+Non Kinetic Ops..integrate police EW Higher HQ G2
13.Assess success and collateral damage plus 2nd 3rd order effects
14.After Action Review
15.Change int requirements after int collected while executing ops
16.New Cdrs Intent
That's my continuos running Tactical int ops cycle for CRPF
My
pilot unit will address insurgent tactics not insurgent forces.And the
cdr will be taught to differentiate on knowledge domain..what he thinks
he knows..what he actually knows and what he NEEDS to know.Confirm what
he thinks he knows.Compare with what he actually knows.Then zero to
missing info.Tempo demands simplicity.
No complex architecture. Am simply giving everything a structured form aided by Coy Int Section
Coy level int capability COIN Enduring Effects: