Your SlideShare is downloading. ×
COMPASS Early Safety Warning System (ESWS)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

COMPASS Early Safety Warning System (ESWS)

964

Published on

Screenshot-based presentation of the Early Safety Warning System developed in the context of the COMPASS SESAR-JU WP-E project, targeting safety management in Air Traffic Management (ATM) systems.

Screenshot-based presentation of the Early Safety Warning System developed in the context of the COMPASS SESAR-JU WP-E project, targeting safety management in Air Traffic Management (ATM) systems.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
964
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. COMPASS Early SafetyWarning System (ESWS)SESAR/JU WP-E COMPASS Projecthttp://www.compass-sesarju.euDimitris Kolovos, Richard PaigeDepartment of Computer ScienceUniversity of York{dimitris.kolovos, richard.paige}@york.ac.uk
  • 2. Usage Scenario• ESWS has access to flight plans of flights crossing aparticular sector on a particular day (from 00:00 to24:00)• ESWS also has access to other sources of informationsuch as ACC headers, meteorological data etc.• ESWS analyses this data and provides early safetywarnings to the user– Based on user-defined patterns expressed using adedicated pattern language (EPL)• Early Safety Warnings are warnings about complexevents which, if left to develop, can compromise thesafe operation of the ATM system
  • 3. Slide 3Slide bar allowing the userto move to different timesin the day.Map that providesa visual overview of thesector.
  • 4. Slide 4Blue points: Sector entry/exit pointsGreen points: Waypoints in the sectorSolid lines: Airway fragmentsDashed lines: Ends do not belong to thesame airway but 1 or more flights havebeen found to fly directly between their ends
  • 5. Slide 5Airway fragments highlighted according todirectionality,Blue fragments: UnidirectionalRed fragments: Bidirectional
  • 6. Slide 6Selecting en element on the mapmakes its properties appearin the Properties panel
  • 7. Slide 7User moved time slider to 09:36:00The positions of flights that have crossedor will cross the sector are displayed on the map.
  • 8. Slide 8Selecting a flight makesits properties appear inthe Properties view
  • 9. Slide 9The Traffic Level view displaysthe number of flights in the sectorat each time during the day.
  • 10. Slide 10The Fragments viewdisplays the number of flightsthat will be crossing eachfragment during the day.Double-clicking on afragment reveals its endson the map
  • 11. Slide 11The Fragments viewdisplays the number of flightsthat will be crossing eachimportant point during the day.
  • 12. Slide 12The Airspaces viewallows users to switchbetween airspaces (sectors)
  • 13. Slide 13We switch to theEHAMTA sector
  • 14. Slide 14The conflicts view displaysthe results of conflict analysis
  • 15. Slide 15Double-clicking on a conflictloads a detail report of theconflict and highlights the involvedflights on the map.
  • 16. Slide 16In the report, users caninteract with the evolutionof the conflict in time
  • 17. Slide 17Users can also exploreother conflicts that arehappening at the same time
  • 18. Slide 18
  • 19. Slide 19
  • 20. Slide 20Finally, users can alsoexplore other conflicts whichare not happening at thesame time but which involvethe same flights
  • 21. Slide 21
  • 22. Slide 22Users can specify arbitrarypatterns using theEpsilon Pattern Language
  • 23. Slide 23This pattern checks for flights withsimilar call signs (common source of confusion)This pattern checks for conflicts thatoccur at the same time (challenging to handle)
  • 24. Slide 24This pattern checks for conflicts thathappen while the occupancy of thesector is particularly highThis pattern checks for conflicts thatinvolve ascending/descending flights
  • 25. Slide 25This pattern checks for periods inthe day with low visibility and strong winds
  • 26. Slide 26Patterns can be matchedagainst the state of the sectorover the 24hrs period
  • 27. Slide 27The user can explore identifiedmatches through a dedicated view
  • 28. Slide 28Pattern matches are also groupedby the elements of the airspace thatare involved in them to supportroot cause analysis

×