IRREVERSIBLE MOMENTUM
THE MAIN CONVERSATION
Raj G. Iyer, Ph.D., speaks to the audience at the Cyber Security Summit held in Wiesbaden, Germany, July 26. The summit brought together professionals from military and civilian backgrounds to discuss cybersecurity practices and technology that will increase readiness for the U.S. Army. (Photo by Michele Wiencek, U.S. Army Europe and Africa)
Army, as evidenced by some of the struggles with programs like the Integrated Personnel and Pay System – Army.
kinetic versus nonkinetic responses. Te Army has deployed several prototypes—including our science-and-technology effort called Rainmaker and other existing solutions, such as Gabriel Nimbus—at Project Convergence 22 to validate the solutions, especially in contested and denied, degraded, intermittent or limited environments.
ADVANTAGE, ARMY Te Army will also assess the data fabric to see if it can meet Title 10 requirements for things like business health metrics and executive analytics that are currently performed by our Army Vantage data platform. Army Vantage saw the greatest adoption of the platform in the 2022 fiscal year, enabling data democ- ratization to more than 38,000 users worldwide who used the platform. To date, the users have built hundreds of dashboards and analytics products enabling readiness reporting, vaccine tracking, noncombatant evacuation operations tracking from Afghanistan, contract de-obligations, and most recently was used in support of operations in Ukraine by the XVIII Airborne Corps. As the most robust data platform in the DOD, we have shown that getting a user-friendly tool to users can enable the Army to become data-centric at all echelons of the Army, not just for senior leaders.
Te Army has committed to fully adopting and implement- ing DevSecOps. Whether this is for business systems or tactical systems, the advantages that come with Soldier-centered design and Agile software development to deliver operational capability into the hands of real users in short cycles are critical to ensuring that the eventual product meets user needs. A multiyear big-bang approach to software development has not worked well for the
14 Army AL&T Magazine Winter 2023
DevSecOps is also a key enabler to ZT since the software can follow a continuous authority-to-operate model, thereby elimi- nating the months of paperwork and the approval process before the system can be fielded. Te Army CReATE DevSecOps plat- form, built in cARMY, is our accredited solution that can be used by Army and industry software development teams.
Te Army Software Factory in Austin, Texas, an early adopter, has shown that, when CReATE is used, the applications can be in the hands of Soldiers in days instead of months. But for the Army to scale DevSecOps, we need to also reform other acquisition processes. Tis is where the Army will focus in the 2023 fiscal year to adopt the software-acquisition pathway and answer the question of whether the Army will ever transition a piece of soft- ware into sustainment if we accept that “software is never done.”
Our biggest pilot to validate DevSecOps in the 2023 fiscal year is through the Enterprise Business Systems ‒ Conver- gence program. Tis pilot helped my office shape the strategy for DevSecOps. Trough a nontraditional acquisition process, my office leveraged a big-bang approach that would be deliv- ered by the 2027 fiscal year. At the conclusion of this period, Enterprise Data System Catalog (EDSC) will follow a continu- ous-delivery and continuous-integration model that will ensure software is continually modernized and will never transition to sustainment. Most recently, the Army was able to turn around a struggling program for tuition assistance called Army IgnitEd by following Agile methodologies.
INSTITUTIONAL TRANSFORMATION Te success of digital transformation depends on how well the Army can reform our supporting institutional process. Greater centralization through the cloud requires a pivot from the histor- ically decentralized nature of executing programs in the Army. It requires greater coordination and synchronization across stake- holders to achieve consensus-based decisions.
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
