1World Meteorological Organization

ICG-WISBrasilia 14-17 July 2008

WIS User Requirements

WORLD METEOROLOGICAL ORGANIZATION

Weather – Climate - Water

2World Meteorological Organization

WIS User RequirementsWIS User RequirementsContentsContents

• The WIS User Requirements document addresses three main areas– The process for gathering, maintaining and

implementing User Requirements– Summary of Requirements– Analysis of Requirements

3World Meteorological Organization

WIS User RequirementsWIS User RequirementsProposed ProcessProposed Process

Assessment of Requirements

(WIS Project Office – interim measure)

Review of Requirements

(New ET on User Requirements - to be formed)

User Reqmts Doc, WIGOS Obs db + TBD db

Determine Optimal Way to Meet User Requirements

WG-PIW | ET-OI | ET-CTS

Consolidation of Views

(New ET on User Requirements)

Consolidated and Endorsed User Requirements

Implementation of Services Addressing User Requirements

Member States (CIO)

Statement of Guidance, including endorsed user requirements and proposed implementation approach

Ad Hoc Requests for WIS Services

Decisions on Implementation of formal and Ad Hoc Requests

Questionnaire Responses, Meeting Reports, interviews, etc

Decisions on WIS Components

Designation of GISCs and DCPCs

EC, TCs, RAs, Member States

WIS DCPC and GISC Nominations

Requirements Assessment Phase

RRR Phase

4World Meteorological Organization

WIS User RequirementsWIS User RequirementsAnalysis ofAnalysis of RequirementsRequirements

• Section 3 of the document summarises the information that has been provided in questionnaire responses, meeting reports, presentations and other documents

• Although the questionnaire responses are not uniform in their level of detail, and some responses remain outstanding, from the information received so far, the requirements expressed so far are generally consistent with the functional scope of WIS

5World Meteorological Organization

WIS User RequirementsWIS User RequirementsScope and Sizing ImplicationsScope and Sizing Implications

• Obtaining information that can be directly used to determine the size and scope of WIS remains an issue

• The WIS implementation process needs to be robust enough to cope with quite wide variations in the accuracy and completeness of the requirements information

• High-level such as trend information and traffic survey data will need to be overlaid with the “bottom-up” requirements information (e.g. resulting from questionnaires)