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 DATA: FROM THE FOXHOLE TO THE PENTAGON


unstructured, semi-structured, what type of data source it’s coming from and what type of connection is required to absorb that information.” (See Figure 2, Page 20.)


Finding that data is just the first step. Te dashboard team then makes contact with the data’s owners to identify which pieces are relevant and needed for senior leaders. At first, the team set out to capture any and all data from those identified sources. Over time, it developed a more targeted approach, seeking only data that is orig- inal and authoritative from each source.


“What we’re looking to do is methodically and deliberately go through one domain at a time,” said Col. Jette. (A domain might be “people,” “training,” or “equip- ment.”) “We’re having the leaders from each domain identify the priority systems that are their ‘center of mass.’ Tere are, in some cases, scores of data systems within a particular domain, and we simply don’t have time to cover all of them, so we’re


asking the domains to identify the top 10 or so. We discuss those, how they relate to each other, how they provide original information to the Army.”


That original information is key. For example, the Army Leader Dashboard will need to pull data from the Logis- tics Modernization Program (LMP), also at PEO EIS. LMP alone has some 40 terabytes of data—more than 17 billion single-spaced, typed pages. However, of those 40 terabytes, only a fraction is orig- inal and authoritative information, so the challenge is to identify which pieces to pull and which to disregard.


WHICH DATA IS THE BEST? The team focused on the concept of


“cornerstone data”—that is, the Army’s uniquely identifiable things. “We’ve iden- tified the need for at least four categories: people, units, major equipment and places, at the site level,” Col. Jette said. “I’m an individual; I can always be identified by


my Social Security number. A unit will have a unit identification code, a piece of major equipment will have a 16-digit item unique identifier [UID], and places will have a site UID or a particular building will have a real property UID.”


Te dashboard team then builds on that cornerstone data, linking the many thou- sands of secondary attributes associated with those uniquely identifiable things. If a commander wanted to locate all active-duty sergeants stationed at Fort Bliss, Texas, who have Chinese language proficiency and advanced cybersecurity certifications, the dashboard would enable that search.


Part of the challenge, though, is decid- ing which is the primary, trusted source for a given dataset. For instance, human resources data is sprinkled across nearly every system the Army operates. A Soldier’s name, date of birth, Social Secu- rity number or other relevant details


MORE THAN THE USUAL DASHBOARD


According to the Army Data Strategy, data should be visible, accessible, understandable, trusted and interoperable. Lt. Col. Rob Wolfe, Strategic Initia- tives Group director at PEO EIS and the lead for the dashboard project, said the dashboard team has been driving the kinds of conversations that will help achieve that goal.


“What we’re seeing is a change in the way the Army governs and manages data,” Wolfe explained. “These problems are driving change—hopefully, enduring change—so that we can maintain consistent, quality data. Between the Office of Business Transformation, which is responsible for architecture, the Army Analyt- ics Board, which is responsible for how we integrate and analyze data, and the Army Data Council, which is responsible for standards, we are seeing those bodies getting into the same room and having conver- sations that the Army hasn’t had before.


“It’s more than just a dashboard,” Wolfe continued.


“It’s the first thing we’ve seen that allows leaders at all echelons of command to look across domains. There are a lot of systems that allow you to look at people, to look at equipment, to look at training, but there are not any systems that allow you to look across all those areas and see how resourcing decisions in training affect people, or vice versa. We’re really trying to give leaders a tool to make strategic resource deci- sions and understand the impacts across the Army.” His goal is to enable “insight-driven” decisions.


For the dashboard team, readiness is the bottom line.


“What previously could take multiple weeks is now being done in real time,” said Rajat Senjalia, techni- cal director for the Strategic Initiatives Group. “When senior leaders can utilize one tool that can aggregate the necessary information, it enables you to make an executive-level decision on anything from troop movement to resource allocation. That is invaluable to the Army.”


https://asc.ar my.mil 17


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