WIGOS Operational Information Resource (WIR) Etienne Charpentier, OBS/OSD WMO; OBS

WIGOS operational Information Resource (WIR)  Goal: Provide single access point for WIGOS stakeholders (Network decision makers, Implementation Coordinators, Data users etc.)  Shall contain all relevant information on the status and evolution of WIGOS and its components  To be fully operational from 2015

WIR purposes  General info. on WIGOS & benefits + impact  Overall description of existing component observing systems (metadata)  Monitor evolution of observing systems capabilities, compare with plans, and look at progress  Access to existing national & regional plans  Assistance to Members Understanding observational user requirements Provide information on the required standards Identifying gaps & potential synergies For data users: Identifying lists of stations & metadata For developing countries: Impl. guidance & tools Mechanism for matching needs with resources

Users of the WIR (audience)  Members  Regional Associations  Technical Commissions & experts  Data users (internal & external to WMO)  Obs. network managers & implementers  Partners  All use information from the WIR  All contribute information to the WIR

WIR Components  Portal: General WIGOS information Basic documents  SORT: Standardization of Observation Reference Tool WIGOS relevant Standards and best practices  OSCAR: Observing Systems Capabilities Analysis and Review Tool Network design and planning Tool for Rolling Requirements Review Process Sub-components oOSCAR/Requirements:Observational user requirements oOSCAR/Space:Space-based observing systems capabilities oOSCAR/Surface:Surface-based obs. systems capabilities oOSCAR/Distributed:Relevant distributed information systems

WIGOS Web Portal OSCAR SORT Critical Review BASIC INFORMATION Benefits, Impacts Communication and Outreach Capacity Building WIP, WDIS, CONOPS… Data policies Etc.. OSCAR/ Surface OSCAR/ Requirements OSCAR/ Space OSCAR/Distributed E.g. GAW, JCOMMOPS, Radar DB etc Standardization of Observation Reference Tool Observing Systems Capability Analysis and Review Tool Implementers of Observing Systems Data users OSCAR User Interface WIS CPDB

WIR Complexity and Development Effort foreseen OSCAR Web Portal, Basic Information SORT

WIR development milestones  End 2012Overall functional requirements  Draft plan  Development Team set up  Feb. 2013Kick off meeting (cross Dept.)  Aug. 2013Start development of OSCAR stage 1  Aug. 2013Detailed Specifications of OSCAR stage 2  Aug. 2013Detailed Specifications of SORT  May 2014OSCAR s1 operational  (excl. OSCAR/Distributed)  Nov. 2014OSCAR s2 operational  (incl. OSCAR/Distributed)  Dec. 2014Implementation of WIR Portal in future  WMO Content Management System (CMS)  Mar. 2015Tests & validation  (incl. with Members, RAs, TCs)  Apr. 2015WIR Operational

Status of WIR development  “WIR Development Plan” proposing completion of WIR by 2015  WIR Development Team set up  Status of components WIR functional specifications ready Portal tree defined SORT basic requirements under discussion OSCAR/Requirements operational OSCAR/Space operational OSCAR/Surface specifications ready

Role of Members, RAs, TCs  Members & RAs Compilation of national & regional requirements Assist for the collection of information on national & regional capabilities Use the WIR tools for national & regional network design & planning  Technical Commissions Technical advise (e.g. IPET-OSDE on OSCAR requirements) Compilation and validation of global requirements (application area focal points) Assist for the collection of information on specific observing systems capabilities (e.g. GAWSIS, WHYCOS, JCOMMOPS)

Overall requirements for the WIR 1/9  Providing general information on WIGOS (outreach, ref. materials, functional architecture, etc.) Benefits of WIGOS Impact of WIGOS implementation on Members

Overall requirements for the WIR 2/9  Overall description of existing component observing systems List of stations contributing to WIGOS (metadata) Information on products they deliver (link to WIS)

Overall requirements for the WIR 3/9  Evolution of observing systems Outline existing national & regional plans Monitoring evolution of capabilities Comparing with plans (national, regional) Ascertain progress

Overall requirements for the WIR 4/9  Assist Members and those in charge of observing network design and implementation to understand the requirements for the relevant observing systems, including standards and recommended practices and procedures, and observational user requirements, in order for them to make appropriate decisions

Overall requirements for the WIR 5/9  Assist Members to identify observational gaps through critical review and to conduct network design studies, in order for them to address those gaps

Overall requirements for the WIR 6/9  To assist Members to understand the full potential of the current observing systems with regard to the WMO Application Areas, including those systems operated by partner organizations, to enhance: Scope & availability of observations made by specific observing stations Collaborations & partnerships (nationally, regionally, globally) Data sharing Data exchange

Overall requirements for the WIR 7/9  Provide data users with immediate access to the list of WIGOS component observing systems, with: Basic set of observational metadata for each (specified by WMO Technical Regulations), Links to the appropriate existing national databases where more detailed information is available

Overall requirements for the WIR 8/9  Provide developing countries with guidance on observing network implementation, and tools they can readily use to document their own observing systems  e.g. by using the OSCAR tool of the WIR, they could avoid the need to develop a database nationally

Overall requirements for the WIR 9/9  Provide a mechanism for matching specific needs (capacity building, gaps, etc.) with resources (via knowledge sharing, donor contributions etc)

