UAS Control Segment (UCS) Technical Overview - Raytheon

UNCLASSIFIED
UAS Control Segment (UCS)
Technical Overview
Brian Schechter
Application Architecture Subcommittee Chair
UCS Working Group
UNCLASSIFIED
August 18, 2011

UNCLASSIFIED
OA UCS Acquisition Architecture Objectives Goals
Utilizing an Open, Standards-Based Service-Oriented
Architecture (SOA) approach , the UCS Architecture will
enhance:
• Operational and Acquisition Efficiencies
• System-to-System Interoperability
• Warfighter Capability
UCS Architecture does not currently cover:
• Low-level C2 interface between UAVs and ground
stations as existing standards such as STANAG 4586
provide standardization path-forward in this area
• Human-Machine Interfaces (HMIs)
UNCLASSIFIED 2

Feb 2009
ADM
Current Focus
UNCLASSIFIED
UCS Architecture Time Line
Time Line
St Structuring t i
2009
Dec 2009
Concept p
Version 0.5
Exploration Incl. AV-1
Architecture Definition and Demonstration
June 2010
Version 1.0
UNCLASSIFIED
Architecture Modeling
1QFY12
Version 2.1
Nov 2010
IWP Demo
Mar 2011
JSIL Demo
3
3

Abstraction
UNCLASSIFIED
UCS Architectural Views
Application Architecture Model
Services Services Services
Services
Service Domain 1 Service Domain 2 Service Domain 3 Service Domain 4
Technical Architecture
Operating Environment, Development Environment, Certification
Environment
IA and
Security
Management
Reference Architecture
Application 1 Application 2 Application 3 Application 4
Middleware Middleware Middleware Middleware Middleware
Guest OS Guest OS Guest OS Guest OS Guest OS
Embedded Hypervisor and Separation Kernel
Multi-Core Processor
Implementation Architectures
UNCLASSIFIED
Services Views
Standards / Certification
Views
System Views
Deployment Views
4

UNCLASSIFIED
Executive Application Board Provides Architecture
Mgmt & Guidance
UCS UCS Working Group Executive Mgmt
� Integrated Master Schedule
� Working Group Scorecards
� Working Group Plenary Meetings
� Interface with OSD UCS Steering Group
� Program of Work
� Terms of Reference
� Business Processes
AV-1
Configuration Control Board (CCB)
� Change Request (CR) Management
� Document Release Approval
Architecture Guidance Document
� Architecture Overview and Rationale
�� IImplementation l t ti Guidance G id and d Lessons L Learned L d
External Communication
� Briefing g Materials, Resources
� Public Website
� Presentations and Meetings
� Open Business Model (OBM)
UNCLASSIFIED 5

UNCLASSIFIED
Subcommittees
OSD UCS
Perform
Working
the Technical
Group
Work
Executive
Board
Architecture
Application
Platform
Certification
Development
Implementation Architecture
Architecture
Architecture
Tools
System
Architectures
Experiments
Conformance
Data Model
Mission Control
Mission
Planning
Dynamic
Airspace
External
Messaging &
Communication
Payload
P Product d PED
System Use
Cases
Computing
Infrastructure
Security Mgmt
& IA
Infrastructure
Services
MDA Process
IA
M3 Architecture
System Safety CM/DM
• Subcommittees form Task Groups
to perform well-defined portions of
their work
•Task Groups exist until these tasks
are completed l t d
UNCLASSIFIED 6

UNCLASSIFIED
Application Architecture Subcommittee
Subcommittee 2: Application Architecture
Define and develop p a common, , open p and scalable application pp architecture for command and
control of Unmanned Aircraft Systems System (UAS) Use Cases Group 2 through Group 5 at Platform Independent
Model (PIM) level using OMG Model Driven Architecture® (MDA)
System Use Cases
� Mission-Level Use Case and Scenario Textual Descriptions
� Mission-Level Use Case Diagrams (UML)
� System-Level Activity / Sequence Diagrams (UML)
Data Model
� Data Meta-Model (UML) ( )
� Logical Data Model (UML)
� Logical Data Model to Interface Data Model Projections (UML)
Domain Architecture
� UCS Architecture partitioned into Domains based on Subject Matter
� Domain / Sub-domain Textual Descriptions
� Domain-Level Use Cases and Activity / Sequence Diagrams (UML)
�� SService-Level i L l Textual T t l Descriptions
D i ti
� Service-Level Interfaces (SOAML)
7
UNCLASSIFIED 7

