Select to view content in your preferred language

Tier Name and Tier Rank is empty

511
2
Jump to solution
11-01-2024 12:00 AM
JohnGoat
Occasional Contributor

Hi all,

If the features is a Subnetwork Controller, it is seen that the Tier Name and Tier Rank values ​​are filled. Why are the Tier Name and Tier Rank values ​​not filled for all sub-features included in the Subnetwork Controller? 

If these fields were filled in, we could use a more detailed Filter Barrier in tracing operations. For example, with a Filter Barrier such as TIERRANK = 3 And normaloperatingstatus = 0, I could find the switching equipment at the desired Tier in transitions between tiers with trace.

 

1.jpg

2.jpg

  

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

The types of tie devices are pretty unique within each tier, so if you see an open medium voltage switch you know its a tie between two distribution circuits. If you see an open high voltage switch its for your transmission system.

Tier rank and tier name are used to indicate the tier rank and tier name of the subnetwork controller. For features that participate in the subnetwork you will need to infer this using the subnetwork name.

View solution in original post

0 Kudos
2 Replies
RobertKrisher
Esri Regular Contributor

The types of tie devices are pretty unique within each tier, so if you see an open medium voltage switch you know its a tie between two distribution circuits. If you see an open high voltage switch its for your transmission system.

Tier rank and tier name are used to indicate the tier rank and tier name of the subnetwork controller. For features that participate in the subnetwork you will need to infer this using the subnetwork name.

0 Kudos
JohnGoat
Occasional Contributor

@RobertKrisher wrote:

The types of tie devices are pretty unique within each tier, so if you see an open medium voltage switch you know its a tie between two distribution circuits. If you see an open high voltage switch its for your transmission system.

Yes you are right, but we have a custom Utility Netwrok data schema. Our data schema does not have unique data types at each tier. For example, the same data type is present in every tier transition.

Tier rank and tier name are used to indicate the tier rank and tier name of the subnetwork controller. For features that participate in the subnetwork you will need to infer this using the subnetwork name.


 

0 Kudos