UCATS Unmanned Control & Tracking System Kurt Chewning Jennifer Greene Dave Manley Jeanette Smith John Smith Team DJ 3 K

UCATS – Final Presentation 2 2 Agenda Introduction Problem & Mission Statements Concept of Operations System-of-System Description Processes & Design Products Stakeholder Value Mapping Architecture (Functional & Physical) Algorithm Development Simulation Demonstration Business Case Conclusions & Future Work

Introduction Problem:  Coordinating airborne Unmanned Aerial Vehicles (UAVs) to intercept and track a Target Of Interest (TOI) in an urban environment is time consuming and labor intensive. 3 UCATS – Final Presentation

4 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 5 people to 1  Reduce time required to calculate TOI intercept from 45 minutes to 5 minutes

UCATS – Final Presentation 5 5 Problem Scoping - CONOPs

UCATS – Final Presentation 66 Problem Scoping - System-of-Systems (SOS) Functionality Operator Accepts Tasking and Provides Feedback Requests TOI Intercept Plans Interact w/UCATS Loads Local Maps onto UCATS Review & Concur or Edits Plans Confirm TOI Location Tasking Authority Determine TOIs to Track Tasks Operator Generate TOI Tracking Tasking Provides Maps UAV Provide Position Data to UCATS Communicate w/UCATS Autonomously Track TOI Provide Surveillance Data Conduct Search Pattern (as needed) Ask operator for TOI Confirmation UCATS Recommend Intercept Plan – Predict TOI Location – Determine if Intercept is feasible – Recommend UAV Intercept Course – Recommend UAV-to- TOI Assignment Comm w//UAV(s) Provide Surveillance video from UAV(s) Accepts Requests / Provides Feedback Autonomous Tracking System 6 UCATS – Final Presentation

System Engineering Process Development Model: “Vee” Model  Developed fidelity of deliverables and design artifacts using spiral development philosophy (Not necessarily spiral model) Process used to develop the UCATS:  Defined System Level Problem – i.e. Defined scope of problem  Developed Requirements  Determined System Level UCATS Design Defined UCATS functionality Developed Level 1 and 2 Functional and Generic Physical architecture Developed Instantiated architecture Developed HCI Spec with Usability Study UCATS – Final Presentation 7 7

Systems Engineering Management Statement of Work (SOW): Description of customer deliverables Program Management Plan  Linked Schedule  Org & Roles and responsibilities  Deliverables and design artifacts w/POCs Business Case – Describes UCATS business concept Risk Management Plan  Used to mitigate all risks Systems Engineering Management Plan (SEMP)  Systems Engineering Process Description  Engineering Tools: CORE for architecture design Visio for SysML modeling Google Maps/Google Earth API Matlab Eclipse IDE for JavaScript HTML for the algorithm Product Assurance Plan (PAP) – Quality Requirements  Single POC generates artifact  Peer review of artifacts Configuration Management (CM) Control – Website UCATS – Final Presentation 8 8

99 UCATS System Design Products Problem Scoping Products:  Concept of Operations (CONOPs)  Stakeholder Value Mapping (SVM)  Use Cases  External System Definition & Diagrams Requirements: Systems Requirement Specification (SRS) UCATS Architecture:  Analysis of Alternatives (AoA)  Functional Model  Communications Physical Architecture  Interface Physical Architecture  Algorithm  Command & Control Stations  HCI Specification  Functional Architecture  Generic Physical Architecture  Instantiated Architecture  Prototype w/Algorithm Reporting: Final Report and Presentation UCATS Architecture:  System Modeling: Activity Diagrams 9 UCATS – Final Presentation

UCATS Schedule UCATS – Final Presentation 10

UCATS – Final Presentation 11 Problem Scoping - SVM Key Civilian Stakeholders  SEOR Sponsor – K.C. Chang  SEOR Faculty  Team DJ3K SVM was key document in identifying AoA design down-select criteria CriteriaRelative Weight Performance53 Accuracy53 Interoperability52 Availability52 Usability51 Security50 Extensibility47 Flexibility47 Reliability47 Safety45 Agility44 Reproducibility41 Portability33 Affordability32 Maintainability31 Transparency of Operations19 11 UCATS – Final Presentation

Problem Scoping – System Level Problem UCATS – Final Presentation 12 Use Cases  Describes how system is used  Develop Target of Interest (TOI) Intercept Plans  Receive Video from UAV Tracking Operations  Develop Intercept Plans for New Tasking SOS Activity Diagram  Describes external system activities External Systems Diagram  Shows external system interactions w/UCATS  Basis for UCATS Functionality P-Diagram  Basic UCATS Functionality System Level Problem Definition Process 12 UCATS – Final Presentation

System Level Problem - P Diagram UCATS – Final Presentation 13 UCATS InputsOutputs Controllable Uncontrollable Maps (Topology) UAV location Operator interface TOI location TOI Priority TOI ID Request UAV Video Power TOI path Weather Designation of NFZ LOS & SATCOM interferences Algorithm (Priority) Functional & Physical Architecture Human Interface UAV to TOI assignment Intercept Route Communication to UAV

14 Architecture - UCATS Functionality Level 1 Functionality - Provide Command and Control Functions  Functionality determined using AoA UCATS Activity Diagram  Expansion of SOS Diagram  Shows interactions of UAV, Operator, and UCATS UCATS Level 1 Functional Architecture  Provides ins, outs, and constraints between UCATS  Basis for Level 2 Decomposition UCATS Functional Architecture Definition Process 14 UCATS – Final Presentation

