Latest Contributions by JohnAlsup

Since two cables cannot exist in the same x,y,z, the Attribute Rule you pointed out is designed to set the Z of the cable to ensure there is no topological conflict.  However, in our case this may not be the behavior you desire.  If so, you can remove/dispable/delete the attribute rule.  However, you will need to ensure the cables are not all occupying the same x,y,z. ... View more

Hi Vish. By adding these as features in the utility network class, you are significantly increasing the size of the network index.  My first question is, why should the "spans" be in the network index?   Are you tracing on them?  Do you want the subnetwork names of the subnetworks the span contains?   We did add a new asset group in StructureLine called Aerial Span in the latest electric model.  This could be used for this, however, doing so may impact performance of operations like trace and update subnetwork.      ... View more

The Utility Network is both Z and M aware.   The domain, resolution and tolerance can be viewed on the properties of the feature dataset that contains the Utility Network.  Typically, it will have a tolerance of .0001 units, but could be different if you changed the spatial reference. Z Tolerance (Environment setting)—ArcGIS Pro | Documentation   ... View more

Hi Lindsey On question 1.  Both methods you describe are valid, but the Z value might need to be larger depending on your vertical tolerance. As to which is better, that is up the each consumer.  Personally, I like the transformer tanks spread out so I can see each one.  But, I could see where having them stack might better for spatial placement, you just have to remember to set the Z value or set it in the template.   As for Question #2, I would use a Electric Assembly/Low Voltage Service and then place all my services as content of the assembly and then use a Line End on the Low Voltage line and create connectivity associations from the Low Voltage Services (meters) to the line end.  When multiple ElectricDevices and ElectircJunctions share the same X,Y,Z, only one will get connected to the network.  Since only 1 has the same Z as the line, it is the only one connected.  Connectivity from coincidence requires the same X,Y,Z and you can only have one Device or Junction as the same X,Y,Z.  ... View more

I would suggest using a "Shortest Path" trace.  Since a Ring is basically the same as mesh, there are two or more paths to the power source.  As Mike pointed out, this create indeterminate flow direction, so a directional trace upstream down work. ... View more

I would leverage the d_configuration table and add a new column for your configuration.   ... View more

You should look at the FME Workbench, which can be used in Data Interop. https://community.safe.com/s/article/utility-network-migration-tools You would need to update it a little, but it will get you a lot closer. ... View more

The switch could be either, although in this case, I should have left it as Overhead.  This modeling is based on our latest model which is the ArcGIS Enterprise v1 (model 4).  There is nothing in the model that requires 10.9, you should be able to apply it to a 10.8.  Try it and if it fails, you can email directly at [email protected] ... View more

Good catch, I will update the diagram.  For underground the feature would be ElectricJunction, Asset Group :Medium Voltage Connection Point, Asset Type:Underground Phase Connector.       ... View more

this image shows it a bit clearer   ... View more

The associations, which did not show up well, are between the switches/fuses and the orange balls which are Tap features.  There are no associations between the Line End feature and anything else.  You really don't need the line end at all. ... View more

Hi Lindsy If you are going to rely on the Utility Network to maintain phase, then you will need to model in a specific way.  In the image I have attached, this is basically how you will need to model this type of connection.  This allows the system to maintain the phase connectivity for you.  One thing to note is that the switch should never sit directly on the tapped line, as the system will not know which line is being protected.  Also, if a "Tap" feature is connected to the tapped line, then you will need for the switch to not be at the same x,y,z as the tap.  You would also need a junction to junction connectivity association to create the connection between the switch and the tap.       ... View more

Hi Linsdsey A Pad Mounted Switch (AKA Pad Mounted Switchgear) is a very complex piece of equipment that typically has multiple cables entering and exiting and consists of multiple switches and fuses and busbar.  The correct paths for energy cannot be defined by a single points.  There are multiple types of switches that can be found in this equipment that have very different characteristics.  The simplest is the Cabinet Switch, to the most complex V and T Blades.  Each of these has different terminal configurations and path characterizes in the Utility Network Electric Model. Here is an example of the internals of a Pad Mounted switch.  This would have 4 sets of cables entering the cabinet. Two sets of switches and two sets of fuses.  The smaller picture is from a customer’s map in the Geometric Network.  The blackbox is the Pad Mounted Switch and it contains four switches, four sets of lines and four busbars.   As Phil points out, this is a starting point and the rename table provides an easy way to change names of things, as long as the function of that thing does not change. ... View more

in my opinion, fields in the UN should only ever be viewed in the context of the subtype anyway.  In fact, that rule should really apply to any table with subtypes.  We demonstrated field reuse to help reduce the total number of attributes on any given table/class.  More fields will have an impact on performance.  How much, we have not documented, but everything comes with a price. ... View more