ICM RiskMaster allows 2D hydraulic results from InfoWorks ICM to be combined with economic data to allow damages to be quantified.
Traditionally flood management policies have been based upon the design standard philosophy, where policy makers decide on an appropriate protection level to be achieved within the flood system which is used to design and manage hydraulic infrastructure. In contrast with this approach and following the guidelines specified in the EU Floods Directive 2007/60/EC on the assessment and management of flood risks, flood management policies based on risk rather than system performance have been developed in recent years. Flood risk management policies are based on the evaluation of the consequences generated by flooding events and the alleviation measures on the expected flood impacts over a given time period.
Risk-based analysis methods can be used in order to assess and manage hydraulic infrastructure which protects assets from flood events. A flood-risk methodology analyses a hydraulic system based on the evaluation of the consequences derived from the service of the hydraulic infrastructure rather than system performance. Thus, in contrast with traditional performance methods, in which the hydraulic system is expected to service a specific loading level, a flood risk approach should take into account all type of events based on their probability of occurrence. The results of the analysis provide a comprehensive view of the performance of the hydraulic system and the consequences derived from flood events.
The calculation of risk involves multiplying the damage result for each receptor in a simulation with the probability of occurrence of the event simulated. The total damages are calculated at each damage receptor by taking the 2D flow depth and using the depth-damage curve to associate this with a damage value. This is then summed for all damage receptors to provide a total damage value for each return period. This in turn is multiplied by the event probability, to provide the annual damage. Continue reading
Want to make your code understood to colleagues?
Want to ignore certain lines whilst developing an InfoNet SQL?
A double Backslash ‘\\’ acts as a comment in InfoNet SQL Comments. In computer programming, a comment is a programmer-readable explanation or annotation in the source code of a computer program. They are added with the purpose of making the source code easier for humans to understand, and are generally ignored by compilers and interpreters. Continue reading
With the release of IWLive Pro in 2016, Innovyze delivered the next generation of IWLive Pro, a significantly refined product using the latest technology and specifically designed to provide all existing IWLive Pro users with a simple upgrade path from IWLive to the newer, more powerful, IWLive Pro platform.
The first version of IWLive was commercially released in 2010. IWLive has served the industry well, providing a live operational decision support tool however many of the underlying technology components are reaching the end of their useful life and limiting the functionality in IWLive. Continue reading
Not exactly an InfoNet specific post but for those users working with the UK’s WRc’s MSCC Sewer CCTV Survey Standard this blog may be of use, it explains how to better visualise the data exchange XML file. A typical File looks as follows and is made up of an initial standard XML Header followed by the Survey Header and then the observations. The Survey Header and Observations are then repeated for each survey.
The following link will take you to the XML Specification For MSCC4 Sewer Inspection Data on the WRc’s website and explains the above format exactly. Continue reading
We have extended our special upgrade prices for InfoWorks WS Pro to all existing InfoWorks WS users until December 15, 2017. Contact your local Innovyze representative for full upgrade information.
Current InfoWorks WS users may continue to receive support for InfoWorks WS until December 31, 2017.
When it comes to version numbers, there are different rules for the various components of InfoWorks ICM and its associated Services.
Local and Remote Simulations
When creating and scheduling a simulation from your local machine and running it on a remote machine, there must be an exact match between the version of ICM on the local machine and the version of ICM on the remote machine. The remote machine can have either a full installation of ICM, or just the Remote Agent, but either way, the version number must match, right down to the build number (i.e. v7.0.4, build 14015). This rule ensures that regardless of whether you run your simulation locally on your machine or remotely on another machine, you are guaranteed to get the same answers each time (because you’re using the exact same software version each time). The Agents and Coordinator will only allow a remote simulation when there is an exact match between Local and Remote machine, so the end-user doesn’t need to check anything at run-time. Continue reading
With the release of InfoWorks WS Pro in 2016, Innovyze delivered the next generation of InfoWorks WS, a significantly refined product using the latest technology and specifically designed to provide all existing InfoWorks WS users with a simple upgrade path from InfoWorks WS to the newer, more powerful, InfoWorks WS Pro platform.
Development of InfoWorks WS started in mid 1990’s with the first version commercially released in October 1998. InfoWorks WS has served the industry very well for many years now, however, many of the underlying technology components are reaching the end of their useful life.
A decision has been made to cease development of InfoWorks WS and retire the product from our portfolio of active products. Its retirement date was 17 January, 2017, and we are no longer selling new licenses of InfoWorks WS. Innovyze will continue to provide support for existing InfoWorks WS users with valid annual maintenance contracts until 31st December 2017. After that date we will not be providing support for InfoWorks WS.
This document aims to provide answers to the questions that you may have regarding the sunset of InfoWorks WS.
A long time ago now, version 10.5 or earlier, objects in InfoNet had the ability to only store a fixed number of images or attachments. As an example the Manhole Surveys object could only store four images and attachments in all.
Old Dialog Box
Old Dialog Box with Attachments
InfoNet now has the ability to store an unlimited number of images and attachments per object. However the old fixed number are the default set. Continue reading
System curves can be a very powerful tool for an engineer to use when designing a new pump station or evaluating an existing pump station as they allow the engineer to see where the pump will operate along it’s pump curve. However, many engineers find it is difficult to find guidance material available on how to create system curves or in identifying key factors that should be considered when creating system curves. To assist the engineer our Innovyze team has created a presentation that includes a basic introduction to system curve concepts, details on the key factors to consider when creating system curves, and how the model software can be used to develop system curves.
The system curve presentation can be downloaded in PDF format using this link: