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
SEE THE UNOBVIOUS


With uncertainty resolving over time, we enter the engineering and manufacturing development phase, where M&S invest- ments are still required as we learn more about our more mature “engineering design models.” Computer-assisted design and manufacturing are invaluable as we refine requirements and design while using developmental testing to validate matur- ing models. Tese operational models also help us better realize the logistical support plans that previously had been conceptual.


At this point there is likely a divergence of models: the real-world mission kind (test articles) that can fly, roll or swim through- out the multidomain battlefield, and the hardware (and software)-in-the-loop


models. Te latter are typically being run within computers to predict perfor- mance in a huge variety of conditions and scenarios via Monte Carlo simulations (multivariate probability distributions).


Both serve to inform project stakehold- ers, especially you, the PM. Often, we have to cut a deal with the operational testers to let us use something less than a full-up system for destructive testing. No sense firing a .50-caliber machine gun at a nuclear submarine—just use a panel (skin) from the side of one. (Sound crazy? Just read the account in “Te Pentagon Wars” of the time some folks wanted to fire a tank main gun round at a combat-loaded Bradley Fighting Vehicle, just to see what


would happen.) PMs must negotiate the use of models instead, to reduce the costs of test articles.


SAVE THE BACON Another bacon-saving episode—in this case, in the evolution of the Javelin missile project—was an engineering and manu- facturing development field simulation that we felt would probably be more to satisfy bureaucrats’ demands than to learn anything new about our system. How wrong we were! With immature models and prototypical hardware and software, we found out unequivocally that our FLIR (forward-looking infrared) sensor sensitiv- ity specification was validated—and there would thus be zero room for design trades on that aspect of the system.


With the production and deployment phase drawing near, and as stereolithog- raphy technology is advancing now to 3D printing, output models will still be used to prove out production planning and manufacturing processes using factory simulations. Low-rate initial produc- tion test articles will no longer be models, but production-representative—the real thing. And, as with the example above of the Army Tactical Missile System initial operational test and evaluation, M&S can still save the day by revising the test score as successful that was initially thought to be a failure. In that same three-month major operational test event on the very eve of system deployment to the Persian Gulf War, we were able to use over 1,000 simulated fire missions, done solely by computer model, to convince testers and other stakeholders to support the full-rate production decision.


TRAIN HERE FIRST


Soldiers practice convoy operations on virtual battlespace simulators. Training simulators go hand in hand with rigorous modeling as tools supporting the optimal design and use of warfighting systems, especially if the number of actual systems available to train is limited. (U.S. Army photo by Staff Sgt. Anaidy G. Claudio, 368th Public Affairs Detachment)


Of course, during the operations and support phase we will be getting user feed- back to help us elaborate evolving ideas for more capability through modifica- tions, tech insertion and so on. Here again,


108 Army AL&T Magazine October-December 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