CSG Progress Report Melbourne (FL), March 2013 1 EUROCAE WG-78 / RTCA SC-214 Sub-Group Meeting Melbourne (FL), US 25-29 March 2013 CSG Progress Report

CSG Progress Report

Melbourne (FL), March 2013

1

EUROCAE WG-78 / RTCA SC-214

Sub-Group MeetingMelbourne (FL), US

25-29 March 2013CSG Progress

ReportMeeting

ObjectivesWork Organisation

Jane HAMELINK Jane HAMELINK , (THANE)

RTCA CSG Co-Chair

Thierry LELIEVREThierry LELIEVRE, (ALTRAN)

EUROCAE CSG Co-Chair

CSG Progress Report


2Weekly CSG Webex

SC214/WG78 CSG Meetings and Webex (since Plenary #16, Washington DC, December 2012)

SPR / INTEROP

Version J

26 Nov. 2012

SPR / INTEROP

Version J (March

2013 release)

(Input for Melbourne

SG Meeting)

Consolidated 4DTRAD OSD

SC217/WG44 Coordination on Airport Mapping Data Base to support D-TAXI Graphical display based on D-TAXI Clearance.

Weekly OSA Webex

Plenary #17, Plenary #17, Webex, Webex,

Jan.2013Jan.2013

CSG Progress Report


Update of SPR Section 1 – Introduction and SPR Section 2 – ATS Functions

Consolidation of 4DTRAD OSD

Dedicated Meeting in Jan 2013, Oakland (CA). 4DTRAD OSD has been consolidated:

• Definition of 4DTRAD Terminology (e.g. 4D Trajectory, 4DTRAD Service Provider, 4DTRAD Clearance, Route Negociation, …)

• Clarification on the use of RTA and Speed Schedule• Removal of Ground-Ground coordination related OR• Clarification / rewording of OR• Simplification of Operating Method Tables• Change in CPLDC Messages:

o (New) UM336 IN THE CRUISE [Speed Schedule]o (Replacement) UM116R RESUME NORMAL SPEED [Flight PhasesO]

=> RESUME NORMAL SPEED

=> RESUME NORMAL SPEED IN THE CLIMB

=> RESUME NORMAL SPEED IN THE CRUISE

=> RESUME NORMAL SPEED IN THE DESCENT

Open issues/actions: To provide relationship with Global 4D Trajectory Based Operation Concept (e.g. references to SESAR & NEXGEN

Concept of Operations) Review new OR organisation (proposed by Greg - on-going) To update ITBO OSD (part of 4DTRAD OSD) speed schedule and interaction with Nav community (e.g. SC227/WG85 or group of experts)

3

Main Achievements since Plenary#16

CSG Progress Report


D-TAXI Coordination (SESAR D-TAXI Team / SC217/WG44 (Airport Mapping Database ED-99C))

Dedicated Webex (Feb 2013) with SESAR D-TAXI Team and SC217/WG44 Use of D-TAXI Clearance text/parameters for graphical display ([TaxiRouteGraphic] parameter is not used) [on-going] Assessment of consistency between D-TAXI Clearance text/parameters and elements/objects used

in Airport Mapping Database. E.g. Extension from 8 characters to 15 characters the lenght of the “Holding Point Name" parameter in order to comply with

operational need and graphical requirement (as per Airport Mapping database, ED99) E.g. Proposed changes in Airport Mapping Database (ED99C) to comply with operational need that are reflected in

SC214/WG78 D-TAXI Message definiton.

Open Issue: AIRBUS Position paper about provision of D-TAXI Graphical data

Resolution of PDR#312 [INTEROP] Ambiguous specification of the ATN default checksum algorithm

Dedicated Webex (29 Jan 2013) with ATN implementors : THALES, EGIS Avia, AIRBUS It is agreed that the modulo 255 should be applied at any time during the computation of the checksum, including during the

last step when computing X0 and X2. Therefore, the checksum must not include a 0xFF byte. In ones complement mode, the result must be identical, therefore the conversion 0xFF to 0x00 must be performed as well on X0 and X2

To remove the ambiguity, an Amendment Proposal (AP) to doc 9880 will be sent to the ICAO WG-M CCB once the CCB is officially created. The AP includes a coding example to be used by implementation to check their encoding.

The support of the AP is documented in the SC214/WG78 INTEROP document No impact on Backward Interoperability

4


CSG Progress Report


Editors Review of B2/FANS Accommodation (PU-30)

The document structure have been re-organised in order to be more consitent (and for clarity) Removal of Accommodation Requirement redundancy (notably between Services, Messages and

Parameters) Improvemement of accommodation requirement consistency Traceability to ED-154 requirements added in an annex

Open issues: To define/confirm operationnal acceptability of some rules for B2/FANS accommodation , e.g.:

• [B2] UM190 FLY HEADING [degrees] => [FANS] UM94 TURN [direction] HEADING [degrees] ? • Conversion of a FANS downlink containing a Position parameter with no Lat/Lon into a B2 Message containing a PositionR parameter for

which the Lat/Lon is mandatory? • Rules for accommodation of Speed Schedule Messages (which are not in FANS) :

» [B2] UM116R RESUME NORMAL SPEED [Flight PhaseO] => [FANS] UM116 RESUME NORMAL SPEED [+ UM169 ‘IN THE <phase of flight>’]

» [B2] UM334 IN THE CLIMB [speed schedule] => [FANS] UM169 ‘IN THE CLIMB’ + UM106 MAINTAIN [speed] [+ UM106 MAINTAIN [speed]]

» [B2] UM336 IN THE CRUISE [speed schedule] => [FANS] UM169 ‘IN THE CLIMB’ + UM106 MAINTAIN [speed] [+ UM106 MAINTAIN [speed]]

» [B2] UM335 IN THE DESCEND [speed schedule] => [FANS] UM169 ‘IN THE CLIMB’ + UM106 MAINTAIN [speed] [+ UM106 MAINTAIN [speed]]

• DCL Accommodation rules: [B2] UM73 is converted into [FANS] UM80. What happened when B2 UM73 is concatenated to [B2] UM80? What happened when [B2] UM73 sent alone? Etc… See PU-30 (UM73R and chapter related to DCL)

5


CSG Progress Report


CPLDC

Provision of Speed Qualifier (At, At or greater, At or less) in RouteClearanceR / Route information additionalR / WaypointSpeedLevel parameter (SC227/WG85 Cmt#9)

Main changes in CPLDC Messages Set:o (New) UM252 URGENT ATC MESSAGE ELEMENT with a "N" response attribute and an "H" alert attribute is created to support

message alerting function.o (New) UM336 IN THE CRUISE [Speed Schedule] to allow provision of Speed Schedule clerance during the Cruise flight phaseo (Replacement) UM116R RESUME NORMAL SPEED [Flight PhasesO] to allow cancellation of Speed Schedule « constraint »

=> RESUME NORMAL SPEED

=> RESUME NORMAL SPEED IN THE CLIMB

=> RESUME NORMAL SPEED IN THE CRUISE

=> RESUME NORMAL SPEED IN THE DESCENT

Open Issues: Clarification for DCL:

o When UM73 is sent concatenated with UM80, should we repeat the same data (e.g. Departure Airport, …)?o Clarification is required for the parameter ClearedFrom and PositionR used in the [Departure ClearanceR] parameter: Is it always

an Airport?o The [ClearedFrom] provided (departure)Airport and a Ground Location. Does DCL/ClearedFrom require a ground location?o During the Webex it has been agreed to replace [PositionR] by a new variable [ClearedTo] pointing on [PositionR]. Nevertheless It

appears that this parameter can only be a Destination Airport. Does this new DCL/ClearedTo (or PositionR) be only the Destination Airport? If yes, can we replace it by [Destination Airport]?

o When UM73 is concatenated to UM80/UM79, what happens when the clearance limit provided in each message element does not match

[Lateral Deviation] is used to define a deviation from the route. Can it be more than Left, Right or Either Side? (i.e. North, East,…)

STATE PREFFERED LEVEL / STATE TOD => REPORT PREFFERED LEVEL / REPORT TOD? Need for new message (COMPLY WITH PUBLISHED SPEEDS) to comply with published speed constraints when assigning a

speed schedule Status of changes require to support PBN operations?

6


CSG Progress Report


ADS-C

Simplification of EPP Event Contract: The 11 EPP Change Events are replaced by 3 EPP Events:

EPP Window and EPP Reporting Window are merged into one EPP Window RTA Status Change event triggers the ETA Min/Max report (no EPP)

7


EPP Flight Plan Change

Triggered when any of the following event occur within the EPP window:

• a waypoint is inserted or deleted

• a lateral offset is entered, modified or deleted

• a level constraint is inserted, modified or deleted

• a speed constraint is inserted, modified or deleted

• a RTA is inserted, modified or deleted

EPP Next waypoint in horizon

Triggered when a waypoint that was not previously within the time reporting parameter is now within that time interval, subject to the 128 point maximum limit of the extended projected profile report

CSG Progress Report


ADS-C (continued)

New Reject Reason for rejecting a EPP Tolerance Event contract request or a ETA Min/Max contract request the when the specified waypoint is not part of the route: “Waypoint not in the route”;

Open Issue: Vertical type is not available for the ETA Min/Max. Is it operationally required? What are use cases for this type? (the case of a

TOD pseudo WPT).

New Turbulence Deviation Event: Triggered when the peak EDR value within the turbulence observation window is greater than the peak EDR threshold as specified

in the event contract request. Triggers the sending of the Met Data report (no EPP)

Open Issues: Does it require a Turbulence data Block independant from Met data Block? To clarify if the turbulence event behavior: does the peak threshold apply to the peak over the turbulence observation window (way

describe in this ADS-C version) or does it apply for the instantaneous turbulence peak? To validate the use of the 15 minutes default value for the turbulence observation window (when not specified)

New definition of Turbulence (in Met Data Block): Refinement of the content of the turbulence information in the ADS-C Meteorological Report in compliance with ICAO Annex 3,

Appendix 4 provisions for routine air-reports and special air-reports. Provision of the Turbulence average and Turbulence Peak (EDR value) within a Turbulence Observation Window.

Open Issue: Airspeed Change / Speed Mach threshold resolution: 0,01 or 0,05?

OSA Consolidation => See Thomas progress report

8


CSG Progress Report


9

SPR/INTEROP Comments/PDRs Status Overview (1/3)

79 PDRs created against version I (1 February 2012) 24 PDRs created against version J (22 June 2012)(total is 425!)

5 PDRs are « Working » and 14 PDRs are « Proposed Fixed » on versions I & J.

CSG Progress Report


5 PDR are “WORKING”:

• 345 [SPR/INTEROP][CPDLC] Addition of New/Reinstated CPLDC Messages• 347 [SPR/INTEROP][CPDLC] Deletion of CPLDC Messages• 419 [SPR/INTEROP][ADS-C] New definition of Turbulence• 428 [SPR/INTEROP][CPLDC] Clarification for use of ClearedFrom & PositionR in [Departure ClearanceR] parameter• 433 [FANS] Review of FANS 1/A INTEROP document

14 PDRs are “PROPOSED FIXED”:

• 312 [INTEROP] Ambiguous specification of the ATN default checksum algorithm• 418 [SPR/INTEROP][ADS-C] EPP Event Simplification• 420 [SPR/INTEROP][CPLDC] Allow the provision of a time tolerance in CROSS AT TIME clearances • 421 [INTEROP] Update the list of AE-qualifiers in doc 9880• 422 [SPR/INTEROP][ADS-C] Mandatory provision of Seconds in Time (new variable [Timesec] • 423 [SPR][ADS-C] Both IAS/Mach cannot be provided in EPP / Estimated Speed • 424 [INTEROP/CPDLC] No use of route clearanc indexes • 425 [SPR/INTROP] [CPDLC] Renumbering of the Relative Speed Clearances UM111R and UM113R • 426 [SPR/INTEROP][CPLDC] Change in UM116 to cancel Speed Schedule • 427 [SPR/INTEROP][CPLDC] New Message UM336 IN THE CRUISE [Speed Schedule] • 429 [SPR/INTEROP][ADS-C] New reason for rejecting for Tolerance event contract and ETA min/Max contract • 430 [SPR/INTEROP] VOLMET NCN - identification of airports for which TAF is not provided • 431 [SPR/INTEROP][CPLDC] Provision of Speed Qualifier in RouteClearanceR / Route information additionalR /

WaypointSpeedLevel parameter • 432 [SPR/INTEROP][CPLDC] D-TAXI / Extension of Holding Point Name parameter to 15 Characters

10

SPR/INTEROP Comments/PDRs Status Overview (2/3)

CSG Progress Report

Melbourne (FL), March 2013SPR/INTEROP Comments/PDRs Status Overview (3/3) (on versions I/J)

No new comment!

See PU-10_SPR-Version_J_Master_Comment_Matrix_March2013 that contains all comments recieved and their resolution status.

11 comments are still working/open

9 related to OSA: To be coordinated with OSA Tiger Team. Are they obsolete?

1 related to D-TAXI: To confirm with DTAXI team the need for providing the taxi duration in UM319. Feedback from D-TAXI Sesar Team is expected by June

1 Editorial (To update DCL figures)

CSG Progress Report


To address Open issues /PDRs

To review EPP Definition (White Paper submitted by Boeing (Gordon))

To update ITBO OSD

To address feedback from ICAO (OPMET) on WP5 – Meteorological Information submitted during OPLINKP5

To progress on OSA

What else?

12

Meeting Objective

CSG Progress Report


13

CSG SESSION ORGANISATION

Monday Tuesday Wednesday Thursday Friday

AM

(9

.00

– 13

.00)

CPDLC Tutorial

Resolution of open PDRs/Issues

CPLDC

(Jane, Fred & Thierry)


Review of THALES

Pos.Paper

ADS-C


OSA/OPA Session

Review of update of

OSA/OPA

(Thomas )

AOB

(Jane & Thierry)

PM

(1

4.00

– 1

7.00

)

Common Session

SG Progress Reports

Review of EPP Definition Paper

Review of ITBO OSD


Review of Rules for FANS

Accommodation


End of the Meeting


CPLDC


CSG Progress Report


1414

Remark ? Comment ?Remark ? Comment ?

CSG Progress Report


1515

SPARESSPARES

CSG Progress Report


16


SPR/INTEROP Status: New version of SPR/INTEROP posted on the FAA Website (PDR/Comment resolution, improvement of SPR/INTEROP consistency and editorial cleaning)

PU-10 SPR Version J:

PU-10_SPR-J_Chapter 1-Introduction_26 November 2012.docPU-10_SPR-J_Chapter 2-ATS Functions_26 November 2012.docPU-10_SPR-J_Chapter 3-ATS Services Description_26 November 2012.doc PU-10_SPR-J_Chapter 3-CM _26 November 2012.docPU-10_SPR-J_Chapter 5-CPLDC _26 November 2012.docPU-10_SPR-J_Chapter 6-ADS-C_26 November 2012.docPU-10_SPR-J_Chapter 7-FIS_26 November 2012.docPU-10_SPR-J_AnnexFGHI_3Dec2012.doc

PU-20 INTEROP ATN Version J : Last version of PU-20 has been split into two documents: PU-20 covering B2 IReq with no B2/B1 BC IReq and PU-70 including B2/B1 BC IReq. (See PDR#403) PU-20-J_ATS_INTEROP_(261112)_Part1-redlinePU-20-J_ATS_INTEROP_(261112)_Part2A-ASN1 CPDLC B2 –redline.docPU-20-J_ATS_INTEROP_(261112)_Part2B-ASN1 ADS FIS redline.docPU-20-J_ATS_INTEROP_(261112)_Part3-ANNEX A TSD redline.doc In replacement of last PU-20-J 22 June 2012 Part 1 to Part 5. No change PIOCS (yet)

NEW - PU-70 B1 / B2 BACKWARDS COMPATIBILITY INTEROP Version J: PU-70 is a new document that includes B2 IReq and B1 Backward Compatibility IReq. (See PDR#403) PU-70-J_ATS_INTEROP_BC_(261112)_Part1-redline.docPU-70-J_ATS_INTEROP_BC_(261112)_Part2-ASN1 CPDLC B2BCB1-redline.doc

PU-30 INTEROP FANS/ATN Version J :

PU-30-J_FANS_INTEROP_ (261112).doc

Documents

CSG Progress Report Melbourne (FL), March 2013 1 EUROCAE WG-78 / RTCA SC-214 Sub-Group Meeting Melbourne (FL), US 25-29 March 2013 CSG Progress Report