BALANCING ACQUISITION RISK WITH DEPLOYABILTY REWARD


IN TRANSIT


A bulldozer is loaded inside of a C-17 Globemaster III in Afghanistan in support of Operation Resolute Support, Jan. 13, 2016. (Photo by Staff Sgt. Corey Hook, U.S. Air Forces Central)


requirements and military standards and ensure their securement tiedown plans are realistic. If not, changes to the design can be made prior to production or testing. Design changes this early in the development phase are less costly and there is little schedule risk to production.


It is common for commercial systems adapted for a military appli- cation to not have lift and tiedown provisions that are properly located and sufficiently strong to support multimodal military deployments. Tis means a bulldozer could be secured on a rail- car, lashed down to a ship or secured inside an aircraft over many deployments over its lifetime. Multimodal deployments require the tiedown provisions on the bulldozer to be placed and sized so that different strength and number of chains can be applied at different angles depending on the transport mode. Commercial items are not usually designed with multimodal movements in mind. A commercial bulldozer typically will be equipped with tiedown provisions accommodating only high- way movement on a lowboy trailer. Te movement of a bulldozer


50 Army AL&T Magazine Spring 2025


on a railcar or secured inside an aircraft requires more chains to secure it for those transport modes. Tis is just one example of how designing for transportability for multiple transport modes is not always intuitive.


BALANCING AGILE ACQUISITION WITH TRANSPORTABILITY REQUIREMENTS Another key addition into AR 70-47 is that SDDCTEA provides formal transportability engineering input into the MTA outcome determination. SDDCTEA accomplishes this by evaluating the system versus its transportability requirements based upon the materiel developer transportability report and the results of any transportability testing that occurred prior to the outcome deter- mination. When multiple vendors develop systems or prototypes, SDDCTEA will issue a transportability statement or approval specific to each vendor’s proposed solution to support the outcome determination. Before the recent changes in AR 70-47, the trans- portability of the designs was not formally considered at outcome determination. Informing the program office of the ability to


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