Configure Tracing

Publishes in Mobile config and Solution Center

Mobile config

ArcFM Mobile tracing allows field crews to identify the parts of the electric or gas system that would be affected if a part of that system needed to be isolated. For electric, tracing indicates the first upstream protective device plus all equipment and customers downstream of that device. For gas, it indicates all connected pipe up to the nearest valves. To use this functionality, tracing settings must first be specified in the Solution Center, and they must be individually specified for each operational map that requires trace functionality. Once specified, the icon in the lower right portion of the Mobile map is enabled. If the icon is not enabled, tracing settings have not been specified. The required fields in Solution Center, regardless of the type of tracing you're performing, must exist and be populated in your geodatabase. For electrical tracing, both the TraceWeight and FeederInfo fields must be configured in Solution Center. For gas tracing, the TraceWeight, SOP In, SOP Out, Distribution Main Layer, and Meter Layer fields must be populated in Solution Center.

Tracing is available for datasets with Feeder Manager configured and with functioning ArcFM traces.

The tracing configuration form changes based on the utility type of the operational map that you select in the first drop-down. If the map service for which you are configuring tracing has the word Gas or Electric in the display name, the drop-down is set accordingly, but you can change that if desired. Additional drop-downs and values are also populated based on the feature service.

IMPORTANT:

Read Configure Gas Tracing or Configure Feeder Manager 1.0 to configure your network for gas or electric tracing.
ArcFM Mobile supports both Feeder Manager 1.0 and Feeder Manager 2.0 but requires FM1.0 fields to be populated. Therefore, if you are using FM2.0, you must have Feeder Sync enabled to populate the applicable FM1.0 fields.

Take it for a drive! (The link opens/switches to the Solution Center app and accesses the Operational Maps tab. Click an operational map on the left, then click Tracing on the right.)

Electric Utility Type:
- TraceWeight Field: contains the field that is designated as the traceweight field in the geodatabase. This field must have the same name across all features in the network.
- Connectivity Tolerance: represents the connectivity tolerance of features in the network. The field respects Esri’s default and automatically detects the correct map units (feet, meters, etc.). If the default is incorrect, you can manually change it.
- FeederInfo: contains the field that is designated as the FeederInfo field in the geodatabase.
- Customer Counting: the method for determining the number of customers affected by an isolation action. Options are:
  - Count loadpoints — count the number of features designated as loadpoints that are affected
  - Count related records — count the number of records that are related to affected loadpoints. If you select this option, you are prompted to select a table from the map service that is related to the loadpoints table and should be used for counting (e.g., Service Address).
  - None — don't count affected customers.
  IMPORTANT: To take advantage of load point counting, the FdrMgrLoadPoint object class model name should be assigned during FM1.0 configuration. Refer to Service Point in the ArcFM Desktop Configuration Guide for more information.
Gas Utility Type:
- TraceWeight Field: contains the field that is designated as the traceweight field in the geodatabase. This field must have the same name across all features in the network.
- Connectivity Tolerance: represents the connectivity tolerance of features in the network. The field respects ESRI's default and automatically detects the correct map units (feet, meters, etc.). If the default is incorrect, you can manually change it.
- SOP In Field and SOP Out Field: contain the SOP In and SOP Out fields for the gas features. These fields must also have the same name across all features in the network.
- Distribution Main Layer: represents the layer in the map service designated as being the Distribution Main in the network.
- Meter Layer: represents the layer in the map service designated as being the meter or service in the gas network.
- Standard Operating Pressure: location in the network where standard operating pressure is referenced. Options are:
  - Field on feature class — standard operating pressure will be determined by a field in the database. If you select this option, you are prompted to select an SOP Field from the map service.
  - Related pressure table — standard operating pressure will be determined by a pressure table. If you select this option, you are prompted to select a Related Layer (SOP table) and an SOP Field on Related Layer.
    
    IMPORTANT: If your organization tracks gas pressures via a related table, you must make the related pressure table setting prior to creating your gas replicas. If this setting is not made first, the gas pressures table is not populated correctly in resulting replicas. You must recreate your replicas if you already have gas replicas and change this setting.
- SOP Unit (psi, bar): an optional text field where you can enter your SOP units.
- Customer Counting: the method for determining the number of customers affected by an isolation action. Options are:
  - Count meters — count the number of meters that are affected
  - Count related records — count the number of records that are related to affected loadpoints. If you select this option, you are prompted to select a table from the map service that is related to the loadpoints table and should be used for counting (e.g., Service Address).
  - None — don't count affected customers.
  IMPORTANT: To take advantage of load point counting, the FdrMgrLoadPoint object class model name should be assigned during FM1.0 configuration. Refer to Service Point in the ArcFM Desktop Configuration Guide for more information.

TIP: If you make changes to the tracing configuration here or in ArcFM, or if you change the region polygon layer used for replica creation, you should recreate all of your replicas to ensure that ArcFM Mobile has current data to perform offline tracing.