J-UCAS Common Systems & Technologies Industry Day For Common Operating System (COS) Development...

J-UCASJ-UCASCommon Systems & TechnologiesCommon Systems & Technologies

Industry DayIndustry DayFor For

Common Operating System (COS) Common Operating System (COS) DevelopmentDevelopment

J-UCASJ-UCASCommon Systems & TechnologiesCommon Systems & Technologies

Industry DayIndustry DayFor For

Common Operating System (COS) Common Operating System (COS) DevelopmentDevelopment

Mr. Marc J. PitarysMr. Marc J. PitarysDeputy DirectorDeputy Director

Joint Unmanned Combat Air SystemsJoint Unmanned Combat Air SystemsJune 24, 2005June 24, 2005PUBLIC RELEASE

Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

TopicsTopics

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

PUBLIC RELEASEDistribution Statement A: Approved for Public Release case #5277– Distribution Unlimited

Joint Unmanned Combat Air Systems --Joint Unmanned Combat Air Systems --

Unique Joint ProgramUnique Joint Program

• DARPA-Air Force-Navy Development – Began 1 Oct 2003DARPA-Air Force-Navy Development – Began 1 Oct 2003– Outgrowth of Earlier DARPA ProgramsOutgrowth of Earlier DARPA Programs

• Program ObjectivesProgram Objectives– Demonstrate Concept Feasibility & FlexibilityDemonstrate Concept Feasibility & Flexibility– Conduct Operational Assessment (OA) of J-UCAS CapabilitiesConduct Operational Assessment (OA) of J-UCAS Capabilities– Maintain Competitive Environment throughout the ProgramMaintain Competitive Environment throughout the Program– Facilitate Early Fielding Decision … End of the DecadeFacilitate Early Fielding Decision … End of the Decade

• Atypical Program ArchitectureAtypical Program Architecture– Spiral Development Approach with Aggressive TimelinesSpiral Development Approach with Aggressive Timelines

• Cutting Edge Technology … ATDs … Operational AssessmentCutting Edge Technology … ATDs … Operational Assessment

– ContractorsContractors• Boeing Team (X-45 air vehicles)Boeing Team (X-45 air vehicles)• Northrop Grumman Team (X-47 air vehicles)Northrop Grumman Team (X-47 air vehicles)• Common Operating SystemCommon Operating System Consortium (Boeing, NG, Johns Hopkins APL) Consortium (Boeing, NG, Johns Hopkins APL)

• Large Program - $4B+ over the FYDPLarge Program - $4B+ over the FYDPPUBLIC RELEASE

Distribution Statement A: Approved for Public Release Case # 4655– Distribution Unlimited

Joint Unmanned Combat Air Systems -- Joint Unmanned Combat Air Systems --

The VisionThe Vision

StrikeStrikeStrikeStrike

SurveillanceSurveillanceSurveillanceSurveillance

Electronic AttackElectronic AttackElectronic AttackElectronic Attack

SEAD – DestructiveSEAD – Destructive & Non-Destructive& Non-DestructiveSEAD – DestructiveSEAD – Destructive & Non-Destructive& Non-Destructive

• Dangerous Missions – Denied AirspaceDangerous Missions – Denied Airspace• Survivable Air VehiclesSurvivable Air Vehicles• Advanced Sensors & WeaponsAdvanced Sensors & Weapons• Network-Centric ArchitectureNetwork-Centric Architecture• Distributed Command & ControlDistributed Command & Control• Intra-operable PlatformsIntra-operable Platforms• Collaborative OperationsCollaborative Operations• Land or Sea Based SystemLand or Sea Based System• Global OperationsGlobal OperationsPUBLIC RELEASE

Distribution Statement A: Approved for Public Release case #4178– Distribution Unlimited

J-UCAS System ElementsJ-UCAS System Elements

A Way Forward …A Way Forward …

ControlControlStationsStations

Payload Systems Payload Systems

Direct SupportDirect Support

Air VehiclesAir Vehicles

CoCommonmmonOperating SystemOperating System

Architecture, algorithms & software:Architecture, algorithms & software:• Control / manage system resourcesControl / manage system resources• Facilitate information exchangeFacilitate information exchange• Provide battlespace awarenessProvide battlespace awareness• Enable inter-platform functionalityEnable inter-platform functionality• Enable autonomous operationsEnable autonomous operations• Maintain quality of serviceMaintain quality of service

OperationalOperationalInfrastructureInfrastructure

CommunicationsCommunications

PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #2129– Distribution Unlimited

Video Animation (Excerpt) --Video Animation (Excerpt) --

J-UCAS in ActionJ-UCAS in Action

Focus – Autonomous FunctionalityFocus – Autonomous Functionality

• SEAD Mission EnvironmentSEAD Mission Environment

• Multi-Platform Collaborative OperationsMulti-Platform Collaborative Operations

