Your SlideShare is downloading. ×
0
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
Aero dataworkshop 2d-module-03_v1.0_en (2)
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

Aero dataworkshop 2d-module-03_v1.0_en (2)

221

Published on

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
221
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
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. <ul><li>Aeronautical Data 2-Day Workshop </li></ul><ul><li>Module: 3 </li></ul><ul><li>eTOD &amp; Other AeroData: Data Quality Context </li></ul>
  • 2. <ul><li>Objectives </li></ul><ul><li>Understanding of Annex 15… </li></ul><ul><ul><li>eTOD Requirements; and </li></ul></ul><ul><ul><li>Requirements for Related Aeronautical Data </li></ul></ul><ul><li>Implications for Indonesia </li></ul><ul><ul><li>Treatment of existing data </li></ul></ul><ul><ul><li>Planning of future priorities &amp; programmes for eTOD and other aeronautical data </li></ul></ul>
  • 3. <ul><li>ISO 19000 General Requirements </li></ul><ul><li>Audit and traceability </li></ul><ul><li>Other metadata </li></ul><ul><ul><li>Provenance </li></ul></ul><ul><ul><li>Coverage </li></ul></ul><ul><ul><li>Description </li></ul></ul><ul><ul><li>Access status </li></ul></ul><ul><li>Data Quality </li></ul><ul><li>Essential : Systems &amp; Procedures* to enable the State to satisfy these requirements </li></ul><ul><ul><li>For managing data within eTOD &amp; Procedure Design environment </li></ul></ul><ul><ul><ul><li>Particularly for supporting/enabling PBN and all RNAV flight procedure designs </li></ul></ul></ul><ul><ul><li>For managing interchange of data with AIS/AIP – *particularly until systems are integrated, or interfaced! </li></ul></ul>
  • 4. Annex 15 Areas
  • 5. <ul><li>Annex 15 Areas 1 &amp; 2 </li></ul><ul><li>1. Within the area covered by a 10-km radius from the ARP, terrain data shall be collected and recorded in accordance with the Area 2 numerical requirements. </li></ul><ul><li>2. In the area between 10 km and the TMA boundary or 45-km radius (whichever is smaller), data on terrain that penetrates the horizontal plane 120 m above the lowest runway elevation shall be collected and recorded in accordance with the Area 2 numerical requirements. </li></ul><ul><li>3. In the area between 10 km and the TMA boundary or 45-km radius (whichever is smaller), data on terrain that does not penetrate the horizontal plane 120 m above the lowest runway elevation shall be collected and recorded in accordance with the Area 1 numerical requirements. </li></ul><ul><li>4. In those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions and/or regulations, terrain data shall only be collected and recorded in accordance with the Area 1 numerical requirements. </li></ul><ul><li>Note.— Terrain data numerical requirements for Areas 1 and 2 are specified in Table A8-1. </li></ul>
  • 6. Annex 15 Areas
  • 7. <ul><li>Obstacle Data Collection – Areas 1 &amp; 2 </li></ul><ul><li>1. Obstacle data shall be collected and recorded in accordance with the Area 2 numerical requirements specified in Table A8-2: </li></ul><ul><ul><li>a) any obstacle that penetrates the conical surface whose origin is at the edges of the 180-m wide rectangular area and at the nearest runway elevation measured along the runway centre line, extending at 1.2 per cent slope until it reaches 120 m above the lowest runway elevation of all operational runways at the aerodrome (1.2 per cent slope reaches 120 m at 10 km); in the remainder of Area 2 (between 10 km and the TMA boundary or 45-km radius, whichever is smaller), the horizontal surface 120 m above the lowest runway elevation; and </li></ul></ul><ul><ul><li>b) in those portions of Area 2 where flight operations are prohibited due to very high terrain or other local restrictions and/or regulations, obstacle data shall be collected and recorded in accordance with the Area 1 requirements. </li></ul></ul><ul><li>2. Data on every obstacle within Area 1 whose height above the ground is 100 m or higher shall be collected and recorded in the database in accordance with the Area 1 numerical requirements specified in Table A8-2. </li></ul>
  • 8. Terrain &amp; Obstacle Data Collection – Area 3 1. Data on terrain and obstacles that extend more than a half-metre (0.5 m) above the horizontal plane passing through the nearest point on the aerodrome/heliport movement area shall be collected and recorded. 2. Terrain and obstacle data in Area 3 shall be collected and recorded in accordance with numerical requirements specified in Table A8-1 and Table A8-2, respectively.
  • 9. Terrain Data Collection Surface – Area 4 Only terrain data shall be collected and recorded in Area 4 in accordance with the numerical requirements specified in Table A8-1.
  • 10. <ul><li>Annex 15 Classes of Data by Area </li></ul><ul><li>Areas 1-4 </li></ul><ul><li>Segmented by requirements for different applications </li></ul><ul><ul><li>Procedure Design – TMA </li></ul></ul><ul><ul><li>Enroute – Different Requirements (eg, LSALT) </li></ul></ul><ul><ul><li>Area 4 – Precision Approach Cat II/III </li></ul></ul><ul><ul><li>Area 3 – Surface Movement (including Taxiways) </li></ul></ul>
  • 11. <ul><li>Data Quality Requirements </li></ul><ul><li>Audit &amp; traceability – important aspects </li></ul><ul><ul><li>Why? </li></ul></ul><ul><ul><ul><li>Allows you, as professionals, to judge what to do with the data </li></ul></ul></ul><ul><ul><ul><li>Quality control and data improvement </li></ul></ul></ul><ul><ul><ul><li>Security (eg, procedure integrity, restricted nature, etc) </li></ul></ul></ul><ul><ul><ul><li>Corporate knowledge in humans (previously) vs systems (increasingly necessary) </li></ul></ul></ul><ul><ul><li>What’s required to support this capability? </li></ul></ul><ul><li>Metadata </li></ul><ul><ul><li>Data Quality </li></ul></ul>
  • 12. <ul><li>Data Quality Requirements </li></ul><ul><li>Metadata </li></ul><ul><ul><li>Data Quality </li></ul></ul><ul><ul><li>Example for Actual Data </li></ul></ul>
  • 13. Data Quality Requirements <ul><li>Metadata – Data Quality Terminology </li></ul>
  • 14. Statistics ! Dark blue is less than one standard deviation from the mean. For the normal distribution , this accounts for 68.27   % of the set; while two standard deviations from the mean (medium and dark blue) account for 95.45%; three standard deviations (light, medium, and dark blue) account for 99.73%; and four standard deviations account for 99.994%. The two points of the curve which are one standard deviation from the mean are also the inflection points .   Source: &lt; http://en.wikipedia.org/wiki/Standard_deviation &gt; z σ percentage within CI percentage outside CI ratio outside CI 1 σ 68.2689492% 31.7310508% 1 / 3.1514871 1.645 σ 90% 10% 1 / 10 1.960 σ 95% 5% 1 / 20 2 σ 95.4499736% 4.5500264% 1 / 21.977894 2.576 σ 99% 1% 1 / 100 3 σ 99.7300204% 0.2699796% 1 / 370.398 3.2906 σ 99.9% 0.1% 1 / 1000 4 σ 99.993666% 0.006334% 1 / 15788 5 σ 99.9999426697% 0.0000573303% 1 / 1744278 6 σ 99.9999998027% 0.0000001973% 1 / 506800000 7 σ 99.9999999997440% 0.0000000002560% 1 / 390600000000
  • 15. Quality Management <ul><li>Types of Errors </li></ul><ul><ul><li>Refer RTCA-DO276 5.4 </li></ul></ul><ul><li>Aeronautical Data Requirements </li></ul><ul><li>Annex 4, accuracy and integrity, but also resolution (all through the document) – eg, Annex 4, 14.6(g) Aerodrome Ground Movement Chart – ICAO * NB: in this case it conflicts with Annex 14 &amp; 15 requirements for same data </li></ul><ul><li>Example of RESOLUTION </li></ul><ul><ul><li>1/100 second = approximately 0.3m or 1ft </li></ul></ul><ul><ul><ul><li>Annex 14, App 5 </li></ul></ul></ul><ul><ul><ul><li>Annex 15, App 7 </li></ul></ul></ul><ul><ul><ul><li>Covered in our system since ~ 2002 </li></ul></ul></ul><ul><ul><ul><li>Being updated to include newer and still evolving requirements </li></ul></ul></ul><ul><li>Annex 15 - Aeronautical Data Requirements: applies to all aeronautical feature data , not just obstacles and terrain </li></ul>
  • 16. Data Quality Requirements <ul><li>Metadata </li></ul><ul><ul><li>Data Quality - Obstacles </li></ul></ul>
  • 17. Data Quality Requirements <ul><li>Metadata </li></ul><ul><ul><li>Data Product Specification - Example </li></ul></ul>
  • 18. Q&amp;A &amp; Discussion <ul><li>Suggested discussion points </li></ul><ul><ul><li>Applying same principles to all aeronautical data – throughout data lifecycle and system-wide </li></ul></ul><ul><ul><li>Treatment of existing data </li></ul></ul><ul><ul><li>Planning of future priorities &amp; programmes for eTOD and other aeronautical data </li></ul></ul>

×