1. FACE 101 Robert Matthews NAVAIR Public Release 2013-920
Air Combat Electronics (PMA209)
FACE Integrated Project Team Lead (AIR )
FACE Steering Committee Chair
Robert Sweeney
FACE Lead Engineer (AIR )
FACE Technical Working Group Chair
NAVAIR Public Release
Distribution Statement A
"Approved for public release
distribution is unlimited”
Note throughout – all slides scrubbed to ensure trademark guidelines are followed (specifically, “FACE” may not be used as a noun).

2. Executive Overview
Approved under

3. Transitioning to Open Interface Architecture
New slide

4. Overlap of Capabilities
FACE Technical Standard, at a minimum, could provide for the Intersection of all Platform Data points
Applications written to Baseline Profile would run on ALL platforms
(Extremely Portable but may not leverage fuller capabilities of some platforms!)
Helicopter
Bomber
Cargo
Nav
Comm SA …
Fighter
Approved under
UAS

5. Why FACE Initiative?
DoD Airborne systems are typically developed for a unique set of requirements by a single vendor
Long lead times, even for urgent needs
Platform-unique designs limit reuse of software and increase cost
Creates barriers to competition within and across platforms
Current DoD Acquisition structure does not support the process of software reuse across different programs
Aviation community has not adopted a common set of OA standards sufficient to allow the reuse of software components across the DoD fleet
Aviation community has failed to enforce conformance to any existing open standards that are in use
Platform PMAs are not funded to assume cost or schedule risk of multi-platform requirements
Approved under
The Future Airborne Capability Environment (FACE) initiative is an approach designed as a response to the DoD aviation community’s problems

6. FACE Objectives
Establish a standard common operating environment to support portable capability-based applications across Department of Defense (DoD) avionics systems
Determine a strict set of Open Standards for the environment
Build upon Open Architecture (OA), Integrated Modular Avionics (IMA) and Modular Open Systems Approach (MOSA)
Portable, Modular, Partitioned, Scalable, Extendable, Secure
Reduce life cycle costs and time to field
Obtain Industry and DoD Program Management endorsement
Foster competitive marketplace
Facilitate conformance with standards to maximize interoperability between applications within the avionics system
Approved under

7. Why a FACE Consortium?
A consortium formed under the auspices of The Open Group is a “Voluntary Consensus Standards Body” as defined by the Nat’l Tech. Transfer Act and OMB Circular A-119 with the following attributes:
Openness
Balance of interest
Due process
An appeals process
Consensus
Enabler for consortium participation by US agencies
Foundation of consortium status under National Cooperative Research and Production Act (NCRPA)
Graphic modified from version approved under

8. FACE Consortium Members
Lockheed Martin
US Army PEO Aviation
Naval Air Systems Command (NAVAIR)
Rockwell Collins
Sponsor Level Member Organizations
ATK
GE Aviation Systems
IBM
Textron Systems
BAE Systems
General Dynamics
Northrop Grumman
US Army AMRDEC
Bell Helicopter
Green Hills Software
Raytheon
UTC Aerospace Systems
Boeing
Harris Corporation
Sierra Nevada Corp.
Wind River
Elbit Systems of America
Honeywell Aerospace
Sikorsky Aircraft
Principal Level Member Organizations
AdaCore
Chesapeake Technology Int’l.
Enea Software & Services
KIHOMAC
Stauder Technologies
Aitech Defense Systems, Inc.
CMC Electronics
ENSCO Avionics
Kutta Technologies
Support Systems Associates
Astronautics Corporation of America
Cobham Aerospace Communications
Esterel Technologies
L-3 Communications
Symetrics Industries
Exelis Inc.
LDRA Technology
Thomas Production Company
Avalex Technologies
Core Avionics & Industrial Inc.
Fairchild Controls
LynuxWorks
Tresys Technology
Barco Federal Systems
CTSi
GE Intelligent Platforms
Mobile Reasoning, Inc
TTTech North America, Inc.
Brockwell Technologies
Curtiss-Wright Controls Defense Solutions
General Atomics Aeronautical Systems, Inc.
Physical Optics Corp.
Tucson Embedded Systems
CALCULEX
Presagis
US Army Electronic Proving Ground
Carnegie Mellon Univ. – Software Engineering Institute
DDC-I
Howell Instruments, Inc.
QinetiQ North America
DornerWorks
Johns Hopkins Univ. - APL
Verocel
Real-Time Innovations
CERTON Software, Inc.
Draper Laboratory
Kaman Precision Products
Zodiac Data Systems
RichlandTechnologies
Associate Level Member Organizations
The FACE Consortium was formed in 2010 by The Open Group

