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
QUARTERBACKING DIGITAL TRANSFORMATION


For most of the past two decades the Army has operated within a network-centric paradigm. Programs lived or died by whether they were network centric.


also means an increased reliance on a digital ecosystem in the engineering process. From remote-control tanks to resilient communications networks, Soldiers rely on complex systems of systems that comprise interconnected and mutually depen- dent parts. Each time one of these individual components gets upgraded, the dependencies and interfaces are put on trial to make sure they were understood and documented well. In an analog system, tracking these requirements is cumbersome. But with digital engineering, the Army’s goals become achievable.


Te challenge for ASA(ALT) is to get everyone speaking the same digital language, so we can understand each other. It’s one thing to gain efficiencies if all systems in one platform are neatly and systematically defined, but it’s another thing altogether to deliver every ASA(ALT) system with digital models that can be shared and leveraged by integrators, testers and logisticians.


Taking this down a level further, this means establishing and integrating models that describe each aspect of a complex system and making sure all our systems leverage the same underlying data structures and pull from the same authoritative sources of truth. Tis process is called model-based systems engineering, which is an important subset of digital engineering.


Programs across the Army have realized benefits and are increas- ing their use of digital engineering but need a common playbook to ensure that system (and subsystem) representations are consis- tent, reusable, able to be integrated with one another, and traceable to operational needs. Much like in the game of foot- ball, when everyone on the team is running the play properly, the efficiencies are exponential.


Key Effort: Model-Based Systems Engineering Style Guide


As part of a larger plan for adopting digital engineering prac- tices across ASA(ALT), DASA DES is developing a style guide for ASA(ALT) to be released this fiscal year. Tis style guide will enable programs adopting model-based systems engineering to do so in a uniform way to maximize the value to the Army. Te


36 Army AL&T Magazine Winter 2023


style guide is being developed in close coordination with other service components and Army organizations to ensure maximum interoperability and commonality across DOD.


CONCLUSION Te Army is making significant investments in digital transfor- mation because achieving a digitally enabled and data-driven land component requires decisive action. It involves setting the stage for data centricity; it involves transitioning across-the-board to modern software development and leading practices for digi- tal engineering; and it involves the important work of training, coaching and mentoring along the way.


As Swanson put it, “Te role of DASA DES is part quarterback and part cheerleader. We are focusing on providing key enabling guidance and architectures, but also coaching and mentorship to programs out on the front lines fighting the good fight each day.” Te Army is expecting these investments to pay dividends as the acquisition force embraces digital transformation through the ranks.


For more information contact the Office of the DASA DES, dasa- des@army.mil.


DARREN LEBLANC is a senior technical adviser with CommNet, supporting DASA DES. In his current role, he helps the Army analyze and solve complex problems related to digital transformation. He holds a B.S.


in engineering from Messiah University and


has done interdisciplinary graduate work at Harvard Business School, Stevens Institute of Technology and Western Seminary.


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