Group Charters

Advisory Board: The charter of the Advisory Board is to provide guidance and advice to the consortium.

Subcommittees: The Subcommittees develop specific content and deliverables as directed by Business and Technical Working Groups.

  • Enterprise Architecture (EA) Standing Committee Team: The charter of the EA Standing Committee is to define and develop formal architecture products (artifacts) to create a clear, top-level picture of the FACE Enterprise for a wide variety of FACE Consortium and outside audiences, address the FACE role in the context of related initiatives and programs, and ensure internal consistency across the FACE Business and Technical architecture.
    • EA 25: The charter of the EA Air Worthiness Subcommittee is to address Air Worthiness considerations across the FACE Technical Standard. The purpose of the subcommittee is to ensure that FACE conformant software, associated artifacts, and the process to produce them (1) contribute towards evidence of Air Worthiness where possible, explicitly citing common requirements, processing and guidance, (2) address both commonality and variance at a high level, (3) and do not preclude the ability to meet airworthiness requirements.
  • Business Working Group (BWG): The charter of the FACE Business Working Group (BWG) is to develop, implement, and communicate Industry-Government business practices and procedures. These business practices and procedures guide the implementation of FACE contracting, conformance approval practices, and registry and repository processes that incorporate the FACE vision and mission. The FACE Business strategy is described by the business policies and procedures for establishing and maintaining a marketplace of FACE conformant software components that can be integrated into multiple platforms. The BWG defines these business practices to communicate FACE Consortium goals to DoD and industry leaders and promote the use of the FACE approach in avionics developments, procurements, and upgrades.
    • Business Strategy (BSS): The charter of the Business Strategy Subcommittee (BSS) is to evaluate, develop, and disseminate business practices that will support the successful development, delivery, maintenance, and conformance of components and systems to the FACE Technical Standard. The scope of the BSS effort includes the examination of requirements for, and subsequent modeling of, government-to-government, government-to-contractor, and contractor-to-contractor interactions in the execution of contractual obligations utilizing the FACE environment.
    • Conformance: The charter of the Conformance Subcommittee is to 1. Define and sustain the FACE Conformance Program to include a set of plans, policies, and procedures, defining the roles and responsibilities of participants, for certifying software products submitted for FACE Conformance Certification. 2. Provide outreach, education, and guidance regarding the FACE Conformance Program to participants and other interested parties.
    • Outreach: The BWG Outreach Subcommittee promotes the adoption and support of the FACE Technical Standard and business approach. These efforts include developing and coordinating messaging, education, events, and outreach efforts for a global aerospace and defense audience.
  • Technical Working Group (TWG): The FACE Technical Working Group (TWG) is the body responsible for all FACE Consortium technical aspects. The charter of the TWG is to identify open standards where such exist, define standards that do not yet exist and provide guidance for using these standards to achieve portability of software-based capabilities across multiple avionics platforms. The TWG defines the Technical Standard for the FACE Reference Architecture, provides guidance supporting the standard, develops additional support documentation, provides implementation guidance, and supports the development of procedures for FACE conformance. The TWG also develops technical products associated with the FACE Enterprise such as the FACE Shared Data Model, Reference Implementation Guide, and Conformance Verification Matrix and User’s Guide.
    • Security (ST): The charter of Security Subcommittee is to focus on security-specific considerations associated with avionics systems and software. The subcommittee is tasked with providing security-specific input for the FACE Technical Standard and Reference Implementation Guide as well as reviewing other sections of these documents for consistency and content relative to security. The FACE Technical Standard and Reference Implementation Guide will remain public distribution documents; the Security Subcommittee will capture any restricted information in separate appendices.
    • Conformance Verification Matrix: The charter of the Conformance Verification Subcommittee is to serve as to serve as the TWG focal point for the FACE Conformance Program, including:
      • Analyze the requirements of each Edition of the FACE Technical Standard and develop a Conformance Verification Matrix (CVM) specific to that edition; including segment allocation, verification methods, potential artifacts needed for inspection, and identification of conditional applicability.
      • Provide recommendations for Conformance Test Suite requirements and perform technical evaluations upon upgrades to adopted versions of the Conformance Test Suite.
      • In coordination with the Business Working Group, publish and maintain the Conformance Certification Guide and facilitating the Conformance Overview.
      • Serve as FACE Verification Authority (VA) Community of Practice (CoP) representation in the FACE Consortium, and provide Technical Working Group (TWG) oversight to ensure published VA CoP guidance is in alignment with each Edition of the FACE Technical Standard.
  • Transport: The charter of the FACE Transport Subcommittee is to consider modifications to the Transport Services Segment (TSS) sections of the FACE Technical Standard and other TWG work products. The subcommittee will harmonize with the Configuration, Data Model, and Health Monitoring/Fault Management Subcommittees to eliminate inconsistencies inhibiting implementation.
  • Software Safety: The charter of the Software Safety Subcommittee is to produce the guidance documentation associated with software development processes used to produce airworthy certification evidence using the FACE Technical Standard. Of note, this subcommittee is not responsible for producing documentation that defines the airworthiness requirements for software products, nor should the reader infer that following the FACE Technical Standard will qualify the software as airworthy. The purpose of the subcommittee is to ensure that FACE conformant software and artifacts don’t preclude the ability to meet airworthiness requirements.
  • Graphics: The charter of the Graphics Subcommittee is to provide a definition of graphical services and guidance on their implementation, utilizing guidance from existing standards and methodologies.
  • General Enhancement: The charter of the General Enhancement Subcommittee is to be responsible for the modification of the FACE Technical Standard for all changes that will touch more than one segment or subcommittee. The subcommittee coordinates changes between multiple subcommittees and is responsible for enhancements and modifications that are not addressed by the specialized subcommittees.
  • Standard: The Standard Subcommittee is comprised of the TWG Chair, Vice Chair, all subcommittee leads and co-leads, plus an additional industry subject matter expert to represent the Operating System (OS) viewpoint. Their role is to coordinate subcommittee activities to ensure the charters of the TWG and Subcommittees are met.
  • Domain Interoperability Working Group (DIOG): The FACE Data Architecture Working Group (DAWG) is the body responsible for all FACE Data Architecture and Data Model aspects. The charter of the DAWG is to determine the elements of a Data Architecture, define those elements, identify applicable open standards where they exist, define standards where none exist, and provide guidance for using these standards to achieve interoperability at the data level. The DAWG defines the Data Architecture standard and the relevant sections of the FACE Technical Standard (working with the TWG), provides guidance supporting the standards, develops additional support documentation, provides implementation guidance, and supports the development of procedures for FACE conformance. The DAWG may also develop technical products associated with the FACE Enterprise such as content for inclusion in the FACE Shared Data Model.
    • Language: The charter of the Data Architecture Language Subcommittee is to define the methodology for capturing data syntax and semantics for the FACE architecture, guided by existing standards and methodologies. The focus is on data exchanged by software components developed to the FACE Technical Standard. This subcommittee is responsible for all artifacts that are included in a FACE standard.
    • Shared Data Model: The charter of the Shared Data Model Subcommittee is to review SDM CRs with submitters, provide recommendations to the Shared Data Model Configuration Control Board (SDM CCB), to develop pertinent SDM content, and to provide direction to Software Suppliers submitting SDM CRs.
    • Guidance: The charter of the Data Architecture Guidance Subcommittee is to develop guidance documents, document best practices, and provide Software Suppliers with the information necessary to adopt the FACE Data Architecture. The Data Architecture Guidance Subcommittee is also responsible for alignment activities and evaluation of other data modeling approaches.
  • FACE UCS Alignment Liaison: The charter of the FACE UCS Alignment Liaison is to participate in both UCS and FACE meetings, and report on areas where working groups can align and are collaborating to leverage each others’ business and technical products.
  • Integration Workshop Standing Committee: Collaborate with the BWG/TWG to establish and enforce technical entrance criteria for public FACE Consortium sanctioned Technical Interchange Meetings (TIM) and similar events & Discover, evaluate, and produce FACE reference implementation examples and facilitate adoption and publication of those reference examples.
  • Standards Alignment Standing Committee: The charter of the Standards Alignment Standing Committee (SAS-C) is to align to relevant standards development efforts to increase FACE adoption opportunities.
  • Course Accreditation Standing Committee: The charter of the Course Accreditation Standing Committee to advise on the following related to training accreditation

1.What falls under the accreditation process?

2.Who are the intended audiences?

3.What are the syllabus and learning outcomes?

4.What boundaries exist with respect to the training process?

5.What accreditation process will we follow?

6.What certification does the trainee get?

7.What is the timeline and criteria for rolling out the process?

 

Sponsor-Level Members

sponsors - Airforce LCMC sponsors - Boeing sponsors - Lockheed Martin sponsors - Naval Air Systems Command sponsors - Program Executive Office Aviation sponsors - Collins Aerospace