ARMY AL&T
Rucker, indicated the enablers that play a role in establishing joint service interoperability:
• Common operating picture (COP) forces.
• C2 for dynamic retasking within/ between components.
• Local/global distribution of video/ data with common links.
• Responsive sensor-to-shooter kill chain.
Soldiers assigned to the 4th Special Troops Battalion, 4th Brigade Combat Team (BCT), 1st Cavalry Division (Div.), UAS Platoon, move to a UAS launch and recovery site on Forward Operating Base (FOB) Hunter, Iraq. (U.S. Army photo by 1LT Joanne Cotton.)
Interoperability profiles for all Army UAS include:
• Universal Ground Control Station (UGCS).
• One System Remote Video Terminal (OSRVT).
• Tactical Common Data Link. • Manned/Unmanned Teaming.
The interoperability future of UAS lies with the UGCS and OSRVT. Among other capabilities, the UGCS provides the commander with the ability to control and receive data from multiple unmanned aerial types and tactical fl ex- ibility; enables UGCS/OSRVT-linked systems; maximizes UAS operator/ maintenance training and simulation; and provides payload products to the network for exploitation. Carlile advised that, “UGCS will control all types of UAS, as well as have the ability to oper- ate eight UAS at the same time.” This allows the ground commander to control the UAS using point-and-click technol- ogy through the OSVRT. The OSVRT increases the tactical commander’s situ- ational awareness of the operational environment by allowing Soldiers to mark and capture tactical information onscreen. It has multiple confi gurations for tactical fl exibility and correlated sensor data and map with metadata.
38 APRIL –JUNE 2010
Interoperability is also achieved through the Ground-Based Sense and Avoid System (GBSAA). A networked SoS, GBSAA is composed of system ground- based sensors, data links, procedures, logic, and interfaces. These work to detect an airborne intruder and declare a threat, if applicable, in time to allow the UAS to react and prevent air collision.
Joint Service Interoperability There is no doubt that making UAS joint across the services is an integral aspect of employing UAS successfully. “The joint is no longer conceptual; it’s a reality, and arguably, a necessity,” said COL Jeffrey N. Colt, Commander, Joint UAS COE, Creech Air Force Base (AFB), NV. He also posed the question, “As we look to joint interoperability, the bottom line is, what’s the right metric and how much, and how do we measure its effects?” Across the full spectrum of operations, the services must be corre- lated. COL Robert J. Sova, U.S. Army Training and Doctrine Command Capability Manager for UAS, Fort
• Common terminology/TTPs. • Common training for joint missions. • Common processing, exploitation, and dissemination architecture.
Another key aspect of joint service interoperability is complex airspace management. “As much as we like to segment the airspace among the services, the reality is that it’s one airspace, and we have to integrate within it and oper- ate together,” said COL Anthony W. Potts, Project Manager (PM) Aviation Systems. “We lock up so much airspace. The ability to manage it effectively is truly a combat multiplier.” Part of this is adopting a conceptual SoS view where there is seamless integration between the civilian and tactical airspace.
The Joint UAS COE, headquartered at Creech AFB, represents the joint stake- holder and realizes many of the joint issues. The COE focuses on nonmate- rial solutions and training and readiness. Focus areas include national airspace access, bent-down locations and air- space requirements, operator standards and joint mission qualifi cation require- ments, satisfying the see-and-avoid requirement, and solutions for work- ing better with coalition partners. Colt advised that the development of
We’ve learned that UAS are continuing to prove themselves in key operational roles for the Army—and for the other services—on a daily basis.
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
