ARMY AL&T
A mechanic works on MRAP vehicles at the MSF in Kuwait. (U.S. Army photo by Barbara Hamby.)
independent suspension systems (ISS) designed to improve the blast- protected vehicles’ off-road performance in Afghanistan. A third piece involves refitting a portion of the baseline MRAP fleet with ISS.
“This decision to go with improved suspensions is part of our ongoing commitment to providing Soldiers the safest, most survivable vehicle pos- sible,” Peterson said. “The improved suspension is aimed at providing better off-road capability and has the added benefit of improving the overall ride quality and vehicle performance on the unimproved roads found throughout theater.”
Capabilities Insertion (CI) Just as the number of vehicles required has increased, each service and compo- nent also requires unique and evolving vehicle equipment configurations. The MRAP JPO continues to adapt and work toward testing and integrating
42 JULY –SEPTEMBER 2010
effective and enhanced armor solu- tions as the enemy modifies its means of attack.
The MRAP CI program was developed by the JPO and formally launched in summer 2008, but “we actually started inserting things back into the vehicles almost immediately,” said Dave Hansen, Principal Civilian DPM MRAP Program. “We focused on anything that helped us manufacture or install our government-furnished equipment and then on to survivability and safety issues, such as the GRS [gunner restraint system].”
The CI program was created to address multiple critical Joint Urgent Operational Needs Statements (JUONS) as a single program and single requirements base so optimiza- tion could ensue. It also had an eye toward the future to enable easier incorporation of solutions to future JUONS. The JPO leveraged the inter- nal capabilities of the U.S. Army Tank Automotive Research, Development, and Engineering Center (TARDEC), as well as external partnerships to include the Joint MRAP enterprise. Thanks to a coordinated team effort across numerous DOD agencies and organi- zations, hundreds of new capabilities have been added, including overhead
The CI program was created to address multiple critical JUONS as a single program and single requirements base so optimization could ensue.
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