COMPUTING CONVERGENCE
MFoCS, developed to converge separate computing functions into a single architecture, will run JBC-P and other C4ISR applications. (Photo courtesy of DRS Technologies Inc.)
A
pple’s iPhone took a standard architecture and improved it, then provided a soft- ware development kit (SDK)
that enabled third-party developers to quickly and inexpensively create appli- cations, or “apps,” that deliver weather, social media, games and more. It worked intuitively, at the touch of a finger and with little or no instruction. By deliver- ing the power of the Internet when and where we wanted it, apps revolutionized information delivery and had us all say- ing, “Tere’s an app for that.”
Tat kind of “smart” is the Army’s objec- tive as it moves forward with its Common Operating Environment
(COE). With-
out sacrificing warfighter capability or information security, but recognizing the need to converge multiple systems onto a
common architecture, the Army is using a standards-based approach to try to pass
“the iPhone test”—provide the intuitive interface and rapid delivery with the common look and feel of the smartphone.
COE is an approved set of computing technologies and standards that enable the rapid development and execution of secure and interoperable applications across a variety of computing environments. Established in 2010 by the Army’s chief information officer/G-6 and the assis- tant secretary of the Army for acquisition, logistics and technology, the COE guide- lines support the Army’s 30-year strategic modernization approach. Te COE con- sists of six computing environments: the data cloud, command post, mounted or platform, mobile, sensor, and real-time safety-critical or fires and missiles.
Te COE infrastructure services, defined set of standards, and processes act as a platform and playbook for industry part- ners, government program managers and third-party developers. Te COE sets the foundation to enable rapid develop- ment of a stable, secure infrastructure, allowing the Army to field capabilities quickly while creating a long-term evo- lutionary plan that is sustainable and affordable. Currently, integrated develop- ment environments (IDEs) and SDKs are left to the discretion of the developer. Te CEs introduce a standard set of DOD- approved IDEs and SDKs for third-party developers, allowing for innovation and rapid transition of capability.
THE TECH-SAVVY SOLDIER Tis model of doing business goes a long way toward meeting the expectations
TOWARD GREATER INTEROPERABILITY
A Soldier from 2nd Brigade Combat Team (BCT), 1st Armored Division (2-1 AD) uses a Nett Warrior device in November 2013 during Network Integration Evaluation (NIE) 14.1 at Fort Bliss, TX. The Army expects greater alignment of JBC-P with the well-known Android-based infrastructure to boost interoperability between the MCE and the mobile, handheld computing environment found in Nett Warrior. (Photo by Nancy Jones-Bonbrest, PEO C3T)
ASC.ARMY.MIL
59
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
