x NOTAM Trial Presentation x NOTAM Workshop 2

x. NOTAM Trial Presentation x. NOTAM Workshop #2 Brussels, 20 -21 November 2007 Item 6 European Organisation for the Safety of Air Navigation 1

Objective of the presentation l l l 2 Highlight trial objectives Explain application architecture Mention who will participate Present data provider interfaces Present data user interfaces

Trial objectives l demonstrate the maturity of the “digital NOTAM” concept l l l validate the AIXM 5 timeslice model to managing permanent and temporary changes l l discover business rules check the completeness of (selected) AIXM 5 feature definitions l l 3 use real NOTAM messages -> capture the information in AIXM provide digital NOTAM data to test users identify missing attributes or associations identify un-complete lists of values

Trial objectives l involve AIS Offices from ECAC State as test digital NOTAM data providers l l identify potential digital NOTAM users and applications l l 4 understand the digital NOTAM concept identify challenges to implementation discover roadmap discover the digital NOTAM strengths identify early benefits confirm that digital NOTAM can improve safety and efficiency identify essential bottlenecks that could prevent early adoption of digital NOTAM

2008: Digital NOTAM Trial 5

x. NOTAM Provider Interface l Test ‘digital NOTAM providers’ from NOTAM offices of ECAC States l l equipment needed l l fast Internet connection (not dialup) high-resolution computer screen (minimum 1280 x 1024) Firefox / Internet Explorer Start point is an already published NOTAM. l l 6 plus a few other States The interface will not be used to create NOTAMs It will help encode them in AIXM 5.

Baseline (Static) Data l l l 7 Providers will not have to maintain Baseline data Initial data exported from the EAD Static Database (SDO) Maintained by a constant feed of data from the SDO

Getting Data Test ‘digital NOTAM users’ – organisations who will exploit the AIXM 5 messages: l l advanced briefing concepts, using graphics and visual hints in addition or in replacement of the current NOTAM text; dynamic display of the current status of the airport surfaces and temporary obstacles on electronic flight bags; presentation to the pilot and to air traffic controllers of active restricted airspace and closed routes; etc. Four ways for getting the data: l x. NOTAM User Interface l l 8 immediate report – result tables & AIXM 5 data subscription - AIXM 5 messages Web Feature Service (WFS) – simplified AIXM Web Service (SOAP) – full AIXM

Web Feature Service (WFS) l 9 Enable the visualisation of the x. NOTAM database content with Sky. View 2

Test data providers l Confirmed l l l Interested by the Trial l l 10 Belgium Czech Republic Iceland Poland Romania Serbia & Montenegro Slovenia Switzerland Egypt South Africa Albania Austria France Spain

Test data users l Test data agreement signed by l l l l Interested by the Trial l l 11 Comsoft (Germany) Frequentis (Austria) Luciad (Belgium) ROMATSA (Romania) Sky. Job Electronic Flight Bag (UK) Servicios Aeronauticas Costa Azanar (Spain) European Aeronautical Group – EAG (UK) Jeppesen (USA) Lufthansa Systems (Germany) National Geospatial Agency – NGA (USA)

x. NOTAM Trial Application 12

x. NOTAM Trial Application l General considerations l Do not forget: it’s a trial! l l Operational use is excluded! Relatively small budget Focus on technical validation (AIXM) In case of difficulties l l 13 Follow priorities Record difficult aspects for later

x. NOTAM Trial Application l HMI l Options l l 14 Text forms versus graphics Generic versus tailored for types of event

x. NOTAM Trial Application l Because of constraints (time and budget) l Relatively non-sophisticated l l l Data providers need to understand the AIXM model in detail l l A real operational application is expected hide some of the AIXM complexity Given the constraints, result is very good l l l 15 text forms, generic Limited business rules Clean “Event” based workflow Smooth navigation Very interesting: Timeline Viewer

Data Provider and Data User Interfaces 16

Basics 17

User dependent l 18 The menu items a user sees is dependent on his role: l A data user will see: Home and Reporting l A data provider will see: Home, Events and Reporting l An administrator will see all of the menus

l 19 Providing data

Providing data: Event management 20

Providing data: Event management 21

Providing data: New event l 3 types of event Temporary l Permanent l Transient l 22

Providing data: Processing an event 23

Providing data: Attaching new feature 24

Providing data: Attaching new feature 25

Providing data: Attaching new feature 26

Providing data: Attaching existing feature l 27 Use search criteria to find the feature required

l 28 Using data

Using data: Viewing events 29

Using data: Viewing events 30

Using data: Viewing features 31

Using data: Viewing features 32

Using data: Manage subscriptions 33

l 34 Administration

Administration: Organisations 35

Administration: Organisations 36

Administration: Operators 37

Administration: Feature ownership 38

Administration: Feature ownership 39

Questions? 40