jorna2

7/27/2019 jorna2

http://slidepdf.com/reader/full/jorna2 1/23

1

Ground Human Machine Interface

(GHMI): trends and the future

by

P. Jorna, GHMI Project Leader

NLR

7/27/2019 jorna2


2

Role of man in ATM: the past

Designers perspective: human is a nuisance factor

Human sciences ok in knowledge, but no products!

Software: ‘use it or perish’, no rights for the ‘user’ Second (international) thoughts:

‘Human bypass’ strategy proves impossible!!

Humans and HF knowledge, needs to be exploited

Approach: break the borders, cross the bridges..

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

7/27/2019 jorna2


3

Human and Machine ‘teaming’

Goal: bottleneck reduction for controllers, more

efficient use of human capabilities

Possible strategies Automation philosophy• remove tasks ‘Automatic’

• tailor tasks ‘Adaptable’

• workload dependent ‘Adaptive’ • change tasks ‘Advanced’

PHARE tools approach, controller in charge

7/27/2019 jorna2


4

Project structure of GHMI:

General HMI automation principles

HMI for Advanced Tools (PATS)

Specific Controller Working Positions (CWP)

PHARE DEMONSTRATIONS

7/27/2019 jorna2

http://slidepdf.com/reader/full/jorna2 5/23 5

Defining the controller

human machine interface

Operational concept & Human task analysis

Initial HMI design & dialogue(s)

Part task(s) prototyping Evaluation & experiments

Iterations

Specifications & implementations Training

Validation: did it work?, benefits?, risks? etc.

7/27/2019 jorna2


7/27/2019 jorna2


0

0,2

0,4

0,6

0,8

1

Manual Detection Resolution

S i z e

i n d e x

Low traffic

High traffic

Machine assistance helpful?

Workload reduced

Pupil size decrease with lower workload

7/27/2019 jorna2


8

0

10

20

30

40

50


S e c o n d s

Low traffic

High traffic


Improved detection times

Detection of non-confirmed clearances

7/27/2019 jorna2


9

0

5

10

15

20


Low traffic

High traffic


Still subjective uncertainty!(

NASA TLX subjective workload ratings

7/27/2019 jorna2


10

PD-1: mastering the

implementation processPlan view display HIPS speed view Selected aircraft

ADFL Track Data Block HIPS altitude view HIPS horizontal view

7/27/2019 jorna2


11

A PD1 example: the Highly

Interactive Problem Solver

7/27/2019 jorna2


12

The work and experiences

of the design teams

An international, multi-disciplinary group

HMI & automation design proved very complex

Conceptual (im)maturity hampered task analysis After en-route design (PD1) complexity increased

as well as the time constraints

Design teams split up in PD2, PD3 and Training

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

Pressure: produce deliverable within project scope

7/27/2019 jorna2


13

PD-2: apply PD1 HMI to

ETMA

selected label

SAS 171 B737 :

ast cleared FL : FL 125

current FL : FL 210speed : 360 kts

eading : 182

a/c equipment : 3-D

eight category : medium

destination : EDDF

descentFL 100 -> FL 80

descent

FL 80 -> FL 70

descent

FL 70 -> 3000 ft

deceleration

300 kts -> 250 kts

deceleration

250 kts -> 220 kts

Metering Fix

GEDERN (GED)

SAS171 B737 EDDF210 36 182 -1820125 0 0

3D M

7/27/2019 jorna2


14

A 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 runwa y 25L aircraft planned for runwa y 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

7/27/2019 jorna2


15

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

7/27/2019 jorna2


16

An unresolved AMD issue…..

Eye scanning under low traffic conditions

7/27/2019 jorna2


7/27/2019 jorna2


18

PD3: when the going gets

tough, the tough get going...

Many CWP’s!

‘Gate to Gate’

7/27/2019 jorna2


19

A PD3 example: departures

7/27/2019 jorna2


20

Where we are with HMI

standardisation for ATM.

GHMI followed a ‘generic’, common approach

Controller acceptance gradually increased through

participation & familiarisation (training)

Direct object manipulation ok, but trajectory handling

needs to simplified

‘What if’ tools helpful, various CWP design options

GHMI software: still ‘a need for speed’ Co-ordination between controllers needs attention

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

7/27/2019 jorna2


21

And the future…...

The work was completed, but it is not finished!

Experiments are in need to learn about impact on

controller behaviour, traffic awareness and ASAS

Non nominal conditions need validation

Training issues need to be explored further

The road ahead needs good transportation

Lets travel that road together : EEC, RE’s, FAA etc.

A life time opportunity for improvements!

7/27/2019 jorna2


22

Many thanks to the team

and….Until we meet again!

Continue the collaboration

Go for a PHARE NEXT

It is tough, but it works!

Also for US…..

7/27/2019 jorna2


23

Ground Human Machine Interface

(GHMI): trends and the future

byP. Jorna, GHMI Project Leader

NLR next

http://localhost/var/www/apps/conversion/tmp/scratch_7/velten.ppt

http://localhost/var/www/apps/conversion/tmp/scratch_7/velten.ppt

Documents

jorna2