Add Terminal Configuration (Utility Network Tools)
Summary
Adds a terminal configuration to an existing utility network.
Network features with terminals require constraints that define the valid configuration of the internal connectivity of the device or junction object. This tool allows you to add a new terminal configuration to a utility network that can be assigned to a class at the asset group or asset type level using the Set Terminal Configuration tool.
Usage
Terminals are configured on a device or junction object by assigning a terminal configuration. Only one terminal configuration can be assigned to each of the asset types that support terminals.
The terminals on a feature or object have a directionality setting. They can be set as directional (only one flow direction is permitted) or bidirectional (both flow directions are permitted).
A minimum of two terminals must be specified and a maximum of eight terminals can be specified. The terminal names should be descriptive such as high-side or source-side.
For features with three or four terminals, you can define valid paths. This is designed to handle complex switching devices when you need to constrain the flow paths between pairs of terminals. For example, in a four-terminal device with terminals named A, B, C, and D, you may want to allow flow from A to B and C, but not from A to D.
The network topology must be disabled.
When working with an enterprise geodatabase the following are requirements:
This tool must be connected to the default version to run.
- All other sessions connected to the default version are blocked from running validate or enable operations during the enable operation.
The Input Utility Network parameter value must be from a database connection established as the database utility network owner.
The connected ArcGIS Enterprise portal account must be the portal utility network owner.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Utility Network |
The input utility network to which the terminal configuration will be added. |
Utility Network; Utility Network Layer |
|
Name |
The name of the terminal configuration. |
String |
|
Directionality |
Specifies the directionality of the terminal configuration. A directional traversability model means the flow for the terminal will only go in one direction. A bidirectional traversability model means the terminal allows flow in both directions.
|
String |
|
Terminals (Optional) |
The name and directional flow of each directional terminal. A minimum of two terminals must be specified, and a maximum of eight can be specified. The name of each terminal cannot exceed 32 characters. This parameter is required if the Directionality parameter value is Directional. Value table columns:
|
Value Table |
|
Terminals (Optional) |
The name of each bidirectional terminal. A minimum of two terminals must be specified, and a maximum of eight can be specified. The name of each terminal cannot exceed 32 characters. This parameter is required if the Directionality parameter value is Bidirectional. |
Value Table |
|
Valid Path(s) (Optional) |
The name or names and valid path or paths for the terminal configuration. For bidirectional traversability, this parameter is required if you have three or four terminals. If you are using directional traversability, one of the terminals must be upstream to have valid configurations. Valid paths must be created to indicate which path or paths in a device or junction object are valid for a resource to travel through. Provide a name for each valid path as well as a value. Use the following for the value:
Value table columns:
|
Value Table |
|
Default Path (Optional) |
The default path of the valid configurations. This will be assigned to new features that have this terminal configuration assigned to their asset type. If no valid paths have been specified, the default path All will be used.
|
String |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Updated Utility Network |
The updated utility network. |
Utility Network |
Environments
This tool does not use any geoprocessing environments.
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes