Transcript Slide 1

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
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
Scope: All of Naval Aviation
UNCLASSIFIED
Solution - FACE
• Modern processing environment
– 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
Page # 3
UNCLASSIFIED
FACE Implementation
Flight Control
Surfaces
Flight Control
Systems
Mission
Critical
Sensors
Networks
External Interfaces
OFP
FACE
Flight Controls
Displays
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
Page # 4
UNCLASSIFIED
FACE Modular Architecture
Partition
OFP
Partition
Partition
Partition
Partitioned: ARINC 653
time and space
Partition
Situational
StrikeLinkPartition
FliteScenePartition Future Partition
Partition
Partition
Awareness
Digital CAS
Map
New
FusionSituational
Application
Application
Application
Partition
Partition
Partition
Partition
Partition
Engine
Awareness
OFP
FliteScene
Spare
StrikeLink
ApplicationFusion
Situational
OS
OS
Awareness
Engine
OFP
OS
StrikeLink
OS
OS
Fusion
Engine
FACE Middleware
Components
OS
OS
Device Drivers
OS
FliteScene
OS
OS
Spare
OS
FACE Middleware
Components
OS
OS
OS
Separation Kernel
FACE Middleware Components
BIT /Terminal
OS
BSP
Separation Kernel
Device Drivers
Device Drivers
BIT /Terminal
Separation Kernel
BIT /Terminal
BSP
BSP
Applications, Scalable, Independent Partitions,
Supports Modern Security Environment
...
Scalable
Page # 5
UNCLASSIFIED
Modular Open System
Approach (MOSA)
•
FACE provides teeth to the five key principles of MOSA
UNCLASSIFIED
– 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
UNCLASSIFIED
FACE Consortium
• The Open Group manages the Consortium
–
–
–
–
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
Page # 8
UNCLASSIFIED
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
FACE Consortium - A Collaborative Approach
to define a Common Open Standard
Page # 9
UNCLASSIFIED
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
FACE - Truly Open Architecture Achieved
Page # 10
UNCLASSIFIED
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
FACE - CRITICAL to delivering Future Airborne Capabilities
Application across T/M/S maximizes benefits
Page # 11
UNCLASSIFIED
Questions ?
Mike Williamson, PMA209E
Mission Systems
Deputy Program Manager
[email protected]
(301)757-9441
Bob Matthews, PMA209EA
Mission Systems
Deputy Capability Lead
[email protected]
PMA209 Vision: where DoD organizations insist upon common,
(301) 995-4971
capability-centric avionics systems for their inherent value,
interoperability, and cost-effectiveness.
Page # 12
UNCLASSIFIED
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
UNCLASSIFIED