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
ASK THE RIGHT QUESTIONS


Programmers use heuristics, “rules of thumb,” to reduce complex- ity, parameters and processing power needs, or to fill knowledge gaps during algorithm development. Tese heuristics may trade off optimality, completeness, accuracy or precision. Te heuris- tics could affect the program’s ability to find an optimal solution when multiple solutions exist or prevent it from finding the most correct or optimal solution. Tey may also only nominally decrease computing time. Poor heuristic choices and underly- ing assumptions degrade the validity of an algorithm’s output.


In the end, humans determine the underlying assumptions used to design AI programs. Te result presented to consumers is often a black box containing a mix of clever programming and smartly analyzed data. But if created poorly, models can be too sensitive or not sensitive enough, resulting in too many false positives or false negatives. Corner cases, human insertion of errors and inaccurate models from bad or limited datasets will also lead to errors. Data requirements, accurate modeling, processing power and fallibility also apply to other AI specialties, such as facial and voice recognition.


ASK THE RIGHT QUESTIONS, GET THE RIGHT TECHNOLOGY DOD is investing heavily in AI to gain military advantages and reduce workload. A working knowledge of AI will help product managers better understand industry presentations, and will help assess technical maturity and determine viability and scalability of a solution during the market research phase.


Preliminary market research questions include:


• How is the model built? What are the underlying assumptions? • How is the model tested? Was training data used in the test set? • How well does the model reflect the real world? What are the performance results of testing? How much better than random chance? What are the precision, recall and f-scores (closer to 100 percent is better) and confidence level in the results? What is the rate of false positives and negatives?


• How was the dataset gathered? If data was gathered from people, did the people know it was being gathered? How big are the training and test datasets? If the dataset isn’t built yet, how long will it take and how much will it cost to build?


• How well does the program perform against deception and adversarial inputs (e.g., a subject wearing sunglasses or a hat)? What happens when the program is presented with corner cases?


• How much computing power is required? Where does the processing occur? How long does it take for results to be computed?


88 Army AL&T Magazine Summer 2019


• Can the algorithm be updated easily? How are improvements inserted? How is real-time performance measured? Can oper- ators determine when the algorithm is performing poorly in real time?


• How well does the program work with existing programs to input and export insights?


• Is the system autonomous or human-assisted? How much human assistance does it require?


• Where are decisions made? Are they made by humans, or does the program automatically do it? This is a critical question for decisions about the use of force.


• What rights does the government have to the dataset and the trained model?


CONCLUSION Increases in processing power have enabled greater advances in AI to solve complex problems on and off the battlefield. Tere are still limits to what AI can do, however. We can be cautiously optimistic but must exercise prudence and rigor to ensure that we can identify the difference between a viable solution and a black box filled with empty promises. Asking the right questions up front will help unveil technology readiness—and help DOD steer clear of vendor oversell—enabling the right acquisition deci- sions and the efficient spending of Army resources.


For more information, go to the Program Executive Office for Command, Control and Communications –Tactical (PEO C3T) website at http://peoc3t.army.mil/c3t/, or


the PEO C3T Public Affairs Office at 443-395-6489 or usarmy.APG.peo-c3t.mbx.pao-peoc3t@mail.mil.


LT. COL. JENNY STACY is the product manager for Satellite Communications within the Project Manager for Tactical Network at PEO C3T. She has an M.S. in computer science from the Naval Postgraduate School; her thesis, “Detecting Age in Online Chat,” received the Gary Kildall Award for computing innovation. She also holds a B.S. in computer science from the United States Military Academy at West Point. She is a member of the Army Acquisition Corps, and is Level III certified in program management and Level II certified in information technology.


contact


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