SC-214 / WG-78
Mgt Meeting
15-19 Nov 2010
Rockville, MD – Lockheed Martin
ATN Baselines 2 & 3
CM
CPDLC
D-FIS
Data Communication Standards Publication Plan
DLIC
D
E
C
2
0
1
1
J
U
N
2
0
1
3
SPR for ATN Baseline II
Interoperability Standard for Data
Communication Via ATN Baseline II
Interoperability Standard for an ATN Baseline II
Ground System Providing Service to FANS-1/A+
Aircraft
SPR for ATN Baseline III
Interoperability Standard for Data
Communication Via ATN Baseline III
Interoperability Standard for an ATN Baseline III
Ground System Providing Service to FANS-1/A+
Aircraft
AFN
AMC
ACM
DCL
DDTAXI(t) TAXI(g)
ACL
     



   
   
4DTRAD FLIPINT
IM

PR
D-ATIS D-OTIS
D-RVR D-HZWX
 







  



  

Publication Approach


Proposal FAA DataCom for Two Volumes; end of 2011 and mid 2013
SPR for ATN Baseline II (12/2011)



Support contracting for ground systems
Support non-integrated aircraft
Scope



Interoperability Standard for Data Communication Via ATN Baseline II (12/2011)



Incorporates SPR for ATN Baseline II by reference
Introduces D-OTIS, D-RVR, IM, D-TAXI (graphic), D-HZWX, 4DTRAD
Interoperability Standard for Data Communication Via ATN Baseline III (6/2013)



Supports AFN, FLIPINT, DCL, AMC, ACM, ACL, PR
SPR for ATN Baseline III (6/2013)



Supports DLIC, D-ATIS (subset D-OTIS), DCL, AMC, ACM, ACL, D-TAXI (text)
Not for routine use of complex clearances
Interoperability Standard for an ATN Baseline II Ground System Providing Service to
FANS-1/A+ Aircraft (12/2011)


DLIC, AFN, D-ATIS (subset of D-OTIS), DCL, AMC, ACM, ACL, D-TAXI (text), FLIPINT (incl. EPP), PR
Routine use of complex clearance (ACL extended route variable) requires integrated FMS
Incorporates by reference Interoperability Standard for Data Communication Via ATN Baseline II
Introduces D-OTIS, D-RVR, IM, D-TAXI (graphic), D-HZWX, 4DTRAD
Interoperability Standard for an ATN Baseline III Ground System Providing
Service to FANS-1/A+ Aircraft (6/2013)


Incorporates by reference Interoperability Standard for an ATN Baseline II Ground System Providing Service
to FANS 1/A+ Aircraft
Introduces IM
Resolution to Recs in Pos Papers
Paper1: FAA Issues

2.1.1 Airspace change definition


2.1.2 Operational requirements versus service and application requirements


Response agreed but reference should be to Annex 10/Vol2Ch8, rather than
DO306/ED122 – delegated to CSG – work to be completed by mid April 2011
2.1.3 Mixed “data link capable” fleet operations


Cannot be acted upon yet, pending JPDO input at a later date, deadline for
comments is end of Dec 2010
There is no impact on the SPR. The considerations mentioned in the reply are
removed.
2.1.4 Performance-based framework - RCP





Response modified as follows:
FAA-AVS is requested to provide guidance on specification of technical performance
criteria for the CM application.
Maintain RCP values for selected DFIS services.
Finalise together with OPLINK the revised RCP values and the operational
requirements. . Pending on the outcome, the RCP Manual may be extended with 1 or
2 new RCP values (e.g.RCP 180 & 300). See also item 2.1.1. ‘78/214’: Within the
constraints of statistical approach align the RCP values with those in the RCP
manual.
Delegated to CSG
Resolution to Recs in Pos Papers
Paper1: FAA Issues…cont

2.2.1 CPDLC message set and 2.2.2 CPDLC indications
(modes, incoming messages) and alerts (failures, loss of
connection)

CSG will review the CPDLC message set





Deadline mid April 2011 for DCL, AMC, ACM, ACL, D-TAXI (text), IM,
D-TAXI Graphic,
Deadline end of 2012 for 4DTRAD
The use of CPDPLC Indications and Alerts Attributes has to be
updated, based on feedback from external validation activities. (if
some address that specific point)
For 2011 delivery date, JPDO input is needed by January 10-14,
2011 78/214 SG meeting
Delegated to CSG
Resolution to Recs in Pos Papers
Paper1: FAA Issues…cont

2.2.3 Aircraft’s flight guidance system (e.g., FMC) autoload and
data transfer (e.g., ADS-C EPP, radio freq, clearance data)





In general, all messages containing the Route variable are candidate for
autoload.
A screening of all CPDLC messages for autoload is needed; and the
principle needs to be discussed, including all avionics stakeholders
Additional Ors or Safety Requirements for autoload of CPDLC messages
may need to be defined
There may a safety issue for LINK2000 avionics that can technically receive
complex clearances through UM80; however not all LINK2000 avionics can
act upon the received clearance or meet RCP. The LINK2000 local safety
cases today limits the uplinking to maximum 2 waypoints.
Delegated to FAA by December 31 2010, then CSG by Feb 2011
Resolution to Recs in Pos Papers
Paper1: FAA Issues…cont






2.2.4 D-TAXI textual/graphical consistency/accuracy

Feedback from validation projects are awaited to confirm the requirement for Graphical D-TAXI

The issue needs to be resolved by end of 2012
2.2.5 Partial CPDLC application – harmonization

We confirm our commitment to not support partial builds

FAA AIR will draft objectively verifiable definition of “routine use of complex clearances”
for consideration by CSG at subgroup meetings during the week of 1/10/2011 .
2.3.1 We confirm our commitment to not support partial builds.

Accommodate FANS 1/A+ implementation of ADS-C for Ground system implementations
of ATN Baselines II & III.

ATN Baseline III implementation requires EPP.
2.3.2 OBE
2.4.1 Partial D-FIS

We confirm our commitment to not support partial builds

Utility of proposed services to be assessed jointly with TOPS at January Subgroup

ATN Baseline II incorporates D-ATIS

ATN Baseline III incorporates all defined D-FIS services.
2.5.x To be addressed in meeting of Ad Hoc Management Group (WEBEX)
planned for TBA.
Meetings 2011
SGs
January 10-14
US, FAA Tech Centre, Atlantic City
P12
April 11-15
Berlin, DFS
SGs
June 20-24
US
SGs
Aug29 – Sept2
Europe
P13
Sept 26-30
Europe
SGs
Oct 31 – Nov 4
US
P14
Dec 5 - 9
US – RTCA , DC