Electric Device Unit Table use case

[BryanMay531]

Could anyone please give an example of a good use case for the Electric Device Unit Table?  I have a meter device that is always connected to a recloser device.  I'm wondering if I could use the Unit Table mainly because there are about 16 fields to add somewhere for the meter and there are only 71 meters in the system.  Is this a good use case?

[JohnAlsup · Accepted solution]

In our Electric Foundation model, we dropped the ElectricDevice Unit table several years ago, when non-spatial support was released with the Utility Network.  There are several draw backs to a related table.

1) Phase will not be maintained by the system

2) These related objects will not be returned in any trace.  

3) These related objects will not be included in an export subnetwork

4) These units cannot be used in any network summaries

If you don't care about any of the above, then yes you could use a related table.  However, you will have to include the related table in the publishing map.

[RobertKrisher · Accepted solution]

@JohnAlsup  @BryanMay531 

One important thing that is easy to overlook in John's response is that the electric device unit has been replaced by the Electric Junction Object non-spatial object table. You did this because the Electric Junction Object table doesn't suffer from the limitations outlined in his response. If you want to know more about how to use this new table in the electric model, you can watch this presentation from IMGIS: IMGIS - Esri Videos: GIS, Events, ArcGIS Products & Industries