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
CONSTRAINTS AND CONTROLS


Joint Requirements Oversight Council Adopts More Decisive Process


by Margaret C. Roth S


maller meetings, more-focused in- formation, and a stronger focus on priorities: These are steps that the Joint Requirements Oversight


Council (JROC) has taken to establish a more efficient, decisive, and ultimately effective way of validating major pro- gram requirements.


Speaking Nov. 2 at the PEO/SYSCOM Commanders’ Conference on “Improving Requirements Definition and Manage- ment,” Air Force Brig Gen Richard S. Stapp, Deputy Director for Requirements, Joint Staff (J-8), said, “We’ve made some very major changes” in the JROC process since the summer to fulfill JROC’s mandate— to make cost, schedule, and performance trades when looking at requirements.


“More than any other body in the Depart- ment [of Defense], they’re really charged with shaping the force—what do we need to fight the next fight [and] how do you bal- ance it against the budget you have” within the desired schedule. That said, “What the JROC has not done a good job of in the past is making those trades,” Stapp said.


He noted that “90 percent of ACAT [Acquisition Category] 1 programs are over cost and over schedule, and they have been for the last decade. It’s not a good track record.” The result is “all sorts of disruption and chaos” when funds have to be pulled from other programs to cover cost overruns, and budgets must be rewritten. “What we want to do with the


124 UPGRADING PORTFOLIOS


The Joint Requirements Oversight Council is considering each weapon system that comes before it to ensure that the system fits into the entire portfolio of solutions to fill a capability gap. Here, the new Apache Block III (AB3) helicopter lifts off the runway at the Boeing complex in Mesa, AZ, during a rollout ceremony in November 2011. The AB3 features key upgrades to previous Apache helicopters, including Level 4 interoperability with an unmanned aircraft system. (U.S. Army photo by Program Executive Office Aviation.)


requirements process is try to settle that down to some extent.” More-executable programs will mean more stable expendi- tures for DoD at a time when competition is intensifying for funding from base bud- gets, Stapp said.


“Right now there is no appetite and no budget for 100 percent solutions. You have to be willing to assume risk,” he said.


Setting clear priorities based on rigorous analysis is key, he added. “Not every- thing should have equal importance.” The JROC wants to be able to “debate the really difficult issues,” to look at each weapon system and its mission scenario and see how it fits into the total portfolio to fill a capability gap. “This is going to be much more deliberative than it’s going to be consensus-driven,” Stapp said.


Army AL&T Magazine


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