Latest Contributions by JohnAlsup

‎11-06-2023

There is no way to stop at a vertex count or similar. What is at the X? Is this just where two lines of the same asset group and asset type intersect or is there some junction or device there?

‎11-06-2023

If you are trying to actually trace the structure network, not a domain network, you can use a Connected Trace or Shortest Path Trace.

‎11-06-2023

it would only work for tracing the structure network, not a subnetwork.

‎11-06-2023

It sounds like this is a case where you have multiple wires you want to represent as a single line, which is going to be an issue in the Utility Network, as the UN is designed to model physical assets. So, to accomplish this you could create a container feature, like an aerial span, where it contains the two lines from the two different circuits. The other option is to make all your lines containers and make all wires non-spatial content, but I would not suggest that, as it would be a bit more complex to edit.

‎11-05-2023

Does the downward leg to the service actually (electrically) belong to both circuits? The only way I could think of that being the case is it were getting one phase from CB 1 and another from CB 2, which is probably not what is occurring. Is it actually the case where you have two physical lines running down to the service, each a separate line?

‎11-03-2023

Hi Richard Responses #1) We do not have an example of this in the sample data, but I will make sure to add this. #2) The subnetwork name of the service would only get one subnetwork name. The subnetwork name of the switch would get both. What you could do is add a new asset type to one of the Service Asset Groups and assign it a terminal configuration with three terminals (two upstream terminals) and define the path like what is shown in this diagram and then assign this terminal config. Then connect the each of the incoming circuit lines to each of the upstream terminals such that each terminal is connected to only one line.

‎11-03-2023

Assuming this is not a mesh network, but two separate circuits, then normally you would have an switch that connects to both circuits just before the service. It is typically called a Source Selectable Switch or Automatic Throw Over Switch. This switch would have three terminals (two upstream). Then the terminal path on the switch would set to only provide a path to one source or circuit at a time. Then the service is only part of one subnetwork at any time.

‎10-25-2023

What Foundation release is this from and what versions of Pro and Enterprise are you using?

‎09-08-2023

Yes, that should be fine, as this domain is not used in a network attribute.

‎09-08-2023

As Robert states, adding asset types or domain codes and descriptions is easy. Changing an Asset Type name or code is very risky and will probably fail on apply. Changing domain names can be risky if the domain is assigned to a network attribute, so for changing names, I would use the D_Rename option.

‎08-31-2023

We designed the lifecycle status to only have values that impact tracing. Each of the status we have use a bit in the network index, changing the domain, would increase the number of bits and potentially cause it to no longer be stored inline, impacting performance of tracing and update subnetwork. That is why we added a second status attribute, we called it construction status. This gives more status options, but does not increase the number of bits used for typical tracing. So I would ask, how is In Service -Warranty different from In Service. I would probably add a construction status for Warranty and not change lifecycle status.

‎08-21-2023

can you send me just the c_subnetworkcontrollers table?

‎08-21-2023

I frequently use duplicated subnetwork names in mesh electric, so I know that works in the asset package. The errors you are showing are about terminal assignment being used for two different subnetworks. Is this asset package purely the result of an export to asset package or was the asset package post processed in some way?

‎08-15-2023

I'm guessing you have the tier defined as Radial and not Mesh. Unfortunately there is not a good way to change this except to take all your data back out to asset package and change it there and then reload it. You could make it trace without this error, but you will not be able to run update subnetwork with your current configuration without getting this error when two or more subnetworks are tied togehter.

‎08-15-2023

Changing the Normal Status of the device to closed should connect them. But, you will get multiple subnetwork names on all the features in both subnetworks if you run update subnetwork. If this is just for tracing, then you can run the trace without running update subnetwork.

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by JohnAlsup

Re: stop trace at any vertex along the edge

Re: Set Structure feature as starting point

Re: Set Structure feature as starting point

Re: Nested Subnetworks in Electrical Model

Re: Nested Subnetworks in Electrical Model

Re: Nested Subnetworks in Electrical Model

Re: Nested Subnetworks in Electrical Model

Re: Apply Asset Pkg error message

Re: Adding domain values to an existing domain in an Asset Package question.

Re: Modifying Asset Package directly vs using D_Rename Table

Re: Modifying the Lifecycle Status Domain Values in the UN

Re: Apply Asset Package - Duplicate Subnetwork name in C_SubnetworkControllers table

Re: Apply Asset Package - Duplicate Subnetwork name in C_SubnetworkControllers table

Re: How can I change the status of a switch breaker, that connects two different circuits, to close

Re: How can I change the status of a switch breaker, that connects two different circuits, to close

Re: 14 Million Associations - Best way to load to ...

Re: Migrating Pole–Conductor Relationships to Stru...

Re: Migrating Pole–Conductor Relationships to Stru...

Re: Migrating UN from one geodatabase to another g...

Re: Subset of Data to UN

European Utility Network Community (UNC)

Electric Generation and Transmission