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; } } }

Nejlepší postup pro správu měřicích bodů plynu (nebo bodů propojení či zachycení) a ventilů jako řadičů podsítě v Utility Network

CoronaGis

Ahoj všichni,

Pracuji s Esri Utility Network pro distribuční systém plynu a mám konkrétní otázku ohledně nejlepšího postupu při zacházení s měřicími body plynu (PM) - (nebo body propojení či zachycení) - a ventily jako řadiči podsítě.

V našem současném systému (geometrická síť) jsou oblasti definovány těmito třemi objekty:

ventily
měřicí body
body propojení nebo zachycení

Zde je zjednodušená ilustrace scénáře:

Zelená čára představuje District A.
Modrá čára představuje District B
Ventil (zobrazený jako symbol motýla) se nachází na hranici mezi District A a District B.
Měřicí bod (PM) je velmi blízko ventilu (asi 1 metr od něj) a patří do District B.

Pokud nakonfigurujeme jak ventil, tak PM jako řadiče podsítě, způsobí to problémy s validací podsítě, protože střední potrubí (X), které ve skutečnosti patří do District B, by bylo definováno jako nová mini oblast.

Moje pochybnosti a otázky jsou:

Doporučuje se používat pouze ventily jako řadiče podsítě a považovat měřicí body (PM) za běžná aktiva logicky propojená s ventily? Do které fcl/skupiny aktiv/typu aktiva je lepší PM zařadit? Jaká pravidla můžeme použít (junction-edge nebo umístit měřicí bod mimo potrubí)?
Doporučuje se používat pouze ventily jako řadiče podsítě s atributem, který identifikuje, že jsou také používány jako PM?
Případně existuje nejlepší praxe pro modelování měřicích bodů a ventilů oba jako řadiče podsítě, když jsou tak blízko sebe a patří do stejné oblasti?
Jak ostatní implementace utility network řešily tento druh situace?
Existují specifická pravidla nebo konfigurace podsítě, která mohou v tomto případě zabránit chybám validace?

Děkuji předem za jakoukoli radu nebo příklady!
Astrid

Najděte více příspěvků označených jako

Gas

Pipeline

Accepted answers

Ayan Palit

@CoronaGis Thanks for posting your use case with details and drawing. I encourage organizations to conceive the best way to model the network, rather than duplicate what a legacy system used to do. Utility Network has much broader modelling capabilities with greater possibilities.

Here are my comments:

Start at identifying the subnetworks for your gas distribution system. A great resource for this is: Managing Gas and Pipeline Networks: Creating Subnetworks
Is District similar to a pressure zone? If so, Compressor or Regulator are the prime candidates to act as the subnetwork controller for Pressure tier.
Controllable valves are the prime candidates to act as the subnetwork controller for isolation tier.
Measurement points do not impact network behavior and therefore not good choice for 'device' and hence 'subnetwork controller' (only devices can act as controllers).
Assuming use of the Gas and Pipeline Referencing Utility Network Foundation , PipelineDevice has a yes/no flag field, that can be used to indicate Measurement or SCADA indicator. Note this is simply an attribute, and doesn't impact network behavior.

Utility companies often have unique business requirements that drive the modelling decisions. Hoping others in the community will share their implementation advice.

All comments

Ayan Palit

Here are my comments:

Start at identifying the subnetworks for your gas distribution system. A great resource for this is: Managing Gas and Pipeline Networks: Creating Subnetworks
Is District similar to a pressure zone? If so, Compressor or Regulator are the prime candidates to act as the subnetwork controller for Pressure tier.
Controllable valves are the prime candidates to act as the subnetwork controller for isolation tier.
Measurement points do not impact network behavior and therefore not good choice for 'device' and hence 'subnetwork controller' (only devices can act as controllers).
Assuming use of the Gas and Pipeline Referencing Utility Network Foundation , PipelineDevice has a yes/no flag field, that can be used to indicate Measurement or SCADA indicator. Note this is simply an attribute, and doesn't impact network behavior.

Utility companies often have unique business requirements that drive the modelling decisions. Hoping others in the community will share their implementation advice.

RobertKrisher

It depends on the kind of valve between the two districts and what tier the subnetworks belong to. I'll call out @TomDeWitte for the final design intention of the model since it doesn't contain any definition of a district metering area. At the end of the day, it is your model, and you should configure it to meet your needs.

If we interpret your question through the way the model comes configured, I have to assume that the district is either a system, pressure zone, or isolation zone. You can look at the data model to see what devices are allowed to control subnetworks to infer how the model was designed to be used:

System - If these districts represent different systems and the PM is actually a meter, then this could be represented as a system subnetwork where the PM is a Custody Transfer Meter.

Pressure Zone - If the valve regulates pressure, this could be represented as a pressure subnetwork where the valve is a regular and the subnetwork controller. The PM would be a Pressure Monitoring Device.

Isolation Zone - If the valve is a Controllable Valve between two arbitrary areas of your network that you want to be isolation zones (it seems unlikely, but I'll mention it here). The

If it's some kind of metering district, then we'd be talking outside of the current configuration, and I'd want to defer to Tom before I exercise too much creativity.

TomDeWitte

When I looked at your diagram, I interpreted it to be at least 2 OVERLAPPING subnetworks. The Gas Measurement Meter (PM), I would guess to be what we call a custody transfer meter, which is one of the types of device our gas and pipeline industry model uses as a subnetwork controller to distinguish between two system subnetworks. The valve at the edge of your districts could be a pressure regulating valve, which our gas and pipeline industry model uses as a subnetwork controller to distinguish between two pressure subnetworks, or the valve could be an controllable valve used for emergencies, in which case we use that type of valve as a subnetwork controller to distinguish between two isolation zones. The pipe between the two devices can belong to more than one type of subnetwork. That pipe will participate in a system subnetwork, a pressure subnetwork and a isolation subnetwork.

Tom

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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