PETAL-II Preliminary Eurocontrol Test of Air/ground data Link, Phase II Operational Validation & Early Implementation Rob Mead PETAL-II Trials Manager.

PETAL-II Preliminary Eurocontrol Test of Air/ground data Link, Phase II

Operational Validation &Early Implementation

PETAL-II Preliminary Eurocontrol Test of Air/ground data Link, Phase II

Operational Validation &Early Implementation

Rob MeadRob Mead

PETAL-II Trials ManagerPETAL-II Trials Manager

Eurocontrol, DIS/ATDEurocontrol, DIS/ATD

TopicsTopics

Trials ContextTrials Context

PETAL-IIPETAL-II Current operations and statusCurrent operations and status

AAL / ARINC ATN Extension AAL / ARINC ATN Extension

Preliminary ResultsPreliminary Results

PETAL “Operations first, then technology.”

PETAL “Operations first, then technology.”

GOAL: requirements validation & captureGOAL: requirements validation & capture Are we headed in the right direction?Are we headed in the right direction?

So, we implement:So, we implement: ODIAC operational concept, services, ODIAC operational concept, services,

procedures, & abnormal modesprocedures, & abnormal modes international standards where ever possibleinternational standards where ever possible withwith airlines, industry, service providers airlines, industry, service providers withwithoutout backing a technology (triple stack) backing a technology (triple stack) withwith the ops floor and cockpit skeptics the ops floor and cockpit skeptics

PETAL-II Operational PackagePETAL-II Operational Package OperationalOperational trials, in situ, trials, in situ, with userswith users Clearly defined procedures and airspaceClearly defined procedures and airspace Pilot and controller always in commandPilot and controller always in command Voice readback before clearance executionVoice readback before clearance execution Fully silent for all other communicationsFully silent for all other communications Limited CPDLC message set (32 up, 12 down)Limited CPDLC message set (32 up, 12 down)

Routine R/T (transfer, level, route, heading, Routine R/T (transfer, level, route, heading, crossing conditions, vertical rate, speed, + few)crossing conditions, vertical rate, speed, + few)

A A littlelittle ADS and CM / AFN (log-on) ADS and CM / AFN (log-on) ATN (and FANS-1/A) compliant events.ATN (and FANS-1/A) compliant events. Multiple a/g datalink-equipped aircraftMultiple a/g datalink-equipped aircraft

PETAL-II Front-End

Processors

NEANGroundStations

Mode-S

ARINCVDL-2 stations

PETAL-II Players, End-EndPETAL-II Players, End-End

ParisMaastricht

NEAN ATN SITAFANS-1/A

SAS, Lufthansa AAL ANZ, UAL, DLH, COA, etc. Simulation

ICAO CNS/ATM Op data and behavior

Downlink Parameters

Reims FAA

PETAL-II Review (current ops)PETAL-II Review (current ops) NEAN Live Operations: Apr ‘98 NEAN Live Operations: Apr ‘98

600+ flights June - Oct '98600+ flights June - Oct '98 400+ April - June '99400+ April - June '99

FANS-1/A live operations: Feb ‘99FANS-1/A live operations: Feb ‘99 24-29 August: 23 of 36 total flights24-29 August: 23 of 36 total flights Key addition to resultsKey addition to results

Connection-orientedConnection-oriented Automated cockpitAutomated cockpit New cockpit culturesNew cockpit cultures

Over 1200 flights have used CPDLC in 9 monthsOver 1200 flights have used CPDLC in 9 months Multi-stack operations in placeMulti-stack operations in place All day, all sectors (14+)All day, all sectors (14+)

Maastricht SectorsMaastricht Sectors ABOVE HAMBURG AND SOLLING = HIGH EAST

ABOVE COASTAL = COASTAL HIGH

ABOVE DELTA = DELTA HIGH

Maastricht Controller HMIMaastricht Controller HMI

NEAN Airborne HMINEAN Airborne HMI

NEAN Communications LogNEAN Communications Log

B777 Flight DeckB777 Flight Deck

Airborne HMIAirborne HMI

NEAN CDTINEAN CDTI FANS-1FANS-1

B747-400 MCDUB747-400 MCDU B777 Flat PanelsB777 Flat Panels

FANS-A DCDU?FANS-A DCDU? ATN MCDUATN MCDU

High Level ResultsHigh Level Results Original objectives met at end ‘98Original objectives met at end ‘98 Tremendous amount of validation materialTremendous amount of validation material Total rewrite of one key service (transfer)Total rewrite of one key service (transfer) Numerous defects identified (e.g. timers)Numerous defects identified (e.g. timers) Requirements gaps identified, e.g.:Requirements gaps identified, e.g.:

log-onlog-on message pairsmessage pairs concatenated message rulesconcatenated message rules

ClearlyClearly added momentum to implementation added momentum to implementation

Ground ArchitectureGround ArchitectureController

HMIController

