Presentation is loading. Please wait.

Presentation is loading. Please wait.

Background on the RMDCN

Similar presentations

Presentation on theme: "Background on the RMDCN"— Presentation transcript:

1 Background on the RMDCN
Tony Bakker Network and Security Section ECMWF RMDCN Steering Group, 4-6 June 2008, Vienna

2 RMDCN Steering Group, 4-6 June 2008, Vienna

3 Establishment of the RMDCN (1)
Jan 1993 – necessity to reorganize GTS in RA VI (WMO RA VI working group on Planning and Implementation of the WWW in RA VI) Subgroup on Regional aspects for the GTS made first proposal for global modernisation of RMTN to be known as “Regional Meteorological Data Communication Network” May 1994 – RMDCN Steering Group (RA VI General Assembly, 11th session, Oslo) 1995 – Steering Group recommended that ECMWF participate in this Steering group ECMWF constituted a “critical mass” of partnerships RMDCN and ECMWF requirements very similar ECMWF has got agreed set of rules and procedures RMDCN Steering Group, 4-6 June 2008, Vienna

4 Establishment of the RMDCN (2)
Jul France made a request to ECMWF Council to consider a proposal for a Joint Telecommunications Network between ECMWF and GTS in WMO RA VI Sep 1996 – 2nd meeting RMDCN Steering Group ECMWF to undertake procurement, implementation and operation of network RA VI Contract Advisory Committee (CAC) to advice ECMWF Establish a RMDCN Operation Committee (ROC) Conclude an agreement between WMO and ECMWF Oct 1996 – ECMWF TAC established a Subgroup on RMDCN RMDCN Steering Group, 4-6 June 2008, Vienna

5 First TAC Subgroup on RMDCN
Reported to TAC 24 (July 1997) that a managed network could provide a viable solution for a telecommunications service to the ECMWF member States Assisted in preparation and review of procurement documents Prepared draft of WMO-ECMWF agreement Council 47 (Dec 1997) approved ITT for the provision of the RMDCN ITT issued 6 March 1998 Council 49 (Dec 1998) approved selection of EQUANT Network Services Ltd to provide the RMDCN Best value for money Best coverage for the whole WMO RA VI RMDCN Steering Group, 4-6 June 2008, Vienna

6 WMO – ECMWF Agreement Following the approval of a Resolution by RA VI General Assembly (12th Session) and approval during 48th ECMWF Council: July 1998 – Exchange of letters between Director ECMWF and WMO Secretary-General. Key elements: ECMWF will provide a meteorological network to its Member States and is willing to extend this service to all RA VI members RMDCN to be part of GTS regarding RA VI telecommunication requirements ECMWF will carry out procurement and monitoring of the RMDCN (including monitoring of SLA and Quality of Service) Underlying transport layer will not change for 5 years Only for GTS and related traffic RMDCN Steering Group, 4-6 June 2008, Vienna

7 March 2000 First Operational Network
Madrid T oulous e Dublin ECMWF Exeter Oslo Brussels De Bilt Copenhagen Norrköpping O f fenbach EUMETS A Helsinki alli n Riga V ilniu s W arsa w Prague Zurich ienn a Ljubljana Zagreb Bratislava Budapest Rome Athens Skopje Sofia Bucharest Ankara Beirut Damascus Belgrade Luxem- bourg Amman Reykjavik Lisbon R TH – Regional elecommunications Hub NMC – National Meteorological Centre Abu Dhabi Jeddah Beijing New Delhi oky o RMDCN – Regional Meteorological Data Communication Network (Oct 2006) Moscow WMC – World Meteorological Centre Frame Relay Architecture with PVC’s Service Level 24 * 7 99.5% availability 4 hour repair time October 2006 – Frame Relay Network: 43 Sites connected (3 Mission Critical, 1 Disaster Recovery) and 1 cascaded (Syria) RMDCN Steering Group, 4-6 June 2008, Vienna

