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
FROM SENSOR TO SHOOTER FASTER


machine-to-machine information sharing requires common standards and well- defined system interfaces.


LESSONS LEARNED In preparation for the live demonstration, the RCCTO partnered with the Systems Integration Lab of the U.S. Army Combat Capabilities Development Command’s C5ISR Center at Aberdeen Proving Ground, Maryland, to create a devel- opment environment. Tis consisted of computers hosting “virtual machines” of the Air Force’s Common Mission Control Center software, the message translation software and the Army Advanced Field Artillery Tactical Data System applica- tion—that is, the sensor that would detect a target, the software that would translate the message generated by the sensor, and the artillery that would fire on the target.


In a complex fight in an anti- access and area denial environment, the time it


takes to deliver information from sensor to shooter is critical.


110 Army AL&T Magazine Summer 2019


Te early testing enabled proper transla- tion and formatting of the critical message traffic.


Both the lab testing and the demon- stration highlighted the need for more standard workflows for fires units when passing messages to joint forces, includ- ing observer mission updates. Additionally, capabilities for sharing situational aware- ness could be enhanced to streamline the air and ground fires clearance processes while minimizing the potential friendly fire or fratricide.


for


Additional analysis will be necessary to move toward greater use of common standards. On a modern battlefield, with multiple units and multiple services, this becomes a much more complex idea that will require the application of advanced machine learning and artificial intelli- gence. One of the key assumptions behind the April demonstration vignette is that the sensor detects an unplanned target as a


“Joint Force Commander Critical Target,” as described in the multiservice tactics, techniques and procedures publication for dynamic targeting. Tese particular targets typically represent a very small portion of the total, and in most cases require an immediate response because of the potential danger to friendly forces.


CONCLUSION Te sensor-to-shooter team successfully demonstrated the technical feasibility of machine-to-machine connectivity facili- tating Air Force and Army bidirectional message passing. Next, the RCCTO team is planning to conduct a possible end-to- end test of the entire sensor-to-shooter kill chain. Tis expanded chain will yield additional lessons learned and insights into machine-to-machine execution and the time to completion of complex kill chains. Additional development could explore an early discussion on hosting the


adapter software at an Army unit, creat- ing a more direct link from an Air Force platform to an Army fires unit. Collabo- ration with U.S. Army Europe continues, with G-3 Fires and G-6 providing input and expertise for continued development of a direct link test and network connec- tivity for the current software.


Ultimately, the Army will need to conduct additional exercises to evaluate message flows in disparate geographic locations to further operationalize the technology. One of many sensor-to-shooter efforts, this will be an important step in creating a better integrated and more lethal joint team to defeat anti-access and area denial measures.


For more informat ion, go to the RCCTO website at ht tps:// rapidcapabilitiesoffice.army.mil/.


MAJ.(P) ISAAC LEWELLEN is the RCCTO Sensor-to-Shooter Joint Project lead. He is an air defense officer with Patriot and indirect fire protection capability battalion experience. He holds a B.S. in psychology from the University of Oregon.


CHIEF WARRANT OFFICER 3 JAMES PATRICK is a network management tech- nician for the RCCTO Sensor-to-Shooter project. He is a signal warrant officer with experience in communications and acquisitions.


LARRY JENNINGS is the MITRE Corp. project lead across various RCCTO initia- tives. He has specialized in advanced concepts development and agile acquisition over the last several years. He holds a M.S. in management information systems from Bowie State University and a B.S. in busi- ness administration from the University of Montana.


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