Federal Aviation Administration DCIT 39: S1P1 DCL E2E Summary DRAFT To: DCIT All WG From: Data Comm Production SE Date: DCIT 39, 11 March 20154 DRAFT

Federal AviationAdministration

DCIT 39: S1P1DCL E2E Summary

DRAFT

• To: DCIT All WG• From: Data Comm Production SE • Date: DCIT 39, 11 March 20154• DRAFT

2Federal AviationAdministration

DCL E2EDCIT #39, 11 March 2015

High Priority Future Capabilities:#

Function/Topic

Description IOC/Salt Lake City Waterfall Notes

2 Cleared as Field Criteria

Criteria for CAF if SID or SID/transition is applied that does not change anything prior to first filed fix.

If route starting with first fix after SID transition has not changed and controller adds SID or SID/Tfix, then eligible for CAF. Flight deck stakeholders think this is a hazard. Remove this.

Rules relaxed to allow CAF in cases where ERAM adds or changes the SID and/or T-fix, as long as route starting with the first fix after the T-fix has not been changed.TBD

Ensure no ambiguity about how a SID and transition rejoin the route. See details High Critical IOC to prevent uplink if ANY change to SID/Tfix regardless of source.

4

Error Processing and Session Management

Recover from some error without terminating session.

If error and go to voice, then session is also terminated.

TBD Need to clarify conditions for when avionics and ground system are recoverable. High

11 Push DCL Send approved clearance as soon as session established on controller/system approval.

Provide initial clearance as response to DM25 only

TBD At P-30, after system or controller approval, send initial CPDLC departure clearance if flight has logged on. Else queue for logon and send then. High, for waterfall?

18 Contact Uplink - Call Request

Controller request for voice contact by pilot

None TBD Needs operational concept clarification. Would be separate message. High for controller?.



Cleared As Filed Criteria Draft RulesKey Site/IOC:1. IF the Data Comm route, starting from the first

element after the transition fix (if applicable) is changed in any way from the Original Filed route, THEN NOT CAF. This is case for any route amendment after original flight plan filing.

2. IF the route, starting from the transition fix is unchanged, but the SID is changed, THEN may be CAF.

a. For IOC, this is NOT CAF if done by ERAM or if SID is in the Original Filed route.

b. CAF if NO SID in any ERAM route and only done by controller.

3. IF the SID has been removed from original filed route, THEN NOT CAF

4. IF the route, starting from the first element after the transition fix, is unchanged, and the controller adds a SID or SID+transition, THEN CAF

5. IF the route, starting from the first element after the transition fix, is unchanged, and ERAM adds a SID+transition, THEN NOT CAF

6. IF the route, starting from the first element after the transition fix, is unchanged, and the SID+transition or just the transition is changed, THEN NOT CAF

Waterfall:1. IF the route, starting from the first element after

the transition fix is changed in any way, THEN NOT CAF. No change

2. IF the route, starting from the transition fix is unchanged, but the SID is changed, THEN CAF. Relaxes to allow for SID-only changes. No change to uplink

3. IF the SID has been removed from original filed route, THEN NOT CAF. No change

4. IF the route, starting from the first element after the transition fix, is unchanged, and the controller adds a SID or SID+transition, THEN CAF No change

5. IF the route, starting from the first element after the transition fix, is unchanged, and ERAM adds a SID+transition, THEN Enhanced CAF. Change to ECAF uplink

6. IF the route, starting from the first element after the transition fix, is unchanged, and the SID+transition or just the transition is changed, THEN Enhanced CAF. Change to ECAF uplink



BACKUP



Purpose

• Review Updated S1P1 E2E Document for Plenary approval– Comment resolutions– Additional text since January review

• Review key functions planned for IOC or Waterfall– Arrival Transition– Cleared as Filed– Airway-Airway

• Solicit DCIT feedback on future/TBD priorities



DCL E2E Overview

• S1P1 Production System– Initial deployment starting in June 2015 at SLC, then HOU/IAD– End of deployment waterfall by 2016 December

