Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>These are compact features through which your utility resource flows and devices can affect your resource in several ways. Devices can optionally have terminals when there are distinct entry points to the device. Devices can be connected to other devices, junctions, and lines. Devices can be contained within assemblies.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Assembly feature class represents complex point features which contain other devices and lines. Like device features, assembly features are compact features but they differ in that assemblies contain other significant devices. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. Assemblies can contain devices, lines, and junctions. You can view the internal features of an assembly on the map or in the diagram view.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Junction class represents locations where lines connect to lines or lines connect to devices. A key use for junction features is to allow devices or lines to connect to another line at an intermediate vertex. You can think of a junction as 'glue point' at key places to connect all the features of a utility network. Junctions can be contained within assemblies.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Structure Junction feature class represents compact features which are tracked in a utility's asset inventory system. A structure junction can be either a structural feature that a device is attached to or a container of devices.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Line feature class represents linear features. These are the lines which deliver your utility resource. Lines can be connected to other lines, junctions, and devices. Lines can be contained within assemblies.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Structure Line contain lines which carry a resource. Structure lines participating as containers can contain other structure lines.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The SubnetLine feature class is a collection of subnetwork lines which define the current extent of a resource flow. Subnetworks are not directly edited like the other features in a domain network. Rather, they are generated by tracing the flow of a resource from a source (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 like a switch or flow. Because of switching devices, subnetworks frequently change and can be quickly regenerated on demand. The subnetwork line feature class is updated with a tool to update subnetworks and each subnetline is the aggregate of all the line features within a subnetwork.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>The Structure Boundary feature class represents features whose outline should be display on a map view or container view. Structure boundaries can contain structure edges, structure junctions, devices, lines, assemblies, and junctions.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Service Territory is used to ensure that features are not accidentally added outside the area that a utility serves.</SPAN></P></DIV>