topic Utility Network – Why is “Station” modeled as a Device instead of an Assembly? in ArcGIS Utility Network Questions

Utility Network – Why is “Station” modeled as a Device instead of an Assembly?

MatteoMagnani_WT — Wed, 06 May 2026 13:48:14 GMT

Hi everyone,

I’m working on a Water Utility Network Solution data model and I have a question about Esri’s modeling approach.

Specifically, I’m trying to understand why the “Station” asset group (with asset types such as Sample or Pump) is implemented within the Device feature class, rather than as an Assembly.

From a conceptual standpoint, a “station” could be seen as a container or aggregation of multiple components, which would make it seem closer to an assembly than to a single network element.

What is the reasoning behind this design choice in the Utility Network model?
Is it related to topology constraints, network behavior (e.g., connectivity participation), or asset management considerations?

Thanks in advance!

Re: Utility Network – Why is “Station” modeled as a Device instead of an Assembly?

MikeMillerGIS — Wed, 06 May 2026 15:47:36 GMT

We model these locations as devices to simplify data conversion from existing datasets and to support ongoing editing and data maintenance. The device feature is configured as a container, allowing you to add unit-level details using WaterJunctionObject features. If a more detailed representation of a pump station or other facility is required, I recommend using structural containment through the Structure Boundary or Structure Junction features instead.

For example, lets look at a Pump Stations. In this example, we are modeling three pumps.

If we turn on Show Content, we can see that fitting and the valves turn on.

So we are essentially modeling "Assemblies", but using the structure boundary instead of a domain Assembly feature.