• VignettesVignettes– Target Detect, Geo-locate, ID and AttackTarget Detect, Geo-locate, ID and Attack

– Collaboration for SurvivabilityCollaboration for Survivability

– Damage ToleranceDamage Tolerance

– Autonomous Aerial RefuelingAutonomous Aerial Refueling

– Preemptive & Reactive OperationsPreemptive & Reactive Operations

PUBLIC RELEASE Distribution Statement A: Approved for Public Release #4785 – Distribution Unlimited

Cooperative OperationsCooperative Operations

Mission Planning TimeMission Planning Time

Joint Unmanned Combat Air Systems -- Joint Unmanned Combat Air Systems --

… ‘Raising the Bar’… ‘Raising the Bar’

Operator : Vehicle RatioOperator : Vehicle RatioGlobal HawkGlobal Hawk

1 : 11 : 1PredatorPredatorMany : 1Many : 1

J-UCASJ-UCAS1 : Many1 : Many

…

J-UCASJ-UCASMulti Ship, CooperativeMulti Ship, Cooperative

Targeting & AttackTargeting & AttackInteroperableInteroperable

J-UCASJ-UCASMulti ShipMulti Ship

HoursHours

Global HawkGlobal HawkSingle ShipSingle Ship

DaysDays

Communication ManagementCommunication Management

Fielded SystemsFielded SystemsSingle Ship OnlySingle Ship Only

Stove-Piped SystemsStove-Piped SystemsNo CooperationNo Cooperation

Global HawkGlobal HawkDedicated ChannelDedicated Channel

per Vehicleper VehicleLarge Bandwidth BlocksLarge Bandwidth Blocks

J-UCASJ-UCASShared ChannelsShared ChannelsQuality of ServiceQuality of Service

Net ReadyNet Ready

Operational EnvironmentOperational Environment

J-UCASJ-UCASDenied AirspaceDenied Airspace

Survivable DesignSurvivable DesignLand & Sea BasedLand & Sea Based

Mainstream Air OpsMainstream Air Ops

Predator & Global HawkPredator & Global HawkSecured AirspaceSecured Airspace

Land BasedLand BasedDissimilar Air OpsDissimilar Air Ops

PUBLIC RELEASEDistribution Statement A: Approved for Public Release Case #4178– Distribution Unlimited

TopicsTopics



Common Operating SystemCommon Operating System

CoCommon Operating Systemmmon Operating System The Architecture, Algorithms & Software,The Architecture, Algorithms & Software, thatthat::• Control / Manage System ResourcesControl / Manage System Resources• Facilitate Information ExchangeFacilitate Information Exchange• Provide Battlespace AwarenessProvide Battlespace Awareness• Enable Inter-platform FunctionalityEnable Inter-platform Functionality• Enable Autonomous OperationsEnable Autonomous Operations• Maintain Quality Of ServiceMaintain Quality Of Service

X-45X-45

X-47X-47Other Other Air VehiclesAir Vehicles

RemoteRemote Control ElementControl Element

PUBLIC RELEASE

Approved for Public Release Case #2129 - Distribution Unlimited

J-UCAS “Common Operating System”J-UCAS “Common Operating System”

J-UCASJ-UCASCommon Operating SystemCommon Operating System

CommercialCommercialOperating SystemOperating System

Manages Resources:Manages Resources:–SensorsSensors–WeaponsWeapons–Communication Links / BandwidthCommunication Links / Bandwidth–Air VehiclesAir Vehicles

Manages Resources:Manages Resources:– MemoryMemory– CPU timeCPU time– Disk SpaceDisk Space– Peripheral Devices Peripheral Devices

(keyboard, mouse, Etc.)(keyboard, mouse, Etc.)

Provides Security:Provides Security:–Controls Access to the SystemControls Access to the System

Provides Security:Provides Security:–Controls Access to the SystemControls Access to the System

Facilitates Information Exchange:Facilitates Information Exchange:– Global Information Grid (GIG)Global Information Grid (GIG)

Facilitates Information Exchange:Facilitates Information Exchange:– Data BusData Bus

Human System Integration (HSI):Human System Integration (HSI):– Decision AidsDecision Aids– Common relevant operational pictureCommon relevant operational picture

Graphical User Interface (GUI): Graphical User Interface (GUI): – Windows System organizes images and Windows System organizes images and

controls on screencontrols on screen

Provides System Services:Provides System Services:– Contingency ManagementContingency Management– FusionFusion– Publish/SubscribePublish/Subscribe– Discovery/MediationDiscovery/Mediation– Communication ServicesCommunication Services– Data RepositoryData Repository

Provides Services:Provides Services:– Schedules, loads, initiates, and supervises the Schedules, loads, initiates, and supervises the

execution of programsexecution of programs– Allocates storageAllocates storage– initiates and controls input/output operationsinitiates and controls input/output operations– Handles errors Handles errors

Resides:Resides:– On top of Embedded OSOn top of Embedded OS

