HONEST BROKER
sessions and white paper solicitations that there were a whole host of capabilities that are truly novel approaches, that really pushed us to say, hey, let’s take it to the next level and see this in action. And that’s what led to the burn-off events. Te other success story is AI for electronic warfare. We thought that this would be a long-term type of action for the RCO, but after discussing some of the capabilities at one of our open-door sessions, we’re pushing hard to integrate it to support require- ments for deployed forces. We believe we can bring AI in and it will begin to help reduce the cognitive burden and workload on electronic warfare officers.
Other efforts we’re looking at now are long-range fires and loi- tering space munitions. Loitering munitions are similar to UAVs [unmanned aerial vehicles], but are also munitions that can loi- ter in a space until a target is identified. Loitering munitions are already on station and can attack without calling in an airstrike or forces.
Tis all happened by chance. We were having discussions about other technical areas and this came up, and we brought it back to RCO leadership, who wanted to explore it more. Tat’s one of the benefits of having us out there: You can identify solutions you didn’t think were on the front burner and were still several years away. Truly, this is what the ETO is meant to do.
If an industry partner has an idea they want to share with the ETO, where do they start?
We encourage everyone to visit our website (http://rapid
capabilitiesoffice.army.mil/eto/) or LinkedIn page (https://
www.linkedin.com/company/us-army-RCO). We use both of these sites for outreach and are continually updating them with any current events, upcoming efforts, RFIs [requests for information] and more. In addition, we are part of SOCOM’s tech scouting database Vulcan. Tis enables any company with access to submit commercial technology. Te database is not just sorted into an RCO category, or SOCOM entries, but instead the technology is shared so any government orga- nization looking for technology for, say, PNT, can search it and see what pops up. It is meant to be collaborative and to break down silos. Te link to our submission into Vulcan is through our website, on the ETO page, by clicking on Submit a Technology.
Is the ETO evolving as the mission of the RCO begins to expand beyond electronic warfare, PNT and AI?
It is evolving and will continue to evolve. I see it as a living organization that will continue to meet whatever the needs of the RCO and Army are. It’s already evolved from the days of just being an ombudsman, being that filter, to now doing these small bets in different areas, trying to test drive capabilities and really putting ourselves out there. We are always looking at what the next big focus might be for the Army. It can change rapidly. For example, we could begin looking at capabilities to support megacity operations. With these operations, you have to think about it differently, thinking about how you use PNT while on a clearing mission of a 100-story building versus a movement and maneuver in an open space; being able to communicate with folks in subway tunnels or wherever it might be. It’s much harder to communicate through traditional means [in these situations], and we are looking at how we can deliver prototypes to deployed forces in these areas more rapidly.
Any set goals for the next 12-15 months?
By the end of the year, I would like to see a clear transition path for whatever comes out of those small bets we’re placing. I really, truly believe there are capabilities out there today that could help provide enhanced function to either electronic warfare or PNT in helping achieve a rapid capability to support deployed forces. And we are starting to see some of those transition paths build now. Already, in just a few short months, the RCO fielded initial mounted and dismounted electronic warfare prototypes to forces in Europe that are helping them detect and under- stand enemy activity in the electromagnetic spectrum. We’ll continue along this path by upgrading those prototypes based on user feedback, while also focusing on what’s next. What capability gap will combatant commanders come to us with next, and how can we move quickly enough so that we are not caught without a rapid solution?
For more information, go to
http://rapidcapabilitiesoffice.army. mil/eto/ or
http://rapidcapabilitiesoffice.army.mil.
MS. NANCY JONES-BONBREST is a staff writer for Data Systems Analysts Inc., providing contract support to the Army Rapid Capabilities Office. She holds a B.S. in journalism from the University of Maryland, College Park. She has covered Army modernization for several years, including multiple training and testing events.
36
Army AL&T Magazine
April-June 2018
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