HMIController

HMIController

HMI

Flight Data Processing System- Flight plan / address association- ATN SARPS version 2.3 (ICAO doc 9705), CPDLC, ADS, CM- All datalink service logic (e.g. connection set-up / transfer, timers, etc.)

P2FEP

NFEP- Aircraft address/state- ASE emulation CM, CPDLC, ADS- Data conversion

FaFEP- Aircraft address/state- ASE emulation CM, CPDLC, ADS- Data conversion

ALLA- Aircraft address/state- Data conversion

ProATN - ASEs: CM, CPDLC, ADS - ATN Router

FANS-1/A Gateway

NEANServer

IDD 4.0BER

IDD 4.0PER

PETAL-IIe: AAL InitiativePETAL-IIe: AAL Initiative US and European airspaceUS and European airspace Core set of common messagesCore set of common messages Interoperable, documented functional Interoperable, documented functional

differencesdifferences Interoperable, documented procedural Interoperable, documented procedural

differencesdifferences

ATS / Airline deadlock brokenATS / Airline deadlock broken Harmonisation for airlines and ATSHarmonisation for airlines and ATS

PETAL-II Review (ATN)

Jan ‘99: PETAL-II End-End Spec’s frozenJan ‘99: PETAL-II End-End Spec’s frozen

Spring '00: First flights Spring '00: First flights cancan take place take place BAC1-11 trials ATN and Services, and satcomBAC1-11 trials ATN and Services, and satcom

May ‘01: AA, Maas, & Reims red label flightsMay ‘01: AA, Maas, & Reims red label flights 4 B767-300ER (European operations)4 B767-300ER (European operations)

Jun ‘02: First flights at Miami (FAA Build 1)Jun ‘02: First flights at Miami (FAA Build 1) Jun ‘03: US Key Site Build 1A (national 2004)Jun ‘03: US Key Site Build 1A (national 2004)

Maastricht & Reims SectorsMaastricht & Reims Sectors

UY

URFL340

FL245

XN

UNFL340

FL245

Global Timelines

1997 1998 1999199619951994 2000 2001 20042002 2003 2007 ….20062005

Base-1

PETAL

Op Concept

Op Requirements

LINK

Sim

PETAL-II extension

PETAL-II

Base-2

Sim

B-1

B-1A

B-2

FAA Implementation Program

CPC

ADS

AIDC

PIT

Preliminary ResultsPreliminary Results

Questionnaires and InterviewsControllers and Flight Crews

Problem & System Improvement ReportsControllers and Flight CrewsProject OfficeDesign Authorities

Statistics, e.g.Transmission and dialogue timesMessage useFDP system states, e.g. log-on, connect, transferall analysed for comm performance & debug

Data SourcesOperator and Designer Experience and Logs

Data SourcesOperator and Designer Experience and Logs

Integration Teams are EssentialIntegration Teams are Essential

Develop End-to-End SpecificationsDevelop End-to-End Specifications FAA Builds 1 and 1A (key site, Miami ARTCC)FAA Builds 1 and 1A (key site, Miami ARTCC) Maastricht and French UACsMaastricht and French UACs End-end procedures, automation, messagesEnd-end procedures, automation, messages interoperable use of SARPS, now to DO/EDinteroperable use of SARPS, now to DO/ED

Plan and coordinate initial fielding & certPlan and coordinate initial fielding & cert (air, ground, comm) (air, ground, comm)

Monitor and manage initial operationsMonitor and manage initial operations Formalise issues via RTCA/Eurocae, ICAOFormalise issues via RTCA/Eurocae, ICAO

Mixed EquipageMixed Equipage Simultaneous datalink aircraft / sectorSimultaneous datalink aircraft / sector

Up to 30 aircraft (all types) in sector at one timeUp to 30 aircraft (all types) in sector at one time Flight time / sector: 5 - 30 minutesFlight time / sector: 5 - 30 minutes Max number datalink aircraft (June '99): 3Max number datalink aircraft (June '99): 3 Overlap time: 1 - 16 minutesOverlap time: 1 - 16 minutes Datalink use: heavy to not at allDatalink use: heavy to not at all

Mixed equipage Mixed equipage preliminarypreliminary results results Equipage ratio: 1-3 datalink / 5-30 totalEquipage ratio: 1-3 datalink / 5-30 total Controllers unaware of NEAN or FANS-1/AControllers unaware of NEAN or FANS-1/A Not considered a serious problem Not considered a serious problem butbut Will limit benefitsWill limit benefits Minimum one flight per control session requiredMinimum one flight per control session required

Response Times and CPDLC UseResponse Times and CPDLC Use PETALPETAL-I-I dialogue & delivery times confirmed. dialogue & delivery times confirmed.

Max dialogue time, 10s = 55%Max dialogue time, 10s = 55% Observed performance acceptable = 84%Observed performance acceptable = 84% Actual averages = about 30sActual averages = about 30s

