Your systems. Working as one.

ArchitectureExecutive Summary

William AntypasChief Consulting EngineerFACETM Standards Alignment Chair

TSS SC Chair

June 20, 2013

FACE™ is a trademark of The Open Group

NAVAIR Public Release 2012-1233

Distribution Statement A "Approved for public release

distribution is unlimited”

Executive Summary Agenda

– FACE Strategy– FACE Business Model– FACE Technical Standard

Your systems. Working as one.

Executive Overview

COEs and Mobile Computing• Advances in mobile productivity owe much to Common Operating

Environments• A Smartphone example highlights the benefits of COEs and gives

contrast to the DoD Avionics domain• The FACE Technical Standard establishes a COE for DoD Avionics

Commercial Military

TM

•FACE, 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!)

Overlap of Capabilities

Fighter

Bomber

Helicopter

Cargo

UAS

NavCommSA…

• 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

Why FACE?

The Future Airborne Capability Environment (FACE) is an approach designed as a response to the DoD aviation community’s problems

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)

Steering Committee

Enterprise Architecture

AdvisoryBoard

FACE / UCS Alignment

Technical Working

Group

Business Working

Group

600+ Individual Participants

Consortium Structure

The FACE Consortium was formed in 2010 by The Open Group

Sponsors:•Lockheed Martin•Naval Air Systems Command (NAVAIR)•US Army PEO Aviation•Rockwell Collins

Associates: • AdaCore• Aitech Defense Systems• Barco Federal Systems• Brockwell Technologies• CALCULEX• Carnegie Mellon SEI• Chesapeake Technology

Int’l.• CMC Electronics• CoreAVI• CTSi• Curtiss-Wright Controls

Defense Solutions• DDC-I• DornerWorks• Draper Laboratory• Esterel Technologies• FMS Secure Solutions• GE Intelligent Platforms• Johns Hopkins Applied

Physics Lab

• L-3 Communications• LDRA Technology• LynuxWorks• Objective Interface Systems

• Physical Optics Corp.• Presagis• QinetiQ North America• Real-Time Innovations• Richland Technologies• Stauder Technologies• Support Systems Associates• Symetrics Industries• Thomas Production

Company• Tresys Technology• TTTech North America• Tucson Embedded Systems• Verocel• ViaSat• Zodiac Data Systems

FACE Consortium Members

Principals: • ATK• BAE Systems• Bell Helicopter• Boeing• Elbit Systems of

America• GE Aviation Systems• General Dynamics• Green Hills Software• Harris Corporation

• Honeywell Aerospace• Northrop Grumman• Raytheon• Sierra Nevada Corp.• Sikorsky Aircraft• Textron Systems• US Army AMRDEC• UTC Aerospace

Systems• Wind River

Publically Released FACE Deliverables• FACE Business Guide

– Steering Committee approved Business Guide August 2011

– Business Guide received PAO approval September 2011– http://www.opengroup.org/bookstore/catalog/g115.htm

• FACE Technical Standard– Steering Committee approved Technical Standard

January 2012– The Open Group Governing Board approved without

objection 26 January 2012 – Edition 1.0 published and available at the following link on The Open

Group's Bookstore: – http://

www.opengroup.org/bookstore/catalog/c122.htm– Edition 2.0 released – March 2013

– https://www2.opengroup.org/ogsys/catalog/c137

How FACE 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 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

Your systems. Working as one.

Business Overview

BUSINESS WORKING GROUP(BWG)

Business Model

Library Outreach

TWG Support

BWG Structure

Conformance

Business Products

• Business Guide• Contract Guide• Library Implementation

– FACE Library Requirements Document Edition 2.0 – FACE Library

• Conformance Process– FACE Conformance Policy – FACE Conformance Certification Guide – FACE Conformance Statement– FACE Verification Statement

• Conduct Outreach

Stakeholders

AcquisitionGuidance

Scenarios

IP Licensing

FACE Products & Services

DFARS

Impacts

Major Business and Policy Issues That FACE Wrestles With

FACE Contract Guide

• Suggested Request For Proposal Language– Contract Requirements– Evaluation Criteria

• Suggested Contract Language– Performance– Incentive– Fee

FACE Conformance Policy

FACE Repository/Library

Your systems. Working as one.

Technical Overview

TECHNICAL WORKING GROUP

(TWG)

SEGMENT LEADS

Data Modeland Data Definition

• Configuration Model• Data Model• Health Monitor Data

Model• Data Definition

Reference Implementation

Guide• Technical Architecture

Views• Organization• Safety/Security• Implementation and

integration• Language runtimes and

network libraries

Conformance Verification

Matrix

• Edition1.0 Revisions• FACE Introduction

BWG Support

• Conformance• Repository

