Transcript UCATS Unmanned Control & Tracking System

UCATS
Unmanned Control & Tracking System
Team DJ3K
Kurt Chewning
Jennifer Greene
Dave Manley
Jeanette Smith
John Smith
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
UCATS – Final Presentation
2
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.
UCATS – Final Presentation
3
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
4
Problem Scoping - CONOPs
UCATS – Final Presentation
5
Problem Scoping - System-of-Systems (SOS)
Functionality
Autonomous Tracking System
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
Tasking
Authority
Operator
•
• Determine
TOIs to Track
• Tasks
Operator
• Generate
TOI Tracking
Tasking
• Provides
Maps
•
•
•
•
•
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
UCATS – Final Presentation
UCATS
Recommend Intercept
Plan
– Predict TOI Location
– Determine if Intercept
is feasible
– Recommend UAV
Intercept Course
– Recommend UAV-toTOI Assignment
• Comm w//UAV(s)
• Provide Surveillance
video from UAV(s)
• Accepts Requests /
Provides Feedback
•
6
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
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
8
UCATS – Final Presentation

UCATS System Design Products

Problem Scoping Products:






Concept of Operations
(CONOPs)
Stakeholder Value Mapping
(SVM)
Use Cases
External System Definition &
Diagrams
UCATS Architecture:

Requirements: Systems
Requirement Specification
(SRS)


UCATS Architecture:



System Modeling: Activity
Diagrams


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
Presentation
UCATS –– Final
Final Presentation
9
UCATS Schedule
UCATS – Final Presentation
10
Problem Scoping - SVM

Criteria
Key Civilian Stakeholders



SEOR Sponsor – K.C. Chang
SEOR Faculty
Team DJ3K
Performance
Accuracy
Interoperability
Availability
Usability
Security
Extensibility
Flexibility
Reliability
Safety
Agility
Reproducibility
Portability
Affordability
Maintainability
Transparency of Operations
Relative
Weight
53
53
52
52
51
50
47
47
47
45
44
41
33
32
31
19
SVM was key document in identifying AoA design down-select criteria
UCATS – Final Presentation
11
Problem Scoping – System Level Problem
System Level Problem Definition Process

Use Cases





SOS Activity Diagram


Describes external system
activities
External Systems Diagram



Describes how system is used
Develop Target of Interest (TOI)
Intercept Plans
Receive Video from UAV
Tracking Operations
Develop Intercept Plans for
New Tasking
Shows external system
interactions w/UCATS
Basis for UCATS Functionality
P-Diagram

UCATS – Final Presentation
Basic UCATS Functionality
12
System Level Problem - P Diagram
Uncontrollable
TOI path
Weather
Designation of NFZ
LOS & SATCOM interferences
Inputs
Maps (Topology)
UAV location
Operator interface
TOI location
TOI Priority
TOI ID Request
UAV Video
Power
UAV to TOI assignment
Intercept Route
Communication to UAV
UCATS
Outputs
Algorithm (Priority)
Functional & Physical Architecture
Human Interface
Controllable
UCATS – Final Presentation
13
Architecture - UCATS Functionality

UCATS Functional Architecture Definition Process
Level 1 Functionality Provide Command and
Control Functions


UCATS Activity Diagram



Expansion of SOS
Diagram
Shows interactions of
UAV, Operator, and
UCATS
UCATS Level 1
Functional Architecture


UCATS – Final Presentation
Functionality determined
using AoA
Provides ins , outs, and
constraints between
UCATS
Basis for Level 2
Decomposition
14
Architecture - UCATS Level 1
Functional Hierarchy
UCATS – Final Presentation
15
UCATS Instantiated Architecture [1]

Communication Module


Most trade-off and most affected by technology upgrades
Key technology considerations:




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)


Encryption technology
Satellite Communication (SATCOM) radios
Bandwidth
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 Level 1 Generic Physical
Architecture
UCATS – Final Presentation
17
UCATS Instantiated Architecture

Key Down-Select Criteria




Meet UCATS functionality and SRS
Extensibility – Encouraged Modular Design.
Simplicity
Stationary ground control
station


