FloodWorks Technical Review
© Innovyze 1 01/07/2012
Real
‐
Time
Operational
Forecasting,
Warning
&
Reporting
Technical
Review
FloodWorks - Technical Review
Contents
Overview of FloodWorks ... 1 Key components of a FloodWorks System ... 2 FloodWorks Event Manager ... 2 FloodWorks Configuration Manager ... 3 FloodWorks Server ... 3 Outline of operation and functionality ... 3 Forecast module capabilities and modelling methods ... 4 Overview ... 4 Model algorithms and model components ... 4 Data manipulation and preparation algorithms ... 5 Use of observed data to update model forecasts... 5 State‐correction ... 5 Error‐prediction ... 5 Snow‐melt modelling ... 6 Rainfall‐runoff modelling ... 6 Flow routing ... 7 Storm surge modelling ... 7 Hydrodynamic modelling ... 7 Analysis module ... 8 Forecast database ... 9 FloodWorks Web Server ... 9 Licencing... 10 Configuration ... 10 Documentation ... 10 Hardware configurations ... 10 FloodWorks, Windows Terminal Server and Citrix ... 11 Software Authentication ... 12 Installation ... 13 Support and Training ... 13Innovyze FloodWo 01/07/2
Overv
FloodW hydrolo control w Typical • • • • A Flood • • • • • • FloodW architec • • • This do function requirem e orks Technic 2012view
of
Fl
Works offers gical and h within a use application Fluvial & Urban flo Operatio wasterwa Operatio and irrig dWorks syst Consolidate Pass this da Automatica Analyse and Raise alarm Publish repo Works is a cture. Some Multiple us targeted to efficiency o Complete c data source aided by a u Extensive support to for future a strategy. ocument pr nality of ments and su cal ReviewloodWor
s powerful hydrodynam er friendly, a s include: & coastal floood forecast onal manag
ater and urb onal manage ation system tem provides e and verify ata to one or ally initialise d report on b ms and integr orts, alarms forecasting of its key fe er interfaces o specific of use. configuration es, model co user friendly tools for allow opera actions and t rovides tec the Flood upport provi
rks
and comp mic modellin automated re ood forecasti ting and war gement of an drainage ement of w ms. s the functio real-time hy more model e and run the both the obs rate with ala and system g system eatures inclu s that allow users, impr n of the en onnectivity, y configurati scenario cr ators to exa then choose chnical desc dWorks sy isions availa 1 prehensive f ng, analysis eal time enving & warni rning f stormwa systems water resour onality to: ydrometric & ls of the are e models served data a arm dissemin alert status based on ude: UI function roving the ntire system alarms and ion managem reation and amine multip e the optima criptions o ystem soft able from Inn
facilities th , alarm not vironment. ing ater, rces & SCADA d a of interest and the mod nation system to the Intern a client/se nality to be ease and , including d reporting, ment GUI. d decision ple options al operating f the key ftware, IT novyze. hat integrate tification, d data from va t el results ms to broad net. erver, multi e data assi decision sup arious source cast these a i-user, mul imilation, pport and es; alarms. lti-model
Key
components
of
a
FloodWorks
System
The FloodWorks software is extremelyflexible and modular and designed to operate either on single PCs for single user applications or be distributed over multiple PCs connected across both LANs and WANs for enterprise wide implementation.
The functionality of each of the above components is discussed in the sections below.
FloodWorks
Event
Manager
The operational event management user interface, ‘FloodWorks Event Manager’, emphasises ease of use in combination with user-friendly tools for visualising and reporting forecast results. The software is developed for an international market, is available in several languages (including those using non-roman character sets) and allows Clients to specify the local technical terminology used within the interface. The following functionality is provided within in the Event Manager user interface:
• Facility to initiate new runs of the forecasting system (with selection of initial conditions) or re-run previous forecasts or variants of those forecasts;
• Scheduling of regular system runs;
• Selection of forecast options, such as forecast for selected points only, switch between alternative meteorological forecasts, apply user-configured forecasts to specific points at particular times;
• Editing of input data to correct or disable erroneous telemetry data, enter control data for structure operations, enter measured or forecast data from other sources, interpolate data.
• Facility to ‘carry-over’ user-edited data from a previous run to a new run, or to all subsequent runs.
• Map display of data from the forecast summary tables, with full pan and zoom. • Map backgrounds using data in standard ESRI formats, with labelling options. • Tabular display of data from the forecast summary tables.
• Graphical and tabular display of forecast and telemetry time-series data. • Export of time-series data and results to ASCII and csv files.
• Point and click access to time-series displays from map and tabular summary displays. • Facilities to configure standard sets of display windows, for different geographical
regions, and switch quickly between them.
• Ability to display and compare forecasts from different runs.
• Ability to instantly access results for user-configured ‘Areas of Interest’ (user-configured groups of data streams of particular interest).
• Facilities for constructing reports and bulletins (including automatic generation of bulletins) for subsequent issue via fax or e-mail, or for saving external to FloodWorks. Via the external reporting facility, output can be manually issued to a website.
• Review of errors in runs through detailed log files.
• Printing and print-preview for all displays, reports and bulletins.
• Generation of events via an external SMS program to indicate changes in system mode due to the triggering of certain combinations of events.
FloodWorks Technical Review
© Innovyze 3 01/07/2012
FloodWorks
Configuration
Manager
The operational forecasting system is supported by a powerful suite of software tools within FloodWorks Configuration Manager for configuring the FloodWorks model network over GIS backgrounds (ESRI shapefiles, standard image formats) and for building and calibrating individual model components.
These tools include:
• Τhe FloodWorks network editor for configuring the model network. This includes the set-up of sites, data streams, and forecasting points for a full range of data types, including flow, level, rainfall, snow parameters, meteorological parameters, battery voltage and a range of parameters from the hydrodynamic model;
• Calibration tools for PDM, KW and PACK model components;
• Linkage with the InfoWorks software for building and calibrating hydrodynamic models;
• Powerful workgroup model management facilities enabling: o Management of new and existing model libraries. o Management of multiple modellers on multiple projects. o Consolidation of data from multiple sources.
o Model version control and audit trail through a central ‘master’ database. o Allocates data source and confidence to model attributes using data ‘flags’. o Local administration and system management, including control of access
permissions by individual user log-in details. o Comparisons between networks.
FloodWorks
Server
Outlineofoperationandfunctionality
The following outline provides a brief description of the principal modules involved in the operation of FloodWorks.
Whenever a new forecast is initiated, the data-gathering module collects the latest data from the available data sources (telemetry, radar.) This module matches up the data points from the telemetry and other systems to the model input data series and carries out data validation and conversion of data formats. In automatic operation, or if the operator has no changes to make, these data pass directly to the forecasting module. This module feeds the data through a network of hydrological and hydrodynamic models to generate forecasts of levels, flows, structure operations and other quantities over the selected forecast period. The forecast time-series from the forecasting module are processed by the analysis module, which summarises and interprets the forecast time-series in relation to the warning levels defined for the various forecast points. The system maintains detailed log files on all aspects of its operation, including data loading procedures, forecast runs, and queue management operations. FloodWorks Queue Manager manages all of the processes of run scheduling, run allocation to clustered servers and data loading. It is the Queue Manager that enables multiple-server systems to run on a duty-duty or duty-standby configuration, enabling resilience to hardware problems or failure.
Through the Event Manager user-interface, operators can initiate additional runs, display the data from any of the runs in the form of maps, tables, graphs or reports, and construct fax or email bulletins based on the forecasts. Forecasts are run automatically at regular intervals, as scheduled
within Event Manager. Operators are also able to carry out user-runs in which they can select initial conditions for a run, initiate runs based on previous forecasts, produce forecasts only for selected parts of the network, choose between alternative meteorological forecasts, and edit any of the observed or forecast data to be used in the run. For instance, an operator might carry out a sequence of runs that differ only in the operation of selected control structures, in order to decide on the alternative that gives the lowest risk of flooding. For robustness to hardware problems, it is recommended that the FloodWorks virtual server (where the runs are carried-out) is run in parallel on two server machines (in duty-duty or duty-standby configuration) with failover capability and shared storage. This redundancy enables continued operation of the forecasting system in the event of hardware failure.
Data‐gatheringmodule
The purpose of this module is to gather data from a variety of sources and prepare the data in a form suitable for use by the forecasting module. The data gathering module is designed to collect inputs from:
• Hydrometric databases • Telemetry systems
• Weather radar, including formats from the United Kingdom, the USA and Japan • Numerical weather prediction model output
• Meteorological Department qualitative and quantitative forecasts
Each run of the data-gathering module creates a ‘snapshot’ of the input data. One or more runs of the forecasting module can be carried out using the same snapshot data, thus ensuring that any differences between forecasts are due to forecast options chosen by the operator, and not by the arrival of new data.
Forecast
module
capabilities
and
modelling
methods
Overview
FloodWorks uses a network of models to calculate forecasts of flow, level and other variables at distinct ‘forecast points’ throughout a river basin or urban catchment. Many types of model, including hydrological and hydrodynamic, can be combined into a single, integrated network. The outputs from each model can be combined with observed data in order to update the models’ forecasts, which in turn provide the input to models further downstream. If the user requires forecasts only for selected points or branches of the network, model calculations for other parts of the network are not carried out. A single, integrated model network for the entire region can thus be used very efficiently to provide forecasts for selected parts of the region. In particular, it is possible to produce forecasts for upstream reaches (using fast, hydrological models) without producing forecasts for the main reaches (involving more complex, hydrodynamic models). Unlike some other modelling systems used for forecasting, FloodWorks is specifically designed for real-time use, particularly in terms of speed of operation and robustness to missing or invalid data. Forecasts are ‘hot-started’ from previous runs and (as noted above) involve only the minimum necessary computation. Input data are validated and cross-checked, and missing or invalid data can be in-filled by specialised models within the network.
Model
algorithms
and
model
components
To help describe the capabilities of FloodWorks, it is useful to point out two different uses of the word ‘model’. The word ‘model’ may be used to refer to a method or algorithm for calculation (independent of its use in any particular catchment). FloodWorks contains a library of model algorithms, ranging from the simplest algorithm for in-filling gaps in time series, through hydrological process algorithms for rainfall-runoff modelling and flow routing, to the highly
FloodWorks Technical Review
© Innovyze 5 01/07/2012
functional InfoWorks RS, SD & CS hydrodynamic algorithms. All these algorithms run as part of a single software program, so that data can be transferred rapidly between them without the need for intermediate files. Moreover, new algorithms can be added easily during the development process, as they all share the same programming interface for data exchange. It is also common to talk of ‘models’ of specific physical entities, such as individual catchments or river reaches. A model in this sense actually consists of parameters and structural data that have been measured or calibrated for the entity in question, and that will be used by one or more model algorithms to compute the model outputs. Such a model is referred to as a component of a FloodWorks model network (just as a catchment or a river reach is a component part of a river basin). The remainder of this section is concerned with the functionality of the various model algorithms. However, the unique strength of the FloodWorks approach to river flow and urban forecasting is the ability to apply a wide variety of model algorithms within a highly flexible network of model components.
Data
manipulation
and
preparation
algorithms
FloodWorks provides a variety of simple model algorithms whose purpose is to manipulate and prepare data for the more complex hydrological models. These include algorithms to:
• Validate and cross-check data from different sources in order to detect instrument errors.
• Calculate areal-average rainfall from point measurements.
• Calculate areal-average potential evaporation from point measurements of temperature and humidity.
• Combine observed and forecast data from different sources according to user-defined priorities, for example area rainfall from rain gauge measurements, radar measurements, regional weather forecasts or user-defined forecasts;
• Convert between level and flow;
• Apply minimum values to time-series for system robustness;
• Infill missing data in time-series using a set of alternative time-series with priorities for use.
• User defined models using the Ruby scripting language. These models can be simple arithmetical calculations through to providing inputs to more complex algorithms.
Use
of
observed
data
to
update
model
forecasts
A vital feature of any forecasting system is the ability to compare observed data (usually flow data) with the corresponding model outputs and to use this information to update and improve the model forecasts. This procedure must be carried out automatically and efficiently in real time. FloodWorks provides two mechanisms for updating model forecasts using observed data, described below.
State‐correction
For simple models with a small number of internal state variables (such as rainfall-runoff models) the model output error can be interpreted as an error in the model states (arising from the accumulation of errors in the model inputs). The states can then be corrected using an empirical scheme to apportion the model error between the states. These state-correction schemes are specific to different types of model, as described in the following sections.
Error‐prediction
For complex models with many states and multiple outputs (flow routing, hydrodynamic models) it is very difficult to apportion model error between model states. Moreover, changing the internal states in such models can cause instability and generate unrealistic transients that can be avoided only by time-consuming iteration of the model calculations. However, the time-series of errors
from such models are usually highly auto-correlated and thus the errors themselves can be modelled and predicted using statistical time-series methods. FloodWorks provides auto-regressive moving average (ARMA) models for use as error-predictors – the predicted errors are then subtracted from the model output to give the updated forecast.
Snow
‐
melt
modelling
The standard choice for snowmelt modelling in a FloodWorks model network is the Pragmatic Snowmelt (PACK) model developed by CEH Wallingford, UK. The snowmelt process is represented in simplified terms using a snow store and a melt store to represent the snow pack storage. Melting of the snow store is controlled by a simple temperature index equation. The resulting melt enters the melt store where it is released slowly from its base. A second higher orifice allows release of water from the pack (snow and melt water) at a higher rate. The height of the orifice varies with the total water equivalent of the pack. This serves to represent the rapid break-up of the pack as a critical liquid water content is reached. An additional component is included to allow for incomplete spatial coverage of snow over a catchment for shallower, older packs. This employs an areal depletion curve to calculate the proportion of the catchment covered by snow, allowing some rain to fall on snow-free ground and effectively enter the rainfall-runoff model directly. Two forms of the snowmelt algorithm exist within FloodWorks. The first is used in ‘point form’ at snow survey sites and excludes the areal depletion curve. This is used to obtain errors between the model snow-pack water equivalent and the surveyed amount. These errors are transferred to the second form (the ‘catchment form’) of the model to adjust catchment snow-pack water equivalents.
Rainfall
‐
runoff
modelling
The standard choice for rainfall-runoff modelling in a FloodWorks model network is the Probability Distributed Moisture (PDM) model developed by CEH Wallingford, UK. The PDM model is a lumped conceptual model of the rainfall-runoff process at the catchment scale.
An important feature of the model is that it recognises that there is variation in the depth of soil moisture storage capacity across a catchment, and that the catchment response to rainfall will change as these stores become saturated (increasing the effective contributing area of the catchment). The probability distribution method of describing the variation in soil moisture capacity provides an efficient parameterisation that can be fitted to rainfall and flow data alone. Evaporation is expressed as a function of potential evaporation and soil moisture content. Precipitation falling on the saturated area of the catchment goes to form surface runoff which is routed through two linear reservoirs (with short time constants) while the remaining precipitation adds to the soil moisture store. Recharge to groundwater is expressed as a function of soil moisture content and goes to form base-flow, which is routed through a single reservoir (with a long time constant). Observed flow data can be used to update the model by apportioning the error in the modelled flow between the various stores in the model. The apportionment scheme and empirical gain factors used to correct the model states are determined during model calibration. The catchment is assumed to drain freely. The effects of artificial storage (dams) can be modelled using other algorithms, including simple storage options in the flow routing algorithm and more complex reservoir operations in the hydrodynamic algorithm. A specialised reservoir model algorithm can also be applied to avoid the need to use the full hydrodynamic algorithm. The PDM models within a FloodWorks network carry out continuous accounting of soil moisture both between events and from season to season. All that is required is to run the forecast system at regular (daily) intervals to keep the model states up to date. There is no need for a separate method to calculate antecedent conditions or take account of variation in response between seasons. The PDM model is suitable for forecasting over the full range of flows and has been used in operational drought management systems as well as flood forecasting systems.
FloodWorks Technical Review
© Innovyze 7 01/07/2012
Flow
routing
The KW model is the standard model for flow routing within FloodWorks, and uses the kinematic wave (KW) approximation to the St Venant equations to represent simple channel flow that is not subject to backwater effects. Lateral inflows at each node of the model may be input independently or scaled from upstream flow, and various simple functions may be applied to the flow at each node to represent the effects of out-of-channel storage or loss. If required, wave speed may be varied as a function of flow. There is no state-correction within the model; updating is achieved by applying one or more ARMA error-predictors to the model outputs. The KW model is able to provide fast and effective modelling of flow for the relatively steep, upstream reaches of a river network. Where there are significant backwater effects, complex structures, or forecast points without a level-flow relationship, a full hydrodynamic model may be required.
Storm
surge
modelling
The MULTFC Wave Transformation model predicts wave activity, given a spectral distribution of offshore wave conditions. The model uses the concept of wave rays, which are lines perpendicular to the wave crest. These rays are followed or tracked towards offshore, from a selected inshore point to the offshore edge of the grid system using Snell’s law to calculate changes in ray path due to refraction effects. Since the ray paths are reversible, each ray then gives information on how energy travels between the offshore edge to the grid system and the inshore point of interest. The MULTFC model is based on the TELURAY wave refraction model of HR Wallingford Ltd, UK.
Hydrodynamic
modelling
All three of the InfoWorks free surface hydrodynamic models are available within FloodWorks. InfoWorks RS includes full solution modelling of open channels, floodplains, embankments and hydraulic structures. Rainfall-runoff simulation is available using both event based and conceptual hydrological methods and water quality simulation is available for both conservative and non-conservative pollutants. An optional fully-dynamic, 2D surface flood simulation, integrated with the
1D open-channel and floodplain hydraulic simulation, is also available. InfoWorks SD is a fully dynamic, hydraulic modelling software solution designed specifically to fulfil the demanding requirements of today's stormwater networks.
To model rainfall infiltration and inflow accurately requires the ability to model stormwater flows through a complex environment with its diversity of underground and overland structures and paths. InfoWorks SD applies precisely the
same high quality of function and analysis to both open channels and closed conduits. Every frequently encountered stormwater hydraulic structure may be modelled in InfoWorks SD. An optional fully-dynamic, 2D surface flood simulation, integrated with the pipe and surface-channel hydraulic simulation, is also available. InfoWorks CS provides water utilities with a uniquely effective tool with which to
undertake hydrological modelling of the complete urban water cycle. Essential for identifying and justifying cost effective infrastructure improvements, InfoWorks CS also provides a practical method for operational control, including real time control, of your wastewater network.
Other applications include urban flooding and pollution prediction and the modelling of water quality and sediment transport throughout the network. As well as supporting fast and accurate network modelling, there are specific tools to support the modelling of subcatchment take-off and infiltration. Offering exceptionally fast and robust simulations, InfoWorks CS facilitates the swift modelling of total networks or any sub-network. Users may now simulate models of up to 100,000 nodes with confidence that the results will be as accurate as those for far smaller models. An optional fully-dynamic, 2D surface flood simulation, integrated with the pipe and surface-channel hydraulic simulation, is also available.
Analysis
module
The forecasting module generates time series of flow, level and other data at forecast points throughout the FloodWorks model network. The analysis module automatically summarises and interprets these time series with respect to warning criteria defined for the different forecast points and for the region as a whole. FloodWorks carries out a simple but flexible analysis of observed and forecast data in order to alert operators to potentially important events. In FloodWorks terminology, an event is a feature of a data stream (observed or forecast) that potentially merits attention. Examples include:
• Observed data flagged as out-of-range or low quality; • Data missing at times for which it would be expected;
• Observed or forecast level exceeds (or falls below) a given threshold; • Observed or forecast level rises faster than a given rate;
• Observed or forecast rainfall exceeds a given total over a given period; • Observed or forecast inflow exceeds a given total over a given period.
The FloodWorks system administrator can define and name different types of event, specify the data streams on which they may occur, and enter specific data (threshold levels, totals, periods) for each possible event on each data stream. FloodWorks post-forecast analysis detects and summarises each event, calculating time of onset, duration, peak/total and other quantities as appropriate. These are then reported through the FloodWorks Event Manager user interface in a range of ways:
• Flashing sites on the map view; • Passing of thresholds on the graphs; • Event counts in the run summary;
• Event details in the full and brief forecast summaries.
Any of these formats can be passed to FloodWorks’ externally generated MS Word reports. Combinations of triggered events underpin the concept of FloodWorks ‘modes’. A mode is defined as the state of alert of the flood forecasting system at any time. A typical system might have a set of three modes:
• Base • Alert • Storm
In base mode, where there are no significant events occurring, the system is typically scheduled to run once per day. After a run where a certain combination of interesting events has been triggered, the system can be scheduled to change mode into a higher state of alert, typically running more frequently and causing certain telemetered gauges to be polled more often. In the highest state of alert in this example, runs may be scheduled to occur very frequently, at say 15
FloodWorks Technical Review
© Innovyze 9 01/07/2012
minute intervals, to keep close scrutiny of a flood event as it occurs, typically causing polling to occur more frequently to ensure that the system has the latest observed data. Changes of mode can be set to trigger the sending of an SMS message, using an external mail sending protocol triggered by a post-run script, to alert key users to the new state of system alert.
Forecast
database
The time-series forecasts generated by the forecasting module, together with the summary tables produced by the analysis module, are stored in the forecast database located on the primary forecasting workstation. The results from each run of the forecasting system are held independently within the forecast database, and include a copy of all the input data used by the run. This copy serves two purposes. Firstly, a forecast can be re-run to investigate the effects of specific changes to the input data. Secondly, during any post-event analysis of system performance it is essential to be able to reproduce a run exactly in order to determine the cause of problems or deficiencies in the operation of the system.
FloodWorks
Web
Server
The thin client functionality is based around the existing reporting functionality together with an XML style sheet processor for generating HTML web pages. The process in summary is:
• In FWCM, the user sets up the graphs, maps and summaries that they wish to appear on the web pages by picking data streams from lists in a Report Specification object. • FWCM exports the Report Specifications in an XML format similar to the report
specification files that contain the style and format control desired for the web site (generally supplied by the Clients IT staff). The FloodWorks user need not see this XML.
• In FWEM, the user can pick from available Report Specifications for automatic production of web pages from a run or for immediate production from a completed run.
• Web output is produced in a combination of XML and PNG (both hidden from the user) and binary time series formats by a program running in a web queue on the server. This output is not available to the user other than through the FloodWorks Web Server application. The output appears as a file in the run’s output folder.
• The FloodWorks Web Publisher application copies the run’s web output file onto the web server PC.
• The FloodWorks Web Server application, running on the web server PC, extracts the XML, PNG and time series data and combines them with XSLT style sheets to generate web pages for streaming to clients (web browsers). Customers can provide their own style sheets or can use the default one provided by FloodWorks. Using their own style sheets will allow customers to change the layout, add logos, ignore parts of the output, add static text and pictures.
Licencing
There are three types of web licence: Web Publisher, Web Server and Web Client. The Web Server and Web Client licences would always be on the same dongle. This dongle would typically reside on a PC in the DMZ between the customer’s LAN and the web, although it could be on the LAN or even on the same dongle as the FloodWorks Server. The Web Publisher licence might be on the same PC as the FloodWorks Server licence, or it might be on a separate PC if the customer wished to separate the generation of web output from simulations for performance reasons. The new features in FWEM for generating web output are only be available when connected to a server on a PC that has a FloodWorks Web Publisher licence. The FloodWorks Server checks for a Web Publisher licence before generating web output. The FloodWorks Web Server application will check for a Web Server licence before producing web pages. The Web Server application will require clients (i.e. web browsers) to log in before streaming web pages to them. Client licenses will be based on the number of simultaneous logged-in clients. Clients will time out and lose their login after a certain period of inactivity. After timing out, clients will still be able to see the web page they were looking at as well as any others that are cached on their PC from previous viewings, but will have to log in again to see any new pages. Login will be based on a system of session cookies, so clients are be required to have cookies enabled on their machines. The customer will also have to accept that our dongle-checking process, which will be a multi-threaded application written in C++, runs on the web server, which is likely to be in the DMZ between their LAN and the web.
Configuration
There is a “Report specification” object in FWCM, which will essentially have the job of creating XML report specification files (currently called RPT files) on the server. Each report specification file can be used to create either a Word report or a web page. An exported Server can contain any number of Report Specifications. Each Report Spec will give rise to a single Word report or a single web page.
Documentation
Innovyze’s products include an on-line HELP system based on HTML pages, and include keyword searching and indexing to enable easy navigation between topics. All functionality, system installation and configuration topics are covered in the on-line help, and users have the ability to print pages from the help system on a required basis. The Help system is provided for both the FloodWorks Event Manager and the FloodWorks Configuration Manager. Innovyze does not provide printed manuals. FloodWorks is provided with an on-line Tutorial with data. The tutorial is designed to assist and guide a new user to go through the steps in configuring a FloodWorks system. The Tutorial has been designed to complement the 1-day “Introduction to FloodWorks” training course. All documentation, menus and dialogs are written in English.
Hardware
configurations
The minimum specification for FloodWorks is an Intel Pentium D, Pentium Extreme Edition or Dual Core Xeon processor with at least 1Gb of RAM. However, for better performance, an Intel Core2Duo or AMD X2 Athlon processor should be used and the RAM should be increased to a minimum of 2Gb. For the very best all round results use the latest Intel (Core-i5 or Core-i7 or multi-core Xeon) or AMD Opteron or Phenom II processor and install at least 4Gb of RAM. As a general rule, the more cores the PC has the better, although the gains do start to tail off once 8 cores is reached.
FloodWorks Technical Review
© Innovyze 11 01/07/2012
The ICA, along with simulation engines in InfoWorks CS and InfoWorks RS is a 32-bit executable, but will on a 64bit machine and operating system. Full support is provided for the 64-bit edition of Windows XP and Windows Vista (Service Pack 1) from v10.0 of InfoWorks. Support is also provided for Microsoft Windows Server 2003, 2003 R2 and Windows Server 2008. Under these Operating Systems the software can support more than 2GB of memory, which gives InfoWorks more address space (up to a limit of 4Gb), making it capable of creating much larger 2D meshes. Please note that FloodWorks is only supported on x64 versions of Microsoft 64-bit operating systems, not on Itanium versions.
FloodWorks is fully supported on the new Windows 7 platform (x86 and x64) now that Microsoft have formally released it to the manufacturing industry (Windows 7 RTM release or later). FloodWorks is not supported on Windows 95, Windows 98, Windows ME, Windows NT v3.51 or Windows NT4 operating systems. This is because Microsoft no longer provides any support for these legacy products. If using Windows 2000, Service Pack 3 (or later) must be applied to use FloodWorks. It is recommended to apply Service Pack 3 for Windows XP, although this is not a system requirement for FloodWorks to run. Those running Windows Vista should ensure they are at Service Pack 1 (SP1) and that the latest fixes and security patches have been applied. For large models (greater than 10,000 pipes/nodes), a significant amount of disk space will be required. This is both for simulation results and the numerous temporary files created during the model build / data transfer process. If data and results are to be held on the local machine, at least 200Gb of free disk space should be available after installation of the operating system, FloodWorks, and any other software tools (i.e. Microsoft Office or your preferred GIS application). For best performance, use a good quality hard drive and make sure it has fast data access speed.
Large networks, particularly those with ground models containing DTM, DEM or LIDAR data, require a lot more memory and a lot more disk space to manipulate than standard data.
If the database is to be held on a Network Server, make sure the network itself can handle the large amount of traffic that will be created. At a minimum, a Fast (100Mb) Ethernet is recommended, but a Gigabit network environment is preferable. If the system is based on a T1 connection (1.5Mb) or even 10Mb Ethernet, it is possible that the network is unable to cope with the added demands that FloodWorks could place on the system.
FloodWorks,
Windows
Terminal
Server
and
Citrix
FloodWorks works well on a Windows 2000 Terminal Server. Performing long simulation runs in this way is a good way of avoiding tying up an individual’s personal desktop machine. When more than one modeller will want to use each terminal server at the same time, more than one processor is highly recommended. Each modeller must log on using a different username and they must use separate InfoWorks local roots (which will be the case if they use the InfoWorks default location). InfoWorks can use lots of memory for large networks and simulations use lots of CPU. Therefore the size the server should be set appropriately for the number of concurrent users and type of use. For multiple users on a terminal server you must have a Network Dongle for InfoWorks. If more simulations are run simultaneously than there are available processors in the Server the total time taken to run them will be longer than if they were ran one after the other. If a fast LAN is available there should not be any network performance issues using InfoWorks remotely. If bandwidth is an issue note that GeoPlan results replay animations by sending a complete bitmap each frame. On Windows 2000 Terminal Server remote windows only have 256 colours available which limits the effectiveness of using thematics on a GeoPlan. Windows 2003 Terminal Server when used with the new client
software does not have this limitation supporting colour depths up to 24 bits (True Colour). If the Terminal Server is to be used for running long simulations and analyse results (do replays) using your normal desktop PC here a few of recommendations:
• Use a different username when you log into the terminal server (otherwise you won't be able to easily run simulations on the terminal server and your desktop machine at the same time)
• Log into the Terminal Server and schedule the runs using only checked in network and select the option to put results files on the server.
• Close the main InfoWorks program and leave the simulation controller running. This reduces resource usage on the Terminal Server and releases the UI licence.
Generally speaking, any software that works on Terminal Server will also work with the Citrix MetaFrame Presentation Server. Citrix MetaFrame Presentation Server and Client talk using the ICA protocol (not RDP that Microsoft use) and the server sits on top of Windows Server. They have more client options (including a browser one) and the protocol is suitable for low bandwidth connections - although we suspect that full screen bitmap animations won't be very fast on such a connection.
Software
Authentication
Licensing is on a per user basis, authentication is provided by electronic Dongles attached to either the local PC or a Network Server. We supply the Dongle in either USB or Parallel format. Given that most modern day computers, particularly laptops, no longer have a parallel port, we recommend opting for a USB style Dongle when opting for a Local Dongle solution.
The InfoWorks licence restricts the movement of licences controlled by a Local Dongle. The use of a Network Dongle gives much more flexibility in this respect and provides a much more secure way to authenticate the use of your Wallingford Software licences in a corporate environment. A Network Dongle remains resident on the corporate Network, and provides access to InfoWorks for individual users connected to the Network, without the need for a Dongle to be attached to a particular PC. Licences that are authenticated by a Local Dongle can be upgraded to 'seats' on either a LAN based or WAN based Network Dongle at any time. Our definition of LAN based authentication is considered to be within an office complex/building. In the situation where an organisation operates a number of offices on a Business Park, or where the main office is supplemented by staff in one or more nearby satellite offices, the people working in these offices are considered to be on the same LAN from an InfoWorks licensing point-of-view. Where network 'seats' are destined for staff in a variety of very disparate offices, then you will either need to deploy a specific LAN based Network Dongle for each those locations, or opt for WAN based configuration, where anyone in any of your regional offices can gain authentication to use InfoWorks from a WAN based Network Dongle in a remote location. WAN based authentication outside the original country of purchase is strictly prohibited. We have chosen to keep our Network Dongle implementation as simple and straightforward as possible. It will work over virtually any TCP/IP or UDP network configuration. The configuration is such that even a VPN (Virtual Private Network) connection is possible. Such VPN access is permitted for occasional use, such as when staff are required to work from Home for short periods of time.
FloodWorks Technical Review
© Innovyze 13 01/07/2012
Installation
FloodWorks installation can be either locally on independent PC’s (or a Laptop for mobile use) or installed on an intranet server for greater flexibility of use. Storage of data sets may be local or network server based depending on IT requirements.
Support
and
Training
Innovyze operates a support and maintenance licence agreement to ensure that our clients protect and maintain the investment they have already made in the product, and to ensure that they are able to take full advantage of all the latest features as they become available in the software. In addition, by ensuring that the product remains supported, our clients are able to protect its ‘trade-in’ value against any new software that may be purchased in the future. Innovyze has a particularly aggressive development programme for all of our products, with two full releases scheduled for each year. In each release, we endeavour to provide new features and functionalities that have been requested by our users to ensure that the investment that is made through a support and maintenance contract is well served. Support of the solution is primarily a local function with standard 5-day week support. Additionally, due to Innovyze’s global nature, support from Europe, North America, Asia or Australia can be resourced if required. User and Management training is offered on a number of levels to match client requirements. Standard and Advanced user courses are available.
