Isdefe Ingeniería de Sistemas

1. IsdefeIngeniería de Sistemas CARE/ASAS ACTIVITY 2 FOLLOW-UP:VALIDATION FRAMEWORK DISSEMINATION FORUM 10.10.2002

2. CARE/ASAS ACTIVITY 2 FOLLOW-UP:VALIDATION FRAMEWORK DISSEMINATION FORUM WP 1: SCENARIO FRAMEWORK TEMPLATE FOR ASAS APPLICATIONS VALIDATION Isdefe: Juan Alberto Herrería García jherreria@isdefe.es Bretigny, 10/10/2002

3. TEMPLATE TEMPLATE? TEMPLATE STRUCTURE TEMPLATE APPLICATION CONCLUSIONS

4. Template? TEMPLATE?

5. Template? (I) • WHAT THE TEMPLATE IS? • MAIN GOAL: SUPPORTING THE DESIGNER IN THE CREATION OF A VALIDATION SCENARIO FOR ASAS APPLICATIONS • COMPLEMENTED WITH ASAS APPLICATION AND HIGH LEVEL OBJECTIVES (HLO); AND ALSO GENERAL DATA OF THE EXERCISE • THEREFORE, THE TEMPLATE INTRODUCES THE INITIAL VALIDATION FRAMEWORK: • SELECTION OF ASAS APPLICATION (VF, ACTION 2) • DEFINITION OF THE HIGH LEVEL OBJECTIVES (VF, ACTION 5) • SUPPORT THE DESIGN OF THE VALIDATION SCENARIO (VF, ACTION 12)

6. Template? (II) • WHY IS A TEMPLATE NEEDED? • STANDARDIZE THE VALIDATION SCENARIOS FOR ASAS APPLICATIONS • FACILITATE THE TRACEABILITY OF THE SCENARIOS • SUPPORT DESIGNERS IN THE CREATION OF VALIDATION SCENARIOS FOR ASAS APPLICATIONS • ENSURE THOROUGH AND CONSISTENT VALIDATION OF ASAS APPLICATIONS

7. Template Structure TEMPLATE STRUCTURE

8. Template Structure (II)

9. Template Structure (I) • STRUCTURE BASED ON PO-ASAS CATEGORIES AND APPLICATIONS • ONE SPECIFIC TEMPLATE (SHEET) FOR EACH ASAS CATEGORY: • Airborne Traffic Situational Awareness • Airborne Spacing • Airborne Separation • Airborne Self-Separation • THE TEMPLATES ARE DIVIDED IN NINE (9) COLUMNS. THE FOUR CATEGORIES HAVE THE SAME COLUMNS. • EACH COLUMN ADDRESSES DIFFERENT PARTS OF THE INITIAL VALIDATION FRAMEWORK: • Column 1: ASAS Application & Associated Phase of Flight • Column 2: High Level Objectives • Column 3 to 9: Scenario • THE CONTENTS (GROUPS=BULLETS & ELEMENTS=BOXES) OF THE COLUMNS CAN VARY FROM ONE CATEGORY TO OTHER

10. Template Structure (III) • COLUMN 1: ASAS APPLICATION • ADDRESSES THE ASAS APPLICATIONS AVAILABLE FOR EACH ASAS CATEGORY • EACH ASAS CATEGORY HAS ONE OR SEVERAL ASSOCIATED PHASES OF FLIGHT • GROUP = ASAS APPLICATION; ELEMENTS = PHASES OF FLIGHT • AIRBORNE TRAFFIC SITUATIONAL AWARENESS IS THE ONLY ASAS CATEGORY WITH IN THE AIR AND ON THE GROUND APPLICATIONS

11. Template Structure (IV) • COLUMN 2: HIGH LEVEL OBJECTIVES • THE HIGH LEVEL OBJECTIVES FOR EACH ASAS CATEGORY ARE CLUSTERED IN THE FOLLOWING GROUPS: • SAFETY • CAPACITY • ECONOMICS • ENVIRONMENT • SECURITY • FOR EACH GROUP, ELEMENTS ARE DEFINED ACCORDING TO THE OBJECTIVES AIMED BY THE ASAS CATEGORIES