Ground Control Station
Contains




UCATS – Final Presentation
Wheeled trailer for high
mobility
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
18
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
UCATS – Final Presentation
19
Simulation & Priority Algorithm Development

TOI Priority

Local Optimization


Global Optimization



UAV with shortest time assigned to TOI
UAVs collectively travel to TOIs in
shortest time
If all priorities are different results are
same as Local
AoA Evaluation
Criteria




Optimization
Performance
Flexibility
Maintainability
UCATS – Final Presentation
20
Simulation Demonstration
UCATS – Final Presentation
21
Simulation Demonstration
UCATS – Final Presentation
22
Simulation Demonstration
UCATS – Final Presentation
23
Simulation Demonstration
UCATS – Final Presentation
24
Business Case



Market Strategy
Cost Model
Sensitivity Analysis
NPV
IRR
Breakeven
point
Cost-ofCapital
Worse
$4,729,614
19%
Baseline
Better
$20,894,683 $41,144,092
25%
40%
8.6 yrs
7 yrs
5.2 yrs
15%
10%
10%
UCATS – Final Presentation
25
Business Case


Decision Analysis
 Influence Diagram
 Decision Tree
Tornado Diagram
UCATS – Final Presentation
26
UCATS Conclusions

UCATS system design used SE processes


UCATS implements a unique algorithm




Customer Choice
Modularity & Extensibility
Reduces manpower


Recommend local optimization
Recommend use of a relay UAV
Designed for generic UAV use


Deliverables: PAP, SEMP, RMP, value mapping, business case,
etc.
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
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
UCATS – Final Presentation
28
Future UCATS Work

Conduct detailed design of UCATS hardware:


Select the specific UCATS Components
Determine if UCATS should include communication UAV



Conduct detailed design of software:



Key aspect of SW development involves HCI design
Need top refine with usability testing
Improve fidelity of algorithm




May get technology improvement with SATCOM
Customer may decide UAV costs to expensive and not require
continuous stream of surveillance video
Fuel levels & consumption rates
Wind speed/direction, weather conditions
Smaller-sized vehicles
Update Business Case to reflect final design decisions
UCATS – Final Presentation
29
Thanks



Dr. Chang - Sponsor
Ashwin Samant - Sponsor
Dr. Speller - Advisor
UCATS – Final Presentation
30
Questions?
Backup Slides
UCATS Risks
Created a Risk Management Plan to identify UCATS
risks.

Priority
Risk
Risk ID
Number
1
001
Communications Reliability
2
002
UAV Assignment Algorithm
3
003
Timeframe
4
004
Team Distance Constraints
5
005
Routing of UAVs
Risk Title
Probability
Impact
Frequent
Extremely
High
Occasional
Extremely
High
Occasional
High
Likely
Moderate
Unlikely
High
UCATS - Status Report
Risk
Level
Change
Responsible
Person
.41
NEW
Team DJ3K
.27
NEW
Team DJ3K
.15
NEW
Team DJ3K
.06
NEW
Team DJ3K
.005
NEW
Team DJ3K
33
UCATS Risks
#3
Schedule Risk
#1
Communications Reliability
Timeframe
#4
Technical Risk
Technical Risk
Risk Mitigation:
-- Conduct an AoA on the
method of communication.
Team Distance Constraints
Technical Risk
#5
Probability
5
4
Technical Risk
UAV Assignment Algorithm
3
2
Routing of UAVs
1
High - Major disruption in the plan.
Med - Some disruption in the plan.
Low - Little or no disruption.
#2
1
2
3
4
Consequence
UCATS - Status Report
5
Risk Mitigation:
-- Work very closely with
Ashwin Samant.
-- Interface regularly with
project sponsor.
-- Hold frequent technical
reviews.
34
System Level Problem - Use Case

Use Cases



UCATS – Final Presentation
Develop Target of Interest
(TOI) Intercept Plans
Receive Video from UAV
Tracking Operations
Develop Intercept Plans
for New Tasking
35
UCATS Level 2 Generic Physical Architecture
UCATS – Final Presentation
36