Dr. Francis' Brief

1
J-UCASCommon Systems TechnologiesIndustry
Day For Common Operating System (COS) Development
Mr. Marc J. Pitarys Deputy Director Joint
Unmanned Combat Air Systems June 24, 2005
PUBLIC RELEASE Distribution Statement A
Approved for Public Release Case 5277
Distribution Unlimited
2
Topics

• J-UCAS Overview
• The Common Operating System (COS)
• The COS Consortium
• Technology Contributor Opportunities

PUBLIC RELEASE Distribution Statement A Approved
for Public Release case 5277 Distribution
Unlimited
3
Joint Unmanned Combat Air Systems --Unique Joint
Program

• DARPA-Air Force-Navy Development Began 1 Oct
  2003
• Outgrowth of Earlier DARPA Programs
• Program Objectives
• Demonstrate Concept Feasibility Flexibility
• Conduct Operational Assessment (OA) of J-UCAS
  Capabilities
• Maintain Competitive Environment throughout the
  Program
• Facilitate Early Fielding Decision End of the
  Decade
• Atypical Program Architecture
• Spiral Development Approach with Aggressive
  Timelines
• Cutting Edge Technology ATDs Operational
  Assessment
• Contractors
• Boeing Team (X-45 air vehicles)
• Northrop Grumman Team (X-47 air vehicles)
• Common Operating System Consortium (Boeing, NG,
  Johns Hopkins APL)
• Large Program - 4B over the FYDP

PUBLIC RELEASE Distribution Statement A
Approved for Public Release Case 4655
Distribution Unlimited
4
Joint Unmanned Combat Air Systems -- The Vision
Electronic Attack
Surveillance
Strike
SEAD Destructive Non-Destructive
PUBLIC RELEASE Distribution Statement A Approved
for Public Release case 4178 Distribution
Unlimited
5
J-UCAS System ElementsA Way Forward
PUBLIC RELEASE Distribution Statement A
Approved for Public Release Case 2129
Distribution Unlimited
6
Video Animation (Excerpt) -- J-UCAS in Action

• Focus Autonomous Functionality
• SEAD Mission Environment
• Multi-Platform Collaborative Operations
• Vignettes
• Target Detect, Geo-locate, ID and Attack
• Collaboration for Survivability
• Damage Tolerance
• Autonomous Aerial Refueling
• Preemptive Reactive Operations

Video
PUBLIC RELEASE Distribution Statement A
Approved for Public Release 4785 Distribution
Unlimited
7
Joint Unmanned Combat Air Systems -- Raising
the Bar
Operator Vehicle Ratio
Global Hawk1 1
PredatorMany 1
J-UCAS1 Many
J-UCASDenied Airspace Survivable Design Land
Sea Based Mainstream Air Ops
Operational Environment
Predator Global Hawk Secured Airspace Land
Based Dissimilar Air Ops
Global HawkSingle Ship Days
Mission Planning Time
J-UCASMulti Ship Hours
J-UCAS Shared Channels Quality of Service Net
Ready
Global HawkDedicated Channelper Vehicle Large
Bandwidth Blocks
Communication Management
J-UCASMulti Ship, Cooperative Targeting
Attack Interoperable
Fielded SystemsSingle Ship Only Stove-Piped
Systems No Cooperation
Cooperative Operations
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 4178 Distribution
Unlimited
8
Topics

• J-UCAS Overview
• The Common Operating System (COS)
• The COS Consortium
• Technology Contributor Opportunities

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
9
Common Operating System
X-45
X-47
Other Air Vehicles

• Common Operating System
• The Architecture, Algorithms Software,
• that
• Control / Manage System Resources
• Facilitate Information Exchange
• Provide Battlespace Awareness
• Enable Inter-platform Functionality
• Enable Autonomous Operations
• Maintain Quality Of Service

Remote Control Element
10
J-UCAS Common Operating System
11
Common Operating System (COS) --Why Develop It?

• Provide Needed Mission Functionality
• Manages interactions between system components
• Enable collaborative operations
• Allows Autonomous Operations
• Facilitate agile bandwidth management
• Reduce Development Costs
• Build it one time
• Dont throw it away- Use on Follow-on Programs
• Reduce Technology Barriers to Entry
• Attract best-of-breed algorithms
  functionality