12. Template Structure (V) • COLUMNS 3 TO 9: SCENARIO • COLUMN 3 -AIRSPACE: Restrictions, Types, Areas, Elements, Airport Category • COLUMN 4 -TRAFFIC: Volume, Complexity, Flight Schedule, Timeframe, Aircraft Type, Geographical Scope, Equipment Type, Aircraft Performance • COLUMN 5 - ATS INVOLVED: ATC, FIS, TIS-B, APP, Alert Service, GNSS, ATFM, Performance Management, New Services, Surface Control and Guidance • COLUMN 6 -RULES: Flight Rules, Separation, Phraseology, RVSM, Aircraft Sequencing, Conflict Resolution Strategy, Co-ordination and Transfer Procedures, Trained Flight Crews, Airport Usage • COLUMNS 7 & 8 -TASKS AND ACTORS • COLUMN 9 -TECHNOLOGY: • GROUND:Communications, Surveillance, ATM • AIRBORNE: Communications, Surveillance, Navigation, Display

13. Template Application TEMPLATE APPLICATION

14. Template Application (I) • TEMPLATE APPLICATION • APPLICATION OF THE TEMPLATE IN THREE STEPS

15. Template Application (II) • 1st step: WHAT I VALIDATE (ASAS APPLICATION) • MANDATORY: TO SELECT ONE ASAS APPLICATION • RECOMMENDED: ONE ASAS APPLICATION PER TEMPLATE • EXAMPLE • ASAS CATEGORY: • AIRBORNE SELF-SEPARATION • ASAS APPLICATION: • AIRBORNE SELF-SEPARATION IN SEGREGATED EN-ROUTE AIRSPACE • Cruise

16. Template Application (III) • 2nd step: WHAT I WANT TO OBTAIN (HLO) • MANDATORY: TO SELECT AT LEAST ONE HLO • EXAMPLE • SAFETY • Improve safety • CAPACITY • Increase capacity • ECONOMICS • Improve flight efficiency and flexibility • Optimise flight profile

17. Template Application (IV) • 3rd step: HOW I TEST (SCENARIO) - AIRSPACE • MANDATORY: TO SELECT AND DEFINE ELEMENTS FROM: • RESTRICTIONS (IF APPLICABLE) • ELEMENTS • TYPES • GEOGRAPHICAL SCOPE • AREAS • EXAMPLE • FFAS • Sectors and schedule • Adjoining airspace • Entry/exit points • Transitions zones • Restricted areas • Mediterranean area

18. Template Application (V) • 3rd step: HOW I TEST (SCENARIO) - AIRSPACE (2) • SECTOR INFORMATION

19. Template Application (VI) • 3rd step: HOW I TEST (SCENARIO) - TRAFFIC • MANDATORY: TO SELECT AND DEFINE ELEMENTS FROM: • VOLUME • AIRCRAFT TYPE • COMPLEXITY • EQUIPMENT TYPE • FLIGHT SCHEDULE • AIRCRAFT PERFORMANCE • TIMEFRAME • EXAMPLE • VOLUME: increase 20% current volume • FLIGHT SCHEDULE: time, Aircraft ID, Aircraft Model, Equipment, Trajectory • TRAJECTORY: entry and exit points and times, FL, aircraft ID, routes • TIMEFRAME: 2005-2010 • AIRCRAFT TYPE: FAA. Heavy 10%, Medium TP 35%, Medium TJ 55% • EQUIPMENT TYPE: Equipped 100% • AIRCRAFT PERFORMANCE: BADA

20. Template Application (VII) • 3rd step: HOW I TEST (SCENARIO) - TRAFFIC (2) TRAFFIC INFORMATION REQUIRED

