Latest Contributions by RobertKrisher

The attribute substitution category is assigned to a device or junction that can substitute or "swap" the phasing of a downstream line, it must also have a network attribute that is configured for attribute substitution defined for it, and any features that are substituting phases must have that attribute populated. If you have a double dead-end pole top assembly where the B and C phases are swapped, you'd use attribute substitution. A subnetwork tap is a network category assigned to a feature that allows the feature to not restrict phasing on the downstream tap line. If you have a B-phase line tapped off a 3-phase overhead line, you would place a B-phase overhead tap (which has the subnetwork tap network category assigned to it at the intersection of the two lines. Because it is a subnetwork tap it would allow the B-phase line to be energized without restricting the phasing of the mainline to also be 3-phase. If you were to place a 3-phase dead end on the mainline, it would restrict all the downstream lines to be B-phase. ... View more

Migration I recommend you read the articles in this learning series to answer your questions: Migrating to the Utility Network. The first tutorial in the series shows you how to create a data migration starting with the simple data mappings tool. The simple data mappings tool helps create a migration workspace that does all the transformations for you, append with transformation requires you to create your own mappings with translations (a very tedious process!). If done properly they both can achieve the same results, but creating your own migration and transformations can take months, but using the simple data mappings tools processes takes hours. Field Maps Field maps is still working on supporting the utility network. Until it does you will need to select the option to deploy a v6 utility network when you deploy your utility network. No Domain If you deploy a utility network without a domain, you will only have structural features. This means you won't be able to represent any utility features for tracing or analysis. ... View more

It looks like you are using custom fonts in your ArcGIS Pro map, for the server to render those symbols you will need to install the fonts on each server as well. You should avoid publishing feature services that contain subtype group layers because they have many limitations and known issues. Instead you should follow the best practices outlined in this article for how to manage services/maps in an ArcGIS Enterprise deployment: https://community.esri.com/t5/arcgis-utility-network-blog/best-practices-for-working-with-utility-network/ba-p/1339979 ... View more

Any latency between you and the file geodatabase, such as the latency of accessing a network share or through a VPN, will adversely impact performance. If you were to put that file geodatabase locally, or if the data were stored in a mobile geodatabase, the operation would be much faster. A file geodatabase represents data using a file structure, which means that any time the data is accessed your client must interrogate a number of different files. This can result in hundreds and thousands of requests for even a simple operation like panning a map. The latency of your connection to that file geodatabase is added to every request, even a 100ms latency can add minutes or hours of processing time to a simple operation. ... View more

The utility network doesn't restrict you from connecting multiple lines to the same terminal. While there are some situations where this is not considered valid (like a valve), it's not a constraint we could apply to all termianls in all models. The most common example is how customers model manholes (sewer/storm) and transformers (electric), where the upstream terminal is connected to two lines on its upstream side. Imposing this new constraint would break existing models and require those customers implementing the utility network to redraw all the manholes and transformers in their database. ... View more

@MohamedIsmael  can you be more specific? The feature class itself is read-only, but you can add fields to it (assuming you don't have any schema locks). The field is then populated when update subnetwork is run using the summary functions you have defined in your subnetwork definition. ... View more

Add a field like you would on any other table/class (using one of the GP tools or the Field view), then use the Set Subnetwork Definition tool to configure summaries on your subnetwork definition that reference those fields. This is what the online help means when it says this:   ... View more

It is required because of branch versioning. When working with a utility network in an enterprise geodatabase you must enable branch versioning on the utility network dataset. When you enable branch versioning, we automatically enable archiving because the tables that are registered as branch versioned are storing all the historical edits in the tables themselves. You cannot disable archiving on branch versioned data. In addition to the online help, it is also discussed in this article: To Branch or Not to Branch - An Introduction to Branch Versioning   ... View more