ITP CPDLC Ad Hoc Group Status

1. ITP CPDLC Ad Hoc Group Status

2. ADS-B ITP Communication requirements RTCA/EUROCAE approved ADS-B ITP SPR (DO-312/ED-159) requires Direct Controller Pilot Communications (DCPC) Preformatted free text CPDLC allowed until formatted message set standard is developed ITP CPDLC Ad-Hoc Group Formed to support the definition of advanced ATS datalink systems Initial focus: support ITP CPDLC standards development Group includes Boeing, FAA, Airbus, CRISTAL ITP members (Iceland, NATS UK, etc.), Eurocontrol Customer of group is SC214/WG78 (info to SC186) Two primary products Updates to ED-100A/DO258A (Interop), ED-122/DO306 (SPR) as required (complete in 2009) Inclusion into SC-214/WG78 “Safety Performance Requirements For Advanced ATS Data Communication” (complete in 2011)

3. ITP CPDLC AdHoc group – Summary TARGET = APR 2009 (TBC) TARGET = JUL 2009 (TBC) CPDLC for ITP Operational Definition(ITP CPDLC AdHoc group) CPDLC for ITP ISFs(ITP CPDLC AdHoc group) Step 1a ITP Operational Service Description Step 2a Assess ED122/DO306 impact and provide ISF if required Step 2b Provide ED100A/DO258A ISF Step 1b ITP Environment Assumptions CPDLC for ITP in Advanced ATS Datalink(WG78 / SC214) CPDLC for ITP ED/DO Changes Step 3a Validation ED122/DO306 ISF (if any) and provide Change 1 if required Step 4a CPDLC Safety & Performance assessment Step 4b CPDLC Interoperability Step 3b Provide ED100A/DO258A Change 1 CONSISTENCY REQUIRED TARGET = DEC 2009 TARGET = DEC 2011

4. Operational Definition (i.e. Operating Methods & Diagrams, Messages and Parameters) in OSED/SPR Performing the Interop requirements definition in parallel with OSED/SPR update, based DO-312/ED-159 and on the ICAO PANS ATM amendment approved by SASP • Interoperability Requirements definition in two steps • Interop based on existing CPDLC messages (current FANS 1/A systems) • Take into consideration constraints linked with the use of existing messages (e.g. precanned Free Text) • Assess the acceptability of any limitation identified towards the “ideal” solution • Interop based on new CPDLC messages (advanced ATS systems) • No technological constraints • Should encompass what we expect to be the “ideal” CPDLC solution for ITP ITP CPDLC Adhoc Group

5. Existing FANS systems • Planning to provide an Amendment to ED100A • Approach in line with the proposed amendment to PANS ATM approved by SASP • ITP Request • DM9-REQUEST CLIMB TO [altitude] and DM10-REQUEST DESCENT TO [altitude] • DM67-free text for ITP request reference • Providing unambiguous format of each data to be included in the free text • Only 1 or 2 ITP request references supported • Slight change of wording in the global ITP request presentation • ITP Clearance • UM20-CLIMB TO AND MAINTAIN [altitude] and UM23-DESCEND TO AND MAINTAIN [altitude] • UM169-free text for ITP clearance reference • Providing unambiguous format of each data to be included in the free text • Only 1 or 2 ITP request references supported • Slight change of wording in the global ITP Clearance presentation ITP CPDLC Adhoc Group

6. Advanced ATS Systems • Provide an OSED to be included into the SC214 SPR by September Plenary • Note that currently the TORs for SC214 does not include Oceanic applications • Plan to keep the OSED as ‘generic’ as possible to stay included in SC214 no matter the SC214 TORs’ outcome • Provide the list of new CPDLC messages and details to be included into Interop by September Plenary • Approach in line with the proposed amendment to PANS ATM approved by SASP • ITP Request • Change free text DM67 to standard message • ITP Clearance • Change free text UM169 to standard message ITP CPDLC Adhoc Group