SOLDIERS OPERATING A COMMON INTERFACE REQUIRE SHORTER TRAINING CYCLES, AND THE COMMON VIEWER AND COMMON MAP REQUIRES JUST ONE LICENSE, INSTEAD OF MANY, FOR APPLICATIONS THAT PREVIOUSLY WERE SEPARATELY HOSTED.
Following the mandatory safety protocols to avoid friendly fire, software programs like the Advanced Field Artillery Tactical Data System (AFATDS) play a crucial role in enabling the guns to accurately select and fire the right ammunition.
C
As the world of technology changes every 18 months, how does the Army keep up? How do we provide the best product for our Soldiers and the best value for the taxpayers? Historic acquisition processes have been optimized for hardware devel- opment and procurement, but not scaled to coincide with the military’s increased demand for software and Web-based capabilities. To incorporate more agility into the acquisition process, the Army’s acquisition community is planning to pilot the 2009 Defense Science Board- recommended acquisition process for software in the AFATDS Increment II development process.
Te AFATDS program is managed by Product Director Fire Support Command and Control (PD FSC2), under Proj- ect Manager (PM) Mission Command
old steel on target is the only important metric of success for a field artillery Soldier in the heat of combat.
within the Program Executive Office Command, Control
and Communica-
tions – Tactical (PEO C3T). PD FSC2 develops and manages a suite of sys- tems that plan and execute the delivery of both lethal and nonlethal effects and fires; the systems include the Joint Auto- mated Deep Operations Coordination System, Centaur, the Gun Display Unit – Replacement, the Lightweight Forward Entry Device, and the Pocket-Sized For- ward Entry Device (PFED), which is likely to follow AFATDS as a pilot par- ticipant to coincide with its transition to software-based capabilities.
A NONTRADITIONAL APPROACH With the Army Acquisition Executive’s authorization anticipated for spring 2013, the AFATDS pilot will come at a critical time to satisfy DOD’s push for more efficient business practices and better buying power across the Armed Forces. It also correlates to the Army’s creation of a Common Operating Environment, an approved set of computing technologies and standards that enable the rapid development of secure and interoperable applications across several defined computing environments.
PM Mission Command is charged with weaving together all the warfighting capabilities across several computing environments including the Command Post Computing Environment (CP CE). In addition to fires planning, the CP CE includes maneuver, sustainment, protec- tion and intelligence capabilities.
As a launching point, the AFATDS pilot will incorporate the existing acquisition process, beginning with the Materiel Development Decision, the formal entry point into all acquisition submissions that assigns a program to a specific PEO. From there, the new Information Technology (IT)
acquisition approach
will follow the capabilities development process described in the Joint Capabili- ties Integration and Development System Manual (online at
https://acc.dau.mil/ CommunityBrowser.aspx?id=530432), and will meet the requirements of “IT Box” capabilities as determined by the combat IT development community.
Unlike a traditional acquisition program, the pilot IT acquisition approach elimi- nates the formal production and fielding milestone decision reviews at Milestone C. It incorporates multiple Full Deploy- ment Decisions to field
incremental
ASC.ARMY.MIL 35
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