• Enable competition at the function level
• Assure Intra- and Inter-operability
• Primes collaborate to develop
• Same software used on all platforms
• Decouple System IT from Platforms
• Allow natural development timelines
• Reduce interdependencies

12
Common Operating System -- Functionality Lines
of Demarcation
CommonOperating System
Support
Sensors

• Vehicle SpecificHealth Management
• Ground Test
• Built in Test
• Portable Field Testers

• Resource Management
• Sensors
• Payloads
• Attack
• Power
• Contingency Management
• System
• Mission
• Network Management
• Quality of Service
• Bandwidth Allocation
• Link Control
• Critical GIG Interfaces
• MILSTAR
• Link 16
• SIPRNET
• TCDL
• JWICS

• Information Management
• Publish/Subscribe
• Fusion
• Battle Management
• Common Relevant Operational Picture
• Integrated Fire Control
• Human System Integration
• Display Management
• Decision Aids
• Situation Awareness
• Planning
• Mission
• Collection
• Dynamic Re-planning

• Signal Processing
• Mission DataProcessing
• Sensor Modes

Weapons
VMS

• Stores Management
• Crypto Key Loading

• Guidance
• Flight Control
• Vehicle Contingency Management
• Fuel Control
• Engine Control
• Diagnostics
• Redundancy Management
• Subsystem Control
• GPS/INS Navigation
• IFF Transponder
• Brakes
• Environmental Control System

Platform Specific Software

• Landing Gear
• Actuators
• Power Distribution Units
• Weapons Bay Doors
• (Taxi, take-off, and landing capability)

• Real Time Operating System (RTOS)
• Operating System Isolation Layer
• Subsystem interfaces
• Taxi and take-off operator displays

13
Common Operating System --Architecture
Architecture Characteristics

• Open
• Specifications available to multiple contractors
• Non-Proprietary
• Source Code Available
• Can be used, copied, modified, and redistributed
  by the Government without charge
• Uses Industry Standards
• Technical Standards agreed to by Industry and
  Professional Organizations

APPLICATION SERVICES
MIDDLEWARE
Government Rights to Application Services
(Prioritized)

• Government Purpose Rights
• License software from various developers for the
  life of the COS
• Limited Rights where there is no alternative (in
  rare instances)

14
Common Operating System Build Schedule (As of
31 May 05)

• Functionality from Build 0
• Critical GIG interfaces
• BLOS communications
• LOS communications
• JMPS Pre-mission planning support
• Primary Route and Contingency Management
• Support for Comm, Single Ship ESM, and Weapons
• HSI for Single Ship Demos
• Sensor Management
• SAR- Limited to Image Collection and BIT
• ESM- Single Ship (ALR-69)
• Weapon Management
• Information Management Fusion (ESM Track Data)

• Middleware Services
• Publish/Subscribe
• Discovery/Mediation
• Communication Services
• Data Repository
• OS Abstraction Layer
• Demonstration Application Services
• Weapon-Target Assignment
• Sensor Manager
• Human System Interface (HSI) for Demo missions
• Distributed Interactive Simulation (DIS)
  interface

Build 0 Basic Services Dec 05
Build 1 Single Ship Jun 07
FYO5
FY10
FY09
FY06
FY08
FY07
Dec 08 Build 2 Multi-Ship

• Battle Management Interface to ADSI
• Collects Track Data for operators
• Network Management
• Quality of Service
• Attack Management
• Contingency Management
• System
• Mission
• Information Management Fusion (Off-board/On-board
  )

• Functionality from Build 1
• Interfaces to Mission Planning and Intel Cell
• SIPRNet
• JWICS
• In-flight Mission Planning
• Primary Route Planning and Contingency Management
• Auto-router
• HSI for Multi-Ship Operations
• Sensor Management
• ESM- Multi-Ship
• SAR- Automatic Target Cueing, Image Registration,
  and Fusion

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
15
COS Functionality Description- Build 0
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
16
COS Functionality Description- Build 1
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
17
COS Functionality Description- Build 2
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
18
COS Functionality Description- Build 2 (cont.)
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
19
COS Supports J-UCAS Advanced Operations
MULTI-SHIP OPERATIONS
NETWORK-CENTRIC OPERATIONS
Shared Space
EO
Discovery Metadata Catalog
Structural Metadata
Data Contents
Common Operating System
ESM
SAR
AUTONOMOUS OPERATIONS
20
Topics