Resides:Resides:– On top of BIOSOn top of BIOS

PUBLIC RELEASE


Common Operating System (COS) --Common Operating System (COS) --

Why Develop It?Why Develop It?Common Operating System (COS) --Common Operating System (COS) --

Why Develop It?Why Develop It?• Provide Needed Mission FunctionalityProvide Needed Mission Functionality

– Manages interactions between system Manages interactions between system componentscomponents

• Enable collaborative operationsEnable collaborative operations– Allows Autonomous OperationsAllows Autonomous Operations– Facilitate agile bandwidth management Facilitate agile bandwidth management

• Reduce Development CostsReduce Development Costs– Build it one timeBuild it one time– Don’t “throw it away”- Use on Follow-on Don’t “throw it away”- Use on Follow-on

ProgramsPrograms• Reduce Technology Barriers to EntryReduce Technology Barriers to Entry

– Attract ‘best-of-breed’ algorithms & Attract ‘best-of-breed’ algorithms & functionalityfunctionality

– Enable competition at the function levelEnable competition at the function level• Assure Intra- and Inter-operabilityAssure Intra- and Inter-operability

– Primes collaborate to developPrimes collaborate to develop– Same software used on all platformsSame software used on all platforms

• Decouple System IT from PlatformsDecouple System IT from Platforms– Allow natural development timelinesAllow natural development timelines– Reduce interdependenciesReduce interdependencies

CommonCommonOperatingOperating

SystemSystem(COS)(COS)

PUBLIC RELEASE


Common Operating System --Common Operating System -- Functionality Lines of DemarcationFunctionality Lines of Demarcation

• Information ManagementInformation Management• Publish/SubscribePublish/Subscribe• FusionFusion

• Battle ManagementBattle Management• Common Relevant Common Relevant

Operational PictureOperational Picture• Integrated Fire ControlIntegrated Fire Control

• Human System IntegrationHuman System Integration• Display ManagementDisplay Management• Decision AidsDecision Aids• Situation AwarenessSituation Awareness

• PlanningPlanning• MissionMission• CollectionCollection• Dynamic Re-planningDynamic Re-planning

• Resource ManagementResource Management•SensorsSensors•PayloadsPayloads•AttackAttack•PowerPower

• Contingency ManagementContingency Management•SystemSystem•MissionMission

• Network ManagementNetwork Management•Quality of ServiceQuality of Service•Bandwidth AllocationBandwidth Allocation•Link ControlLink Control

• Critical GIG InterfacesCritical GIG Interfaces•MILSTARMILSTAR•Link 16Link 16•SIPRNETSIPRNET•TCDLTCDL•JWICSJWICS

CommonCommonOperating SystemOperating System

VMSVMS

SensorsSensorsSupportSupport

• GuidanceGuidance• Flight ControlFlight Control• Vehicle Contingency Vehicle Contingency

ManagementManagement• Fuel ControlFuel Control• Engine ControlEngine Control• DiagnosticsDiagnostics• Redundancy ManagementRedundancy Management• Subsystem ControlSubsystem Control• GPS/INS NavigationGPS/INS Navigation• IFF TransponderIFF Transponder• BrakesBrakes• Environmental Control SystemEnvironmental Control System

• Landing GearLanding Gear• ActuatorsActuators• Power Distribution UnitsPower Distribution Units• Weapons Bay DoorsWeapons Bay Doors• (Taxi, take-off, and landing (Taxi, take-off, and landing

capability)capability)

• Signal ProcessingSignal Processing• Mission DataMission Data

ProcessingProcessing• Sensor ModesSensor Modes

• Vehicle SpecificVehicle SpecificHealth Management Health Management

• Ground TestGround Test• Built in TestBuilt in Test• Portable Field Portable Field

TestersTesters

WeaponsWeapons

• Stores ManagementStores Management• Crypto Key LoadingCrypto Key Loading

Platform SpecificPlatform SpecificSoftwareSoftware

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

PUBLIC RELEASE


Common Operating System --Common Operating System --

ArchitectureArchitecture

MIDDLEWARE SERVICES

COS Services API

BattleManagement

PlanningHuman System

Interface

Sys Mgmt-Multi-Ship Ops

ContingencyManagement

Resource & Sensor Mgmt

NetworkManagement

InformationMgmt

Critical GIGInterfaces

Data StoresServices

SystemServices

InformationAssurance

• OpenOpen– Specifications available to Specifications available to

multiple contractorsmultiple contractors

• Non-ProprietaryNon-Proprietary– Source Code AvailableSource Code Available

– Can be used, copied, Can be used, copied, modified, and redistributed modified, and redistributed by the Government without by the Government without chargecharge

• Uses Industry StandardsUses Industry Standards– Technical Standards agreed Technical Standards agreed

to by Industry and to by Industry and Professional OrganizationsProfessional Organizations

Architecture CharacteristicsArchitecture Characteristics

1.1. Government Purpose Rights Government Purpose Rights 2.2. License software from various License software from various

developers for the life of the developers for the life of the COSCOS3.3. Limited Rights where there is no Limited Rights where there is no

alternative alternative (in rare instances)(in rare instances)

MIDDLEWAREAPPLICATION SERVICES

Government Rights to Application Government Rights to Application Services (Prioritized)Services (Prioritized)

PUBLIC RELEASE


FY09FY09

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

FYO5FYO5 FY06FY06 FY08FY08

– Middleware ServicesMiddleware Services• Publish/SubscribePublish/Subscribe• Discovery/MediationDiscovery/Mediation• Communication ServicesCommunication Services• Data RepositoryData Repository

– OS Abstraction LayerOS Abstraction Layer– Demonstration Application Demonstration Application

ServicesServices• Weapon-Target Assignment Weapon-Target Assignment • Sensor Manager Sensor Manager

– Human System Interface (HSI) for Human System Interface (HSI) for Demo missionsDemo missions

– Distributed Interactive Simulation Distributed Interactive Simulation (DIS) interface(DIS) interface

Build 0: Basic Services Build 0: Basic Services Dec 05Dec 05

Dec 08Dec 08Build 2: Multi-ShipBuild 2: Multi-Ship

– Functionality from Build 0Functionality from Build 0– Critical GIG interfacesCritical GIG interfaces

• BLOS communicationsBLOS communications• LOS communicationsLOS communications

– JMPS Pre-mission planning supportJMPS Pre-mission planning support • Primary Route and Contingency ManagementPrimary Route and Contingency Management• Support for Comm, Single Ship ESM, and Support for Comm, Single Ship ESM, and

WeaponsWeapons– HSI for Single Ship DemosHSI for Single Ship Demos– Sensor ManagementSensor Management

• SAR- Limited to Image Collection and BITSAR- Limited to Image Collection and BIT• ESM- Single Ship (ALR-69)ESM- Single Ship (ALR-69)

– Weapon ManagementWeapon Management– Information Management: Fusion (ESM Track Data)Information Management: Fusion (ESM Track Data)

Build 1: Single ShipBuild 1: Single ShipJun 07Jun 07

– Functionality from Build 1Functionality from Build 1– Interfaces to Mission Planning and Intel CellInterfaces to Mission Planning and Intel Cell

• SIPRNetSIPRNet• JWICSJWICS

– In-flight Mission PlanningIn-flight Mission Planning• Primary Route Planning and Contingency ManagementPrimary Route Planning and Contingency Management• Auto-routerAuto-router

– HSI for Multi-Ship OperationsHSI for Multi-Ship Operations– Sensor ManagementSensor Management

• ESM- Multi-ShipESM- Multi-Ship• SAR- Automatic Target Cueing, Image Registration, and SAR- Automatic Target Cueing, Image Registration, and

FusionFusion

– Battle Management*: Interface to ADSIBattle Management*: Interface to ADSI• Collects Track Data for operators Collects Track Data for operators

– Network Management*Network Management*• Quality of ServiceQuality of Service

– Attack ManagementAttack Management– Contingency ManagementContingency Management

• SystemSystem• MissionMission

– Information Management: Fusion (Off-board/On-Information Management: Fusion (Off-board/On-board)board)

FY10FY10FY07FY07


BUILD 0

Middleware Services All tasks associated with the development of core services that enable an application to interoperate within the enterprise

•Publish/Subscribe This component provides services to support synchronous and asynchronous exchanges. This includes publication/subscription, messaging services, etc.

•Discovery/Mediation The discovery component provides a set of services that enables the formulation and execution of search activities to locate data assets (files, databases, directories, web pages, streams) by exploitation metadata descriptions stored in and or generated by Information Technology (IT) repositories (directories, registries, catalogs, etc). This also includes the ability to search for metadata semantics to support mediation.This mediation component provides a set of services that enable transformation processing (adaptation, aggregation, transformation, and orchestration), situational awareness support (correlation and fusion), negotiation (brokering, trading, and auctioning services), and publishing.

•Communication Services This component provides application level services that provide point to point, client/server, peer to peer, multicast, and other connection topologies. These would be low-level protocol connections, as opposed to a publish/subscribe service that hides the protocol connection.

•Data Repository All of the mechanisms for managing files, databases, and other sources of persistent storage. Data may be cached locally to improve performance, as well as stored in a central repository. Distributed data storage shall not be addressed.

OS Abstraction Layer This component provides programming interfaces to a common Portable Operating System Interface (POSIX) compliant set of operating system abstractions.

Demonstration Application Services Applications built to demonstrate capabilities of the Build 0 middleware.

•Weapon-Target Assignment All tasks associated with the component development which provides weapon target pairing services based on mission type, air vehicle type and weapon type.

•Sensor Manager Sensor Manager for demonstration purposes.

