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
WIN-T INCREMENT 2


CW5 Leslie Cornwall (left) and MAJ Marcus Odum from the U.S. Army Training and Doctrine Command Capabilities Manager Networks and Services examine WIN-T equipment during a WIN-T Increment 2 Engineering Field Test at Fort Huachuca, AZ. (U.S. Army photo courtesy of Program Executive Office Command, Control, and Communications-Tactical (PEO C3T).)


capability to the company commander. The SNE’s primary purpose is to provide a combat radio network extension to


“heal” tactical radio nets using the larger WIN-T backbone.


A side benefit is that the company com- mander’s vehicle becomes a lower-level node connected directly to the larger WIN-T backbone.


The SNE’s combat radio network extension was specifically designed for lower-echelon radio nets, such as Soldier Radio Waveform, Enhanced Position Location Reporting System, and Single Channel Ground and Airborne Radio System. These can be broken into separate networks, or fractured, because of terrain features between formations that make line-of-sight communications impossible.


EXTENDING THE NETWORK The Soldier on the ground is the Army’s greatest asset and is in many respects our most important sensor on the battlefield. Yet network users at echelons of company level and below have the greatest disadvantages.


There are myriad challenges in extending the network down to the lowest levels of the tactical formation. One of those chal- lenges is to effectively provide satellite communications (SATCOM) down to these disconnected, geographically dis- tributed lower echelons.


To help alleviate this particular issue, WIN-T Increment 2 introduces the Sol- dier Network Extension (SNE), which brings an initial SATCOM OTM


The SNE has the capability to heal that network over the SATCOM component of the WIN-T network. But, because it is a node in the WIN-T network, the company commander’s vehicle now has limited network connectivity to the tacti- cal backbone, both ATH and OTM.


FACILITATING OPERATIONS Another challenge throughout the Army formation, and a major challenge for the S-6, is network operations (NetOps): the planning, administration, management, response, initialization, and spectrum and frequency allocation of the network.


WIN-T Increment 2 introduces the framework that begins to integrate the NetOps tools behind a single standard


human computer interface, almost like a “digital dashboard.” It also marks the beginning of policy-based network man- agement of the tactical network.


The S-6 and G-6, based on the com- mander’s intent and mission execution, now have the tools to manage spectrum very much like we currently manage and prioritize indirect fires. WIN-T Incre- ment 2 also allows an unprecedented level of digital participation by the S-6 and G-6 in the military decision-making process.


Key to the planning and execution is the initial capability in the tools pro- vided to plan the network and “weight the main effort.”


As an example, if a battalion is the main effort, it can be allocated priority for mes- sage traffic by adjusting the quality of service (QoS) of the traffic in the network. If the battalion needs additional band- width, that, too, can be adjusted.


These policies can be pushed out to the WIN-T nodes remotely over the network. Once the agreed-upon policies are pushed out, the WIN-T Increment 2 network will automatically prioritize informa- tion according to precedence or category. Thus, mission-critical messages, such as 9-line medevac requests or calls for fire, receive higher priority. Vital information is delivered ahead of routine data.


This QoS, provided in part by a QoS edge device, is in addition to the standard QoS that is inherent in the current Internet Protocol Network.


A S C . A RMY.MI L 25


ACQUISITION


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