Best practices for managing assets from other utilities company within the same territory (ArcGIS Utility Network)

CoronaGis

Our company manages pipelines and we have generated the Utility Network with assets belonging to our company.
However, in the same area, there are assets belonging to other companies (sometimes we have only partial information) which are mapped and displayed (read only) when needed.

In your opinion, what is the best way to manage assets from other company?

1) create a specific dataset with specific FCs using UN model?
2) create a specific dataset with specific FCs without UN model?
3) insert the data in the same UN we have made from our data even if we get a LOT of dirty areas?
4) something else?

Thank you

Astrid

RobertKrisher

I'm curious to hear what other utilities say, but consider what your requirements are and how much time you're willing to spend creating/maintaining these features. If they are shared structures (like poles) that are owned by other companies, then you'll probably want them in your utility network. If you're talking about privately owned infrastructure that you provide service to and are responsible for maintaining, then again you may want to keep this in your network. If it's just additional infrastructure in the area that you need to be spatially aware of, then you likely won't want to include it in your network but make it available as simple features.

You don't want to take an approach that would result in creating a large number of dirty areas or topology areas in your network as this will affect the network features that you do own in the area and make quality assurance harder (because you will be unable to maintain a clean topology).

View solution in original post

RobertKrisher

I'm curious to hear what other utilities say, but consider what your requirements are and how much time you're willing to spend creating/maintaining these features. If they are shared structures (like poles) that are owned by other companies, then you'll probably want them in your utility network. If you're talking about privately owned infrastructure that you provide service to and are responsible for maintaining, then again you may want to keep this in your network. If it's just additional infrastructure in the area that you need to be spatially aware of, then you likely won't want to include it in your network but make it available as simple features.

You don't want to take an approach that would result in creating a large number of dirty areas or topology areas in your network as this will affect the network features that you do own in the area and make quality assurance harder (because you will be unable to maintain a clean topology).

CoronaGis

Thank you very much for your contribution.

If I understand correctly, your advice is to use a dedicated dataset (except in specific cases).

Another question: would you port the data from other company assets in UN format (only line, device, junction, and assembly) or would you leave the data in its original format (geometric network)?

I ask because we will have .aprx files and webmaps that will need to show both sets of data together (our property assets and other company assets) and these assets would be readonly.

Thank you

Astrid

RobertKrisher

I would recommend you manage them as simple features in a separate dataset and if you want to do network analysis with their data you will need to wait for them to migrate off their geometric network.

CoronaGis

.