Latest Contributions by RobertKrisher

If memory serves me, the delete tool doesn't verify the description of the rule being deleted, only the rule ID. With that being said, it's good to have the full description so you can verify the rules being deleted before you run the script. In order to do that you will need to use the arcpy Describe method to read the utility network properties and look up the network source name, asset group name, and asset type names for each of the from/via/to elements. This can be achieved by looking at the asset groups and asset types of all the edge sources and junction soures for all of your domain networks. ... View more

It's not quite so clear cut, I recommend you spend time looking at the area I mentioned in the Electric Utility Network Foundation for examples. The two approaches you outlined above are both equally valid using the assembly/device approach. Example B looks like it would work for non-spatial objects, but based on the style of the diagram I don't think that is what is being depicted (it looks like documentation from the assembly/device model). ... View more

There are multiple ways, all equally valid, to model your equipment. The short version is that you can use assemblies and devices if you want to represent all your features spatially OR you can use device points and junction objects if you want to just represent the location of the bank spatially and represent your units non-spatially. Now for the details/history: When the utility network was originally released there was no concept of non-spatial objects, so your choices were to a) Model the bank of equipment an assembly and all the internals of the assembly as devices and junctions. b) Model the bank of equipment as a device and use the device unit table to represent individual assets within the assembly. Most customers chose the first approach because it allowed all of these objects to be included in the JSON files created by the Export Subnetwork tool. When the utility network introduced non-spatial objects the "Device Unit" and "Wire Unit" tables in the model were replaced with the new non-spatial object tables: Electric Junction Object and Electric Edge Object. You can find examples of this in the newer Electric Utility Network Foundations by looking at the subnetworks that have names starting with "Essential". You can also just open the Electric Edge/Junction Object tables and navigate to specific examples (single phase transformers, fuses, etc). ... View more

There are two users presenting on this topic at the upcoming User Conference (2023): Managing Facilities & Vertical Assets with GIS ... View more

@RomuldKiobya when you export your asset package you can (and should!) choose to include the data from your database. Then after you've adjusted your service territory in the asset package you should apply the asset package to a new geodatabase. ... View more

Try running the tools directly from the geoprocessing pane instead of through the task framework and see if that produces more consistent results. ... View more

@JeffBlake The best practice depends on what kind of user you're sharing your map with. For a collection of best practices for creating maps referencing utility network data, I recommend you refer to the following tutorial. This tutorial demonstrates the importance of configuring things like subtype group layers and display filters. For desktop users, you should create a map using ArcGIS Pro that references those feature services and either share the individual map with them as a map file or if you have a collection of items (multiple maps, page layouts, etc) you may choose to share an entire project with your users. For web users, you will likely still use ArcGIS Pro to author your map, but you will share the resulting map as a Web Map. This web map should be very similar to your desktop map, especially with regard to the use of subtype group layers. The only catch is that you must be using at least ArcGIS Enterprise 10.9.1 for subtype group layers to appear in your field maps and at least ArcGIS Enterprise 11.1 for subtype group layers to appear in the Web Map Viewer in ArcGIS Enterprise. ... View more

@JeffBlake the map used to publish the feature service should not have subtype group layers. The subtype group layers should be used when you are consuming the feature service in your desktop maps or web maps. ... View more

As long as the cable is spatially coincident with both the network distribution point and the address point you should be able to achieve this by creating an attribute rule that runs when a new drop cable is created. It can then perform a spatial query to find the network distribution point and the address point information and perform the logic you have outlined above (calculate the cable type, update the customer count on the distribution point, and associate the address point with the distribution point). You can learn more about attribute rules on this page in the online help. You can also try out two free tutorials that show you several examples of how to use attribute rules (one and two). ... View more