BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Murphy (US), Tim":MAILTO:tim.murphy@boeing.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=iccaiansp@
 aeronav.net:MAILTO:iccaiansp@aeronav.net
ATTACH:CID:010D01AD62C64A4DAC020F80499A4B63@boeing.com
ATTACH:CID:CFD2A3B8A351874E80576C9F36CCE540@boeing.com
DESCRIPTION;LANGUAGE=en-US:ICCAIA NSP Advisors\,\n\nPlease join me if you c
 an for a discussion of a coordinated industry position with respect to the
  timeline for DFMC GBAS.  I’d like to have this discussion and modify IP
  XX so that it can be a better coordinated industry position before it is 
 submitted for NSP/6.  So please read the draft (attached) and come ready t
 o discuss any aspects of the paper that you may not agree with.  Also note
  that Linda Lavik has prepared a proposed compromise schedule (shown below
 ).  I’d like to get everyone’s views before we submit this IP under th
 e ICCAIA banner.\n\nThanks\nTim Murphy\nSenior Technical Fellow\nCommunica
 tions\, Navigation and Surveillance - BCA - Airplane Systems\nOffice (425)
  965-6744 - Cell (425) 280-6844 - Fax (425) 342-5812\n\nLinda’s proposed
  revision to the paper:\n\nIn the GWG telecon on October 14\, there did no
 t seem to be any clear conclusions\, however\, these are some takeaways:\n
 -       A careful review of the concept is needed\, with respect to other 
 operational contexts and use cases than the approach\, landing\, rollout a
 nd take-off phases that the current GBAS concepts are standardized for (AI
  232)\n-       The view of the European Commission is that there is a need
  to target an accelerated timeline compared to the ones above\n-       Inp
 ut from RTCA is needed in order to consider the dependencies with the DFMC
  SBAS MOPS and the future DFMC GBAS MOPS (Jwgs4/WP35)\n\nThe following dra
 ft timeline takes the two first considerations above into account\, but mu
 st be revised to take input from RTCA into account. It is noted that this 
 timeline is expected to require considerable effort from the relevant stak
 eholders. It is also noted this timeline is based on the assumption that t
 he concept review concludes that the preferred concept is similar to the o
 ne investigated by and proposed by SESAR. Both aspects impose some risk on
  the timeline.\n\n2021    Collect requirements from additional operational
  use cases\, evaluate possible concepts against them\nQ4 2021 A high level
  concept (similar to the level of detail currently proposed by SESAR\, wit
 h all options selected) agreed in ICAO and RTCA\nQ4 2022 A detailed concep
 t paper agreed in ICAO and RTCA\, similar level of detail as the 2009 GAST
  D concept paper\nGWG drafting group to start an update package to ICAO SA
 RPs\nRTCA/EUROCAE to start drafting airborne MOPS\nQ4 2024?        A basel
 ine airborne MOPS\nPrototype airborne implementations for validation\nQ4 2
 025?        A baseline development SARPs for GAST F\nPrototype ground impl
 ementations for validation\n2028    A validated GAST F SARPs ready for pro
 posal to NSP\n\n\n
UID:040000008200E00074C5B7101A82E00800000000604A2E5F2DA9D601000000000000000
 0100000001D1186C94EDB334B964601DC85D3B8B0
SUMMARY;LANGUAGE=en-US:ICCAIA GWG Member Meeting
DTSTART;TZID=Pacific Standard Time:20201028T060000
DTEND;TZID=Pacific Standard Time:20201028T080000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20201023T184029Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:virtual
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-409491484
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR