1. J-UCAS Common Systems & Technologies Industry Day For Common Operating System (COS) Development J-UCAS Common Systems & Technologies Industry 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 OverviewJ-UCAS Overview The Common Operating System (COS)The Common Operating System (COS) The COS ConsortiumThe COS Consortium Technology Contributor OpportunitiesTechnology 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 2003DARPA-Air Force-Navy Development – Began 1 Oct 2003 –Outgrowth of Earlier DARPA Programs Program ObjectivesProgram 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 ArchitectureAtypical Program Architecture –Spiral Development Approach with Aggressive Timelines Cutting Edge Technology … ATDs … Operational AssessmentCutting Edge Technology … ATDs … Operational Assessment –Contractors 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 System Consortium (Boeing, NG, Johns Hopkins APL)Common Operating System Consortium (Boeing, NG, Johns Hopkins APL) Large Program - $4B+ over the FYDPLarge 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 StrikeStrike SurveillanceSurveillance Electronic Attack SEAD – Destructive & Non-Destructive & Non-Destructive SEAD – Destructive & Non-Destructive & Non-Destructive Dangerous Missions – Denied Airspace Dangerous Missions – Denied Airspace Survivable Air Vehicles Survivable Air Vehicles Advanced Sensors & Weapons Advanced Sensors & Weapons Network-Centric Architecture Network-Centric Architecture Distributed Command & Control Distributed Command & Control Intra-operable Platforms Intra-operable Platforms Collaborative Operations Collaborative Operations Land or Sea Based System Land or Sea Based System Global Operations Global Operations PUBLIC RELEASE Distribution Statement A: Approved for Public Release case #4178– Distribution Unlimited

5. J-UCAS System Elements A Way Forward … ControlStations Payload Systems Payload Systems Direct Support Air Vehicles Common Operating 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 OperationalInfrastructure Communications 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 EnvironmentSEAD Mission Environment Multi-Platform Collaborative OperationsMulti-Platform Collaborative Operations VignettesVignettes –Target Detect, Geo-locate, ID and Attack –Collaboration for Survivability –Damage Tolerance –Autonomous Aerial Refueling –Preemptive & Reactive Operations PUBLIC RELEASE Distribution Statement A: Approved for Public Release #4785 – Distribution Unlimited

7. Cooperative Operations Mission Planning Time Joint Unmanned Combat Air Systems -- … ‘Raising the Bar’ Operator : Vehicle Ratio Global Hawk 1 : 1 Predator Many : 1 J-UCAS 1 : Many … J-UCAS Multi Ship, Cooperative Targeting & Attack Interoperable J-UCAS Multi Ship Hours Global Hawk Single Ship Days Communication Management Fielded Systems Single Ship Only Stove-Piped Systems No Cooperation Global Hawk Dedicated Channel per Vehicle Large Bandwidth Blocks J-UCAS Shared Channels Quality of Service Net Ready Operational Environment J-UCAS Denied Airspace Survivable Design Land & Sea Based Mainstream Air Ops Predator & Global Hawk Secured Airspace Land Based Dissimilar Air Ops PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #4178– Distribution Unlimited

8. Topics 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 RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

9. Common Operating System Common Operating System Common Operating System The Architecture, Algorithms & Software, The Architecture, Algorithms & Software, that: that: 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-45 X-47 Other Air Vehicles Remote Control Element Control Element PUBLIC RELEASE Approved for Public Release Case #2129 - Distribution Unlimited

10. J-UCAS “Common Operating System” J-UCAS Common Operating System Commercial Operating System Manages Resources: –Sensors –Weapons –Communication Links / Bandwidth –Air Vehicles Manages Resources: –Memory –CPU time –Disk Space –Peripheral Devices (keyboard, mouse, Etc.) Provides Security: –Controls Access to the System Provides Security: –Controls Access to the System Facilitates Information Exchange: –Global Information Grid (GIG) Facilitates Information Exchange: –Data Bus Human System Integration (HSI): –Decision Aids –Common relevant operational picture Graphical User Interface (GUI): –Windows System organizes images and controls on screen Provides System Services: –Contingency Management –Fusion –Publish/Subscribe –Discovery/Mediation –Communication Services –Data Repository Provides Services: –Schedules, loads, initiates, and supervises the execution of programs –Allocates storage – initiates and controls input/output operations – Handles errors Resides: –On top of Embedded OS Resides: –On top of BIOS PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

