UNCLASSIFIED

UAS Control Segment (UCS)

Technical Overview

Brian SchechterApplication Architecture Subcommittee ChairApplication Architecture Subcommittee Chair

UCS Working Group

August 18, 2011

UNCLASSIFIED

OA Acquisition ObjectivesUNCLASSIFIED

UCS Architecture 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 4586stations as existing standards such as STANAG 4586 provide standardization path-forward in this area

• Human-Machine Interfaces (HMIs)

UNCLASSIFIED 2

Time LineSt t i

UCS Architecture Time LineUNCLASSIFIED

Structuring

Feb 2009ADM

2009Concept

Dec 2009Version 0.5ADM p

Exploration Incl. AV-1

Architecture Definition and Demonstration

June 2010Version 1.0

Nov 2010IWP DemoMar 2011

Architecture Definition and Demonstration

JSIL Demo

Architecture Modeling

1QFY12Version 2.1

Current Focus

3

UNCLASSIFIED3

Application Architecture Model

Architectural ViewsUNCLASSIFIED

UCS Architectural ViewsApplication Architecture Model

Services Services ServicesServices Views

Services

Technical ArchitectureOperating Environment, Development Environment, Certification

Environment

Standards / Certification Views

Service Domain 1 Service Domain 2 Service Domain 3 Service Domain 4

Reference Architecture

IA and Security

ManagementApplication 1 Application 2 Application 3 Application 4tr

actio

n

Guest OS Guest OS Guest OS Guest OS Guest OS

Middleware Middleware Middleware Middleware Middleware

Management

Embedded Hypervisor and Separation Kernel

System Views Abs

Implementation Architectures

Multi-Core Processor

Deployment Views

UNCLASSIFIED 4

UCS Working Group Executive Mgmt

Application ArchitectureUNCLASSIFIED

Executive Board Provides Mgmt & GuidanceUCS Working Group Executive Mgmt

Integrated Master Schedule Working Group Scorecards Working Group Plenary Meetings Interface with OSD UCS Steering Group

AV-1 Program of Work Terms of Reference Business Processes

Configuration Control Board (CCB)

Change Request (CR) Management Document Release Approval

Architecture Guidance Document Architecture Overview and Rationale I l t ti G id d L L d

External Communication

Implementation Guidance and Lessons Learned

Briefing Materials, Resourcesg Public Website Presentations and Meetings Open Business Model (OBM)

UNCLASSIFIED 5

Executive

OSD UCS Working GroupUNCLASSIFIED

Subcommittees Perform the Technical Work

Architecture Application Platform Certification Development

Executive Board

Architecture Implementation

System Architectures

System Architectures

Application Architecture

Data ModelData Model

Platform Architecture

Computing InfrastructureComputing

Infrastructure

Certification Architecture

IAIA

Development Tools

M3 ArchitectureM3 Architecture

ExperimentsExperiments Mission ControlMission Control

MissionMission

Security Mgmt & IA

Security Mgmt & IA

InfrastructureInfrastructure

System SafetySystem Safety CM/DMCM/DM

ConformanceConformanceMission PlanningMission Planning

Dynamic AirspaceDynamic Airspace

Infrastructure Services

Infrastructure Services

MDA ProcessMDA Process

External Messaging &

Communication

External Messaging &

Communication

Payload P d PED

Payload P d PED

• Subcommittees form Task Groups to perform well-defined portions of their work•Task Groups exist until these tasks

l t dProduct PEDProduct PED

System Use Cases

System Use Cases

are completed

UNCLASSIFIED 6

Subcommittee 2: Application ArchitectureDefine and develop a common, open and scalable application architecture for command and

Application Architecture SubcommitteeUNCLASSIFIED

System Use Casesp , p pp

control of Unmanned Aircraft Systems (UAS) 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) S i L l T t l D i ti Service-Level Textual Descriptions Service-Level Interfaces (SOAML)

7

UNCLASSIFIED 7

Subcommittee 2: Application ArchitectureDefine and develop an implementation architecture for a flexible, technology-neutral

Platform Architecture SubcommitteeUNCLASSIFIED

System Use Casesinfrastructure for UCS that: Implements and 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 Platform Technologies

MDA Process MDA Process Guidance

y g g System Configurability Requirements

UNCLASSIFIED

PIM to PSM Transformation Examples

8

Subcommittee 2: Application ArchitectureIdentify the best technical approaches for Certification (Information Assurance System Safety

Certification Architecture SubcommitteeUNCLASSIFIED

System Use CasesIdentify the best technical approaches for Certification (Information Assurance, System Safety and Airworthiness) for the UCS Architecture 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 Management Plan (IAMP) Canonical Information Assurance Case (Goal Structured Notation)

Information Assurance (IA)

Canonical Information Assurance Case (Goal Structured Notation)

System Safety and Airworthiness

Data Meta-Model (UML) Logical Data Model (UML) L i l D t M d l t I t f D t M d l P j ti (UML) Logical Data Model to Interface Data Model Projections (UML)

UNCLASSIFIED 9

Subcommittee 2: Application ArchitectureAddress aspects related to the implementation of the UCS architecture, including : Developing a

Architecture Implementation SubcommitteeUNCLASSIFIED

System Use Casesreference architecture or architectures; Defining experiments to aid in the validation of the UCS architecture; Determining conformance of systems and services to the UCS architecture.

R f A hit tSystem Architectures

Reference Architecture Reference Implementations

Dismounted User Transportable/Mobile System Fixed Facility

Experiments

Experiments defined to validate Architecture Quality Attributes in AV 1

Implementation Lessons Learned

Experiments defined to validate Architecture Quality Attributes in AV-1

Conformance Data Dictionary Open Architecture Assessment Tool Guidance on measuring Program of Record (PoR) compliance G id ‘ ’ Guidance on program ‘on-ramps’ Component Specification Template

UNCLASSIFIED 10

Subcommittee 2: Application ArchitectureProvides guidance recommendations and implementations of tools for use in the Model Driven

Development Tools SubcommitteeUNCLASSIFIED

System Use CasesProvides guidance, recommendations, and implementations of tools for use in the Model Driven Engineering approach adopted by the UCS-WG. 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.

Common Development Environment (tools) for UCS Architecture

M3 Architecture

Based on OMG Model Driven Architecture (MDA) Approach

Configuration, Change and Data Management

Architecture Governance Processes

11

UNCLASSIFIED 11

Release 2.1 Scheduled for Dec 22, 2011UNCLASSIFIED

Release 2.1 Scheduled for 1QFY12

H

Volunteer Organizations Funded Organizations

AS

Heterogeneous mix of 17 funded companies

UNCLASSIFIED 12