• J-UCAS Overview
• The Common Operating System (COS)
• The COS Consortium
• Technology Contributor Opportunities

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
21
Development Strategy RationaleWhy a Consortium?

• Consortium is a single entity composed of
  numerous organizations to focus resources on a
  common effort
• Common functionality is needed by both primes
• No one company has all the needed resources nor
  capabilities to complete the Common Operating
  System development
• Opportunity to incorporate the best of breed
  solution
• Lowers barriers to entry for new technology
• Avoids a proprietary, closed OS implementation

• Provides a formal mechanism for cooperation
  amongst developing organizations
• Rules Articles of Collaboration
• Established Structure Integrator/Broker and
  Primes
• Process for dispute resolution
• Allows the Government a mechanism to control
  ownership of the Common Operating System

22
Integrator/Broker Description

• Key 3rd Party Not an LSI
• Intellectual Property Opportunity None
  Limited?
• Six objectives of Integrator Broker (described in
  solicitation)
• Act as an impartial broker within the consortium.
• Facilitate, coordinate, and (if necessary)
  complete the development of the J-UCAS enterprise
  architecture.
• Facilitate, coordinate, and (if necessary)
  complete the development and integration of the
  COS.
• Develop and maintain an executable J-UCAS
  architectural model.
• Provide available infrastructure to support
  technology identification and evaluation (e.g.
  simulation, labs, etc.).
• Maintain configuration control of Interface
  Control Documents (ICDs), executable models, and
  COS software releases.

23
COS Consortium --Roles Responsibilities

• JHU/APL
• Function as the Consortiums recording secretary
  and configuration manager for the COS development
  effort
• Provide for an electronic, WEB-Based
  collaborative environment
• Administer and coordinate technology
  competitions
• Administer certain Technology Contributor
  subcontracts and
• Remain free from conflicts of interest to fulfill
  its role as DARPAs trusted agent.
• Boeing and NGSC
• Participate as Primary Developers and Integrators
  of the COS
• Technology Contributors
• Contribute Technology to the Consortium as
  authorized by the CMC
• Not party to the Articles of Collaboration

24
J-UCAS Business Model Mechanics
3.
2.

1.
Consortium
COS

• Government funds COS development through the
  individual consortium members agreements
• Consortium delivers COS software to the
  government- Integrator/Broker releases COS to the
  government
• Government furnishes COS to the primes for
  integration into their systems

25
Topics

• J-UCAS Overview
• The Common Operating System (COS)
• The COS Consortium
• Technology Contributor Opportunities

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
26
Potential Organizations to work as a Technology
Contributor

• Federally Funded RD Centers
• Military and Government Laboratories
• Universities
• DOD Contractors
• Others?
• Teams?

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
27
COS Applications Infrastructure
Component Development
HSI IPT
Applications
Infrastructure IPT
COI Data Models Interfaces IPT
Contingency Management IPT
Information Assurance Sub-IPT
Route Management IPT
Edge Data Services Sub-IPT
Enterprise Services Sub-IPT
Assessment Management IPT
Sensor Management IPT
Platform Portability Sub-IPT
Mission Management IPT
Enterprise Svs Mgmt Sub-IPT
Track Management IPT
Weapons Management IPT
Exploitation IPT
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
28
COS HSI (Detail)
Human Systems Interface IPT
HSI Integration Framework
Operator Interfaces Sub-IPT
TC Candidate Future
TC Candidate
J-UCAS has an Immediate Need for HSI Technology
Contributor Support
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
29
Governments Intent for COS HSI

• Consistent look and feel in terms of appearance
  and behavior
• Generic and Community of Interest (COI)
  functionality
• Utilization of services to provide necessary
  functionality
• Legacy tolerant approach
• Flexibility and scalability ability to modify
  and evolve as new techniques and technologies
  mature
• User roles and profiles

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
30
Situation Assessment

• Three development efforts taking place
• X-45 control element, X-47 control element, and
  COS
• Two vehicle specific control elements (X-45 and
  X-47) are being developed
