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
THE FINOPS REVOLUTION


I


n 2018, then-Secretary of the Army Ryan McCarthy made a significant decision to support the migration of the Army’s finance and logistics


systems from on-premises data centers to commercial cloud computing facilities. Since then, the cloud revolution has taken firm hold across the service, bolstered by the establishment of the Enterprise Cloud Management Agency in March 2020 and the recent publication of updated guid- ance within the Army Cloud Plan 2022.


One of the seven strategic objectives of the plan is to provide cloud cost transparency and accountability. To prevent underuti- lized services and unexpected, avoidable costs, the plan says the Army will use “a combination of enterprise-provided


common services and cloud consumption tracking for all cloud consumers.”


One still evolving cloud financial manage- ment discipline that’s slowly being adopted by the federal government, including the Army, is financial operations—coined FinOps. FinOps is an evolving cloud financial management discipline and cultural practice that enables organiza- tions to maximize business value and collaborate on data-driven spending deci- sions, employing cross-functional teams to work together to maintain financial control while also ensuring rapid deliv- ery of capability. Te concept of FinOps helps organizations manage their spend- ing on cloud infrastructure and services responsibly. It is a way of tracking and


managing variable costs. Tis makes it easier for program, technical and financial teams to work together and make intelli- gent choices about the most efficient use of funds.


Te Program Executive Office for Enter- prise Information Systems (PEO EIS), which migrated the Army’s massive General Fund Enterprise Business System (GFEBS) to the cloud in 2020 and has conducted several more migrations since then, has put a FinOps framework and practice in place over the past two years. Trough this framework, the Army is now effectively monitoring and manag- ing cloud infrastructure and services contracts related to cloud computing. Tis has proven to reduce costs, improve performance and maximize strategic cloud modernization objectives.


To manage the service’s cloud infrastruc- ture budget in years to come, the Army needs the agility and scalability that the FinOps revolution provides.


EVOLUTION BEFORE REVOLUTION As cloud computing has become more widespread in both the public and private sectors, organizations have begun look- ing for ways to leverage cloud services. Te goal is to maximize both techno- logical and cost potential. Cloud-based applications enable real-time collabo- ration among stakeholders, resulting in more efficient operations. Collaboration on cloud infrastructure and services can be accomplished through the built-in tools of cloud infrastructure service providers. Tese applications give users visibility into their cloud infrastructure to track, manage and optimize their cloud costs.


TEAM PLAYERS


The FinOps team works with cross-functional teams to maintain financial control while also ensuring rapid delivery of capability. (Graphic by the FinOps team, PEO EIS)


At a higher level, organizations need to implement cloud-based contract vehi- cles, such as the Army’s Cloud Account


66 Army AL&T Magazine Summer 2023


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