110 likes | 242 Views
EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group PARIS (France, Europe) , 26–30 September 2011. CPLDC Message Set Assessment Status. Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE , (ALTRAN) EUROCAE CSG Co-Chair. CPDLC Message Set Assessment History.
E N D
EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group PARIS (France, Europe), 26–30 September 2011 CPLDC Message Set Assessment Status Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE, (ALTRAN) EUROCAE CSG Co-Chair
CPDLC Message Set AssessmentHistory • Increase of the CPLDC Msg Set (as per Doc 44444 Ed 15) to support: • New datlinkoperations (NEXGEN/SESAR): • Interval Management, • Surface Operations (D-TAXI), • 4DTrajectory Management (4DTRAD) • Improvment of existingdatalinkoperations (LINK2000+, Oceanic) • Daily DL operations use a small CPDLC msg set : • OCR (FANS): • S-Pac: ~ 25 msgs out of 182 UM & 80 DM • NAT: Similar figures expected • LINK2K+: • ANSPs select small # of UMs • Growingmsg set is a concern: • More difficult to manage by flight crew • Increaseavionicscosts • HumanFactorsAnalysis (FAA/VOLPE) • => CPLDC MESSAGE SET OPTIMIZATION IS REQUIRED! • Triggered by OPLINKP • Delegated to WG78/SC214 • Coordination with Regional groups (NAT, PAC, LINK2K+ ,etc) • Final Approval of Msg set in hands of OPLINKP • Assessment started in Jan. 2011 • Initial feedbacks from AIRBUS, BOIENG, ISAVIA, NAT, EUROCONTROL, FAA • Coordination with Regional groups (NAT (coordinator : Leifur Hákonarson (Iceland) , PAC, LINK2K+ ,etc) and OPLINK
CPDLC Message Set AssessmentOverview The CPLDC message set is optimized to be more consistent with operational (Oceanic & Continental) needs • New capabilities : • Surface Operations • 4D Trajectory Mgt • FIM • Tailored Arrival, OPD,… • Useless messages are removed • New messages are added or existing messages are updated to support current operations • Convergence with GOLD • ASAS, ITP (ADS-B ops), … • Messages leading critical/safety issues are removed or reworded or replaced
CPDLC Message Set AssessmentOverview 73 New UM Focus on UPLINK 114 UM Unchanged 172 UM Doc 4444 Ed.15 245 UM Required 32 UM Reworded 26 UM Replacement (New variable/Parameter) 99 UM Not Required 26 UM Replacement Doc 4444 Ed.15 73 UM Doc 4444 Ed.15 SPR version I (14Sept 2011)
CPDLC Message Set AssessmentOverview 35 New DM Focus on DOWNLINK 66 UM Unchanged 84 DMs Doc 4444 Ed.15 119 DM Required 6 UM Reworded 12 UM Replacement (New variable/Parameter) 46 DM Not Required 12 DM Replacement Doc 4444 Ed.15 34 DM Doc 4444 Ed.15 SPR version I (14Sept 2011)
245 UPLINK / 119 DOWNLINK are Required (+ ~ 20 UM / 8 DM FIM Msgunderdefinition) • 172 UM / 84 Messages are kept from Doc 4444 Ed.15 • 114 UM / 66 DM are unchanged • 32 UM / 6 DM are reworded, with no change of Message ID, usually to be avoid misleading/confusion: • AT [time) / BY [time] reworded respectively in AT OR AFTER TIME [time] / AT OR BEFORE [time] • AT [position] / BY [position] reworded respectively in AFTER PASSING [Position] / BEFORE PASSING [position] • Other wording improvement examples: • e.g. UM7 EXPECT CLIMB AT [time] is reworded in UM7 EXPECT HIGHER AT TIME [time] • e.g. DM44 ENSUING WAYPOINT (position) is reworded in DM44 NEXT PLUS ONE WAYPOINT (position) • 26 UM / 12 UM are replaced due to new variable/parameter definition to support advanced DL capabilities/services (e.g. 4DTRAD, DCL, Tailored arrival) • some [time] are required to support time expressed in second to support 4DTRAD • e.g. DM34 NEXT WAYPOINT ETA [time] is replaced by DM34R NEXT WAYPOINT ETA [timesec] • some [time] are required to support time expressed in second with a time tolerance to support 4DTRAD e.g. UM58 CROSS [position] AT [time ] AT [level] is replaced by UM58R CROSS [position] AT [RTAtimesec] AT [level] • Main parameters changes: • [Route clearance] replaced by [Route Clearance Enhanced] notably to provide a “Clearance Limit” and a time expressed in seconds. • [Departure Clearance] => [Departure Clearance Enhanced] including more capabilities to provide departure route indication • [Procedure Name ] => [Name Instruction] including more capabilities to provide procedure indication
245 UPLINK / 119 DOWNLINK are Required (+ ~ 20 UM / 8 DM FIM Msgunderdefinition) • 73 UM / 35 DM are New Messages • To support new datalink services (as defined in SESAR/NEXGEN) • 4DTrajectory Management • e.g. UM337 CLEARANCE LIMIT [position] / DM157 PLANNED SPEED IN THE CLIMB [speed schedule] • Surface Operations / D-TAXI • e.g. UM329 INTERSECTION DEPARTURE [intersection] / DM151 REQUEST TAXI UPDATE [position information] • To improve existing operations • ITP • e.g. UM341 ITP [aircraft reference list] • Convergence with GOLD: • some preformatted free text are translate in new CPDLC Message • e.g. UM363 RELAY TO [aircraft flight identification] [unit ID] [relay text] / DM171 RELAY FROM [aircraft flight identification] [relayed text response]
99 UPLINK / 46 DOWNLINK are Not Required • All 99 UM / 46 DM are removed from Doc 4444 Ed.15 CPLDC Message Set • 26 UM / 12 DM are replaced due to new variable/parameter definition to support advanced DL capabilities/services (e.g. 4DTRAD, DCL, Tailored arrival) • 73 UM / 34 DM are removed due to: • No identified operational needs / Not often used in current datalink operations(e.g. CRUISE Messages) • Redundantcy with other Messages (e.g; UM189 ADJUST SPEED TO [speed] is deemed redundant with UM106 MAINTAIN [speed]) • “Misleading/Confusing” Messages (e.g. some EXPECT messages) • Messages leading a safety issue (e.g. UM165 THEN) • Messages that can be accommodated by combination of existing/new messages (e.g. EXPEDITE / IMMEDIATELY Messages)
ONGOING TASK / OPEN ISSUES • Addition of FIM Messages (around 20 UM / 8 DM) – Definition is still under progress • Consolidation of Definition of Flight Deck Automation Status • Loading of route uplinks into the flight plan in the FMS • Loading of data into other systems • Providing assurance of clearance execution • Provision of computed data for reports • Issue: Clarification is also required on how to handle/to consider such avionics capabilities in SPR Standard (Requirement? Recommendation? …) • Few Messages are still under assessment notably D-TAXI Messages
ADS-C & NAT Feedback • Current version (19 August 2011) of ADS-C SPR (Safety and Performance Requirements) availableat: • http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms_services/sc214/current_docs/version_i/media/SPR-I-Part4-ADS-App_19_August_DRAFT.doc • NAT Feedback on current ADS-C version highlydesirable • Commentsinvitedbefore 26 October 2011