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
the capability and get it into the hands of our Soldiers as quickly as possible.


Jones-Bonbrest: So how important, then, is the partnership between the Assistant Secretary of


the Army for Acquisition,


Logistics and Technology (ASA(ALT)) community and the sustainment community?


Muzzelo: From my perspective, it’s


extremely important. Systems are in the field for several years. So, as sustain- ment strategies are developed, we look at who are the vendors, are we buying data rights, is


it sole-source, are there


commercial products integrated in that capability, and what are the strategy and cost for that capability over the long term. If the sustainment and life-cycle manage- ment communities aren’t talking, you’ll have many challenges and obstacles in developing the strategy and then imple- menting it. On the sustainment side, in support of


the program offices, we’re


responsible for sustaining systems for many years. So if we’re not in sync, that


Muzzelo: I would also add that in sus- tainment, we are never funded to the full


leads to serious organizational and pro- gramatic challenges, and at the end of the day it really impacts our ability to pro- vide the best support to Soldiers.


Martin: Te fact of the matter is that deci- sions made by project managers [PMs] early in the program can significantly impact what happens on the back end. With approximately 70 percent or more of the costs for a weapon system over its life being executed on the sustainment side, it is prudent that there is mutual understanding and mutual partnering on the front end. A decoupling there can result


in significant inefficiencies and


costs. We’re seeing that today, and it is the essence of the partnership that exists between AMC on the sustainment side and ASA(ALT) on the acquisition side. It’s critical. Te better the partnership and engagement throughout the entire program life cycle, the more effective the program will be.


amount we need. So if


the PM imple-


ments strategies to be as cost-efficient as possible on the acquisition side, that also comes into play when we’re sustaining the systems. We have many competing priorities, sometimes within different PMs that are in the same PEO, so that partnership and prioritization can only be successful if there’s a relationship and conversation between both organizations.


Jones-Bonbrest: Can you give exam- ples of this partnership that are already in place?


Martin: Tere really are four issues that we have selected locally as opportuni- ties to partner. Each addresses a couple of areas where we have seen a need for improved security


efficiencies. Tey include patching, software assurance,


software licensing and field support.


Muzzelo: Security patching is a good place to start. I mentioned that we use a lot of COTS products, at least in PEO C3T’s domain of weapon systems, and there are certain challenges that come with this. For example, Microsoft and Apple have to patch their systems. Most consumers are familiar with that process. Te Army faces some of the same challenges. Te Army’s process historically has been to send out CDs on a quarterly basis with security patches, which requires Soldiers to manually install software from the CD. In today’s high-tech environment, that’s a nonstarter. So we’re working collabora- tively with PEO C3T to get the patches integrated, tested and posted to one site where users can download those patches for tactical


systems. We’ve started that MAKING CONNECTIONS


Networked vehicles provide on-the-move communications, mission command and situational awareness that commanders need to lead from anywhere on the battlefield. PEO C3T and CECOM have different but overlapping responsibilities for the C4ISR system readiness that supports the Army network. (U.S. Army photo by Amy Walker, PEO C3T Public Affairs)


initiative with Fort Campbell and Fort Bragg, and we’ll go to Germany next. Tat’s a partnership that is beneficial not only to us but also the Soldier, and it really reduces the security risk of our tac- tical Army networks and systems.


ASC.ARMY.MIL 49


SCIENCE & TECHNOLOGY


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  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203