Latest Contributions by JohnAlsup

I would not modify this domain for that purpose.  Neutral can be indicated a number of ways.  You could write a label expression for the phase field for  add N when systemgrounding = Wye. You could add another attribute for Neutral or use the Shared Neutral attribute = N or Y, it has neutral null means no neutral.   Updating the Phase field used in tracing could have unintended consequences, like making your system not traceable in some cases.  I have seen that when customers wanted to change it to model phase orientation.  It broke the system. ... View more

Why propagate Neutral? By adding the N, you would be increasing the number of bits used in the network index and not just adding a single value to the phase domains, but actually adding 8 domain coded values.  Neutral is only found on Wye circuits.  Neutral can be shared between circuits.  Now, lets talk about propagation.  If I have Delta circuit (3 wire system) say at 23 kV and I want to step it down to say 12470/7200 kV Wye.  Since I am not propagating N at the start of the circuit there is no way to introduce it without making the Step Down transformer a subnetwork controller.  You can do that, but many don’t want to do that.  So at the Circuit Head you would propagate ABC and you would the system below the step down the ABCN, but N will never get propagated in this scenario.  Next question is why do I need to trace on Neutral?  Not a rhetorical question. ... View more

You will want to have the network attribute inline if it is used in the subnetwork definition, as not inline requires more queries and could have a significant impact on performance. Also, what bit are you planning to add.  I'm guessing this is electric.  Adding more bit to phase may get very complicated.  For example, there is no way to represent phase orientation with this field.  Also, if you are trying to include something like Neutral as a bit or static wire, that also will get very complicated.   ... View more

I guess you have three options to accomplish this. 1) Use multiple traces, each trace stopping at locations where flow need a value set.  This would not be a fast solution! 2) Use a single trace and export the subnetwork connectivity to a json and then read the json, traversing the connectivity and calculating the value.  You could do this in python. 3) Write a tool in Enterprise SDK (SOI probably) that performance a trace.  Try using the IUNTraceResults4.TraceResultPaths property to walk the connectivity.  I have not tried this, but will soon.     ... View more

check the attributes on the junction features that are used in the subnetwork definition, like lifecyclestatus.   ... View more

Propagation will not work for this workflow.  You could use Functions in a trace.  The field you would use would need to be a network attribute.  Then you could use a trace to subtract the fields value.   ... View more

The imported junction feature is probably on a location on the line where there is no vertex.  When you create the junction using Pro, Pro actually edits the line and adds a vertex. ... View more

Yes, this is standard functionality in the Utility Network.  If you will examine our Electric Foundation Solution, we have many examples of this. ... View more

Can you clarify what you mean by duplicated structure layers?   ... View more

are you talking about a Transmission system or Balanced Three Phase system or an Unbalanced System?  Transmission and Balanced are easily modeled using a Hierarchical.  If you send me your email address I can add you to a Beta for a Transmission model that is Hierarchical.  [email protected] ... View more

If you use the D_Rename option in the Apply Asset Package, as Robert pointed out, you don't have to deal with updating the rules or subnetwork definition.  The process takes care of all that for you.  If you manually rename, then yes, you will have to deal with changing the rules, subnetwork definition, network categories, etc. ... View more