• E2E is designed to represent CURRENT functionality– Updated as S1P1 requirements change– DCP and DCIT will scrub to determine when to update

• Please send comments to:– Carol Burr, [email protected], Bruce Notley, [email protected],

Kevin Grimm, [email protected], Arnol Ketros, [email protected]

– Any format, but spreadsheet was provided

mailto:[email protected]






CPDLC DCL E2E Current Version• Working draft, V1.1, dated 3/02/ 2015• Description

– Aligned with Data Comm Program requirements as of mid-Dec 2014 (WSSD 5.0)

– Includes resolved comments from All WG telecon 1/14/15

• Content changes previously reviewed with All WG1. User must file ICAO FPL for PDC and CPDLC DCL2. If cannot send CAF, then send initial UM79. If unable to send UM79, then send

UM803. If cannot send CAF, and airway-airway with no published intersecting waypoint,

then no uplink. Terminate FANS connection and handle via voice.4. Provide pilot response in separate Dispatch Message to AOC5. When route is included in revised DCL, include SID, transition,

Climbvia/Maintain and climbout even if not changed

• Clarifications previously reviewed with All WG– Departure and/or destination airport is not in route clearance variable for UM79– Immediate termination when handling multiple flight plans (deletion of

unselected flight plan)– Various editorial



Changes since Jan

– Based on additional comments – Functional (open comments needing review)

• NAT Tracks filing – simplified – needs review• Relogon steps – DRAFT needs review• Clarified Cleared as Filed – needs review• Error message content, e.g., free text content• Appendix A. Removed placeholder for ARINC 622 encoding. Does not provide

added value since under the hood only• Appendix E. Clarified what is in IOC vs future builds.

– Arrival procedure without a published transition – SLC and going forward– Cleared as Filed with only SID/ transition changes– Removed Trials tables. This E2E is for new users; start clean

– Editorial• Added section headers and revised numbering. Goal was readability.



Selected Future Capabilities*: Summary # Function/Topic Description IOC/Salt Lake City Waterfall Notes

1

Arrival Transition Fix Processing

Avionics only allows joining an arrival procedure at published T-Fix.

Prevent the uplink of a route that contains an unpublished Arrival T-fix. This includes the first base leg point.

First base leg point will be valid point for entering the arrival procedure, as NO Transition case

See examples

2 Cleared as Field Criteria

Criteria for CAF if SID or SID/transition is applied that does not change anything prior to first filed fix.

If route starting with first fix after SID transition has not changed and controller adds SID or SID/Tfix, then eligible for CAF.

Rules relaxed to allow CAF in cases where ERAM adds or changes the SID and/or T-fix, as long as route starting with the first fix after the T-fix has not been changed.

Ensure no ambiguity about how a SID and transition rejoin the route. See details High Critical IOC

3 Airway-Airway Intersections

Unloadable CPDLC DCL due to airway-airway intersection.

TDLS will prevent DCL uplink for airway-airway, display to controller, terminate session, go to voice.

Coordinated solution with en route. Draft approach is to insert waypoints and lat/lon.

En Route and Tower results should be consistent. TBD avionics fixes.

* Extracted from Appendix E in E2E



Arrival Transition Fix Processing

• Background– Avionics only allows joining a STAR at published T-Fix– When clearance is to a fix other than published T-Fix

• (voice) Pilot loads STAR into avionics, then deletes points prior to STAR entry

• (uplink) There would be a partial load on avionics

• Current IOC Processing– Ground system will only send published Arrival T-fixes in the

route portion of a clearance – Ground system will prevent an uplink if no there is no Arrival T-

fix in the route portion, terminate any session and go to voice• Only impacts UM80 (initial or revised) or UM83• If CAF or UM79, no impact since not in uplink



Current Processing: Example

• RAVNN3 STAR to BWI– Only CSN and RIC are valid Arrival T-fixes– OTT is first fix on base leg (common

join) for CSN and RIC transitions,

• Examples (simplified)– a) Original or Revised Flight Plan - KRDU

BEXGO1 LVL OTT RAVNN3 KBWI – b) Original or Revised Flight Plan - KRDU