15 Architecture - UCATS Level 1 Functional Hierarchy 15 UCATS – Final Presentation

UCATS Instantiated Architecture [1] Communication Module  Most trade-off and most affected by technology upgrades  Key technology considerations: Encryption technology Satellite Communication (SATCOM) radios Bandwidth  Key design Considerations UAVs use both SATCOM and Line-of-Sight (LOS) Radio Buildings in urban areas will restrict LOS comms Processors – One main UCATS processor(s) Simpler and more reliable than processor for each functionality Software Architecture:  Integral part of UCATS design  HCI Design part of usability assessment  Algorithm part of prototype UCATS – Final Presentation 16 UCATS – Final Presentation

UCATS Level 1 Generic Physical Architecture UCATS – Final Presentation 17 UCATS – Final Presentation

18 UCATS Instantiated Architecture Stationary ground control station  Wheeled trailer for high mobility Ground Control Station Contains  SATCOM and LOS radios  Encryption module  Operator station: PC w/ two CPUs UCATS software Two displays for operator interface One display for surveillance video. Communications relay UAV for LOS Comms Key Down-Select Criteria  Meet UCATS functionality and SRS  Extensibility – Encouraged Modular Design.  Simplicity 18 UCATS – Final Presentation

19 Simulation Development Previous Efforts: Tracking algorithm previously developed  Tangent-plus-Lyapunov Vector Field Guidance (T+LVFG)  MatLab Algorithms Incorporated Google Earth Visualization (GUI) Designed for 2 UAVs & 2 TOIs  UAV 1 tracks TOI 1  No TOI priority Current Efforts: Allow for various combinations of UAVs and TOIs Obstacle Avoidance TOI Priority Enhance web interface with user Spiral development

Simulation & Priority Algorithm Development AoA Evaluation Criteria  Optimization  Performance  Flexibility  Maintainability TOI Priority  Local Optimization UAV with shortest time assigned to TOI  Global Optimization UAVs collectively travel to TOIs in shortest time If all priorities are different results are same as Local 20 UCATS – Final Presentation

21 Simulation Demonstration 21 UCATS – Final Presentation

22 Simulation Demonstration 22 UCATS – Final Presentation

23 Simulation Demonstration 23 UCATS – Final Presentation

24 Simulation Demonstration 24 UCATS – Final Presentation

25 Business Case WorseBaselineBetter NPV$4,729,614$20,894,683$41,144,092 IRR19%25%40% Breakeven point8.6 yrs7 yrs5.2 yrs Cost-of- Capital15%10% Market Strategy Cost Model Sensitivity Analysis 25 UCATS – Final Presentation

Business Case UCATS – Final Presentation 26 Decision Analysis Influence Diagram Decision Tree Tornado Diagram 26 UCATS – Final Presentation

UCATS Conclusions UCATS system design used SE processes  Deliverables: PAP, SEMP, RMP, value mapping, business case, etc. UCATS implements a unique algorithm  Recommend local optimization Recommend use of a relay UAV Designed for generic UAV use  Customer Choice  Modularity & Extensibility Reduces manpower  Number of operators from 5 to 1 Operates efficiently  TOI tracking is estimated to take approximately 5 minutes with UCATS vs 45 minutes to track 5 TOIs UCATS – Final Presentation 27 UCATS – Final Presentation

SYST 798 Conclusions Addressed requirements for course  Developed a complex systems project in the field of SE  Researched and in detail defines a problem to simulate a real-life proposal  Conceives of possible solutions  Justified down-selection  Developed a plan of scheduled activities to accomplish that task  Identified and conducted appropriate AoAs, system level modeling, and economic feasibility that supported the proposed solution  Provide an oral presentation, written report and website 28 UCATS – Final Presentation

Future UCATS Work Conduct detailed design of UCATS hardware:  Select the specific UCATS Components  Determine if UCATS should include communication UAV May get technology improvement with SATCOM Customer may decide UAV costs to expensive and not require continuous stream of surveillance video Conduct detailed design of software:  Key aspect of SW development involves HCI design  Need top refine with usability testing Improve fidelity of algorithm  Fuel levels & consumption rates  Wind speed/direction, weather conditions  Smaller-sized vehicles Update Business Case to reflect final design decisions 29 UCATS – Final Presentation

Thanks Dr. Chang - Sponsor Ashwin Samant - Sponsor Dr. Speller - Advisor 30 UCATS – Final Presentation

Questions?

Backup Slides

UCATS - Status Report 33 UCATS Risks Created a Risk Management Plan to identify UCATS risks. Priority Risk Risk ID Number Risk TitleProbabilityImpact Risk Level Change Responsible Person 1001Communications Reliability Frequent Extremely High.41NEWTeam DJ 3 K 2002UAV Assignment Algorithm Occasional Extremely High.27NEWTeam DJ 3 K 3003Timeframe OccasionalHigh.15NEWTeam DJ 3 K 4004Team Distance Constraints LikelyModerate.06NEWTeam DJ 3 K 5005Routing of UAVs UnlikelyHigh.005NEWTeam DJ 3 K

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

System Level Problem - Use Case UCATS – Final Presentation 35 Use Cases  Develop Target of Interest (TOI) Intercept Plans  Receive Video from UAV Tracking Operations  Develop Intercept Plans for New Tasking

UCATS Level 2 Generic Physical Architecture UCATS – Final Presentation 36 UCATS – Final Presentation