Product(s):	WaterGEMS, WaterCAD, OpenRoads Designer, OpenSite Designer, OpenRail Designer
Version(s):	CONNECT Edition
Area:	BIM

Problem:

Is it possible to export a water network modeled in WaterCAD/GEMS to OpenRoads Designer in order to build a 3D/BIM model?

Solution:

There is no direct way to import a WaterCAD/GEMS model file into OpenRoads Designer, but there is a workaround to do this by exporting the data from WaterCAD/GEMS thru an intermediate database like Shapefiles, Excel/Access files, and then importing it in OpenRoads Designer using the ModelBuilder tool.

In this article we have explained the workflow by two situations:

• having an existing WaterCAD/GEMS model and doing an import to OpenRoads Designer from scratch.
• building a standardized workflow to apply in multiple future projects (to make process repetition quick).

Important Aspects to be considered prior starting.

• Are you new to OpenRoads Designer’s Utility Modeling? If you are starting with OpenRoads’s Utility modeling, it’s highly recommended to run some Introduction workshops in order to learn the basics functions of modeling tools including its Workspace. Access the existing learning materials on LEARNServer. For the BIM administration perspective to cover tasks like Customization of Fitting libraries and drawing production, access this page for information on Workspace Management.
• Previous knowledge on ModelBuilder is required: The ModelBuilder tool available in OpenRoads Designer is the same one also available in WaterCAD and WaterGEMS. If you are not familiar with this tool you can learn more about it thru the WaterCAD/GEMS Fundamentals Learning Course (workshop 9) or a dedicated Workshop named “Importing Network from Excel Data” under OpenRoads Designer training course.
• Ground and Network Elevations: For the 3D network construction, it’s necessary to have both ground/top elevation data at the nodes. WaterCAD/GEMS’s model natively holds only the network’s elevation data at nodes. It’s possible to add Custom Fields in WaterCAD/GEMS through the User Data Extensions tool. To learn more about this tool access this article.
• Water Networks in OpenRoads Designer: OpenRoads organizes non-drainage/sewer network data (Water, Gas, Communication, etc.) in a similar way how it’s seen in WaterCAD/GEMS, where the data can be edited and read through FlexTables and Properties grid window. There are other WaterCAD/GEMS familiar tools in OpenRoads such as “Selection Sets”, “Queries”, “ModelBuilder”, “User Data Extensions”, etc. It helps a lot the learning curve on OpenRoads for existing WaterCAD/GEMS users.
• WaterCAD/GEMS nodal elements versus OpenRoads Designer’s Utilities nodal elements: while the hydraulic models have different types of nodal elements like Junctions, Pumps, Pressure Reduction Valves and etc, in OpenRoads all nodes are stores together into one class called “Water Nodes”, and the type of the node will be differentiated by the Feature Definition.

• Avoid Duplicated Labels: as a good practice for 3D model updates/synchronization, keep network elements with unique Labels (globally).

Importing data from WaterCAD/GEMS into OpenRoads (steps from scratch)

• Open the WaterGEMS model.
• If not already, add a Custom Field named “Elev Top” for all node layers in the model using the “User Data Extension” tool.

• Fill in the “Elev Top” field.
• Preparing the model to export data:
  • Create or edit a FlexTable (for each model element type) selecting the appropriate fields (see suggestion below) that will be imported later by OpenRoads Designer:
    1. Pipes:
       1. Label, Start Node, End Node, Diameter, Material
    2. Nodes (Junctions, PRV, FCV, etc):
       1. Label, X Coordinate, Y Coordinate, Elevation, Top Elevation

Consider adjustments to be made in the 3D model for some elements such as Reservoir and Tanks.

You can choose to export the model data to an Excel spreadsheet or to shapefiles. Choose the Excel only if your pipes don’t have bends, otherwise export to Shapefiles instead.

• Excel option: Export network data to Excel following the steps explained in this wiki. Use the FlexTables created above as base. Remember to export all element type used in the model.
  • Keep a Steady State scenario active while exporting.
