Analysis of running number of traces to get the whole diagram of Electric UN

[AbigailMiller]

Hi Folks,

As per our organizational requirements, we are supposed to run a trace operation and export the entire diagram to software by delivering it to our vendor for Electric UN. I would like to know how to get the whole diagram and how many times we should run the trace operation to capture the control devices; and network lines for the entire study area.

Any kind of insight would be highly appreciated.

Regards,

Abigail

[AnneYvonneBlin]

Hello @AbigailMiller 
There is a lot to tell about your question. Network diagrams are designed to represent a simplification of large network areas or highlight details of small network areas. So, first of all, what kind of study area your diagram will represent? What is the size of this area (network element count)? Could the diagram focus on specific network elements only?

[AbigailMiller]

Hi @AnneYvonneBlin ,

I am using the same data for Naperville region deployed the Utility Network Expanded solution. I am looking forward to capture all the subnetwork, controller, devices.

Could you please suggest on that.

Regards,

Abigail

[AnneYvonneBlin]

Hi @AbigailMiller,

Do you imagine creating a diagram per subnetwork, or a diagram for all your subnetworks?
As I said above, a diagram representing your network in which you see a diagram feature for each network element is of little interest. Moreover, depending on the size of your network, you won't be able to generate such a diagram, or the diagram generated will be unusable.
Also, there are a few points to consider before creating diagrams:

1. Nothing prevents you to generate diagrams from a selection set present in your network map that you obtain after one of the following operations:
   - a manual selection
   - any network trace you run.
   However, building a diagram from a large set of input network elements is time consuming. Indeed, the input selection set must be retrieved from each layer in the network map and analyzed before the diagram build starts. The larger the set of network elements in input, the longer it will take to process it.
2. The more important the final diagram junctions/edges/containers counts, the longer it will take to store each diagram feature in the geodatabase
3. The more important the diagram feature count, and the more complex the definition of diagram layers, the longer it will take to load and display the diagram.
4. The smaller the number of diagram features, the quicker it is to apply layouts to your diagram.

Because of 1/ we strongly recommend building your diagrams from diagram templates that you configured with a Trace rule. This allows you to start the diagram creation from a very small set of input network elements. Then, the Trace rule (Subnetwork trace, Find Connected trace, Downstream trace and so on) configured at the beginning of the diagram rule sequence on the diagram template is applied in-memory to build the initial diagram graph. Applying a trace during diagram build is really faster than using the trace result returned as a selection set in the map as the initial input.
Because of 2/, 3/ and 4/ we recommend to add simplification rules on your diagram template (Collapse Container rules, Reduce Junction rules) so the resulting diagrams focus on the only relevant network devices and so the final count of the diagram features is limited.

Best regards
Anne-Yvonne