search.noResults

search.searching

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
should consider mandatory for its future logistics enterprise system. Tat system must be:


• Governed and funded by a single entity. • User-centric, with an architecture that maximizes self-service.


• Able to rapidly respond to change and introduce new functionality.


• Scalable—up or down—for both infra- structure and services.


• Acquired as an outcome-based managed service.


Transforming the Army’s disparate ERPs into an enterprise with these characteris- tics will be hard, but it can be achieved with three major efforts: Consolidate ERP sustainment; consolidate business intelli- gence and analytics; and finally, collapse different ERPs into a unified ERP.


SYSTEMS AND SUPPORT UNDER ONE ROOF The U.S. Army Communications- Electronics Command’s


(CECOM)


Software Engineering Center is spearhead- ing the initial steps toward the first effort. CECOM recently announced plans to explore consolidating sustainment across its ERP portfolio. We applaud leaders for taking these steps but suggest they prepare for an even bolder one. Additional central- ization between core ERP sustainment (owned by CECOM) and modernization efforts (owned by the assistant secretary of the Army for acquisition, logistics and technology) would make it easier for Army leaders to prioritize between investments in current versus future capabilities—and help fully optimize life cycle management of the Army’s logistics systems.


Acquisition professionals can readily see benefits of this consolidation, includ- ing improved visibility into requirements and better buying power that can drive cost savings. Also, the ability to prioritize spending across a larger pool of require- ments, using combined resources, will ensure that the most impactful require- ments are addressed—not just the top priority for a slice of the enterprise.


Further, ERP support service contracts should shift away from buying capacity to buying outcomes. When requirements are not well-defined, using multi-award indef- inite delivery, indefinite quantity contracts or blanket purchase agreement-like strat- egies can help mitigate risk to the Army. By leveraging these acquisition vehicles, the Army can award more highly targeted and smaller task orders to a handful of pre- qualified vendors. Task orders could take


PUTTING THE RIGHT TOOLS IN PLACE


Soldiers assigned to the 3rd Armored Brigade Combat Team, 1st Cavalry Division ready an M1A2 Abrams main battle tank for maintenance at Exercise Bright Star 2017 in Egypt. Mechanics worldwide rely on logistics systems such as LMP for transparency of available inventory. Changes to LMP and similar ERPs would improve their effectiveness and lower the costs of operating them. (U.S. Army photo by Staff Sgt. Leah R. Kilpatrick, 14th Public Affairs Detachment)


HTTPS: / /ASC.ARMY.MIL


111


COMMENTARY


+


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  |  Page 149  |  Page 150  |  Page 151  |  Page 152