S&T [science and technology] side of the acquisition community to learn what’s possible—and then also with industry to gain a better understanding of what they’re doing that might provide solu- tions to our capability gaps.


But we still have to make sure we disci- pline ourselves in terms of how we write our requirements, discipline ourselves in terms of how we build our requirements. One key feature, as far as I’m concerned, is that as we build our requirements, we need to understand how much is enough to get us the capability we want. And [there may be] some areas where we say,


“Hey, we’d like to stretch ourselves in terms of the capabilities we want to get. Tey [industry] are making some things that allow us to operate more effectively or that give us some additional key fea- tures in terms of lethality or mobility or some other type of ‘-ility.’ ” And then we have to be able to understand that those additional or enhancing things become tradable; otherwise our requirements will exceed our ability to pay for them.


So it’s collaboration, it’s discipline in the requirements, and then it’s making sure that we understand what’s most important, the must-have things to get a capability. And then we can say, “Hey, you know, if we get this it’s great, it will certainly give us added capability or enhance the capability.” But it’s also tak- ing into account the fact of what can be designed, what can be developed, what can be done over time and what it’s going to cost you: Tat allows us to begin to think about scaling back to get to a more affordable solution.


So that’s in general terms how we go about getting that work done through collaboration. Tere are a couple of things that we have done in recent months, in this year, FY15, to just try to get the


COLLABORATION BLUEPRINT


SSG Joshua Blake from the Army’s 3rd Armored Cavalry Regiment briefs leaders of the U.S. Army Tank Automotive Research Development and Engineering Center (TARDEC) on the final day of the Soldier Innovation Workshop, held May 18-20 at the Detroit Arsenal in Warren, MI. Soldiers collaborated with transportation design students from Detroit’s College for Creative Studies to develop ideas and designs that will inform the concept and requirements for future mobile protected firepower capabilities. Requirements don’t just specify how a system should be built and used; they can also be a blueprint for how government and other stakeholders will work together. (Photo by Jerome J. Aliotta, TARDEC)


community as a whole to recognize. And one of the things we’re undergoing right now is a series of ROC drills—rehearsal of concept drills—going from capability development to materiel acquisition to delivery of systems.


And this has become a joint effort [involving] not only ARCIC but also the ASA(ALT) community with heavy partici- pation from a lot of stakeholders, including the HQDA G-8 and G-3 folks. Te ROC drill is intended to just walk us through the process from the requirements docu- ment to an approval, to the resourcing, to all the work that has to go on to define the


real technical specification of what that requirement is, to make sure that we don’t overreach on those as well, and then get us to the materiel delivery.


We’ve already done one ROC drill on an existing capability. We wanted to really plow into something that we know that we’re going after, and we’d like to try to see if we can get to the right solution in an innovative way and see if we can get it more rapidly than the normal process typically allows.


But then we’d like to take ourselves through another series of ROC drills to


ASC.ARMY.MIL 15


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