The EMERALD RTD Plan and the ASAS Validation Framework

2. The EMERALD RTD Plan and the ASAS Validation Framework R P (Bill) Booth 10 October 2002

3. EMERALD RTD & the ASAS VF Objective To compare the EMERALD RTD Plan against the MAEVA Validation Framework to determine the nature of validation exercises necessary to deliver the plan

4. EMERALD RTD & the ASAS VF What is the EMERALD RTD Plan?

5. EMERALD RTD & the ASAS VF RTD Plan for ASAS applications • Identification of the RTD issues • Identification of RTD domains: • Operational concepts • Benefits & constraints • Safety Assessment • ASAS operations and human factors • ASAS design and airborne functions • Transition issues

6. EMERALD RTD & the ASAS VF RTD Plan for ASAS applications • User requirements or concept phase • User requirement analysis or feasibility phase • Functional requirements or acceptability phase • ASAS development or prototyping phase • Experimentation or validation phase • Implementation phase (not part of the RTD plan)

7. EMERALD RTD & the ASAS VF User requirements (or concept phase) • The concept of ‘Co-operative Air Traffic Control’ needs to be investigated in more detail • There is a need for operational requirements for ASAS applications based on expected benefits (and constraints)

8. EMERALD RTD & the ASAS VF User requirement analysis (or feasibility phase) • Select ASAS applications for European needs • Conduct an initial cost/benefit analysis • Define operational scenarios • Define ASAS requirements for the ADS-B media • Define an airborne architecture for ASAS and airborne functions • Conduct initial safety studies

9. EMERALD RTD & the ASAS VF Functional requirements (or acceptability phase) • Define operational procedures for the selected ASAS applications • Define the new ‘Rules of the Air’ and the airborne separation minima • Conduct a pass/fail, cost/benefit analysis • Address the transition issues : suitable rate of equipage, impact upon aircraft operators and ATM organisations

10. EMERALD RTD & the ASAS VF ASAS development (or prototyping phase) • Develop prototypes for ASAS equipment and for the new ground system functions • Conduct off-line simulations for the evaluation of ASAS algorithms and compatibility with ACAS • Develop real-time mock-ups • Draft industry standards • Prepare initial training programmes for pilots and controllers

11. EMERALD RTD & the ASAS VF Experimentation (or validation phase) • Conduct real-time simulations involving pilots and controllers • Conduct flight trials • Measure the potential benefits and constraints through a validation process • Re-evaluate the cost/benefit analysis • Conduct an in-depth safety study • Finalise ICAO standards and industry standards

12. EMERALD RTD & the ASAS VF How does the RTD Plan Map onto the Validation Activities?

13. EMERALD RTD & the ASAS VF Validation Activities and the RTD Plan • RTD plan issues equate to Validation aims of MAEVA • In some cases experiment techniques are specified • Cost/benefit (efficiency) issues • Architecture and algorithm issues • Some examples follow….

14. “Measure potential benefits & constraints through real-time simulations”

15. “Validate ASAS algorithms through real-time simulations”

16. “Validate the new share of responsibility between pilots and controllers”

17. EMERALD RTD & the ASAS VF Conclusions • The ASAS VF maps well to the high-level activities defined in the RTD plan. • Many issues in the RTD Plan are outside the validation scope. • Some issues in the RTD plan need further definition leading to high-level VF objectives • Key issue is complete specification of the ASAS applications to be validated

18. ASAS - Thematic Network An Advertisement Kick-off November 2002 Further details from Francis Casaux or Bill Booth

19. The EMERALD RTD Plan and the ASAS Validation Framework