Future Airborne Capability Environment (FACE) CAPT Ralph Portnoy PMA209 Air Combat Electronics Mike Williamson, PMA209E Mission Systems Deputy Program Manager PMA209 champions development, integration and cradle-to-grave support for common avionics solutions in safety, connectivity, mission computing & interoperability

Scope: All of Naval Aviation Purpose of FACE FACE is a Common Operating Environment allowing for: Rapid insertion of capabilities Break the Operational Flight Program (OFP) cycle Leveraging common capabilities Reuse capabilities that have been developed on other platforms Common interpretation of standards More capability for existing budgets through leveraging Satisfaction of Weapon Systems Acquisition Reform Act of 2009 requirements Title II, Section 202(b) (5) - Use of modular, open architectures to enable competition for upgrades Increase competition through Industry defined, Government directed, common, verifiable, open standards Allow vendors to focus on innovation with the future budgets instead of focusing on recreating the wheel on every platform. Scope: All of Naval Aviation

Solution - FACE Modern processing environment True Open Systems Modular, Partitioned, Scalable, Portable, Extendable, Secure True Open Systems Adherence to commercial standards wherever possible Eliminate proprietary hooks in architecture Library of capability based services and applications Government / Industry partnership Paradigm shift required Capability based requirements in a Platform Centric world Cross-platform commonality Industry cooperation – use of open commercial standards FACE will bring rapid insertion of capabilities within existing budgets It will be a modern processing environment that will be modular, partitioned, scalable, portable, extendable and secure It will provide true open systems through adherence to commercial standards and elimination of proprietary hooks It will provide a library of portable capability “apps” Resulting in the ability to strictly manage Avionics Architecture 3

Ensures Interoperability and Cost Savings FACE Implementation Flight Control Surfaces Flight Control Systems Flight Controls OFP Mission Critical Displays Sensors Networks External Interfaces FACE Inputs Software Library KEY IDEAS Common Interpretation of Standards for Sensors and Networks Common Software Applications isolated from unique platform software Ensures Interoperability and Cost Savings

FACE Modular Architecture Partitioned: ARINC 653 time and space Partition Future New Application OS FliteScene Map StrikeLink Digital CAS Situational Awareness Fusion Engine OFP Separation Kernel FACE Middleware Components Device Drivers BSP BIT / Terminal Partition Spare OS FliteScene StrikeLink Situational Awareness Fusion Engine OFP Separation Kernel FACE Middleware Components Device Drivers BSP BIT / Terminal Partition Spare OS FliteScene StrikeLink Situational Awareness Fusion Engine OFP Separation Kernel FACE Middleware Components Device Drivers BSP BIT / Terminal . . Scalable . Applications, Scalable, Independent Partitions, Supports Modern Security Environment

Modular Open System Approach (MOSA) FACE provides teeth to the five key principles of MOSA Principle I: Establish an Enabling Environment Enable technical and business environment for open architecture acquisition Principle II: Employ Modular Design Define a technical environment that allows for portable, modular, software capabilities that can be reused across multiple platforms Principle III: Designate Key Interfaces Define key vertical and horizontal interfaces for portability, modularity, and interfaces to legacy systems Principle IV: Use Open Standards Develop an open standard for DOD avionics architecture defined by commercial open API’s and Interface standards Principle V: Certify Conformance Provide guidance to industry on the use of a standard Software Development Kit as well as a conformance test suite Establish process for independent verification and validation

FACE Technical Objective Drive towards modern computing architecture Build upon commercialized integrated modular avionics model (reduced regression testing, reduced cost, shorter schedules) Build upon Modular Open System Approach (MOSA) and Naval Open Architecture Modular: Government owned/licensed library of modular software applications/services Partitioned: ARINC 653 Time and Space Scalable: Ability to add new capabilities with clearly defined interfaces Secure: Multiple Independent Levels of Security (MILS)/Multilevel Security (MLS) capable Software Driven Objective, Hardware Agnostic Integrated commercial avionics- Commercial model allows for building a system and then selling for profit. Capability leveraging is used for cost and schedule sharing in the commercial aviation industry. Software driven capabilities should be broken up into modules that can be executed separately instead of package together into one OFP.

