POST
|
If you never change any rules or terminal configuration or association rules or network attributes or network categories, then you probably would never see some of the errors I am referring to. These are errors in the network properties that arise due to changes in the network properties. For example, I have a device with a two terminal configuration. Now, I change that device to use a single terminal configuration, but I did not change all connectivity rules. So, when I export those rules, I won't be able to import them as some of them will be invalid.
... View more
11-08-2023
06:02 AM
|
1
|
1
|
647
|
POST
|
Copy & Paste and XML Import will bring over any errors that exist in things like rules, roles, etc. Apply Asset Package will catch those in Apply and prevent them from being introduced in to your new utility network
... View more
11-07-2023
05:53 AM
|
2
|
1
|
760
|
POST
|
Hierachical won't help you here. You will have to make this two seperate lines.
... View more
11-06-2023
04:01 PM
|
0
|
0
|
661
|
POST
|
A service territory class can contain multiple polygons. Changing the extents of the service territory class after creating the utility network is not supported. You should make your service territory class extent large enough to cover all your current and future service territory before creating the UN.
... View more
11-06-2023
02:06 PM
|
0
|
0
|
271
|
POST
|
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?
... View more
11-06-2023
02:03 PM
|
1
|
0
|
274
|
POST
|
If you are trying to actually trace the structure network, not a domain network, you can use a Connected Trace or Shortest Path Trace.
... View more
11-06-2023
10:05 AM
|
0
|
0
|
247
|
POST
|
it would only work for tracing the structure network, not a subnetwork.
... View more
11-06-2023
03:48 AM
|
0
|
0
|
284
|
POST
|
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.
... View more
11-06-2023
03:46 AM
|
1
|
5
|
689
|
POST
|
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?
... View more
11-05-2023
03:57 PM
|
0
|
0
|
707
|
POST
|
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.
... View more
11-03-2023
05:43 AM
|
0
|
0
|
757
|
POST
|
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.
... View more
11-03-2023
03:30 AM
|
1
|
0
|
796
|
POST
|
What Foundation release is this from and what versions of Pro and Enterprise are you using?
... View more
10-25-2023
01:39 PM
|
0
|
0
|
396
|
POST
|
Yes, that should be fine, as this domain is not used in a network attribute.
... View more
09-08-2023
11:56 AM
|
0
|
0
|
328
|
POST
|
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.
... View more
09-08-2023
10:25 AM
|
1
|
1
|
509
|
POST
|
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.
... View more
08-31-2023
10:00 AM
|
4
|
0
|
363
|
Title | Kudos | Posted |
---|---|---|
1 | yesterday | |
1 | a week ago | |
1 | 03-21-2024 11:27 AM | |
2 | 03-14-2024 11:29 AM | |
1 | 03-12-2024 07:40 AM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|