FEWS-NL Acceptance Testing Document - part 1: Live System

(1)

FEWS-NL

(2)

Prepared for:

DG Rijkswaterstaat, RIZA

FEWS-NL

Acceptance Testing Document

Albrecht Weerts

(3)

For the Site Acceptance Test (SAT) of the FEWS-NL test scripts have been prepared. The test scripts for the Site Acceptance Test are a subset of the tests included in the Acceptance Test Documentation.

The Acceptance Test Documentation comprises the following documents: · Part 1: Live System

· Part 2: Implementation – Rhine and Meuse · Part 3: Master Controller

The FEWS-NL Acceptance Testing Document – Part 1: Live System is presented in this document.

Guide to the reader

(4)

FEWS-NL Q4025.00 May, 2006

Acceptance Testing Document Part 1: Live System

WL | Delft Hydraulics _i

1

Test Record

Test Performed By A. Weerts (WL | Delft Hydraulics) & E. Sprokkereef (RIZA Arnhem)

A. Weerts (WL | Delft Hydraulics) & L. van Hal/ B. van der Pas (RIZA Arnhem)

Date of Test 7/04/2006 & 2/5/2006

Version of Software Tested FewsNL 1.70 April 2006

Overall pass/fail Pass

Observations & comments

(7)

2

Introduction

2.1 Purpose of this document

This document defines the steps to be taken to perform system tests and to compare the results of the tests with the expected outcome for each test. It is intended to be printed and the test pass/fail information hand written on it during testing. The annotated document plus any additional materials (printouts etc) form the test record and will be filed.

2.2 Scope of this document

This document is intended to test the FEWS-NL system as it stands at SAT and the implementation of each both the Meuse and the Rhine implementation.

2.3 Context of this issue

(8)

FEWS-NL Q4025.00 May, 2006

3

Setting up the Test

3.1 Installation of FEWS-NL

The operational forecasting system tests will be run using the Rhine and Meuse configurations of FEWS-NLas set up in the operational environment at RIZA Arnhem. Although each test will be described to use a particular regional configuration, the actual; configuration used may vary.

3.2 Test Procedure

The tests described in this document describe functionality provided by FEWS-NL to act as a live forecasting system. All tests will be done through use of the Operator Clients of the applicable region.

(9)

4

Test LS.1: Connecting to the Live System

4.1 Starting Operator Client – Fully Synchronised Profile

Objective: The objective of this test is to confirm the Operator Client correctly connects to the

Live System with a “fully synchronised” profile.

Using this profile all the data available in the central database will be synchronised to the local data store. These data cover a period of up to the length of the rolling barrel

Reference:

Test Record (please include name and signature)

Date of test: _____________________________________

RIZA representative: _____________________________________

Delft/Tessella representative _____________________________________

Method:

· Prior to commencing the test, any Operator Clients running on the computer on which the test is to be performed must be switched off.

· To avoid having to wait too long for a full synchronisation, this test is carried out with an Operator Client that has recently been synchronised

Settings:

No. Expected Results Pass Fail

LS.1-1 (a)

Double-Click the Icon for FEWS-NL.

A splash screen with the name of the FEWS-NL will show. Progress on the system starting up is shown in the splash screen

The main map display renders. LS.1-1

(b)

(10)

FEWS-NL Q4025.00 May, 2006

LS.1-1 (d)

After synchronisation of time series is complete, check the available data and confirm this is as expected for the selected profile for both the Meuse and the Rhine

NOTE: Inspect the profile to determine the expected length of series synchronised and the data types included.

Please make any addition comments on the test here

(11)

4.2 Starting Operator Client – Minimum Profile

Live System with a minimum synchronisation profile.

Using this profile a selection of data available in the central database is synchronised. How this selection is made is configured in the applicable log-on profile. The download of data is similar to the fully synchronised profile, except that at initial log-on only the last 48 hours of data is

downloaded. Grids are not included.

Reference:

Date of test: _____________________________________

Method:

· To confirm the synchronisation using this minimum profile is correct, the local data store is first deleted prior to commencing the test

Settings:

LS.1-2 (a)

A splash screen with the name of the FEWS-NL implementation will show. Progress on the system starting up is shown in the splash screen LS.1-2

(b)

The main map display renders. A screen is automatically displayed requesting the user to select the Master Controller to log and the Synchronisation Profile.

