Transcript FACE brief for SUMO

FACE 101
Robert Matthews
NAVAIR Public Release 2013-920
Distribution Statement A
"Approved for public release
distribution is unlimited”
Air Combat Electronics (PMA209)
FACE Integrated Project Team Lead (AIR-1.3.1.5)
FACE Steering Committee Chair
Robert Sweeney
Air Combat Electronics (PMA209)
FACE Lead Engineer (AIR-4.5.3.2)
FACE Technical Working Group Chair
FACE™ is a Trademark of The Open Group
Executive
Overview
FACE™ is a Trademark of The Open Group
Transitioning to Open
Interface Architecture
3
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Overlap of Capabilities
Helicopter
Bomber
Fighter
Nav
Comm
SA
…
Cargo
UAS
• 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!)
4
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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 multiplatform requirements
The Future Airborne Capability Environment (FACE) initiative is an approach
designed as a response to the DoD aviation community’s problems
5
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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
•
•
•
•
6
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
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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 A119 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)
7
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
FACE Consortium Members
Sponsor Level Member Organizations
• Lockheed Martin
• Naval Air Systems Command (NAVAIR)
•
•
•
•
•
• US Army PEO Aviation
• Rockwell Collins
Principal Level Member Organizations
ATK
BAE Systems
Bell Helicopter
Boeing
Elbit Systems of America
•
•
•
•
•
GE Aviation Systems
General Dynamics
Green Hills Software
Harris Corporation
Honeywell Aerospace
•
•
•
•
•
IBM
Northrop Grumman
Raytheon
Sierra Nevada Corp.
Sikorsky Aircraft
•
•
•
•
Textron Systems
US Army AMRDEC
UTC Aerospace Systems
Wind River
Associate 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 • Cobham Aerospace
America
Communications
• Esterel Technologies
• L-3 Communications
• Symetrics Industries
• Exelis Inc.
• LDRA Technology
• Thomas Production Company
• Fairchild Controls
• LynuxWorks
• Tresys Technology
• GE Intelligent Platforms
• Mobile Reasoning, Inc
• TTTech North America, Inc.
• Avalex Technologies
• Barco Federal Systems
• Brockwell Technologies
• CALCULEX
• Carnegie Mellon Univ. –
Software Engineering
Institute
• CERTON Software, Inc.
• Core Avionics & Industrial
Inc.
• CTSi
• Curtiss-Wright Controls
Defense Solutions
• DDC-I
• DornerWorks
• Draper Laboratory
• General Atomics Aeronautical •
Systems, Inc.
•
• Howell Instruments, Inc.
•
• Johns Hopkins Univ. - APL
•
• Kaman Precision Products
•
Physical Optics Corp.
• Tucson Embedded Systems
Presagis
• US Army Electronic Proving
Ground
QinetiQ North America
Real-Time Innovations
RichlandTechnologies
The FACE Consortium was formed in 2010 by The Open Group
8
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
• Verocel
• Zodiac Data Systems
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
9
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Published FACE Documentation
• FACE Technical Standard Edition 1.0
– http://www.opengroup.org/bookstore/catalog/c122.htm
• Technical Corrigendum for FACE Edition 1.0
– https://www2.opengroup.org/ogsys/catalog/U131
• FACE Technical Standard Edition 2.0
– Including Data Model and Reference Implementation Guide
– www.opengroup.org/bookstore/catalog/c137.htm
• FACE Conformance Policy
– https://www2.opengroup.org/ogsys/catalog/X1303
• FACE Conformance Authorities Plan
– https://www2.opengroup.org/ogsys/catalog/X1302
• FACE Business Guide, Version 1.1
– http://www.opengroup.org/bookstore/catalog/g115.htm
10
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Major Business & Policy Issues
FACE Initiative Wrestles With
Impacts
IP Licensing
Stakeholders
Scenarios
Acquisition
Guidance
FACE
Products & Services
DFARS
11
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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
• Establish initial capabilities
– 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
12
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Technical
Overview
FACE™ is a Trademark of The Open Group
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.
War-Fighting Platform
Portable
FACE
application
Portable
FACE
application
Portable
FACE
application
FACE Computing Environment
FACE Computing
Environment
Existing Computer Hardware
New Computer Hardware
Avionics Networks
14
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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
15
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Eliminates Barriers to Portability
Tight Coupling
here is a barrier
to portability
• Truly portable applications require
common open standards at
multiple layers in the architectures
• Prevents lock-in and improves
competition throughout supply
chain
Traditional
Application
SPECIFIC
Display Hardware &
Software
Presentation
Concerns
(Display H/W & S/W,
headless transports, cursor
devices, etc.)
Other cooperating and/or
supporting applications
Tight Coupling
here is a barrier
to portability
SPECIFIC
Radios, Networks &
software
subsystems
Business Logic Concerns
(Many MIL-STDs, FMF,
RNP/RNAV, Situational
Awareness, etc.)
I/O Concerns
(Interface Cards, Radio
ICDs, Networks, OFPs,
etc.)
Portable FACE
Application
Tight Coupling
here is a barrier
to portability
SPECIFIC
Display Hardware &
Software
Presentation
Concerns
(Display H/W & S/W,
headless transports,
cursor devices, etc.)
Adaptation
Layer
Business Logic
Concerns
Tight Coupling
here is a barrier
to portability
(Many MIL-STDs, FMF,
RNP/RNAV, Situational
Awareness, etc.)
SPECIFIC
Operating System & Drivers
• Uniform application of
common open standards
across DoD aviation needed
to break “Cylinders of
Excellence”
16
http://www.opengroup.org/face
SPECIFIC
Radios, Networks &
software
subsystems
Distribution Statement A: Approved for Public Release
2013-920
Other cooperating and/or
supporting applications
Adaptation
Layer
Tight Coupling here
no longer impacts
application
portability
I/O Concerns
(Interface Cards, Radio
ICDs, Networks, OFPs,
etc.)
Immutable abstraction
interfaces enable
portability as tight
coupling is moved out
of the “application”
Adaptation
Layer
SPECIFIC
Operating System & Drivers
No longer a barrier to
portability due to
selection of operating
system standards
being present at all
computing
environments
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
17
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
FACE Architecture Example Block Diagram
18
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Standardization and Constraint
on UoP Interfaces
19
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Transport Services Segment
20
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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
21
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Transport Services API Data
Model Definition
22
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
FACE Architecture - Generic
Partitioned View
Standard
Transport
interfaces
Standard
OS
interfaces
23
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Next Steps
• Technical
 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
