1 / 16

xNOTAM Trial – closed NOV 2008

xNOTAM Trial – closed NOV 2008. xNOTAM Trial. Limited set of features: Airspace, AirspaceUsage; RouteSegment, RoutePortionUsage, Significant Points (Navaid and Designated Points); Aerodrome, Aerodrome Surfaces Usage, Runway, RunwayDirection, Taxiway; Obstacles; Notes Reversed Workflow

pkennedy
Download Presentation

xNOTAM Trial – closed NOV 2008

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. xNOTAM Trial – closed NOV 2008

  2. xNOTAM Trial • Limited set of features: • Airspace, AirspaceUsage; • RouteSegment, RoutePortionUsage, Significant Points (Navaid and Designated Points); • Aerodrome, Aerodrome Surfaces Usage, Runway, RunwayDirection, Taxiway; • Obstacles; • Notes • Reversed Workflow • NOTAM -> digital NOTAM • In future: digital NOTAM -> NOTAM…

  3. Overall • Objectives achieved: • Validate AIXM 5 • encoding the information contained in NOTAM messages • temporality concept • Improvements of the model -> implemented in AIXM 5.1 • Provide a proof of concept for a “digital NOTAM encoding application” • not intended for operational use or for production!!! • we need a much user-friendly and faster HMI for an operational system! • Provide a significant amount of test xNOTAM data • to system developers

  4. Execution of the Trial

  5. Lessons learned • Some key features (airspace, airport usage, obstacle, etc.) account for 50-70% of the NOTAM • End users have priorities for what NOTAM should become digital first • Initial input from LH Systems, SAS, KLM, Eurocopter, etc. • Focus Group task Incremental implementation ! Candidates for increment 1 - Airspace activation / reservations - Route closures - Navaid events - Airport / Runway closures - Obstacles - SNOWTAM - all other NOTAM as text “Note” on the feature !

  6. Lessons Learned • Data provider application shall help the operator to validate the data (HMI-1) • Was all expected data provided? • Does data comply with all business rules? • Is data plausible? • If possible, visualise the data in the context of the static data • Example – closed twy on airport layout • Example – obstacles on airport/airspace background • Example – active airspace on route/airspace background

  7. Lessons Learned • Data provider application shall minimise the data input effort (HMI-2) • Shall have a consistent (unique?) workflow • Avoid re-typing data that is already available • If available, partial AIXM format received from external source (“digital NOTAM proposal”) • At least cut/paste from another application, eventually in human-readable form • Example: airspace coordinates input as (“452434N 0333422E, 452532N 0333401E, 451434N 0333422E”) instead of individual input of each position • Example: “MON-FRI, 09:00-17:00”, “SUN, SAT, HOL”, etc. instead of complex timesheet input form

  8. Lessons Learned • Data provider application shall minimise the data input effort (cont.) • Wherever appropriate, graphical input • Example: twy / twy portion closure • Example: work in progress area

  9. Lessons Learned • ICAO NOTAM Text to be produced automatically and displayed “as you input data” (HMI-3) • Will ensure consistency between digital/text • Will give confidence to the operator that the data was correctly input

  10. Lessons Learned • Data synchronisation is important! • Baseline data • Digital NOTAM • NOTAM -> Checklist • Digital NOTAM • Assured delivery (digital signature) • Data synchronisation service is necessary for both static & dynamic data (APLI-1)

  11. Digital SNOWTAM Trial

  12. Scope Execution: Winter 2009-2010 • Service provider • Briefing • FPL • chart • FMS data • etc. • End user • Pilot • Airline OPS • ATC • etc. Originator (Digital NOTAM) Image Text Application AIXM 5 (Digital NOTAM) xNOTAM Trial (origination only) xSNOWTAM Trial (end-to-end)

  13. Digital SNOWTAM Trial 2009-2010 • SNOWTAM Message Sample   0902020400 ESSA S ESSA S0C)01L F)71/71/71 G)01/01/01 H)69/63/60 SFH N)71/GOODC)08 F)71/71/71 G)01/01/01 H)62/65/68 SFH N)71/GOODC)01R F)71/71/71 G)01/01/01 H)70/66/68 SFH N)71/GOODR)7/MEDIUM-GOODT)RWYS AND TWYS CONT 10 PER CENT. APRONS CONT 25 PER CENT

  14. Digital SNOWTAM Trial (2009-2010)

  15. Initial results • Surface Contamination model is validated • Including extra capabilities, • Detailed information for each Apron, TWY, stand • Portion of Apron covered by contaminant • Contamination percentage (very important for airlines) • Individual observation time for each element • Etc. • Very well received by airlines • Overview page – suggested by SAS and KLM • Perfectly feasible as operational application in 1-2 years • Report to AI-OPS: Poor compliance of issued SNOWTAM with ICAO specification • Complex N) & R) fields • Probably, for a good reason, but then the ICAO standard is in need for update… • Syntax errors in F, H, G

More Related