TWG Structure

• Develop conformance verification matrix

• Define conformance test suite requirements

• Develop matrix user’s guide

Transport Services Segment

• TSS API• TSS Configuration

• FACE Technical Standard Edition 2.1– 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, 2.1– Use Cases– Safety Guidance– Security Guidance– Best Practices

FACE Edition 2.0 Technical Deliverables

FACE Technical Strategy

War-Fighting Platform

Existing Computer Hardware New Computer Hardware

FACE Computing EnvironmentFACE Computing

Environment

Portable FACE

application

Portable FACE

application

Portable FACE

application

Avionics Networks

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.

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

• Uniform application of common open standards across DoD aviation needed to break “Cylinders of Excellence”

TraditionalApplication

PresentationConcerns

(Display H/W & S/W, headless transports, cursor

devices, etc.)

Business Logic Concerns(Many MIL-STDs, FMF, RNP/RNAV, Situational

Awareness, etc.)

I/O Concerns(Interface Cards, Radio ICDs, Networks, OFPs,

etc.)

Other cooperating and/or supporting applications

SPECIFICDisplay Hardware &

Software

SPECIFICRadios, Networks &

software subsystems

Tight Coupling here is a barrier

to portability

Tight Coupling here is a barrier to portability

Tight Coupling here is a barrier

to portability

SPECIFICOperating System & Drivers

Tight Coupling here is a barrier to portability

Portable FACEApplication

PresentationConcerns

(Display H/W & S/W, headless transports, cursor devices, etc.)

Business Logic Concerns

(Many MIL-STDs, FMF, RNP/RNAV, Situational

Awareness, etc.)

I/O Concerns(Interface Cards, Radio ICDs, Networks, OFPs,

etc.)

Other cooperating and/or supporting applications

SPECIFICDisplay Hardware &

Software

SPECIFICRadios, Networks &

software subsystems

Tight Coupling here no longer impacts application portability

AdaptationLayer

AdaptationLayer

AdaptationLayer

SPECIFICOperating System & Drivers

No longer a barrier to portability due to selection of operating system standards being present at all computing environments

Immutable abstraction interfaces enable portability as tight coupling is moved out of the “application”

FACE Layered Architecture

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

• FACE 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 51-53 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

Interface Overview

OS Segment Interfaces

Operating System Segment

FACE

O/S

API

s

FACE

Run

time

APIs

FACE

Fra

mew

ork

APIs

Standardized FACE Operating System API Profiles

Standardized FACE Runtime API

Standardized FACE Framework APIs

FACE Operating System(O/S)

FACE Runtimes(RT)

FACE Frameworks

(FW)

No FACE Standardization

of “Bottom side” interfaces

No FACE Standardization of “Bottom side” interfaces

No FACE Standardization of “Bottom-side” interfaces

I/O Services Segment

I/O Service Management Capability

I/O Data Movement Capability

Device Driver Normalization Adaptation Capability

15

53

Driv

er

42

9 D

river

Se

ria

l Driv

er

Oth

er

Driv

ers

Platform Specific Services Segment

I/O Config(XML)

I/O Services Segment

I/O Configuration Data would contain the full specification for each I/O interface.

Standard device drivers based on operating system and hardware of choice.

I/O Interface

Transport Services Segment

FACE Data Model Architecture

• 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

Units of Portability

Portable Component Segment

Operating System

FACE I/O Services

FACE Platform Specific Services

FACE Transport Services

Traditional FACE Application

Mission-Level Capability

Runtime based FACE Application

Mission-Level Capability

Programming Language Runtime

Unit of PortabilityUnit of PortabilityUnits of Portability

Framework based FACE Application

Mission-Level Capability

Application Framework

Units of Portability Dashed Box denotes bundled deliverable set

Framework based FACE Application

Mission-Level Capability

Application Framework

Programming Language Runtime

Must Use

C

A

Must Use

Reference Implementation Guide

Technical Conformance

• Technical– Finalize FACE Standard Edition 2.1– Begin FACE Edition 3.0– Complete Edition 2.1 implementation guidance– Prototype/validate Standard Edition 2.0 (Academia)

• Business Develop Business Guide– Develop Contract Guide – Develop Library Implementation Guidance– Develop Conformance Implementation guidance– Conduct Outreach– Support CORP project and associated Program BCAs

Next Steps

• FACE will enable getting mobile capabilities to the Warfighter faster and at a lower cost

• FACE is being designed through industry and government collaboration

• FACE is addressing the business concerns that have hampered other OA initiatives

• FACE should be considered for any Defense avionics software procurement where reuse is a goal

• FACE and its model for public-private partnership are relevant to many domains, where it goes from here is up to you

Summary

Your systems. Working as one.

BACKUP