Latest Contributions by RobertKrisher

You would set the lifecycle status to Out of Service (LifecycleStatus=0) and then set the construction status to be Abandoned (ConstructionStatus=1) or Removed (ConstructionStatus=2). This seems a little weird at first, but as Mike mentioned it's done to make tracing faster as well as to make it easier to extend the model with your own status values. Many customers will customize their construction status domain with statuses from their own work management or construction design applications. By separating the attributes for controlling tracing (lifecycle status) from the states represented for construction management (construction status) you can customize your status values without needing to worry about how it will affect tracing. ... View more

You can find the definitions of all the error codes in the online help here: Errors—ArcGIS Pro | Documentation Some general resources you can use to get up to speed on the UN for electric: Learn ArcGIS Utility Network for Electric Utilities Here's an article that provides more details about those error numbers specific to the electric industry: Electric Topology Errors For a better overview of the number of errors I recommend running the Summarize Utility Network Errors tool that was included in the utility network foundation project you downloaded (its part of the Utility Data Management Support Tools). The two errors to start with are your type 25 errors (stacked points) and your type 37 errors (subnetwork tap). These are likely responsible for many of your other errors. For the stacked point features, you can't have multiple devices at the same xy location. If these are duplicate features, delete all but the correct feature. If these are devices co-located at a structure, you will need to offset them in your map while still maintaining proper connectivity to lines. For the subnetwork tap errors, those features have a special configuration that restricts how they are allowed to be connected to lines (learn more about subnetwork taps). You can either edit all those features to meet the new drawing requirements or you can remove the subnetwork tap category from them. Doing the latter will limit some of the functionality for those features, but if this is all transmission features you're modeling I wouldn't worry about it too much (subnetwork taps are typically used to handle single phase taps in unbalanced model). Type 25 and type 37 errors will cause the system to also generate a lot of type 8 and 9 errors, so once you cleared up all the 25s and 37s, you'll be in a better place to understand the remaining errors. ... View more

That will depend on your workflows and user requirements. I recommend you familiarize yourself with the ArcGIS Architecture Center. Start by looking at the network management system reference architecture (especially the design decisions and considerations). You can then look at several test studies that were performed using this reference architecture to see how it performs under different scenarios, and use that to make informed decisions about your own design decisions. ... View more

@PierreloupDucroix correct, a geoprocessing service runs within the context of the server and feature service. Does the account you're using to run the geoprocessing services have the correct user type extension? Is the script any better behaved if you use the ArcGIS API for Python instead of ArcPy? ArcPy was originally developed for desktop analysis, so I have noticed that when you need to be precise with service login information in a non-ArcGIS Pro context that the ArcGIS API for Python (which was developed to target AGOL/ArcGIS Enterprise) is more reliable. ... View more