UCATS Unmanned Control & Tracking System

1. UCATSUnmanned Control & Tracking System Team DJ3K Kurt Chewing Jennifer Greene Dave Manley Jeanette Smith John Smith UCATS - Status Report

2. Agenda • Problem & Mission Statements • Schedule • Conops • Completed Tasks • Ongoing Tasks • Website • Stakeholder Value Mapping • UCATS Risks • System-of-System Description • Requirements • Architecture (Functional & Physical) • Algorithm Development • Future Plans UCATS - Status Report

3. Problem Statement • Tracking Targets of Interest (TOIs) in densely populated areas present unique and difficult problems when ensuring public safety and security. • Coordinating airborne UAVs to intercept and track a TOI in an urban environment is time consuming and labor intensive. UCATS - Status Report

4. Mission Statement • The UCATS is a command and control system designed to: • Route UAVs to TOIs • Monitor the UAV location • Redirect the UAVs when new tasking arrives • Primary Mission: • To recommend which airborne UAVs should track TOIs • Direct the UAVs on a TOI intercept course • Monitor UAV position • Redirect the UAVs as new TOI tasking becomes available. • Goal: • Reduce manpower from five operators to a single operator • Reduce mission planning time from 45 minutes to 15 minutes or less UCATS - Status Report

5. CONOPs UCATS - Status Report

6. Networked Schedule UCATS - Status Report

7. Completed Tasks • Project Management Plan (PMP) • Statement of Work (SOW) • Systems Engineering Management Plan (SEMP) • Risk Management Plan (RMP) • Product Assurance Plan (PAP) • System Requirements Specification (SRS) • Concept of Operations (CONOPs) • Use Cases • Functional Model Analysis of Alternatives • External System Definition & Diagrams UCATS - Status Report

8. Ongoing Tasks • Stakeholder Value Mapping (SVM) • Functional Architecture • Physical Architecture • Business Case • Analysis of Alternatives • Physical Architecture (Comms, Interface, Video, etc) • Command & Control Stations • Algorithm Development • Website UCATS - Status Report

9. Website UCATS - Status Report

10. Stakeholder Value Mapping • Homeland Defense/Law Enforcement • FBI • CIA • DHS • DEA • CBP • Military • Army • Navy • Air Force • National Guard • Civilian • SEOR Sponsor – K.C. Chang • Team DJ3K • Urban Community • Industry UCATS - Status Report

11. Stakeholder Needs Analysis • Accuracy • Affordability • Safety • Security • Reliability • Maintainability • Usability • Availability • Transparency of Operations • Interoperability • Portability • Reproducibility • Performance UCATS - Status Report

12. SVM Needs Analysis [2] • Work to be completed: • Finalize Needs • Complete assessment UCATS - Status Report

13. UCATS Risks • Created a Risk Management Plan to identify UCATS risks. UCATS - Status Report

14. UCATS Risks 5 Probability 4 3 2 Consequence 1 1 2 3 4 5 #1 #3 Technical Risk Schedule Risk Communications Reliability Risk Mitigation: -- Conduct an AoA on the method of communication. Timeframe #4 Technical Risk Team Distance Constraints #2 Technical Risk UAV Assignment Algorithm Risk Mitigation: -- Work very closely with Ashwin Samant. -- Interface regularly with project sponsor. -- Hold frequent technical reviews. #5 Technical Risk Routing of UAVs High - Major disruption in the plan. Med - Some disruption in the plan. Low - Little or no disruption. UCATS - Status Report

15. System-of-Systems (SOS) Functionality UCATS - Status Report

16. SOS External Systems Diagram UCATS - Status Report

17. UCATS SRS Mission Requirements • UCATS shall generate an intercept plan • Predicted Target of Interest (TOI) TOI location • TOI intercept feasibility • UAV intercept routes to TOI • UAV(s) to TOI assignments • UCATS shall be capable of directing new tasking to UAVs to new TOIs. • UCATS shall communicate with generic medium size UAVs up to 40 miles away from the UCATS. • Only one operator is needed to interface with UCATS to obtain full UCATS functionality. • UCATS shall command and control up to five UAVs. UCATS - Status Report

18. UCATS Functional Architecture [1] • Used AoA to determine UCATS functional architecture • UCATS top level function Provide Command and Control Functions decomposed into four level one functions • Communicate With UAV • Accept Operator Requests and Provide Feedback • Compute UAV Presets • Accept Video and Display UCATS - Status Report

19. UCATS Functional Architecture [2] UCATS - Status Report

20. UCATS Functional Architecture [3] • Level One Functions mapped to UCATS components • Functions decomposed two levels deep • Input, Outputs, and Constraints defined • IDEF0 used to model Functional Architecture • Future Task, Map Functional and Physical Architect to Operational Requirements UCATS - Status Report

21. UCATS Functional Architecture [4] UCATS - Status Report

22. UCATS Generic Physical Architecture UCATS - Status Report

23. UCATS Generic Physical Architecture • UCATS Built from four components • Comms Module: Sends messages to and receives data from the UAV • Interface Module: comprises the Human Computer Interface for UCATS • Presetting Algorithm Module: contains the algorithm needed to provide operator recommendations • Video Module: receives and displays video UCATS - Status Report

24. Algorithm Past Development • Tracking algorithm previously developed • Tangent-plus-Lyapunov Vector Field Guidance (T+LVFG) • MatLab Algorithms • Incorporated Google Earth Visualization (GUI) • Java Script • Designed for 2 UAVs & 2 TOIs UCATS - Status Report

25. Algorithm Current Development • Allow for various combinations of UAVs and TOIs • 5v5, 5v3, 3v5, etc • Obstacle Avoidance • Intergration with tracking algorithm • TOI Priority • What UAV should track which TOI • Greedy Algorithm • Enhance web interface with user • Spiral development UCATS - Status Report

26. Algorithm Current Development [2] • TOI Priority • 3 Cases • # of UAVs = # of TOIs • # of UAVs > # of TOIs • # of UAVs < # of TOIs • Highest priority TOI assessed first • Closest UAV to TOI is assigned based on distance • Dynamically changing TOI priority UCATS - Status Report

27. Algorithm GUI Development UCATS - Status Report

28. Algorithm Future Development • TOI Priority • UAV and TOI heading • UAV altitude for multiple UAVs tracking the same TOI • Communication Simulation • Loss of signal due to range • Loss of signal due to shadowing UCATS - Status Report

29. Future Plans • Continue work on… • Getting Stakeholder Approval/Comments on value mapping, SRS, and functional and physical architecture • Finalize Functional Architecture • Complete AoAs for Physical Architecture instantiation • Algorithm Development • Prototype • Business Case • Analysis of Alternatives • Website • Final Report & Presentation UCATS - Status Report

30. Questions? UCATS - Status Report