CPDLC good for strategic commCPDLC good for strategic comm CPDLC CPDLC notnot good for tactical acft separation good for tactical acft separation

regardless of transmission speedregardless of transmission speed tactical = use, not message typetactical = use, not message type

CPDLC good for climb, cruise, descendCPDLC good for climb, cruise, descend

(climb-out & approach???) (climb-out & approach???)

FANS-1/A ObservationsFANS-1/A Observations ARINC 424 vs. ground nav databasesARINC 424 vs. ground nav databases

CPDLC connection for close departuresCPDLC connection for close departures If automated event, may occur at poor timeIf automated event, may occur at poor time Aircrew HMI should consider not alerting Aircrew HMI should consider not alerting

"connect" at same level as clearance"connect" at same level as clearance Resume Own Nav without a "to"Resume Own Nav without a "to" Concatenation and Conditional Clearances Concatenation and Conditional Clearances

require additional restrictionsrequire additional restrictions

All applicable to ATNAll applicable to ATN

ATN Interoperability IssuesATN Interoperability Issues You You havehave message pairs. Standardise them! message pairs. Standardise them! Log-onLog-on

What's a "positive log-on"?What's a "positive log-on"? Mandatory (optional) log-on dataMandatory (optional) log-on data Static ground CM addresses / airborne data basesStatic ground CM addresses / airborne data bases Which aircraft address used by the ground?Which aircraft address used by the ground?

Logical Response (LACK)Logical Response (LACK) How does aircraft know whether to use them?How does aircraft know whether to use them? How do you resolve the cockpit differences?How do you resolve the cockpit differences?

Who connects CPDLC, air or ground?Who connects CPDLC, air or ground? New airspaces > different needs (e.g. timers)New airspaces > different needs (e.g. timers)

Operational ResultsReported Usefulness (controllers)

Operational ResultsReported Usefulness (controllers)

0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Time Clearance

Speed Clearance

Vertical Rate Clearance

Heading Clearance

ATC Mic Check

Route Request

Route Clearance

Flight Level Request

Flight Level Clearance

Transfer of Voice

No Comment

Not Useful

Useful

Message SetsMessage Sets Cut the message set, at least for initial opsCut the message set, at least for initial ops

Eases HMI and training (300+ messages??)Eases HMI and training (300+ messages??) Too many options (e.g. meter data types)Too many options (e.g. meter data types) Some don’t fit ops (e.g. deviate N/S/E/W)Some don’t fit ops (e.g. deviate N/S/E/W) No guidance on how to handle "bad" optionsNo guidance on how to handle "bad" options

Trick is to find a common core, andTrick is to find a common core, and Define interop handling for data types involvedDefine interop handling for data types involved Design HMIs to have these "on top"Design HMIs to have these "on top" Implement those firstImplement those first International set now being standardisedInternational set now being standardised

Builds and BaselinesBuilds and Baselines

0

10

20

30

40

50

60

70

80

90

100

Build 1A PETAL-II PETAL-IIe Build 2

Uplink

Downlink

Baseline 2

0

10

20

30

40

50

60

70

80

90

100

Build 1A PETAL-II PETAL-IIe Build 2

0

10

20

30

40

50

60

70

80

90

100

Build 1A PETAL-II PETAL-IIe Build 2

PETAL-II Datalink CapabilityLive operations, all 12 sectors, all day (539 CPDLC flights, 6/98 - 9/98)

Cap

abili

ty

1997 19981996 1999

NEANOperations

ATN 1.1 compliant - FDPS - Operations

Pre-Op environment

FANS-1/AOperations

ATN 1.1 compliant - FDPS - Operations

FANS-1/A Front-End

Pre-Op environment

FANS-1/AATN

2001 . . . . . .

NEAN

ATNOperations

ATN 2.3+ compliant - FDPS - Operations

Operational upgrades

FAA interoperable

Final step to certified / op approved environment

2000

Link 2000+

What Is This All Accomplishing?What Is This All Accomplishing? Bringing requirements into touch with realityBringing requirements into touch with reality Bringing standards into contact with designersBringing standards into contact with designers Uncovering expensive interoperability issues Uncovering expensive interoperability issues

beforebefore initial operations initial operations Bridging the Transatlantic divideBridging the Transatlantic divide

for procedures and systemsfor procedures and systems for operationsfor operations

Breaking the "you go first" deadlockBreaking the "you go first" deadlock Bringing together comm providers, airlines, Bringing together comm providers, airlines,

ATS, and suppliers to build a single systemATS, and suppliers to build a single system

ConclusionConclusion We have broken the "I will if you will" We have broken the "I will if you will"

deadlockdeadlock

Monthly report or newsletter distro?Monthly report or newsletter distro?

Individual or organizational inputIndividual or organizational input?? [email protected]@eurocontrol.be www.eurocontrol.be/projects/eatchip/petal2/