11. Common Operating System (COS) -- Why Develop It? Provide Needed Mission FunctionalityProvide Needed Mission Functionality –Manages interactions between system components Enable collaborative operationsEnable collaborative operations –Allows Autonomous Operations –Facilitate agile bandwidth management Reduce Development CostsReduce Development Costs –Build it one time –Don’t “throw it away”- Use on Follow-on Programs Reduce Technology Barriers to EntryReduce Technology Barriers to Entry –Attract ‘best-of-breed’ algorithms & functionality –Enable competition at the function level Assure Intra- and Inter-operabilityAssure Intra- and Inter-operability –Primes collaborate to develop –Same software used on all platforms Decouple System IT from PlatformsDecouple System IT from Platforms –Allow natural development timelines –Reduce interdependencies CommonOperatingSystem(COS) PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

12. Common Operating System -- Functionality Lines of Demarcation Information ManagementInformation Management Publish/SubscribePublish/Subscribe FusionFusion Battle ManagementBattle Management Common Relevant Operational PictureCommon Relevant Operational 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 Common Operating System VMS Sensors Support GuidanceGuidance Flight ControlFlight Control Vehicle Contingency ManagementVehicle Contingency Management 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 capability)(Taxi, take-off, and landing capability) Signal ProcessingSignal Processing Mission Data ProcessingMission Data Processing Sensor ModesSensor Modes Vehicle Specific Health ManagementVehicle Specific Health Management Ground TestGround Test Built in TestBuilt in Test Portable Field TestersPortable Field Testers Weapons Stores ManagementStores Management Crypto Key LoadingCrypto Key Loading Platform Specific Software 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 Approved for Public Release Case #4296 - Distribution Unlimited

13. Common Operating System -- Architecture MIDDLEWARE SERVICES COS Services API Battle Management Planning Human System Interface Sys Mgmt- Multi-Ship Ops Contingency Management Resource & Sensor Mgmt Network Management Information Mgmt Critical GIG Interfaces Data Stores Services System Services Information Assurance OpenOpen –Specifications available to multiple contractors Non-ProprietaryNon-Proprietary –Source Code Available –Can be used, copied, modified, and redistributed by the Government without charge Uses Industry StandardsUses Industry Standards –Technical Standards agreed to by Industry and Professional Organizations Architecture Characteristics 1.Government Purpose Rights 2.License software from various developers for the life of the COS 3.Limited Rights where there is no alternative (in rare instances) MIDDLEWARE APPLICATION SERVICES Government Rights to Application Services (Prioritized) PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

14. FY09 Common Operating System Build Schedule (As of 31 May 05) FYO5 FY06FY08 –Middleware Services Publish/SubscribePublish/Subscribe Discovery/MediationDiscovery/Mediation Communication ServicesCommunication Services Data RepositoryData Repository –OS Abstraction Layer –Demonstration Application Services Weapon-Target AssignmentWeapon-Target Assignment Sensor ManagerSensor Manager –Human System Interface (HSI) for Demo missions –Distributed Interactive Simulation (DIS) interface Build 0: Basic Services Dec 05 Dec 08 Build 2: Multi-Ship –Functionality from Build 0 –Critical GIG interfaces BLOS communicationsBLOS communications LOS communicationsLOS communications –JMPS Pre-mission planning support Primary Route and Contingency ManagementPrimary Route and Contingency Management Support for Comm, Single Ship ESM, and WeaponsSupport for Comm, Single Ship ESM, and Weapons –HSI for Single Ship Demos –Sensor 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 Management –Information Management: Fusion (ESM Track Data) Build 1: Single Ship Jun 07 –Functionality from Build 1 –Interfaces to Mission Planning and Intel Cell SIPRNetSIPRNet JWICSJWICS –In-flight Mission Planning Primary Route Planning and Contingency ManagementPrimary Route Planning and Contingency Management Auto-routerAuto-router –HSI for Multi-Ship Operations –Sensor Management ESM- Multi-ShipESM- Multi-Ship SAR- Automatic Target Cueing, Image Registration, and FusionSAR- Automatic Target Cueing, Image Registration, and Fusion –Battle Management*: Interface to ADSI Collects Track Data for operatorsCollects Track Data for operators –Network Management* Quality of ServiceQuality of Service –Attack Management –Contingency Management SystemSystem MissionMission –Information Management: Fusion (Off-board/On- board) FY10 FY07 PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