UNCLASSIFIED
Platform Architecture Subcommittee
Subcommittee 2: Application Architecture
Define and develop an implementation architecture for a flexible, technology-neutral
infrastructure for UCS that: Implements System Use and Cases distributes Application Service Interfaces and Data
Models; Provides a safe/secure computer architecture, reusable PSM mappings to supporting
middleware, OS, and hardware; Supports composability of mission services, reference
implementation, and testing.
Computing Infrastructure
� Core API Standards (CAPIS)
� DODAF viewpoint StdV-1 Standards Profile
Security Management & Information Assurance
� Security and Information Management Use Cases (UML)
� System Security and Information Assurance Management Plans (IAMP)
Infrastructure Services and Configuration
� Infrastructure Services PIM (UML)
� Definition of underlying y g Platform Technologies g
� System Configurability Requirements
MDA Process
� MDA Process Guidance
� PIM to PSM Transformation Examples
UNCLASSIFIED
8

UNCLASSIFIED
Certification Architecture Subcommittee
Subcommittee 2: Application Architecture
Identify the best technical approaches for Certification (Information Assurance, Assurance System Safety
and Airworthiness) for the UCS System Architecture Use Cases relative to DoD Certification guidance; assess the
UCS Architecture relative to these DoD Certification considerations; and propose changes to the
UCS Architecture where Certification deficiencies are identified.
Information Assurance (IA)
� Information Assurance Management Plan (IAMP)
�� Canonical Information Assurance Case (Goal Structured Notation)
System Safety and Airworthiness
� Data Meta-Model (UML)
� Logical Data Model (UML)
�� LLogical i l Data D t Model M d l to t Interface I t f Data D t Model M d l Projections P j ti (UML)
UNCLASSIFIED 9

UNCLASSIFIED
Architecture Implementation Subcommittee
Subcommittee 2: Application Architecture
Address aspects related to the implementation of the UCS architecture, including : Developing a
reference architecture or architectures; System Use Defining Cases experiments to aid in the validation of the UCS
architecture; Determining conformance of systems and services to the UCS architecture.
System Architectures
�� RReference f AArchitecture hit t
� Reference Implementations
� Dismounted User
� Transportable/Mobile System
� Fixed Facility
� Implementation Lessons Learned
Experiments
�� Experiments defined to validate Architecture Quality Attributes in AV-1 AV 1
Conformance
� Data Dictionary
� Open Architecture Assessment Tool
� Guidance on measuring Program of Record (PoR) compliance
�� GGuidance id on program ‘on-ramps’
‘ ’
� Component Specification Template
UNCLASSIFIED 10

UNCLASSIFIED
Development Tools Subcommittee
Subcommittee 2: Application Architecture
Provides guidance guidance, recommendations, recommendations and implementations of tools for use in the Model Driven
Engineering approach adopted System by the UCS-WG. Use Cases This includes tools for specifying, analyzing,
developing, and implementing the UCS 2.0 Architecture. The scope of this activity includes UML
development tools, code generation capabilities, model import/export, and configuration
management.
M3 Architecture
� Common Development Environment (tools) for UCS Architecture
� Based on OMG Model Driven Architecture (MDA) Approach
Configuration, Change and Data Management
� Architecture Governance Processes
11
UNCLASSIFIED 11

UNCLASSIFIED
Release Release 2.1 2.1 Scheduled for Dec 1QFY12 22, 2011
Volunteer Organizations Funded Organizations
Heterogeneous mix of 17 funded companies
H
A
S
UNCLASSIFIED 12