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 MAKING OF A PACKARD


Packard Award-winning reality. However, they are only several of many. Scores of people within the organizations contrib- uted to the success of the project, as did many other individuals and organiza- tions across and outside DOD who were brought in to find new ways to success- fully expedite the traditional acquisition process. From EW officers to Army head- quarters staff, from cybersecurity experts within the Office of the Assistant Secre- tary of the Army for Acquisition, Logistics and Technology (ASA(ALT)) to the U.S. Army Test and Evaluation Command, from the Army’s Rapid Equipping Force to industry partners and many others, the achievements leading to the Packard were a team effort that reflects the best of what the Army can do when the stakes are high. Here is a look behind the curtain.


AWARD WINNERS


The team received the 2018 David Packard Excellence in Acquisition Award in February. From left are Ken Strayer, deputy project manager for PM EW&C; Doug Wiltsie, former RCO executive director; Brandon Little-Darku, RCCTO engineer; Hon. David L. Norquist, performing the duties of the U.S. deputy secretary of defense; Lt. Col. Eric Bowen, former product manager for Prophet; Hon. Ellen M. Lord, undersecretary of defense for acquisition and sustainment; Tanya Skeen, former RCO executive director; Vanessa Pittman, RCCTO business manager; Col. Kevin Finch, project manager for EW&C; and Marty Hagenston, Col., USA, Ret., former project manager for EW&C. (DOD photo by U.S. Army Sgt. Amber I. Smith)


THE DIRECTOR: DOUG WILTSIE


“Te big thing for us was speed. Where we had the opportunity to take risks, we did. It started with our board of direc- tors [BOD], which at the time comprised the secretary of the Army, chief of staff of the Army and Army acquisition execu- tive. We briefed the BOD, but there was no requirement to brief anyone else, due to the RCO’s unique charter. So the approval cycle was significantly shorter. Te power of the BOD was it allowed us to bring in a broad end-to-end solution for the type of capability we needed to provide. And


12 Army AL&T Magazine Spring 2019


then, working with the unit, we developed what the specific requirements would be for mounted, dismounted, and planning and management systems. We developed an incremental strategy that increased the capability performance over time. We got prototypes into the hands of the users, who got to train on the equipment and give us continuous feedback on the performance and how to improve it. With this strategy, we fielded the first increment in one year, which was very impressive.”


The power of teamwork: “Te user was actually in the lead of this project the entire time. From the delivery of the


concept of operations to the performance of the system they wanted, the Soldiers and the EWOs [electronic warfare offi- cers] in those brigades really helped shape how the system was going to operate. Tey were committed to the incremental strat- egy, where we put elementary pieces of equipment into their hands first, knowing that the capability was going to get better over time. PM EW&C was the other crit- ical element to this project. Te Rapid Capabilities Office had unique authorities but limited people to put on this proj- ect, so we partnered with PM EW&C to develop the solutions, prioritize the incre- ments, develop the sustainment process,


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