Ideas

Showing 10 of 1370

Costs that vary based on different parameters (Material, size, buried depth, etc)

Costs vary based on different parameters as it is not the same to replace a 6in pipe vs a 12 in pipe. Pipes that are buried deeper are also more expensive.

Martha Nunez about 2 years ago in Info360 Asset / Rehab actions & cost 0 In progress

19 VOTE

Model results as TVD connectors

We'd like to have model results as an input in the TVD connectors. An example is where we have observed flows that we would like to use at a tributary and then switch to catchment flows when the observations run out. We know this can be done using...

Richard Body about 5 years ago in InfoWorks ICM / Calibration / Results / Sharing / Time Series DB 0 Gathering support

3 VOTE

Have a costs library available under the rehab actions page

With this functionality, users could have an estimated cost for all assets in their system as soon as they run the rehab tree. This eliminates additional data input and management making the cost reporting much more efficient specially for those u...

Martha Nunez about 2 years ago in Info360 Asset / Rehab actions & cost 0 Gathering support

3 VOTE

Support for LACP v7 and v8

This is a request for support for LACP CCTV Management in Info360 Asset.

Martha Nunez almost 3 years ago in Info360 Asset / CCTV Standards (e.g. PACP) / Rehab actions & cost 1 On roadmap

2 VOTE

TSDBs to produce logs of SQL queries

This is important to assist troubleshooting issues related with TSDB performance during implementation and maintenance of TSDBs. The log should include the exact queries produced by their streams when data is updated.

Guest over 4 years ago in InfoWorks ICM / SQL / Time Series DB 0 Gathering support

2 VOTE

Use Machine Learning to estimate subcatchment inflows to network

Allow users to skip parameterized subcatchment hydrology estimates which may become outdated over time and replace it with machine learning on measured data from TSDB. Flow meter could train algorithm which learns to predict flows based on rainfa...

Guest about 5 years ago in InfoWorks ICM / Calibration / Time Series DB 1 Gathering support

2 VOTE

Export of simulation log files from ICMLive

We'd like the log file to be automatically exported as part of the live modelling workflows. This log file contains important information pertaining to the TSDBs that we would like to use in some additional post-processing. Could this be part of t...

Richard Body over 5 years ago in InfoWorks ICM / Live Modeling / Time Series DB 0 Gathering support

2 VOTE

One more File name format for ASCII Grid (forecast) in Spatial TSDB

Now the file name format like *YYYYMMDDHH_hhhmm of ASCII grid (forecast) can be supported in Spatial TSDB. However, if the user has a forecast origin accurate to minute, it cannot be used. A new file name format of *YYYYMMDDHHMM_hhhmm should be in...

Guest over 5 years ago in InfoWorks ICM / Time Series DB 0 Gathering support

1 VOTE

TVD connector input fields longer than 64 characters

The "input" fields for TVD connectors are currently limited to 64 characters. I have TSDB streams with names longer than 64 characters, and I would like to be able to use those streams as inputs to the TVD connectors.

Iain Scott over 5 years ago in InfoWorks ICM / Time Series DB 0 Gathering support

1 VOTE

Support for different table schemas from SQL Server in the TSDB

We have a SQL Server database containing flow survey and rainfall data. All of the raw data is saved in one table and views are created for each monitor via a stored procedure, We use schemas to control permissions on the database tables. Only t...

Guest over 5 years ago in InfoWorks ICM / API / Exchange / Time Series DB 0 Gathering support

Please enter your email address

FILTER BY CATEGORY