Scribd Logo
Upload

Welcome to Scribd!

  • 31 views

    Ground Human Machine Interface (GHMI) : Trends and The Future

    Uploaded by

    Avinash Hegde
    The document discusses the Ground Human Machine Interface (GHMI) project, which aimed to develop a harmonized interface between air traffic controllers and machines. It describes how earlier approaches saw humans as a nuisance, but the GHMI recognized the importance of incorporating human factors. The project developed prototype tools and controller working positions through multiple phases, evaluating them and improving the interfaces through an iterative process. While the interfaces increased controller acceptance and reduced workload over time, further validation and standardization are still needed to fully realize the benefits of improved human-machine collaboration in air traffic management.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Ground Human Machine Interface (GHMI) : Trends and The Future

    Uploaded by

    Avinash Hegde
    31 views23 pages
    The document discusses the Ground Human Machine Interface (GHMI) project, which aimed to develop a harmonized interface between air traffic controllers and machines. It describes how earlier approaches saw humans as a nuisance, but the GHMI recognized the importance of incorporating human factors. The project developed prototype tools and controller working positions through multiple phases, evaluating them and improving the interfaces through an iterative process. While the interfaces increased controller acceptance and reduced workload over time, further validation and standardization are still needed to fully realize the benefits of improved human-machine collaboration in air traffic management.

    Original Description:

    Paper Presentation topic

    Original Title

    jorna2

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the Ground Human Machine Interface (GHMI) project, which aimed to develop a harmonized interface between air traffic controllers and machines. It describes how earlier approaches saw humans as a nuisance, but the GHMI recognized the importance of incorporating human factors. The project developed prototype tools and controller working positions through multiple phases, evaluating them and improving the interfaces through an iterative process. While the interfaces increased controller acceptance and reduced workload over time, further validation and standardization are still needed to fully realize the benefits of improved human-machine collaboration in air traffic management.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    31 views23 pages

    Ground Human Machine Interface (GHMI) : Trends and The Future

    Uploaded by

    Avinash Hegde
    The document discusses the Ground Human Machine Interface (GHMI) project, which aimed to develop a harmonized interface between air traffic controllers and machines. It describes how earlier approaches saw humans as a nuisance, but the GHMI recognized the importance of incorporating human factors. The project developed prototype tools and controller working positions through multiple phases, evaluating them and improving the interfaces through an iterative process. While the interfaces increased controller acceptance and reduced workload over time, further validation and standardization are still needed to fully realize the benefits of improved human-machine collaboration in air traffic management.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 23

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

    by P. Jorna, GHMI Project Leader NLR

    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..


    2

    PHARE tasking: deliver a harmonised HMI with usable tools.

    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


    3

    Project structure of GHMI:


    General HMI automation principles

    HMI for Advanced Tools (PATS)

    Specific Controller Working Positions (CWP)

    PHARE DEMONSTRATIONS
    4

    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.

    Machine assistance helpful? Datalink HMI prototypes


    KLM123 s 153 120 100 s 402 280 250 4 B747 045 010 6 = up linked (green) = no response > 30s. (red) = acknowledged (green) = unable (red)

    Label version

    plot symbol

    Table version

    Machine assistance helpful? Workload reduced


    Pupil size decrease with lower workload
    1 0,8

    Size index

    0,6 0,4 0,2 0 Manual Detection Resolution

    Low traffic High traffic

    Machine assistance helpful? Improved detection times


    Detection of non-confirmed clearances
    50 40

    Seconds

    30 20 10 0 Manual Detection Resolution

    Low traffic High traffic

    Machine assistance helpful? Still subjective uncertainty!


    (

    NASA TLX subjective workload ratings

    20 15 10 5 0 Manual Detection Resolution


    9

    Low traffic High traffic

    PD-1: mastering the implementation process


    Plan view display HIPS speed view Selected aircraft

    ADFL

    Track Data Block

    HIPS altitude view

    HIPS horizontal view

    10

    A PD1 example: the Highly Interactive Problem Solver

    11

    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

    12

    PD-2: apply PD1 HMI to ETMA


    selected label SAS 171 B737 : last cleared FL current FL speed heading a/c equipment weight category destination : FL 125 : FL 210 : 360 kts : 182 : 3-D : medium : EDDF
    SAS171 210 36 125 0 182 B737 EDDF -1820 0 3D M

    deceleration 300 kts -> 250 kts

    descent FL 100 -> FL 80

    Metering Fix GEDERN (GED)

    descent FL 80 -> FL 70

    descent FL 70 -> 3000 ft

    deceleration 250 kts -> 220 kts

    13

    A PD-2 example: the AMD


    heavy

    3-D / class B

    planning time SAB513: 10:28:20

    4-D / class A

    label colour green: arrival via RUD

    label colour yellow: arrival via PSA

    delay pointer label colour blue: arrival via GED

    actual time at GATE: 10:15

    actual time: 10:15

    aircraft planned for runway 25L

    aircraft planned for runway 25R

    14

    An unresolved AMD issue..


    Eye scanning under various traffic conditions
    Time line

    15

    AMC 282

    Hand-off
    RIVER AMC 282

    10

    Traffic Datalink
    05
    IB E 326 IB E 326

    Pre-acceptance

    15

    An unresolved AMD issue..


    Eye scanning under low traffic conditions

    16

    An unresolved AMD issue..


    Eye scanning under high traffic conditions

    17

    PD3: when the going gets tough, the tough get going...
    Many CWPs! Gate to Gate

    18

    A PD3 example: departures

    19

    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..?


    20

    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, REs, FAA etc. A life time opportunity for improvements!

    21

    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..

    22

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


    by P. Jorna, GHMI Project Leader NLR
    next

    23

    You might also like