Design of UAV Systems

1. Design of UAV Systems c 2003 LM Corporation Control stations • Lesson objective - to discuss • Control stations • including … • Functions • Approaches • Sizing • Example problem Expectations - You will understand the fundamentals of UAV control stations and the overall size, weight and complexity of the associated systems 10-1

2. Design of UAV Systems c 2003 LM Corporation Control stations Importance • UAV systems cannot operate without control stations • - Even if they are autonomous • A good understanding of control station design issues and requirements are among the most important issues addressed during UAV pre-concept design 10-2

3. Design of UAV Systems http://www.fas.org/irp/program/collect/pioneer.htm Launch and Recovery http://www.fas.org/man/dod-101/sys/ac/equip/afmss.htm Mission Planning http://www.fas.org/irp/program/collect/pioneer.htm http://www.fas.org/irp/program/disseminate/uav_tcs.htm Mission and Payload Management Information Processing and Dissemination c 2003 LM Corporation Control stations Control Functions 10-3

4. Design of UAV Systems c 2003 LM Corporation Control stations levels of control l UAV Tactical Control System (TCS) Definitions • Level 1 - • Receipt and transmission of secondary imagery or data. • Level 2 - • Receipt of imagery or data directly from the UAV. • Level 3 - • Control of the UAV payload. • Level 4 - • Control of the UAV, less takeoff and landing. • Level 5 - • Full function and control of the UAV to include takeoff and landing. • Source -http://www.fas.org/irp/program/disseminate/uav_tcs.htm 10-4

5. Design of UAV Systems Direct control Flight path control http://www.fas.org/irp/program/collect/eagle-eye.htm d/dt,dh/dt and dV/dt Control stick …or Navigation Control http://www.fas.org/irp/program/collect/uav_gcs.htm Attack return etc. UAV Annual Report FY 1997 DarkStar Fully autonomous Supervised control c 2003 LM Corporation Control stations Levels of autonomy 10-5

6. Design of UAV Systems http://www.fas.org/irp/program/disseminate/uav_tcs.htm http://www.fas.org/irp/program/collect/eagle-eye.htm Multi-System System Unique c 2003 LM Corporation Control stations Span of control 10-6

7. Design of UAV Systems http://www.fas.org/irp/program/disseminate/uav_tcs.htm Ground Rear Area http://www.fas.org/irp/program/collect/pioneer.htm Sea http://www.fas.org/irp/program/disseminate/uav_tcs.htm Forward Area http://www.army.mil/armyimages.htm Air Lockheed Martin Aeronautics Company c 2003 LM Corporation Control stations Control Location 10-7

8. Design of UAV Systems c 2003 LM Corporation Control stations Global Hawk example 10-8

9. Design of UAV Systems c 2003 LM Corporation Control stations Global Hawk MCE 10-9

10. Design of UAV Systems c 2003 LM Corporation Control stations Global Hawk LRE 10-10

11. Design of UAV Systems c 2003 LM Corporation Control stations Pioneer GCS 10-11

12. Design of UAV Systems c 2003 LM Corporation Control stations Predator GCS Trojan Spirit GDT 30 ft x 8 ft x 8 ft commercial van The GCS consists of (1) a pilot position and (2) a payload operator position (interchangeable), (3) a Data Exploitation, Mission Planning and Communications position where imagery is annotated and initially exploited, and a (4) SAR workstation Source http://www.fas.org/irp/agency/daro/predator/toc.html 10-12

13. Design of UAV Systems c 2003 LM Corporation Control stations Pointer GCS 10-13

14. Design of UAV Systems c 2003 LM Corporation Control stations UCAV control (status) 10-14

15. Design of UAV Systems c 2003 LM Corporation Control stations Another common GCS 10-15

16. Design of UAV Systems c 2003 LM Corporation Control stations And another 10-16

17. Design of UAV Systems c 2003 LM Corporation Control stations Mission control issues Mission planning concept Site requirements Vehicle control concept Manpower requirements Payload control concept Overall size Product exploitation concept Estimated cost Weapon control concept (for UCAV) 10-17

18. Design of UAV Systems • Mission planning concept - For military users, manned and unmanned aircraft will almost certainly use common mission planning tools. Example - USAF Mission Support System (AFMSS) has individual data modules that tailor it for each aircraft in the fleet. Global Hawk and Predator missions are planned like any other aircraft • - Civilian users will probably do the same - the selection of UAV mission planning tools may be driven by what exists • Vehicle control concept will be driven by near vs. long term cost considerations and mission needs • - Autonomy costs a lot to develop, direct control doesn’t • - Autonomy will cut long term operations and support costs c 2003 LM Corporation Control stations Selection considerations 10-18

19. Design of UAV Systems c 2003 LM Corporation Control stations Considerations - cont’d • Payload control concept will be driven by the ConOps • - If the ConOps is to bring data back for analysis, automated payload control will be cost effective • - If the ConOps requires real time data analysis and sensor retasking, direct control will probably be required • - Automation can be used to reduce operator work load • Payload product exploitation concept will also be driven by Conops • - If data is to be sent elsewhere for analysis, no on-site processing will be required • - Otherwise, significant on-site processing will be required • - Efficient data processing tools will be required to keep the task work load down and the crew size small 10-19