The WIR web portal 1/2 wir.wmo.int  Single point of access to all WIGOS related information, and WIR components & tools  General information on WIGOS Concept Benefits Impact Data policies  Generic information on core WIGOS component observing systems, and co-sponsored observing systems GOS, GAW, WHYCOS, GCW GOOS, GCOS, GTOS  Information on how to access data, and link to WIS  Data monitoring information from WIS

The WIR web portal 2/2 wir.wmo.int  Access to basic communication & outreach documents e.g. WDIS WIP CONOPS WIGOS Imperative document Functional Architecture EGOS-IP WIGOS Communication & outreach strategy  Information on national & regional plans, incl. IPs, status, gaps, and templates  Guidance on mechanisms for matching needs with resources

Standardization of Observations Reference Tool (SORT) 1/3  A tool for Members to Assist network supervisors, managers, operators, and data uses to easily access information on relevant WIGOS Regulatory Materials ostandards & practices for observing platform implementation, operations ounderstanding data  A tool for Experts to better apprehend standards, identify inconsistencies, and propose solutions  Goals are to Optimize operational & development costs Support production of coherent, traceable, documented data-sets Improve data quality, and measurement uncertainty Enhance data usability Harmonize standards & enhance interoperability

Standardization of Observations Reference Tool (SORT) 2/3  Modernized, standardized access to up-to-date standards, recommended practices, procedures, and guidelines  Step 1: Access to all relevant documents  Step 2: Information System (CMS type & database) to allow: Referencing of specific standards & practices using taxonomy & vocabulary to be defined e.g. oNetwork management (e.g. design, installation, maintenance …) oInstrument standards (e.g. siting, classification, uncertainty …) oMetadata (station types, instrument types, variables …) oData exchange oQuality management o… Cross referencing Queries & search Identify problems, inconsistencies, and propose solutions

Standardization of Observations Reference Tool (SORT) 3/3  Example of atomization of standards  WMO No. 8, Part I, chapter Recording the circumstances in which measurements are taken Temperature is one of the meteorological quantities whose measurements are particularly sensitive to exposure. For climate studies in particular, temperature measurements are affected by the state of the surroundings, by vegetation, by the presence of buildings and other objects, by ground cover, by the condition of, and changes in, the design of the radiation shield or screen, and by other changes in equipment. It is important that records should be kept not only of the temperature data, but also of the circumstances in which the measurements are taken. Such information is known as metadata (data about data).  Characterization of the standard atom: Technical Regulation (should) Scope: Global Owner: WMO Status: Official Discipline: Meteorology Instrument Variable: air temperature Siting and exposure Representativeness Data management: metadata Standard “atom” level of desired granularity to de defined / agreed

Observing System Capabilities Analysis and Review Tool (OSCAR)  CBS (2010) adopted strategy for establishing a database in support of the Rolling Requirements Review (RRR) process  Requirements Database (avail. since 2011), now included as OSCAR/Requirements  Content of “Dossier on the space-based GOS” migrated to OSCAR/Space (2012)  Available on-line

OSCAR | Objectives  In support of the “RRR” for the analysis, design and planning of WIGOS:  Recording of user requirements  Comparison with actual or planned capabilities  In support of the use of WIGOS  One-stop access to satellite, instrument, and ground-based network metadata

OSCAR (core component) OSCAR/ Requirements OSCAR/ Space (Satellites, Instruments) OSCAR/Distributed (existing DBs) Radar DB JCOMMOPS GAW Streamlined Public User Interface Contributors Surface- based part Maintain content Authority /Maintenance rests with Owners WMO Application Area Focal Points Maintenance of Requirements Link to OSCAR User Interface (e.g. via web service -to be defined) WMO Space Programme Administration Maintain content OSCAR/ Surface (Vol A, Radiosondes) Core modules share some resources Independent Systems

OSCAR/Requirements  Official repository of requirements for observation of physical variables in support of WMO Programmes  Requirements are defined in a “technology-free” manner  Stores definitions and details of around 200 variables and more than 600 requirements OSCAR/ Requirements

OSCAR/Requ. | Process  For each Application Area, designated focal points have limited editing rights on the database  After review and endorsement, these changes become visible to the public  Process overseen by CBS IPET-OSDE

OSCAR/Space  Inventory of factual information  Access to Satellites, Instruments, Agencies metadata  Advanced search, filter and export tools  Expert assessments of space-based capabilities  Network review against pre-defined capabilities  Assessment of the relevance and limitations of instruments against particular measurements OSCAR/ Space

OSCAR/Space Process  Content is directly maintained on-line, lead by the WMO SP office  Process overseen by relevant Expert Groups (ET- SAT, ET-SUP)

Satellite view

OSCAR/Surface  Inventory of factual information  Content from Vol A, Radiosondes  Historical, current and future metadata  Advanced display, filter, query and export facilities similar to OSCAR/Space  Critical review tools  Comparing user requirements with instrument performances  GIS supported analysis on an interactive map OSCAR/ Surface

OSCAR/Surface | Process  Authorized focal points to maintain information on stations, instruments and measurements

OSCAR/Distributed  For integration of partner database content (GAW, JCOMMOPS, Radar), interfaces need to be defined between OSCAR and the DBs  Level of possible integration and technical solution needs to be investigated  Integration in OSCAR v2

Overall Requirements  Data must be harmonized among modules to be comparable and interchangeable  Interface must be user-oriented and coherent, appropriate tools must be provided to enter, update, search, filter and export data

 Thank you for your attention!  Questions ?