1 Ground Human Machine Interface (GHMI): trends and the future by P. Jorna, GHMI Project Leader NLR.

11

Ground Human Machine Interface (GHMI): trends and the future


byby

P. Jorna, GHMI Project LeaderP. Jorna, GHMI Project Leader

NLRNLR

22

Role of man in ATM: the pastRole of man in ATM: the past

Designers perspective: human is a Designers perspective: human is a nuisancenuisance factor factor Human sciences ok in knowledge, but Human sciences ok in knowledge, but no products!no products! Software: ‘use it or perish’, no rights for the ‘user’Software: ‘use it or perish’, no rights for the ‘user’ Second (international) thoughts: Second (international) thoughts:

‘‘Human bypass’ strategy proves impossible!!Human bypass’ strategy proves impossible!! Humans and HF knowledge, Humans and HF knowledge, needsneeds to be exploited to be exploited

Approach: break the borders, cross the bridges..Approach: break the borders, cross the bridges..

PHARE tasking: deliver a harmonised HMI with usable ‘tools’.

33

Human and Machine ‘teaming’Human and Machine ‘teaming’

Goal: bottleneck reduction for controllers, more Goal: bottleneck reduction for controllers, more efficient use of human capabilitiesefficient use of human capabilities

Possible strategiesPossible strategies Automation philosophy Automation philosophy• remove tasksremove tasks ‘Automatic’‘Automatic’• tailor taskstailor tasks ‘Adaptable’‘Adaptable’• workload dependentworkload dependent ‘Adaptive’‘Adaptive’• change taskschange tasks ‘Advanced’‘Advanced’

PHARE PHARE toolstools approach, controller in charge approach, controller in charge

44

Project structure of GHMI:Project structure of GHMI:

General HMI automation principles

HMI for Advanced Tools (PATS)

Specific Controller Working Positions (CWP)

PHARE DEMONSTRATIONS

55

Defining the controller human machine interfaceDefining the controller human machine interface

Operational concept & Human task analysisOperational concept & Human task analysis Initial HMI design & dialogue(s)Initial HMI design & dialogue(s) Part task(s) prototypingPart task(s) prototyping Evaluation & experimentsEvaluation & experiments IterationsIterations Specifications & implementationsSpecifications & implementations TrainingTraining Validation: did it work?, benefits?, risks? etc.Validation: did it work?, benefits?, risks? etc.

66

Machine assistance helpful? Datalink HMI prototypesMachine assistance helpful? Datalink HMI prototypes

KLM123153

120 100

402 280 250B747 045 010

plot symbol

= up linked (green)

= acknowledged (green)= unable (red)

= no response > 30s. (red)

Label versionLabel version

Table versionTable version

77

0

0,2

0,4

0,6

0,8

1

Manual Detection Resolution

Siz

e in

de

x

Low traffic

High traffic

Machine assistance helpful?Workload reducedMachine assistance helpful?Workload reduced

Pupil size decrease with lower workload

88

0

10

20

30

40

50


Se

co

nd

s

Low traffic

High traffic

Machine assistance helpful?Improved detection timesMachine assistance helpful?Improved detection times

Detection of non-confirmed clearances

99

0

5

10

15

20


Low traffic

High traffic

Machine assistance helpful?Still subjective uncertainty!(

Machine assistance helpful?Still subjective uncertainty!(

NASA TLX subjective workload ratings

1010

PD-1: mastering the implementation processPD-1: mastering the implementation process

Plan view display HIPS speed view Selected aircraft

ADFL Track Data Block HIPS altitude view HIPS horizontal view

1111

A PD1 example: the Highly Interactive Problem SolverA PD1 example: the Highly Interactive Problem Solver

1212

The work and experiences of the design teamsThe work and experiences of the design teams

An international, multi-disciplinary groupAn international, multi-disciplinary group HMI & automation design proved very complexHMI & automation design proved very complex Conceptual (im)maturity hampered task analysisConceptual (im)maturity hampered task analysis After en-route design (PD1) complexity After en-route design (PD1) complexity increasedincreased

as well as the time constraintsas well as the time constraints Design teams split up in PD2, PD3 and Training Design teams split up in PD2, PD3 and Training

team to allow for PD ‘overlaps’, team to allow for PD ‘overlaps’, experiments Cut!experiments Cut!

Pressure: Pressure: produceproduce deliverable within project scope deliverable within project scope

1313

PD-2: apply PD1 HMI to ETMAPD-2: apply PD1 HMI to ETMA

selected labelSAS 171 B737 :last cleared FL : FL 125current FL : FL 210speed : 360 ktsheading : 182a/c equipment : 3-Dweight category : mediumdestination : EDDF

descentFL 100 -> FL 80

descentFL 80 -> FL 70

descentFL 70 -> 3000 ft

deceleration300 kts -> 250 kts

deceleration250 kts -> 220 kts

Metering FixGEDERN (GED)

SAS171 B737 EDDF210 36 182 -1820125 0 0

3D M

1414

A PD-2 example: the AMDA PD-2 example: the AMD

4-D / class A

heavy

3-D / class B

planning time SAB513: 10:28:20

actual time: 10:15

aircraft planned for runway 25L aircraft planned for runway 25R

label colour yellow:arrival via PSA label colour blue:

arrival via GED

label colour green:arrival via RUD

actual time at GATE: 10:15

delay pointer

1515

An unresolved AMD issue…..An unresolved AMD issue…..

RIVER

IBE 326IBE 326

AMC 282

AMC 282

05

10

15

Time line

Hand-off

Datalink

Traffic

Pre-acceptance

Eye scanning under various traffic conditions

1616


Eye scanning under low traffic conditions

1717


Eye scanning under high traffic conditions

1818

PD3: when the going gets tough, the tough get going...PD3: when the going gets tough, the tough get going...

Many CWP’s!Many CWP’s!‘‘Gate to Gate’Gate to Gate’

1919

A PD3 example: departuresA PD3 example: departures

2020

Where we are with HMI standardisation for ATM.Where we are with HMI standardisation for ATM.

GHMI followed a ‘generic’, common approachGHMI followed a ‘generic’, common approach Controller acceptance Controller acceptance graduallygradually increased through increased through

participation & familiarisation (training)participation & familiarisation (training) Direct object manipulation ok, but trajectory handling needs Direct object manipulation ok, but trajectory handling needs

to simplifiedto simplified ‘‘What if’ tools helpful, various CWP design optionsWhat if’ tools helpful, various CWP design options GHMI software: still ‘a need for speed’ GHMI software: still ‘a need for speed’ Co-ordination between controllers needs attentionCo-ordination between controllers needs attention

GHMI a starting point for the next century……..?GHMI a starting point for the next century……..?

2121

And the future…...And the future…...

The work was completed, The work was completed, but it is not finished!but it is not finished! Experiments are in need to learn about impact on Experiments are in need to learn about impact on

controller behaviour, traffic awareness and ASAScontroller behaviour, traffic awareness and ASAS Non nominal conditions need validationNon nominal conditions need validation Training issues need to be explored furtherTraining issues need to be explored further The road ahead needs good transportationThe road ahead needs good transportation Lets travel that road Lets travel that road togethertogether: EEC, RE’s, FAA etc. : EEC, RE’s, FAA etc.

A life time opportunity for improvements!A life time opportunity for improvements!

2222

Many thanks to the team and….Until we meet again!Many thanks to the team and….Until we meet again!

Continue the collaborationContinue the collaborationGo for a PHARE NEXTGo for a PHARE NEXTIt is tough, but it works!It is tough, but it works!Also for US…..Also for US…..

2323



byby

P. Jorna, GHMI Project LeaderP. Jorna, GHMI Project Leader

NLRNLRnextnext

1 Ground Human Machine Interface (GHMI): trends and the future by P. Jorna, GHMI Project Leader NLR.

Documents

Transcript of 1 Ground Human Machine Interface (GHMI): trends and the future by P. Jorna, GHMI Project Leader NLR.