WaterGEMs export to EPANET

Hi Joaquin,

A few questions to start troubleshooting this:

1. What version of WaterGEMS are you using? You can check under File > Help > About. If you are not using the latest version (10.03.05.05), you may want to upgrade in case there is a fix related to the issue in question. See: Downloading OpenFlows Software
2. When you say that the nodes and pipes will not "Transfer" to EPANET, do you mean that when you open the .INP file in EPANET itself (what version?), you only see the nodes and tanks? What if you go to Report > Table > Network Links?
3. When you export to INP, are you choosing to use element labels or element IDs for the EPANET labels? Note that EPANET itself does not support duplicate labels, hence the option to export IDs which are unique.
4. Are you seeing any user notifications after exporting to the INP file? If the export process is failing before the pipe/pump/valve export step, that could explain the missing elements. Review the messages and correct any issues, then try exporting again.
5. Is the issue happening with all pipes, valves and pumps, or just some? Note that pumps and valves are node elements in WaterGEMS but link elements in EPANET, so extra link elements should be created upon export. See also:
   1. Missing pipes when exporting to EPANET
   2. What are the limitations of importing/exporting EPANET files?
   3. Troubleshooting problems with importing EPANET or EPASWMM files

If this does not help, please provide a copy of the model for review, plus any special steps needed to reproduce. If using a recent version, you can go to File > Save to Package, then send or upload the resulting ZIP file, then reply back to let us know: Sharing Hydraulic Model Files on the OpenFlows Forum

Hello Jesse,

I do get a user notification message stating "object reference not set to an instance of an object".  

Hi Joaquin, that message indicates a failure occurring during the export process. I would suggest using the Validate tool to check for any problems with the model that the EPANET export is getting stuck on, and make sure you're using the latest version (10.03.05.05): Downloading OpenFlows Software 

You will see a note in this article about a specific known issue in version 10.03.02.75 causing that exact error on export, if a hydropneumatic tank is included in the model. If that is the situation, you can remove the hydropneumatic tank or convert into an equivalent regular tank element in order to export.

If you need further help, please provide a copy of the model for review: Sharing Hydraulic Model Files on the OpenFlows Forum