InfoWorks ICM has the ability to model both urban drainage systems and fluvial systems in an integrated manner. In the past, urban drainage systems would have been modelled in InfoWorks CS and the migration of data from InfoWorks CS to ICM is well documented with virtually all data migrated between the 2 softwares. This is because InfoWorks ICM has its roots in InfoWorks CS.
This is not the case on the fluvial side, where models exist in our river modelling software, InfoWorks RS. The setup of InfoWorks ICM and InfoWorks RS are a little more distinctive. Most fluvial modelling software use cross-sections and links but they differ in the ways they represent structures and junctions, InfoWorks RS and ICM are no exception to this. Nonetheless it is still possible to migrate network data between InfoWorks RS and ICM with some ease, avoiding the time-consuming re-creation of the entire fluvial model network. Although it should be noted there are some incompatible network objects that exists in InfoWorks RS, these are primarily Routing reaches, Bernoulli Loss Units, Flapped Orifices, Blockage Units and Symmetrical conduits. There are also no junction nodes (although these can be represented in InfoWorks ICM as break nodes) or connectivity links. This means that some of the connectivity requires fixing within InfoWorks ICM. There are also differences in the approach to modelling bridges which is identified later in this article.
The first thing to note, is that with an InfoWorks ICM license, it is possible to open the InfoWorks RS viewer software which allows the user to open, view and export InfoWorks RS model networks. With the InfoWorks RS network open, Right click on the Network with IWRS and click on Export->to CSV… Export the RS Network to CSV with the following options checked:
Within ICM, create a new network and set the appropriate Co-ordinate system using Geoplan->Select Coordinate System. You can then Import the IWRS network to ICM from CSV using Network->Import->Model->from RS csv network data. This will bring across the network data including compatible objects such as subcatchments (with PDM/SRM boundaries where appropriate), river reaches, banklines, storage areas, 2D objects (excluding mesh) and compatible structures. The next step in the process would be to change the downstream node to an outfall node, where appropriate, and then review the connectivity where there were connectivity links in InfoWorks RS.
The approach to bridges in InfoWorks RS and InfoWorks ICM is also different, with InfoWorks RS limited to empirical approaches. There are different data requirements between the 2 softwares, with InfoWorks ICM requiring 5 cross-sections representing the upstream bridge section, upstream bridge face, downstream bridge face, downstream bridge section and a deck level. Not all of these sections were compulsory in InfoWorks RS, the data was not necessarily geo-referenced and the bridge openings had no lengths. However, the migration from InfoWorks RS to InfoWorks ICM will migrate the bridges across and recreate them based on a number of assumptions. These assumptions and other important conversion notes are explained in the InfoWorks ICM help topic ‘Importing InfoWorks RS Network Data’ which it is recommended is reviewed prior to migration of data between the 2 softwares.
Whilst it is not possible to directly migrate boundary data between InfoWorks RS and InfoWorks ICM, it is possible to recreate the boundary in InfoWorks ICM, or create a run in InfoWorks RS, export the results to csv files, change the header and import these into InfoWorks ICM.
Operational regimes for structures and pumps in InfoWorks RS were represented as logical control rules, these would need to be manually re-written in the InfoWorks ICM RTC format.
Other importers exist in InfoWorks ICM to import ISIS (Flood Modeller Pro) networks and HECRAS geometry. These will allow you to bring in existing fluvial model data in InfoWorks ICM, for use independently, or with the 2D or pipe network functionality for an integrated model.