Transcription
MEVA/TMG/33 — WP/0224/04/18Thirty‐third MEVA Technical Management Group Meeting (MEVA/TMG/33)Willemstad, Curaçao, 29 – 31 May 2018Agenda Item 1:Approval of Meeting Agenda, Work Method and ScheduleREVIEW OF CONCLUSIONS AND ACTIONS FROM PREVIOUS MEVA/TMG MEETINGS AND FROMNACC/WG MEETINGS(Presented by TMG Coordinator)EXECUTIVE SUMMARYThis working paper presents a follow‐up and summary concerning the conclusionsfrom MEVA/TMG/31 Meeting and from the ANI/WG/3.Action:StrategicObjectives:Suggested actions are listed in Section 3. Safety Air Navigation Capacity and EfficiencyReferences: 1.Thirty Second MEVA Technical Management Group Meeting(MEVA/TMG/32), K Havana, Cuba, 10 – 12 May 2017Fifth North American, Central American and CaribbeanWorking Group Meeting (NACC/WG/5), Port of Spain, Trinidadand Tobago, 22‐26 May 2017MEVA II and III Teleconferences for Monthly reportsANIWG/03 Meeting.Introduction1.1The Thirty Second MEVA Technical Management Group Meeting (MEVA/TMG/32) washeld in Havana, Cuba, 10 – 12 May 2017. In this meeting the conclusions from previous meetings werereviewed and updated accordingly, concluding that all previous valid MEVA TMG conclusions werecompleted or superseded.2.Discussion2.1Appendix to this paper presents a follow‐up to the conclusions of the MEVA/TMG/32and the NACC/WG/5 Meetings. Actions are suggested in this follow‐up.
MEVA/TMG/33 — WP/02—2—3.Suggested Actions3.1The Meeting is invited toa)review the follow‐up of the valid conclusions shown under the Appendix;b)inform on actions and activities regarding each conclusion;c)incorporate better monitoring mechanisms; andd)take appropriate action as needed.———————————
FOLLOW UP TO VALID CONCLUSIONS FROM THE MEVA TMG/32 AND NACC/WG/5 MEETINGSNAM/CAR AIR NAVIGATION IMPLEMENTATIONMEVA TMG/32 MEETINGConclusionsCONCLUSIONMEVA TMG/32/1 INVOICE DETAILSDescriptionRemarksStatusThat, to improve the understanding of the monthly MEVAIII invoice, particularly on charge changes, the MEVAService Provider:MEVA Service ProviderVALIDa) Closeb) Closec) Pendinga)submit a formal communication to all MEVAusers of the cost they are currently charged forbandwidth;b)notify the users henceforth every time themonthly amount charged in the invoice changes,especially if the increase affects all users; andCONCLUSIONMEVA TMG/32/2 VOICE AND DATACHANNEL WITHOUT OPERATIONThat,a)States with assigned channels that are notoperational promote within their State the use of thesame and their commissioning as soon as possible, for thisthey will forward the implementation plan for the servicesto the MEVA Coordinator no later than 30 August 2017;andStatesVALIDAPPENDIXc)provide a formal communication and thebreakdown of the invoice to all MEVA Members by July2017.It is necessary that the States reviewthis Appendix WP with the objectiveof reviewing the channels that doneed to be updated and the channelsthat are not necessary. All accordingto the needs and real capacity.b)States carry on the necessary test andoperational agreements to ensure that the channels willbe operational by the end of 2017.That, if the necessary actions are not taken to carry outthe activities under Conclusion MEVA/TMG/32/2, theState analyze if channels are not required and request tothe MEVA Coordinator to cancel the channel by 15December 2017.VALIDMEVA/TMG/33 – WP/02CONCLUSIONMEVA TMG/32/3 NON OPERATIONALCHANNEL
CONCLUSIONMEVA TMG/32/4 CONCLUSIONMEVA/TMG/32/5 FAULT REPORTINGAND TROUBLESHOOTING PROCEDURESSWITCHINGRemarksStatusThat, considering that several dedicated voice circuits arenot fully operational in the MEVA Network and to providethe use of these circuits, Aruba, Curacao, DominicanRepublic, Jamaica and ICAO review and complete the useof the hotlines/shoutlines that are not in use by August2017.Aruba, Curacao, Dominican Republic,Jamaica and ICAOVALIDThat,StatesVALIDa)States use the 2400 line to check the faultreporting and troubleshooting procedures implementedby The Service MEVA Provider through this service line;andCuba, Cayman Islands, DominicanRepublic, Haiti and United States,indicated that the procedure isworking properly.b)States report their results of operation to theTask Force Coordinator for follow‐up on its correctfunctioning by 31 October 2017.It is necessary to have the validationfrom other States.That, in order to maintain the Service Level Agreement(SLA) for switched lines:Cuba and the MEVA Service Provider.a)the MEVA Service Provider add another trunkline at no extra cost for the MEVA Members by July 2017;andFrequency added the 7 line and theperformance of the switched lineshave been improved as requested.CLOSED‐ A2 ‐CONCLUSIONMEVA TMG/32/6 MEVASYSTEM LINE INCREASEDescriptionCuba and the MEVA Service Provider evaluate theswitched line performance once the additional trunk lineis added and report it to the MEVA/TMG by December2017.CONCLUSIONMEVA TMG/32/7 MEVA III‐REDDIG IINEW INTERCONNECTIONSThat, Trinidad and Tobago, United States and COCESNAinform on any progress made on the MEVA III‐REDDIGinterconnection and take a decision by December 2017.Trinidad and Tobago, United Statesand COCESNAMEVA/TMG/33 – WP/02ConclusionsVALID
ConclusionsCONCLUSIONMEVA TMG/32/8 IMPLEMENTATIONOF THIRD PARTY SERVICESDescriptionRemarksThat, the Rapporteur of the MEVA Task Force, Stateswishing to participate, and ICAO:Rapporteur of the MEVA Task Force,States wishing to participate, andICAOa)carry out an analysis of the request made byCuraçao with the aim of determining the technical andoperational requirements necessary to use the MEVAnetwork as means of communication to provide the ADS‐Bdata to the States;b)analyze and determine the role that the serviceprovider of the communications service will play in theimplementation of third party services; andOFCONCLUSIONMEVA TMG/32/10 REPLACEMENTAFTN WITH AMHS LINESOFCLOSEDState Letter Ref: E.OSG ‐NACC72869 dated 13 April 2018State Letter Ref: E.OSG ‐ E.OSG ‐NACC72920 dated 20 April 2018ICAOCLOSEDState Letter Ref: E.OSGNACC67278 dated 28 June 2017MEVA Service ProviderCONCLUSIONMEVA TMG/32/11 ACTIONS BEFORETHE ITU WORLDRADIOCOMMUNICATION CONFERENCE2019 (WRC‐19)That, ICAO and the MEVA TMG carry out an action plan toensure that States develop the protection of frequenciesnecessary in their territories to maintain current andfuture aeronautical services before the ITU WorldRadiocommunication Conference 2019, to be presented atand followed‐up by the MEVA/TMG/33.ICAO and the MEVA TMGVALIDCONCLUSIONMEVA TMG/32/12 DECOMMISSIONINGOF X.25 NETWORK IN UNITED STATESThat, in order to allow United States to complete thedecommissioning of its X.25 network, the remaining Statesusing X.25:StatesVALIDa)share their anticipated schedule for AMHStransition with the MEVA/TMG Coordinator by 30 June2017;b)work with United States to determine whethertransition to temporary X.25 support is required; andc)begin plans for appropriate testing as required.CLOSEDMEVA/TMG/33 – WP/02That, in order to formalize the decommissioning cost, theMEVA Service Provider officially provides MEVA Membersthe proposed cost and process for decommissioning AFTNlines replacing them with AMHS by July 2017.‐‐ A3 ‐CONCLUSIONMEVA TMG/32/9 INTEGRATIONBRITISH VIRGIN ISLANDS ON MEVAc)present the study by August 2017 to thedirectors of the Civil Aviation Authorities of the States forapproval.That, ICAO communicates by 30 June 2017 the BritishVirgin Islands (BVI) the approval by the Meeting of itsintegration to the MEVA network.ClosedProcedure was developed by the FAAand ICAO, and sent to the MEVAmembers for commentsStatus
ANI/WG/3/3 ‐ PROTECTION ANDRECOGNITION OF C BAND SPECTRUMUSAGEDescriptionThat, in order to take the technical and regulatory actionsto support existing and future operation of the fixedsatellite service earth stations within the band 3 400 – 4200 MHz, as an aid to the safe operation of aircraft andreliable distribution of meteorological information insome States, NAM/CAR States take the appropriatemeasures in order to ensure the protection of the satelliteC‐band operated by the National and Regional VSATnetworks:RemarksMEVA Members will act and follow‐up with their National SpectrumAuthorityStatusMEVA/TMG/33 – WP/02ConclusionsVALIDa) registration of the aeronautical VSAT frequencies in theStates register held by the national authorities ofregulation of telecommunication; andb) follow‐up with the concerned authorities in the Statesto further register the frequencies in the ITU MasterInternational Frequency Register (MIFR) by February 2017.‐ A4 ‐
ConclusionsANI/WG/3/6 ‐ AMHS IMPLEMENTATIONPROCESS IN THE CAR REGIONStatusc) carry on with the additional task of testing thetransmission of XML data through AMHS systMEVA TMG Coordinator to keep theMEVA Members involved on theneed for MEVA Network capabilitiesand circuits.ANI/WG/3/6(c) – AMHSImplementation Process in the CARRegion(c ) carry on with the additional taskof testing the transmission of XMLdata through the AMHS system,coordinating these activities with theAMHS TF.TheFAAhaspreviouslydemonstrated the transport of XMLdata in the AMHS message body (i.e.the equivalent of the AFTN messagebody). Recent recommendationsfrom Europe propose an AMHSprofile to transport XML data as anAMHS File Transfer Body Part (FTBP)– akin to an email attachment.Since TMG31, the FAA has verifiedsupport for FTBP in its test systems.It should be noted that FTBP is a“AMHSEnhancedfeatureofServices”, but it should be clarifiedthat support for FTBP does not implysupport of other Enhances Servicesfeatures.Demonstration of XML transportusing FTBP should ideally beconducted using XML data suppliedby a Met group since the transport ofIWXXM information is expected to bethe first requirement.The FAA is ready to test owardfutureimplementation, there is concernregarding use of FTBP in a mixedAFTN/AMHS network, since anyrouting (including alternate routing)via an AFTN node will block the FTBPtransport.VALIDMEVA/TMG/33 – WP/02Remarks‐ A5 ‐Description
TMG/31/3 ‐ OPERATIONAL USE OFMEVA III CIRCUITSTMG/31/4 ‐ COMPLETION OF MEVA IIINODE INFRASTRUCTURE IN MIAMITMG/31/7 ‐ E/CAR AFS ‐ MEVA IIINETWORK INTERCONNECTIONTROUBLESHOOTING MANAGEMENTAND COORDINATION PROCEDURERemarksStatusThat, in order to ensure the operational use of all thecontracted MEVA III circuits (SDD listed), all the MEVAMembers with pending circuits to be operational performthe necessary actions (operational agreement, procedure,etc.) and report the completion of this task or itsprogress status to the MEVA TMG Coordinator and ICAOby 30 September 2016.All Members to reportThat, in order to complete the necessary infrastructurein the MEVA III node in Miami, United States coordinatewith the MEVA Service Provider to conduct thearrangement to complete the full independency of theT1 lines and report the MEVA/TMG/32 Meetingaccordingly.United States(FAA)As oftoday, Frequentis isprovidingthree T‐1 lines where twoare operational. The third T‐1diversity problem has not States, COCESNA, and Trinidad &TobagoVALIDThat, in order to conduct a follow‐up of the MEVA III‐REDDIG II Interconnection circuits requirements,a) MEVA Service Provider resolve the problemsidentified in the PAD equipment;b) Curaçao, Panama and United States continue theoperational/technical coordination with Colombia,Venezuela and the respective SAM States for theimplementation of the radar data sharing and AMHScircuits;c) Trinidad and Tobago and COCESNA follow‐upon the cost/technical aspects for deciding the bestsolution for the implementation of the PIARCO‐AtlantaAMHS circuit, including Letter of agreement updates asneeded; andd) the progress and updates to this implementation bereported to the MEVA/TMG/32, applying the MEVA IIIadditional circuit process.That, in order to improve the coordination andmanagement actions for trouble shooting failuresinvolving the interconnection of E/CAR AFS and MEVA IIINetwork, the MEVA III TF, the MEVA Service Providerand the ECAR NTG Rapporteur develop by 30 July 2016,a draft Troubleshooting management and coordinationprocedure for approval of the MEVA Members and theE/CAR AFS Members.CLOSEDThe conclusion is following thoughthe conclusions 32/2 and 32/3‐ A6 ‐TMG/31/6 ‐ FOLLOWUP TOIMPLEMENTATION OF MEVA III –REDDIGII INTERCONNECTION CIRCUITREQUIREMENTSDescriptionMEVA/TMG/33 – WP/02ConclusionsThe provider indicated that:The PAD packet transfer relies onproper packet acknowledgementby end‐user equipment – nothingto update on PAD configuration.Inconsistentwindowsizeprogramming on PAD still on place.Adapting put on hold in accordancewith the agreement with FAA forAruba PAD.MEVA Task Force, MEVA ServiceProvider, and E/CAR/NTG RapporteurA draft trouble shooting procedure isbeing developed by Trinidad andTobago and reviewed or MEVAMember.CLOSED
ConclusionsTMG/31/9 ‐ ACTION PLAN ANDAGREEMENT FOR MIGRATION OF AFTNLINES TO AMHS LINESTMG/31/10 ‐ IMPLEMENTATION OFNEWMEVA III CIRCUITSDescriptionThat, in order to optimize the cost and use of thenetwork bandwidth, without violating the originalcontracts of the network, for those Members that arerequesting that existing AFTN lines to migrate to AMHScircuits, the MEVA III TF develop a draft Action Plan andAgreement to allow this migration by 30 September2016.That, in order to ensure the operational need and arealistic date for the implementation of the new circuitslisted in Table 3 of the MEVA TF/31 Report, the MEVAMembers involved in the new circuits:RemarksMEVA III Task ForceFrequentis will provide a copy ofdraft agreement on migration ofAFTN lines to AMHS by June 2017to be reviewed by MEVA Members.StatusCLOSEDMEVA MembersVALID(Derrick Grant)MEVA MembersVALIDMEVA III Task ForceVALIDa) evaluate these needs with their correspondingoperational counterparts;b) apply the “MEVA III Additional circuit” procedure;andc) inform the MEVA/TMG/32 Meeting.That, considering that United States X.25 network isbeyond the end of life and has no active vendormaintenance with difficult continued sustainment andto complete decommissioning of its X.25 network,‐ A7 ‐TMG/31/11 ‐ CHANGING X.25CONFIGURATION TO X.25 SVCCONNECTIONSa) MEVA III TF evaluate the impact for the change (X.25configuration to receive X.25 SVC connections)reporting the MEVA Members by 30August 2016; andb) CAR States having legacy X.25 AFTN circuit migrateto a TCP/IP to X.25 conversion capability by 30November 2017.TMG/31/12 ‐ REVIEW OF CAR/SAMeANPVOLUME II CNS REQUIREMENTSc) conduct a revision of these requirements, particularlyon the ATN architecture and A/G and G/GCommunications; andd) report their recommendations to the MEVA TMG/32Meeting.MEVA/TMG/33 – WP/02That, in order to ensure that the CAR/SAM eANPVolume II has the CNS requirements reflecting the bestpractices and updates identified in th MEVA IIINetwork, the MEVA III TF:
MEVA/TMG/33 – WP/02NACC/WG/5 MEETINGConclusionsDescriptionRemarksStatusNEW CONCLUSION NACC/WG/5DRAFT CONCLUSIONNACC/WG/5/7RADAR DATA SHARINGFOR IMPROVING SAFETY OF OPERATIONSDRAFT Dominican Republic‐Jamaica,COCESNA‐Ecuador, Mexico‐CubaVALIDCuba, Dominican Republic and UnitedStatesVALIDThat, in order to ensure their active support for theICAO WRC‐19 position for the protection of theaeronautical frequency spectrum and future satisfactionof frequency spectrum aviation needs, NAM/CARStates/Territories:NAM/CAR States/TerritoriesVALIDa)include the main points addressed by theICAO position in the International TelecommunicationUnion (ITU) World Radio‐communication Conference(WRC) International Telecommunication Union (ITU)WRC‐19 for the protection of the C‐band when used foraeronautical purposes and the ICAO WRC‐19 position asa whole, including any amendments, when preparingnational ITU WRC‐19 proposals in coordination with theNational Spectrum Management Authority;b)include representatives from civil aviationadministrations and aviation experts from nationaldelegations, to the extent possible, when participatingin the ITU‐ Radio and regional preparatory activities forWRC‐19; andc)register the aeronautical Very Small ApertureTerminal (VSAT) frequencies of your State/Territory withthe respective National Authority of the Spectrum toofficially register them in the ITU Master InternationalFrequency Register (MIFR) by the ANI/WG/5 meeting.— END —‐ A8 ‐DRAFT CONCLUSIONNACC/WG/5/23 ACTIVESUPPORTFROM STATES FOR ICAO ITU WRC‐2019POSITIONThat, to improve the safety of operations on the safetyhot spots identified by the GREPECAS GTE, cuador,Mexico‐Cuba begin to share radar data with theadjacent FIRs as soon as possible providing their actionplan for this purpose to the ANI/WG by 31 October2017.That, in order to test the XML capacity of the CARregional networks, Cuba, Dominican Republic andUnited States coordinate for XML testing over AMHSreporting their progress by 30 December 2017.
MEVA TMG/32/10 REPLACEMENT OF AFTN WITH AMHS LINES That, in order to formalize the decommissioning cost, the MEVA Service Provider officially provides MEVA Members the proposed cost and process for decommissioning AFTN lines replacing them with AMHS by July 2017. MEVA Service Provider CLOSED