9. How FACE Initiative is Different From previous DoD OA efforts
DoD worked with The Open Group to establish the FACE consortium such that each Service and Industry members had an equal voice in determining the solution
Aggressive outreach by both Industry and Gov’t
Build executive interest and adoption from the bottom up
1 Contract Award (Navy), 1 RFP (Navy), 8 RFIs to-date (5 Navy, 3 Army), 2 BAAs (1 Navy, 1 Army), 1 SBIR (Army)
FACE initiative is addressing business aspects in parallel with development of the Technical Standard
Analyzed previous OA efforts
Developed FACE Business Guide
Defined in sufficient detail to allow conformance certification
Public-Private collaboration to establish value for both customer and supplier
Approved under
RFPs
Navy C-130T (Awarded - Lockheed Martin -- $30 Million)
Navy Next Generation Jammer
RFIs
Army Airborne Radio Control Display Unit (CDU) Replacement
Army FACE Reference COE
Army Industry Day
Navy ADDS
Navy C-130T
Navy Full Motion Video
Navy RNP/RNAV PCS
Navy H-1 HMD
BAAs
Joint Multi-Role Technology Demonstrator
Navy AACUS
SBIRs
Army Air-to-Air Targeting of Turreted Systems

10. Published FACE Documentation
FACE Technical Standard Edition 1.0  
Technical Corrigendum for FACE Edition 1.0
FACE Technical Standard Edition 2.0
Including Data Model and Reference Implementation Guide
FACE Conformance Policy
FACE Conformance Authorities Plan
FACE Business Guide, Version 1.1
New slide

11. Major Business & Policy Issues FACE Initiative Wrestles With
Impacts
IP Licensing
Stakeholders
Scenarios
Acquisition
Guidance
Approved under
FACE
Products & Services
DFARS

12. FY13 FACE Initiatives FACE Consortium – Gov’t & Industry
Publish FACE Technical Standard Edition 2.0
Including Data Model and Reference Implementation Guide
Draft FACE Technical Standard Edition 3.0
Enhanced Security and Data Model
Publish FACE Conformance Policy and Procedures
Establish initial capabilities
Publish FACE Repository/Library Policy and Procedures
Publish FACE Contracting Guide
Develop RFI/RFP SOW, SSS, CDRL, L&M language to improve competition
Align FACE Consortium with OSD UCS Technical Society via MOA
FACE Ecosystem – Gov’t & Academia
Continue JPALS risk reduction
Assess/Model UCS-FACE Reference Architecture
Produce baseline Conformance Tools to FACE Technical Standard Edition 1.0 and 2.0
FACE Adoption - Gov't
Support platform architecture/roadmap assessments
Participate in Source Selection Evaluation Teams
Approved under ; updated to show which documentation has been published

13. Technical Overview
Approved under

14. FACE Technical Strategy
The FACE strategy is to create a software environment on the installed computing hardware of DoD aircraft (a.k.a. platforms) that enables FACE applications to be deployed on different platforms with minimal to no impact to the FACE application.
Approved under