20. Design of UAV Systems c 2003 LM Corporation Control stations Considerations - cont’d • The weapon control concept (for UCAV) will be driven by ConOps and weapon type • - It is highly unlikely that machines will be allowed to attack without human authorization unless a target is preplanned and fixed (like a cruise missile) • - Otherwise operator intervention and authorization to attack will be required • - The amount of information required to support a decision to attack may be substantial • - Fire and forget weapons can also be highly automated • - On board guided weapons by definition require high levels of operator involvement 10-20

21. Design of UAV Systems c 2003 LM Corporation Control stations Considerations - cont’d • Site requirements - At a minimum, a control station will be required at the launch and recovery area • - Depending on the ConOps, other control stations may be required • - Mission control is often collocated with the user of the system or its product (Global Hawk example) • - Sometimes, multiple users are involved 10-21

22. Design of UAV Systems c 2003 LM Corporation Control stations Considerations - cont’d • Manpower requirements - With enough automation, a single operator should be able to handle multiple UAVs and their payloads • - To date, however, multiple operators are required for one UAV with the typical assignments being • (1) Launch and recovery • (2) Vehicle control • (3) Payload control • (4) Payload information processing • - Predator example (for 4 air vehicle squadron) • - 6 air vehicle operators • - 9 payload operators • - 9 data exploitation and mission planners • - 3 SAR imagery analysts 10-22

23. Design of UAV Systems c 2003 LM Corporation Control stations Sizing • Little public control station information is available • What information does exist is mostly from marketing brochures • - Lots of pictures, little substance • Janes UAVs and Targets has some data that we can parameterize for sizing purposes • The available data falls into two broad categories • Short range, portable systems • Van or trailer mounted long range control stations with environmental enclosures 10-23

24. Design of UAV Systems c 2003 LM Corporation Control stations Size and cost • Nominally each operator station in an enclosure requires about 350 - 400 cuft at about 12 lbs/ft^3 • There is very little publicly available control station cost information; Global Hawk CGS @ $45M (including comms), Predator @ $6.8M (excluding comms) 10-24

25. Design of UAV Systems c 2003 LM Corporation Control stations Next subject • Lesson objective - to discuss • Control stations • including … • Functions • Approaches • Sizing • Example problem 10-25

26. Design of UAV Systems 27.4 Kft 212 nm 27.4 Kft 10 Kft 158 nm 27.4 Kft 100 nm 200 nm x 200 nm c 2003 LM Corporation Control stations Example problem • Five medium UAVs, four provide wide area search, a fifth provides positive target identification • WAS range required (95km) not a challenge • Only one UAV responds to target ID requests • No need to switch roles, simplifies ConOps • No need for frequent climbs and descents • Communications distances reasonable (158nm & 212 nm) • Speed requirement = 280 kts • Air vehicle operating altitude • differences reasonable • We will study other options as trades • Where should the control station(s) be located? • How big are they? 10-26

27. Design of UAV Systems c 2003 LM Corporation Control stations Considerations • Command and control approach • How to control the UAVs, where to locate control stations and how many operators to employ • Control options • Direct control (remotely piloted) • Inexpensive but high operations and support risk • Navigation (waypoint and flight path) control • Slightly more complicated but low risk operations • Supervised control (high level mission management) • Operational benefits but complicated development • Autonomous • Minimizes operators but very complicated to develop • Control locations will be driven by our threshold requirement approach • Minimum requirement is for one control station • Located at the launch and recovery base • Navigation control approach will minimize risk 10-27

28. Design of UAV Systems 27.4 Kft 212 nm 27.4 Kft 10 Kft 158 nm 27.4 Kft 100 nm 200 nm x 200 nm c 2003 LM Corporation Control stations Number of operators • Assume one air vehicle operator can control all wide area search operations • Low work load activity – basically a monitoring task • Another air vehicle operator handles ID operations • Controls both air vehicle and payload • Wide area search/moving target payload operations require one operator (at a • minimum) • Fourth operator processes • data and disseminates • intelligence to users • Fifth operator for launch • and recovery and backup • Sixth operator to control • air and ground computer and • communications systems 10-28

29. Design of UAV Systems c 2003 LM Corporation Control stations Updated requirements • Control Station element • Waypoint/flight path control • 6 control consoles [air vehicle/EO/IR (2), SAR (1), C3I (1), product process/dissemination(1), launch and recovery(1)] C3I = C2I + Communications 10-29

30. Design of UAV Systems c 2003 LM Corporation Control stations Homework • Assess control station requirements for your project and develop a approach that you think will work (1) Determine control station locations (2) Estimate number of operators and seats (3) Estimate weight(s) and volume(s) (4) Document your derived requirements • Submit your homework via Email to Egbert by COB next Thursday. Document all calculations. 10-30

31. Design of UAV Systems c 2003 LM Corporation Control stations Intermission 10-31