1 / 9

Trajectory TIM

Trajectory TIM. The Common Lexicon and FIXM Development. Rod Little / Cris Ianculescu , FIXM Development Team February 6, 2014. A common lexicon is a documented set of terminology that is specific to a particular industry or domain.

axelle
Télécharger la présentation

Trajectory TIM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trajectory TIM The Common Lexicon and FIXM Development Rod Little / CrisIanculescu, FIXM Development Team February 6, 2014

  2. A common lexicon is a documented set of terminology that is specific to a particular industry or domain

  3. Point-to-point ATM data exchanges use data elements with similar names but different meanings For Example

  4. A common lexicon of data elements must be established amongst a global set of stakeholders Improves the consistency of information across ATM systems Removes the misinterpretation of information leading to performance degradation and potential safety impacts Provides a reference source to system developers looking to gain understanding of the FIXM standard

  5. FIXM's lexicon has been developed via a bottoms-up approach beginning with individual DE proposals Finalize FIXM Logical Model CCB Concurrence? Yes Finalize FIXM Data Dictionary FIXM Data Dictionary FIXM Logical Model FIXM Schema No 2 Expand/Normalize DEs for DD & Logical Model Development FIXM Releases (v1.0, v1.1, v2.0) See slide #6 1 Conduct Initial Harmonization of DE Proposals Conduct Research of Existing ICDs Note: These pre-defined processes involve regularly scheduled Technical Review Meetings Artifacts as part of regular FIXM releases

  6. Pre-defined processes involve regularly scheduled Technical Review Meetings • Pre-defined Process #1: Conduct Initial Harmonization of DE Proposals • Includes DE name and description • Facilitated by weekly Data Dictionary Technical Review Meetings (DD-TRMs) with international stakeholders* • Initial identification of DEs that may be out of scope • Initial identification of homonymous/synonymous proposals • Initial determination of development iterations • Results posted to website for continued collaboration • Pre-defined Process #2: Expand/Normalize DEs for DD & Logical Model Development • Facilitated by weekly DD-TRMs and Modeling Technical Review Meetings (M-TRMs) with international stakeholders* • Finalize initial harmonization efforts • Develop additional DE characteristics (e.g. alternate names, relationships, business rules, data type, etc.) • Initiate logical model development • Results posted to website for continued collaboration and CCB review *Note: International Stakeholders include: FAA EUROCONTROL Single European Sky ATM Research Airservices Australia Japan Civil Aviation Bureau Nav Canada

  7. Future FIXM releases will develop its lexicon via a top-down approach beginning with Operational Scenarios Develop Operational Scenarios and Diagrams Extract FIXM Concepts from Scenarios Develop Conceptual Model CCB Concurrence? FIXM Conceptual Model Expand Concepts for Logical Model Development Yes No Develop Logical Model FIXM Conceptual Dictionary FIXM Logical Model Data Dictionary FIXM Logical Model Note: FIXM Schema These pre-defined processes involve regularly scheduled Technical Review Meetings Artifacts as part of regular FIXM releases

  8. Major Lessons Learned • Develop website for collaboration and action item tracking • Archive DEs when necessary, never delete • Add notes to individual DEs linking them to the meeting minutes that capture when they were discussed and in what context

  9. Questions? http://www.fixm.aero

More Related