DESTINATION: INTEGRATION
COE-compliant systems now in the field, and an enhanced version is on track for delivery as a critical part of the Army’s Mission Command Network of 2020.
Te COE is not itself a POR, but rather a system of systems that applies standards and an open architecture to unite exist- ing programs, with the goal of delivering technologies in a more user-friendly, cost- efficient way. In an environment where most acquisition guidance and legislation is focused on PORs, the COE represents a major cultural change for the Army.
Because of the sheer number of systems, technologies and organizations involved, it requires extensive collaboration and governance to synchronize capabilities for deployment in order to achieve the desired user experience.
But the pain comes with significant pay- off. As in the Tesla model, the COE’s software-driven approach to support and sustainment will enable the Army to con- tinuously improve capabilities over time by delivering updates to applications. Tis does more than finally bring the Army in line with commercial best prac- tices. It also will allow us to keep up with our own pace of change as tactical units become more expeditionary, demand more agile command posts and extend the network down to the Soldier level.
A NEW PLAYBOOK A fairly new company, Tesla Motors had the advantage of starting out in 2003 using current business models of build- ing integrated systems from the ground up. Te Army, on the other hand, has needed to evolve by adapting current
business models to hundreds of existing systems in various configurations.
To effectively manage this dramatic
change, the assistant secretary of the Army for acquisition, logistics and tech- nology (ASA(ALT)) has carved the COE into six functionally based computing environments
(CEs), led by program
executive offices: 1) Command Post, 2) Mounted, 3) Mobile Handheld, 4) Sensors, 5) Real-Time/Safety Critical/ Embedded, and 6) Data Center/Cloud/ Generating Force. At
the ASA(ALT)
headquarters level, the System of Systems Engineering and Integration (SoSE&I) Directorate has the responsibility to implement COE by providing enterprise- level system-of-systems engineering and architecture products, governance, syn- chronization and execution oversight.
Within each CE, there are anywhere from six to 53 different PORs, each with a separate project or product manager responsible for a migration plan to bring the system into COE compliance. Often, these plans involve multiple steps to com- plete the evolution from current “thick client” systems to Web-based software applications. Tis incremental approach is necessary but also complex; it results in multiple versions of the same CE that reach readiness for fielding at different times and then must be synchronized for deployment as part of the overall COE.
COE IN ACTION
SFC Teddy Scott, field artillery data specialist with the U.S. Army Operational Test Command’s Integrated Test and Evaluation Test Directorate, uses the CP CE fires widget during a risk reduction evaluation event at Fort Bliss, Texas, in November 2015. “Web-based widgets mirror a Web page you would use every day,” said Scott, who generated fire support using the Advanced Field Artillery Tactical Data System and viewed a common map of the engagement area using CP CE version 2, one of six computing environments that make up the COE. (U.S. Army photo by Devon Bistarkey, PEO C3T)
To support these migrations, the Army had to make initial investments in improved infrastructure such as com- mon software for maps, chat and other functions, and high-performing servers that can store and process data previ- ously managed by multiple, individual machines. We had to adopt common technical standards that affect current PORs as well as future capabilities, while tailoring program management timelines
70
Army AL&T Magazine
April-June 2016
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
