search.noResults

search.searching

saml.title
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
STITCHING THE ARMY'S DATA FABRIC


To reach that future objective state, the Army is following an incremental approach to deliver data fabric capability over time through the network capa- bility set construct. Working across the Army modernization enterprise, and in collaboration with our joint service and industry partners, the Army has matured its own tactical data fabric and is now experimenting with additional commer- cial capabilities, with the goal of initial fielding in fiscal year 2023.


THE WHY AND WHAT Access to the right information at the right time is a critical element to achieving future battlefield advantage at the oper- ational and tactical levels. Timely access to data depends on agility in how data is managed. As Chief of Staff of the Army Gen. James McConville put it, “We’ve got to be able to move data machine to machine very, very quickly. Tat is the secret if you want to get to speed, range and convergence.”


To achieve that goal, there are several chal- lenges the Army needs to overcome. First, data in warfighting functional systems (such as fires, maneuver or sustainment) is often stovepiped or isolated, which can result in inconsistent and missing data in the common operational picture. When data is exchanged between warfighting function systems,


it is frequently


compressed due to message exchange formats, and it loses some of the informa- tion from the original source. Additionally, data is unnecessarily restricted from poten- tial consumers when systems inherit the classification of the network they reside on, rather than managing the classifica- tion of the data itself. Finally, artificial intelligence (AI) capabilities—a necessity in order to operate at the speed of digi- tal war—are starved for data, because warfighting systems generate information at high volume but without great value, as


So how does it work? Recently, the JADC2 Cross-Functional Team, run by the Joint Staff J-6, codified data fabric as a “Department of Defense federated data environment for sharing information through interfaces and services to discover, understand, and exchange data with part- ners across all domains, security levels and echelons.” Te key capability components to achieve this outcome include metadata tagging, common interfaces, and security and access controls.


16


much of the collected data remains unpro- cessed and difficult to find, unbeknownst to the operator.


Tese technical challenges, coupled with the rising number of data sources avail- able to operators, underscores the need for autonomous, flexible data integration capabilities that harvest and deliver the required data when needed. Data fabric provides that common layer to enable data discovery, synchronization and security across multiple silos and platforms— addressing the conundrum of having both too much data and too little.


Metadata tagging describes character- istics about the data such as security or origin, and supports automated process- ing. Applying these tags using data fabric’s common design patterns and discoverable infrastructure helps make data visi- ble, accessible, understandable, trusted, interoperable and secure.


The fabric creates a larger pool of data that is more enriched, synchronized and transparent, and routes the right data to the operator who needs it.


Common data interfaces are standards that ensure data can cross boundaries where independent systems interact with- out losing its meaning. Tese interfaces are essential to getting data to and from data producers and consumers, including machine-to-machine accessibility. In both military and commercial instances of data fabric, this framework is achieved through application programming interfaces (APIs), which are software intermediaries that allow distinct applications to interact. Data fabric APIs are open and standards- based, which enables the Army to more quickly implement new and existing capa- bilities from multiple services and industry partners.


Te final components of data fabric focus on access controls and security. Access controls determine whether an individ- ual, or an AI algorithm, is permitted to search, retrieve, read, create or manipu- late data. Data security protects the data itself—at rest and in transit, regardless of the system hosting environment—from unauthorized discovery, modification or destruction. Together, access controls and security support efficient access to, and sharing across, varied data sources with- out compromising the integrity of the information.


PROJECT RAINMAKER Te Army’s major contribution to data fabric development thus far is called Proj- ect Rainmaker, a science-and-technology effort spearheaded by the Command, Control, Communications, Computers,


Army AL&T Magazine


Fall 2021


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