BEXGO1 LVL RAVNN RAVNN3 KBWI

•CAF or UM79 - OK– Normal uplink with “as filed/then as filed”

•UM80 or UM83 - no uplink – Lack of published transition results in no

uplink– Go to voice (terminate session if applicable)



Future (Waterfall) Capability: Example• RAVNN3 STAR to BWI

– Only CSN and RIC are valid Arrival T-fixes– OTT is first fix on base leg (common join) for CSN

and RIC transitions,

• Example (UM80) components (simplified)• a) Original or Revised Flight Plan - KRDU BEXGO1

LVL OTT RAVNN3 KBWI – CAF or UM79 – OK. Build normal uplink. – UM80 or UM83 – Uplink RAVNN3 with no transition.

(proceduretransition = is not present, as it is optional variable) First fix on base leg (OTT) will be identified by ground automation

– Avionics interprets this as entering the STAR at the common join point (OTT)

– OTT would be last fix in route clearance variable

• b) Original or Revised Flight Plan - KRDU BEXGO1 LVL RAVNN RAVNN3 KBWI

– CAF or UM79 – OK. Build normal uplink. – UM80 or UM83 – No uplink. Mid-stream joins are TBD



Cleared As Filed (CAF) Criteria

• Current Processing– Filed/Amended Flight Plan

• Ground automation compares the proposed route to the originally filed route to determine if CAF eligible. If equal, then eligible for CAF

• Comparison includes complete, merged route, which has any PDR/PDAR (SID or SID/STAR) included – Published SID/Transition – Published SID/Transition fix plus additional route elements– Route elements and no published SID/Transition– PDAR can include arrival procedure/transition, e.g., STAR

– If there is no SID/Transition in the filed or amended flight plan and controller adds, then eligible for CAF

• Operational Feedback– Allow flights to get CAF if the only change is the addition of the SID by ground automation

• Voice CAF does not include SID• SID is not included in the loadable portion of the route clearance (only included as free text UM169)

– Allow flights to get CAF if the only change is the modification of the SID or transition as long as join back to the route is visible

• Future Capability– In progress, needs to be worked with SE and DCIT WGs– Concept of “Enhanced CAF (ECAF)” UM169 to ensure connection back first fix in route – Would apply to CAF and Initial UM79 format



Cleared As Filed Criteria Draft RulesKey Site/IOC:1. IF the Data Comm route, starting from the first

element after the transition fix (if applicable) is changed in any way from the Original Filed route, THEN NOT CAF. This is case for any route amendment after original flight plan filing.

2. IF the route, starting from the transition fix is unchanged, but the SID is changed, THEN may be CAF.

a. For IOC, this is NOT CAF if done by ERAM or if SID is in the Original Filed route.

b. CAF if NO SID in any ERAM route and only done by controller.

3. IF the SID has been removed from original filed route, THEN NOT CAF

4. IF the route, starting from the first element after the transition fix, is unchanged, and the controller adds a SID or SID+transition, THEN CAF

5. IF the route, starting from the first element after the transition fix, is unchanged, and ERAM adds a SID+transition, THEN NOT CAF

6. IF the route, starting from the first element after the transition fix, is unchanged, and the SID+transition or just the transition is changed, THEN NOT CAF

Waterfall:1. IF the route, starting from the first element after

the transition fix is changed in any way, THEN NOT CAF. No change

2. IF the route, starting from the transition fix is unchanged, but the SID is changed, THEN CAF. Relaxes to allow for SID-only changes. No change to uplink

3. IF the SID has been removed from original filed route, THEN NOT CAF. No change

4. IF the route, starting from the first element after the transition fix, is unchanged, and the controller adds a SID or SID+transition, THEN CAF No change

5. IF the route, starting from the first element after the transition fix, is unchanged, and ERAM adds a SID+transition, THEN Enhanced CAF. Change to ECAF uplink

6. IF the route, starting from the first element after the transition fix, is unchanged, and the SID+transition or just the transition is changed, THEN Enhanced CAF. Change to ECAF uplink