Human System Interface for Demo Missions Displays created for visibility into of middleware services activities.

Distributed Interactive Simulation (DIS) Interface

A modeling and simulation protocol that allows the Government and Contractor simulation sites to pass data and control interface in data packets using a common description.

COS Functionality Description- Build 0COS Functionality Description- Build 0


BUILD 1

Critical GIG Interfaces

BLOS Comm Communication Interfaces to the individual systems’ primary and backup Beyond Line of Sight (BLOS) communication terminals. A common set of commands for command and control of the air vehicles and their subsystems.

LOS Comm Communication Interfaces to the individual systems’ primary and backup Line of Sight (LOS) communication terminals. A common set of commands for command and control of the air vehicles and their subsystems.

JMPS Pre-mission planning support

Functions associated with the mission/route plan generated by the mission planning cell. Converting the mission/route plan and for use with the Common Operating System.

•Primary route and Contingency Management

Primary route and contingency (back up) route planned before vehicle take-off.

•Support for Comm, Single Ship ESM, and Weapons

Pre-mission mission/route planning (interface to the Joint Mission Planning Segment (JMPS) or Mission Planning Cell to provide routes, communications, weapons, sensors, and other task plans)

HSI for Single Ship Demos The HSI includes but is not limited to:• Health and Status Management• Decision Aids• Platform Specific Operator Interfaces

Sensor Management Sensor Management component services that include support for:• Electronic Support Measures (ESM)• Synthetic Aperture Radar (SAR)

•SAR- Limited to Image Collection and BIT

The SAR sensor management component provides the capability to send a message to operate and receive status on the SAR system and antenna. The SAR sensor management component shall provide the capability to:• Switch on/off the SAR sensor including emergency switch off and place the sensor in standby or ECM/ECCM mode operation.• Receive status on the SAR systems.

•ESM-Single Ship ALR-69

The ESM sensor management product provides the capability to send a message to operate, and receive status on the ESM sensor. The ESM sensor management component shall provide the capability to:• Switch on/off the ESM sensor including emergency switch off and place the sensor in standby or Electronic Countermeasures/Electronic Counter-Countermeasures (ECM/ECCM) mode operation.• Receive status on ESM systems.

Weapon Management All tasks associated with the component development which provides the capability to determine the launch acceptability region for an air vehicle based on weapon type, target parameters, environmental conditions, and air vehicle position and velocity.

Information Mangement Fusion (ESM Track Data)

Track fusion provides the management of track responsibility between systems to include handover and synchronization. Fuse Electronic Order of Battle (EOB) data with ESM data



BUILD 2 (Pg 1 of 2)

Interfaces to Mission Planning and Intel Cell

•SIPRNet Interface software that allows J-UCAS to communicate over the Secret Internet Protocol Routing Network (SIPRNet).

•JWICS Interface software that allows J-UCAS to the Joint Worldwide Intelligence Communication System (JWICS).

In-flight Mission Planning This includes the management of functions which determine when new plans should be generated or considered by the operator and/or the intelligent software when running autonomously. Mission planning component services shall support:• Threat Assessment• Target Assessment• Mission/Route Assessment• Vehicle Assessment• Prediction Models

•Primary Route Planning and Contingency Management

In-flight route generation for primary route and other contingency route options. All tasks associated with the component development of route survivability.

•Auto-router The Auto-Router component generates routes which account for the current set of tasks, communications status, sensor status, threat environment, natural environment (i.e. weather), terrain, and signature for an air vehicle. Its primary task is to generate survivable routes for the Air Vehicle in real-time. Route survivability determines how survivable a route is given a threat environment and signature for an air vehicle. Route Survivability is defined to be the capability to produce a Probability of Survival (P(s)) of an air vehicle flying a given route.

HSI for Multi-Ship Operations The Human System Interface (HSI) includes that allows operators to control up to four air vehicles during mission operations.

Sensor Management Sensor Management component services shall include support for ESM in the form of the Advanced Tactical Targeting Technology (AT3) and SAR collections to support the kill chain.

•ESM- Multi-Ship The ESM – Multi-ship sensor management component shall provide the capability to operate, control, and receive status in the Multi-ship ESM sensor (AT3)

•SAR- Automatic Target Cueing, Image Registration, and Fusion

The software necessary to chip images out of SAR maps, register the pixels from the SAR map for generating Desired Mean Points of Impact for Precision Guided Munitions, and Fusion of SAR imaged targets with targets obtain from the Electronic Order of Battle (EOB).



BUILD 2 (Pg 2 of 2)

Battle Management: Common Relevant Op. Picture

The functions necessary to provide situation awareness to J-UCAS operators and mission commanders. Display of blue and red force information. Interface to Air Defense Systems Integrator (ADSI)

Network Management- Quality of Service

Services that provide an application/transport layer end-to-end quality of service. Quality of Service is the ability of a network to deliver service needed by specific network applications from end-to end with some level of control over delay, loss, jitter, and/or bandwidth.

