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
ARMY AL&T


MOVING ACQUISITION


Transportability engineering is vital in an accelerated acquisition process.


by Michael Bartosiak E


fficient and rapid deployment of the Army is crucial to the National Defense Strategy. Te DOD acquisition community has a key role in obtaining materiel, equipment and weapon


systems that fulfill Soldier requirements. Te acquisition community is evolving by accelerating or streamlining systems acquisition to meet those needs in a timelier manner. Using a commercial off-the shelf (COTS) acquisi- tion strategy to acquire military systems can reduce initial production costs as well as fielding times. However, those benefits could come at the price of transportability issues that impact deployability and work against some of the aims of the National Defense Strategy.


Te military has a unique requirement to transport large and heavy systems by rail, ship, air or highway regularly during deployments. Commercial items do not have the same transportability and deployability requirements and therefore are not designed for frequent shipment. Mili- tary systems are required to have special provisions that enable rapid lifting and tie-down. Large or heavy mili- tary systems, referred to as transportability problem items, have requirements that define very specific transportabil- ity criteria. As the design of military systems approaches the limits of the certain transportation assets, meeting the transportability requirements becomes critical.


ADDRESS TRANSPORTABILITY EARLY James N. Mattis, the 26th secretary of defense, once stated, “If you cannot move, you are not lethal.” Tere- fore, transportability engineering is an essential part of the acquisition process. Requirement writers, materiel devel- opers and program offices need to consider how units will deploy once the systems they develop are integrated into the formation. Designing transportable systems enables the force to be agile and deployable.


It is important to consider transportability requirements early and throughout the acquisition process. When they are considered only later in the process, issues can occur—a redesign after a system is in production can hinder system performance and effectiveness.


For example, a commonly proposed solution for address- ing transportability of large or heavy systems after production is to create a transport configuration—how systems reduce for movement on a mode of transport, like a train—by removing parts from the system. While this may be a viable solution as it has less effect on initial cost and schedule, removing parts could result in slower deployment times and be an operational burden to the unit using the system. Te removed parts must be pack- aged and shipped with the system, and those packaged


https://asc.ar my.mil


127


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