1 / 13

Safety and ASAS Applications Progress and Contents Ken Carpenter on behalf of the AP1 team

Safety and ASAS Applications Progress and Contents Ken Carpenter on behalf of the AP1 team. SAF-ASAS. It is a paper, and it’s in draft Drafting group is the AP1 team reporting to the FAA/EUROCONTROL R&D Committee This talk will cover purpose of SAF-ASAS progress that has been made

karlyn
Télécharger la présentation

Safety and ASAS Applications Progress and Contents Ken Carpenter on behalf of the AP1 team

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. Safety and ASAS ApplicationsProgress and ContentsKen Carpenteron behalf of the AP1 team ASAS Thematic NetworkSecond Workshop

  2. SAF-ASAS • It is a paper, and it’s in draft • Drafting group is the AP1 team reporting to the FAA/EUROCONTROL R&D Committee • This talk will cover • purpose of SAF-ASAS • progress that has been made • the contents of the paper (8 slides) • who to complain to • Completed version should be available in November ASAS Thematic NetworkSecond Workshop

  3. Purpose • To provide guidance on • how to develop safe applications • how to demonstrate that applications are safe • Discusses the problems for each category • does not discuss specific applications • does not try to show that ASAS is safe • Provides a review of the available methods • Discusses the use of the methods for ASAS applications • Discusses what it means for an ASAS application to be safe ASAS Thematic NetworkSecond Workshop

  4. Progress • Jan 2002 • work started • Dec 2002 • draft version (D1) distributed for comment • chapter 4 (‘Guidelines for safe ASAS applications’) not present • comments have been received and accommodated • Aug 2003 • second draft (D2) distributed for comment • chapter 4 complete - no chapter 5 (‘Conclusions’) • comments have been received, are being considered • Nov 2003 • document complete • Feb 2004 • Presentation to FAA/EUROCONTROL R&D Committee ASAS Thematic NetworkSecond Workshop

  5. Contents • Chapter 2 • the provision of safety • safety issues in ASAS applications (by category) • Chapter 3 • safety standards • design and assessment methodologies • Chapter 4 • development of safe ASAS applications • safety assessment of ASAS applications ASAS Thematic NetworkSecond Workshop

  6. The provision of safety • Same requirements for ASAS applications as any other ATM operation • ASAS assists the provision of separation • by controllers or by flight crew • ASAS applications have to meet the TLS for separation provision • proof of safety by comparison has to be justified • TLS for separation provision ~ 108 collisions/flight hour? • ASAS has to support safe applications • Equipment certification requirement - 109 collisions/flight hour ASAS Thematic NetworkSecond Workshop

  7. Safety issues in ASAS applications • Gives all the specific issues we thought of • General considerations • in addition to those listed below • human performance • ACAS • For each category • the role of ASAS in separation provision • safety issues related to roles and procedures • safety issues related to systems • safety issues related to implementation ASAS Thematic NetworkSecond Workshop

  8. Safety standards • Review of existing standards that apply to ASAS • SAE ARP 926A, 4754, 4761; FAR & JAR AMJ 25-1309 these are for systems • DO-264/ED78A • end to end • Air Traffic Services supported by communications • FAA NAS Modernization Safety Management Program • EUROCONTROL Safety Regulatory Requirements • ESARR 4 & EATMP ANS Safety Assessment Methodology • OSA methodology central to most work on ASAS • needs expansion to comply with ESARR 4 ASAS Thematic NetworkSecond Workshop

  9. Assessment methodologies • Design and human factors analysis • analytical • empirical • Risk analysis • hazard analysis • human error assessment • ICAO - collision risk assessment and separation • comparison with TLS • comparison with a reference system • Use made to date for ASAS applications ASAS Thematic NetworkSecond Workshop

  10. Development of safe ASAS applications • Recommends iterative development • concept • early specification • full specification • pre-deployment • operations • Favour hybrid/spiral model for development process • iterative loops through objectives, evaluation of alternatives, development, validation and assessment • Guidelines on addressing safety and human performance during development ASAS Thematic NetworkSecond Workshop

  11. Safety assessment of ASAS applications • Everything affects safety • the operational procedures • the decision support tools • the controllers and pilots • the communications • Guidelines offered on • operational safety analysis • technical safety analysis • spacing values and separation minima • Guidelines on each of the application categories ASAS Thematic NetworkSecond Workshop

  12. Activities versus development phase ASAS Thematic NetworkSecond Workshop

  13. Points of contact • Rose Ashford (NASA PoC) • rashford@mail.arc.nasa.gov • Gene Wong (FAA PoC): • gene.wong@faa.gov • Francis Casaux (EUROCONTROL PoC) • casaux@cena.fr ASAS Thematic NetworkSecond Workshop

More Related