15. BUILD 0 Middleware ServicesAll tasks associated with the development of core services that enable an application to interoperate within the enterprise Publish/SubscribeThis component provides services to support synchronous and asynchronous exchanges. This includes publication/subscription, messaging services, etc. Discovery/MediationThe 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 ServicesThis 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 RepositoryAll 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 LayerThis component provides programming interfaces to a common Portable Operating System Interface (POSIX) compliant set of operating system abstractions. Demonstration Application ServicesApplications built to demonstrate capabilities of the Build 0 middleware. Weapon-Target AssignmentAll tasks associated with the component development which provides weapon target pairing services based on mission type, air vehicle type and weapon type. Sensor ManagerSensor Manager for demonstration purposes. Human System Interface for Demo MissionsDisplays 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 0 PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

16. BUILD 1 Critical GIG Interfaces BLOS CommCommunication 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 CommCommunication 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 DemosThe HSI includes but is not limited to: Health and Status Management Decision Aids Platform Specific Operator Interfaces Sensor ManagementSensor 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 ManagementAll 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 COS Functionality Description- Build 1 PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

17. BUILD 2 (Pg 1 of 2) Interfaces to Mission Planning and Intel Cell SIPRNetInterface software that allows J-UCAS to communicate over the Secret Internet Protocol Routing Network (SIPRNet). JWICSInterface software that allows J-UCAS to the Joint Worldwide Intelligence Communication System (JWICS). In-flight Mission PlanningThis 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-routerThe 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 OperationsThe Human System Interface (HSI) includes that allows operators to control up to four air vehicles during mission operations. Sensor ManagementSensor 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-ShipThe 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). COS Functionality Description- Build 2 PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

18. 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 ManagementAll 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 ManagementThis 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. SystemSystem 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). MissionMission 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.) 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 AUTONOMOUS OPERATIONS Shared Space Structural Metadata Data Contents Discovery Metadata Catalog SAR ESM EO CommonOperatingSystem PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

20. Topics 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 RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

21. Development Strategy Rationale Why a Consortium? “Consortium” is a single entity composed of numerous organizations to focus resources on a common effort“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 organizationsProvides 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 SystemAllows the Government a mechanism to control ownership of the Common Operating System PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

22. Key 3 rd Party … Not an LSIKey 3 rd 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.Act as an impartial broker within the consortium. 2.Facilitate, coordinate, and (if necessary) complete the development of the J-UCAS enterprise architecture. 3.Facilitate, coordinate, and (if necessary) complete the development and integration of the COS. 4.Develop and maintain an executable J-UCAS architectural model. 5.Provide available infrastructure to support technology identification and evaluation (e.g. simulation, labs, etc.). 6.Maintain configuration control of Interface Control Documents (ICDs), executable models, and COS software releases. Integrator/Broker Description PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

23. COS Consortium -- Roles & Responsibilities JHU/APLJHU/APL 1.Function as the Consortium’s recording secretary and configuration manager for the COS development effort; 2.Provide for an electronic, WEB-Based collaborative environment; 3.Administer and coordinate technology competitions; 4.Administer certain Technology Contributor subcontracts; and 5.Remain free from conflicts of interest to fulfill its role as DARPA’s trusted agent. Boeing and NGSCBoeing and NGSC 1.Participate as Primary Developers and Integrators of the COS Technology ContributorsTechnology Contributors 1.Contribute Technology to the Consortium as authorized by the CMC 2.Not party to the Articles of Collaboration PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

24. Government funds COS development through the individual consortium members’ agreementsGovernment funds COS development through the individual consortium members’ agreements Consortium delivers COS software to the government- Integrator/Broker releases COS to the governmentConsortium delivers COS software to the government- Integrator/Broker releases COS to the government Government furnishes COS to the primes for integration into their systemsGovernment furnishes COS to the primes for integration into their systems J-UCAS Business Model Mechanics $ Consortium COS 1. 2. 3. PUBLIC RELEASE Approved for Public Release Case #4296 - Distribution Unlimited

