1. May 2008 ET-CTS Toulouse 1 Debriefing on WIS Aspects Discussions from the ICM IMTN Cloud 1 (Washington Nov 2007) Jean-François Gagnon Telecommunications and Security Division Information Technology Infrastructure Chief Information Officer Branch Environment Canada jean-francois.gagnon@ec.gc.ca

2. May 2008 ET-CTS Toulouse 2 WIS-GTS data communication structure and requirements on MTN Presented by Jean-Michel Rainer Presentation available in documents Following 5 slides are reproduced from the presentation

3. May 2008 ET-CTS Toulouse 3 WIS Vision

4. May 2008 ET-CTS Toulouse 4 IGDDS GTS Data pull Data push WIS WIS/GTS: for time and operation-critical data & products WIS/IGDDS: for space-based data & products WIS/DAR: data discovery, access and retrieval Data push: routine distribution of data & products Data pull: access to and retrieval of data & products DAR WIS DATA-COMMUNICATIONS FUNCTIONS AND SERVICES (for weather, water, climate and related data and products)

5. May 2008 ET-CTS Toulouse 5 IGDDS WIS/GTS: for time and operation-critical data & products WIS/IGDDS: for space-based data & products WIS/DAR: data discovery, access and retrieval Data push: routine distribution of data & products Data pull: access to and retrieval of data & products Data pull Data push Essentially through telecom. with guaranteed quality of service, e.g. leased circuits, dedicated data com network services, sat.-based systems,.. Essentially through satellite based data distribution systems, e.g. DVB-S GTS Essentially through the Internet (HTTP, FTP, VPN…) DAR WIS WIS DATA-COMMUNICATIONS IMPLEMENTATION (for weather, water, climate and related data and products)

6. May 2008 ET-CTS Toulouse 6 IGDDS within the WIS GEO satellites in the region LEO satellites Global data (recorded/dumped) DCPC Data, metadata & user management R&D satellites GISC (Data, metadata and user management) Central processing Regional processing Local processing Polar orbiting satellites Network of HRPT stations RARS Data exchange with other DCPCs Satellite products Central processing Interoperability National centres and other users Routine Dissemination ADM Other media Other media Request/ reply (Internet) Request/ reply (Internet) Request/ reply (Internet) Request/ reply (Internet)

7. May 2008 ET-CTS Toulouse 7 WIS Data Policies Complies with WMO data policies –Res. 40 (Cg-XII) and Res. 25 (Cg-XIII) Will follow evolution of WMO data policy –Procedures for managing of access rights, control of data retrieval, registration and identification of users, etc can be defined, as and when required –Anonymous downloading is technically possible, but depends on whether a NC permits that feature –Has no system-inherent features that would violate international legal frameworks

8. May 2008 ET-CTS Toulouse 8 Key Future Milestones Consolidate plans on development, governance and implementation of WIS: 2007-2008 Develop WIS regulatory documentation and guidance material for implementation, including specifications for the GISC interfaces and a unified user interface: 2007- 2008 Develop scheme and practices for security, authentication and authorization procedures for WIS services : 2007-2008 Implementation of first operational GISC: 2008 Implementation of other operational GISCs: 2009 - 2011 Implementation of DCPCs, i.e. WIS interfaces at WMO programmes’ centres: 2008-2011

9. May 2008 ET-CTS Toulouse 9 WIS Technical Specifications Chris Eliott Specifications will be used for GISC, DCPC & NC certification Focus moves from “communications centric” to “data management” ICG-WIS is accountable for technical specifications SIMDAT is included, but is not the only solution

10. May 2008 ET-CTS Toulouse 10 Organization and Design Principles for the WIS Data Communication Structure Presented by jfg for Hiroyuki Ichijo Revised version of this paper to be discussed in Toulouse Comments gathered in Washington: –1 or 2 (or many) clouds: Need to better describe the need and the interaction of 1 or 2 clouds –Propose one specific solution as the design, or –use generic terms to describe an architecture. –Backup (redundancy): Finalize decision on –Using separate dedicated network, or –Using Internet Design of connectivity in backup network should match connectivity in main network –For example full mesh versus not full mesh –Is integrity requirement same for all datasets? –In general: streamline and simplify document as much as possible Ensure design principles are in coherent with the decisions surrounding the future of IMTN Cloud 1 (as currently under discussion)