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
MORE BANG FOR GOVERNMENT BUCKS


FIGURE 1


Integration (CMMI) High Maturity processes. Because ARDEC provides engineering


support to many Army


armament systems and has the domain knowledge for those systems, we can look for opportunities for technology refresh using developmental technologies across the domain of systems we support. For those systems that are in sustainment, we can incorporate technologies that are in development at a much lower cost and shorter time frame than just maintaining the current configuration through obso- lescence management techniques.


$53.2 MILLION, 354 MONTHS IN COST AND SCHEDULE AVOIDANCE Grouping weapon systems into families at the design stage can help reduce costs by ensuring that reusability is baked into the original product. (SOURCE: ARDEC)


CMMI is another enabler for ARDEC’s Weapons and Software Engineering Center. We became the first DOD organi- zation to receive a Maturity Level (ML) 5 rating in June 2006 and were reappraised at ML5 in CMMI V1.3 for development in May 2013. CMMI in general is about optimizing and improving processes, and Maturity Level 5 specifically is about learning from past performances; we applied this ML 5 principle to reduce the number of defects cropping up later in development, when they require more rework to fix. We leveraged mature code from past projects—code that has already been tested and successful—and optimized “within phase” verification to catch defects early.


ARDEC’s success with reuse and in- house development started with a failure. A project manager (PM) at ARDEC put out a contract for a mortar fire-control system (MFCS), with ARDEC engineers helping out as part of the integrated prod- uct team (IPT). But after the contractor missed multiple milestones and was over budget and behind schedule, the PM ter- minated the contractor for default and handed all of the work to ARDEC.


54


KNOWLEDGE AND PROCESS IMPROVEMENT Two key factors enabled RDECOM’s success with MFCS and other in-house development projects: the domain knowledge built up over years of provid- ing support


to many Army armament


systems (even when a contractor builds a given system, RDECOM engineers might provide assistance as part of the IPT), and Capability Maturity Model


Army AL&T Magazine October-December 2015


As a result, we went from catching only 26 percent of defects in the phase they originated in, to catching 91 percent in the originating phase. Since 2005, ARDEC has fielded every system defect- free; CMMI processes allow us to deliver this quality at lower cost.


CONSISTENT DELIVERY CMMI best practices have enabled sev- eral programs at Picatinny Arsenal, NJ, to consistently develop and deliver high- quality products that stay within cost and schedule estimates. Te associated


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  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208