How are you supposed to designate abandoned or removed assets with the latest UN updates?

[Joshua-Young]

I am working on migrating a stormwater geometric network to a utility network but I see with the June release the Lifecycle_Combined and Lifecycle_Status have changed dramatically from the previous values and there is new Construction_Status. I see that abandoned and removed are now in Construction_Status.

How do I map abandoned and removed assets in the geometric network to these three fields that all seem to be trying to do the same thing but with different values?

[MikeMillerGIS]

We moved that modeling of an assets lifecycle to two fields as we found that many implementations added a lot of codes to the lifecyclestatus domain.  The LifecycleStatus network attribute is used in the subnetwork definition and the network attributes used in the subnetwork definition should be set as Inline.  Inline network attributes will be added internally to the topology, making retrieval more efficient.

To support all the possible states an organization might set on a asset and still support an inline attribute on lifecycle, we broke the modeling of lifecycle into two fields.

The lifecyclestatus is used to model is the asset a barrier or not.  You can extend this domain, but you need to make sure you do it using a power of 2 and ensure you do not exceed the available bits for inline network attributes.

The construction status is not an inline and can be expanded to support any state the asset can be.

[RobertKrisher · Accepted solution]

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.

[SamDeLore]

We made the decision to remove any non-live assets from our UN, we really only use the Lifecycle status domain for in service assets, or assets that are 'live', but currently not in use.

All other features (abandoned / proposed) get moved to Feature classes outside the UN, it's a bit more work to setup, but it's a big benefit to the config of rules, symbology, labelling, topology errors and you get complete flexibility with the schema of those other feature classes.