All ideas

Showing 117

upgrade the embedded Ruby interpreter

It is a pity that there is no way to upgrade the embedded Ruby interpreter. Unfortunately, that old version is not compatible with many of the useful Ruby Gems – severely limiting its usefulness. Do you have plans to include a more recent version ...

Guest about 1 month ago in InfoWorks ICM / API / Exchange 2 Under consideration

5 VOTE

Increase RTC Comment Length and Configuration

Currently RTC Comments are limited to 69 characters and only appear within a single box that you need to scroll horizontally to read. Please allow comments to be much larger and have multi-line format so we can add useful comments and explanations...

Dave White 3 months ago in InfoWorks ICM / RTC 1 Under consideration

10 VOTE

Additional Custom Fields available when needed

Our company uses all available user fields and needs additional room for sharing important metrics derived from hydraulic analyses. We want an option to toggle on additional fields to store this information alongside pipes for Themes and references.

Nathan Gerdts 7 months ago in InfoWorks WS Pro / Other 0 Under consideration

21 VOTE

Improved scenario organization

Can we have the scenarios functionality improved to allow for scenarios to be organized into folders, ordered by various attributes (other than time of creation) and a search function within the scenario window. It would be useful to have the fold...

Guest over 1 year ago in InfoWorks WS Pro / Engine 3 Under consideration

15 VOTE

Improved Scenario Manager

Improved options around the parent child options. basically setting up a more structured option so that if you update a parent scenario (not just the base) then all child scenarios (ideally copied from during creation) would get the updates. i.e. ...

Duncan Allen about 1 year ago in InfoWorks WS Pro / Productivity 2 Under consideration

6 VOTE

Change default field name behaviour when exporting to shape file

When exporting model network data to shapefile format, the default export field names generated in the “open data export centre” are currently very awkward. The issue arises because many field names in ICM are longer than ten characters, but shape...

Jason Kulsdom 6 months ago in InfoWorks ICM / Export Data 2 Under consideration

14 VOTE

Automated Data Exchange with InfoAsset Manager

If we think of asset management as divided into day-to-day work and organization (InfoAsset Manager) and long term, CIP planning work (Info360 Asset), this idea would bring asset management full circle. It'd also provide a huge workflow benefit fo...

Tim Medearis over 1 year ago in Info360 Asset / Integrations 3 Under consideration

18 VOTE

Variable depth for open channels and swales

One limitation we are running into is the inability to model varying depths within swales in InfoDrainage. Often open channels will run along road corridors for example where the crest either remains at a similar elevation while the depth changes....

Guest over 1 year ago in InfoDrainage / Visualization 1 Under consideration

7 VOTE

Time series results for thematic maps

In the current state you need to add simulation results to a model and then preform a SQL to add a TSR result to a userfield. It would be easier to just add TSR results to the thematic SQL options.

Farhan Meke 8 months ago in InfoWorks ICM / Theme 3 Under consideration

12 VOTE

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 over 1 year ago in Info360 Asset / Rehab actions & cost 0 Under consideration

Please enter your email address

FILTER BY CATEGORY