WMO SECRETARIAT
WMO INFORMATION SYSTEM
FUNCTIONAL ARCHITECTURE
“Managing and Moving Weather, Water and Climate
Information in the 21st Century”
World Weather Watch
Information Systems and Services
_________________________________________________________________________________
Version 1.0
8 October 2008
WMO Information System Functional Architecture
DOCUMENT VERSION CONTROL
Version
Authors
Date
Description
0.1
Robert Husband,
David Thomas and
Eliot Christian
Robert Husband,
David Thomas and
Eliot Christian
Robert Husband
David Thomas
Eliot Christian
Fred Branski
Robert Husband
David Thomas
Eliot Christian
Fred Branski
31/01/08
First draft for discussion
05/03/08
Second draft
13/03/08
Third draft
03/06/08
Fourth draft after a review. Major changes include:
i) general textual clarifications;
ii) updates to the model, including:
- changes to A11, A12 and A13 to better illustrate
National, Regional and Global activities and to
harmonise terminology;
- removal of references to files and bulletins and their
replacement with observations, products and
information;
- harmonised treatment of internal and external users
for the delivery of information (internal information
delivery has been removed from A11 and A12 - all
information is now delivered via function A5);
- the archive functionality has been separated out and
marked out of scope;
- the retrieve functionality has been removed.
iii) 2 types of DCPC have been introduced (a simple
DCPC and a DCPC with RTH functionality).
Robert Husband
David Thomas
Eliot Christian
Fred Branski
8/10/08
Changes include:
- minor textual updates to reflect reviewers
comments on version 0.4;
- further lower level detailing of the function A6
(Manage System Performance) to reflect i.a.
the comments of the ET-OI;
- population of Section 4 (Pre-existing Functions
Within WIS)
0.2
0.3
0.4
1.0
116104025
WWW/ISS
Page 2 of 40
WMO Information System Functional Architecture
Table of Contents
EXECUTIVE SUMMARY ........................................................................................................................ 5
Purpose, Outline, and Authority of this Document ........................................................................... 6
Purpose of this Document ................................................................................................................... 6
Outline of this Document ..................................................................................................................... 6
Authority of this Document .................................................................................................................. 6
1
2
Functional Scope of WIS ............................................................................................................... 7
1.1
Basis ......................................................................................................................................... 7
1.2
Impact on the WIS Functional Architecture .............................................................................. 8
1.3
Relationship to Physical Architecture ....................................................................................... 8
1.4
Open Issues .............................................................................................................................. 9
WIS Functional Architecture ....................................................................................................... 11
2.1
Adopted Standard for the Functional Architecture ................................................................. 11
2.2
Context (Level 0) .................................................................................................................... 12
2.3
Level 1 Functional Diagram .................................................................................................... 13
2.3.1
2.3.2
2.3.3
2.4
Data Management Thread ............................................................................................................ 13
Service Provision Thread.............................................................................................................. 14
Performance Management Thread ............................................................................................... 14
Functional Decomposition Below Level 1 ............................................................................... 15
2.4.1
Decomposition of A1: Collect Observations, Generate Products, Create Metadata and Archive
Information ................................................................................................................................................... 15
2.4.2
Decomposition of A3: Maintain and Expose Catalogue of Services and Information .................. 16
2.4.3
Decomposition of A5: Deliver Information to Users (Internal and External) .............................. 16
2.4.4
Decomposition of A6: Manage System Performance .................................................................... 16
2.5
Relationship Between Model and WIS “In Scope” Items ........................................................ 18
2.6
Hierarchy of Functions ............................................................................................................ 20
3
WIS Components and their Minimum Constituent Functions................................................. 21
4
Pre-existing Functions Within WIS ............................................................................................ 23
APPENDIX A – WIS Functional Model ............................................................................................... 25
APPENDIX B – Hierarchy of Functions ............................................................................................. 38
APPENDIX C – List of Abbreviations ................................................................................................ 39
APPENDIX D – Glossary of Terms .................................................................................................... 40
List of Figures:
Figure 1: Integration Definition for Function Modelling (IDEF0) ............................................................ 11
Figure 2: WIS Context Diagram ............................................................................................................ 12
Figure 3: Level 1 Functional Diagram ................................................................................................... 13
Figure 4:
Decomposition of A1 - Collect Observations, Generate Products, Create Metadata and
Archive Information ............................................................................................................................... 15
Figure 5:
Decomposition of A6: Manage System Performance ..................................................... 17
116104025
WWW/ISS
Page 3 of 40
WMO Information System Functional Architecture
Figure 6:
Figure 7:
Decomposition of A61: Non-Real-time Performance Monitoring .................................... 17
Decomposition of A62: Real-time Performance Monitoring ............................................ 18
List of Tables:
Table 1: Scope of WIS (extracted from the WIS Project Plan) ............................................................. 8
Table 2: Relationship Between “in scope” Items and Functional Architecture .......................... 20
116104025
WWW/ISS
Page 4 of 40
WMO Information System Functional Architecture
EXECUTIVE SUMMARY
This document describes the main functional components of WIS, with the associated data-flows. This
high-level description provides a systematic view of how WIS functions.
A structured methodology is used to describe the WIS functions, based on a widely accepted
standard (Integration Definition for Function Modelling - IDEF0). The application of this methodology
results in a hierarchy of functional diagrams. To facilitate their interpretation, these diagrams are
accompanied by a textual description of the main functions and associated information flows.
The overall WIS functional model is then used to propose the minimum functional scope of its
constituent components [National Centres (NCs), Data Collection or Production Centres (DCPCs) and
Global Information System Centres (GISCs)].
Finally, the WIS functionality is related to the functions carried out within the existing WMO ICT
systems including the Global Telecommunications System (GTS) and the IGDDS; illustrating the
additional functionality provided by WIS.
116104025
WWW/ISS
Page 5 of 40
WMO Information System Functional Architecture
Purpose, Outline, and Authority of this Document
Purpose of this Document
The purpose of this document is threefold:
-
to describe the functional architecture of WIS;
to relate the WIS functional architecture to its logical components (i.e. NC, DCPC and GISC);
to identify the WIS functions that form the basis of the existing major WMO IT systems (i.e.
GTS and IGDDS).
Outline of this Document
The document consists of the following main sections:
Section 1:
Section 2:
Section 3:
Section 4:
Functional Scope of WIS;
WIS Functional Architecture;
WIS Components and their Minimum Constituent Functions;
Pre-existing Functions Within WIS.
Authority of this Document
This document is a reference document that is produced and maintained by the WIS Project Office.
The document lies hierarchically below the WIS Project and Implementation Plan (WPIP).
116104025
WWW/ISS
Page 6 of 40
WMO Information System Functional Architecture
1
1.1
Functional Scope of WIS
Basis
A comprehensive description of the context, functional scope and implementation approach for WIS is
provided in the WIS Project and Implementation Plan (WPIP).
In view of its particular relevance to the functional architecture, the table provided in section 1.3
“Scope” of the WPIP is duplicated below.
In Scope
1
Routine collection and automated dissemination of time-critical and operation-critical information
(‘push’).
2
Timely delivery service for information (appropriate to requirements) including delayed mode
data.
3
Information subscription services (subscribe to ‘push’) by authorised users.
4
Ad-hoc requests for information (‘pull’) by authorised users.
5
Integration and management of duplicated files or messages (information entity) including
version control (i.e. corrections and duplicates) The blending of real time and delayed mode
information is handled in other processes of information custodians.
6
Integration of data collection and distribution systems either in place or under development within
the WMO programmes including the satellite programme’s Integrated Global Satellite Data
Distribution System (IGDDS) and the use of the internet via all programmes.
7
Access to WMO registries and catalogues, including a portal for metadata discovery (Information
Discovery)
8
Discovery, Access and Retrieval Service (DAR) to information serving directly from GISCs of
current content (as distinct from only providing metadata)
9
Interoperability with other user communities including earth sciences and the various GEO
societal benefit areas (GEOSS).
10
Assurance processes for ensuring adherence to data and information usage policy.
11
Identification and authorisation processes
12
Network security
13
Information security including exchange over open and closed networks. i.e. Ensure the quality
of the information is maintained while in the transit and communications components. e.g. quality
of service according to GTS manual
14
Merit assessment of new and existing communication technologies (i.e. solution should be
flexible and scalable to allow for taking advantage of new technologies).
15
Information collection and distribution systems within Member states. Although internal collection
and distribution practices within countries are totally under the control of the Member state, these
are a part of WIS. Also, WIS should be able to register national systems should members desire
116104025
WWW/ISS
Page 7 of 40
WMO Information System Functional Architecture
In Scope
international access to them.
16
Quality and performance monitoring of collection and distribution services and systems
17
Metadata profiles for describing information and information services.
18
Management of metadata & effectiveness of metadata, system handling of metadata
Not in scope at this time.
1
Who decides what information passes on WIS. This comes back to the information provider.
2
User registration and shared user registers, virtual organisation issues.
3
Information visualisation and integration. This is a value added service available through NC and
DCPC. Available and future API may enable users to achieve this function.
4
Information subsection and creation of new products. Too hard at present and will come in later
development stages
5
Quality control and assurance processes for data and products. These are being managed within
other stages in the information creation and collection at present, especially within the NC.
Table 1: Scope of WIS (extracted from the WIS Project Plan)
1.2
Impact on the WIS Functional Architecture
The majority of the “in scope” items in section 1.1 have a functional dimension and need
corresponding provisions within the functional model.
Table 1, together with incoming and outgoing dataflows, will be used to define the functional scope of
WIS. This provides the basis for the WIS functional architecture (see section 2 for further details).
Additionally, a cross-check is made with the “in-scope” items defined in section 1.1 to ensure
appropriate provisions for the “in scope” items are included within the architecture (see section 2.5).
The “not in scope” items are not addressed.
1.3
Relationship to Physical Architecture
The functional architecture is a logical construction and provides an orthogonal view to that of the
physical architecture.
Only the minimum functionality associated with an NC, DCPC and GISC is described via the
functional architecture (see section 3 for further details),
Actual physical implementations of NCs, DCPCs and GISCs may vary considerably and possibly
include distributed designs and/or joined designs (e.g. NC + DCPC).
116104025
WWW/ISS
Page 8 of 40
WMO Information System Functional Architecture
1.4
Open Issues
The following table list the open issues that will be addressed in future versions of this document.
Issue Identifier
Issue Description
1
The need to relate “threads” to use cases
2
Possible need to redistribute some of the real-time functions
within A6 to functions A1 to A5 (already partially done for A5 see pages A-8 and A-9 of Appendix A).
3
The function related to performance management (A6:
Manage System Performance) needs to be further developed:
4
The set of monitoring parameters needs to be defined and
should include those for the interfaces as laid out in the WIS
Compliance Specifications. As a minimum, the monitoring
parameters should enable the key values defined in the
service specification to be verified (and reported upon). In
support of this, a standardised menu of user services also
needs to be developed (and reflected in a service
specification) – also a user requirements issue. This service
specification would include the latency requirements for each
service type (e.g. 2 minutes for centre-to-centre warnings) and
would imply the requirement for time-stamping at both ends latency requirements are not universally addressed in the
current set of operational documentation – the minimum
requirement would be for the monitoring of data receipt and
transmission times for data that is exchanged. Also, the data
monitoring approach should be adaptive and reflect when the
data becomes available, rather than when it was scheduled to
be available. Sample SLAs could be a source of information.
Concerning
implementation,
the
network
availability
monitoring approach needs to work when no data is being
transmitted.
.
The sub-functions of A5 (and their balance) need to be
revisited to reflect that 99% of real-time dissemination is
event-driven. The menu of delivery service options needs to
be reflected in the document, noting that priorities do not map
directly onto the service delivery structure (dependent on the
product). Also a request/reply service is needed to support
GTS RTHs, (e.g. retransmission and adhoc). Also an internal
messaging is required (address messaging) and an
administrative message service – e.g. for notification of
operational information.
Sections
Affected
2
2 and 3
2
5
Information security – a cross-check with the GTS Manual is
required to ensure that all relevant functionality has been
included
2 and 3
6
Network security – the approach adopted to ensure network
2 and 3
116104025
WWW/ISS
Page 9 of 40
WMO Information System Functional Architecture
Issue Identifier
Issue Description
Sections
Affected
security may require an update to the functional architecture.
4
7
116104025
Terms used need to be harmonised – a placeholder is
included in Appendix D
WWW/ISS
Appendix D
Page 10 of 40
WMO Information System Functional Architecture
2
WIS Functional Architecture
2.1
Adopted Standard for the Functional Architecture
In order to develop the WIS functional architecture in a systematic and rigorous manner, an
appropriate standard was selected that is supported by tools which facilitate the implementation of the
standard.
The standard known as Integration Definition for Function Modelling [IDEF0] is both simple and highly
regarded. In addition, an important feature of this standard is the clarity of its functional
representations, which can be interpreted by a broad audience without the need for specialist skills.
Some of the main features of the IDEF0 standard are summarised in Figure 1 (below).
defines how the
Function carries out
the transformation
Control
the result of the
transformation carried
out by the Function
source data which
is transformed by
the Function
Input
Functions transform the
Inputs into Outputs in
accordance with the
Controls and making
use of the Mechanisms
Function
Output
Mechanism
identifies the resources/facilities
that are used by the Function
(e.g. humans, computers...)
Figure 1: Integration Definition for Function Modelling (IDEF0)
The IDEF0 standard supports the hierarchical decomposition of both functions and data flows. As
one drills deeper into any part of the model, further definition is evident in the inherited functions and
data flows; yielding a logical hierarchy of data flows and functions.
The particular software tool used to support the implementation of the IDEF0 standard is “Workflow
Modeler” - a product of the Meta Software Corporation.
116104025
WWW/ISS
Page 11 of 40
WMO Information System Functional Architecture
2.2
Context (Level 0)
At the highest level, the functional architecture of WIS is determined by its "context" (or environment).
The WIS context is indicated in Figure 2 (below).
Regulatory and Guidance Documents
(including applicable data policies and performance requirements)
Reference Information
(WIGOS, IOC, etc)
Information Services
Observations, Products,
Information and/or
Associated Metadata
WMO Information System
(WIS)
Reports of Performance
Against Requirements and SLAs
A0
User
Requests
Figure 2: WIS Context Diagram
In accordance with the IDEF0 standard:
-
the WIS “inputs” are depicted by arrows on the left of the box;
-
the WIS “outputs” are depicted by arrows coming out of the box on the right;
-
the WIS “controls” (which define how the WIS functions should be implemented) are depicted
by the arrow entering at the top of the box. [The brackets around the arrowhead denote the
“tunnelling” of this information – i.e. to avoid the diagrams becoming too cluttered and
unreadable, this dataflow is not indicated on the subsequent lower level decompositions].
At the level of the context diagram, the labels attached to the arrows represent the highest level in a
hierarchy of data-flows that are subsequently described in the lower level decompositions.
The A0 box itself represents the full scope of all WIS functions and the “bold edging” indicates that
this function box has further decompositions within the model. The labelling convention followed for
the function boxes is:
A0:
Context
A1, A2, A3…
Functional decomposition of Context
A11, A112, A113…
Functional decomposition of A1, (similarly for A2, A3, etc)
In principle, any function can be decomposed into an arbitrary number of sub-functions. Purely for
readability, the decomposition is normally limited to 6 sub-functions by the Workflow Modeler tool
(with an absolute maximum of 9 sub-functions). This constraint is only applied to the breadth of the
decomposition and not the depth (i.e. the number of functional levels) which is unconstrained.
Some non-WIS functions are included within the model to facilitate understanding of data flows even
though they are not within the scope of WIS – e.g. see decomposition of functions A11 and A12.
116104025
WWW/ISS
Page 12 of 40
WMO Information System Functional Architecture
2.3
Level 1 Functional Diagram
The level 1 functional diagram (figure 3 below) lies immediately below the context diagram, inherits its
attributes, and provides a high-level overview of how WIS functions.
There are three main threads1 to the level 1 functional diagram:
-
The data management thread makes sure that the required data is available within WIS to
meet the needs of the users;
The service provision thread processes user requests for information and provides the
associated information to the users;
The performance management thread monitors and controls the overall performance of WIS
and provides performance reports).
-
User Role Assignment
Procedure
User Requests with
Assigned Role
User
Requests
I3
Information Search
Requests
Information Search Results
Information Services
Assign User
Role
Maintain and Expose
Catalogue of Services
and Information
Catalogue Browse
Requests
A2
Applicable
Data Policy
O1
"Browsable" DAR
Metadata Catalogue
A3
Dissemination
Metadata Catalogue
Subscriptions
Requests for
Information
Authorise
Access to
Information by
Users
"Ad Hoc" Requests
Information Access
Authorisations
A4
Reference Information
(WIGOS, IOC, etc)
Deliver
Information to
Users (Internal
and External)
A5
I1
Information
Observations, Products,
Information and/or
Associated Metadata
I2
Delivered Information via
WIS Information Delivery
Services
Reports of Performance
Against Requirements and SLAs
O2
DAR Metadata
Updates
Collect Observations,
Generate Products,
Create Metadata and
Archive Information
A1
Monitoring Data
from all functions
Maintained and Consolidated
DAR Metadata Catalogue
Manage
System
Performance
A6
Control Actions to
All Functions
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
Figure 3: Level 1 Functional Diagram
2.3.1
Data Management Thread
The data management thread primarily involves 2 functions:
-
A1:
A3:
Collect Observations, Generate Products, Create Metadata and Archive Information
Maintain and Expose Catalogue of Services and Information
The purpose of function A1 is to collect and archive all the relevant WIS information, and to create the
required Discovery Access and Retrieval (DAR) metadata. There will be an initial population of the
DAR metadata, which will then be maintained by updates.
Function A3 has both a service provision component and a data management component. The data
management component mainly involves the generation and maintenance of a consolidated DAR
1
In this context “Thread” is used as a collective term to embrace a set of functions and dataflows which relate to a particular
high-level objective (i.e. data management, service provision or performance management)
116104025
WWW/ISS
Page 13 of 40
WMO Information System Functional Architecture
metadata catalogue (see section 2.3.2 for a description of the service provision component of function
A3).
2.3.2
Service Provision Thread
The service provision thread primarily involves 4 functions:
-
A2:
A3:
A4:
A5:
Assign User Role
Maintain and Expose Catalogue of Services and Information
Authorise Access to Information by Users
Deliver Information to Users (Internal and External)
As indicated by function A5, the service provision thread addresses the information needs of both
internal and external users.
The thread starts with an initial user request. To process this request the authorised user role(s) must
be determined. This determination is performed by function A2 in accordance with the relevant user
role assignment procedure.
The subsequent processing of the request then depends on its typology. The three options are
identified in figure 3:
a)
b)
c)
Information Search Requests;
Catalogue Browse Requests;
Requests for Information.
Option a): the request is passed to function A3, which searches the consolidated DAR catalogue and
provides the search results to the user.
Option b): the request is passed to function A3, which makes available the relevant parts of the DAR
catalogue to the user for browsing.
Option c): the request is passed to function A4 for verification that the request is consistent with all the
applicable data policies. This could be a follow-on action as a result of previous requests of type a) or
b). Once verified, access is authorised and the subsequent process depends on the type of
information request. Two options are available:
i)
ii)
“subscription” requests (a user requests that information be provided on a routine basis);
“ad hoc” requests (no recurring service provided).
Option i): the request is passed to function A3 which updates the dissemination metadata catalogue,
and the information is then delivered to the user via function A5 (after being relayed from function A1).
It should be noted that the dissemination metadata catalogue defines how information is provided to
users by Function A5 and contains all the details as to how the data should be delivered to the user.
Option ii) is similar to option i) with the exception that the dissemination metadata catalogue is not
updated (no recurring service) and the request is passed directly to function A5 without the
involvement of function A3.
2.3.3
Performance Management Thread
The performance management thread primarily involves function A6: Manage System Performance.
As reflected in its decomposition, this function has a real-time component and a non real-time
component. The real-time component receives status information from all WIS functions and issues
“control” actions as appropriate.
The non real-time component provides reporting information to WIS management entities on the
performance of the WIS in accordance with the WIS performance requirements – see “tunnelled”
control in figure 2 (context diagram).
116104025
WWW/ISS
Page 14 of 40
WMO Information System Functional Architecture
2.4
Functional Decomposition Below Level 1
The Level 1 functional decomposition given in section 2.3 is an overview of the main WIS functions
and their inter-relationships in terms of dataflows.
This section describes, in a systematic way, their constituent lower level functions and associated
dataflows.
2.4.1
Decomposition of A1: Collect Observations, Generate Products, Create Metadata and Archive
Information
Function A1 is decomposed into 3 sub-functions (see figure below) which have some similarities in
terms of functionality, but are different in terms of scope (national, regional and global).
Observations, Products,
Information and/or
Associated Metadata
I2
National
Information
Collect, Generate and
Archive National
Information & Create
Metadata
A11
DAR Metadata
Updates
O1
Collect, Generate and Archive
Regional, Programme-related and
Specialised Information & Create
Metadata
I1
Reference Information
(WIGOS, IOC, etc)
A12
Information
O2
Regional, Specialised
and Programme-related
Information
Maintained and Consolidated
DAR Metadata Catalogue
I3
Collect and Cache Global
Information
Delivered Information via
WIS Information Delivery
Services
I4
Global Information
A13
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
Figure 4: Decomposition of A1 - Collect Observations, Generate Products, Create Metadata and
Archive Information
Function A11 operates primarily at the national level with the following functional components (see
Appendix A-4):
-
Note:
Collect National Observations (A111);
Check Meteorological Content of Products and Observations (A112);
Archive (A113);
Generate National Products (A114);
Generate Metadata (A115);
Unpack Information (A116);
Verify Correct Telecommunication Attributes of Information (A117).
functions A112 and A114 are not within the scope of WIS (see section 1.1) but have been
included because they are commonly associated with this process.
116104025
WWW/ISS
Page 15 of 40
WMO Information System Functional Architecture
Function A12 is similar to function A11, but operates primarily at the regional level (see Appendix A-5
for further details).
Function A13 (see Appendix A-6) is primarily at the global level and differs from functions A11 and
A12 in that:
-
it does not collect information and instead relies on functions A11 and A12 for the collection of
information;
it provides a 24 hour cache (for retrieval) of globally-required data.
2.4.2
Decomposition of A3:
Maintain and Expose Catalogue of Services and Information
Function A3 consists of three sub-functions (see Appendix A-7):
-
Search DAR Metadata Catalogue (A31);
Maintain and Expose Consolidated DAR Metadata Catalogue (A32);
Maintain Dissemination Metadata Catalogue in Accordance with Authorised Subscriptions
(A33).
2.4.3
Decomposition of A5:
Deliver Information to Users (Internal and External)
Function A5 is further decomposed into the following sub-functions (see Appendix A-8 and A-9):
-
-
Schedule and Control Activities (A51):
Derive Time-driven (synchronous) activity schedule and list of event-driven
(asynchronous) activities (A511);
Monitor for Events (A512);
Resolve any Activity Scheduling Conflicts, reflecting relative service priorities (A513)
Package Information for Delivery (A52).
This function ensures information is delivered in a manner that reflects service priorities. To achieve
this, the delivery of the data is controlled so that time-driven and event-driven activities are interwoven
in a manner that is consistent with service priorities. The process is driven by user requests for data (as
reflected in the contents of the Dissemination Metadata Catalogue or “ad hoc” requests). This basic
input information is used to generate the synchronous activity schedule, and the list of event-driven
activities. As events occur (detected by A512) function A513 ensures that the synchronous and
asynchronous activities are executed in a manner that reflects the overall service priorities.
2.4.4
Decomposition of A6:
Manage System Performance
As noted previously function A6 has both a non real-time (offline) and a real-time component, which is
reflected in its decomposition (see Appendix A-10):
-
Non Real-time Performance Monitoring - A61;
Real-time Performance Monitoring – A62.
116104025
WWW/ISS
Page 16 of 40
WMO Information System Functional Architecture
Regulatory and Guidance Documents
(including applicable data policies and performance requirements)
Reports of Performance
Against Requirements and SLAs
Non Real-time
Performance
Monitoring
O1
A61
Monitoring Outputs
from all functions
Discrepancy Reports
I1
Control Actions to
All Functions
Real-time Performance
Monitoring
O2
A62
Figure 5: Decomposition of A6: Manage System Performance
The first of these activities (A61) has two components:
-
Analyse Traffic Trends (A611);
Analyse Performance Against Requirements and SLAs (A612).
Traffic Trend Report (including
recommendations for evolutions/upgrades)
Monitoring Outputs
from all functions
Analyse Traffic
Trends
I1
Reports of Performance
Against Requirements and SLAs
A611
O1
Analyse
Performance
Against
Requirements and
SLAs
Discrepancy Reports
I2
A612
Figure 6:
Performance Report (including
recommendations for improvements)
Decomposition of A61: Non-Real-time Performance Monitoring
A611 analyses the traffic trends on the WIS and, based on this trend information, makes
recommendations for upgrades/evolutions of the WIS telecommunications infrastructure as appropriate.
A612 compiles information on the performance of the WIS and compares it with the relevant WIS
requirements (service specifications, SLAs, etc). This comparison is then consolidated into reports,
together with any recommendations for improvements – usually resulting from an analysis of
discrepancies. These reports provide a source of information for periodic WIS Performance Reviews.
The aim of activity A62 is to monitor and control the real-time performance of WIS. Two components
of this activity have been highlighted:
-
Real-time Monitoring of the Telecommunications Network (A621);
Real-time Monitoring of the Application Content (A622)
116104025
WWW/ISS
Page 17 of 40
WMO Information System Functional Architecture
Network Status (e.g. Availability, Capacity
Utilisation, etc)
Discrepancy Reports
Real-time Monitoring
of the
Telecommunication
Network
O1
A621
Network Configuration
Actions
Monitoring Outputs
from all functions
I1
Dissemination Metadata
Catalogue
Control Actions to
All Functions
Real-time
Monitoring of the
Application Content
Application Content
Status
Figure 7:
O2
A622
Application Content Management Actions
(e.g. coding corrections, request for retransmission
of missing information, removal of duplication information, ....)
Decomposition of A62: Real-time Performance Monitoring
Activity A621 focuses on the monitoring of the telecommunications infrastructure (e.g. network
availability, outages, capacity, utilisation, etc) and optimises in real-time the use of this infrastructure.
Activity A622 monitors, at a high level, the application content of the WIS (i.e. the information) and,
using reference information contained in the dissemination metadata catalogue, takes appropriate
actions in the event of exceptions.
Additionally, a verification is performed (e.g. checksum) on information to check that information is
not changed during its passage through WIS.
2.5
Relationship Between Model and WIS “In Scope” Items
The following table illustrates how “in scope” items identified in section 1.1 are reflected within the
functional architecture.
Item
Description
Relevant Provisions within the Functional
Architecture
1
Routine
collection
and
automated
dissemination of time-critical and operationcritical information (‘push’).
All functions, but principally functions A1 and
A5
2
Timely delivery service for information
(appropriate to requirements) including
delayed mode data.
Principally function A5
3
Information subscription services (subscribe
to ‘push’) by authorised users.
Principally functions A2, A4, A3 and A5
4
Ad-hoc requests for information (‘pull’) by
authorised users.
Principally functions A2, A4 and A5
5
Integration and management of duplicated
files or messages (information entity)
including version control (i.e. corrections and
duplicates) The blending of real time and
delayed mode information is handled in other
A622 covers this item
116104025
WWW/ISS
Page 18 of 40
WMO Information System Functional Architecture
Item
Description
Relevant Provisions within the Functional
Architecture
processes of information custodians.
6
Integration of data collection and distribution
systems either in place or under development
within the WMO programmes including the
satellite programme’s Integrated Global
Satellite Data Distribution System (IGDDS)
and the use of the internet via all
programmes.
WIS functional architecture enables the data
collection and distributions systems to be
interoperable through the use of Service
Oriented Architecture practices. The level of
integration
will
depend
on
chosen
implementation solutions.
7
Access to WMO registries and catalogues,
including a portal for metadata discovery
(Information Discovery)
Covered (functionally) by A3 supported by A2
8
Discovery, Access and Retrieval Service
(DAR) to information serving directly from
GISCs of current content (as distinct from only
providing metadata)
Discovery: A3, Access: A2 & A4 Retrieval: A1
& A5
9
10
Interoperability with other user communities
including earth sciences and the various GEO
societal benefit areas (GEOSS).
WIS
functional
architecture
enables
interoperability with other communities
through the use of Service Oriented
Architecture practices. Achieving this is
dependent on the Interface Specifications, in
particular those relating to A2, A3, A4 and A5
Assurance processes for ensuring adherence
to data and information usage policy.
Function A4 is controlled by the “applicable
data policy”
Identification and authorisation processes
Assumed to form part of the “User Role
Assignment Procedure” and “Applicable Data
Policy” – controls on functions A2 and A4
respectively
Network security
Network security has two main components,
(1) Physical, and (2) Practices and
Procedures. All functional components have a
role in security, especially, A2, A4 and A5 as
the major IO interfaces and A6 as the system
management. Most aspects are covered in
the manual on GTS and other guidelines. The
functional model will need to be regularly
reviewed to account of any new aspects,and
any functional implications of adopted
approaches for achieving network security..
Information security including exchange over
open and closed networks. i.e. Ensure the
quality of the information is maintained while
in
the
transit
and
communications
components. e.g. quality of service according
to GTS manual
Practices and procedures along with network
and hardware security are an important part
of information security. As with networks all
functional components have a role in security,
especially, A2, A4 and A5 as the major IO
interfaces
and
A6
as
the
system
management. A cross-check with the GTS
manual is needed to establish if other aspects
need to be considered
11
12
13
116104025
WWW/ISS
Page 19 of 40
WMO Information System Functional Architecture
Item
14
Description
Relevant Provisions within the Functional
Architecture
Merit assessment of new and existing
communication technologies (i.e. solution
should be flexible and scalable to allow for
taking advantage of new technologies).
Out of scope of the functional architecture –
although it could be expected that
recommendations for new technologies could
be introduced as a result of A611 (Analyse
Traffic Trends)
15
Information collection and distribution systems
within Member states. Although internal
collection and distribution practices within
countries are totally under the control of the
Member state, these are a part of WIS. Also,
WIS should be able to register national
systems should members desire international
access to them.
The functional architecture is consistent with
these objectives
16
Quality and performance monitoring of
collection and distribution services and
systems
Covered in a generic sense by function A6
17
Metadata profiles for describing information
and information services.
Out of scope of the functional architecture –
which assumes their existence
Management of metadata & effectiveness of
metadata, system handling of metadata
Management of metadata is principally
covered by function A3 (with inputs provided
by A1)
18
Table 2: Relationship Between “in scope” Items and Functional Architecture
2.6
Hierarchy of Functions
The function tree, derived from the model, is given in APPENDIX B – Hierarchy of Functions.Error!
Reference source not found.
116104025
WWW/ISS
Page 20 of 40
WMO Information System Functional Architecture
3
WIS Components and their Minimum Constituent Functions
Based on the guidance given in the WIS Project Plan, the following table defines the minimum
constituent functionality for NCs, DCPCs and GISCs. Grey text is used to indicate where
apportionment of functionality is determined at a lower level of functional decomposition.
“OOS” Indicates out of scope of WIS.
To facilitate a mapping onto the current GTS architecture, two types of DCPC have been defined:
-
DCPC (without the functions associated with an RTH on the GTS);
DCPCRTH (including the functions associated with an RTH on the GTS).
Function (referenced to functional model)
WIS Component
NC
A0
A1
A11
A111
A112
A113
A114
A115
A116
A117
A12
A121
A122
A123
A124
A125
A126
A127
A13
A131
A132
A134
A135
A2
A3
A31
A32
A33
WMO Information System (WIS)
Collect Observations, Generate Products, Create
Metadata and Archive Information
Collect, Generate and Archive National Information &
Create Metadata
Collect National Observations
Check Meteorological Content of Products and
Observations
Archive
Generate National Products
Generate Metadata
Unpack Information
Verify Correct Telecommunication Attributes of
Information
Collect, Generate and Archive Regional, Programmerelated and Specialised Information & Create Metadata
Collect Regional, Specialised and Programme-related
Observations
Check Meteorological Content of Observations
Archive
Generate Regional, Specialised and Programme-related
Products
Generate Metadata
Unpack Information
Verify Correct Telecommunication Attributes of
Information
Collect and Cache Global Information
Unpack Information
Verify Correct Communication Attributes of Information
Associate Information with DAR Metadata1`
Maintain and make available Cache of Global
Information for 24 Hours
Assign User Role
Maintain and Expose Catalogue of Services and
Information
Search DAR Metadata Catalogue
Maintain and Expose Consolidated DAR Metadata
Catalogue
Maintain Dissemination Metadata Catalogue in
DCPC
DCPCRTH
X
X
OOS
OOS
OOS
OOS
OOS
OOS
X
X
X
X
GISC
X
OOS
OOS
OOS
X
X
X
X
X
X
X
X1
X1
X1
X2
X
X
X
1
For access to its proprietary information and in accordance with the applicable data policy and
authorised user functions
2 For access to the metadata catalogue and global information in accordance with the applicable data
policy and authorised use functions
116104025
WWW/ISS
Page 21 of 40
WMO Information System Functional Architecture
Function (referenced to functional model)
A4
A5
A51
A511
A512
A513
A52
A53
A6
A61
A611
A612
A62
A621
A622
Accordance with Authorised Subscriptions
Authorise Access to Information by Users
Deliver Information to Users (Internal and External)
Schedule and Control Activities
Derive Time-driven (synchronous) activity schedule and
list of event-driven (asynchronous) activities
Monitor for Events
Resolve any activity scheduling conflicts, reflecting
relative service priorities
Package Information for Delivery
Deliver Information
Manage System Performance
Non Real-time Performance Monitoring
Analyse Traffic Trends
Analyse Performance Against Requirements and SLAs
Real-time Performance Monitoring
Real-time Monitoring of the Telecommunications
Network
Real-time Monitoring of the Application Content
116104025
WWW/ISS
WIS Component
NC
DCPC
DCPCRTH
GISC
X1
X1
X1
X2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Page 22 of 40
WMO Information System Functional Architecture
4
Pre-existing Functions Within WIS
The following table identifies which WIS functions are already implemented within existing WMO ICT
Systems [i.e. Integrated Global Data Dissemination System (IGDDS) and the GTS]. For ease of
comparison, the functions contained within WIS components (i.e. NC, DCPC and GISC) are also
indicated.
A0
A1
A11
A111
A112
A113
A114
A115
A116
A117
A12
A121
A122
A123
A124
A125
A126
A127
A13
A131
A132
A134
A135
A2
A3
A31
A32
A33
Function (referenced to functional model)
WMO Information System (WIS)
Collect Observations, Generate Products, Create
Metadata and Archive Information
Collect, Generate and Archive National Information &
Create Metadata
Collect National Observations
Check Meteorological Content of Products and
Observations
Archive
Generate National Products
Generate Metadata
Unpack Information
Verify Correct Telecommunication Attributes of
Information
Collect, Generate and Archive Regional, Programmerelated and Specialised Information & Create Metadata
Collect Regional, Specialised and Programme-related
Observations
Check Meteorological Content of Observations
Archive
Generate Regional, Specialised and Programme-related
Products
Generate Metadata
Unpack Information
Verify Correct Telecommunication Attributes of
Information
Collect and Cache Global Information
Unpack Information
Verify Correct Communication Attributes of Information
Associate Information with DAR Metadata
Maintain and make available Cache of Global
Information for 24 Hours
Assign User Role
Maintain and Expose Catalogue of Services and
Information
Search DAR Metadata Catalogue
Maintain and Expose Consolidated DAR Metadata
Catalogue
Maintain Dissemination Metadata Catalogue in
Accordance with Authorised Subscriptions
WIS
GTS
IGDDS
X
OOS
X
X
OOS
OOS
OOS
OOS
X
X
X
OOS
X
X1
X
X
OOS
OOS
X6
OOS
X
X
X
OOS
OOS
OOS
OOS
X
OOS
X
X
OOS
OOS
X
X
X
X1
X
X
X6
OOS
X
X
X
X
X
X
X
X2
OOS
OOS
X
X
OOS7
X
X3
X
X
X
X4
X4
X6
X6
X
X2
X
1
Some Metadata is available in GTS publications
Available through the “Product Navigator”
2 Some information is contained within GTS Routeing Tables exchanged between centres (tables are
not consolidated)
7 Not in scope of EUMETCast (used as the IGDDS reference implementation) but this functionality is
provided by the EUMETSAT Earth Observation Portal
3 Implicitly done at a high level – GTS is a “trusted” network
4 Manual process which requires implicit knowledge
6
116104025
WWW/ISS
Page 23 of 40
WMO Information System Functional Architecture
A4
A5
A51
A511
A512
A513
A52
A53
A6
A61
A611
A612
A62
A621
A622
5
Function (referenced to functional model)
Authorise Access to Information by Users
Deliver Information to Users (Internal and External)
Schedule and Control Activities
Derive Time-driven (synchronous) activity schedule and
list of event-driven (asynchronous) activities
Monitor for Events
Resolve any activity scheduling conflicts, reflecting
relative service priorities
Package Information for Delivery
Deliver Information
Manage System Performance
Non Real-time Performance Monitoring
Analyse Traffic Trends
Analyse Performance Against Requirements and SLAs
Real-time Performance Monitoring
Real-time Monitoring of the Telecommunications
Network
Real-time Monitoring of the Application Content
WIS
GTS
X
X5
IGDDS
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
OOS
External users route their data requirements through their National Centre (who acts as an agent)
116104025
WWW/ISS
Page 24 of 40
WMO Information System Functional Architecture
APPENDIX A – WIS Functional Model
116104025
WWW/ISS
Page 25 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Regulatory and Guidance Documents
(including applicable data policies and performance requirements)
Reference Information
(WIGOS, IOC, etc)
Information Services
Observations, Products,
Information and/or
Associated Metadata
WMO Information System
(WIS)
A0
User
Requests
NODE: A-0
116104025
TITLE:
Reports of Performance
Against Requirements and SLAs
Appendix A - 1
CONTEXT
WWW/ISS
Page 26 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
User Role Assignment
Procedure
User Requests with
Assigned Role
User
Requests
I3
AUTHOR:
R. Husband
REV:
Draft Q
Information Search
Requests
Information Search Results
Information Services
Assign User
Role
A2
Maintain and Expose
Catalogue of Services
and Information
Catalogue Browse
Requests
Applicable
Data Policy
"Browsable" DAR
Metadata Catalogue
A3
Subscriptions
Requests for
Information
O1
Authorise
Access to
Information by
Users
A4
Dissemination
Metadata Catalogue
"Ad Hoc" Requests
Information Access
Authorisations
Reference Information
(WIGOS, IOC, etc)
Deliver
Information to
Users (Internal
and External)
A5
I1
Information
Observations, Products,
Information and/or
Associated Metadata
I2
Delivered Information via
WIS Information Delivery
Services
Reports of Performance
Against Requirements and SLAs
O2
DAR Metadata
Updates
Collect Observations,
Generate Products,
Create Metadata and
Archive Information
A1
Monitoring Outputs
from all functions
Maintained and Consolidated
DAR Metadata Catalogue
Manage
System
Performance
A6
Control Actions to
All Functions
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
NODE: A0
116104025
TITLE:
Appendix A - 2
WMO Information System (WIS)
WWW/ISS
Page 27 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Observations, Products,
Information and/or
Associated Metadata
I2
National
Information
Collect, Generate and
Archive National
Information & Create
Metadata
A11
DAR Metadata
Updates
O1
Collect, Generate and Archive
Regional, Programme-related and
Specialised Information & Create
Metadata
I1
Information
O2
Reference Information
(WIGOS, IOC, etc)
Regional, Specialised
and Programme-related
Information
A12
Maintained and Consolidated
DAR Metadata Catalogue
I3
Collect and Cache Global
Information
Delivered Information via
WIS Information Delivery
Services
I4
Global Information
A13
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
NODE: A1
116104025
TITLE:
Appendix A - 3
Collect Observations, Generate Products, Create Metadata and Archive Information
WWW/ISS
Page 28 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Observations from
territory, aircraft and ships
Observations, Products,
Information and/or
Associated Metadata
Collect National
Observations
National
Observations
Archive
A111
I1
Check
Meteorological
Content of
Products and
Observations
A113
A112
Maintained and Consolidated
DAR Metadata Catalogue
DAR Metadata
Updates
O2
Generate
Metadata
I3
National Products
Reference Information
(WIGOS, IOC, etc)
A115
Generate
National
Products
I2
A114
Delivered Information via
WIS Information Delivery
Services
Verify Correct
Telecommunication
Attributes of
Information
Un-packed
information
National
Information
O1
A117
Unpack
Information
I4
A116
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
NODE: A11
116104025
TITLE:
Appendix A - 4
Collect, Generate and Archive National Information & Create Metadata
WWW/ISS
Page 29 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
Observations, Products,
Information and/or
Associated Metadata
I1
Regional/Specialised
Observations
Maintained and Consolidated
DAR Metadata Catalogue
Meteorologicallychecked
Observations
A121
R. Husband
REV:
Draft Q
Archive
A123
Check
Meteorological
Content of
Observations
Collect Regional,
Specialised and
Programme-related
Observations
AUTHOR:
DAR Metadata
Updates
A122
Generate
Metadata
I2
Reference Information
(WIGOS, IOC, etc)
I3
Generate
Regional,
Specialised and
Programmerelated Products
Regional and
Specialised Products
A124
Un-packed
information
Delivered Information via
WIS Information Delivery
Services
O1
A125
Verify Correct
Telecommunication
Attributes of
Information
Regional, Specialised
and Programme-related
Information
O2
A127
Unpack
Information
I4
A126
Note: Bold red text and red activity borders denote functions which are out of scope of WIS
NODE: A12
116104025
TITLE:
Collect, Generate and Archive Regional, Programme-related and Specialised Information & Create Metadata
WWW/ISS
Page 30 of 40
Appendix A - 5
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Delivered Information via
WIS Information Delivery
Services
I2
Unpack Information
Global Information
A131
O1
Verify Correct
Communication
Attributes of
Information
Associate
Information with
DAR Metadata
A133
Maintained and Consolidated
DAR Metadata Catalogue
A132
Maintain and
make available
Cache of Global
Information for 24
Hours
Global Information Associated
with Metadata
I1
A134
NODE: A13
116104025
TITLE:
Appendix A - 6
Collect and Cache Global Information
WWW/ISS
Cached Global
Information
Page 31 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Information Search
Requests
Information Search Results
I1
Search DAR
Metadata Catalogue
O1
A31
Maintained and Consolidated
DAR Metadata Catalogue
Catalogue Browse
Requests
I2
O4
Maintain and Expose
Consolidated DAR
Metadata Catalogue
DAR Metadata
Updates
I4
A32
"Browsable" DAR
Metadata Catalogue
O2
Dissemination
Metadata Catalogue
Maintain Dissemination
Metadata Catalogue in
Accordance with Authorised
Subscriptions
Subscriptions
I3
O3
A33
NODE: A3
116104025
TITLE:
Appendix A - 7
Maintain and Expose Catalogue of Services and Information
WWW/ISS
Page 32 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Dissemination
Metadata Catalogue
I1
Prioritised Activity
Schedule
"Ad Hoc" Requests
I3
Schedule and
Control
Activities
A51
Events
Package
Information for
Delivery
Maintained and Consolidated
DAR Metadata Catalogue
A52
I2
Reference Information
(WIGOS, IOC, etc)
Delivered Information via
WIS Information Delivery
Services
Information packaged
for delivery
I4
Information
Deliver
Information
O1
A53
Information
I5
NODE: A5
116104025
TITLE:
Appendix A - 8
Deliver Information to Users (Internal and External)
WWW/ISS
Page 33 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
Dissemination
Metadata Catalogue
I1
Time-driven Activity Schedule
Derive Time-driven
(synchronous) activity
schedule and list of
event-driven
(asynchronous)
activities
A511
R. Husband
REV:
Draft Q
Service Priorities
Resolve any activity
scheduling conflicts,
reflecting relative service
priorities
Event-driven
Activity List
AUTHOR:
"Ad Hoc" Requests
Prioritised Activity
Schedule
O1
A513
I2
Monitor for
Events
A512
Activities for which Event
Conditions are Satisfied
Events
I3
NODE: A51
116104025
TITLE:
Appendix A - 9
Schedule and Control Activities
WWW/ISS
Page 34 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Regulatory and Guidance Documents
(including applicable data policies and performance requirements)
Reports of Performance
Against Requirements and SLAs
Non Real-time
Performance
Monitoring
O1
A61
Monitoring Outputs
from all functions
Discrepancy Reports
I1
Control Actions to
All Functions
Real-time
Performance
Monitoring
O2
A62
NODE: A6
116104025
TITLE:
Appendix A - 10
Manage System Performance
WWW/ISS
Page 35 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
AUTHOR:
R. Husband
REV:
Draft Q
Traffic Trend Report (including
recommendations for evolutions/upgrades)
Monitoring Outputs
from all functions
Analyse Traffic
Trends
I1
Reports of Performance
Against Requirements and SLAs
A611
O1
Analyse
Performance
Against
Requirements and
SLAs
Discrepancy Reports
I2
A612
NODE: A61
116104025
TITLE:
Performance Report (including
recommendations for improvements)
Appendix A - 11
Non Real-time Performance Monitoring
WWW/ISS
Page 36 of 40
WMO Information System Functional Architecture
WMO INFORMATION SYSTEM
Network Status (e.g. Availability, Capacity
Utilisation, etc)
AUTHOR:
R. Husband
REV:
Draft Q
Discrepancy Reports
Real-time Monitoring
of the
Telecommunication
Network
O1
A621
Network Configuration
Actions
Monitoring Outputs
from all functions
I1
Dissemination Metadata
Catalogue
Control Actions to
All Functions
Real-time
Monitoring of the
Application Content
Application Content
Status
NODE: A62
116104025
TITLE:
O2
A622
Application Content Management Actions
(e.g. coding corrections, request for retransmission
of missing information, removal of duplication information, ....)
Appendix A - 12
Real-time Performance Monitoring
WWW/ISS
Page 37 of 40
WMO Information System Functional Architecture
APPENDIX B – Hierarchy of Functions
A0
WMO Information System (WIS)
A1
Collect Observations, Generate Products, Create Metadata and Archive Information
A11 Collect, Generate and Archive National Information & Create Metadata
A111 Collect National Observations
A112 Check Meteorological Content of Products and Observations
A113 Archive
A114 Generate National Products
A115 Generate Metadata
A116 Unpack Information
A117 Verify Correct Telecommunication Attributes of Information
A12 Collect, Generate and Archive Regional, Programme-related and
Specialised Information & Create Metadata
A121 Collect Regional, Specialised and Programme-related Observations
A122 Check Meteorological Content of Observations
A123 Archive
A124 Generate Regional, Specialised and Programme-related Products
A125 Generate Metadata
A126 Unpack Information
A127 Verify Correct Telecommunication Attributes of Information
A13 Collect and Cache Global Information
A131 Unpack Information
A132 Associate Information with DAR Metadata
A133 Verify Correct Communication Attributes of Information
A134 Maintain and make available Cache of Global Information for 24
Hours
A2
Assign User Role
A3
Maintain and Expose Catalogue of Services and Information
A31 Search DAR Metadata Catalogue
A32 Maintain and Expose Consolidated DAR Metadata Catalogue
A33 Maintain Dissemination Metadata Catalogue in Accordance with Authorised
Subscriptions
A4
Authorise Access to Information by Users
A5
Deliver Information to Users (Internal and External)
A51 Schedule and Control Activities
A511 Derive Time-driven (synchronous) activity schedule and list of eventdriven (asynchronous) activities
A512 Monitor for Events
A513 Resolve any activity scheduling conflicts, reflecting relative service
priorities
A52 Package Information for Delivery
A53 Deliver Information
A6
Manage System Performance
A61 Non Real-time Performance Monitoring
A611 Analyse Traffic Trends
A612 Analyse Performance Against Requirements and SLAs
A62 Real-time Performance Monitoring
A621 Real-time Monitoring of the Telecommunication Network
A622 Real-time Monitoring of the Application Content
116104025
WWW/ISS
Page 38 of 40
WMO Information System Functional Architecture
APPENDIX C – List of Abbreviations
Cg
CBS
DAR
DCPC
ECMWF
GEO
GDPFS
GEOSS
GISC
GOS
GTS
ICAO
ICG-WIS
ICT
IGDDS
IMTN
ISS
MTN
NC
NMC
NMHS
RM-ODP
RTH
SDI
SOA
TCP/IP
V-GISC
WIGOS
WIS
WMC
WMO
WPIP
WWW
116104025
World Meteorological Congress
Commission for Basic Systems
Discovery, Access and Retrieval
Data Collection or Production Centre
European Centre for Medium Range Weather Forecasts
Group on Earth Observation
Global Data Processing and Forecast System
Global Earth Observations System of Systems
Global Information System Centre
Global Observing Systems
Global Telecommunication System
International Civil Aviation Organisation
Inter-Commission Coordination Group on WMO Information System
Information and Communications Technology
Integrated Global Data Distribution System
Improved Main Telecommunication Network
Information Systems and Services (Programme Area of CBS)
Main Telecommunication Network
National Centre
National Meteorological Centre
National Meteorological and Hydrological Service
Reference Model for Open Distributed Processing (ISO/IEC 10746)
Regional Telecommunication Hub
Spatial Data Infrastructure
Service Oriented Architecture
Transmission Control Protocol / Internet Protocol
Virtual Global Information System Centre
WMO Integrated Global Observation Systems
WMO Information System
World Meteorological Centre
World Meteorological Organization
WIS Project and Implementation Plan
World Weather Watch (Programme or System)
WWW/ISS
Page 39 of 40
WMO Information System Functional Architecture
APPENDIX D – Glossary of Terms
TERM
DESCRIPTION
Reference Information:
Slowly varying auxiliary information that is needed by WIS to
implement the functions (e.g. place names, centre names, airport
abbreviations, country boundaries, etc) – see Volumes A, C1, C2
and D of WMO Manual on Weather Reporting (WMO No.9).
Data, Products and Information:
In CBS data is generally defined as observations. When
observations are combined into summaries or used to derive new
information, they are then referred to as products. When describing
data and products, CBS refers to them as information. To systems
people, any information passing through their systems is data, and
this is reflected in many of the common terminologies such as data
management or data volumes which in this context really mean
information management and information volumes.
116104025
WWW/ISS
Page 40 of 40