Devices, Terminals and downstream outputs

[I_P1]

Hi, 

I have a question about the use of terminals and devices.

Terminals can allow the discerning of different outputs from a single device for tracing operations and subnetworks definition, like a transformer and its downstream outputs lines (max 7 lines). But for managing the various outputs, for example, in order to have one output line 'on' and one other line 'off', is it mandatory to add an additional device to do that for each line?

This is what I have understood from the online material and frequently-asked-questions, like the question and answers below: Do I need to convert my unit records into features? Only if a single unit feature has a different device status then other unit features in the same device. For example, if a non-gang operated three-phase switch has one of the three switches open, then this case should be migrated as three individual switches. If no cases like this exist in your data, then you can migrate the unit records to the ElectricDeviceUnit table

Please let me know.

Thanks

[MikeMillerGIS]

You could leverage the terminal paths of a device.

For instance, you have a selectable switch.  Which has three terminals, A, B and C.  When defining the terminal configuration, you set terminal paths of None, A-B, A-C, and A-B & A-C.  The device can be set to be in one of these states.  So if you wanted to disconnect C, you would set the device to A-B.

[I_P1]

So in a case like the one below, where I have 7 outputs (B - H), I should add all the possible path combinations in order to have a line or more than one disconnected? Isn't it easier with an additional device?

[MikeMillerGIS]

We went down the same path on xfrs and decided using terminals for the each lug was not worth.  You can accomplish the same result with a highside and lowside.  As you cannot define attributes on a terminal, what value does modeling each lug and how the wires connect.  It is best to detail the wiring as attributes.  If you need to model each lug for export to CIM, then additional features are needed, as they each need attributes and a known ID.