FACE Consortium Organization Structure & Group Charters

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
Enabling Access to Sound Archives through Integration, Enrichment and Retrieval WP1. Project Management.
IAEA 1 The IAEA has revised the 1996 Safety Standards 50-C/SG-Q: QA Requirements and Safety Guides Published in 1996 Promotes structure: –Management –Performance.
May 2010 Slide 1 SG Communications Boot Camp Matt Gillmore 03/07/11.
BENEFITS OF SUCCESSFUL IT MODERNIZATION
A Navy Business Initiative Defense Daily OA Summit 12 November 2013 Nickolas H. Guertin, PE Director for Transformation DASN RDT&E
ANSI/EIA A EIA STANDARD Earned Value Management Systems Overview May 2, 2006 NDIA Program Management Systems Committee Walt Berkey, Lockheed.
FACE 101 Robert Matthews NAVAIR Public Release
Smart Grid - Cyber Security Small Rural Electric George Gamble Black & Veatch
Systems Engineering in a System of Systems Context
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
IT Governance and Management
SE 464: Industrial Information systems Systems Engineering Department Industrial Information System LAB 02: Introduction to SAP.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
The topics addressed in this briefing include:
December 3, 2010 SAIF Governance Framework A Brief Update on work to date.
Roles and Responsibilities
Chapter 6 Software Implementation Process Group
MISMO Business and Standards Round-up Fall 2013 Educational Summit & Workshops MISMO Business and Standards Round-up Presenters: Kyle Bensen, MGIC, Chair.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Global Privacy and Information Quality Working Group.
Future Airborne Capability Environment (FACE)
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
SacProNet An Overview of Project Management Techniques.
1 Emergency Management Standards EM- XML Consortium & EM Technical Committee Presentation to Steve Cooper March 18,2003.
Georgia Institute of Technology CS 4320 Fall 2003.
OpenSG Status UCAIug Members Meeting Chris Knudsen – Chair Gary Stuebing – Vice-Chair November 9 th, 2009.
Presents: Information for participants: Your microphone will be muted for the formal presentation. If your audio portion the presentation is not working,
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Configuration Management of Post-Fukushima Regulations CMBG June 2013 David Gambrell Director, Severe Accident Management Southern Nuclear.
United States Department of Justice Achieving Information Interoperability and Business Agility The Justice Reference Architecture:
The DoD Information Enterprise Strategic Plan and Roadmap (SP&R)
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Federal Software Asset Management Initiative Concept of Operations Report to the Executive Steering Committee March 8, 2004 Implementing the President’s.
Developing a Project Management Standard for Your Organization Francine DiMicele, PMP June 08, 2015 NC Piedmont Triad Chapter.
AFLCMC… Providing the Warfighter’s Edge SOSA Industry Day: Working Agendas August 4, 2015.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
OMB Circular A-16 Supplemental Guidance (Endorsed) Ivan DeLoatch, Staff Director Lew Sanford Jr. & Wendy Blake-Coleman NGAC Meeting, February 4, 2009.
Government and Industry IT: one vision, one community Vice Chairs April Meeting Agenda Welcome and Introductions GAPs welcome meeting with ACT Board (John.
CT TEFT 1 November 5, Agenda Introduction Goal of Pilot Tier Piloting Activity to Pilot Role of Connecticut in the pilot Standards and Technologies.
State of Georgia Release Management Training
DEVELOPMENT OF UNIFORM CONTRACTING AND PROCUREMENT POLICIES  Procurement Reform Task Force Recommendation #7  Approach  Key Initiatives  “Go Forward”
Association of Enterprise Architects International Committee on Enterprise Architecture Standards Jan 23, Collaborative Expedition Workshop #57aeajournal.org.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
1 Industry Advisory Council’s Enterprise Architecture Shared Interest Group (IAC EA SIG) Collaborative Approach to Addressing Common Government- Industry.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Building a BA Center of Excellence Gain Momentum...Produce Results!
Overview: Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) Services Support FGDC Coordination Group Meeting 6 February 2007.
May 2010 Slide 1 SG Communications Boot Camp Matt Gillmore 11/1/2010.
Security Methods and Practice Principles of Information Security, Fourth Edition CET4884 Planning for Security Ch5 Part I.
SQA project process standards IEEE software engineering standards
Federal Enterprise Architecture (FEA)
SQA project process standards IEEE software engineering standards
Improving Mission Effectiveness By Exploiting the Command’s Implementation Of the DoD Enterprise Services Management Framework - DESMF in the [name the.
Module 1 IAEA Safety Standards on Management Systems.
ESMF Governance Cecelia DeLuca NOAA CIRES / NESII April 7, 2017
The Open Group Architecture Framework (TOGAF)
By Jeff Burklo, Director
Federal Strategic Sourcing Initiative Government-Wide Wireless Program Industry Day II December 5, 2011.
Web Services Interoperability Organization
WORK STREAM TEAM DELIVERABLES
Executive Sponsor: Tom Church, Cabinet Secretary
Presentation transcript:

FACE Consortium Organization Structure & Group Charters Updated: December 5, 2013

The FACE Consortium Org Chart

FACE Consortium High-Level Charters Technical Working Group (TWG): The charter of the FACE Technical Working Group (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 is technical body responsible for all FACE Consortium technical aspects. The TWG defines the Technical Standard for the FACE Reference Architecture, provides guidance supporting the standard, develops additional support documentation, provides implementation guidance, and defines procedures for FACE Conformance. Business Working Group (BWG): The charter of the FACE Business Working Group (BWG) is to Develop, Implement and Communicate Attractive Industry-Government Business Models that Incorporate the FACE Vision and Mission. - The BWG defines business models to communicate FACE Consortium goals to DoD and Industry leaders and promotes the use of the FACE approach in avionics developments, procurements and upgrades. They also establish requirements for the Library of FACE conformant products and defines the policies for FACE Conformance. Enterprise Architecture (EA) Team: The charter of the EA Team is to Define and develop formal architecture products (artifacts) to create clear, top-level picture of the FACE Enterprise for a wide variety of 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. 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. 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.

Business Working Group Enterprise Architecture FACE BWG Org Chart Business Working Group Chair: Dennis Stevens (Lockheed Martin) Vice Chair: David Boyett (US Army AMRDEC) Enterprise Architecture Steve Davidson (Raytheon) FACE / UCS Alignment Bill Antypas (NAVAIR) Business Model Subcommittee Gabriel Flores (Northrop Grumman) Conformance Subcommittee Steve Goetz (US Army AMRDEC) Library Subcommittee David Boyett (US Army AMRDEC) Outreach Subcommittee Chip Downing (Wind River)

FACE BWG Subcommittee Charters BWG Subcommittees: Business Model (BMS): The charter of the BMS is to evaluate, develop, and disseminate business models that will support the successful development, delivery, maintenance and conformance of components and systems to the FACE Technical Standard. The scope of the BMS 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. The BMS shall use all available resources within Government, Industry and Academia to accomplish these stated goals. Conformance: The charter of the Conformance Subcommittee is to develop the FACE Conformance Program which will include a set of plans, procedures, and certification environments, with roles and responsibilities for participants, to Certify the Software Products that have applied for FACE Conformance Certification Library: The charter of the FACE Library Subcommittee is to define the operational, functional, and physical requirements for identification, storage, management, and distribution of FACE conformant products, and develop a plan to enable the FACE Consortium to implement these requirements. Outreach: The charter of the Outreach Subcommittee is to promote the uptake and support of the FACE approach and the FACE Consortium by developing and coordinating messaging, outreach efforts, and events.

FACE TWG Org Chart TECHNICAL WORKING GROUP Chair: Robert Sweeney (NAVAIR) Vice Chair: Kirk Avery (Lockheed Martin) BWG Support (Robert Sweeney/Kirk Avery/Dr. Bubba Davis/Marcell Padilla) Standards Subcommittee (Robert Sweeney/ Kirk Avery/David Bowes) EA Support (Kirk Avery/Jeff Hegedus/Robert Sweeney) Edition 1.0 Revisions Edition 2.1 Revisions Edition 3.0 Revisions FACE Introduction Conformance Library Configuration (Joel Sherrill/Joe Dusio) Data Model (Jeff Hegedus/Bill Kinahan) Reference Implementation Guide (Kirk Avery/David Bowes) Conformance Verification Matrix (Dr. Bubba Davis/Marcell Padilla) Graphics (Paul Jennings/Levi Van Oort) Airworthiness Guidance (George Romanski/Glenn Carter) General Enhancement (Robert Sweeney/Brett Caspers Transport (Kirk Avery/Bill Antypas) Security (Joe Neal/Scott Wigginton)

FACE TWG Subcommittee Charters TWG Subcommittees: Data Model and Data Definition: The charter of the Data Model Subcommittee is to define configuration data, messages and requirements for transient and persistent data models and meta data in the FACE architecture, guided by existing standards and methodologies. Reference Implementation: The charter of the Reference Implementation Subcommittee is to produce a FACE Reference Implementation Guide providing implementation and integration guidance and development scenarios. Security Team (ST): The charter of ST 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 Implementation Guide as well as reviewing other sections of these documents for consistency and content relative to security. The ST is encouraged to participate in all FACE technical subcommittee and wider team activities and provide feedback, guidance and recommendations on the security impacts or challenges posed. The ST will be ITAR compliant. The FACE Technical Standard and Implementation Guide will remain public distribution documents; the FACE ST will capture any restricted information in separate appendices.

FACE TWG Subcommittee Charters TWG Subcommittees, Cont’d: Verification Matrix: The charter of the Verification Matrix Subcommittee is to analyze the requirements of the FACE standard and develop a Conformance Verification Matrix for each edition of the FACE Technical Standard. The matrix is intended to identify methods and artifacts needed for FACE conformance verification. This subcommittee will also publish a Matrix User's Guide for use by Verification Authorities (VAs) as well as software suppliers. This subcommittee will provide recommendations for Conformance Test Suite requirements. 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 Technical Working Group (TWG) work products. The subcommittee will harmonize with the Configuration, Data Model, and Health Monitoring/Fault Management (currently inactive) subcommittees to eliminate inconsistencies inhibiting implementation. Configuration: The charter of the Configuration Subcommittee is to identify, scope, and document the required configuration capabilities and how they relate to each FACE profile and segment. Given these capabilities, identify and document configuration interfaces and activities as well as any impact on the FACE architecture. Tagline: “Portable Configuration for Portable Components”

FACE TWG Subcommittee Charters TWG Subcommittees, Cont’d: Software Safety: The charter of the Software Safety Subcommittee is to produce the guidance document associated with software development process and production of airworthy software using the FACE standard. 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 modification of the FACE Technical Standard for all changes that will touch more than one segment or subcommittees. The subcommittee coordinates changes between multiple subcommittees and is responsible for enhancements and modifications that are not addressed by the specialized subcommittees. Health Monitoring Fault Management (HMFM - currently inactive): The charter of the HMFM Subcommittee is to scope, identify and capture the required HMFM capabilities and how they relate to each FACE profile. Given these capabilities, they identify and document HMFM interfaces, associated data modeling and impact of HMFM on the FACE architecture at large.