FACE Consortium The Open Group manages the Consortium Membership Company with experience leading Gov’t/Industry consortiums Goal to develop FACE architecture and interfaces Based on a standard of open commercial standards Develop FACE business model Membership Includes all 3 services 13 Founding Members 5 New Members FACE Consortium kick-off meeting held 8 June 2010 Working groups formed & engaged in Technical & Business efforts

Consortium Deliverables Technical Group Define Open Standard of Commercial Standards Supports DoD Modular Open Systems Approach (MOSA) and Weapon Systems Acquisition Reform Act of 2009 Define horizontal and vertical interfaces Develop a software development toolkit (SDK) Government owned Available to all vendors Develop a conformance verification process Business Group Develop a business model that is attractive to industry and government How do we do it? We need to define the standard then use that standard as part of the requirements for all new systems. We will embed all new capabilities into the FACE architecture without replacing the OFP ADDS will be the first targeted program Once FACE is defined there will need to be a software development toolkit that will be government owned and available to all vendors FACE Consortium - A Collaborative Approach to define a Common Open Standard 9

FACE - Truly Open Architecture Achieved FACE Implementation Draft FACE Standard available in December 2010 FACE Standard to be placed on contract for two new acquisitions in FY-11 ECPs to existing programs will incorporate FACE standard where possible Full FACE ROI dependent on wide acceptance & implementation in multiple T/M/S Permits leveraging of investments, speeds capability delivery, fosters interoperability Classified data recording requirements Digital video (HUD, BDA, surveillance, cockpit, etc…) Audio recording Digital data rest requirements (MFOQA, maintenance, intel, etc…) Multiple bus recording Electronic warfare/weapons/navigation/etc… 1553, Ethernet, fiber channel, RS422, ARINC 429, etc… Engine monitoring (IMD, HUMS, MFOQA, vibration, etc…) Rapid download capability (CSR/FDR, MFOQA, TAMMAC, IMD/HUMS) Bulk memory (TAMMAC, etc…) Data loaders ASQ-215/AMU/DMD replacement Multiple NAVAIR platforms: 2/3rds of the Navy’s Fleet affected by obsolete loaders (>1500 aircraft) FACE - Truly Open Architecture Achieved 10

Summary FACE defined by an Industry / Government Consortium FACE defined by Standardizing a set of Open Standards FACE will be scalable with independent partitions supporting modern security environment FACE will facilitate conformance to a common avionics architecture ensuring interoperability FACE will reduce time to field new capabilities In summary: FACE will facilitate strict management of avionics architecture ensuring interoperability and cost savings for the future. It will be scalable with independent partitions supporting security requirements. All PMA-209 programs will be FACE conformant starting with ADDS which will prioritize services required of FACE version 1. Ultimately, FACE will be defined by those in this room by establishing a Standard of Open Standards within a very aggressive timeline to support ADDS SRR in DEC 10 and RFP in MAR 11. FACE - CRITICAL to delivering Future Airborne Capabilities Application across T/M/S maximizes benefits 11

Questions ? Mike Williamson, PMA209E Mission Systems Deputy Program Manager michael.williamson@navy.mil (301)757-9441 Bob Matthews, PMA209EA Deputy Capability Lead robert.matthews@navy.mil (301) 995-4971 PMA209 Vision: where DoD organizations insist upon common, capability-centric avionics systems for their inherent value, interoperability, and cost-effectiveness.

Intellectual Property (IP) In FACE, it is the environment that is open Hardware and application software IP is acceptable Hardware Hardware agnostic – Board support package must meet hardware interfaces IP at the board level is acceptable Open competition at the board level Software Software library will be a mix of government owned, open source, and industry licensed software IP in a software program acceptable as long as the software package is completely FACE conformant