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
ADAPTING EXPERIMENTATION AND TESTING


logistics may have an idea for streamlining supply chain manage- ment. Instead of filing a suggestion report for the currently used software and hoping for the best, they can use FOSS frameworks such as Angular and Django to create a proof of concept. Angu- lar’s robust front-end development capabilities can facilitate the creation of an intuitive user interface for tracking and manag- ing supplies in real time. Concurrently, Django, with its efficient back-end structure, can be used for complex data processing and integration with existing military databases. Te application may perform some lightweight tasks, which could be containerized with Docker or Kaniko. Tese tools allow the application to be standardized and isolated from its environment, making it porta- ble and consistent across any computing platform. Te application can then be deployed and shared with other units, giving them the ability to deploy the application in a Kubernetes cluster or other container orchestration services. Kubernetes, a popular orches- tration system, manages the deployment, scaling and operations of these containers across a cluster of virtual machines. Putting this power in the hands of Soldiers in the battlefield leverages the power of innovation and FOSS. Tis approach fosters an envi- ronment where the best ideas are given space and tooling to be developed and deployed by Soldiers who will use them on the front lines.


TRAINING THE NEXT GENERATION OF SOLDIER-DEVELOPERS Initiatives like the Army Software Factory, Kessel Run (U.S. Air Force), Kobayashi Maru (U.S. Space Force) and the U.S. Marine Corps Software Factory are at the forefront of this transformation, and have leveraged FOSS to train, enable and deliver software to DOD. Tese factories are not only upskilling service members, but also providing commanders with organic problem-solvers who can be deployed as strategic assets. DOD is learning the impor- tance of the potential of FOSS, modern development practices that emphasize agility and the principles of DevSecOps, where security is woven into the fabric of software from day one. Tese programs align with DOD’s emphasis on building a technolog- ically empowered force.


NAVIGATING CHALLENGES AND EMBRACING COLLABORATION Some might question the practicality of FOSS. Te question of whether it will it create a patchwork of unmanageable custom tools is a valid concern. Tat’s why there also needs to be a push to promote collaboration and secure knowledge sharing. Imag- ine repositories where proven solutions are not locked away, but accessible to units across the force. A breakthrough developed to streamline medical logistics in one theater could be adapted and


https://asc.ar my.mil 99


deployed to others, multiplying its impact and reducing duplica- tive efforts. Tis collaborative model reinforces DOD’s guidance on open-source software (OSS), which highlights the importance of knowledge sharing to maximize the potential of open-source solutions. As a caveat, there exists the need for a legal review of approved OSS; special licensing and user agreements need to be reviewed by the proper legal team to ensure licensing compliance.


CONCLUSION Integrating FOSS in military operations is not just about tech- nological advancement. It signifies a fundamental shift toward a more agile, innovative and technologically proficient military force. Te Army’s new software policy and the growing recogni- tion of FOSS’s value herald a future where military innovation is continuous, collaborative and deeply integrated into defense strat- egies. As our adversaries also navigate the digital terrain, leading the race to harness the full spectrum of technological innova- tion will be critical in defining the future of military supremacy.


For more information on open-source software, go to https:// dodcio.defense.gov/Open-Source-Software-FAQ/#q-isnt- using-open-source-software-oss-forbidden-by-dod-informa- tion-assurance-ia-policy.


CAPT. NOE LORONA is an active duty Army captain assigned to the Signal Branch. He serves as a platform engineer for the Army Software Factory, where he plans, develops and deploys cloud architecture to support Agile application development. He holds a Doctor of Management from Colorado Technical University and an M.S. in management and a B.S. in information technology, both from National American University. His professional certifications include Certified Associate in Project Management from the Project Management Institute and six Computing Technology Industry Association certifications.


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  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148