summary of the ninth meeting joint rtca special committee 217 ...

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 1SUMMARY OF THE ELEVENTH MEETINGJOINT RTCA SPECIAL COMMITTEE 217EUROCAE WORKING GROUP 442 nd thru 5 th of April 2012Brussels, BelgiumHosted by SESAR A6 GroupExecutive SummaryRTCA SC-217 met jointly with EUROCAE WG-44 for the Eleventh Plenary at facilities ofthe SESAR A6 Group in their offices in Brussels, Belgium from April 2 nd to April 5 th , 2012The focus for this meeting was on preparing DO-276/ED-98 (User Requirements forElectronic Terrain and Obstacle Data) for the Final Review and Comment (FRAC)process, and on the Airport Surface Routing Network Validation and Verificationdocument.Updating the DO-276/ED-98 document is basically completed. The meeting addressedoutstanding issues pertaining to the content.The content of the new ASRN V&V document has been outlined. First drafts of scope,methodology, and roles and responsibility sections have been written. The meetingfocused on Section One, which has now reached the mature draft status. An action itemroad map was agreed and a point of contact within the committee for ensuringcompletion of the road map was established.The group discussed the need for future releases of the standards DO-272/ED-99 andDO-291/ED-119 and related ToR proposals as well as the potential for involvement infuture releases of DO-200/ED-76 and DO-201/ED-77.The next meeting will be held at RTCA Headquarters in Washington D.C. from June 18ththrough June 22, 2012. This will be the FRAC Resolution Meeting for DO-276/ED-98.1 Introduction1.1 OpeningThe joint RTCA SC-217 and EUROCAE WG-44 Meeting was opened by John Kasten(RTCA SC-217 chairman) and Stephane Dubet (EUROCAE WG-44 chairman).Stephane Dubet provided a briefing on the SESAR A6 Group that was facilitating themeeting and worked through logistics for the week.The minutes from the last meeting in Phoenix were accepted.

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 21.2 Round RobinAll participants were introduced in a round robin. The attendance list is attached.1.3 Schedule & AdministrationThe Agenda was reviewed and some timing adjustments made to accommodateavailabilities. This meeting was focusing on the following items• Terrain & Obstacle• ASRN Validation and Verification• Discuss how to address the new ToR to the PMCAll presentations made during the meeting are available on RTCA SC-217 Workspace.1.4 RTCA Records of MembershipJohn passed around the attendee sign in sheet for RTCA.1.5 SC-217 Membership ChangesLisa Haskell (Jeppesen) announced that this meeting would be her last meeting due tochanging jobs and responsibilities within Jeppesen. Lisa was lead on the Content Sub-Group and will need to be replaced in that role should a ToR extension be approved.Christian Pscherier (Jeppesen) previously informed the co-chairs that he would nolonger be able to attend the meetings, at least for the year 2012, due to priority workassignments within Jeppesen. Christian was the SC-217 Secretary and will need to bereplaced. No decisions were made at this meeting due to the limited participation. JohnKasten indicated he would create the minutes for this meeting in Brussels and wouldlook to the group for a new Secretary for the June Meeting at RTCA HQ. Stephen(Steve) Moody of Jeppesen joined the group for his first meeting. Steve works in theJeppesen Corporate Technical Standards Department and has an extensive aviationinformation background.2 Presentations & Report outs on Action Items2.1 ToR updatesMike Burski provided a briefing on the March RTCA PMC meeting where the discussionpaper submitted by SC-217 on the need to address updating DO-200 and potentiallyDO-201 was reviewed. The essence of the briefing is that the FAA PMC membershiphas been tasked with performing a review of the update needs from the FAAperspective, with a request to submit a letter to the PMC for the June 2012 meeting. Asthe official PMC Meeting minutes were not available, the exact task definition was notavailable. Mike will provide this as soon as it does become available.The current ToRs cover:• DO-276B/ED-98B (June 2012)• ASRN Verification and Validation (DO-xxx) (Dec. 2012)NOT covered are:

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 3• Update of DO-291/ED-119 due to DO-276/ED-98 update• New DO-272x/ED-99x updated content and reformatting• New DO-291/ED-119 due to DO-272x/ED-99xUpdate Rational for DO-272/ED-99x are:• Avionics manufacturers are missing some essential data, which the group wasnot able to include in the time frame for DO-272C/ED-99C due to workload.Examples include Notes or low visibility taxi.• AEEC ARINC 816 Working Group has agreed to allow DO-272/ED99 to be thecontent driver for ARINC 816. They have identified a set of additional attributesrequired for their work.• The general structure of document needs a revision.• Completion of the ASRN for the entire airport surface, to include aprons andparking stands.• Evaluate what is required to move towards SWIM, i.e., is the current AMDBstructure compatible with a SWIM network.• Ensure complete ASRN through a review of current ASRN from the ATC air andground users’ perspective.• Also impact from other committees deliverables (i.e. SC-206 and SC-214/WG-78) with regard to ASRN must be included.• Consistency in the release of DO-272/276/291 / ED-98/99/119.The group agreed that the above rationale must be developed and presented to thePMC for an updated ToR at the next available meeting in June 2012 to ensurecontinuity.2.2 Document Time Lines2.2.1 DO-276/ED98, “B” Version in June 2012, “C” Version in December 2013.2.2.2 DO-272/ED-99, “D” Version in December 2013.2.2.3 DO-291/ED-119, “C” Version in December 2013.2.2.4 DO-xxx (ASRN V & V), “Original” in December 2012.2.2.5 DO-200/ED76, “B” Version in December 2013 (pending PMC action).2.2.6 DO-201A/ED-77, no time line proposed as approval uncertain.2.2.7 General desire within SC-217 to continue expressing to RTCA Management theneed to have these documents being worked in a sustained effort.

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 42.3 Activity report from the Sub-Groups2.3.1 Data Quality (non-numeric), Applications, Content,Connectivity, Temporality and Data Quality (numeric).These sub-groups are currently not active, pending ToR updates.2.3.2 Britta Eilmus: GuidanceIt was noted that a “Guidance Document” is within the Terms of Reference for EurocaeWG-44 but not for RTCA SC-217. Britta reported that a document based on DO-272B/ED-99B and DO-291A/ED-119A is very near completion and could be ready forreview at the June 2012 Meeting. Work has not begun to update this to the currentversions. As this is not an RTCA document, the review process will follow Eurocaeguidelines.It was noted that Eurocontrol did much of the original work on the Guidance MaterialDocument and has expressed the need for this document to be made available to theuser community at no-charge. Neither RTCA nor Eurocae has a mechanism for nochargedocuments, although it is possible to have a “Report” issued by Eurocae (withoutcharge) provided the document does not include requirements or has been selected foran “ED” status.Decision was to further discuss the publication options with Eurocontrol and Eurocaeand agree on a course of action.2.4 Allan Hart: Status of Terrain and Obstacle(Presentation and Draft Documents to be made available on the RTCA Workspace)The group held monthly telecons to work on the open action issues.Allan present draft version 9 of DO-276/ED-98. This version had been circulated withinthe committee and a significant comment document was received from Tim Roe (not inattendance). Allan had previously incorporated any comments that were editorial innature. Allan walked the group thru the remaining comments. Not all comments weresufficiently understood or resolvable without further conversation with Tim and Allanindicated he would set up a telecom for April 16 th for that work.The group spent considerable time on paragraph 3.3.10 “Height” in the document.Discussions included “how many points in a line obstacle” and was there a requirementfor both a maximum (included) and a minimum(not included) height value. Allan willwork towards resolution within his sub-group.Other important discussion items included: deciding on a “name” for Area 2 as ICAOAnnex 15 uses a “sentence” to describe the area but no simple name; reviewing thenumerical requirements in Section Four; reviewing the attributes for lighting and markingof obstacles and how that relates to similar attributes for Vertical Polygons in DO-272;discussion on the title for Section Six; acronym list clean-up and a qualified review ofAppendix “C”.

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 5A number of items that were beyond “committee editing time available” weredocumented as Action Items for Allan and the sub-group to review and resolve (SeeAction Item List).The time line for the document leading up to FRAC resolution during the June 2012 wasdiscussed:- FRAC Version of Document to RTCA no later than April 25 th , 2012.- Close of comment period will be May 25 th , 2012- Allan to be focal point for comments, copy to the co-chairs- Allan requests that anyone provide comments other than editorial ensure theyare at (or represented at) the June FRAC Resolution Meeting at RTCAHeadquarters.- Ensure (with RTCA) that both PDF and Word Documents are available forreview.- Ensure with RTCA that they can provide the line numbered version forcomment.It was noted that as of the meeting time, the issue of re-use of the ICAO Annex 15illustrations for the Areas 2 through 4 had not been received but was being worked byRTCA. The chair noted that the illustrations were required and would have to beincluded.Another open topic is that Vertical Structures in AMDB may be identical with points in theTerrain and Obstacles database. While the committee has work to do make sure thatthe data structures are compatible, vendors will have to address the issue of the samedata captured twice.

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 62.5 RTCA Policy Regarding Electronic Plenary, MeetingLocations and Travel Restrictions.2.5.1 Various RTCA committee member questioned whether there had been anyprogress made within RTCA with regard to conducting Plenary Sessions usingcommunications technologies rather than physical presence. Also questioned inthis discussion was the perception that the RTCA PMC seemed to be morefocused on FAA input rather than industry input and whether this was in line withthe expectation of the participants. Each member of RTCA SC-217 hasvolunteered time and resources with the understanding that the work of thecommittees is more focused on providing industry with the documentation andguidance necessary to meet the needs of the end user and less on meeting theregulatory needs of the FAA. Lack of industry drivers makes travel that muchmore difficult to justify and the use of communications technologies that muchmore important. There was no further information available on either of thesetopics.2.6 Eurocae and ED-76/ED-772.6.1 Stephane Dubet, Eurocae co-chair briefed the group on the activities withinEurocae with regard to updating ED-76 and ED-77 (DO-200 and DO-201). It wasnoted that while the official status is still the same as briefed in December duringthe Phoenix meeting (ED-76 part of WG-44 ToRs, ED-77 under review) moreconsensus regard to the needs was being realized. The two co-chairs will bemeeting with Eurocontrol later in the week on this subject and its relation to ADQ1 and 2. The ADQ process are basically “top-down” where as the approach toupdating the underlying documents would be “bottom-up”; which is consideredthe preferred method voiced by the industry.2.6.2 Gary Livack asked for and Stephane detailed the differences between ADQ-1and ADQ-2 for better understanding. ADQ-1 processes stop with the Statespublication responsibilities (ANSPs). ADQ-2 starts at that point on continuesthrough to the end user. It was pointed out that the current ED-76/77 and DO-200/201 language with regard to the “last mile”, getting any kind of aeronauticallyrequired data loaded for use on the flight deck is lacking in detail and one areathat truly needs to be addressed in any potential updates. Allan Hart (co-chair ofRTCA SC-206 in addition to his membership in SC-217) talked about the globalconcepts of Data Quality for all data this is intend for use on the flight deck andthe concepts that the current “by data type” implementations need to betterapproach.2.6.3 The wrap-up of this discussion confirmed the groups position on the needs forupdating DO-200A and its impact on the tasks related to the RTCA ISRA issuedto SC-217 by SC-206 (see item2.7 below), the importance of getting themessage to the FAA PMC membership and the need for getting ToR drafts (withand without DO-200/DO-201A) in front of the PMC at their June meeting.2.7 RTCA SC-206 Issues ISRA to RTCA SC-217

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 72.7.1 RTCA SC-206 (Aeronautical Information Services (AIS) and Meteorology(MET) Data Link Services) has issued an Inter-Special CommitteeRequirements Agreement (ISRA) to RTCA SC-217 – a request to provide inputon Data Quality Requirements for all of the types of data that SC-206 isconsidering. Allan Hart, co-chair of RTCA SC-206 reviewed for the group thepurpose and intent of the issuing the ISRA. The ISRA is in the format of therequired form and a spread sheet that lists areas of data and attributes of thoseareas. John Kasten asked whether there was a time line associated with theresponse to the ISRA as it appears that considerable effort will be required torespond. Allan indicated no specific time line had been established. Johninformed the group that he would take a first stab at addressing the spread sheetto get a better idea of the processes to be used and the areas of expertiserequired to complete the response.2.7.2 Gary Livack pointed out two areas of particular concern that he is hearing in thevarious industry meetings that he attends, namely weather and the underlyinggeopolitical “polygons” that would be required to support current methods ofsevere weather announcements. Gary also pointed out the significantrequirements to support NOTAMs. Gary took an action item to provide the groupwith samples of the kind of weather and NOTAM data that were providing thebackground to his questions. John noted that these items will be addressed inthe response to the ISRA as far as they are part of the request.2.7.3 Gary Livack questioned whether or not the group felt that the current ASRNprovisions were sufficient to support voice – activated applications. While this isnot part of the SC-206 work, Gary felt the needs should be investigated in amanner similar to the work planned for the ISRA review.3 ASRN Verification and Validation Document3.1 V & V Document Road Map/Action Item List3.1.1 The group reviewed the road map/action item list for the draft document andnoted that many of the assignments made have not yet been completed. As themajority of the assignment were to group members who were not able to be atthe Brussels meeting, not much time was time was spent on this listing.3.1.2 Mike Burski was at the meeting and presented his paper on the ATC Operationsaspects that needed to be addressed in the document. Mike noted that the inputhe was providing was not yet ready for incorporating into the draft document andwas being provided as a first time. As the discussions evolved, the group wasable to incorporate most of what Mike had written in the correct portions of thedocument with a complete review. The reminder of the paper was added to thedraft in a “still to be reviewed” state.3.1.3 Gary Livack suggested that it might be appropriate to create a “mini-conuse”section for the document. Stephane Dubet agreed that such wording is important

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 8but questioned whether or not it should be included in DO-272/ED-98 instead ofthe V & V Document. Beby Rakotoarindriaka indicated that she sees a problemwith this as it goes beyond requirements and into the applications. Her pointswere well understood and a decision to solicit further input from Brian Gilbert ofBoeing (not present) as to his thoughts in the subject. After some discussion, itwas agreed to add an operational concepts portion to the draft document and tokeep open the matter of updating DO-272 for future consideration and action.3.2 V & V Draft Document3.2.1 The group reviewed the current version of the draft document and agreed thatwith that and the input from Mike, progress could be made on writing SectionOne. The result is there Section One (Introduction and Scope) has reached the“mature draft” status.3.2.2 Much of the paper from Mike Burski was used to create the new OperationalConcepts portion of the document. It was noted, however, that more groupreview of this portion would be required.3.2.3 The other portions of the document were reviewed during the work on SectionOne and the appropriate changes in positioning of some of the content weremade.3.3 Next Steps3.3.1 The Road Map/Action Item listing was updated and Beby Rakotoarindriaka wasappointed to be the focal of ensuring that the required inputs would be availablefor draft work and ready for review at the June and subsequent meetings.4 Closing plenary session4.1 Next meetingsDue to conflicts, the group discussed options to reschedule the next meeting. Theoriginal dates from September 10 (Mo.) to September 14 (Fr.) turned out to be the bestcompromise but the location had to be changed. It was agreed that a full week meetingwill be required to get the V & V Document ready for FRAC. This September meetingwill be held in Europe at a location to be determined.Long-term meeting schedule:• June 18 – 22*, 2012, US (RTCA HQ. Washington D.C.) (FRAC Resolution forDO-276B)• September 10-14 2012, Europe (Prague, hosted by Honewell)• December 10-14, 2012, US (FRAC Resolution for V&V), hosted by RockwellCollins, final location to be determined (Florida or Texas)

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 94.2 AttendanceName Organization EMailJohn Kasten Jeppesen john.kasten@jeppesen.comAllan Hart Honeywell allan.hart@honeywell.comStephane Dubet DGAC/SIA stephane.dubet@aviation.civile.gouv.frMike Burski FAA michael.burski@faa.govBeby Rakotoarindriaka Airbus beby.b.rakotoarindriaka@airbus.comBritta Eilmus Avitech AG britta.eilmus@avitech-ag.comLisa Haskell Jeppesen lisa.haskell@jeppesen.comStephen Moody Jeppesen stephen.moody@Jeppesen.comGary Livack FAA garret.livack@faa.gov4.3 Open Action ItemsNr. DateAssignedAssignedToTaskBrussels, April 2012150 BRU2012 ALL Provide input on best dates/location forSeptember Meeting151 BRU2012 Mike Forward formal comments from PMC on DO-Burski 200A/DO-201A when available152 BRU2012 John Confirm with RTCA that they will provide theKasten “numbered version” for FRAC. Check onavailability of Word Version to facilitatecommenting153 BRU2012 Allan Hart Arrange and hold telecom/webex meeting toinclude Carla T and Stephane P on surveytechniques for DO-276154 BRU2012 Gary Provide sample FAA NOTAMS that mightLivack affect the SC-206 ISRA Review155 BRU2012 Britta Review Lighting and Marking in DO-272 andEilmus provide proposal to bring in line with DO-276156 BRU2012 Allan Hart Add Note to DO-276, referencing Area 3 and157 BRU2012 Tim Roe,SteveYoung158 BRU2012 Steve4 with regard to numerical requirementsExplain Confidence Level Comment on DO-276StatusOpenOpenOpenOpenClosedOpenOpenOpenRe-educate group on the use of 95% value in OpenYoung para 4.4.1.1 of DO-276159 BRU2012 Allan Hart Review unprocessed DO-276 DraftOpenTim Roe Document Comments that could not beactioned without further explanation160 BRU2012 Allan Hart Clean Up Acronym List in DO-276 Open161 BRU2012 Allan Hart Review Reference Document List in DO-276 Openfor correct version numbering162 BRU2012 TomEvans,Have Appendix C of DO-276 reviewed byqualified staffOpen

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 10SteveYoung,SC-213163 BRU2012 StephaneDubet164 BRU2012 GaryLivack165-169UnusedNumbersNorrköping, September 2011120 NK2011 JohnKasten,MikeBurski121 NK2011 JohnKasten,StephaneDubetCheck on opportunity to have a meeting withRTCA management in conjunction with SC-206 (Stephane, Allan, Gary) on the bestapproach to DO-200A/DO-201A and BruceDeCleene paper from PMC.Prepare a mini-ConOps proposal on manualentry D-Taxi Application, using voicerecognition technologyPrepare presentation about the releases ofDO-272C/DO-291B for the PMC in June2012Prepare a presentation for the PMC inDecember about the rational for DO-272xand the schedule.Distribute draft to the group by end of Oct.2011.122 NK2011 All Review John’s Draft (#121) and providefeedback.123 NK2011 All Brief your PMC representative about the SC-217 activities and that more is coming.127 NK2011 GaryLivack,MikeBurski128 NK2011 BrianGilbert,Beby R.Investigate new developments in AMDBrelated applications and report to the groupas appropriate.Draft text for acceptance criteria anddistribute before the next meeting.129 NK2011 Tim Roe Draft text about Roles and Responsibilities ofthe V&V document and distribute before thenext meeting.130 NK2011 KaushikRaghu,TomEvans,Allan Hart131 NK2011 PatrickEstendorfer,LisaDraft text about V&V methodology before thenext meeting.Coordinate with Brad Miller, Bruce DeCleeneDraft about routing usability and distributebefore the next meeting.(specific routing)OpenOpenOpenOpen(See AI-8)OpenClosedOpen(Ongoing)Open,272xOpen,V&VClosed inBrusselsOpen,V&VClosed inBrusselsOpen,V&VClosed inBrusselsOpen,V&VMoved toV&V Road

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 11Haskell,MapChristianPschierer133 NK2011 StephaneDubetPresent an updated paper to the next ICAOAIM AIS SGImplement proposed changes into the AIMOpen137 NK2011 Sam VanderStricht,Temporality andeTODGroups138 NK2011 LisaHaskell,Contentgroup141 NK2011 ChristianPschierer, SteveYoung142 NK2011 ChristianPschierer143 NK2011 MikeBurski,StephaneDubet,Roger Li144 NK2011 TomEvans,SteveYoung145 NK2011 Sam VanderStricht,ScottWilsonAIS SG paperCheck consistency of Obstacle temporalattributes with AMDB temporal attributesCheck new roadmap and determine effortand data availability for enhancements.Check for papers disseminating the use ofAMDBsCombine V&V drafts into one documentInvestigate operational impact of routingnetwork / V&V with ATC/ATS.Further develop the introduction and developa list of items to be verified for the V&VdocumentInvestigate options / impact of splitting DO-291 into two parts for AMDBs and Obstacles,or alternative ways to restructure.146 NK2011 All Talk to ATC/ATS to identify if the currentrequirements fit their needs.147 NK2011unused numbers-149Open,291xOpen,272xOpenOpen,V&VClosed inBrusselsOpen,V&VClosed inBrusselsOpen,V&VClosed inBrusselsOpen,291xOpen,272x?Mountain View, June 2011117 SFO 2011 GaryLivack,Matt deProvide information about the FAA AircraftAccess to SWIM demo planned in DaytonaBeach as soon as details are available.Open

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 12RisSept. 2011: No significant results yet,postponed until November.Barcelona, Feb/March 201164 BCN 2011 All Have a look at the Eurocontrol-Wiki websiteand verify if the AIXM Terrain and Obstaclemodel fits the need of the group.https://extranet.eurocontrol.int/http://prismeoas.hq.corp.eurocontrol.int/aixmwiki_public/bin/view/Main/Open65 BCN 2011 AllanHart, Samvan derStricht,Mike Burski,Lisa HaskellLook at AIXM model with the view of using itfor the obstacle portion of the DO-276 datamodel.Open,276xClosed inBrusselsDenver, October 20101 Denver 10 JohnKasten2 Denver 10 DejanDamjanovic, GaryLivack,MikeBurski7 Denver 10 Sam vanderStricht11 Denver 10 BruceKinsler,JohnKastenAre there copyright restrictions on the RTCADocs that would prevent the use in otherdocs such as ICAO and Eurocontrol? Checkif the copyright issue for ICAO Doc 9881 alsoapplies to the Eurocontrol DocDraft a scope statement describing theinteraction of AMDBs with SWIM / SESAR /Nextgen.Mike and Gary will have a meeting next weekwith various FAA groups to discuss thisquestion for both the ground and the air side.Coordinate with AIXM group to add verticalline types of Blastfence.Clarification needed: Blastfence = 8Coordinate with NATCA to get some of ourwords into their IFATCA briefing document. Work in progress, some feedbackduring the application reviewJohn: re-establish contactOpenOpen,ongoingOpenOpen19 Denver 10 Allan Hart Generate UML model for obstacles Open,276x22 Denver 10 BrittaEilmusOpen,276x45-49 unused numbersSupport generation of UML model forObstacles (check attributes comparison withICAO and consistency with AMDB)Depends on #19.Madrid, May 2009Madrid 09 Gary Obtain Capstone 3 Phase 1 data to validate Open,

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 13Livack charting requirements to the group; Report onfindings from Capstone 3 Phase 1 flightevaluation.Gary will try to get an advanced report of theUS Airways trials (NA as of 03/2011).ongoing4.4 DO-272/276/291 Roadmap TopicsNr. DateAssigned103 SFO2011106 SFO2011107 SFO2011108 SFO2011111 SFO2011112 SFO2011113 SFO2011114 SFO2011115 SFO2011AssignedToLisaHaskell,BrianGilbertJohnKastenTim RoeBrianGilbertGroupLisaHaskellBrittaEilmus,JohnKastenBrianGilbertAllan HartTaskThe geometric concepts of “overlapping”polygon & “contained in” polygons need to befurther clarifiedAssess the use of the term “movement area”in DO-272 and make sure usage is consistentin the doc.Review use of “heliport threshold”terminologyFurther develop the FRAC comment on Class“I don't really see what benefit the "class"distinctions are providing”Revisit how best to present the data capturerules and geometric constraints. How shouldthey be consolidated to best convey theinformation to the reader?Revisit potential concatenation of multiplenodes occupying the same locationrwyslopeRunway slope definition shall be furtherworked for the next revisionFor the next revision, address those FRACcomments linked to the numbering of rules(shalls) and the issue of multiple shalls groupin one numbered section.Take care of Brian’s comment 12 on DO-291re “Optional:Conditional” for feature attributeefsttimeStatusOpen,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen,291x75 BCN20113 Denver10ScottWilsonLisaHaskellComment: Remove “Optional:Conditional” orclarify what it meansHave a look on 2D/3D Metadata of DO-291.Draft proposal for the density ofRunwayCenterlinePoints.Requested more information from Airbus. Tobe cross-referenced with Tim Roe via MikeOpen,291xOpen,ongoing,272x

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 14Burski.4 Denver10LisaHaskell27 Denver1029 Denver10SergeyLaletinAllan Hart136 NK2011 GaryLivack,Contentgroup139 NK2011 ContentGroup140 NK2011 ContentgroupFN 2010 LisaHaskell,PatrickEstendorfer, MikeBurski,StephaneDubetFN 2010 DejanDamjanovic, ErikHoeppner, CarlaFN 2010Phoenix09Phoenix09ThomaSam vanderStricht,ScottWilsonDefine value of accuracy forRunwayCenterlinePoints.Requested more information from Airbus. Tobe cross-referenced with Tim Roe via MikeBurski.Check ICAO docs and annexes for runwaycenterlines survey accuracy (buildingmethods) and report to the committeeWrite requirements for low-vis / preferred taxiroutes. Consider wording from Annex 14,chapter 14.Harmonize the table 2A of SC-206Revisit the naming of the Arresting GearLocation feature.Revisit definition of Runway Width (inpractice, the AIP value is used).Review Britta’s proposals for guidancematerial related to Data quality. Britta has to update guidance materialfor 272C/291B after initial documentReview Britta’s proposals for guidancematerial related to generation of AMDBs Britta has to update guidance materialfor 272C/291B after initial documentReview Britta’s proposals for guidancematerial related to data product specification Britta has to update guidance materialfor 272C/291B after initial documentGeoeye comment 2.2: Data Capture Rulesfor Runway Exits not painted physically onthe runway (provide screenshots for unusualsituations)Geoeye comment 2.3: Data Capture rules forRunway Exit Lines on Displaced Areas(provide screenshots for unusual situations)Open,ongoing,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen,272xOpen=> seeroadmapOpen=> seeroadmapOpen=>seeroadmapGuidancematerialgroup,#4Guidancematerialgroup,#4

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 154.5 Verification and Validation RoadmapNr. DateAssignedAssignedToTask1 PHX 2011 John Draft Executive SummaryKasten,StephaneDubet2 PHX2011 Tim Roe Update Section 1.3 Intended Users andUses3 PHX2011 All Review Sections 1.3.1 thru 1.5, DocumentApplicability4 PHX2011 All Decide on retention or removal of section1.6 ApplicationsStatusOpenOpenClosed inBrusselsthruGroupActionOpenClosed inBrusselsthruGroupActionOpenClosed inBrusselsthruGroupAction5 PHX2011 All Review Updated portions of Section 1 OpenClosed inBrusselsthruGroupAction6 PHX2011 Tim Roe Section 2.1 Definitions Harmonization OpenClosed inBrusselsthruGroupAction7 PHX2011 StephaneDubetCoordinate with Tim and Mike on COI(Aviation) AS definition.8 PHX2011 All Review Open and Updated portions ofSection 2.9 PHX2011 Brian Review 3.1 for use of the term “graphGilbert, connection”PierreGamet,Beby R.OpenOpenOpen

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 1610 PHX2011 Brian, Beby Provide lead-in wording for each 3.x Opensection.11 PHX2011 All Review Open and Updated portion of OpenSection 312 PHX2011 Kaushik R.,Allan Hart,Tom EvansDevelop lead-in text for 4 and 4.xsections. Stress the fact that this isexample based. Ensure there is amethod for each “acceptance criteria”.Open13 PHX2011 All Review Section 4. Open14 PHX2011 Patrick Create ?Section 6? Routing Usability OpenEstendorfer Draft about routing usability and distributebefore the next meeting.(specific routing)15 PHX2011 All Review Section 6 Open16 PHX2011 All Disposition Parking Lot Items Open17 PHX2011 All Validate Appendix Open4.6 Closed Action ItemsNr.DateAssignedAssignedTo124 NK2011 SteveYoung125 NK2011 ScottWilson126 NK2011 StephaneDubet132 NK2011 RoyLangridge100 SFO Allan Hart2011102 SFO2011StephaneDubetTaskDraft a scope section of the V&V document,reusing sec. 2.2.4 and Appendix A byWednesdayV&V definitions and send to ChristianDraft text for Data vs. Use ASRN vs. others,Application Independence and send toChristianProvide a presentation about the Area 2achange until FridayValidate if updated “ident” definition workswith DO-276Bring up to AIS-AIM SG the issue of“authoritative data source” / “authorizedsource.” The plenary group liked the FGDCsubcommittee definition Stephane noted.Propose a definition for “authoritative datasource” to the AIS-AIM SG.StatusClosedClosedClosedClosedClosedClosedThe term “authoritative data source” wasdiscussed. It was realized that this is coming,but the group does not feel it is ready forincorporation in our docs. ICAO has notadopted it yet.

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 17Nr. Date Assigned TaskStatusAssignedTo ICAO heading towards a more significantupdate of terms and definitions (includinge.g. SWIM) until the next Annex 15Amendment. No short-term solutionavailable.116 SFO Christian Provide breakdown of comments:Closed2011118 SFO2011119 SFO201162 BCN201187 BCN201125 Denver1037 Denver10PschiererStephaneDubetAllScottWilson,Allan HartGaryLivackopen/withdrawn broken down for NC/H/M…Forward the list of aerodrome grouprepresentatives to Tim Roe and the AIM AISWG response.Group members are invited to find volunteersfor the ASRN V&V leadershipFind ways to capture both Data Originatorand Data Source for AMDB, Terrain,Obstacles (see DO276, 3.6.2).Get into contact with the SC-206 leadershipand the FAA AIM to harmonize our data linkD-NOTAM.ClosedClosedClosedClosedAllan Hart Add temporality information to obstacles ClosedJohnKastenCheck with RTCA if there would be acopyright issue if the guidance materialcontains any RTCA or EUROCAE definitionsor figures. Duplicate of #1Closed

RTCA Paper Number 087-12/SC-217-033April 27, 2012Summary of the eleventh meeting RTCA SC-217/WG-44 in Brussels, Belgium 18Certified as a true and accurate summary of the meeting.John KastenActing Secretary, RTCA SC-217, EUROCAE WG-44John KastenChairman, RTCA SC-217Stephane DubetChairman, EUROCAE WG-44