Attack Management All tasks associated with the development of Attack/Mission Management related components shall be allocated to the Mission Management IPT. This includes all functions which determine the specific assignment of resources against objectives. Mission Management component services shall support: • Task Allocation• Sensor Pairings• Weapon-Target Pairings• Pairing Algorithm Selector • Task generation

Contingency Management This element includes all efforts necessary to design and develop the application level software for COS Contingency Management. Contingency Management is the detection of off-nominal system and mission conditions and suggested course of action (behavior) for the operator and/or intelligent software.

•System System failures are defined as those failures pertinent to a system as defined by a single J-UCAS system (i.e. X-45 air vehicle, X-47 ground station, Mission Planning Cell).

•Mission Mission failures are defined as those failures pertinent to a completing a mission (i.e. Persistent ISR, Pre-emptive destruction SEAD …).

Information Management: Fusion (Off-board/On-board)

Information Fusion component services for COS shall initially support:• Raw Data Processing • Automatic Target Recognition/Automatic Target Cueing• Correlation to support Target Identification using on-board and off-board INTEL products• Mensuration

COS Functionality Description- Build 2 (cont.)COS Functionality Description- Build 2 (cont.)


COS Supports J-UCAS Advanced OperationsCOS Supports J-UCAS Advanced Operations

MULTI-SHIP OPERATIONSMULTI-SHIP OPERATIONS NETWORK-CENTRIC OPERATIONSNETWORK-CENTRIC OPERATIONS

AUTONOMOUSAUTONOMOUS OPERATIONS OPERATIONS

Shared SpaceShared Space

StructuralMetadata

DataContents

DiscoveryMetadataCatalog

SAR

ESM

EO

CommonCommonOperatingOperating

SystemSystem

PUBLIC RELEASE


TopicsTopics

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


Development Strategy RationaleDevelopment Strategy RationaleWhy a Consortium?Why a Consortium?

• ““Consortium” is a single entity composed of Consortium” is a single entity composed of numerous organizations to focus resources on a numerous organizations to focus resources on a common effortcommon effort

– Common functionality is needed by both primesCommon functionality is needed by both primes

– No one company has all the needed resources nor No one company has all the needed resources nor capabilities to complete the capabilities to complete the Common Operating Common Operating SystemSystem development development

– Opportunity to incorporate the best of breed Opportunity to incorporate the best of breed solutionsolution

– Lowers barriers to entry for new technologyLowers barriers to entry for new technology

– Avoids a proprietary, closed OS implementation Avoids a proprietary, closed OS implementation

AgreementAgreementNorthropGrummanNorthropGrumman

BoeingBoeing

Integrator/Broker

Integrator/Broker

Integrator/Broker

A D

B C

A D

B C

A D

B C

JJ--UCAS UCAS PgmPgmOfficeOffice

JJ--UCAS UCAS PgmPgmOfficeOffice

• Provides a formal mechanism for cooperation amongst developing Provides a formal mechanism for cooperation amongst developing organizationsorganizations

– Rules: Articles of CollaborationRules: Articles of Collaboration– Established Structure: Integrator/Broker and PrimesEstablished Structure: Integrator/Broker and Primes– Process for dispute resolution Process for dispute resolution

• Allows the Government a mechanism to control ownership of the Allows the Government a mechanism to control ownership of the Common Common Operating SystemOperating System

PUBLIC RELEASE


• Key 3Key 3rdrd Party … Not an LSI Party … Not an LSI• Intellectual Property Opportunity – None … Limited?Intellectual Property Opportunity – None … Limited?• Six objectives of Integrator Broker (described in solicitation)Six objectives of Integrator Broker (described in solicitation)

1.1. Act as an impartial broker within the consortium.Act as an impartial broker within the consortium.

2.2. Facilitate, coordinate, and (if necessary) complete the Facilitate, coordinate, and (if necessary) complete the development of the J-UCAS enterprise architecture.development of the J-UCAS enterprise architecture.

3.3. Facilitate, coordinate, and (if necessary) complete the Facilitate, coordinate, and (if necessary) complete the development and integration of the development and integration of the COSCOS..

4.4. Develop and maintain an executable J-UCAS architectural Develop and maintain an executable J-UCAS architectural model.model.

5.5. Provide available infrastructure to support technology Provide available infrastructure to support technology identification and evaluation (e.g. simulation, labs, etc.).identification and evaluation (e.g. simulation, labs, etc.).

6.6. Maintain configuration control of Interface Control Maintain configuration control of Interface Control Documents (ICDs), executable models, and Documents (ICDs), executable models, and COS COS software software releases.releases.

Integrator/Broker DescriptionIntegrator/Broker Description

PUBLIC RELEASE


COS Consortium --COS Consortium --

Roles & ResponsibilitiesRoles & Responsibilities• JHU/APLJHU/APL

1.1. Function as the Consortium’s recording secretary and Function as the Consortium’s recording secretary and configuration manager for the COS development effort;configuration manager for the COS development effort;

2.2. Provide for an electronic, WEB-Based collaborative Provide for an electronic, WEB-Based collaborative environment;environment;

3.3. Administer and coordinate technology competitions; Administer and coordinate technology competitions; 4.4. Administer certain Technology Contributor subcontracts; Administer certain Technology Contributor subcontracts;

and and 5.5. Remain free from conflicts of interest to fulfill its role as Remain free from conflicts of interest to fulfill its role as

DARPA’s trusted agent.DARPA’s trusted agent.

• Boeing and NGSCBoeing and NGSC1.1. Participate as Primary Developers and Integrators of the COSParticipate as Primary Developers and Integrators of the COS

• Technology ContributorsTechnology Contributors1.1. Contribute Technology to the Consortium as authorized by Contribute Technology to the Consortium as authorized by

the CMC the CMC 2.2. Not party to the Articles of CollaborationNot party to the Articles of Collaboration

PUBLIC RELEASE


• Government funds Government funds COS COS development through the individual development through the individual consortium members’ agreementsconsortium members’ agreements

• Consortium delivers Consortium delivers COSCOS software to the government- software to the government- Integrator/Broker releases COS to the governmentIntegrator/Broker releases COS to the government

• Government furnishes Government furnishes COSCOS to the primes for integration into to the primes for integration into their systemstheir systems

J-UCAS Business Model J-UCAS Business Model MechanicsMechanics

$$

ConsortiumConsortium COS

1.1.

2.2.

3.3.

PUBLIC RELEASE


TopicsTopics



Potential Organizations to work as a Potential Organizations to work as a Technology ContributorTechnology Contributor

• Federally Funded R&D CentersFederally Funded R&D Centers• Military and Government LaboratoriesMilitary and Government Laboratories• UniversitiesUniversities• DOD ContractorsDOD Contractors• Others?Others?• Teams?Teams?


HSI IPT Applications

Contingency Management IPT

Route Management IPT

AssessmentManagement IPT

Sensor Management IPT

Mission Management IPT

Track Management IPT

Exploitation IPT

Infrastructure IPT

Information Assurance Sub-IPT

Edge Data Services Sub-IPT

Enterprise Services Sub-IPT

Platform Portability Sub-IPT

Enterprise Svs Mgmt Sub-IPT

WeaponsManagement IPT

COI Data Models & Interfaces IPT

ComponentDevelopment

COS Applications & InfrastructureCOS Applications & Infrastructure


COS HSI (Detail)COS HSI (Detail)

Human Systems Interface IPT

Operator Interfaces Sub-IPT

TC Candidate

TC CandidateFuture

HSI IntegrationFramework

J-UCAS has an Immediate Need for J-UCAS has an Immediate Need for HSI Technology Contributor SupportHSI Technology Contributor Support

J-UCAS has an Immediate Need for J-UCAS has an Immediate Need for HSI Technology Contributor SupportHSI Technology Contributor Support


Government’s Intent for COS HSIGovernment’s Intent for COS HSI

• Consistent “look and feel” in terms of appearance and “look and feel” in terms of appearance and behaviorbehavior

• Generic and Community of Interest (COI) functionalityGeneric and Community of Interest (COI) functionality

• Utilization of services to provide necessary functionalityUtilization of services to provide necessary functionality

• Legacy tolerant approachLegacy tolerant approach

• Flexibility and scalability – ability to modify and evolve as Flexibility and scalability – ability to modify and evolve as new techniques and technologies maturenew techniques and technologies mature

• User roles and profilesUser roles and profiles


Situation Assessment Situation Assessment

• Three development efforts taking placeThree development efforts taking place

– X-45 control element, X-47 control element, and X-45 control element, X-47 control element, and COSCOS

– Two vehicle specific control elements (X-45 and X-47) are being Two vehicle specific control elements (X-45 and X-47) are being developed developed

• Each prime developing a platform specific architectures, integrating Each prime developing a platform specific architectures, integrating vehicle and control element hardware, software, and operator vehicle and control element hardware, software, and operator interfaces with the interfaces with the COSCOS

• For the Operational Assessment, the Mission Control For the Operational Assessment, the Mission Control Element will need:Element will need:

– Platform-specific software for taxi, takeoff, launch, and Platform-specific software for taxi, takeoff, launch, and recovery; health and status monitoring; vehicle contingency recovery; health and status monitoring; vehicle contingency managementmanagement

– COSCOS software for mission management software for mission management

• COSCOS provides mission management functionality common to provides mission management functionality common to both vehicles and integrates selected vehicle-specific both vehicles and integrates selected vehicle-specific functionalityfunctionality


COS Heterogeneous HSI IntegrationCOS Heterogeneous HSI Integration

Web-based UI

Custom-built COS User Interface (UI) Container

Embedded UIElement