8 Evolution – Contractual Changes (1)
Supplement 1 – Dec 1999: minor change Supplement 2 – Jun 2002: Extension of the service beyond RA VI to other relevant NMC or organisations involved in the exchange of meteorological or related information as part of WMO or other international programmes willing to sign an Accession Agreement (background was if requested by WMO to implement connections to improve the GTS MTN). TAC recommendation regarding manpower: “Additional RMDCN members will inevitably lead to an increased workload for the RMDCN project team at ECMWF. If the third RMDCN staff member, foreseen from the beginning of the project, is authorised by Council in December 2001, the project team will be able to cope with a limited increase in RMDCN members. The addition of a modest number of connections between existing RMDCN members and WMO members outside RA VI, including the links that would be required for the IMTN project, can be supported without further staffing requirements. However, any substantial increase in RMDCN members would lead to additional manpower requirements.” RMDCN Steering Group, 4-6 June 2008, Vienna

9 Evolution – Contractual Changes (2)
Supplement 3 – Dec 2002: major speed upgrade (including ECMWF funded “basic package” to 384 kbps) Supplement 4 – May 2006: Transition to IPVPN MPLS technology Major changes to Service Level: Mission Critical sites: 100% availability Sites with ISDN backup: 99.9% availability 2 hour repair time Upgrade ECMWF funded “basic package” to 768 kbps RMDCN Steering Group, 4-6 June 2008, Vienna

10 Evolution – Architecture
ECMWF checked regularly the status of new network architectures 2004 proposal to migrate to MPLS Any-to-any connectivity with Class of Service concept Doubling of the access bandwidth Contract extension to March 2009 Thereafter on a rolling basis for successive terms of 12 months Following signature on 8 May 2006, the implementation took 13 months and on 18 June 2007 the RMDCN was using a new IPVPN MPLS architecture Service Level 24 * 7 99.9% availability (100% for Mission Critical) 2 hour repair time RMDCN Steering Group, 4-6 June 2008, Vienna

11 42 Sites 1 extra enhanced (dual access lines; single router)‏
29 ISDN NAS Backup 1 site no Backup (SA)‏ 11 Mission Critical Sites RMDCN Steering Group, 4-6 June 2008, Vienna

12 RMDCN - Availability RMDCN Steering Group, 4-6 June 2008, Vienna

13 Initial contract period Suppl. 4 12-months extension
The Future 2004 2005 2006 2007 2008 2009 2010 Contract Review BCR Effective Date PR Initial contract period Automatic 12-month extension Suppl months extension Current contract with OBS started in Dec 1998 (~10 years on next BCR) An ITT process can take up to months (and that from experience the implementation will suffer some delays), hence a new network service could only be implemented in 2010 at the earliest RMDCN Steering Group, 4-6 June 2008, Vienna

14 Timeline for proposals
2008 January to March: Market Survey April: Annual Price Review with OBS Late spring: Session of the RMDCN RA VI Steering Committee Summer: Session of the TAC Subgroup on the RMDCN Autumn: Report to TAC and to Council Depending on the outcome 2009 March: Issue of the ITT May: Closing date Summer: Evaluation and contract negotiation Autumn: Report to ECMWF committees, WMO RA VI Steering Committee and ECMWF Council Spring: Start of the migration to the new network RMDCN Steering Group, 4-6 June 2008, Vienna

15 TAC Subgroup on RMDCN Established during 37th TAC in October 2007
Terms of Reference to review the scope and methodology of the planned networking market survey; to examine the outcome of the market survey and make recommendations; to involve WMO/RA VI, WMO Secretariat and EUMETSAT as observers in the subgroup, as appropriate; to consider the consequences of any further expansion of the RMDCN to non-RA VI countries. RMDCN Steering Group, 4-6 June 2008, Vienna

Download ppt "Background on the RMDCN"

Similar presentations

Ads by Google