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
and got inside it. … It created that dialogue between Army and industry that is essential for doing anything quickly, for informing Army requirements or helping the Army refine those requirements, by providing that conversation piece,” Sellers said.


THE GRIFFIN LANDS


GDLS displayed its Griffin tech demonstrator at the AUSA Annual Meeting & Exposition. The tech demonstrator offered a tangible starting point for government-industry conversations about the Army’s requirements for MPF, with the ultimate goal of avoiding requirements so prescriptive that they rule out the possibility of industry innovation. (Photo courtesy of General Dynamics)


hosted by the U.S. Army Maneuver Center of Excellence. Te resulting discussions have included the timeline and costs for developing MPF. “Te process … has been pretty successful so far,” said Miller, who noted that major corporate investments are riding on certain key decisions the Army makes up front on a combat vehicle, including its size, weight, survivability, crew size and the kind of aircraft that will transport it.


Miller said a big problem in requirements development of the past has been late-breaking decisions or revisions of key per- formance parameters. Te process of developing requirements needs to settle these major decisions up front, he said. “And then you get to the smaller things that the Army wants, all the way to the widgets. It helps us decide how we want to spend our money.”


Te lines of communication between ARCIC and industry on what the Army wants in the MPF have been open enough that GDLS was able to put together a technology demonstrator in five months for the Association of the United States Army Annual Meeting & Exposition in October 2016 in Washington. It wasn’t just “come up with a solution [and] hope for the best,” as in past years, Peck said.


GDLS’ tech demonstrator—called the Griffin, and not a prototype but at least “a conversation piece that is much more than a PowerPoint,” as Patricia Sellers, GDLS business development manager, put it—got underway even before the industry day, incorporating characteristics that the company thought the Army might want, such as in the turret and gun. “And the Army looked at [the Griffin] and touched it


CONCLUSION Te Army’s combat vehicle modernization strategy as a whole envisions both new vehicles and incremental technological improvements, informed by a continuous assessment, adap- tation and innovation of capabilities, including commercial off-the-shelf solutions. Power generation, gun design, transport- ability and autonomous technologies will be just a few big pieces of the bigger picture, and they’re not likely to come together all at once, but in iterative stages of modernization that require detailed discussion, just as the double-V hull was introduced to the Stryker platform in 2011 to improve survivability. Given what the Army is looking to achieve with the MPF, it might just have to be magical. Or science fiction. But today’s science fiction is often tomorrow’s science fact.


ARCIC wants industry to know that “we’re not just thinking about tomorrow’s war, we’re thinking out toward, you know, 2035. We’ve projected the future in terms of near-, mid- and far-term periods, near-term being now until about 2021, mid- term from 2022 to 2031, and 2031 and beyond is considered far-term,” said Sanchez. “It helps them better see things through the reality of funding that we have to work in. So when they’re delivering, they’re delivering to something in those time periods.”


At the same time, Sanchez acknowledged, our known and potential enemies are developing similar capabilities. “So it’s just a matter of who gets to the better platforms first and who develops the better techniques first.”


With its combat vehicle modernization strategy, which the Army can revise as needed, “we have a living document,” San- chez said, that will enable the Army to avoid the mistakes of the doomed Ground Combat Vehicle, canceled in 2010 after the requirements got out of control and the vehicle was deemed unaffordable. Te increasingly collaborative and iterative process of requirements development gives the Army an oppor- tunity to discover immediately useful technology and spin it out into capabilities the Soldier can use on the battlefield right now. For things that are conceivable but not yet possible, it gives the Army a much better idea of what needs to be parked for now and what can be driven today.


—MS. MARGARET C. ROTH ASC.ARMY.MIL 37


ACQUISITION


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