Short blog to highlight some long forgotten bit of functionality. Functionality that has been here in InfoNet for long while and sometimes it’s the simple stuff can be the most useful. So how about for a quick overview report of the network then try main menu Network > Network Summary, which can be run on the entire network a select or zone. The output to screen a simple breakdown of the network.
Network Summary Output.
Main menu Reports > Summary Report will output to either HTML or a WORD Report.
Surveys, repairs and incidents all contain date fields which include a time. In the CCTV Survey dialog box above, the ‘When Surveyed’ field is split in two. However this is actually just the one field.
Using the TIMEPART(date) function, described below, it should be possible to pull out the time part.
TIMEPART(date) – Given a date, returns the time part as a number in minutes e.g. if the date is 01/02/2008 12:34 this returns 754.0 – the number of minutes after midnight.
The following SQL code shows how to pull out the time and display it not as a numerical in the number of minutes after midnight but rather as an hh:mm value.
Occasionally, it may be desired to change the language in which InfoWorks ICM/Infonet (and other InfoWorks products such as IWCS/RS/WS) is displayed, for instance when visiting clients or colleagues in other countries. If your PC is set up in a particular language due to the system locale and that language is supported in InfoWorks then the software will appear in that language by default (otherwise it will appear in English).
If, however, you would like to see the software menus in English despite the PC system locale being in, say, France, it is possible to override the language by running a command line argument.
The command line argument mechanism works by adding the following:
to the command line when you run the software. You can, of course, do this by setting up a new short-cut and adding the following to the ‘Target’ field (for ICM and using the French language).
"C:\Program Files (x86)\Innovyze Workgroup Client 5.0\InnovyzeWC.exe" /LANG:F
The available languages and their key values are as below:-
Vlaams V (i.e. Flemish for Belgium)
Simplified Chinese SC
Belgian French FB
The strings (both LANG and the letter for the incarnation) are case insensitive.
Pump System Analyst (PSA)
With the PSA extension, users are now able to quickly determine whether a pump station meets pump capacity requirements and to design the pump station improvement plan that best satisfies system needs and maintains optimal pumping efficiency. Both series and parallel pumps are fully supported in determining the best options for pump station upgrade. Multiple pump curves and system head curves can be displayed simultaneously on a single graph.
Let’s assume you want to evaluate whether an existing fire pump can support a required fire demand of 1,000 gpm (Refer to Fig-1). First, open PSA, select Pump 200 into PSA, run the PSA analysis, and the dialog box showing the results will be displayed. Then, in the PSA Results dialog box, add Fire Pump 210 into the Combination Pumps section; make sure the Individual radio button is checked, and click the Update button to update the graph on the right. The pump curves for both Pump 200 and Pump 210 are shown individually in the graph. From the operating points where the system head curves intersect the pump curve of Pump 200, one can see the system demand is roughly 400 gpm. In order to accommodate additional 1,000 gpm fire demand, it is expected that the operating points shift to the right (roughly 1,400 gpm) by turning on Fire Pump 210 (Pump 200 and Pump 210 are in parallel mode).
Posted in InfoWater
On Tuesday 5th August Innovyze’s Water Network and Operational Systems Modelling User Group was held at SA Water’s offices in Adelaide.
Delegates from around Australia and New Zealand attended to see first hand to view the Operation Decision Support System that SA Water have successfully implemented. South East Water presented on how they have automated their External Fire Flow Requests, and MWH gave some examples of complex scripts they have developed for a couple of different clients.
Innovyze thanks all those who presented and attended. Special thanks to SA Water for providing the facilities for the day, and showing the control room and systems to the delegates.
For more information please click on the images below.
When you search and find or select to view a report on the map a default extent is used to show the reports location. It is possible to modify the extent at which the map is displayed when viewing a report. This option is a map specific setting so please consider this when setting up multiple applications or maps.
Below is an example of the where the setting can be useful and how it can be modified.
When you want to see a report on the map you can right click on the report from the list in your saved or completed view and select the option to view report on map.
Within InfoWorks CS there can be situations whereby a small cut out of an existing network run individually may produce difference results for that area as within a larger network.
Typically the things to check when looking into differences in results between two networks would include looking at the simulation parameters that have been set, the hydraulic run schedules as well as a comparison between two networks. Usually after these steps have been taken differences may be identified that answer questions with regard to differing simulation results.
There have been some cases however where a single model has included two or more discrete network areas and when one is run in isolation the results for this differ to the same area in the larger model. After investigation it may become apparent that the simulation parameters are the same, the network objects are the same and the run schedules are the same yet results vary by more than the tolerance for volume balance value being used.
The usual reason for this is particularly difficult to identify in versions prior to 12.5, as here the functionality causing the discrepancy is enabled by default. The areal reduction factor that is used in rainfall smoothing is usually the cause and would indeed differ between the two networks in question. This is dependent on the total runoff area within the network, this means the sum of all the areas for the subcatchments. As a consequence, when using the larger network, albeit the one with two discrete networks incorporated then the total area will be greater than that for the network with only the single area.
The areal reduction factor used for rainfall smoothing will cause a different inflow profile for the subcatchments, the routing will be affected and hence different results produced (even though the volume will remain the same).
It is worth noting that the impact of this will be particularly apparent when only a small section of the total network is looked at in isolation as this is when the difference in areal reduction factor will be the greatest.
For quite some time now users have had the option of using a couple of alternative means of viewing the properties of objects within InfoNet. These are the property dialog box, which has been in the software since time immemorial…
Property Dialog Box
… and the more recently added property editor.
Water main breaks are prevalent in all cities. As engineers and planners, we do everything we can to avoid them and mitigate damages when they occur. Communicating those plans and educating the general public is another story. Having a clearly defined and defensible rehabilitation plan is the foundation for better education of stakeholders. They want to know:
Why did this water main fail? What was the likelihood of this water main to fail? Was there an assessment (financial, environment, and social) on this pipe failing? Was this pipeline planned to be repaired/upgraded in the near future?
Take a look at a sampling of news stories in the last few weeks regarding main breaks in the United State. Is your utility prepared?
Join Innovyze for a free webinar on Wednesday, September 17th, 2014 at 12:00pm US eastern time for a technology update for risk-driven asset planning solutions, and will discuss how utilities are utilizing these toolsets to better manage risk of failure and maximize the value of aging assets.
People who attend this webinar will be able to understand the following items regarding proactive asset planning practices (featuring InfoMaster*):
1. More accurately estimate lifetimes (remaining useful life) of pipes and failure potential
2. Systematically assess consequences of pipeline failures
3. Methods for proper budgeting including targeted approach to rehabilitation, repair and renewal planning.
Click here to reserve your spot. Spaces are limited.
It is possible to override the default table by explicitly naming the table or tables in the clause. This is done by using the ‘SELECT FROM’ keyword e.g. if the default table is Pump Station and you want to select all pipes with width greater than 100 mm you should say SELECT FROM Pipe WHERE width > 100.
Overriding the Default Table
In the unlikely event that you wish to select all pipes you can omit the keyword WHERE and the expression after it and simply say SELECT FROM Pipe. If the table name you wish to use contains spaces in it, it is necessary to put square brackets before and after the name e.g. SELECT FROM [All Links] WHERE width > 100. It is in fact possible to enclose any table name within square brackets so you can in fact say SELECT FROM [Pipe] WHERE width > 100.
A Worked Example