OFG Report PSG 21

1
OFG Report PSG 21

• Søren Dissing

2
Overview

• OFG 22 and 23 meetings
• Human Factors material in the operational
  guidance documents
• Reporting of CPDLC problems via R/T
• Voice Read-back - use Mode S Selected FL info
  instead?
• The MONITOR concept
• The CPDLC demonstrator
• - and an old favourite ICAO update

3
OFG 22 and 23

• MONITOR concept
• A fresh look at HF in OPS guidance documents
• CPDLC automation
• Airbus HMI non-deletion of old logs
• DOC 7030 amendment - SES Datalink IR
• EVALINK feedback
• Brief update ANSP plans
• Airbus and Honeywell requests for OPS input
• Next meeting OFG 24 - April 2009

4
HF material in OPS guidance documents

• HF Chapter only in ATC manual
• HF more or less restricted to HMI considerations
• Not sufficiently specific to CPDLC
• Some issues with readability
• Dedicated HF chapters or HF material integrated
  throughout the guidance documents?
• Revision of ATC Guidance material only or ATC and
  Flight Crew material?

5
Scope of HF work in Link2000
Understand changes in controller/ flight crew
tasks
Identify benefits of Link services
Propose mitigation for issues
Identify potential issues
6
Reporting of CPDLC problems via R/T

• Error reports can lead to lengthy exchanges over
  R/T
• - and as such work against the whole idea behind
  CPDLC
• So..
• The OFG discussed and develop guidelines for
• WHEN to report
• WHAT to report
• ..etc.
• Discussed at some length the need for centralised
  reporting/monitoring

7
Reporting of CPDLC problems via R/T
Some guidance already available in Flight Crew
Guidance Manual Section 7.7
8
Use of Mode S Selected FL information

• - One possible way of avoiding voice read-back

9
Problem

• No PM-CPDLC (but were working on it!)
• MUAC Safety Case calls for VRB for
  Profile-Changing instructions
• Irritating, against the spirit
• Was supposed to be relatively short time?
• What about SFL from Mode S ES?
• To confirm proper reception/reaction?

10
Possibilities

• Discussed and agreed the possibility
• Possibly trials to be planned
• See where this would take us
• BUT,
• MUAC nFDPS not before December 2008
• Possibly, PM-Pioneer in same timeframe
• Last, but not least exactly what is contained
  in the SFL parameter?

11
MONITOR concept

• MONITOR vs. CONTACT
• Originally part of CPDLC message set
• Various issues found during early validation
• Workshop Dec 2004
• White Paper
• Operational Concept Document
• Functional Hazard Analysis
• Safety Assessment

12
MONITOR Concept

• What is it supposed to achieve?
• - further reduce voice communication during the
  transfer phase (is it 40/50/60 )
• Where will it be implemented?
• - Will be trialed operationally in MAAS UAC
• What sort of timescales are we looking at?
• - Overall OPS trials stretches to at least 2013,
  but MONITOR is supposed to be in the first stream

13
MONITOR so far

• Establish the fundamental differences between
  Contact / Monitor, both voice and CPDLC
• PANS-ATM (Doc 4444)
• Annex 2
• Annex 10 vol. II
• Annex 11
• PANS-OPS (Doc 8168)
• Doc 7030
• Doc 9694
• (Doc 9426 and 7754)

14
MONITOR Main problems

• Initial Call
• Two-way contact established?
• Confirmation of Flight Level?
• Has the Flight Crew selected the correct
  frequency?
• Synchronisation of Air/Ground and Ground/Ground
  system events
• Clarification to be sought via ANSP Survey

15
Monitor (voice)
16
Monitor (CPDLC)
17
Initial Call 1/3
18
Initial Call 2/3
19
Initial Call 3/3
20
Youve probably seen this .
21
The CPDLC demonstrator
22
DOC 7030 amendment for the IR

• Flight Planning provisions
• Area of applicability
• Specific exemptions
• Additional exemption policies
• Originally to be discussed at COG 13-15 May /
  24-26 June, but
• as final text must be aligned with IR
• PFA to be finalised in October/November
• COG meets next week in Paris

23
OPLINK Panel - reloaded

• Preparatory meeting Montreal 2 5 September
• Two sets of project documents drafted
• Next step presentation to the ANC in November
• Then
• GET THE WORK DONE!

24
Thank You