Modernising aeronautical information management
•
3 likes•322 views
Modernising Aeronautical InformationManagement by Snowflake Software was presented by Debbie Wilson at the INSPIRE Conference in Krakow, 2010. It describes the steps towards a digital and modernernised Aeronautical Information Management System as defined by the NextGen and SESAR projects.
Recommended
More Related Content
Viewers also liked
Viewers also liked (15)
Similar to Modernising aeronautical information management
Similar to Modernising aeronautical information management (20)
Recently uploaded
Recently uploaded (20)
Modernising aeronautical information management
- 1. Modernising Aeronautical Information Management Debbie Wilson – Business Consultant
- 2. Context • Air Traffic flows are estimated to be 2-3 times higher by 2025 than today • Both initiatives aim to develop secure, net-centric information services that: – Provide a common operating picture enabling access to right information, in right place at right time – Enable end to end information management – Improve aeronautical safety and efficiency
- 3. Future Air Traffic Management Systems • Effective information exchange is at the heart of future ATM – SWIM – Data Exchange Models IT infrastructure program to develop a SOA that will provide aeronautical and weather data to authorized users Used in OWS -7 Aviation Thread
- 4. OWS-7 Aviation Thread Evaluation & Advancement of AIXM • Serve, filter & update using WFS-T 2.0 • Dynamic portrayal using FPS • Metadata & Code lists • Validate WFS against Business Rules Evaluation & Advancement of WXXM • 4D weather data cube • Event Architecture • Time model Advancement of Event Notification Architecture • Multiple sources/types of events/schemas • WFS-T updates Integration of WFS onto SWIM Environment • WFS deployment on FUSE • FAA SWIM security • Ambitious 6 month project: Jan-June 2010
- 5. Demonstration Scenarios • Two scenarios were developed to represent real-world ATM processes for: 1. Transatlantic flight (USA – Estonia) 2. Charter Flight (USA – Canada) • Both scenarios covered: – Flight planning – Pre-flight briefing – In-flight monitoring and assistance: • Diversion due to severe icing at destination airport (scenario 1) • Diversion due to volcanic ash plume (scenario 2)
- 7. Data Maintenance Sub-System Aviation / Met Edit Client Insert timeslice AIXM / WXXM Data store WFS-T 2.0 SQL Insert Publish AIXM/WXXM files Maintain Load Build
- 8. Transforming and loading baseline data Able to load, transform and serve data via WFS within days of receipt
- 9. Near-Real Time Update and Data Exchange Aviation Decision Support Client Event Service Aviation Edit Client Insert change WFS 2.0 Dispatch Client EFB client Push events Event Publisher WFS-T 2.0 SQL Insert Feature Table Queue TableTrigger Feature Table Feature Table getFeature request getFeature response Publish Subscribe
- 10. Requesting data via WFS 2.0 Constructs a WFS query to select possible diversion airports: • Are within 100 nm of Tallinn • Have a runway > 5,000ft and hard surface • Must have Navaids and refuelling facilities • Passenger terminal must be in operation between 18:00 and 23:00
- 11. Requesting data via WFS 2.0
- 12. OWS-7 Flight Dispatch System Aviation Decision Support Client Event Service Aviation / Met Edit Client Insert timeslice WFS 2.0 Dispatch Client EFB client Publish event Event Publisher getFeature request getFeature response Notify AIXM / WXXM Data store WFS-T 2.0 SQL Insert Maintain Load Build Publish AIXM/WXXM files Feature Portrayal Service (WMS 1.3) Registry Service Subscribe
- 13. Visualising Data via Feature Portrayal Service
- 14. Flight Dispatch System using INSPIRE Services WFS-T 2.0 (ISO 19142 & 19143) On-the-fly transformation, load and publication Enabling real-time update and exchange (using both push and pull mechanisms) SOAP Binding and security Enables integration into SOA to ensure secure messaging and access control GetCapabilities & WSDL Enables discovery and use GetFeature & GetPropertyValue: • Spatial & Temporal (NEW) filtering and Stored queries Highly specific data retrieval reducing data traffic & stored queries improve client integration Feature Portrayal Service (WMS 1.3.0) Dynamic generation of images using data from WFS Ensures consistency between data available in view service and data access services User-controlled portrayal Integrate data from distributed WFS and visualise consistently Decouples view and download service Data providers only have to focus on provision of data access services
- 15. Accomplishments • Dispatch clients and EFBs were able to successfully consume and use OGC web services: – WFS 1.1 & WFS 2.0 – Feature Portrayal Service (WMS 1.3.0) – Event Service • Demonstrated services can support all data access requirements for dispatcher and pilots • Aeronautical & weather data can be exchanged in near- real time through distributed web services to enable common operating picture
- 16. Thanks & Questions Further Information • http://www.opengeospatial.org/projects/initiatives/ows-7 • http://www.snowflakesoftware.com/aviation
Editor's Notes
- Good afternoon, I’m Debbie Wilson from Snowflake Software and today I shall be providing you with an overview of the outcomes of the OGC OWS-7 interoperability testbed’s Aviation Thread sponsored by FAA and EUROCONTROL to demonstrate the benefits of using the same OGC web services as defined by INSPIRE to enable the modernisation of aviation information management systems.
- Air traffic levels expected to grow by ~4% year on year which will result in traffic flows 2-3 times higher than today Posing significant operational challenges to aviation domain: as: information flows required to ensure safety, operate efficiently and reduce environmental impact are increasing exponentially and current ATM systems are based on 1960’s technology and can’t cope!! EUROCONTROL and FAA have both embarked on 10 year programmes to modernise aeronautical information management: SESAR and NextGen Both initiatives aim to enable access to right information by the right person at right time using secure, distributed services
- Effective information exchange is at the heart of both initiatives for the development of future ATM systems. To achieve this FAA and EUROCONTROL are working together to develop and define: SWIM: System Wide Information Management Data Exchange Models: these are being developed using the same open, participatory process as INSPIRE and same MDA process resulting in the creation of GML application schemas. To date four exchange models have been developed but they intend to create many more Within the OWS-7, the focus was on testing and using AIXM and WXXM exchange models – both of which are taken into consideration in the development of the INSPIRE Transport Networks and Meteorological and Atmospheric Conditions themes.
- OWS-7 was an ambitious 6 month project (Jan-June 2010): involving a team of over 10 research, commercial and LMO organisations from around the globe and the project focused on 4 key themes: Evaluation and Advancement of AIXM and WXXM: the key objectives of both these topics were to demonstrate the ability to: Transform existing data into AIXM 5.1 and make this accessible through the latest version of the WFS specification (ISO 19142 – or WFS 2.0) Understand the ability to effectively retrieve AIXM and WXXM data using typical complex (spatial/temporal) queries Dynamic portrayal of the data for visualisation in aviation client applications (as a lot of aviation data changes often) Advancement of Event Notification Architecture Demonstrate ability to publish notifications of change caused by events via push mechanisms Particularly to demonstrate the ability for events to be automatically generated after updates are inserted to the datastore via WFS-T Integration of WFS onto SWIM environment (Snowflake Software were commissioned to) Demonstrate ability to securely exchange data within an SOA – i.e through SOAP bindings Investigate what is required to deploy OGC WFS onto the Apache FUSE ESB – which is the next generation of application tier middleware
- To ensure that the services are evaluated under real-world conditions, two scenarios were developed covering typical ATM work practices within dispatch operations for two types of flight: Regular Trans-Atlantic flight between Dallas Fort Worth (USA) and Tallinn (Estonia) Charter flight between USA and Canada commissioned that day These scenarios covered the full dispatch work flow: i) Flight planning, ii) Pre-flight briefing and In-flight monitoring and assistance – with both flights needing to be diverted in flight due to severe icing at destination airport and volcanic ash cloud due to an eruption in Alaska However, due to life imitating art we ended up switching the volcanic ash scenario to Europe given the abundance of real data we had from the Iceland eruption!
- Although the project was split across 4 topics the key aim of OWS-7 was to demonstrate how distributed web services can be integrated together to form an operational flight dispatch system. The flight dispatch system can be broken into key sub-systems: Data Maintenance: responsible for creating and updating aeronautical and meteorological datastores Data Exchange: responsible for enabling online access to data though both push and pull mechanisms Data Portrayal: responsible for transforming data for visualisation within client applications So the following slides will summarise the flight dispatch system developed in the project.
- The Data Maintenance sub-system: is comprised of two core components : An offline component: used to build and load an aeronautical and weather datastore using baseline data Online component GO Publisher WFS-T 2.0: which enables remote maintenance clients to access, edit and insert changes to the baseline data directly into the datastore.
- Despite being a very short term project, the whole system had to be developed from the ground up so the creation of the baseline datastores posed a challenge as we were provided with a lot of data but supplied in 6 or 7 different data specifications – not AIXM or WXXM as these are new data specifications (like those being developed in INSPIRE). However, the project was able to use our COTS solutions: GO Loader and GO Publisher which are generic schema translation software which were able to load, transform and make the data available through a WFS within days of receipt – maximising the time available to the other service providers and client developers to integrate with the WFS and understand the data. Without this capability the project would have really stalled!
- So, once the baseline datastore was established, ongoing updates generated by remote edit clients and inserted directly into the datastore via the transactional WFS 2.0. Once an update was inserted into the database it triggered a number of processes within the database to initiate the generation of State and Event features which were then made accessible to the dispatch and electronic flight bag clients via: Pull mechanisms – by requesting data (often using complex queries) using the WFS 2.0 getFeature and getPropertyValue operations Push mechanisms – where the client subscribes to an event service to receive any changes/events (or NOTAM) to the status of aeronautical or weather features relating to their area of interest in this case the flight path. So when an event is inserted via the WFS this triggers the creation of an event which is pushed to the event service by the event publisher which then selectively pushes this on to subscribed clients based of their filter criteria All of this happens in Near Real time – meaning that once the data is published to the database is accessible to the dispatcher and pilot within minutes. This is a huge benefit compared to existing paper based systems which are often out of date as soon as they are printed.
- To demonstrate the ability to efficiently retrieve data via the WFS 2.0, a number of typical queries that either the dispatcher or pilot would perform were defined. One such example was to identify suitable diversion airports in the event of closure of the destination during flight. So as we can see, the Frequentis dispatch client connects to the Snowflake AIXM WFS 2.0 and the dispatcher uses the query interface to configure this query which is the posted to the service In this example the dispatcher must construct a WFS query to select airports that Are within 100 nautical miles of Tallin Have a runway length > 5000 ft Runway surface must be hard Must have navaids Re-fuelling facilities Airport must have passenger terminal facilities in operation between 14:00 and 18:30 This is a very complex query which using all the filter encoding spatial, temporal, logical and comparison operators!!
- The service responds and returns 12 potential airports which the dispatcher then reviews the information describing each airport to select the most appropriate destination airport for this flight. Such queries are very complex and makes the client development challenging. However, the WFS 2.0 specification provides new operators called Stored Queries which can be used to parameterise common complex queries converting them into more simple HTTP Get or URL string requests I haven’t shown you any examples in this presentation as unfortunately there is not enough time but please feel free to come and visit us downstairs where we can demonstrate how these stored queries will work
- The final part of the Dispatch system is the Data Portrayal system. This consisted of a feature portrayal service which is a dynamic WMS that generates and renders images on-the fly and the registry service containing a set of different styling options defined using OGC SLD and SE definitions. Both aeronautical and weather data are highly dynamic therefore, the aim was to understand the benefits that the FPS would bring to enable
- To demonstrate – this example shows the EFB placing a request to retrieve and visualise volcanic ash SIGMET data and a NOTAM containing updated schedule information for the destination airport received via the event service while enroute. The client places a request to the FPS which inturn retrieves the data from the WXXM and AIXM WFS and renders the data using the portrayal SLD and SE defined by the EFB. The pilot can see that the destination airport has been closed due to dangerous levels of volcanic ash and then contacts the dispatcher for an alternative destination.
- To conclude, within OWS-7 we were able to demonstrate the benefits of developing a flight dispatch system upon web services based on the latest open standards which are the same as those required for INSPIRE: WFS-T 2.0 Enables real-time update and exchange Integration into SOA Discovery and use Ability to retrieve only data you need significantly reduces bandwidth (very important when exchanging data within pilots) FPS (WMS 1.3.0) Ensures consistency between data available through both view and download services Can integrate data from distributed WFS and visualise consistently Decouple view and download services so data providers only have to focus on provision of data access services while portrayal services may be provided centrally
- So despite the short timescales and broad scope, OWS-7 was extremely successful and demonstrated that dispatch clients and EFBs can successfully consume and use distributed OGC web services to access aeronautical and weather data in real-time for improved decision making through a common operating picture
- Thanks and if you want to find out further information about the project then please visit the OGC OWS-7 public pages where you will shortly be able to find videos and engineering reports describing what we did and also visit our aviation pages and come see us downstairs