Special Treatment of Tie Devices

In order to classify barrier features between two feeders in the same tier as either open switches or tie devices, you must map the Designer Field “IsSubnetworkController” to the Utility Network field of the same name.

This field is part of the Utility Network schema, and it has two possible values:

• 0: False, this is a potential candidate for a tie device.

• 1: True, this is a source. If true, the application passes that information into the “tieDeviceInfo” record to denote that the barrier feature is a source and a stitching point from its current feeder to a different feeder it is energizing. Subnetwork controllers are present in the “tieDeviceInfo” record, but they do not represent the barrier between two feeders in the same tier. In other words, they are connection points between two feeders but in such a way that they, at the same time, represent the source/subnetwork controller for one of them.

In order to make final decision if a switch device is going to be marked as a barrier feature between two feeders in the same tier (in other words, a tie device), an additional condition need to be met:

• The GIS field which contains the subnetwork name value for a specific switch (the field is usually named ‘Subnetwork name') needs to have a tuple of subnetwork names as in the following example, SubnetworkA::SubnetworkB. This field needs to be mapped to the SubnetworkName Designer Field.