21. Template Application (VIII) • 3rd step: HOW I TEST (SCENARIO) - ATS INVOLVED • MANDATORY: TO SELECT AT LEAST ONE ATS & DEFINE THE NEW ONES EXAMPLE

22. Template Application (IX) • 3rd step: HOW I TEST (SCENARIO) - RULES • MANDATORY: TO SELECT AND DEFINE ELEMENTS FROM: • FLIGHT RULES (NEW) • AIRCRAFT SEQUENCING • SEPARATION • CONFLICT RESOLUTION STRATEGY • PHRASEOLOGY (NEW) • CO-ORDINATION & TRANSFER PROCEDURES • RVSM • TRAINED FLIGHT CREWS • EXAMPLE • FLIGHT RULES: new • SEPARATION MINIMA: 5NM horizontal and 1000ft vertical, with a tolerance +/- 95% • PHRASEOLOGY: new • RVSM • AIRCRAFT SEQUENCING • CONFLICT RESOLUTION STRATEGIES • CO-ORDINATION AND TRANSFER PROCEDURES: silence • TRAINED FLIGHT CREWS

23. Template Application (X) • 3rd step: HOW I TEST (SCENARIO) - TASKS/ACTORS • MANDATORY: TO SELECT AND DEFINE TASKS AND ACTORS • TASKS • REFERENCE TASKS ARE PROVIDED ON THE TEMPLATE • OTHER TASKS CAN BE DEFINED • ACTORS • Planning Controller – Flight Crew • Tactical Controller – Technology • TWO TYPES OF ACTORS: PERFORMER AND SUPERVISOR • EACH TASKS MUST BE LINKED TO ACTORS

24. Template Application (XI) • 3rd step: HOW I TEST (SCENARIO) - TECHNOLOGY • MANDATORY: TO SELECT AND DEFINE GROUND AND AIRBORNE TECHNOLOGY • GROUND TECHNOLOGY • COMMUNICATIONS • SURVEILLANCE • ATM • AIRBORNE TECHNOLOGY • COMMUNICATIONS • SURVEILLANCE • NAVIGATION • DISPLAY

25. Template Application (XII) • 3rd step: HOW I TEST (SCENARIO) - TECHNOLOGY (2) • AIRBORNE • Redundancy • Communications: • Voice • Data link • Surveillance: • Mode-S • TCAS II/ETCAS • Audio/visual alerts • Traffic information processing • Surveillance data processing (ADS-B) • Conflict detection & resolution system • Navigation: • GNSS with augmentation • FMS • 4D RNAV RNP1 • Flight data system • Automatic management of the separation (connection with FGCS) • Display: • CDTI/EFIS/MCDU HUD • GROUND • Communications: • Voice • Data link • Inter-sector information transfer • Surveillance: • Radar coverage • No radar coverage • TIS-B • ADS-B • CWP HMI with air-craft equipment, ID and delegation status • Controller assistance tool • Traffic density control & estimation tool • MONA • ATM • Planning • Automatization

26. Template Application (XIII) • GENERAL DATA • VALIDATION TECHNIQUE • SCENARIO IDENTIFICATION (ID) • PROJECT • ORGANISATION • CREATION DATE

27. Conclusions CONCLUSIONS

28. Conclusions • NEED OF A TEMPLATE TO STANDARISE THE ASAS APPLICATION VALIDATION • ITS WIDE USE WILL PERMIT THE TRACEABILITY OF THE ASAS EXPERIMENTS TROUGHOUT THE WORLD • THE TEMPLATE PROVIDES A GUIDE TO DEFINE THE VALIDATION SCENARIO, SELECTING THE COMPONENTS AND MORE PARTS • THE SCENARIO MUST BE FURTHER DEFINED THANKS TO AN ELABORATED DOCUMENT DEVELOPING THE SCENARIO CHARACTERISTICS. THIS DOCUMENT FORMS PART OF THE VALIDATION EXPERIMENT DESIGN TO BE CREATED FOLLOWING THE VALIDATION FRAMEWORK GUIDELINES