<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: facing an issue with creating Multiple subnetwork controllers. in ArcGIS Utility Network Questions</title>
    <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401434#M3622</link>
    <description>&lt;P&gt;Hierarchical networks only allow features to belong to more than one subnetwork as long as those networks belong to different tiers. You can belong to a pressure zone and a system, but not to two different pressure zones. If 5000 were a pressure zone and DGS was a pressure system, you wouldn't receive an error. Because both of these subnetworks are the same tier they are not allowed to be interconnected like this.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Mar 2024 14:12:05 GMT</pubDate>
    <dc:creator>RobertKrisher</dc:creator>
    <dc:date>2024-03-27T14:12:05Z</dc:date>
    <item>
      <title>facing an issue with creating Multiple subnetwork controllers.</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401291#M3615</link>
      <description>&lt;P&gt;I am trying to create a new subnetwork controller and I have come across this error and how to solve this.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Angiex__1_0-1711519181031.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/99190iCDFBC72918F9316A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Angiex__1_0-1711519181031.png" alt="Angiex__1_0-1711519181031.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 06:00:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401291#M3615</guid>
      <dc:creator>Angiex__1</dc:creator>
      <dc:date>2024-03-27T06:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: facing an issue with creating Multiple subnetwork controllers.</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401292#M3616</link>
      <description>&lt;P&gt;Hello, I think the error is explicit : you have two controllers with different subnetwork name that are connected.&lt;/P&gt;&lt;P&gt;Here you can find how to solve this error : &lt;A href="https://www.esri.com/arcgis-blog/products/utility-network/water/water-subnetwork-errors/" target="_blank"&gt;https://www.esri.com/arcgis-blog/products/utility-network/water/water-subnetwork-errors/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 06:08:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401292#M3616</guid>
      <dc:creator>PierreloupDucroix</dc:creator>
      <dc:date>2024-03-27T06:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: facing an issue with creating Multiple subnetwork controllers.</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401293#M3617</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/208186"&gt;@PierreloupDucroix&lt;/a&gt;&amp;nbsp;Since its a hierarchical type of network , why cant i be able to have two subnetworks in them? or i dont know where i am explicitly going wrong.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 06:34:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401293#M3617</guid>
      <dc:creator>Angiex__1</dc:creator>
      <dc:date>2024-03-27T06:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: facing an issue with creating Multiple subnetwork controllers.</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401434#M3622</link>
      <description>&lt;P&gt;Hierarchical networks only allow features to belong to more than one subnetwork as long as those networks belong to different tiers. You can belong to a pressure zone and a system, but not to two different pressure zones. If 5000 were a pressure zone and DGS was a pressure system, you wouldn't receive an error. Because both of these subnetworks are the same tier they are not allowed to be interconnected like this.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 14:12:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401434#M3622</guid>
      <dc:creator>RobertKrisher</dc:creator>
      <dc:date>2024-03-27T14:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: facing an issue with creating Multiple subnetwork controllers.</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401582#M3623</link>
      <description>&lt;P&gt;Another thing I like to do is go back and check my subnetwork controllers were set on the correct port. It's rather easy to accidentally set a controller on Port 1 when you meant to set it on Port 2. I've inadvertently created multiple controller conflicts several times this way.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 17:29:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-questions/facing-an-issue-with-creating-multiple-subnetwork/m-p/1401582#M3623</guid>
      <dc:creator>MichaelParma</dc:creator>
      <dc:date>2024-03-27T17:29:13Z</dc:date>
    </item>
  </channel>
</rss>

