nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Utility and Pipeline Data Model 2023 with "Subnetwork Sink" network type

VishApte_NGIS

Hi all,

We are implementing UPDM model for Oil and Gas production systems. We do not need any distribution tier or distribution asset classes.

I notice that the UPDM model's Pipeline network is defined as "Subnetwork Source" model and wondering why.

Since our system will be a production facility collecting the resource right from wellheads to a processing plant / refinery for the final product, we are thinking of changing the network to "Subnetwork Sink" system with Processing Plant / Refinery Facility as the ultimate sink.

Is there any danger in pivoting around the network type from "delivery" to "collection"? Would any of the LRS functionality be impacted? We intend to have tiers as "Production System (rank 1)", "Trunkline (rank 2)", "Gathering (rank 3)". Gathering lines carry the resource from wellheads to satellite plants or compressor stations and then Trunklines carry to the major processing plant or refinery. The network ends there.

Just wondering why UPDM model is Source based and not Sink based in the first place.

Thanks,

Vish

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

MikeMillerGIS

The tiers do not seem correct. It sounds like trunkline and gathering are piers, so they should both be rank 2 or merged into a single tier and use subnetworks to separate them.

RobertKrisher

@VishApte_NGIS what devices are responsible for moving resources through the system? is it the wellheads, pumps, and compressures that are pressurizing and moving materials through pipes? or something at the destination which is drawing materials towards it?

The most important consideration to all of this is how it will respond to an isolation trace. The isolation trace shows you how to isolate an area of a subnetwork from its controllers.

If you model your tiers using sinks, then the isolation trace will show you how to prevent materials from arriving at their destination, and which production sites will be cut off.

If you model your tiers using sources (the typical way for pipeline) the isolation trace will show you how to isolate an area of the network from its supply and which processing plants/refineries might not receive materials as a result.

@TomDeWitte

TomDeWitte

Hi Vish,

As Robert noted, there is a very specific reason for modeling oil and gas pipe networks as Source-fed models versus sink-fed models. The engineering of a gas or oil pipe network is one based on the in-pipe commodity being pushed through the pipe. Whether it is the pump within a pump station or a compressor within a compressor station, the commodity is being pushed through the pipeline.

You mentioned the use of LRS (Linear Referencing System). The Esri provided ArcGIS Pipeline Referencing capabilities of ArcGIS do not require a specific source or sink configuration. You will be able to build and manage routes and measures with either source/sink configuration.

Tom

VishApte_NGIS

Thank you @MikeMillerGIS , @RobertKrisher and @TomDeWitte for your responses.

In theory, the resource is pushed right from wellheads to the processing plant. But it is not a single source that is distributing like Water Treatment Plant or Electric Substation.

The simplistic view of our pipeline system is as below:

We would like to have entire network coming into the processing plant to have a common name e.g. PipelineSystemSubnetworkName value of "Ballena Gas Pipeline System". Then, anything upstream of each satellite stations or nodal pumps or compressor stations to have its own name e.g. GatheringSystemSubnetworkName e.g. "Blue Lake Gas Pipeline". And then network from wellheads to the first manifold downstream to have its own name e.g. FlowlineSystemSubnetworkName of that manifold's id e.g. "Tawewa Basin #108 Gas Pipeline".

Only way I can think of maintaining this as a subnetwork name is creating a collection system and not a distribution. Your thoughts are welcome.

@TomDeWitte Good to know that source or sink does not have any impact on the LRS route creation.

@MikeMillerGIS , we are still contemplating whether flowlines and gathering lines will have different ranks. They might end-up as piers once we develop a prototype.

Thanks,

Vish

RobertKrisher

If you want to do that you can use something like the batch trace tool to do a connected trace to get everything upstream of the processing plant. You can also set up each controller to have the same subnetwork name, maybe broken by rank (PP1 Gathering, PP1 Trunk), they're allowed to be disjoint.

If you keep the model as it is right now, and set up your compressors/pumps as your controllers then when you run an isolation trace it will show you how to cut off pressure from the pump/compressor to prevent gas/oil from leaking out into the enviornment.

If you were to switch to a sink-based model, the isolation trace would only show you how to prevent gas/oil from getting to the treatment plant, but it wouldn't show you how to isolate the pressure source.

Given that there is a workaround for naming your processing areas (batch trace tool) but not for isolation traces, I would lean towards rely on the model as it was built.

You know your data and your business requirements better than I do. Those trunk lines are probably much easier to understand how to isolate than a typical distribution system, but if you model the pipework inside stations than it will be very beneficial to have that isolate trace working the way it was originally configured.

VishApte_NGIS

Thanks @RobertKrisher for your reply.

I will discuss with the engineers about the Isolation Trace requirements. And at a high-level, isolating a pipeline or a plant is a very complex process and currently not done in GIS.

The stationing pipeline and other assets inside the stations are not captured in GIS and are part of the Plant Management System. We will only have representational assets in GIS to fulfill the topological requirements.

Re. Isolation Trace workaround, would Upstream Trace with Filter Barriers criteria of "Category" = "Valve" not achieve the same result for the "Sink" based model? Our pipeline network is strictly radial and not looping/indeterminate like a typical water distribution network. Typically, there will be only one valve upstream that will isolate a section.

Thanks,

Vish

RobertKrisher

@VishApte_NGIS an upstream trace as you have described it would show you the path upstream to the valve(s) to isolate the starting location(s), but not the area affected by the isolation.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.