• Shapefiles option: For each FlexTable, open it and click in the Export button (Very first button in the FlexTable’ s menu bar. Export steps are detailed in this wiki.
• Load OpenRoads Designer application and create a new 2D DGN file using the Workspace and Seed file of your preference.
• Open ModelBuilder (select the “Utility” option)

• Start a new Import.
• Select the Data source type according to the Option you choose.
• Select the File (or Files in case of having Shapefiles). In both ways will take you to view the WaterCAD/GEMS layers to be imported, like illustration below:

• Advancing the steps by clicking “Next”, the following 3 dialog box will help you to pick the Coordinates Units and define other settings of ModelBuilder.
• Advance to the “Specify Field Mappings for each table” step.

The most important part of the process is the datasource field mapping for each water model layers to the destination in the 3D model. As explained in the “Important Aspects” section, OpenRoads stores all nodal elements into a single category, the “Water Node” in our case. So for all nodal layers, you must select the Table Type “Water Node” for the Field Mapping. And pich the “Water Segment” table type for Pipes.

• Map the most appropriate fields for all Nodal Layers as shown below:
  • Table Type: Water Node
  • Key Field: Label
  • X Field: X
  • Y Field: Y
  • Elevation: Elevation (invert)
  • Elev Top: Elevation (Top) – this is the Custom Field created in the beginning of the process.

• Repeat the process for the Pipe layer:
  • Table Type: Water Segment
  • Key Field: Label
  • Start: Start Node
  • Stop: Stop Node
  • Diameter: Diameter (pick the correct unit)
• In the Next step you will pick the Feature Definition to be used for each model layer. The list of Feature Definitions will follow the library used by the Workspace currently used:

• You can advance until the last step to build the model.
• Do minor adjustments in the 3D model if necessary. Use FlexTable and the Layout commands for it. It’s recommended to check if the Pipes have the Fields “Set Invert to Start?” and “Set Invert to Stop?” field enabled (checked), then they can get node’s invert elevation.

Standardized Workflow for Multiple Projects

The process described in the previous section consumes time for its preparation. To optimize the time spent on 3D model construction, the suggested workflow described in this section can help by implementing a “template” that controls the Water network model information.

The workflow consists in set an architecture for the data integration between WaterCAD/GEMS and OpenRoads, using a predefined Intermediate database (to be used as a Data Repository) as illustrated below:

Here are some key characteristics of this process that contribute to leverage the data integration between WaterCAD/GEMS and OpenRoads:

• Seed File for WaterCAD/GEMS: Define a Seed File for WaterCAD/GEMS that stores the Custom Field (Top Elev) and a Custom Element Labeling - Prefix (set under Tools > Options).

• BIM Workspace: Define an OpenRoads Designer Workspace with the Appropriate element libraries (Fittings, Valves, Materials, etc) following your Company Standards, including a Element Labeling standard, equal to the one used in WaterCAD/GEMS.

• Template for the Intermediate Database: have an Empty Access file (.accdb) OR a Package of Empty Shapefiles (one per Water model layer). The Access database would have a Table for Each Water Model layer with the most appropriate fields. Similar could be done with Shapefiles. The Access approach is good because it involves a single file. When choosing this way, modelers should be aware to avoid drawing pipes with bends (use Junctions) when changing piping’s direction instead.

• Living Bridge Data Connections (powered by ModelBuilder): Create a ModelBuilder connection between WaterGEMS and the Intermediate Database and save the connection to an MBC file. Create a second ModelBuilder connection in OpenRoads, to connect the 3D model to the Intermediate database. Save the second connection to another MBC file.

ModelBuilder has an import role in the process, since it’s used at both ends (WaterCAD/GEMS and OpenRoads). As seen in the Illustration above, the connections to the Data Repository have two-ways, since ModelBuilder has functions to Synchronize data from the model out to the Data Repository.

In order to help with the possibility of having data traveling To/From OpenRoads, it’s important to use a Standard for Element Labeling in both WaterCAD/GEMS and OpenRoads. This standard can be a simple predefined Prefix for each type of model element like:

• “WL“ for Pipes,
• “WVLV_FCV“ for FCV,
• “WJ“ for Junctions, and so on…

Then it can be used in the ModelBuilder connections (in both) using the “WHERE” statement:

The WHERE statement will act as a filter to orient the Data Repository while updating the different types of nodes, considering that OpenRoads stores all nodes under the “Water Node” category. In a situation of Synchronizing an information changed in OpenRoads back to WaterGEMS, the information of a Pump, for instance, will arrive in the correct table (or shapefile) of the data repository because it uses a WHERE Statement that filter the OpenRoads nodes that uses the Pump’s prefix.

So, the suggested workflow involves some exclusive template files that users should consume while modeling in WaterCAD/GEMS and during the 3D model construction. Here is the list of the template files involved:

• WaterCAD/GEMS Seed File
• Empty Data Repository File (Access or Package of Shapefiles)
• ModelBuilder Connection WaterGEMS & Repository (MBC)
• ModelBuilder Connection OpenRoads & Repository (MBC)

The typical workflow taken by the user is:

• Use the Seed file when modeling in WaterCAD/GEMS and follow the rules for Element Labeling, Top Elevation data filling and pipe bend usage.
• Make a copy of the Empty Data Repository
• Load the ModelBuilder MBC file into WaterGEMS and integrate it to the Copied Repository file and click on “Sync-Out” (it pushes the data from WaterCAD/GEMS to the Repository)

• Load the ModelBuilder MBC file into OpenRoads and integrate it to the Copied Repository and click on “Sync-In to Model” (it pushes the data from the Repository to OpenRoads).

In both videos you can see that ModelBuilder asks for the repository File’s folder path, and it was made by manipulating both MBC files in a text editor. The row number 7 contains the keys to predefine the folder path to find the data source file, and by keeping then with a inexistent path (as shown in the example below), it forces a prompt to let user to pick the folder:

As seen in the videos above, the data integration steps consume just a couple of clicks and go very quickly when using this standardized workflow.

It’s important to understand that to get an optimal workflow, each company should first set their own template files (Repository, Seed, MBCs) and the Workspace for the BIM modeling. Minor adjustments in the 3D model will normally be needed.

In order to support a deeper understanding of the process, you can find below an example of a Seed File for WaterCAD/GEMS and the Access Repository template and the MBC files used in the videos. The MBC file used in OpenRoads should be used in model created with the built-in Training-Metric Workspace.

Template used in the Videos Above