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

[BryanMay531]

 If I add values to a domain above like I did below, is ok to use codes 6 thru 11, or should I skip values for later versions of the model and the possible migration forward that we might need to do? 

 

[JohnAlsup · Accepted solution]

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

[MatheusSparapani]

Hi John, can you help me?

If I want to add new values in a domain that is used in a network attribute, which path can I follow? For example, I want to add abcn in phasesnormal attribute.

[JohnAlsup]

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.

[MatheusSparapani]

I don't need to trace on Neutral, I just want to have this option on the list domain at the phasesnormal attribute, but, this attribute is a network attribute, my question is, if a add new code domains in a network attribute, I will "change" the number of bits, perhaps this will modify my network and If I understand, it's not usual.

[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.

[MatheusSparapani]

Right John, if I want to include new code domains in a domain that is used in network attribute, like nominalvoltagelinetoline, what I need to do? Just add the code domains or I need to configure another thing?

In this example, I want to add this three domains.

[JohnAlsup]

Non-Inline network attributes are easier to work with.  For voltage, we used the actual value of the voltage in Volts and then give it what ever description we want.  This way we can use the same field across multiple voltage levels.  So, what you have in the picture is the correct way to add them.

[MatheusSparapani]

Great John, do you have some documentation about this? When I can add domain in a list domain that is used in a Network Attribute and when I can't, something like the correctly path to do in both cases.

In some cases I modified a list domains in a attribute like Lifecycle Status (That is used in Network Attribute), and a received a error when a tried to apply the UN, and in simple attributes I don't received errors.

I did a post yesterday about this question, because it is still not very clear to me.

https://community.esri.com/t5/arcgis-utility-network-questions/adding-values-in-a-domain-that-is-use...