|
POST
|
There are no special restrictions for geometry types that pertain to the utility network.
... View more
|
1
|
0
|
58
|
|
POST
|
You can find the supported geometry types on this page: PostgreSQL data types supported in ArcGIS | ArcGIS Pro documentation.
... View more
|
0
|
0
|
82
|
|
POST
|
The looks like a bug. It should not be possible for the subnetwork name for a subnetwork controller to be Unknown.
... View more
|
1
|
0
|
110
|
|
POST
|
when you say they lose the subnetwork name, I assume you mean that the subnetwork name becomes unknown? if you run a trace, does the subnetwork include features or not? Can you post a screenshot of the trace results along with the network attributes for the circuit break? Because I think I know the model you're dealing with, I'll use the fields and values from that model (I apologize for the mix of spanish/english). In particular the Faces operacion and estado del dispotivo of the Interruptor de circuito of the which is the subnetwork controller of the subnetworks. If the faces operacion is set to Desconocido then the entire subbetwork will become unknown (nombre de subred will become deconocido). Similarly, if the controller or the first line's estado ciclio de vida is Fuera de servicio instead of en servicio then the subnetwork will stop at that feature and the remaining features in the subnetwork will become unknown. Summary: If the phasescurrent is set to de-energized, that will cause the subnetwork to be de-energized. You should also check to see if the lifecyclestatus of the circuit breaker or the first line in the subnetwork is set to something other than in-service. I normally also suggest checking the terminal connections between the circuit breaker and line, but because these circuits were previously energized that seems unlikely to be the cause of the issue.
... View more
|
0
|
2
|
123
|
|
POST
|
You can learn more about outputting flow direction information in this article: Flow directions in ArcGIS Utility Network If you're using ArcGIS Pro 3.7, ArcGIS Enterprise 12.1, you can use the Path trace to visualize the path from the source to these controllers.
... View more
|
1
|
0
|
92
|
|
POST
|
The plan is to include that issue in the next ArcGIS Pro 3.7 pro patch, which at this point is ArcGIS Pro 3.7.2. Once the patch has been released the page will be updated to indicate which patch it was included in. This issue was specific to 3.7, so it does not need to be included in any earlier patches.
... View more
a week ago
|
1
|
0
|
55
|
|
POST
|
The issue is resolved in this thread. Because their circuit breakers have busbar on both sides, instead of busbar on one side and conductor on the other, they needed to add a rule that allows busbar to connect to the bus or line side of a circuit breaker then connect the busbar that leads to the field to the line side terminal.
... View more
a week ago
|
0
|
0
|
128
|
|
POST
|
@KokilaM This is the issue I was describing in our previous thread about why your circuits weren't tracing properly. You need to add a second rule that allows busbar to connect to the line side of a circuit breaker as well, then connect the busbar that goes into the field to the line side terminal. This is one of the reasons why customers, and the newest model, have separate classifications for circuit breakers that are subnetwork controllers versus circuit breakers. The terminal configuration on non-controller circuit breaker (if you use one) should also be defined to be bi-directional so it doesn't restrict the direction of flow of electricity within the substation when backfeeding or switching sources. If both lines are connected to the terminal, then the trace will bypass the device (regardless of whether its open or closed) and if there is a subnetwork controller on the line side terminal of the breaker it will not propagate.
... View more
a week ago
|
0
|
1
|
95
|
|
POST
|
@gis_KIWI4 That shouldn't be necessary unless the lines in the substation are connected to the same terminal as the lines outside the substation. This is something that can accidentally happen depending on how the lines connected to the breaker are modeled and how the rules are configured. When a subnetwork trace attempts to traverse a terminal associated with a subnetwork controller it will automatically stop, even if there isn't a condition barrier defined telling it to do so. In the case of a partitioned, source-based domain like electric this can have several outcomes: If the connection is from a different line to the terminal of the controller, and the controllers have the same subnetwork name, then the system treats this as another controller for the subnetwork for the purposes of calculating flow direction. If the connection is from a different line to the terminal of the controller, and the controllers are associated with different subnetworks, it will be an inconsistent subnetwork error. There is a similar error if the controller belongs to a different tier. If the connection is from a different terminal on the device and its crossing the internal edge (i.e. terminal path) of the device, then the subnetwork trace will stop and no error will be returned. Even if the other controller has a different subnetwork name or belongs to a different tier. By setting up a condition barrier to stop at a device that is a subnetwork controller, you are forcing the trace to stop as soon as it encounters a device that is a subnetwork controller, even if the trace doesn't traverse to a terminal associated with a subnetwork.
... View more
2 weeks ago
|
0
|
1
|
171
|
|
POST
|
If you look at the sample electric utility network foundation for north station unit 1 and RMT003 you'll see how its configured. As long as both the power transformer and circuit breaker are configured as subnetwork controllers AND the lines associated with each subnetwork controller are connected to the correct terminal it should work correctly. Can you post a screenshot of what is selected when you trace subnetwork b (circuit breaker) and subnetwork a (the station)? I want to see that before I make any predictions about what is going on.
... View more
2 weeks ago
|
0
|
0
|
248
|
|
POST
|
Please log a case with support. If it works in 12.1 but not in 12.0 it is likely a bug that was fixed in 12.0, and if its important for your production operations you could see if there are plans to provide the fix in a patch or if there is workaround.
... View more
2 weeks ago
|
1
|
0
|
113
|
|
POST
|
You shouldn't need to change the domain on the asset type field. You should just add the values you want, and D_Configure/D_Rename the rest. If you unassign the domain and replace it with a new one, you are deleting all those asset types and will need to manually remove them from all the A, B, and C tables. Which is something best avoided and handled using what I described in the first paragraph.
... View more
2 weeks ago
|
1
|
3
|
175
|
|
POST
|
Met and discussed with @J_iaxin . The problem is that when you run a trace on a feature that belongs to multiple subnetworks the system returns an inconsistent subnetwork name error. In this case, a sub-basin has outlets to two different treatment plants so any traces within that sub-basin return this error. I have asked the user to log an issue and escalate this as a bug. Each subnetwork is consistent, and just because this area can drain to different subnetwork controllers doesn't mean the trace should fail.
... View more
2 weeks ago
|
1
|
0
|
67
|
|
POST
|
for instructions on how to enable logging to start capturing detailed performance information, check this article: Utility Network Diagnostics . Verbose will get you the trace logs, debug will get you access to even more information about all the queries. Remember that switching to a more detailed logging method like this will impact performance, so its best to do it in a QaQc environment. If you do make the change in production, make sure its only for a short amount of time.
... View more
2 weeks ago
|
1
|
0
|
86
|
|
POST
|
@SamDeLore a >3x gain in performance from tracing is a lot more than what we would expect to see and implies that there may be something else that needs reviewed/tuning in your environment. @TomBrown ?
... View more
3 weeks ago
|
1
|
1
|
93
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Monday | |
| 1 | Friday | |
| 1 | Friday | |
| 1 | a week ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
an hour ago
|