24
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
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
–
–
–
–
–
–
25
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
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Page
FACE Technical Standard, Edition
2.0 Technical Enhancements
• FACE Technical Standard Edition 2.0
– 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
26
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Future FACE Standards
• FACE Edition 2.1
–
–
–
–
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
–
–
–
–
–
–
–
–
27
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
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Page
TWG Structure
TECHNICAL WORKING
GROUP
Chair: Robert Sweeney
(NAVAIR)
Vice Chair: Kirk Avery
(Lockheed Martin)
Standards
Subcommittee
(Robert Sweeney/ Kirk
Avery/David Bowes)
•
•
•
•
Data Model
(Jeff Hegedus/Bill
Kinahan)
Airworthiness
Guidance
(George
Romanski/Glenn
Carter)
28
EA Support
(Kirk Avery/Jeff
Hegedus/Robert
Sweeney)
Edition 1.0 Revisions
Edition 2.1 Revisions
Edition 3.0 Revisions
FACE Introduction
Configuration
(Joel Sherrill/Joe
Dusio)
http://www.opengroup.org/face
BWG Support
(Robert
Sweeney/Kirk
Avery/Dr. Bubba
Davis/Marcell
Padilla)
Reference
Implementation
Guide
(Kirk Avery/David
Bowes)
General
Enhancement
(Robert
Sweeney/Brett
Caspers
• Conformance
• Library
Conformance
Verification
Matrix
(Dr. Bubba
Davis/Marcell
Padilla)
Transport
(Kirk Avery/Bill
Antypas)
Distribution Statement A: Approved for Public Release
2013-920
Graphics
(Paul Jennings/Levi Van
Oort)
Security
(Joe Neal/Scott
Wigginton)
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
29
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
BACKUP
FACE™ is a Trademark of The Open Group
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 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
31
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Examples of Application
Packaging
33
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Open Architecture Requirement
• DoD Directive 5000.1
– “E1.1.27. 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 5000.2E
– “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
–
–
–
–
34
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
http://www.opengroup.org/face
Distribution Statement A: Approved for Public Release
2013-920
Page