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
THE WEIGHT THING


In 1987, we contributed our concepts and early prototypes, along with the other Army research, development and engineering centers, to an advanced technology demonstration at U.S. Army Natick Soldier Research, Development and Engineering Center to show what the “Soldier of the Future” would look like. But on demonstration day, we were horrified when we all suddenly realized that everything Army labs were doing was collectively adding weight to the basic Soldier load—whether giving the Sol- diers increased ballistic protection, new rations (which required water to hydrate), optical rifle sights, night vision, computerized radios and even a new bayonet (with sharpening stone). Tere was no doubt that Soldiers needed these new capabilities, but darned if we weren’t all adding weight to our warfighters with our individual high-tech advancements.


Upon entering a major program management office with a port- folio of close combat munitions, I saw firsthand an early “bunker buster” munition development program that was canceled before it could even get off the ground—because no prospective contractor could honestly bid on our request for a 10-pound solution. Te requirements community had stood firm on that one. It would cost them time. It was years later that they eventu- ally had to accept several solutions in the 15- to 17-pound range (the FGM-172 Short-Range Assault Weapon and the Mk 153 Shoulder-Launched Multipurpose Assault Weapon).


Yep, when it comes to weight as a system or program require- ment, it can be a real biggie for you to consider. Is it a measure of your product or program success?


WEIGHT AS DESIGN CONSTRAINT Of course, our materiel development team derives our users’ requirements and translates them into design specifications. So it’s especially important for you to know this: While weight is one of many possible technical performance parameters, it’s one that affects others to perhaps a unique degree.


Just think about the trade-offs among performance parameters of range, payload, speed, mobility, fuel economy, survivability, lethality, transportability and even reliability (if stress-over- strength comes into play with various components). It might


also factor


into durability or


robustness—not-so-often-used


terms intermingled with reliability and utility. Weight can ripple through your system design like water, as second- and third-order effects are realized when things grow out of hand.


Remember that complexity is defined basically as the known and unknown interactions of many different connected pieces, and our business is the business of managing complexity. People want us to do things fast, but it’s more important to do things right. Te following examples illustrate some of the implications of being overweight.


‘I ONCE HAD A WEIGHT PROBLEM …’ Te highly successful Javelin anti-tank missile was a deeply troubled development program in the 1990s—and was almost canceled over its weight problem. Entering this program man- agement office (PMO) in the middle of the engineering and manufacturing development (EMD) phase, I learned weight was one of our four KPPs. We had known it was a risky goal right up front, along with several others. But at milestone B, we said, “We can do it.” It was a much-needed capability to replace the legacy 72-pound (and highly unreliable) Dragon missile.


We had conducted a 27-month technology maturation phase and had selected one prototype from three to take into advanced development. But we were a long way from anything that looked like a true configuration of the finished product. As EMD began, our preliminary design review had only been sufficient to map out the basic design and componentry to be “invented.”


About 18 months into our 36-month EMD phase, approaching critical design review (and before actually building a representa- tive engineering design model), we realized we were not going to be able to make the 35-pound desired (objective) or even 45-pound required (threshold) weight required by the user in the requirement document.


During a typical system development, functionality, weight, cubic dimensions, interfaces and a host of other specifica- tions are allocated to various producers. It may be quite some time before designs evolve, progress is realized and forecasting


Realizing that weight is an important parameter up front and early is important, but not nearly enough alone to alleviate weight’s programmatic perils.


136 Army AL&T Magazine April-June 2018


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