USAICoE and PEO IEW&S conducted a detailed requirements crosswalk based on current programs and quick-reaction capabilities. It was determined that Multi-INT requirements to support MfT operations were already embedded in


intelligence system Documents, as well as


requirements for sensor data ingestion and mission command.


GROUND LEVEL INTEL


Much of U.S. and Coalition Forces’ human intelligence is gathered at the lowest echelons on the tactical edge. Here, LTC Russell Clark (right), a New York Army National Guard Soldier mentoring the Afghan National Police (ANP), meets with village elders in April after ANP officers completed a cordon- and-search operation in Afghanistan’s Dand district, south of Kandahar. (Photo by LTC Russell Clark, New York Army National Guard)


Te HUMINT and SIGINT collection, Processing Exploitation Dissemination, and other sensor capabilities are contained in the current Counterintelligence and Human Intelligence Automated Reporting and Collection System (CHARCS), Biometrics/Forensics, and Prophet Electronic Support and Control program requirements.


In an effort to curtail the time it would take to get these critical capabilities into the hands of the MfTs and allow them to be more effective, the Program Executive Office Intelligence, Electronic Warfare, and Sensors (PEO IEW&S), in conjunc- tion with its partners in the requirements community, embarked on an agile engi- neering process that could save valuable time and best identify materiel solutions.


“Te process is leveraging existing program requirements and limited inte- gration to develop an equipping strategy


that provides collaborative multi-intel- ligence capabilities to the MfTs,” said LTC Jonathan Slater, Product Manager Prophet within PEO IEW&S. “We are looking to share processing and com- munications


capabilities, enabling the


unique Intelligence Soldier to cross-cue and rapidly share critical information.”


To ensure that the MfT is properly equipped, existing intelligence and communication capabilities need to be incrementally modernized and integrated into mission-capable packages.


REHEARSAL OF CONCEPT To support the increasing numbers of MfTs, it was determined that a rapid equipping strategy was needed, referred to as Pursuit and Exploitation (P&E). Te USAICoE, headed by TRADOC Capability Manager Intelligence Sensor, in conjunction with PEO IEW&S supported by PEO Command, Control, and Communications – Tactical and PEO Enterprise Information Systems, led a Rehearsal of Concept (ROC) Drill to initiate the rapid acquisition process. Te drill adhered to system-of-systems engineering (SoSE) principles.


Te ROC Drill was very similar to a Customer Interview in the system engineering process,


led to the creation of


Capability


Development Documents and Capability Production


in which require-


ments are gathered and functionally decomposed. It


a Capability Needs (CNs) list. More than 200 CNs were collected, high- lighting capabilities required to support MfTs through all phases of operations including humanitarian missions. Tose


ASC.ARMY.MIL 41


ACQUISITION


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208  |  Page 209  |  Page 210  |  Page 211  |  Page 212