Utility Network Structures

Our comprehensive guide provides a deep dive into the complex world of utility network structures, delineating their key components across Structure and Domain Networks. Whether dealing with spatial data that maps the physical layout or non-spatial data that catalogs the attributes, this guide outlines the crucial elements that form a utility network, including lines, junctions, boundaries, and various objects. This resource is designed for professionals in urban planning, civil engineering, and GIS, offering clear insights into the interconnected nature of utility systems and the data that supports efficient network management.

Edited at 2022-04-04 11:34:42

mayadagh97@gmail.com

Recent works View more works>>

Utility Network Structures

mayadagh97@gmail.com

Recent works View more works>>

Recommended to you
Outline

Duplicate
link engine management
- 555
- 4
- 2
- 0
Oliveettom
Duplicate
webinar contemplanda
- 432
- 2
- 4
- 3
Oliveettom
Duplicate
Continuous Mining Machine Operators Summary Report
- 186
- 1
- 1
- 0
Ashley
Duplicate
Electricians Summary Report
- 1.4k
- 4
- 21
- 2
Ashley
Duplicate
ISO IEC 27001 2013 PIE FARM METHODOLOGY
- 503
- 4
- 7
- 0
Lisa Anderson
Duplicate
Help Desk Testing Scenarios
- 390
- 1
- 5
- 0
Lisa Anderson
Duplicate
Operating System Structure
- 5.5k
- 144
- 39
- 2
Lisa Anderson
Duplicate
Operating System and Utility Programs
- 737
- 4
- 8
- 1
Lisa Anderson
Duplicate
Security Controls
- 490
- 7
- 4
- 0
Captain O Captain
Duplicate
ArchiCAD Improvements
- 514
- 3
- 13
- 0
Lisa Anderson

Utility Network Structure

Manage Utility and Model Utility System Components {Gas , Water , Electricity , Telecomunications}. Create / Analyze / Validate / Trace utility system

Structure Network

A structure network does not have any resources (such as water or electricity) flowing through it; however, the structure network can contain other features that are part of the resource-delivering network. For example, a vault (which is a structure) can contain valves and regulators (part of the active network). Every Structure can facilitate the flow , but not directly deal with the flow. Like the Transformer : has no flow but it facilitate the flow. Only one Structure Network , can be shared accross different Domain Networks. A Pole may support electric lines, telecommunication wires, and cable lines. Duct bank may carry many types of utility resources.

Spatial Data

"Spatial Data" == "Feature Classes" == "Layers" :- Everything can be modelled as a feature and can be clearly seen on the map "Assembly"

Line

Represents linear features such as trenches and duct banks.

Junction

Represents structural point features such as poles, pads, vaults, and cabinets

Boundary

Represents polygon container features such as "outline of a substation" == "Area".

Non-Spatial Data

"Non-Spatial Data" == "Tables" :- Everything can't be clearly seen on the map because of its large number "Fibres"

Junction Object

Represents junction objects such as racks or ports.

Edge Object

Represents edge objects such as a trench or duct bank. There is "edge object Trench" and there is a "Line Feature Trench" ->> The number and the ability of modelling it on the map.

Domain Network

Each utility network can contain One or more domain networks for each type of utility service that your organization serves. You might create multiple domain networks for different levels of the same utility resource, such as distribution and transmission levels of gas, water, or electricity. Each of these domain networks will share the same structure network so that you can find the devices and lines in your domain networks that are supported by common structures. Domain networks contain the network features through which your delivered resource directly flows.

Spatial Data

"Spatial Data" == "Feature Classes" == "Layers" :- Everything can be modelled as a feature and can be clearly seen on the map "Assembly"

Device

Control the flow of that resource. Represents point features such as valves, meters, transformers, and switches. Devices can optionally have terminals when there are distinct entry points to the device.

Line

Through which a resource flows. Represents linear features such as wires and pipes.

Junction

Junctions placed where features are connected. Represents locations where lines connect to lines or lines connect to devices.

Assembly

Assemblies representing collections of lines, junctions, and devices. Represents point features that contain other features. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. You can view the internal features of an assembly on the map or in the diagram view. Examples of assembly features are switchgear, transformer banks, and pump assemblies.

Sebnetline

Subnetwork lines that define the extent of resource flow. A collection of subnetwork lines that define the current extent of a resource flow. For water or gas utilities, subnetworks are called pressure zones. For electric utilities, subnetworks are called circuits or feeders. Subnetworks are not directly edited like the other features in a domain network. Rather, they are generated by a command to update subnetworks. This command traces the flow of a resource from a subnetwork controller (such as a substation or water tank) through all the devices and lines until either that resource is consumed or the flow is blocked by an interrupting device such as a switch or valve. Because of switching devices, subnetworks frequently change and can be quickly regenerated on demand.

Non-Spatial Data

"Non-Spatial Data" == "Tables" :- Everything can't be clearly seen on the map because of its large number "Fibres"

Junction Object

Represents nonspatial junction objects such as racks or ports that are contained or associated with other network features. Junction objects can optionally have terminals when there are distinct entry points for the object.

Edge Object

Represents nonspatial edge objects such as fibers in a cable.