Test & Evaluation/Science & Technology Program Unmanned and Autonomous Systems Test (UAST)

1
Test Evaluation/Science Technology Program
Unmanned and Autonomous Systems Test(UAST)

• FY2009 Program Execution Review

2
Objectives

• Project Status
• UAST Accomplishments
• UAST Lessons Learned
• Summary

3
UAST Technology Overview

• TE capability shortfalls
• Predicting UAS Intelligence and Behavior
• Emulating Mission Environmental Complexity
• Assessing UAS Effects and Capabilities
• UAST Protocols and Design
• UAS Test Bed and Environment
• UAST Reference Data (Ground Truth)
• UAST Tools and Techniques
• Major technology challenges (in the ST solution
  development)
• Develop algorithms for predictive behavior by
  integrating genetic algorithm, probability
  theory, and autonomous behavior theory
• Construct models to analyze UAS decision
  operations in complex and uncertain environment
• Develop methodologies and metrics to evaluate
  distributive control and situational awareness
• Develop test protocols and algorithms to support
  on-board management system evaluation and UAS
  shutdown
• Develop realistic test bed components, and
  environments to support UAS evaluation approaches
  to unfolding missions via range assessments
• Compile truth data to support range safety, and
  protocols development

4
UAST Technology Overview (cont.)

• How does the focus area prioritize the technology
  challenges (state your rationale)?
• Mapping of TE needs to POR or NPOR as defined
  by
• UAST WG
• DoD Roadmaps
• SPO/ Project Managers
• By technology having broad applications across
  UAS Domains

5
Roadmap leverage of accepted reference models
for testing UAS

• NIST Performance Decomposition Model
• As opposed to componentized UAS view presented in
  roadmap
• Another alternative would be a test framework
  over ALFUS

6
Operational UAST Challenge
7
Autonomy-Base UAST Challenge
8
Cognitive Autonomous System Tester (CAST)
Project 1 of 13
9
High-Fidelity Communications, Modeling Analysis
(HFCMA)
Project 2 of 13
10
Remote Embedded System Test (REST)
Project Description REST is the integrated set of
technologies that replaces a wired
instrumentation system with a wireless, self
powered, self organizing, self healing network of
sensor nodes designed to be manufactured
(embedded and assembled) into the platform
structure and provide continuous test and
evaluation capability as well as integrate into
the platform Integrated System Health
Manager. REST is designed to provide UAST
capability for multiple platform types and DoD
services.

• Deliverables
• Prototype TRL 6 system components
• Flight and Ground Demonstration
• Final Report and White Papers

• Key Future Events Dates
• Start/Finish October 2007/December 2009
• Field Demonstration August 2009
• Final Report October 2009
• Conduct Field Test November, 2009
• Final Report December, 2009

• Transition Partners Dates
• Advanced Composite Cargo Aircraft (ACCA) Program,
  Phase III FY09 (REST TRL 6 Baseline Technology)
  Installed and evaluated in ACCA Fuselage
  Fatigue Test Article (Mar CY2010)
• Vulture (DARPA), In-Work

Project 3 of 13
11
Software Configurable Multi-Channel Transceiver
(SCMT)
Project 4 of 13
12
Micro-beacon Tracking of Autonomous Systems
(MTAS)
Project 5 of 13
13
Virtual Autonomous Teaming Tool(VATT)
Project 6 of 13
14
Standards, Software and Hardware for
Multi-Resolution Maps/Models (MRMM)
Project 7 of 13
15
An Integrated Agent-based Framework for
Simulated, Virtual and Live Testing of Teams of
Unmanned Vehicles (IABF)
Project 8 of 13
16
Reconfigurable Wireless Measurement System (RWMS)
Project 9 of 13
17
Flexible Command and Control Systems (FCCS)
Project 10 of 13
18
A Prescriptive and Adaptive Testing Framework
(PATFrame)
Project 11 of 13
19
Synthetic Collective Unmanned Underwater
Laboratory (SCUUL)
Project 12 of 13
20
MS for UAST
Project 13 of 13
21
UAST FY09 Achievements
22
UAST FY09 Achievements (cont.)
23
UAST FY 09 Lessons Learned

• UAST Working Group MUST shift focus from
  'marveling about UxS's' to 'TE'ing UxS's.' We
  must devise a UAST framework so that the ST that
  will enable various 'paths' through the framework
  can be highlighted and  justified then the ROI of
  ST projects can  be measured. 
• We can move from a focus on a) measuring the
  autonomy algorithm in the payload to b) measuring
  the autonomy of the Whole System and doing so
  sufficiently to Predict, with stated Confidence,
  the anticipated Suitability, Safety,
  Effectiveness and Survivability of the whole
  system.  "How can you 'prove' that your systems
  design will solve the customer's problem before
  you build and prove that design?" 
• The UAST process must be synchronized with PMO's
  view of the world and the TRMC process. Drop
  'ConOps' and talk in terms of Use Cases and Use
  Case Portfolios.  Then ST projects must state
  Objective in terms of Use Case hot spots and a)
  ST intent regarding ameliorating the hot spots
  and b) requirements allocated to other of TRMC's
  ST activities.  
• Use Cases must state the TE implications of the
  whole UxS. TE implications are objectives and
  concepts as stated at the Effects --gt
  Capabilities --gtAlgorithm/Timeline level (not
  System Shall statements) across development,
  prototype, IOC, production

24
Accelerating UAS Deploy through Test
25
Safety in the Battlespace
26
Three Phases of Startups

• Glimpse of Market
• Learning enough to match market with technologies
• Create value proposition for garnering ROI
• Variety
• Extent
• Ambiguity of Operational Necessity Fast
  Tracking Need for Testing for Safe, Suitable,
  Effective, and Survivable UAS

We are currently finishing Phase II 
27
Three Questions

• Are we progressing fast enough to help the
  Warfighters?
• Prototypes, Demos, Beta-Testing
• How can we accelerate ST activity for UAST?
• Use cases
• Connections to UAS programs workshops,
  outreach, conferences, web site, magazine, flyer
• Other? AUVSI, Robotic Rodeo, PERMIS, NIST, SAE,
  INCOSE, IEEE, NDIA, UARCs, Academia
• These rules for triage?
• Must address a TE need
• Must require ST
• Should have a big payoff
• Should have wide applicability
• Should have a transition partner

28
Summary

• UAST Working Group
• MUST devise a UAST ROI framework
• Use-case mapping of test needs for safe,
  suitable, survivable and effective UAS
• Technology forecasting
• CTEIP Mitigation
• Solicit needs from Warfighters, Testers,
  Developers, PMs
• Transition partner development
• How do we accelerate ST investments into TE
  capability?
• UAST overarching role
• Filling in the gaps for testing UAS that are
  being deployed using rapid acquisition practices
• Focus on autonomy TE
• Focus on safety of UAS
• Stakeholder collaboration (COI-UAST)
• Use Cases must state the TE implications of the
  whole UxS
• TE implications are objectives and concepts as
  stated at the
• Effects --gt Capabilities --gtAlgorithm/Timeline
  level (not System Shall statements) across
  development, prototype, IOC, production