Airway-Airway Intersections• Background

– Airway-airway intersection without a published intersection results in undesired uplink• Many users prevent from filing

– Currently, the FAA has published preferred/playbook routes that apply airway-airway intersections on top of filed flight plans

• Being reviewed and deleted as part of a larger route loadability effort• Also applies to the en route domain

• Current IOC Processing– Ground will prevent an initial or revised CPDLC uplink with airway-airway in the route portion of the

clearance• If eligible for a UM79 and the airway-airway intersection is after the TO point, then the ground system will

send a UM79• If initial uplink was able to be sent as CAF or UM79, a revised UM83 may be able to be sent later if the

airway-airway intersection is prior to the AT point– If uplink cannot be built, display error to controller, terminate session (if applicable), go to voice.

• Future Capability– In progress, needs to be worked with SE and DCIT WGs– Will be consistent with en route capability

• Current draft proposal is to add exit/entrance waypoints for the airways, and a calculated lat/lon intersection to the uplink



Summary – 2/5 # Function/Topic Description IOC/Salt Lake City Release Notes

4

Error Processing and Session Management

Recover from some error without terminating session.

If error and go to voice, then session is also terminated.

TBD Need to clarify conditions for when avionics and ground system are recoverable. High

5 Ground system acceptance/rejection of downlink message concatenation with UNABLE

Pilot can send DM1 "Unable" + DM65 "DUE TO WEATHER".

Current S1P1 behavior is to accept UNABLE and ignore the concatenated element.

TBD For S1P2, plan to support DM65 and DM66 for display in en route but TBD for tower

6 End Service Uplink with concatenated free text

Provide rationale when feasible and applicable

No error rationale uplinked TBD

7 PBD/FRD PlaceBearingDistance/ FixedRadialDistance in flight plan. PBD/FRD in some uplinks are not loadable

Changes to en route automation adaptation to address radials, which are not ever uplinkable. PBD/FRD will be sent, some of which are unloadable.

TBD MED How many aircraft are affected.? But individual impact is high.



Summary – 3/5 # Function/Topic Description IOC/Salt Lake City

Release

Notes

8

Non-standard departure clearance request downlink

Processing if downlink not a DM25 or if concatenated elements results and error processing.

a) If DM67 (freetext),b) any message element

other than DM25 orc) c) appended free text

to the DM25, then error

TBD See details.Clarify operational requirements and desired enhancements.Revisit messages. Med

9 Lat/long format Resolution/character length of lat/long in TO point in UM169 versus waypoints in UM79 position variable

UM169 “TO” point will be truncated will be truncated (not rounded) to the minute and be sent as Direction, Hours, Minutes.

TBD TBD if still an issue. Med. Could send a UM169 warning, but not common.

10 Loadable SID with expected departure runway.

Requires ground system to have expected/assigned departure runway and match runway to procedure to make loadable.

No loadable SIDs. SIDs are in UM169 only.

TBD Electronic flight data (TFDM) program scope was reduced at IID in March 2015. Will need to investigate other implementation options. Medium

11 Push DCL Send approved clearance as soon as session established on controller/system approval.

Provide initial clearance as response to DM25 only

TBD At P-30, after system or controller approval, send initial CPDLC departure clearance if flight has logged on. Else queue for logon and send then. High for waterfall?



Summary – 4/5

# Function/Topic Description IOC/Salt Lake CityReleas

eNotes

12

Expanded Automode

Expand automode to include:a. revised initial CPDLCsb. non-trajectory changing revisionsc. trajectory changing revisions

No automode for any type of revisions.

TBD .

13 Multicast - ATIS Code

ATIS Code uplink to one or more aircraft.

None TBD

14 Multicast - Stuck Mic

Stuck Mic uplink to one or more aircraft.

None TBD High/ Med

15 Multicast - Advisories

Advisory information uplink to one or more aircraft.

None TBD See items on Call Requests and CPDLC service outage notificationHigh/ Med

16 Multicast - Altimeter Settings