15. What is FACE Architecture?
A software computing environment to enable product lines for military Aviation
The FACE architecture is comprised of a set of “places” where variance occurs
Points of variance are called “Segments”
The structure created by connecting these segments together is the beginning of the FACE architecture
Horizontal and vertical interfaces defined as part of FACE architecture
New Slide

16. Eliminates Barriers to Portability
Truly portable applications require common open standards at multiple layers in the architectures
Prevents lock-in and improves competition throughout supply chain
Approved under
Uniform application of common open standards across DoD aviation needed to break “Cylinders of Excellence”

17. FACE Architectural Segments
FACE Portable Components Segment
Portable Applications
Portable Common Services
Transport Services Segment
Platform Specific Services Segment
Platform Device Services
Platform Common Services
Graphics Services
I/O Services Segment
Drivers
Operating System Segment
Graphic modified from version approved under

18. FACE Architecture Example - Block Diagram
Graphic modified from version approved under

19. Standardization and Constraint on UoP Interfaces
Approved under

20. Transport Services Segment
Approved under

21. FACE Data Model Architecture
Approved under
Three levels to the primary data and message models aligned with ideas from the Object Management Group’s (OMG) Model Driven Architecture ™
The addition of the Component (UoP) Model allows us to tie components to the messages and data elements in the Platform Model
Supports definition and potentially generation of code and other artifacts

22. Transport Services API Data Model Definition
Approved under

23. FACE Architecture - Generic Partitioned View
Standard Transport interfaces
Approved under
Standard OS interfaces

24. Next Steps Technical Business
Finalize FACE Technical Standard Edition 2.0
Prototype/validate Standard Edition 2.0 (Academia)
Finalize Technical Corrigendum (TC) Edition 1.0
Finalize FACE Technical Standard Edition 1.1 (with TC inputs included)
Develop Edition 2.0 Reference Implementation Guidance
Develop FACE Technical Standard Edition 2.1/3.0
Business
Develop Business Guide
Develop Contract Guide
Develop Library implementation guidance
Develop Conformance implementation guidance
Conduct Outreach
Support CORP project and associated Program BCAs
Approved under ; added additional published documentation

25. Published FACE Standards
FACE Edition 1.0
Baseline Technical Standard and Business Guide 
Proof of concepts prove or disprove viability/functionality of proposed reference architecture
Initial software, integrator and conformance toolkits and reference applications
FACE Edition 1.1
Clarified requirements language
FACE Edition 2.0
Includes all updates from FACE Ed. 1.X series plus new functionality
Adds Data Model
Adds Ada IDLs
Adds Frameworks, Run-Times
Adds Device Protocol Mediation Services and Streaming Media Services
Adds Units of Portability (UoP) Packages

26. FACE Technical Standard, Edition 2.0 Technical Enhancements
Revised Data Model
Enhanced Health Monitor and Fault Management Requirements
Enhanced Configuration Requirements
Addressed Runtime and Component Framework packaging requirements
Allows for two additional Platform Specific Common Services
Device Protocol Mediation (DPM) Services
Streaming Media Services
Implementation Guidance for Edition 2.0
Use Cases
Safety Guidance
Security Guidance
Best Practices
Approved under

27. Future FACE Standards FACE Edition 2.1 FACE Edition 3.0
Enhanced Data Model functionality
Object Oriented Language Standard for TSS and I/O binding
Consistent use of terminology
Header files examples moved to the Reference Implementation Guide (RIG)
FACE Edition 3.0
Updates from FACE Ed. 2.X series
Configuration Services update (Centralized and Local)
Extension of I/O Service message types
Extension of OS API Set
Extension to Multi-Core and Hypervisor
Data Model refinements
DM/TSS harmonization
Extension of Graphics Services