LS.1-2 (c)

Select the first Master Controller on the list and the “Minimum Synchronised” Profile

Two event messages of level INFO indicating the log on to the Master Controller is successful is generated:

(12)

FEWS-NL Q4025.00 May, 2006

NOTE: The actual length of the time series may be longer, as the item that determines i fit is considered is when the time series became available to FEWS-NL

(13)

4.3 Starting Operator Client – Custom Profile

Live System with a Modem profile.

Using this profile a selection of data available in the central database is synchronised. How this selection is made is configured in the applicable log-on profile. Additional options on the length of the time series synchronised as well as specific data types can be selected

Reference:

Date of test: _____________________________________

Method:

· To confirm the synchronisation using this custom profile is correct, the local data store is first deleted prior to commencing the test

Settings:

LS.1-3 (a)

A splash screen with the name of the FEWS-NL implementation will show. Progress on the system starting up is shown in the splash screen LS.1-3

(b)

The main map display renders. A screen is automatically displayed requesting the user to select the Master Controller to log and the Synchronisation Profile.

LS.1-3 (c)

Select the first Master Controller on the list and the “Custom” Profile. Select the required time length of synchronisation

Two event messages of level INFO indicating the log on to the Master Controller is successful is generated:

(14)

FEWS-NL Q4025.00 May, 2006

(15)

5

Test LS.2: Data Synchronisation

5.1 Synchronisation of log events

Objective: The objective of this test is to confirm the log events generated by the Forecasting

Shell Servers and the Master Controller are synchronised at the configured intervals and available for reviewing on the Operator Client.

Reference:.

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client for FEWS-NL is turned on. Any

synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which log events are synchronised may vary.

Settings:

LS.2-1 (a)

On the operator client – select the “System Monitor” item from the menu. Set the level to “INFO” and click on Refresh

The list of INFO messages contains recent entries. LS.2-1

(b)

Enter “TaskRun” as an external event code to search on – click on refresh

The list of filtered messages contains recent entries showing that tasks were executed on the forecasting shell server(s)

LS.2-1 (c)

Repeat steps a-b for Meuse

(16)

FEWS-NL Q4025.00 May, 2006

(17)

5.2 Synchronisation of import data

Objective: The objective of this test is to confirm data imported from external sources on the

Forecasting Shell Servers are synchronised first to the Master Controller following Import and subsequently to the Operator Client for viewing.

Reference:.

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client for FEWS-NL is turned on. Any

synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which import data is synchronised may vary.

· The test is undertaken using MSW and meteorological data only. However, the test may be repeated if requested for other types of import data relevant to FEWS-NL.

Settings:

LS.2-2 (a)

On the operator client – select the “Hydro Measurements” filter. Select the parameter Water Level (H.m).

The icons on the main map display indicate where data is available. If there is no data available a cross is displayed for that location. The expected result is that most of the locations will have data available. LS.2-2

(b)

Select a location where the icon indicates data is available. Select the chart menu.

The chart appears and recent data is displayed for the selected location LS.2-2

(c)

Repeat steps a-b for the Meuse

(18)

FEWS-NL Q4025.00 May, 2006

(19)

5.3 Synchronisation of current forecasts – scheduled

Objective: The objective of this test is to confirm the current forecast run created on the

forecasting shell server through a scheduled forecasting run is automatically uploaded to the Operator Client for viewing.

Reference:.

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client is turned on. Any synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which the operator clients checks for a recent current forecast may vary.

Settings:

LS.2-3 (a)

Start the Operator Client for FEWS-NL. On the operator client – select the “Forecast Management” from the menu. Open the “Current Forecast” tab

The list of forecasts in the local data store displays the most recent current forecast as would be expected from the forecast schedule LS.2-3

(b)

Each of the entries in the list of current forecasts (upper list box) is unique. i.e. there are no duplicates in the list

LS.2-3 (c)

Open the “Forecast Overview” tab

Current forecasts are indicated with a green icon

Approved Forecasts that were previously current are indicated with a different icon

LS.2-3 (c)

Repeat steps a-c for the Meuse

(20)

FEWS-NL Q4025.00 May, 2006

(21)

5.4 Synchronisation of a modified system configuration

Objective: The objective of this test is to confirm that a system configuration which is modified

