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
DRIVING THE FUTURE


Interoperability compliance. Platforms with a high likelihood of someday need- ing to provide unmanned or optionally manned functionality should consider requiring that


ant with the Robotics and Autonomous Systems Ground Interoperability Profile. Te Army developed the profile with its industry partners to provide known inter- faces for interoperating with robotic and autonomous systems. Acquiring a system that already complies with the profile will allow for greater interoperability once the autonomous capability is added.


Physical interfaces. Systems engineers should consider using commercial stan- dards such as those of the Society of Automotive Engineers and the Institute of Electrical and Electronics Engineers to define physical interfaces for applique kit integration. Tey should also leave enough physical space for the later inclu- sion of applique hardware such as radios, computers and associated electrical wiring and connections.


Onboard diagnostics. PMs should require that onboard diagnostic systems come with the base configuration. Tis has the direct advantage of improving maintenance, sustainment and safety. Te


MAN-TRANSPORTABLE ROBOTIC SYSTEM


Small- and medium-sized robots used for route clearance and explosive disposal proved their worth in Iraq and Afghani- stan and are now widespread in the Army. Larger robotic “mules” are on the horizon. (Photo courtesy of Endeavor Robotics)


indirect advantage is that the sensors and data needed for diagnostics offer a founda- tion for providing unmanned capabilities to the system in the future.


interfaces be compli-


Of course, integrating so many new tech- nologies can affect other operations and functions of a system and does require some additional considerations. PMs should ensure that systems are built to the most rigorous standards available. Have the manufacturer run extra fault-injection tests, and make sure the contractor supplies data from those tests, plus safety artifacts such as failure mode diagrams.


COUNTING THE COST One of the great benefits of leveraging advancements in commercial technol- ogy is that market forces and industrial investment have already driven down the cost of many—but not all—technolo- gies. Requirements developers and PMs should conduct market research to deter- mine the cost implications of including robotics-ready technologies in their base configurations. Te D-HMEE develop- ment effort cost the Army roughly $8 million in research, development, test and evaluation over about five years. In hindsight, that amount could have been reduced based on lessons learned


The Army has not been able to take full advantage of these commercial trends— primarily because of the long life cycles of its systems.


throughout the development. But the level of effort to convert any nondigital systems into unmanned systems is significant and makes funding hard to predict.


Te product cost of converting a base HMEE Type I to a D-HMEE config- uration is


approximately $75,000.


The government estimates that if the D-HMEEs had been produced as new production systems, the per-system cost would be around $25,000 higher than the HMEE Type I. Which is to say that in this case, the total cost of getting an unmanned system by building a basic system first and then modifying it is considerably lower than building an unmanned system from scratch.


88


Army AL&T Magazine


Spring 2019


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