28. TWG Structure Graphic modified from version approved under 2012-1233
TECHNICAL WORKING GROUP
Chair: Robert Sweeney
(NAVAIR)
Vice Chair: Kirk Avery (Lockheed Martin)
BWG Support
(Robert Sweeney/Kirk Avery/Dr. Bubba Davis/Marcell Padilla)
Standards Subcommittee
(Robert Sweeney/ Kirk Avery/David Bowes)
EA Support
(Kirk Avery/Jeff Hegedus/Robert Sweeney)
Edition 1.0 Revisions
Edition 2.1 Revisions
Edition 3.0 Revisions
FACE Introduction
Conformance
Library
Configuration
(Joel Sherrill/Joe Dusio)
Data Model
(Jeff Hegedus/Bill Kinahan)
Reference Implementation Guide
(Kirk Avery/David Bowes)
Conformance Verification Matrix
(Dr. Bubba Davis/Marcell Padilla)
Graphics
(Paul Jennings/Levi Van Oort)
Graphic modified from version approved under
Airworthiness
Guidance
(George Romanski/Glenn Carter)
General Enhancement
(Robert Sweeney/Brett Caspers
Transport
(Kirk Avery/Bill Antypas)
Security
(Joe Neal/Scott Wigginton)

29. Summary
FACE initiative will enable getting capabilities to the Warfighter faster and at a lower cost
FACE documentation is being designed through industry and government collaboration
FACE initiative is addressing the business concerns that have hampered other OA initiatives
FACE Technical Standard should be considered for any Defense avionics software procurement where reuse is a goal
Approved under ; updated language to fix trademark violations (i.e. no “FACE” as a noun)

30. BACKUP
Approved under

31. Interface Overview
FACE Technical Standard expands on the MOSA and OA principles
Use of abstraction layers at Key Interfaces to diminish the need for new standards
O/S interface (C) focused on POSIX profile and ARINC 653
I/O abstraction interface (B) based on common I/O API and messaging interface
Standardized Transport abstraction interface (A)
Defined to support POSIX, ARINC 653, DDS, CORBA
Extensible and Flexible for integration of future transport mechanisms
Approved under

32. FACE Overview FACE INITIATIVE TAKEAWAYS
Flight Control
Systems
Existing OFP
Human
Machine
Interface
Flight Controls
Surfaces
Platform
Devices & Networks
Blue Arrows = FACE Interfaces
Black Arrows = Existing Interfaces
FACE Software Library
Capability 1
Capability 2
Capability 3
Capability …
FACE™ Infrastructure
Gray Box = Optional Component
Blue Boxes = Avionics Components
OFP = Operational Flight Program
FACE INITIATIVE TAKEAWAYS
Infrastructure provides open, partitioned, safe, and secure environment
Software capabilities from Software Library are deployed in FACE Infrastructure
Enables portability of software capabilities across platforms
Streamlined integration and certification
Approved under
Reduced Cost and Accelerated Delivery of Capability to the WARFIGHTER

33. Examples of Application Packaging
Approved under

34. Open Architecture Requirement
DoD Directive
“E Systems Engineering. Acquisition programs shall be managed through the application of a systems engineering approach that optimizes total system performance and minimizes total ownership costs. A modular, open-systems approach shall be employed, where feasible.”
N6/N7 Naval Open Architecture (NOA) Requirements Letter 9010, Ser N6N7/5U916276, 23 Dec 05
This letter establishes the requirement to implement Open Architecture (OA) principles across the Navy Enterprise. Warfare systems include hardware, software and people.
SECNAVINST E
“Naval open architecture precepts shall be applied across the Naval Enterprise as an integrated technical and business approach and shall be used for all systems, including support systems, when developing an Acquisition Strategy per ASN(RD&A) memorandum of 5 Aug 04 and CNO (N6/N7) memorandum of 23 Dec 05 with enclosure (1).”
FACE is a rigorous and enforceable definition of OA
FACE is a standard, not a program or product
Single, open interpretation of existing industry standards and software best practices
Established collaboratively between services and industry
Initiated to achieve the goals of OA by explicitly addressing the business and technical issues which plagued other OA attempts