1 / 19

EUROCAE WG-78 / RTCA SC-214 Plenary #12 , Configuration Sub-Group

EUROCAE WG-78 / RTCA SC-214 Plenary #12 , Configuration Sub-Group Berlin (Germany) , 11–14 April 2011. CSG Progress Report Next Steps. Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE , (ALTRAN) EUROCAE CSG Co-Chair. Baseline 1/2/3 Scope.

owen
Download Presentation

EUROCAE WG-78 / RTCA SC-214 Plenary #12 , Configuration Sub-Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EUROCAE WG-78 / RTCA SC-214 Plenary #12 , Configuration Sub-Group Berlin (Germany), 11–14 April 2011 CSG Progress Report Next Steps Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE, (ALTRAN) EUROCAE CSG Co-Chair

  2. Baseline 1/2/3 Scope • Plenary #12 Decisions on Baseline 2 scope: • 4DTRAD (/ITBO) Out of B2 Scope but 4DT messages are kept as part of IER/CRD • ADS-C EPP part of SPR but not part of INTEROP • ADS-C Capabilities to support FANS Accommodation • ACTION CSG :To Assess the feasibility for FANS Accommodation of IM Messages • Updated version of Baseline I / Baseline II / Baseline III Chart

  3. Baseline Accommodation Scenarios • Plenary #12 Decisions: • Backward compatibility is part of the Interop and is optional • Backward compatibility is developed for both the Air and Ground sides • Local Business case should drive the BC implementation • Indication of supported “Baseline” capabilities will be exchanged thru DLIC Logon service • example : • a B3 A/C supporting B1 Backward Compatibility shall declare it supports B3 & B1 capabilities in DLIC Logon request • a B3 A/C supporting B1 & B2 Backward Compatibility shall declare it supports B3, B2 & B1 capabilities in DLIC Logon request • ACTION CSG : To figure out the solution to exchange FMS Autolaoding capability (DLIC, CPLDC,…)

  4. CPDLC Message Set Assessment • Contributions feedback • Air Users/System providers don’t provide systematic assessment regarding the operational need for uplink elements,. • Some Clarifications are required (e.g. the need of precision up to the second for each msg element using time parameter, msg elements using the level parameter (and more specially the blockLevel type), use of Conditional Clearance,...) • Validation activities being under progress, further remarks/validation feedback are likely to be provided later this year By all contributors: 17 messages are REQUIRED 16 messages are NOT REQUIRED B all contributors: 21 messages are REQUIRED 4 messages are NOT REQUIRED 171 DOWNLINK 362 UPLINK REQUIRED NOT REQUIRED NO RECOMMENDATION

  5. CPDLC Message Set Assessment • CPLDC Message Set Assessment Proposal for 17 New Messages

  6. CPDLC Message Set Assessment • Need for more contributions • CSG Agreements: • To provide our SC214/WG78 Assessment: • Assessment of each UM/DM message according to the existing contributions and SC214/WG78 expertise • To send to ATM community a SC214/WG78 proposal for review • Objectives: • To present the initial SC214/WG78 assessment to OPLINK in May (Realistic?) • Final review in June CSG Meeting • Then send it for wider review end of June • How : Thru dedicated Webex?

  7. CPDLC / Alert & Urgent Attribute • Review of VOLPE / POS-PL-CPDLC_MessageAttributes_3_30_2011.doc • CSG Agreements • A single attribute, that combines “Alert” and “Urgency” will replace the previously independent “Urgency” and “Alert” attributes: • The Urgency/Alert (URG/ALRT) attribute delineates the Alerting / Queuing Requirements for received messages that are displayed to the controller or flight crew: • Ground:Mandatory. • Air: Optional • List of “Urgent” Messages

  8. Handling of CPDLC Route Clearance • Review of BOEING / Route Loading Considerations.doc • CSG Agreements • This Position Paper has to be improved with others Air & Ground contributions. • No replacement of the current CPLDC Section till mature new section proposal • ACTION CSG : To send out this Position Paper for CSG Review • => To be reviewed during June meeting before integration • Open Issue : Handling concatenation of UM266 CLEARED TO [position] VIA [route clearance enhanced] and UM XX “REST OF ROUTE UNCHANGED”

  9. Other items… • FIM Review • CSG Agreements: • FIM CPDLC Message Definition • FIM OSA Conclusions => No impact on Existing CPLDC OSA • FIM OPA => No impact on existing CPDLC OPA : RCP181 is applicable • => FIM Messages ready for integration in SPR/INTEROP • Open Issue: FIM Tiger Team request for provision of additional Flight Path information of Target A/C in the FIM Messages => CSG request FIM Tiger Team to specify the FP Information which are needed in order to assess the feasibility of Provision in FIM Messages. • Trajectory Synchronization • Review of GE / POS-PL-POS-PL-Trajectory Synchronization v1.doc • CSG Agreements: • To review ADS-C Waypoint parameter (fixname, Lat/Lon & Vertical Type, Optional • To harmonize as much as possible the CPDLC & ADS-C Variables/Parameters • ATS Functions • CSG Agreements: • ACTION CSG : To replace the current section 2 & 3 by the new ATS Function section (section 2)

  10. Meeting Objectives & Priorities • Integration of DSC OSD: • DDA Messages shall be differentiated from CDA Messages. • Instead of using UM285 CURRENT ATC UNIT [unitName], a new message is defined UMXXX DOWNSTREAM ATC UNIT [unitName]. It shall be sent by the DDA  after accepting the DSC Connection establishment. • Pending Issue : • Does DSC require UM233 USE OF LACK PROHIBITED? • Does DSC require LATENCY TIME CHECK (Sending UM340)? • OSA & OPA? • Showstopper: Airbus raised a strong concern to limit the scope of use of • DSC to only Oceanic Clearances.

  11. Meeting Objectives & Priorities • To review initial contributions for CPLDC Messages Set Assessment • To progress on ATS Function • CPDLC • NOT DONE : To address NAT SG Comments and to propose formal SC214/WG78 Response (see NAT CNSG4 WP09 SC214_WG78.doc) • To address the Urgency/Alert Attributes position paper from VOLPE (see POS-PL-CPDLC_MessageAttributes_3_30_2011.doc) • To address the Trajectory Synchronization position paper from GE (see POS-PL-POS-PL-Trajectory Synchronization v1.doc) • NOT DONE : To address comments received from FAA (Steve FERRA) • Reception of a DM when the CPDLC is not yet enabled • To address DSC Showstopper • To review FIM Message definition • Pending PDRs • To progress on OSA/OPA : FIM, NOT DONE : ADS-C, OCR Integration, DSC • ACTION CSG : Capability to indicate the FMS Integration/no integration • ACTION CSG : FANS Accommodation for FIM • Backward compatibility • To review of the Route clearance section • To assess SPR/INTEROP Maturity regarding Baseline 2 Scope • To consolidate CSG Work plan for the next step 11

  12. CSG NextMilestones CSG Proposal to pospone the 31st Oct-4th Nov CSG Meeting to 7th–12th Novto accommodate the end of the FRAC Period.

  13. CSG Main tasks

  14. CSG Meetings & Webex(untill P13) • US, TBD - Call for Proposal! , 20 – 24 June 2011 • Plenary #13, Paris (France), Septembre 2011 • CSG Webew – EachWednesday – Resolution of Comments / PDRs • DedicatedWebex : • Assessment of CPDLC Message Set • DSC & ADS-C OSA/OPA • Handling of Route Clearance • other?

  15. SPR / INTEROP Version I, 1 April 2011, posted on FAA Web site Thankyou 15

  16. Maintenance of SPR/INTEROP (version H) • 244 PDRs (172 atPlenary #11) createdagainst version H: • List of PDRs are accessible on https://sc214wg78.egis-avia@egis.fr/csg/ • 38 PDRs are still “New/Working”: • 23 for SPR (including [SPR/INTEROP] PDRs) • 13 for INTEROP • 2 for Tech Manual

  17. Maintenance of SPR/INTEROP (1/2) • 275 Comments (216 at Plenary #11) received • Most of the 36 « Open/Working » comments are related to 4DTRAD & D-RVR (Baseline 3) • Most of the 22Deferredcomments are waiting for validation inputs

  18. Maintenance of SPR(2/2) • 130 PDRs (including [SPR/INTEROP] PDRs) • 23 PDRs are still New (17) / Working (11) : • 14 « New » PDRs are related to CPLDC/ADS-C OSA&OPA

  19. Maintenance of INTEROP • 107 PDRs : 14 ATS Technical Manual + 93 INTEROP • For INTEROP: • 13 PDRs are still « Working »: • 6 PDRs are related to INTEROP ATN (1 for PICS) • 6 PDRs are related to INTEROP FANS 1/A+ • 1 PDR isrelated to PICS

More Related