DIGITAL TRANSFORMATION
“CAMO allows its customers to accurately see their cloud spend and usage in near-real time and gives them the ability to take action by supplementing funds and optimizing their cloud usage.”
it provides architecture templates to reduce design costs and envi- ronment complexity.
“When customers first approach us, we put them through the CMAP intake process. From there, we run them through a detailed course on what they’ll need from inception to twilight. Tat mission owner will then get a tailored set of instructions and a phased approach specific to their needs,” said Pushparani Jayapal, chief, Cloud Enablement Division, Army CIO.
Te Enterprise Cloud Management Agency (ECMA), a field operations agency within the OCIO, has migrated 45 applica- tions from milCloud 2.0 to cARMY in fewer than 100 days through the CMAP process. ECMA is also supporting the Program Executive Office for Enterprise Information Systems to tailor CMAP and accommodate their needs, along with other big projects, like using CMAP in gearing up for a data center closure in 2022.
RAPID CLOUD SECURITY CReATE enables Army software teams to get secure, resilient and scalable applications in the hands of their users more quickly. CReATE provides a suite of development, security and opera- tions tools, services and pre-built paths to production.
“As an example, in support of the Army Data Plan, cARMY and CReATE are maturing in capability to enable rapid soft- ware development and interoperability natively in the cloud that meets immediate warfighter needs,” said Lauren Pavlik, chief, Data And Software Division, Army CIO.
CReATE accounts for application security earlier in the software development life cycle, allowing the Army to deliver cloud tools to the warfighter much faster. In today’s environment, security must be at the forefront of application and platform development. It also must be woven into every step of the software develop- ment process and delivered continually.
Te Army Futures Command Software Factory, a primary stakeholder and partner with CReATE, has been using the envi- ronment since 2021 and today has more than 13 applications that have gone to production using one of the CReATE authorized pipelines for continuous delivery and deployment. Te CReATE platform has allowed for Software Factory application teams to take an application from final testing to production, passing all security controls, within as little as three weeks, albeit depen- dent on the complexity of the application and system. Currently, CReATE stakeholders are from over 20 different organizations, which include more than 2,500 users and 300 projects.
CONCLUSION Te Army is modernizing its technological landscape every day. As technology advances at lightning pace, data and data sets are the digital ammunition of the future. ECMA, within the OCIO, is continuously driving data, software and process transformation to deliver a secure, globally domi- nant cloud ecosystem to create a digitally focused Army.
PAUL B. PUCKETT III was the director of the Enterprise Cloud Management Office at the Office of the U.S. Army Chief Information Officer from 2019 to 2022. He served as the principal adviser to the CIO and other senior Army leaders on the Army’s cloud strategy. He holds an M.S. in systems engineering from Te George Washington University and a B.S. in computer management information systems from Liberty University.
https://asc.ar my.mil
23
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
