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
Wrangling Radio REQUIREMENTS


Using lessons learned from sof tware-defined radio development, TRADOC and PM Tactical Radios have developed a unified approach to requirements development, informed by feedback from industry and the user community, that evolves requirements and technologies incrementally.


by COL James P. Ross and Mr. Paul Chernek S 36 defined radios


oftware-defined radios are an integral part of the Army’s future mission command network and the way of the future for tactical communications at the lowest echelons. Unlike older non-networking radios, software- transmit


information using high-bandwidth


waveforms, which function like a wireless network to allow Sol- diers to exchange voice, data and video over the air. With this secure waveform software loaded onto radio “boxes,” the radios act as network nodes that can route and retransmit information in austere environments, including around obstacles and beyond line of sight. Together, the radios and waveforms provide digital communications on-the-move down to the Soldier level.


Technical advances to hardware and software, including radios that support multiple waveforms and waveforms that provide more capability and flexibility, have led to significant changes in the Army’s approach to tactical radio procurement and field- ing by enabling the government to manage the waveforms and lean on industry to fill the hardware requirements. Our strong partnership of the Army acquisition community, the U.S. Army Training and Doctrine Command (TRADOC) and industry is allowing us to adjust and improve tactical radio requirements to support Force 2025 and Beyond.


EARLY JTRS When the Joint Tactical Radio System (JTRS) program began in 1997, the concept of a software-defined radio was just begin- ning. Recognizing the technology’s potential, the military at first tried to pack as many features into individual radios as possible. Te thinking was that “software-defined” meant there would be little impact on the hardware. However, one of the lessons learned during this time was that adding numerous capabilities to the radios affected the hardware and did not always yield the best product. For example, original requirements for the two-channel Manpack Radio had it supporting more than two dozen waveforms for various communications features and an outdated internal barometer for positioning. Such requirements made the radio exceedingly large and heavy—and its power requirements rendered it operationally useless.


Working to refine the requirements, the Army eliminated the barometer and reduced the number of waveforms for the Man- pack Radio to three—Soldier Radio Waveform (SRW), Single Channel Ground and Airborne Radio System (SINCGARS) and ultra-high frequency Tactical Satellite, with the Mobile User Objective System added when its waveform development was completed. With fewer waveforms, the radio could still fulfill


Army AL&T Magazine


July-September 2015


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