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
PATHS TO SUCCESS


B


y now, the Acquisition, Logis- tics, and Technology (AL&T) community is well aware of the detailed guidance from


Dr. Ashton B. Carter, Under Secretary of Defense for Acquisition, Technol- ogy, and Logistics (USD(AT&L)), on providing incentives for greater efficien- cy, starting with in his June 28, 2010, Memorandum for Acquisition Profes- sionals Better Buying Power: Mandate for Restoring Affordability and Productivity in Defense Spending.


At the Defense Acquisition University (DAU) Acquisition Community Sym- posium on April 12, practitioners of AL&T had an opportunity to better understand the genesis for Carter’s guid- ance, and resulting steps taken, in five areas of action—targeting affordability and controlling cost growth; incentiv- izing productivity and innovation in industry; promoting real competition; improving tradecraft in services acqui- sition; and reducing nonproductive processes and bureaucracy.


Following is a detailed look at each of the five areas, as presented at the DAU symposium.


TARGETING AFFORDABILITY AND CONTROLLING COST GROWTH Affordability is a straightforward concept, said David G. Ahern, Deputy Assistant Secretary of Defense, Portfolio Systems Acquisition. The difficulty lies in estab- lishing the necessary discipline to achieve it in every program, so that DOD can develop budgets with a “steady, sustain- able, and predictable rate of growth” and live within those budgets.


Ahern addressed five steps in Carter’s guidance on affordability and controlling cost growth:


92 Army AL&T Magazine


• Mandate affordability as a require- ment. DOD is looking at affordability holistically, Ahern said. “We don’t want to nail it down as a KPP [key perfor- mance parameter], as a JCIDS [Joint Capabilities Integration and Develop- ment System] sort of thing, but as an acquisition target.” Beyond the range of individual cost factors, “we’re look- ing for how that [cost] profile fits into the overall resources,” specifically within that area of acquisition, be it ships, tanks, trucks, or aircraft, he said.


“It is not only the unit [cost], but look- ing at how many units are going to be bought annually, how much RDT&E [research, development, test, and evalu- ation] is required, and how that fits into the ongoing TOA [Total Obligation Authority] of the service.”


• Drive productivity growth through will-cost/should-cost management. Of the various program cost estimates to be considered, the will-cost figure is likely to be in line with the service’s esti- mate or the independent cost estimate, if applicable, of the Director of Cost Assessment and Program Evaluation (CAPE) in the Office of the Secretary of Defense (OSD), Ahern said.


The will-cost estimate is “in the absence of some focused attention to do it better,” he noted. In contrast, “What is required of the program managers to come up with a should-cost is not to say, ‘If the will-cost is this profile, I’ll just take 5 percent off, or 10 percent off it … and I’ll figure out how to do it.’ … To get the job done, we need specific opportunities in competi- tion, in changing the configuration, in challenging requirements, in introducing subcontractor competition—some com- bination of those kinds of activities, with a rifle not a shotgun, to fill up a funnel of opportunities to reduce cost” in develop- ment, production, and/or sustainment.


The should-cost estimate will be the number against which the program is tracked, Ahern said. “There should be a delta in outyears between that should- cost and the will-cost. It can be quite significant in some years, and in some years it won’t be that significant.”


So what’s going to happen to the sav- ings? “We’re going to have to figure out collaboratively, in the enterprise, what’s the best approach to using that money,” said Ahern, who is of the opinion that


“it really belongs to the taxpayers,” not the program manager or even the service. Making a program or product more affordable “is a worthwhile objective regardless” of where the money saved is spent, Ahern said. It may be used to buy more of the item, or be moved to another portfolio, or to the service or OSD to pay other bills. Who makes that decision will depend on how much money is involved and whether it falls in the current year or an outyear, he said.


• Eliminate redundancy within warfighter portfolios. Capability portfolio reviews, such as the Army has adopted, have proved to be a very useful tool by iden- tifying overlaps, he said.


• Make production rates economical and hold them stable. With every pro- duction decision, particularly but not exclusively initial production, DOD has taken “a harder look at not the minimum sustaining rate, but the right rate of production,” Ahern said. “There is a value to having the production line open for some period of time. But on the other hand, … I don’t think a 20-year production makes much sense for almost anything,” especially given rapidly evolving technology.


• Set shorter program timelines and man- age to them. “The longer a program


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