Subnetwork Controllers

Why are the Valve objects are not subnetwork controllers if they influence the resource with on/off?

•A gate valve makes the statement whether a transport resource flows through at this point or not. For this reason, this is a separating element of the type Device.

•Zone separation valves, as the name suggests, separate two networks from each other. These are always closed (off). This creates two independent subnetworks on both sides. When such a valve is opened, the behavior can change significantly. The valve is no zone separation valve anymore.
Various information can be used for the representation. At the same time, it is also possible to obtain further information via analytical processes.

•Thus they are only the separating elements and are terminating elements for both networks! When such a gate valve is opened, the behavior can change significantly. This does not make this gate valve a subnetwork controller, but you must pay special attention to it. This may also result in the requirement for representation. Since the gate valve is not contained in any network, but is only a boundary, it is a zone separation gate valve.

Pay attention to the usability of the model, for this reason zone gate valves are not considered as a separate group, because they come directly from a query or the subnetworks. If a valve becomes a zone separation valve (or vice versa), the asset type would need to be changed, which is a significant effort.

 

Decommissioned and Dismantled Lines

 

How should decommissioned objects be handled?

•Decommissioned lines should be separated from the operational lines with minimal shortening so that these assets are no longer interconnected. This also corresponds to the actual situation in the field.

•Additionally, the decommissioned assets will have the attribute "DetailLifeCycleStatus" set to a type of decommissioning. This will also recalculate the network attribute NET_MainLifeCycleStatus and set it to the "Decommissioned" phase, ensuring that network tracking no longer takes these assets into account.

 

If assets are dismantled, this can also be documented using the value "Dismantling" in the attribute "DetailLifeCycleStatus."

 

By retaining decommissioned or dismantled lines in the dataset, they remain available for reports and statistics for accounting purposes, or for inquiries regarding the network and assets over time (historical data). The object identification remains intact, so that communication with third-party systems continues to function.

To control the visibility of decommissioned or dismantled assets on the map without increasing the complexity of the map display, a "Layer Filter" functionality is planned for the medium term.

A function for outsourcing and archiving decommissioned/dismantled objects into a simple "Archive Feature Class" is not currently planned as part of product development. The development of such functionality may be considered within the scope of customer projects.