1 / 13

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group CEDAR RAPIDS (Iowa, US) 24–28 October 2011

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group CEDAR RAPIDS (Iowa, US) 24–28 October 2011. CSG Progress Report Meeting Objectives Work Organisation. Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE , (ALTRAN) EUROCAE CSG Co-Chair. Maintenance of SPR/INTEROP (version H).

mariel
Download Presentation

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group CEDAR RAPIDS (Iowa, US) 24–28 October 2011

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 Configuration Sub-Group CEDAR RAPIDS (Iowa, US) 24–28 October 2011 CSG Progress Report Meeting Objectives Work Organisation Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE, (ALTRAN) EUROCAE CSG Co-Chair

  2. Maintenance of SPR/INTEROP (version H) • 296 PDRs (290 in Paris, September) created against version H: • List of PDRs are accessible on https://sc214wg78.egis-avia@egis.fr/csg/ + 18 for the Tech. Manual • 26 PDRs are still “New/Working”: • 18 for SPR (CPLDC Message Set + OSA/OPA) • 6 for INTEROP (FANS + ASN 1 Definition) • 2 for Tech Manual • 21 PDRs are “Proposed Fixed”: • 18 for SPR (CPLDC Message Set + OSA/OPA) • 3 for INTEROP (FANS + ASN 1 Definition)

  3. Our next CSG Priorities (Overview) Consolidation of SPR/INTEROP (consistently) for next release : • Resolution of open PDRs • To Resolve and Close New/WorkingPDRs • exceptsomePDRsrelated to CPDLC Message Assessment and Editorial • To Closeeach « ProposedFixedPDRs • Review and Integration of ATS Section update • Review and Integration of OSA/OPA update • Resolution of CM / CPDLC / ADS-C / FIS Open Issues • Editorial Tasks

  4. Resolution of PDRs ATN, FANS and B1 INTEROP PDRs : NEW / WORKING PROPOSED FIXED

  5. Resolution of PDRS SPR OSD PDRs : NEW / WORKING PROPOSED FIXED

  6. Resolution of PDRS SPR OSA/OPA PDRs : NEW / WORKING PROPOSED FIXED

  7. CPLDC Open Issues / PendingTasks • To review FIM Messages • To figure out the OR related to the FMS Integration (consistently with need statements in ATS Function Section) • Status of SQUAWK / ADS-B Messages • Status of UM168 DISREGARD • Proposal is to provide an indication of the clearance type it refers to. e.g. DISREGARD [level/speed/crossing/route/etc] CLEARANCE • Assessment of D-TAXI Message (in consequence of SESAR WP Feedback) • Assessment of proposal for new messages (from FAA/ZNY) • CROSS [specified distance][direction] OF [position] AT [time] AT [level] AT [speed] • DCL revisions in ATN and FANS • OPLINK Comments • …. • NAT SG Feedback? • OPLINK Feedback?

  8. ADS-C Open Issues / PendingTasks • To figure out the OR related to the FMS Integration (consistently with need statements in ATS Function Section) • To assess WG85 Feedback: • …. • EPP event details are inconsistent. • Are the event types supposed to be separate request types, or is the EPP event type an enumerated variable? • => style/editorial issue - leaf fields have to be identified as such • EPP event types are too numerous • Operational need for each event type needs to be validated, at least for the events that are difficult to implement in the avionics. (we may need to tell them which event types are difficult.) • => number of EPP events might be reduced in the light of validation feedback • Speed schedules (nominal, min/max) need definition of interpretation, since there are different possible interpretations of the details. • => Action MJ: to check the description of speed schedule is included in the 4DTRAD material for inclusion in final SPR • [Level] variable is just a number with no description of what altitude reference is used or should be used (baro, standard pressure, geometric, etc.). • => Not an issue specific to SC214 – Applicable to FANS also – No CSG action • Crossover altitude • Question about whether or not it is needed, since we now have speed schedule so the ground system could compute it. • If we do need it, needs to be at least 2 values, one for climb, one for descent, possibly step climbs or descents. • Also, should it be a vertical point type so we have the lat/lon and other EPP data for the point? (this would be difficult to provide for some avionics systems.) • Issue forwarded to 4DTRAD group (CSG Webex date TBD) – Define 2 values or delete the crossover level parameter • Transition level needs to be 2 values, one for climb, one for descent. • => Issue forwarded to 4DTRAD group (CSG Webex date TBD) – ok to define 2 values ? • Assumptions about content of EPP report • Speed changes – some implementations may include only next speed change, not all in trajectory. • We have more input to gather based on prototype implementations • Data in the reports that ground systems do not need • Data needed by the ground systems that are not in the reports.

  9. FIS Open Issues / PendingTasks • To Review of ASN.1 SIGMET for Volcanic Ash, Tropical Cyclone and Other Phenomenon SIGMET •  To Define of SIGMET-support CPDLC message • Confirm the approach to handle State Deviations (vs. SIGMET Annex  3) • To coordinate with ICAO (XML definition of ground/ground D-SDIGMET by 2013) • To review of the new FIS addressing requirements • To review outstanding Honeywell SPR comments   • ……

  10. OTHER OPEN ISSUES / PENDING TASKS • OSA / OPA • Review and Integration of OPA/OSA results • ….. • ATS Function • To review of new set of ATS Functions • To Figure out the FMS Integration Justification • ….. • CM • [tbc] Provision of FMS Integration Capability Indication • …..

  11. EDITORIAL OPEN ISSUES / TASKS • Section 1 / Introduction: • To update Acronyms and Definition • …. • Section 3 / OSD : • To Integrate 4DTRAD OSD • To consider VSG Comment on OSD Consistency • ….. • ….

  12. CSG SESSION organisation DO WE NEED PARALLEL SESSIONS?

  13. Remark ? Comment ? 13

More Related