Altimeter setting uplink to one or more aircraft.

None TBD



Summary – 5/5

# Function/Topic Description IOC/Salt Lake CityReleas

eNotes

17

Contact Downlink – Call Request

Pilot request for voice contact by controller.

None TBD Needs operational concept clarification. Would be separate downlink message - consider DM20 and maybe DM21. Remove.

18 Contact Uplink - Call Request

Controller request for voice contact by pilot

None TBD Needs operational concept clarification. Would be separate message. High for CD.

19 AOC Dispatch Message Notification on CPDLC outage

Provide notification using existing AOC Dispatch message, i.e., “Type B”, for tower outages.

None TBD Current DCIT agreement is to handle via procedures. Need to explore en route dispatch message option using SWIM data publication. Remove.



BACKUP



Error Processing

• IOC/Initial: – Responses to DMs

a. If DM67 (freetext), then error with UM159 + UM169 “FREETEXT NOT SUPPORTED”

b. If any message element other than DM25 or DM67 to request the Departure Clearance, the Ground System will respond with UM162 SERVICE UNAVAILABLE.

c. If the aircrew appends any message element to the DM25, the Ground System will respond with UM159 [errorinformation=unexpectedData] + UM169 [ATSU CANNOT PROCESS DATA APPENDED TO CLEARANCE REQUEST]



Waterfall Change to allow CAF• Filed FP: KSLC TCH./.KJFK• ERAM Processed FP with ADR with a SID/Tfix only applied:

KSLC.LEETZ3.HOLTR.TCH./.KJFK– ADR = LEETZ3.HOLTR– SID =– LEETZ3, SID Tfix = HOLTR– First fix after Tfix= TCH

• Result– Today, this is NOT CAF (would get initial UM79– Waterfall, will be CAF

• Rationale– TCH is first fix after SID Tfix and route is unchanged from original filed route, connecting back at

TCH– Today, if controller added LEETZ3.HOLTR rather than ground automation, would be sent as CAF

• Examples (in progress)– CLEARED TO TCH VIA HOLTR– LEETZ3. HOLTR– AFTER TCH CLEARED TO KBWI ARPT AS FILED, CLIMB VIA SID.....or– CLEARED TO KBWI LEETZ3.HOLTR TCH THEN AS FILED

CLEARED TO TCH VIA HOLTRLEETZ3.HOLTRAFTER TCH CLEARED TO KBWI ARPT AS FILED, CLIMB VIA SID

orCLEARED TO KBWI LEETZ3.HOLTR TCH THEN AS FILED



Change to allow CAF if only SID change

• Filed FP: KSLC.LEETZ3.HOLTR..TCH..EMI…• ERAM Processed FP with ADR that replaced SID, same

Tfix: KSLC.PECOP2.HOLTR..TCH..EMI…– ADR = PECOP2.HOLTR – SID =– PECOP2 (PECOP is common point)– SID Tfix = HOLTR– First fix after the SID Tfix= TCH

• IOC Result = NOT CAF (Near term)– Rationale = Although filed flight plan included SID, if the only

change was to replace the SID, then still in Near Term, not eligible for CAF.

• In end-state, this would be eligible for CAF – CLEARED TO KBWI PECOP2.HOLTR THEN AS FILED



Enhanced CAF (Draft):Example• Change to SID and Transition in UM169 portion• Filed FP: KSLC.SLC2.SLC..TCH… • ERAM Processed: KSLC.LEETZ3.HOLTR..TCH...

• ECAF:– Add TCH to the UM169 portion of UM69 for CAF or Initial

UM79– CLEARED TO TCH VIA HOLTR– LEETZ3.HOLTR– a) AFTER TCH CLEARED TO KBWI ARPT AS FILED, CLIMB VIA SID

or – b) CLEARED TO KBWI LEETZ3.HOLTR TCH THEN AS FILED

Documents

Federal Aviation Administration DCIT 39: S1P1 DCL E2E Summary DRAFT To: DCIT All WG From: Data Comm Production SE Date: DCIT 39, 11 March 20154 DRAFT