isdefe ingeniería de sistemas

CARE/ASAS Activity 2 Follow-up:Validation Framework Dissemination Forum

IsdefeIngeniería de Sistemas

10.10.2002

CARE/ASAS ACTIVITY 2 FOLLOW-UP:VALIDATION FRAMEWORK DISSEMINATION FORUM


10.10.2002



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í[email protected]

Bretigny, 10/10/2002



10.10.2002- 3 -

TEMPLATE

TEMPLATE?TEMPLATE?

CONCLUSIONSCONCLUSIONS

TEMPLATE STRUCTURE TEMPLATE STRUCTURE

TEMPLATE APPLICATION TEMPLATE APPLICATION



10.10.2002- 4 -

Template

?

TEMPLATE?



10.10.2002- 5 -

• 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)

Template?

(I)

WHAT THE TEMPLATE IS?



10.10.2002- 6 -

• 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

Template?

(II)

WHY IS A TEMPLATE NEEDED?



10.10.2002- 7 -

Template

Structure

TEMPLATE STRUCTURE



10.10.2002- 8 -

Template Structure

(II)ACTORSASAS APPLICATION & ASSOCIATEDFLIGHT PHASES

HIGH LEVELOBJECTIVE(S)

AIRSPACE TRAFFIC AIR TRAFFIC SERVICESINVOLVED

RULES TASKS

Performer Supervisor

TECHNOLOGY

Obtain surveillancedata

Tactical controller Flight crew Technology

Tactical controller Flight crew

VOLUME: Very High High Medium Low

FLIGHT RULES: IFR New rules

Manage and pro-cesssurveillance data



COMPLEXITY Broadcast surveil-lance data



RESTRICTIONS: Applicable in a new

class of segregatedairspace to be defined

Capacity/flowrestrictions

SEPARATION: Time Distance Tolerances Co-ordinate trans-fer

of aircraft to nonFFAS

Tactical controller Tactical controller FLIGHTSCHEDULE

Time Aircraft ID Aircraft model Equipment Trajectory

Report technologyperformances de-gradation

Flight crew Technology

Flight crew

Assume responsibi-lity for technologyfailures on airborneequipment

Planning controller Tactical controller


Airborne self separation in ATC-controlled airspace: Cruise Flight level change TMA

TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020

PHRASEOLOGY: Standard New (define)

Assume responsibi-lity for technologyfailures on groundequipment

Flight crew Flight crew

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 anddelegation status

Controller assistancetool

Traffic density control &estimation tool

MONA ATM

Planning Automation

AIRCRAFT TYPE: Perform separationassurance


Flight crew

Assure separationfrom surroundingaircraft

Planning controller Tactical controller Flight crew Technology

Flight crew

ICAO A B C D E F H

FAA Heavy Medium

Turboprop Medium

Turbojet Light

RVSM: Yes No

Request delegationon separationassuranceresponsibility


Tactical controller

Manage the FFAStraffic complexityand density

Planning controller Planning controller

Airborne self separation in segregateden-route airspace Cruise TMA

Define an orderlyflow of traffic (stra-tegic, pre-tacticaland tactical)



EQUIPMENTTYPE:

Equipped* Mixed % equipped aircraft

* Equipped aircraft aremandatory in segregatedairspace

AIRCRAFTSEQUENCING

CONFLICTRESOLUTIONSTRATEGY

CO-ORDINATIONAND TRANSFERPROCEDURES

Decide clearancesand instructions

Planning controller Tactical controller Technology

Tactical controller

Maintain traffic sit-uational awareness


Request exit fromFFAS


AIRCRAFTPERFORMANCE

Follow the control-ler’s clearances andinstructions


Flight crew

Airborne self separation in mixed-equipage en-route airspace: Cruise TMA

SAFETY Improve safety Increase pilot’s

situational awareness Decrease number of

voice communica-tions between con-troller and flight crew

CAPACITY Increase system

capacity Improve flight effi-

ciency and flexibi-lity Decrease controller

workload

ECONOMICS Optimise flight

profile Achieve fuel savings Improve reliability

of flight times Reduce en-route

charges

ENVIRONMENT Achieve fuel savings

SECURITY

TYPES: MAS UMAS FFAS New types

AREAS: En-route TMA Airport New areas

ELEMENTS: Boundaries (space

and time) Entry and exit

points Transition zones Vertical Descent/

Ascent buffer zone(for emer-gencies)

Special areas andalternative routes

Terrain topo-graphy

Atmosphericconditions

GEOGRAPHICALSCOPE

Central Europe Eastern Europe Scandinavia North Atlantic Mediterranean

ATC FIS TIS-B Alert Service GNSS ATFM Performance Management New Services

TRAINED FLIGHTCREWS*

* Mandatory on equippedaircraft

See and avoid othertraffic

Tactical controller Planning controller Flight crew

Tactical controller Planning controller Flight crew

AIRBORNE Redundancy Communications:

Voice Data link

Surveillance: Mode-S TCAS II/ETCAS Audio/visual alerts Traffic information

processing Surveillance data pro-

cessing (ADS-B) Conflict detection &

resolution system Navigation:

GNSS with augmen-tation

FMS 4D RNAV RNP1 Flight data system Automatic manage-ment

of the separa-tion(connection with FGCS)

Display: CDTI/EFIS/MCDU HUD



10.10.2002- 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.10.2002- 10 -

Template Structure

(III)

• 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

COLUMN 1: ASAS APPLICATION



10.10.2002- 11 -

