Interview Questions for UNM model
1) What is Utility Network ?
Answer:
• A utility network is set of tools to manage utility and telecom networks in ArcGIS-Pro,providing a comprehensive framework of functionality for the modeling of utility
systems such as electric, gas, water, storm water, wastewater, and telecommunications.
• The utility network delivers advanced asset modeling capabilities, a modern webGIS architecture, and analysis tools.
• The utility network also serves as a centralized system of record that can be
accessed by everyone at the utility on any device at any time.
• The utility network enables utilities to model the location of assets, including the
modeling of internal configurations of complex assemblies such as pump houses,
meter pits, and valve assemblies.
2) What is Structure network?
Answer: When a utility network is created, a common domain network named the
structure network is included to be shared across different domain networks. Utilities
commonly carry more than one type of resource on a common set of structures. For
example, a pole may support electric lines, telecommunication wires, and cable lines.
Similarly, a duct bank may carry many types of utility resources. Sharing a structure
network among multiple domain networks eliminates redundancy and allows you to
better track joint usage on poles and ducts.
3) What are feature Classes in a structure network?
Answer: The structure network consists of three feature classes and two
tables: StructureJunction, StructureLine, StructureBoundary, Structur
eJunctionObject, and StructureEdgeObject.
These classes are created with system-provided attribute domains assigned to system fields for use by the utility network and require additional configuration for use.
4) What is Domain networks?
Answer: Each utility network can contain one or more domain networks. We might create multiple domain networks for different levels of the same utility resource,
such as distribution and transmission levels of gas, water, or electricity. Or we might
add domain networks if your organization has multiple types of services, such as
natural gas and electricity.Each of these domain networks will share the same structure network so that we can find the devices and lines in our domain networks that are supported by common structures.
Domain networks contain the network features through which our delivered
resource flows. There are five types of features in a domain network: lines through
which a resource flows; devices that control the flow of that resource; junctions
placed where features are connected; assemblies representing collections of lines,
junctions, and devices; and subnetwork lines that define the extent of resource flow.
5) What are feature Classes in a domain network?
Answer: Each domain network consists of five feature classes and two tables that are
created when you add a domain network: Device, Line, Junction, Assembly, SubnetLine, JunctionObject, and EdgeObject. These classes are created with system-provided attribute domains assigned to system fields for use by the utility network and require additional configuration for use.
6) What is Asset Group and asset type in Utility network?
Answer:
Asset Group
•The asset group attribute represents the major classification of utility features.
•The Asset group field is the subtype field of all feature classes in the structure
network and domain network, with the exception of the SubnetLine class.
•Subtype values are established to define the major classification of our assets.
Asset Type
• The asset type attribute represents the minor classification of asset group types.
•The Asset type field is implemented as a set of attribute domains that are assigned
at the subtype level for each asset group.
7) What is difference between Geometric Network Vs Utility Network?
Answer: The difference between a Geometric Network and a Utility Network
lies in their capabilities and use cases within geographic information systems
(GIS). Here’s a brief comparison:
Geometric Network:
• Basic and Reliable: Geometric networks are well-established in GIS and
are used for simpler network structures.• Structure: Consists of nodes (like valves or junctions) and edges (like
pipes or lines) with defined connectivity rules.
• Suitable for Simple Networks: They work well for networks with
straightforward connectivity and less complexity.
• Challenges: Updating geometric networks can be difficult, especially
when dealing with changes to connectivity rules or network components.
They also lack flexibility for more complex utility networks.
Utility Network:
• Advanced and Dynamic: Utility networks are designed to handle the
demands of modern utilities with more complex and dynamic behaviors.
• Components: Includes asset packages, network containers, and
associations for comprehensive modeling of utility networks.
• Real-time Capabilities: They support real-time asset condition tracking,
predictive analysis, and network scenario simulations.
• Flexibility: Utility networks offer advanced features, live updates, and
the flexibility needed for complex networks1.
In summary, while geometric networks are suitable for managing simple and
static utility networks, utility networks are the future, offering a more
scalable, flexible, and feature-rich solution for complex and dynamic utility
management.
8) What is the difference between UPDM, the Utility Network, and ArcGIS Pro?
Answer: At a high level, the UPDM (Utility and Pipeline Data Model) is a
data model that defines the structure (tables, fields, domains, etc.) of
geospatial data and objects (e.g., pipes, conductors, transformers, and
valves). The Utility Network defines the connectivity relationships among
objects and the flow of gas/electricity/water from one place to another
within a network. ArcGIS Pro is the desktop GIS software for creating,
configuring, and managing both the UPDM and the Utility Network.
9) Is ArcGIS Pro required to use the Utility Network?
Answer: Yes. ArcGIS Pro is needed for managing and editing Utility Network
data. It has many functions that leverage the power of the Utility Network,
including the ability to author attribute rules, configure the network, and
implement advanced functionality such as network associations. It is
designed specifically to manage and edit service-based GIS data and work
with the new branch versioning architecture.
10) What are the benefits of implementing the Utility Network?
Answer: The many benefits of implementing the utility network include
streamlined workflows, scalable models, robust system modeling, real-time
integrations and out of the box data reporting through network validations.
11) Can the Utility Network only be viewed and edited through services?
Answer: For all intents and purposes, yes. Esri recommends accessing
Utility Network data exclusively from an enterprise geodatabase via REST
services. However, there is an option to use file geodatabases to support
the Utility Network with the ArcGIS Pro 2.5 release which could be used in
some use cases.
12) Can tracing be done via the Utility Network services?
Answer: Yes! One of the benefits of the Utility Network is that tracing and
automation (e.g., Attribute Rules) are exposed via REST services.
13) What is the difference between Utility Network and Trace Network in
ArcGIS Pro?
Answer: The Trace Network supports flow direction and is more geared
towards use in something like a river network. The Utility Network is more
robust and can handle complex features found in utility networks (terminals
on features, structure attachments, subnetworks, etc.).
14) What is Branch Versioning and how does it work with the Utility Network?
Answer: Branch versioning is the only versioning type available for the
Utility Network. It is similar to traditional versioning, allowing for multiple
simultaneous editors. However, it is designed specifically for editing via
services. In addition, it has a more flat structure, simplifying
administration.
15) What is an association in the Utility Network?
Answer: Associations in the Utility Network allow for features that are not
geometrically coincident to share a relationship and participate in the network
validation tools. Associations are useful both for relating objects that don’t
participate in the network “flow” (for example a structural attachment
association of a transformer to a pole) and for accommodating incomplete
data (for example a network association where a meter is connected to a
main, but the service line has not yet been mapped).
16) How do containers work?
Answer: A container is a type of association (a containment association),
where features are physically (or virtually) inside another feature. A
common example of a container is a station (pump station, regulator
station, substation) which can be represented as a single map feature. This
feature can be “drilled into” to enable viewing of all the station details
(pumps, valves, voltage regulators, etc.).
17) What steps can my organization take to prepare for Utility Network
Migration?
Answer: The most important Utility Network preparation is to confirm that
your data is ready. The UN has specific requirements for network
connectivity and topology. It is important to understand what updates
need to be made either before or during the data migration. Furthermore,
we should confirm that features are snapped and free of overlaps – which
will cause network “dirty” areas and limit tracing capabilities. The number
of dirty areas can be reduced via tools designed to prepare data for a Utility
Network build. Additionally, we should establish a logical naming
convention for subnetwork controllers. Finally, it is important to plan for a
service-based GIS, including any needed upgrades to your GIS
infrastructure, including Portal and ArcGIS Server.
18) What is Dirty Areas?
Answer:
•Dirty areas are created to flag areas where edits have been made against
feature geometry and network attributes, or where error features exist in the
network
•They serve as an indicator that a change to the network has taken place that
is not reflected in the network topology
•Dirty areas are cleared when the network topology is validated as long as no
error features exist within the validation extent
•Dirty areas track the extent of the feature that is edited, the type of edit, the
global ID of the feature, and the editor who performed the operation.
19) Can the service territory feature class be updated?
Ans: There is not currently a tool that allows the service territory to be updated. The options available to account for this are:
-> Make the initial service territory slightly larger than your intended work area to account for potential growth. Keep in mind that network features can be created anywhere within the service territory extent.
-> Use the Utility Network Package tools to export the current utility network configuration to an asset package, stage the utility network using the modified service territory, and reimport the network configuration using the asset package.
20) Can I change an Asset Group or Asset type in the utility network?
Ans: The asset group field is assigned as the subtype field for network feature classes and serves as the major classification for network assets. You can configure additional asset groups by disabling the network topology and adding new code/description subtypes. Existing subtypes cannot be altered or removed, and the subtype field cannot be changed for the feature class.
The asset type field is configured using attribute domains to represent the minor classification of network assets. You can configure additional asset types by disabling the network topology and adding new code/description pairs for the coded value domain. Existing coded value domain code/descriptions cannot be modified, and the domain cannot be deleted.
21) What is the maximum number (max code) for an Asset group subtype and an Asset type domain?
Ans:The code limit for the asset group and asset type allowed is 1024. This means asset group subtypes and asset type domains can be created with codes as high as 1023.
The asset group and asset type fields are used by a utility network for feature classification. These represent the major and minor classification for utility features. To support this, subtypes and coded value attribute domains are configured for these fields. These are stored internally in the network topology as In Line network attributes.
Note - The attribute domain associated with the asset type field must have a field type of short integer.
22) How can I create my own empty asset package?
Answer: The easiest way is to create a new utility network (and domain networks, if necessary) is to export it to an asset package.
23) How do I rename a domain network in the asset package?
Answer: To rename a domain network in an asset package, you'll need to update two items in the asset package. First, update the description of the domain network in the AP_DomainNetworks attribute domain. Be sure to update just the description. Do not change the coded value. Second, rename the prefix on the domain feature classes (Assembly, Device, Junction, Line, and SubnetLine) in the UtilityNetwork dataset of the asset package. If you have attribute rules, you'll also need to update the Input Table name in the B_AttributeRules table.
This is only for domain networks in the asset package; structure networks cannot be renamed.
Important Links:
https://www.esriuk.com/en-gb/arcgis/products/arcgis-utility-network/resources
https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/work-with-a-utility-network.htm
https://www.locana.co/un-connectivity-associations/
https://mediaspace.esri.com/media/t/1_ycdaq1go
https://mediaspace.esri.com/media/t/1_nl5m6g2p/309413912
https://sspinnovations.com/blog/esri-utility-network-modeling-device-terminals/
No comments:
Post a Comment