APR Event vs PipelineJunction (Coupon)

[HazelRiordan]

We use Utility Network with APR.  Coupon is in both. (Utility Network = Pipeline Junction. APR = Event)  Does anyone know why it is in both places and if there is an advantage to putting them in APR?  Esri support says that if we keep them in both, we have to enter them in both.

[AyanPalit · Accepted solution]

@HazelRiordan The Utility and Pipeline Data Model (UPDM) supports multiple implementation patterns.

1. Utility Network (Gas Asset Package)
2. ArcGIS Pipeline Referencing (information model)
3. Utility Network and ArcGIS Pipeline Referencing

The model is flexible to allow for all these implementation variations. In some cases, this introduces redundancy as for Coupons. The choice is up to the organization based on their business requirements.

Coupons maybe better modeled through Utility Network topology and rules - use as Pipeline Junction. However, some pipeline operators using APR-only, model Coupons as LRS event. In either case, there is no reason to keep both and enter the data at both places.

[HazelRiordan]

Thank you for the explanation.  So in that same thought, I should be able to add features to APR and stop tracking them in Utility Network.  For example, if I want to track Pipe Coating & Pipe Spec in APR instead of Utility Network to reduce the amount of segments in Pipeline Line, that should be ok to do. Correct?

[AyanPalit]

@HazelRiordan This becomes a bigger design decision.

I have seen some Transmission pipeline operators model Pipe Coatings as an LRS event; they use Utility Network but do not populate the Coating attribute in PipelineLine. Some choose to take the most prevalent coating and update the Coating attribute in PipelineLine.

Pipe specs are core to  PipelineLine and some may act as Network Attribute that impact functionality. So the recommendation is to keep Pipe specs at the Utility Network.PipelineLine in a combined Utility Network-ArcGIS Pipeline Referencing implementation.