Template Structure

(IV)

• 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

COLUMN 2: HIGH LEVEL OBJECTIVES



10.10.2002- 12 -

Template Structure

(V)

• 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

COLUMNS 3 TO 9: SCENARIO



10.10.2002- 13 -

Template

Application

TEMPLATE

APPLICATION



10.10.2002- 14 -

TEMPLATE APPLICATION

• APPLICATION OF THE TEMPLATE IN THREE STEPS

Template Application

(I)

1st STEP 2nd STEP

What to validate?

ASASAPPLICATION

3rd STEP

How to test?

VALIDATIONSCENARIO

What to obtain?

HIGH LEVELOBJECTIVES

SELECTION DEFINITION CREATION



10.10.2002- 15 -

• 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


(II)

1st step: WHAT I VALIDATE (ASAS APPLICATION)



10.10.2002- 16 -


(III)

2nd step: WHAT I WANT TO OBTAIN (HLO)

EXAMPLE

• SAFETY– Improve safety

• CAPACITY– Increase capacity

• ECONOMICS– Improve flight efficiency and flexibility– Optimise flight profile

• MANDATORY: TO SELECT AT LEAST ONE HLO



10.10.2002- 17 -


(IV)

3rd step: HOW I TEST (SCENARIO) - AIRSPACE

EXAMPLE

• FFAS• Sectors and schedule• Adjoining airspace• Entry/exit points• Transitions zones• Restricted areas• Mediterranean area

• MANDATORY: TO SELECT AND DEFINE ELEMENTS FROM:

• RESTRICTIONS (IF APPLICABLE) • ELEMENTS• TYPES • GEOGRAPHICAL SCOPE• AREAS

FFAS

MASSUA

Transition zones

Buffer zone



10.10.2002- 18 -


(V)

3rd step: HOW I TEST (SCENARIO) - AIRSPACE (2)

SECTOR INFORMATION

C1 40.5012426996 3.5502632803C10 40.1477127474 3.6003476871C104 42.5518645714 1.4497546564C105 42.5239819584 1.5000582420C106 42.4817830885 1.4511399854

1003 C429 C1111003 C111 C1101003 C110 C1091003 C109 C1081003 C108 C1071003 C107 C1061003 C106 C1051003 C105 C104

CornerIDLatitude Longitude

BoundaryCorner1

Corner2 BARCELONATMA Config1 TMW 946 0.0 195.0Bordeaux Config1 LFBFTA 1003 0.0 115.0Bordeaux Config1 LFBFTA 1005 115.0 125.0

ControlCentre

ConfigurationSchedule

Sector BoundaryID

Altitude Low forthe boundary

Altitude High forthe boundary



10.10.2002- 19 -


(VI)

3rd step: HOW I TEST (SCENARIO) - TRAFFIC

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


• VOLUME • AIRCRAFT TYPE• COMPLEXITY • EQUIPMENT TYPE• FLIGHT SCHEDULE • AIRCRAFT PERFORMANCE• TIMEFRAME



10.10.2002- 20 -


(VII)

3rd step: HOW I TEST (SCENARIO) - TRAFFIC (2)

TRAFFIC INFORMATION REQUIRED

000000 DAN556 LEGE RWY EKBI RWY B735 Normal DefaultACNavEquipment 280 280 280

FlightTime

FlightIndicative

DepartureAirport

DepartureRunway

DestinationAirport

ArrivalRunway

Type ofaircraft

Entry FL Exit FL

Cruise FL



10.10.2002- 21 -


(VIII)

3rd step: HOW I TEST (SCENARIO) - ATS INVOLVED

ATC FIS TIS-B APP Alert Service GNSS ATFM Performance ManagementNew Services

• MANDATORY: TO SELECT AT LEAST ONE ATS & DEFINE THE NEW ONES

EXAMPLE



10.10.2002- 22 -


(IX)

3rd step: HOW I TEST (SCENARIO) - RULES

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


• FLIGHT RULES (NEW) • AIRCRAFT SEQUENCING• SEPARATION • CONFLICT RESOLUTION STRATEGY• PHRASEOLOGY (NEW) • CO-ORDINATION & TRANSFER

PROCEDURES• RVSM • TRAINED FLIGHT CREWS



10.10.2002- 23 -


(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



10.10.2002- 24 -


(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



10.10.2002- 25 -


(XII)

3rd step: HOW I TEST (SCENARIO) - TECHNOLOGY (2)GROUND

Communications:VoiceData linkInter-sector information transferSurveillance:Radar coverageNo radar coverageTIS-BADS-BCWP HMI with air-craft equipment, ID and delegation statusController assistance toolTraffic density control & estimation toolMONAATMPlanningAutomatization

AIRBORNERedundancyCommunications:VoiceData linkSurveillance:Mode-STCAS II/ETCASAudio/visual alertsTraffic information processingSurveillance data processing (ADS-B)Conflict detection & resolution systemNavigation:GNSS with augmentationFMS4D RNAV RNP1Flight data systemAutomatic management of the separation (connection with FGCS)Display:CDTI/EFIS/MCDU HUD



10.10.2002- 26 -


(XIII)

GENERAL DATA

• VALIDATION TECHNIQUE

• SCENARIO IDENTIFICATION (ID)

• PROJECT

• ORGANISATION

• CREATION DATE



10.10.2002- 27 -

Conclusion

s

CONCLUSIONS



10.10.2002- 28 -

• 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

Conclusion

s

isdefe ingeniería de sistemas

Documents