search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
CLOUD FORMATIONS


IMPLEMENTATION AND EXPERIMENTATION Te Network Cross-Functional Team is working with the Army’s Enterprise Cloud Management Agency (ECMA), Project Manager Mission Command (PM MC) and others to make this tactical hybrid capability a reality. In the beginning, the team worked with PM Mission Command on a pilot to see if current software could be served from a cloud without operating outside of current contract constraints. PM MC, the Network Cross-Functional Team and the Pennsylvania National Guard proved it was possible in a Non- classified Internet Protocol (IP) Router Network (NIPRNet) environment. Others expanded on that capability once Secret IP Router Network (SIPRNet) capabili- ties were available from ECMA’s cArmy service, which provides an authorized and accredited set of general-purpose multiven- dor cloud environments that host Army IT services for multiple classifications.


Initially, PM Mission Command, the Pennsylvania Army National Guard and the Network Cross-Functional Team collaborated on a pilot to explore the technical possibility of placing currently fielded Mission Command Information Systems, the core of the Command Post Computing Environment, in a NIPRNet cloud—because of accreditation timelines, the pilot could not expand into SIPRNet. Te Tactical Cloud Pilot, Increment I


validated the hypothesis that units could be trained on new software without being issued associated hardware. COVID-19 constraints forced an adaptation that also proved that, while not ideal, such train- ing could be done remotely. Others took notice of the success and began work on their own adaptations. One U.S. Army Training and Doctrine Command use case is attempting to expand the number of users and locations, while units are striving to exercise these capabilities in tactical scenarios to inform the require- ments community.


Today, we are leveraging the XVIII Airborne Corps’ Project Ridgway to pilot hosting capabilities through cArmy, with Amazon Web Services in the 101st Airborne Division and Microsoft Azure in the 82nd Airborne Division. As part of Project Ridgway, which encompasses XVIII Corps data and software modern- ization efforts, these units are providing realistic use cases and putting them to the test with current and legacy software during various experiments and field exer- cises on a mix of hyperscale, commodity and vendor on-premises cloud solutions.


The Network Cross-Functional Team also just began working with I Corps on upcoming events for the spring of 2022. Upon successful I Corps implementation, the Army will have initially experi- mented or piloted with as-is software and


configuration in at least one of the two cArmy cloud options from the battalion all the way up through the corps and brigade echelons, and division in the other.


What value does this bring to the Army? These pilots demonstrate possibility. While not the ideal or most fiscally effi- cient arrangement of software, with the episodic nature of exercises and operations, the Army can put cloud computing to use to enable a persistent, real-time mission command environment delivering those resources as a service to the total Army. When online, every unit asset could have secure access to the same common oper- ating picture of resources and capabilities. In a contested environment, critical data and services for maneuvering capability will remain with the units geographi- cally. However, much work still must be done to make this a feasible option for any program of record. In general, fielding to the cloud with as-is software is currently cost prohibitive.


CONCLUSION Tere is still much work to be done, mainly with the key tool that creates, consumes and disseminates our data: software. With the availability of dynamic computing and storage paradigms enabled by cloud computing comes a new set of challenges for how we use software. Te software that the tactical Army currently owns and operates was not built to be run in


Cloud has become a way to offload expertise requirements and hardware investments while allowing for instant flexibility—if you need more computing and storage resources, you pay for them, click a button and they are instantly available.


34 Army AL&T Magazine Spring 2022


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