Enabling Information Sharing through Common Services Flight Information Exchange Model (FIXM) An Overview Presented To: AT Information Exchange Conference Presented By: Midori Tanino, FAA Date: August 31, 2011
Introduction • The emerging Flight Information Exchange Model (FIXM) is becoming the enabling standard for global interoperability for flight-related data • This presentation will show the origins of FIXM, its current status, future plans, and ways you can participate in its evolution
Agenda • Standardization of Flight Data • Flight Object Data Dictionary • Flight Data Modeling • Engineering Needs • Unambiguous flight identification: GUFI • Flight Data custody • Implementation and NextGen • Demonstrations • Past Experiences • Current and future needs • How you can get involved
Flight Information Challenge Challenges Our Approach • Flight Data is named and • Standardize Flight Data defined differently in names and definitions; different domains provide a globally unique interpretation • Investigate solutions that • Flight Data is exchanged enable the exchange of mostly through tightly flight data in flexible, coupled, point-to-point manageable, discoverable, interfaces and secure ways
Standardization starts with creating a Data Dictionary • FAA developed a ASDE-X tracking data ASDE-X TMA Data Dictionary (DD) Flight Plan information CMS messages Metering data as a census of the CDM messages Airspace EDCTs EDCT / Sub most common flight- Host / ERAM CMS messages User messages ADL files ASDI data related data: Flight schedules • Existing NAS point-to- point interfaces (e.g., Flight Flight Plan ATS messages OAG TFMS schedules information Common Message Set, ASDI). TFM data Int’l ANSP ATOP • Interfaces to other Flight Progress information ANSPs (e.g., JCAB) Hazardous Cargo WebOPSS • New data elements Package Security (e.g., security)
DD was developed iteratively • Identified and prioritized Data Elements • Documented their definition, format, and meaning • Validated the accuracy of the documented Data Elements through reviews by the FO Working Group, Subject Matter Experts from a variety of domains, international collaborators 10/2010 2/2012 6/2010 6/2011 6/2012 Versions 1.0 thru 1.7 Versions 2.0 thru 2.4 Batch 1 Batch 2 Batch 3 110 Data Elements 81 Data Elements ASDE X ASDE X ADL Files ADL Files ATOP ATOP ASDI CTOP ASDI CTOP ERAM ERAM CDM Messages ERAM CDM Messages ERAM Hazardous Cargo Hazardous Cargo CMS Fleet Prioritization CMS Fleet Prioritization FlXM ICAO 2012 Flight Plan ICAO 2012 Flight Plan GUFI Security GUFI Security 0.3 Security Security ICAO Flight Plan TFDM ICAO Flight Plan TFDM TMA TMA Int’l TFM Data Exchange Int’l TFM Data Exchange WebOPSS WebOPSS Total ≈ ≈ 191 Data Elements Total ≈ ≈ 191 Data Elements ≈ ≈ ≈ ≈ * 327 comments have been received throughout the development of the FODD
Added structure with Ontology and Data Modeling • A Flight Object Ontology was developed, based on the DD. This ontology formalizes the definitions of AIXM FIXM WXXM Data Elements and the relationships between them • Conceptual and logical Flight Data Models were NAS-EA created • The models were harmonized with similar models developed by the NAS Enterprise Architecture team ERAM Governance Bodies TFMS TFDM Individual Core Terminal TFMS ERAM Other Stakeholder Extensions Extensions Extensions Extensions Organizations FIXM ANSP I D FAA Observations & Measurements Flight Object Model (FIXM) S A FOC ISO 19130 and others ISO / OGC ISO 19107 (Spatial), ISO 19108 (Temporal) Notional Core + Extension Model ISO 19103 (Basic) Does not represent all stakeholders
Current Status • The Data Dictionary is in its 3 rd major iteration • The data modeling effort has produced the first iteration of FIXM which consists of a UML class model and associated XML schema
Future Steps • Data Dictionary will be augmented to accurately reflect changes and refinements of the data model • Data Model will be completed, reviewed, revised and augmented • Ongoing stakeholder feedback will be adjudicated and the Data Dictionary and FIXM will be updated accordingly • Further engineering analysis will be conducted, including assistance with implementation issues for demonstration or proof-of-concept projects
Engineering Needs: introduction • FIXM is the necessary Aircraft data standard that will Air Traffic Airspace ultimately be used by Control Users solution sets for the FIXM- enabled exchange of data middleware (e.g., SWIM) • Engineering analysis is Other National / Traffic Flow Management International required to understand the Agencies challenges and possible solutions for implementing FIXM-enabled systems
Engineering Needs: GUFI Requirements • Current flights are fairly difficult to define in an unambiguous way across multiple • Unique world-wide aviation domains • Identifies flight leg or flight plan • A Globally Unique Flight Identifier (GUFI) • Unique for given time range must be defined in a way to provide a • Unbound number of GUFIs created in any given time globally unique (both temporal and period spatial) mechanism for naming and • Constant for life-cycle of identifying flights flight • Any entity can create unique • Data correlation problems are examined GUFIs and alternative approaches are studied • Any number of entities to create GUFIs • Potential requirements for a GUFI format • Readable by human or have been identified, which support a machine wide range of future implementation • Conform to international standards decisions
Engineering Needs: Data Custody • Flight data ownership changes through time and space • The relative value (importance) of data elements changes from domain to domain • The flight data interchange mechanisms developed must take into account such transitions and changes
Engineering Needs: Implementation & NextGen • Any flight data interoperability solution (i.e. Flight Object) must be compatible with and aligned to NextGen operational initiatives • FIXM may need to be compatible with SWIM – approaches in defining FIXM that facilitate the implementation of flight data services are being investigated • Some of the engineering issues and implementation alternatives are being analyzed • Learning from early demonstration
Future Steps • Further engineering analysis will be conducted • Subject based analysis including Data Access Control, Data Exchange Modes, Data Redundancy, User Data Customization, Data Discovery, Data Compression, etc. • Engineering Alternatives • GUFI - revision • Implementation issues will be assisted by concept validation / proof-of-concept work • Demonstration work
International Flight Data Object (IFDO) Demonstration (03/2009) Cross-Domain Planning JAX • Constraint-Free, User-Preferred Flight Path • Domestic Metering • Initial Planning Advisories and Reservation SATL5S • Entry/Exit Planning SATL7S SATL4S MIA • Radar Transition Cross-Domain Situational Awareness SMA FIR ZNY FIR
International Flight Data Object (IFDO) Demonstration (03/2009) Objective • Develop a Flight Data set to support information sharing between NAS domestic and international stakeholders Benefits • Facilitate better coordination, situational awareness and collaborative decision making Description • Atlantic-based demonstration in the Florida NextGen Test Bed (FNTB) • FAA’s ATOP, FAA’s ERAM and NAV Portugal’s SATL systems were adapted in the lab to exchange FDO
Surface Exchange Flight Data Object (SEFDO) Demo (11/2009) Regional Departure Scenario: MCO/DAB to CLT Regional ARR Scenario: CLT to MCO International Scenario: LHR to MCO TFM/ER Wx integration � *��%���������+� Oceanic/ER TMA � ��������,�-��(!�)������������� � ������� ������������ LHR CLT � ��!"����� MCO Arr/Dep Mgt � �������������������� � ��������������������������� � ������������������ Oceanic/ER CFPM LHR � ������������ � ����������� � ���� � ������� � ��������������� � ���������������� � ��������������� MCO Surface Mgt DAB Flex Terminal � ����!������������� # ����!������������� # ��$ ��� Next Generation Surface � ������'����� �' � �%���� ������������������$��&� Management Activities � ������'���(�������������� � ������'���(�������������� � �%���� ������������������$��& � �������������������� � �����������������) IFDO SEFDO
Recommend
More recommend