COS-GeneratedControl


User Interface Migration PathUser Interface Migration Path

X-45 Control Station

X-45-Functions X-47-Functions


Interface Interface

User User

Now


X-45-Functions X-47-Functions


Interface Interface

User User

Operational Assessment Common Functions

COS Functions COS Functions

User

Integrated Interface

COS Functions X-45-Functions

User Assistant (user profiles based on role or mission)

X-47-Functions

Future Vision Integrated User Interface


Mission Management IPT

AssessmentManagement IPT

Contingency Management IPT

Route Management IPT

Sensor Management IPT

Track Management IPT

Exploitation IPTWeapons

Management IPT

COS Applications (Detail)COS Applications (Detail)

System Failures

Mission Failures

Auto-Routers

RouteSurvivability

Auto-routerSelection

Pre-mission Route Planning

(JMPS Interface)

Threat Assessments

TargetAssessments

Mission Assessments

VehicleAssessments

Prediction Models

Electronic Support Measures

Synthetic Aperture Radar

Electro-OpticalInfrared

Task Allocation

Sensor Pairings

Weapon-Target Pairings

Pairing Algorithm Selection

Task Generation

Report Collection

Track Fusion

Launch Acceptability

Region

WeaponsInterface

Automatic Target Cueing

Tracking

Mensuration

Raw DataProcessing

Exploitation Algorithm Selection

Multi-ShipESM

TC Candidate

Build 0.0 Baseline

Applications

TC CandidateFuture


Infrastructure IPT

Information Assurance Sub-IPT

Enterprise ServicesMgmt Sub-IPT

Edge Data Services Sub-IPT

Guards

Authentication

SeparationKernel

ConnectionServices

Data StoreServices

Discovery

Messaging

Mediation

WebServices

Collaboration

OS Isolation Layer

Application Isolation Layer

I/O Wrappers

Platform Isolation

Comm.Services

DeploymentSetup/Configuration

NetworkManagement

End-to-EndQuality of Service

WrapperToolbox/Script

EngineTC Candidate

Build 0.0 Baseline

TC CandidateFuture

Enterprise Services Sub-IPT

Platform PortabilitySub-IPT

COS Infrastructure (Detail)COS Infrastructure (Detail)


Component IPT

TechnicalAssessment

EnterpriseArchitecture

Model

Notional Technology ContributorNotional Technology ContributorSelection ProcessSelection Process

EvaluationTeam

Cost-BenefitAnalysis

ProcurementReviewBoard

ContractContract

Model AssistedMetric Based Analysis

Proposal

RFPRFP

Consortium ManagementConsortium ManagementCommitteeCommittee

Industry Industry DayDay

Industry Industry DayDay

Technology ContributorsTechnology Contributors

GovernmentGovernment

(DARPA Oversight)(DARPA Oversight)


TC Selection Process FeaturesTC Selection Process Features

• APL will coordinate processAPL will coordinate process• The Evaluation Team and the Procurement Review Board will The Evaluation Team and the Procurement Review Board will

include members from Boeing, NGC and APLinclude members from Boeing, NGC and APL• Awards will be based on Selection Criteria to achieve best Awards will be based on Selection Criteria to achieve best

value for value for COSCOS• Selected TCs will be contributors, not consortium membersSelected TCs will be contributors, not consortium members

– Contracting through APLContracting through APL– Technical I/F through IPTsTechnical I/F through IPTs


DRAFT COS Consortium OrganizationDRAFT COS Consortium Organization

Executive SteeringCouncil

DARPA-Boeing-NGSC-APL

Executive SteeringCouncil

DARPA-Boeing-NGSC-APL



ConfigurationControlBoard

ConfigurationControlBoard

ConsortiumManagement Committee


NGC M. Buchanan-PM

D. Norman-Dep PM

NGC M. Buchanan-PM

D. Norman-Dep PM

BAC TBD

BAC TBD

APL TBD

APL TBD


Boeing/NGSC/APL


Boeing/NGSC/APLDARPA

Chief EngineersBoeing/NGSC/APLChief Engineers

Boeing/NGSC/APL

Engineering ReviewBoard

Engineering ReviewBoard

Business OpsBoeing/NGSC/APL

Business OpsBoeing/NGSC/APL

ApplicationsDevelopmentApplicationsDevelopment

Test &Evaluation

Test &Evaluation

Modeling &SimulationModeling &Simulation

SEIT/HorizontalIntegration

SEIT/HorizontalIntegration

InfrastructureDevelopmentInfrastructureDevelopment

HSIDevelopment

HSIDevelopment


Questions?Questions?

PUBLIC RELEASE Distribution Statement A: Approved for Public Release #2129 – Distribution Unlimited

J-UCAS Common Systems & Technologies Industry Day For Common Operating System (COS) Development...

Documents

Transcript of J-UCAS Common Systems & Technologies Industry Day For Common Operating System (COS) Development...