25. Topics 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 RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

26. Potential Organizations to work as a Technology 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? PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

27. HSI IPTApplications Contingency Management IPT Route Management IPT Assessment Management 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 Weapons Management IPT COI Data Models & Interfaces IPT Component Development COS Applications & Infrastructure PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

28. COS HSI (Detail) Human Systems Interface IPT Operator Interfaces Sub-IPT TC Candidate Future HSI Integration Framework J-UCAS has an Immediate Need for HSI Technology Contributor Support 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. Government’s Intent for COS HSI “look and feel” in terms of appearance and behaviorConsistent “look and feel” in terms of appearance and behavior 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 new techniques and technologies matureFlexibility and scalability – ability to modify and evolve as new techniques and technologies mature User roles and profilesUser roles and profiles PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

30. Situation Assessment Three development efforts taking placeThree 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 COSEach 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: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 functionalityCOS 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 Web-based UI Custom-built COS User Interface (UI) Container Embedded UI Element COS-Generated Control PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

32. User Interface Migration Path X-45 Control Station X-45-Functions X-47-Functions X-47 Control Station Interface User Now X-45 Control Station X-45-Functions X-47-Functions X-47 Control Station Interface User Operational Assessment Common 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 PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

33. Mission Management IPT Assessment Management IPT Contingency Management IPT Route Management IPT Sensor Management IPT Track Management IPT Exploitation IPT Weapons Management IPT COS Applications (Detail) System Failures Mission Failures Auto-Routers Route Survivability Auto-router Selection Pre-mission Route Planning (JMPS Interface ) Threat Assessments Target Assessments Mission Assessments Vehicle Assessments Prediction Models Electronic Support Measures Synthetic Aperture Radar Electro-Optical Infrared Task Allocation Sensor Pairings Weapon- Target Pairings Pairing Algorithm Selection Task Generation Report Collection Track Fusion Launch Acceptability Region Weapons Interface Automatic Target Cueing Tracking Mensuration Raw Data Processing Exploitation Algorithm Selection Multi-Ship ESM TC Candidate Build 0.0 Baseline Applications TC Candidate Future PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

34. Infrastructure IPT Information Assurance Sub-IPT Enterprise Services Mgmt Sub-IPT Edge Data Services Sub-IPT Guards Authentication Separation Kernel Connection Services Data Store Services Discovery Messaging Mediation Web Services Collaboration OS Isolation Layer Application Isolation Layer I/O Wrappers Platform Isolation Comm. Services Deployment Setup/Configuration Network Management End-to-End Quality of Service Wrapper Toolbox/Script Engine TC Candidate Build 0.0 Baseline TC Candidate Future Enterprise Services Sub-IPT Platform Portability Sub-IPT COS Infrastructure (Detail) PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

35. Component IPT Technical Assessment Enterprise Architecture Model Notional Technology Contributor Selection Process Evaluation Team Cost-Benefit Analysis Procurement Review Board Contract Model Assisted Metric Based Analysis Proposal RFP Consortium Management CommitteeIndustryDayIndustryDay Technology Contributors Government (DARPA Oversight) PUBLIC RELEASE Distribution Statement A: Approved for Public Release Case #5277– Distribution Unlimited

36. TC Selection Process Features APL will coordinate processAPL will coordinate process The Evaluation Team and the Procurement Review Board will include members from Boeing, NGC and APLThe 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 COSAwards will be based on Selection Criteria to achieve best value for COS Selected TCs will be contributors, not consortium membersSelected 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 Executive Steering Council DARPA-Boeing-NGSC-APL Procurement Review Board Procurement Review Board Configuration Control Board Configuration Control Board Consortium Management Committee Consortium Management 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 Consortium Management Committee Boeing/NGSC/APL Consortium Management Committee Boeing/NGSC/APL DARPA Chief Engineers Boeing/NGSC/APL Chief Engineers Boeing/NGSC/APL Engineering Review Board Engineering Review Board Business Ops Boeing/NGSC/APL Business Ops Boeing/NGSC/APL Applications Development Applications Development Test & Evaluation Modeling & Simulation SEIT/Horizontal Integration SEIT/Horizontal Integration Infrastructure Development Infrastructure Development HSI 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