KEY
AFATDS: Advanced Field Artillery Tactical Data System
AMDWS: Air and Missile Defense Workstation AMPS: Aviation Mission Planning System BCS3: Battle Command Sustainment Support System
CPOF: Command Post of the Future C-RAM: Counter-Rocket, Artillery, Mortar DCGS-A: Distributed Common Ground System- Army
FSR: Field service representative JBC-P: Joint Battle Command-Platform JWARN: Joint Warning and Reporting Network JADOCS: Joint Automated Deep Operations Coordination System
OSRVT: One System Remote Video Terminal PSDS2: Persistent Surveillance and Dissemination System of Systems
SWAP-C: Size, weight and power – cooling TAIS: Tactical Airspace Integration System TIGR: Tactical Ground Reporting TMC: Tactical Mission Command UASGCS: Unmanned Aircraft System Ground Control Station
FUTURE VISION
The Army Operating Concept, “Win in a Complex World,” envisions an expeditionary, agile force ready to be task-organized and deployed on short notice to austere locations, and capable of conducting operations immediately upon arrival. But today’s complex, hardware-dense assortment of information systems slows and weighs us down. The COE aims to change that by bringing tactical capabilities closer to what users experience with their integrated, lightweight commercial devices. (SOURCE: Denise Rule, PEO C3T)
to reflect the COE’s system-of-systems approach. All of this groundwork requires intensive cooperation across the Army acquisition, requirements and test communities, along with the Army staff.
But as challenging as this evolution is, Army senior leaders agree that we can’t stick with the status quo. Today, Army informa- tion (IT) systems are developed individually and on their own timelines, with significant redundancy in hardware and soft- ware. Tey are integrated at a test facility after the fact, and it can take months or years to certify integrated capability. After fielding, when a program needs to upgrade hardware or cus- tom software, the Army must send out a specialized team of field service representatives, often at considerable expense, to execute the update. It’s a model that worked well for many years,
but risks leaving the Army behind in today’s software-driven world—where consumers can download apps, update security settings or install the latest version of an operating system over the air in a matter of minutes.
Tink of the COE as a new playbook for how Army IT products are built and deployed. Following the open systems architecture approach of companies like Apple and Google, the COE estab- lishes a common foundation of software, services and interfaces across key systems, which developers use to make different capabilities interoperable “out of the box” rather than having to integrate them down the line. Te COE also includes software development kits that provide third parties the means to create new applications over time to meet changing technologies and operational needs.
ASC.ARMY.MIL 71
SCIENCE & TECHNOLOGY
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