on an operator client can be uploaded to the Central Database and synchronised automatically to other Operator Clients and the Forecasting Shell Servers.

Reference:

Date of test: _____________________________________

Method:

· This test is undertaken with the FEWS-NL Rhine.

· The configuration management system for the Meuse must be available.

Settings:

No. Actions and expected Results Pass Fail

LS.2-7 (a)

· Ensure that the OC for FEWS-NL is not running

· Initiate the configuration management system for FEWS-NL · Select the “RegionConfigFiles”item in the tree view on the left · Review the default version available for Filters

The active version for Filters is version 2.00, and is marked in yellow. LS.2-7

(b)

· Exit the configuration management system for the Rhine · Open the OC FEWS-NL

· Open the manual forecast run. Select the worklow “Rijn_Forecsst_HIRLAM”

· Wait till the run is complete, and download results using the forecast management dialogue.

· Approve the run just downloaded as the “Current Forecast” LS.2-7

(c)

· Exit the OC FEWS-NL

· Return to the configuration management system for Rhine region · Select the “RegionConfigFiles”item in the tree view on the left · Review the default version available for Filters

(22)

FEWS-NL Q4025.00 May, 2006

(d) · Open the operator client FEWS-NL Rhine · Open the manual forecast run. Select the worklow

“Rijn_Forecast_HIRLAM”. Set the T0 to that used previously if this has changed and submit the run

· Wait till the run is complete, and download results using the Forecast management dialogue.

Open the run, and compare

Free space to write any explanations or observations on the test Filter 1.00 does not work with current config.

(23)

6

LS.3: Importing Live Data Feeds

Initial Condition FEWS-NL Test documentation available Live FEWS-NL system available

(24)

FEWS-NL Q4025.00 May, 2006

6.1 Importing live data – MSW

Objective: The objective of this test is to confirm FEWS-NL correctly imports live data from

MSW.

Reference:

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client is turned on. Any synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which import data is synchronised may vary.

· To allow the test to be done in its entirety, the directory where external data is written must be accessible. The location of this directory may be checked by reviewing the input files on the forecasting shell server.

· Prior to running the test the scheduled import run for the region should be suspended using the administrator interface. The scheduled run should be unsuspended after completing the test. NOTE:

LS.3-1 (a)

Open FEWS-NL Rhine region. Monitor the data where the Rhine files obtained from MSW are written to be imported into FEWS-NL

NOTE: A further check can be made by opening an MSW file and noting the name of the location, the parameter plus the time/value.

LS.3-1 (b)

On the operator client

· Manually run an “Import_External” worklflow.

· Select the “Hydro measurements” filter. Select the parameter Water levels (H.m).

The icons on the main map display indicate where data is available. If there is no data available a cross is displayed for that location. The expected result is that most of the locations will have data available. NOTE: Depending on the synchronisation profile, the frequency with which import data is retrieved to the operator client may vary. A

synchronisation message indicating the activity ImportData has been run should have been seen before the data becomes available on the operator client.