• Each prime developing a platform specific
  architectures, integrating vehicle and control
  element hardware, software, and operator
  interfaces with the COS
• For the Operational Assessment, the Mission
  Control Element will need
• Platform-specific software for taxi, takeoff,
  launch, and recovery health and status
  monitoring vehicle contingency management
• COS software for mission management
• COS provides mission management functionality
  common to both vehicles and integrates selected
  vehicle-specific functionality

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
31
COS Heterogeneous HSI Integration
COS-GeneratedControl
Custom-built COS User Interface (UI) Container
Web-based UI
Embedded UIElement
PUBLIC RELEASE Distribution Statement A
Approved for Public Release Case 5277
Distribution Unlimited
32
User Interface Migration Path
Future Vision Integrated User Interface
User Integrated Interface
COS Functions
X-45-Functions
X-47-Functions
Operational Assessment Common Functions
User Assistant (user profiles based on role or
mission)
User
User
Now
X-45-Functions
X-47-Functions
COS Functions
COS Functions
User
User
X-47 Control Station
X-45 Control Station
X-45-Functions
X-47-Functions
X-47 Control Station
X-45 Control Station
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
33
COS Applications (Detail)
Applications
Mission Management IPT
Assessment Management IPT
Contingency Management IPT
Route Management IPT
Sensor Management IPT
Track Management IPT
Exploitation IPT
Weapons Management IPT
System Failures
Auto-Routers
Threat Assessments
Electronic Support Measures
Task Allocation
Report Collection
Launch Acceptability Region
Automatic Target Cueing
Mission Failures
Route Survivability
Target Assessments
Synthetic Aperture Radar
Sensor Pairings
Track Fusion
Weapons Interface
Tracking
Auto-router Selection
Mission Assessments
Electro-Optical Infrared
Weapon- Target Pairings
Mensuration
Multi-Ship ESM
Pre-mission Route Planning (JMPS Interface)
Vehicle Assessments
Pairing Algorithm Selection
Raw Data Processing
TC Candidate Future
TC Candidate
Prediction Models
Task Generation
Exploitation Algorithm Selection
Build 0.0 Baseline
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
34
COS Infrastructure (Detail)
Infrastructure IPT
Edge Data Services Sub-IPT
Information Assurance Sub-IPT
Enterprise Services Mgmt Sub-IPT
Enterprise Services Sub-IPT
Platform Portability Sub-IPT
Guards
Connection Services
Discovery
OS Isolation Layer
Deployment Setup/Configuration
Authentication
Data Store Services
Messaging
Application Isolation Layer
Network Management
Separation Kernel
Mediation
I/O Wrappers
End-to-End Quality of Service
TC Candidate Future
Web Services
Platform Isolation
Wrapper Toolbox/Script Engine
TC Candidate
Build 0.0 Baseline
Collaboration
Comm. Services
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
35
Notional Technology ContributorSelection Process
Government
Industry Day
Model AssistedMetric Based Analysis
Component IPT
Enterprise Architecture Model
RFP
Evaluation Team
Technical Assessment
Procurement Review Board
Cost-Benefit Analysis
(DARPA Oversight)
Technology Contributors
Contract
Proposal
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
36
TC Selection Process Features

• APL will coordinate process
• The Evaluation Team and the Procurement Review
  Board will include members from Boeing, NGC and
  APL
• Awards will be based on Selection Criteria to
  achieve best value for COS
• Selected TCs will be contributors, not consortium
  members
• Contracting through APL
• Technical I/F through IPTs

PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
37
DRAFT COS Consortium Organization

Executive Steering Council DARPA-Boeing-NGSC-APL
Consortium Management Committee Boeing/NGSC/APL
DARPA
Procurement Review Board
Configuration Control Board
Engineering Review Board
Chief Engineers Boeing/NGSC/APL
Business Ops Boeing/NGSC/APL
Applications Development
Test Evaluation
Modeling Simulation
SEIT/Horizontal Integration
Infrastructure Development
HSI Development
PUBLIC RELEASE Distribution Statement A Approved
for Public Release Case 5277 Distribution
Unlimited
38
Questions?
PUBLIC RELEASE Distribution Statement A
Approved for Public Release 2129 Distribution
Unlimited