FACE Architecture Executive Summary


Published on

Presented at the 2013 MBSE Technical Forum in Huntsville, Alabama.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

FACE Architecture Executive Summary

  1. 1. Your systems. Working as one.ArchitectureExecutive SummaryWilliam AntypasChief Consulting EngineerFACETM Standards Alignment ChairTSS SC ChairJune 20, 2013FACE™ is a trademark of The Open GroupNAVAIR Public Release 2012-1233Distribution Statement A"Approved for public releasedistribution is unlimited”
  2. 2. Executive Summary Agenda– FACE Strategy– FACE Business Model– FACE Technical Standard
  3. 3. Your systems. Working as one.Executive Overview
  4. 4. COEs and Mobile Computing• Advances in mobile productivity owe much to Common OperatingEnvironments• A Smartphone example highlights the benefits of COEs and givescontrast to the DoD Avionics domain• The FACE Technical Standard establishes a COE for DoD AvionicsCommercial MilitaryTM
  5. 5. • 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 CapabilitiesFighterBomberHelicopterCargoUASNavCommSA…
  6. 6. • DoD Airborne systems are typically developed for a unique set ofrequirements 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 ofsoftware reuse across different programs– Aviation community has not adopted a common set of OA standards sufficient toallow the reuse of software components across the DoD fleet– Aviation community has failed to enforce conformance to any existing openstandards that are in use– Platform PMAs are not funded to assume cost or schedule risk of multi-platformrequirementsWhy FACE?The Future Airborne Capability Environment (FACE) is an approach designed asa response to the DoD aviation community’s problems
  7. 7. Why a FACE Consortium?A consortium formed under theauspices of The Open Group is a“Voluntary Consensus StandardsBody” 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 consortiumparticipation by US agencies• Foundation of consortium statusunder National CooperativeResearch and Production Act(NCRPA)SteeringCommitteeEnterpriseArchitectureAdvisoryBoardFACE / UCSAlignmentTechnicalWorkingGroupBusinessWorkingGroup600+IndividualParticipantsConsortium Structure
  8. 8. The FACE Consortium was formed in 2010 by The Open GroupSponsors:•Lockheed Martin•Naval Air Systems Command (NAVAIR)•US Army PEO Aviation•Rockwell CollinsAssociates:• AdaCore• Aitech Defense Systems• Barco Federal Systems• Brockwell Technologies• CALCULEX• Carnegie Mellon SEI• Chesapeake TechnologyInt’l.• CMC Electronics• CoreAVI• CTSi• Curtiss-Wright ControlsDefense Solutions• DDC-I• DornerWorks• Draper Laboratory• Esterel Technologies• FMS Secure Solutions• GE Intelligent Platforms• Johns Hopkins AppliedPhysics Lab• L-3 Communications• LDRA Technology• LynuxWorks• Objective InterfaceSystems• Physical Optics Corp.• Presagis• QinetiQ North America• Real-Time Innovations• Richland Technologies• Stauder Technologies• Support Systems Associates• Symetrics Industries• Thomas ProductionCompany• Tresys Technology• TTTech North America• Tucson Embedded Systems• Verocel• ViaSat• Zodiac Data SystemsFACE Consortium MembersPrincipals:• ATK• BAE Systems• Bell Helicopter• Boeing• Elbit Systems ofAmerica• 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 AerospaceSystems• Wind River
  9. 9. 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 26January 2012– Edition 1.0 published and available at the following link on The OpenGroups Bookstore:– http://www.opengroup.org/bookstore/catalog/c122.htm– Edition 2.0 released – March 2013– https://www2.opengroup.org/ogsys/catalog/c137
  10. 10. How FACE is Different From Previous DoDOA efforts• DoD worked with The Open Group to establish the FACE consortium suchthat each Service and Industry members had an equal voice in determiningthe 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 theTechnical 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
  11. 11. Your systems. Working as one.Business Overview
  12. 12. BUSINESS WORKINGGROUP(BWG)BusinessModelLibrary OutreachTWGSupportBWG StructureConformance
  13. 13. 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
  14. 14. StakeholdersAcquisitionGuidanceScenariosIP LicensingFACEProducts & ServicesDFARSImpactsMajor Business and Policy IssuesThat FACE Wrestles With
  15. 15. FACE Contract Guide• Suggested Request For Proposal Language– Contract Requirements– Evaluation Criteria• Suggested Contract Language– Performance– Incentive– Fee
  16. 16. FACE Conformance Policy
  17. 17. FACE Repository/Library
  18. 18. Your systems. Working as one.Technical Overview
  19. 19. TECHNICALWORKING GROUP(TWG)SEGMENTLEADSData Modeland DataDefinition• Configuration Model• Data Model• Health Monitor DataModel• Data DefinitionReferenceImplementationGuide• Technical ArchitectureViews• Organization• Safety/Security• Implementation andintegration• Language runtimes andnetwork librariesConformanceVerificationMatrix• Edition1.0 Revisions• FACE IntroductionBWGSupport• Conformance• RepositoryTWG Structure• Develop conformanceverification matrix• Define conformancetest suiterequirements• Develop matrix user’sguideTransportServicesSegment• TSS API• TSS Configuration
  20. 20. • 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 PracticesFACE Edition 2.0 Technical Deliverables
  21. 21. FACE Technical StrategyWar-Fighting PlatformExisting Computer Hardware New Computer HardwareFACE Computing EnvironmentFACE ComputingEnvironmentPortableFACEapplicationPortableFACEapplicationPortableFACEapplicationAvionics NetworksThe FACE strategy is to create a software environment on the installedcomputing hardware of DoD aircraft (a.k.a. platforms) that enables FACEapplications to be deployed on different platforms with minimal to no impactto the FACE application.
  22. 22. Eliminates Barriers to Portability• Truly portable applications requirecommon open standards atmultiple layers in the architectures• Prevents lock-in and improvescompetition throughout supplychain• Uniform application ofcommon open standardsacross DoD aviation neededto break “Cylinders ofExcellence”TraditionalApplicationPresentationConcerns(Display H/W & S/W,headless transports, cursordevices, etc.)Business Logic Concerns(Many MIL-STDs, FMF,RNP/RNAV, SituationalAwareness, etc.)I/O Concerns(Interface Cards, RadioICDs, Networks, OFPs,etc.)Other cooperating and/orsupporting applicationsSPECIFICDisplay Hardware &SoftwareSPECIFICRadios, Networks &softwaresubsystemsTight Couplinghere is a barrierto portabilityTight Couplinghere is a barrierto portabilityTight Couplinghere is a barrierto portabilitySPECIFICOperating System & DriversTight Couplinghere is a barrierto portabilityPortable FACEApplicationPresentationConcerns(Display H/W & S/W,headless transports,cursor devices, etc.)Business LogicConcerns(Many MIL-STDs, FMF,RNP/RNAV, SituationalAwareness, etc.)I/O Concerns(Interface Cards, RadioICDs, Networks, OFPs,etc.)Other cooperating and/orsupporting applicationsSPECIFICDisplay Hardware &SoftwareSPECIFICRadios, Networks &softwaresubsystemsTight Coupling hereno longer impactsapplicationportabilityAdaptationLayerAdaptationLayerAdaptationLayerSPECIFICOperating System & DriversNo longer a barrier toportability due toselection of operatingsystem standardsbeing present at allcomputingenvironmentsImmutable abstractioninterfaces enableportability as tightcoupling is moved outof the “application”
  23. 23. FACE Layered Architecture
  24. 24. FACE Architectural Segments• FACE Portable ComponentsSegment– Portable Applications– Portable Common Services• Transport Services Segment• Platform Specific ServicesSegment– Platform Device Services– Platform Common Services– Graphics Services• I/O Services Segment• Drivers• Operating System Segment
  25. 25. • FACE expands on the MOSA and OA principles• Use of abstraction layers at Key Interfaces to diminishthe need for new standards– O/S interface (C) focused on POSIX profile 51-53 and ARINC653– I/O abstraction interface (B) based on common I/O API andmessaging interface– Standardized Transport abstraction interface (A)• Defined to support POSIX, ARINC 653, DDS, CORBA• Extensible and Flexible for integration of future transportmechanismsInterface Overview
  26. 26. OS Segment InterfacesOperating System SegmentFACEO/SAPIsFACERuntimeAPIsFACEFrameworkAPIsStandardizedFACE OperatingSystem APIProfilesStandardizedFACE RuntimeAPIStandardizedFACEFramework APIsFACE OperatingSystem(O/S)FACE Runtimes(RT)FACEFrameworks(FW)No FACEStandardizationof “Bottom side”interfacesNo FACEStandardizationof “Bottom side”interfacesNo FACEStandardizationof “Bottom-side”interfaces
  27. 27. I/O Services SegmentI/O Service Management CapabilityI/O Data Movement CapabilityDevice Driver NormalizationAdaptation Capability1553Driver429DriverSerialDriverOtherDriversPlatform Specific Services SegmentI/O Config(XML)I/O ServicesSegmentI/O Configuration Data wouldcontain the full specification foreach I/O interface.Standard device driversbased on operating systemand hardware of choice.I/O Interface
  28. 28. Transport Services Segment
  29. 29. FACE Data Model Architecture• Three levels to the primary data and message models aligned with ideas fromthe Object Management Group’s (OMG) Model Driven Architecture ™• The addition of the Component (UoP) Model allows us to tie components to themessages and data elements in the Platform Model• Supports definition and potentially generation of code and other artifacts
  30. 30. Units of PortabilityPortable Component SegmentOperatingSystemFACE I/O ServicesFACE Platform Specific ServicesFACE Transport ServicesTraditional FACEApplicationMission-LevelCapabilityRuntime basedFACE ApplicationMission-LevelCapabilityProgrammingLanguage RuntimeUnit of PortabilityUnit of PortabilityUnits of PortabilityFramework basedFACE ApplicationMission-LevelCapabilityApplicationFrameworkUnits of Portability Dashed Boxdenotes bundleddeliverable setFramework basedFACE ApplicationMission-LevelCapabilityApplicationFrameworkProgrammingLanguage RuntimeMust UseCAMust Use
  31. 31. Reference Implementation Guide
  32. 32. Technical Conformance
  33. 33. • 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 BCAsNext Steps
  34. 34. • FACE will enable getting mobile capabilities to theWarfighter faster and at a lower cost• FACE is being designed through industry and governmentcollaboration• FACE is addressing the business concerns that havehampered other OA initiatives• FACE should be considered for any Defense avionicssoftware procurement where reuse is a goal• FACE and its model for public-private partnership arerelevant to many domains, where it goes from here is up toyouSummary
  35. 35. Your systems. Working as one.BACKUP