LS.3-1 (c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the MSW file if this step has been carried out (the correct location should then be selected)

(25)

MSW data is correctly imported for FEWS-NL Meuse region

(26)

FEWS-NL Q4025.00 May, 2006

6.2 Importing live data – BC2000

Objective: The objective of this test is to confirm FEWS-NL correctly imports live data from

BC2000.

Reference: FSD2.3.3, LTD 2.4.5

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client is turned on. Either the full synchronisation profile may be selected or the custom profile.

· To allow the test to be done in its entirety, the directory where external data is written must be accessible. The location of this directory may be checked by reviewing the input module configuration files on the forecasting shell server.

LS.3-2 (a)

Open FEWS-NL Rhine region. Monitor the data where the BC2000 files are written to be imported into FEWS-NL

At regular intervals, new data files will appear in this directory. NOTE: A further check can be made by opening an BC2000 file and noting the name of the location, the parameter plus the time/value LS.3-2

(b)

On the operator client – select the “Hydro measurements” filter. Select the parameter “Water Level (H.m)”.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the BC2000 file if this step has been carried out (the correct location should then be selected)

(27)

6.3 Importing live data – ttrr

Objective: The objective of this test is to confirm the FEWS-NL correctly imports live

meteorological data

Reference:

Date of test: _____________________________________

Method:

LS.3-3 (a)

Open FEWS-NL Rhine region. Monitor the data where the ttrrfiles are written to be imported into FEWS-NL

LS.3-3 (b)

On the operator client – select the “meteo measurements” filter. Select the parameter “Precipitation (P.m)”.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the ttrr file if this step has been carried out

(28)

FEWS-NL Q4025.00 May, 2006

6.4 Importing live data – KNMI_Synoptic

meteorological data

Reference:

Date of test: _____________________________________

Method:

LS.3-4 (a)

Open FEWS-NL Meuse region. Monitor the data where the KNMI_Synoptic files are written to be imported into FEWS-NL

LS.3-4 (b)

On the operator client – select the “meteo measurements” filter. Select the parameter “Precipitation (P.m)”.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the KNMI_synoptic file if this step has been carried out

Free space to write any explanations or observations on the test

(29)

meteorological data

Reference:

Date of test: _____________________________________

Method:

LS.3-5 (a)

Open FEWS-NL Rhine region. Monitor the data where the ttrrfiles are written to be imported into FEWS-NL

LS.3-5 (b)

On the operator client – select the “meteo measurements” filter. Select the parameter “Precipitation (P.06) and the parameter “Precipitation (P.12)”.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the synopfile if this step has been carried out

(30)

FEWS-NL Q4025.00 May, 2006

6.6 Importing live data – External Forecasts (WSD)

Objective: The objective of this test is to confirm FEWS-NL correctly imports the WSD external

forecasts. This test is applicable only to the Rhine.

Reference:

Date of test: _____________________________________

Method:

· This test may be undertaken using Meuse or Rhine region

LS.3-6 (a)

Open FEWS-NL Rhine region. Monitor the data where WSD files are written to be imported into FEWS-NL

A new WSD formatted data files will appear in this directory on a new forecast being made. This file is updated once every 6-24 hours. The test confirms only the directory is correctly available.

LS.3-6 (b)

On the operator client – select the “external forecast” filter.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the WSD file if this step has been carried out

(31)

6.7 Importing live data – KNMI_Hirlam Forecasts

Objective: The objective of this test is to confirm FEWS-NL correctly imports the KNMI_Hirlam

forecast. This test is applicable only to both the Rhine and the Meuse.

Reference:

Date of test: _____________________________________

Method:

LS.3-7 (a)

Open FEWS-NL Rhine region. Monitor the data where

KNMI_HIRLAM files are written to be imported into FEWS-NL A new KNMI HIRLAM formatted data files will appear in this directory on a new forecast being made. This file is updated once every 6-24 hours. The test confirms only the directory is correctly available. LS.3-7

(b)

On the operator client – select the “GRID display” filter.

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the KNMI_HIRLAM file if this step has been carried out

(32)

FEWS-NL Q4025.00 May, 2006

WL | Delft Hydraulics _{6 — 1 0}

6.8 Importing live data – DWD_GME Forecasts

Objective: The objective of this test is to confirm FEWS-NL correctly imports the DWD_GME

Reference:

Date of test: _____________________________________

Method:

LS.3-8 (a)

Open FEWS-NL Rhine region. Monitor the data where DWD_GME files are written to be imported into FEWS-NL

A new DWD-GME formatted data files will appear in this directory on a new forecast being made. This file is updated once every 12 hours. The test confirms only the directory is correctly available.

LS.3-8 (b)

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the DWD_GME file if this step has been carried out

(33)

Objective: The objective of this test is to confirm FEWS-NL correctly imports the DWD_LME

Reference:

Date of test: _____________________________________

Method:

LS.3-9 (a)

Open FEWS-NL Rhine region. Monitor the data where DWD_LM2 files are written to be imported into FEWS-NL

A new DWD-LM2 formatted data files will appear in this directory on a new forecast being made. This file is updated once every 12 hours. The test confirms only the directory is correctly available.

LS.3-9 (b)

(c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the DWD_LM2 file if this step has been carried out

(34)

FEWS-NL Q4025.00 May, 2006

6.10 Importing live data – ECMWF_DET Forecasts

Objective: The objective of this test is to confirm FEWS-NL correctly imports the ECMWF_DET

Reference:

Date of test: _____________________________________

Method:

LS.3-10 (a)

Open FEWS-NL Rhine region. Monitor the data where ECMWF_DET files are written to be imported into FEWS-NL

A new ECMWF-DET formatted data files will appear in this directory on a new forecast being made. This file is updated once every 24 hours. The test confirms only the directory is correctly available.

LS.3-10 (b)

The icons on the main map display indicate where data is available. If there is no data available a cross is displayed for that location. The expected result is that most of the locations will have data available.

LS.3-10 (c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the ECMWF_DET file if this step has been carried out

(35)

Objective: The objective of this test is to confirm FEWS-NL correctly imports the ECMWF_EPS

Reference:

Date of test: _____________________________________

Method:

LS.3-11 (a)

Open FEWS-NL Rhine region. Monitor the data where ECMWF_EPS files are written to be imported into FEWS-NL

A new ECMWF-EPS formatted data files will appear in this directory on a new forecast being made. This file is updated once every 24 hours. The test confirms only the directory is correctly available.

LS.3-11 (b)

The icons on the main map display indicate where data is available. If there is no data available a cross is displayed for that location. The expected result is that most of the locations will have data available.

LS.3-11 (c)

The chart appears and recent data is displayed for the selected location. The table includes the data seen in the ECMWF_EPS file if this step has been carried out

(36)

FEWS-NL Q4025.00 May, 2006

7

LS.4: Operational Forecasting

(37)

7.1 Running scheduled current forecast

Objective: The objective of this test is to confirm the FEWS-NL system correctly runs the

scheduled current forecast as configured.

Reference:.

Date of test: _____________________________________

Method:

LS.4-1 (a)

Start FEWS-NL Rhine region. On the operator client – select the “System Monitor” from the menu. Open the “Forecasting Schedules” tab A list of scheduled forecasting runs is displayed. The list includes the workflow, the next pending time and the repeat time.

LS.4-1 (b)

Open the “Forecast management” display.

Confirm that the current forecast available in the local data store is the most recent of the scheduled runs

LS.4-1 (c)

Open the “Forecast management” display.

Confirm that Approved forecast are listed either available locally or centrally at the expected intervals.

LS.4-1 (d)

Open the “Forecast Overview” tab

Current forecasts are indicated with an exclamation mark in a green icon Approved Forecasts that were previously current are with an exclamation mark in a white icon

(38)

FEWS-NL Q4025.00 May, 2006

7.2 Running manual forecast – single run

Objective: The objective of this test is to confirm the FEWS-NL system correctly allows a manual

forecast run to be submitted through an operator client, that the forecast run is executed, and that the data can be retrieved.

Reference:

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client is turned on. Any synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which the operator clients check for a recent current forecast may vary.

Settings:

LS.4-2 (a)

Start FEWS-NL Rhine region. On the operator client – select the “Manual Forecast” from the menu. Select a workflow. Select run. The requested forecast run is submitted for running.

LS.4-2 (b)

Wait till the run completes and is displayed in the forecasts available in the central database.

The recently run forecast is added to the list of completed forecasts

(39)

7.3 Running manual forecast – scheduled run

Objective: The objective of this test is to confirm the FEWS-NL system correctly allows a

scheduled forecast to be submitted through an operator client, that the forecast run is executed as scheduled, and that the data for each run can be retrieved.

Reference:

Date of test: _____________________________________

Method:

Settings:

LS.4-3 (a)

Start FEWS-NL Rhine region. On the operator client – select the “Manual Forecast” from the menu. Select a workflow.

Set the following forecasting :

· Start time to a time 5 min after the current system time · End time to a time 10 minutes after the start time · Interval to 5 minutes

· Leave the T0 shift at zero Select run.

The requested forecast scheduled run is submitted for running. LS.4-3

(b)

On the operator client – select the “System Monitor” from the menu. Open the “Forecasting Schedules” tab

A list of scheduled forecasting runs is displayed. The list includes the run just submitted, the next pending time and the repeat time.

(40)

FEWS-NL Q4025.00 May, 2006

(41)

7.4 Running a manual forecast – specifying a cold state

Objective: The objective of this test is to confirm the FEWS-NL system correctly allows a manual

forecast to be submitted where a cold state start is selected

Reference:

Date of test: _____________________________________

Method:

· This test may be undertaken with either the Rhine or the Meuse region

Settings:

LS.4-7 (a)

· On the operator client – select the “Manual Forecast” from the menu.

· Select a workflow to run a forecast Rhine: Rijn_Forecast_HIRLAM Meuse:Maas_Forecast_HIRLAM · Select the option “Select Initial State” · Select the option “Cold State”

· Set the type of state to use as the “Default” state.

· Set the relative start time to a time longer than the shortest possible period in the configuration (8 days).

· Submit the run

The requested forecast run is submitted for running. LS.4-7

(b)

(42)

FEWS-NL Q4025.00 May, 2006

(43)

8

LS.5: Data viewing and editing

(44)

FEWS-NL Q4025.00 May, 2006

8.1 View current forecast

Objective: The objective of this test is to confirm the FEWS-NL system correctly automatically

allows the current forecast to be viewed automatically on the operator clients.

Reference:.

Date of test: _____________________________________

Method:

· This test is closely related to test LS.4-1

Settings:

LS.5-1 (a)

· Start FEWS-NL Rhine

· Open the “Forecast management” display.

LS.5-1 (b)

· Open the chart using the menu

· With the shortcuts – view the forecast data available.

Without requiring the selection of a specific forecast, data for the current forecast is displayed.

LS.5-1 (c)

· Repeat steps a-b for Meuse region

(45)

(46)

FEWS-NL Q4025.00 May, 2006

8.2 View other forecast

Objective: The objective of this test is to confirm the FEWS-NL system correctly allows other

forecasts than the current forecast to be selected and viewed

Reference:

Date of test: _____________________________________

Method:

Settings:

LS.5-2 (a)

Confirm that the list of approved forecasts is available in the central database (or the local data store).

NOTE: If the Operator Client has been running for some time, the approved forecasts will already be available locally.

LS.5-2 (b)

· If necessary, download the approved forecast previous to the current approved forecast

· Open the approved forecast previous to the current approved forecast

· Select the opened forecast in the Forecast filter · With the shortcuts – view the forecast data available.

Charts now show both the current forecast and data for the selected forecast. An integer prefix is added in the legend to identify the forecasts.

LS.5-2 (c)

· Repeat steps a-b for Meuse region

(47)

(48)

FEWS-NL Q4025.00 May, 2006

8.3 Edit data value

Objective: The objective of this test is to confirm the FEWS-NL system correctly allows a time

series to be edited on an operator client, and that the edited value is made available through synchronisation to all forecasting shell servers and other operator clients.

Reference:

Date of test: _____________________________________

Method:

· Prior to commencing the test two operator client are turned on. Both are connected to the same system. Any synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which the operator clients check for changes in data may vary.

LS.5-3 (a)

· Open FEWS-NL Rhine region · Log out of the MC

· Select the filter “Hydro Measurements” · Select a suitable location

· Select the parameter “Water levels” · Open the Table/Chart in edit mode

Confirm the table is available in edit mode (background is white) LS.5-3

(b)

· Manually enter/amend some of the values in the table by double clicking on the cells to amend and filling the desired value. Press <Enter> once the entry is complete

Confirm the values can be entered manually LS.5-3

(c)

· Copy 4 values in a column from Excel. Note that at least four rows must be selected in the edit window to copy the four values Confirm the values can be copied from (e.g.) Excel

LS.5-3 (d)

· Confirm the edit by clicking on “Apply” · Confirm the changes on request.

· Log in to the MC (this will force the synchronisation of edited series)

A message is displayed asking to confirm the changes LS.5-3

(e)

· Monitor the data on the second Operator Client connected to the standby Master controller

(49)

(50)

FEWS-NL Q4025.00 May, 2006

9

LS.6: Publishing and exporting forecasts

Initial Condition FEWS-NL Test documentation available LiveFEWS-NL system available

(51)

9.1 Export of forecast reports to Web Server– Scheduled

current forecast

Objective: The objective of this test is to confirm the FEWS-NL system correctly exports reports

from the scheduled current forecast for viewing through the operator client.

Reference:

Date of test: _____________________________________

Method:

· This test is closely related to test LS.6-1 and may be carried out in conjunction.

Settings:

LS.6-3 (a)

LS.6-3 (b)

· Open the web display through the “Reports” menu item · View the current forecast reports

(52)

FEWS-NL Q4025.00 May, 2006

(53)

9.2 Export of forecast reports to Web Server– Manually

acknowledged current forecast

Objective: The objective of this test is to confirm the FEWS-NL system correctly exports reports

from a manual forecast acknowledged as current forecast for viewing through the operator client.

Reference:

Date of test: _____________________________________

Method:

· This test is closely related to test LS.6-2 and may be carried out in conjunction.

NOTE Exporting reports to the Web server involves copying of files over a Windows to Unix shared directory. As this is a relatively slow connection it may take up to several minutes before all reports are copied.

Settings:

LS.6-4 (a)

· Open the “Manual Forecast” display. · Select a forecast workflow, and submit to run

Rhine: Rijn_Forecast_HIRLAM Meuse:Maas_Forecast_HIRLAM

· Wait for the forecast to complete, then download

· Set the run as current forecast through the forecast management display.

Confirm that the current forecast available in the local data store is updated as requested

LS.6-4 (b)

(54)

FEWS-NL Q4025.00 May, 2006

WL | Delft Hydraulics _{1 0 — 1}

10

LS.7: Viewing system status

(55)

10.1 View system status

Objective: The objective of this test is to confirm the FEWS-NL system allows viewing of the

status of the Live System.

Reference:.

Date of test: _____________________________________

Method:

· Prior to commencing the test an operator client is turned on. Any synchronisation profile may be selected. However, depending on the synchronisation profile chosen the frequency with which the operator clients check the system status may vary.

· Prior to opening the system status a forecast should be initiated.

Settings:

LS.7-1 (a)

Open FEWS-NL Rhine region.

· Open the “System Monitor” display. · Select the “Log Browser” tab

Log messages of differing levels are displayed LS.7-1

(b)

· Open the “System Monitor” display. · Select the “Live System Status” tab

An overview is given of the live system; including · Availability of the master controller

· Availability of forecasting shell servers · Length of task queues

(56)

FEWS-NL Q4025.00 May, 2006

· Repeat time (minutes) · Next due time

· Status (pending or suspended)

Note: Tasks that are initiated through an event are indicated as suspended

LS.7-1 (d)

· Open the “System Monitor” display. · Select the “Running Forecast” tab

· An overview is given of the currently running forecast runs (if any) This should indicate at least one task – ie the fluvial forecast just initiated (note: some time may be required in updating and refreshing the status display depending on the synchronisation profile selected).

· Wait till the forecast run is completed and removed from the running tasks list automatically. This may last a few minutes (run length plus display refresh interval)

(57)

11

LS.8: Archiving forecasts

(58)

FEWS-NL Q4025.00 May, 2006

11.1 Archiving forecasts

Objective: The objective of this test is to confirm the FEWS-NL system allows a forecast to be

selected and archived.

NOTE: The forecast to archive should be selected such that that forecast will be imminently removed from the system (ie 29 or 30 days old). This to allow re-loading the forecast to the live system.

NOTE: When a forecast run is given with a red font colour in the list of forecasts to be archived this means that data was used by the run that has already expired and as such been deleted from the local data store. As a consequence these runs can no longer be archived as the source data for the run is incomplete. Normally these will be runs just about to fall off the rolling barrel.

Reference:

Date of test: _____________________________________

Method:

· Scheduled forecasts for the selected region are suspended before commencing the test. · Prior to commencing the test an operator client is turned on. Any synchronisation profile may

be selected. However, depending on the synchronisation profile chosen the frequency with which the operator clients check for a recent current forecast may vary.

· To run the test – the export directory for archived forecasts must be accessible

LS.8-1 (a)

· Open FEWS-NL Rhine region

LS.8-1 (b)

· Open the “Forecast management” display. · Select the tab “Archived Forecast””

· Set the option to write to export folder to true

· Select the most recent current forecast - click on “Create

Confirm that an archived forecast is made. The newly archived forecast is added to the list of available archived forecasts. Please note that progress of the production of the archive workflow can be followed via the ‘running forecasts’ tab in the System Monitor.

NOTE: The archived forecast is created on the Forecasting shell Servers. Depending on the synchronisation profile selected, the time for the archived forecast to appear may vary

LS.8-1 (c)

(59)

(60)

FEWS-NL Q4025.00 May, 2006

11.2 Viewing archived forecast

Objective: The objective of this test is to confirm the FEWS-NL system allows an archived

forecast to be selected, opened and the results viewed.

Reference:

Date of test: _____________________________________

Method:

· The archived forecast is viewed on a stand-alone system. The local data store should be deleted from the system before running the test.

· The import directory configured on the stand alone system for archived forecast must be accessible.

LS.8-2 (a)

· Open FEWS-NL Rhine region (stand alone)

· Copy the ZIP file with the archive created in the previous test to the import directory for archives in the stand-alone system.

· Initiate the stand-alone system

· Open the “Forecast management” display. · Open the “Archived Forecast”

· Set Read from Import folder to True · Click “Restore”

Confirm the archived forecast is unpacked and added as a forecast available in the local data store. The import may last several minutes. LS.8-2

(b)

· Open the “Forecast management” display. · Open the tab “Forecast Overview”

· Open the recently unpacked forecast for viewing The unpacked forecast is opened in the explorer for viewing LS.8-2

(c)

· Use the chart and shortcuts to explore the data in the unpacked archived forecast. Compare to the data of that forecast in the live system.

(61)

(62)

FEWS-NL Q4025.00 May, 2006

11.3 Re-running archived forecast – rerun

Objective: The objective of this test is to confirm the FEWS-NL system allows an archived

forecast to be selected, opened and re-run as at the time the forecast was archived.

Reference:

Date of test: _____________________________________

Method:

· The archived forecast is viewed on a stand-alone system. The local data store should be deleted from the system before running the test.

· The import directory configured on the stand alone system for archived forecast must be accessible.

· This test is closely related to the previous test

LS.8-3 (a)

· Open FEWS-NL Rhine region (stand alone)

· Copy the ZIP file with the archive created in the previous test to the import directory for archives in the stand-alone system.

· Initiate the stand-alone system

· Open the “Forecast management” display. · Open the “Archived Forecast”

· Set Read from Import folder to True · Click “Restore”

Confirm the archived forecast is unpacked and added as a forecast available in the local data store

LS.8-3 (b)

· Open the tab “Forecast Overview”

· Open the recently unpacked forecast for viewing The unpacked forecast is opened in the explorer for viewing LS.8-3

(c)

· Open the “Forecast management” display. · Open the tab “Forecast Overview”

· Rerun the imported archived forecast by clicking the “Run” button · Please note that after the run is completed, it can be recognised by

the dispatch time.

· Compare the results of the re-run to the original archived forecast data

(63)

FEWS-NL Acceptance Testing Document - part 1: Live System

FEWS-NL

DG Rijkswaterstaat, RIZA

FEWS-NL

Guide to the reader

Contents

1

Test Record

2

Introduction

2.1 Purpose of this document

2.2 Scope of this document

2.3 Context of this issue

3

Setting up the Test

3.1 Installation of FEWS-NL

3.2 Test Procedure

4

Test LS.1: Connecting to the Live System

4.1

Starting Operator Client – Fully Synchronised Profile

4.2 Starting Operator Client – Minimum Profile

4.3

Starting Operator Client – Custom Profile

5

Test LS.2: Data Synchronisation

5.1

Synchronisation of log events

5.2

Synchronisation of import data

5.3

Synchronisation of current forecasts – scheduled

5.4

Synchronisation of a modified system configuration

6

LS.3: Importing Live Data Feeds

6.1

Importing live data – MSW

6.2

Importing live data – BC2000

6.3

Importing live data – ttrr

6.4

Importing live data – KNMI_Synoptic

6.6

Importing live data – External Forecasts (WSD)

6.7

Importing live data – KNMI_Hirlam Forecasts

6.8

Importing live data – DWD_GME Forecasts

6.10 Importing live data – ECMWF_DET Forecasts

7

LS.4: Operational Forecasting

7.1

Running scheduled current forecast

7.2

Running manual forecast – single run

7.3 Running manual forecast – scheduled run

7.4

Running a manual forecast – specifying a cold state

8

LS.5: Data viewing and editing

8.1 View current forecast

8.2

View other forecast

8.3

Edit data value

9

LS.6: Publishing and exporting forecasts

9.1

Export of forecast reports to Web Server– Scheduled

current forecast

9.2

Export of forecast reports to Web Server– Manually

acknowledged current forecast

10

LS.7: Viewing system status

10.1 View system status

11

LS.8: Archiving forecasts