ADS-B-NRA Status

                   ASAS-TN Malmö
                   26-28 September 2005

                   Jörg Steinleitner (prepared by Gilles Caligaris)
                   CASCADE Infrastructure WP Leader, EUROCONTROL

European Organisation for the Safety of Air Navigation

    l   ADS-B-NRA Status per RFG sub-group deliverable:
        l   Application Definition Sub-group (OSED)
        l   Safety & Performance Requirements Sub-group (SPR)
        l   Interoperability Requirements Sub-group (INTEROP)

    l   Lessons learnt
    l   Way ahead

                AD SG: Operational Requirements

    l   Proposed Final “Operational Service and Environment Definition”
        document (OSED) distributed end of August (version 1.3)
    l   Strong international participation to the commenting and review
    l   Submitted for final CASCADE OFG approval
    l   All issues raised so far covered by OSED version 1.3:
         l   Remaining issue: “manual de-selection of baro altitude transmission”
         l   Update under development to address this issue
    l   OSED consistent with relevant ICAO OPLINKP work
         l   OPLINKP/1 agrees to all ADS-B relevant Doc 4444 changes

                             AD SG: Input to
        Operational Hazards Assessment work

    l   OPS workshops took place for:
         l   Hazards identification and classification
         l   Identification of the required mitigation means
         l   Covering both the “detected” and “not detected” hazards cases

    l   Key input to the SPR Operational Safety Assessment process

                 SPR SG: Process followed

    Nominal OPS mode                  Non-nominal OPS mode

           OPA                                OSA

          Process                            Process

      Performance Rqts                  Safety + Perf. Rqts
    From OPA perspective              From OSA perspective

                    Reconciliation Process
                    èSafety & Performance
         SPR SG: Performance Requirements
                                (OPA) 1/2

    l   Focused on technical performance requirements
    l   Starting from radar baseline requirements identification
    l   Deriving the corresponding ADS-B requirements
    l   Performance requirements allocation between the ground & airborne
    l   As an input to the “reconciliation” process with OSA

          SPR SG: Performance Requirements
                                 (OPA) 2/2

    l   Strong international coordination
    l   Frequent (virtual) gatherings between the various partners
        following the RFG/6 meeting (July 2005)
         l   Methodology: integrity vs accuracy for the corresponding radar baseline
         l   Iterative development of OPA releases, position papers, etc.
    l   Full convergence achieved on the corresponding major issues
    l   Resulted in OPA version 1.4c (23 September)

                      SPR SG: Safety Requirements

    l   Taking into account Operational aspects
        l   Input to OHA from AD SG (OPS expertise)
    l   Strong co-ordination with OPA on methodology
    l   OSA v0.3 delivered mid September:
        l   Allocation of requirements (ASOR)
        l   Updated set of fault trees, incl. internal mitigation means
        l   Definition of minimum position quality requirements – using ICAO “close
            approach probability” (CAP) method for assessing surveillance risk
    l   Initiated “reconciliation” process with OPA
    l   Proposed final update to be issued end of September

                                  SPR SG: SPR Document

    l   Synthesis of OPA & OSA material
        l   Selection of most stringent requirements
    l   Nominal and non-nominal modes of operation covered through
        OPA/OSA “reconciliation” process
    l   Allocation of airborne and ground requirements
    l   SPR version 1.0 release under preparation for approval at
    l   Input to ICAO/SASP work

                                                          INTEROP SG

     l   Where “top-down” (OSED/SPR) meets “bottom-up”
     l   Definition of minimum functional & technical requirements
          l   Basis for compatibility among the various elements of the system
          l   Using a specific (data link) technology
     l   Choice of technical solutions by expressing requirements on
         data formats and dynamics
     l   ADS-B-NRA “pioneering” RFG INTEROP work
          l   Approach: link independent Main Body and link dependent Annexes
          l   RFG develops 1090 ES INTEROP Annex
     l   Truly fast-tracked – to SG approval within 4 months of work !
     l   Now subject to harmonisation with SPR material

                                                       Lessons learnt

     l   ED78A/DO-264 is a good basis for assessment, but needed to
         be adapted to:
         l   The case of dealing with ATC separation minima
         l   Manage the comparison between ADS-B and radar
         l   Clarify how to deal with nominal vs non nominal modes of operation
         l   Ensure that OPS inputs are properly taken into account
         l   Express how OPA and OSA processes can be “reconciled”
     l   Some differences between US and Europe in applying
         methodologies needed to be resolved
     l   ADS-B-NRA proved to be a perfect RFG GSA pioneer
         l   Very much lays the foundation for the work on ADS-B-RAD
         l   Building a strong team !

                                                    The way ahead

     l   RFG/7 to approve ADS-B-NRA SPR & INTEROP documents
     l   Subject to EUROCAE/RTCA “final review and comment”
         l   Final editorial changes (beginning of Nov 05)
         l   Kick-off of FRAC by EUROCAE WG51/RTCA SC-186 in November
         l   Final RFG comment resolution and editing at RFG/8 (13-16 Feb 06)
         l   EUROCAE WG51/RTCA SC-186 approval (17 Feb 06)
         l   EUROCAE Council/RTCA PMC publication during Mar/Apr 06
     l   Forward of all ADS-B-NRA related RFG material to ICAO SASP
         (comparative assessment approach)


Shared By:
jny jhtw jny jhtw