Editing the application settings in the Admin Portal

For more information about the DI App Platform Admin Portal, see the Itron Analytics Admin Portal Help.

In the Itron Analytics Admin Portal, expand Application Settings and click Electric.
Click the Location Awareness tab.
Edit the settings as needed.
1. Under Scheduler, the settings control when and how often the DI App Platform processes results from the location awareness agents. By default, results are processed once per day. For testing purposes, these settings can be changed to process results more frequently. However, in a production environment, more frequent processing does not have an advantage because the location awareness agents typically send relationship models once per day.
  1. Last Scheduler Run Time displays the last time the DI App Platform processed location awareness results.
  2. In Start Date/Time, enter or use the calendar and clock icons to define when the DI App Platform processes the location awareness results. Leaving this blank causes the process to run immediately.
  3. In Frequency, define how often the DI App Platform processes location awareness results. The default value is once per day.
    1. Enter a value for the frequency.
    2. Select a time duration (Minutes, Hours, or Days) from the menu.
2. Under Scheduler settings, the settings control how much location awareness agent data is stored by the DI App Platform and how far back into that data the DI App Platform looks to present results.
  1. In Maximum historic days, enter how many days of historical location awareness results the DI App Platform processes from the location awareness agents. The default value is 10 days.
    
    Recommended (for large utilities only): 3 days
  2. In Missing relationship data maximum days back, enter how many days back the DI App Platform looks for results from missing relationships. For example, if a service point is missing from the location awareness agent's results, the DI App Platform looks at the historical data for this number of days. If it finds a relationship for this service point in the historical data, the DI App Platform assumes that the service point's absence is due to a temporary communication issue and presents the service point in its last known relationship. If it does not find a relationship for this service point in the historical data, the DI App Platform assumes that the service point's absence is intentional and presents the service point without a relationship. This setting only applies to devices with no data- if a device shows up in a different place in the architecture, the DI App Platform changes the relationship right away. This setting is balanced so that missing devices are correctly identified quickly while allowing for temporary communication issues. The default value is 3 days.
  3. In Relationship data retention days, enter how many historical days of location awareness data the DI App Platform stores. This setting must be balanced to control the size of the database. The default value is 30 days.
    
    Recommended (for large utilities only): 5 days
3. Under SNR settings, the settings control how the DI App Platform processes the signal-to-noise ratio (SNR) for meter-to-transformer relationships. Devices on different transformers typically have a low SNR, while devices on the same transformer typically have a high SNR. If two devices have a SNR above the threshold, they are assumed to be on the same transformer.
  1. Select the Enable dynamic SNR threshold checkbox to enable a feature that adjusts the SNR threshold individually for each device to improve results. The default value is enabled.
    
    Recommended: disabled
    
    Important! Do not enable this setting. Its performance is not yet validated.
  2. In SNR threshold, enter the SNRx10 threshold to check for discrepancies in relationships. Increasing this value increases the strictness for which devices are considered neighbors. Valid values are integers from 0 to 255. The default value is 60.
    
    Recommended 130
4. Under Discrepancy settings, the settings control how the DI App Platform determines discrepancies.
  1. Select the Enable discrepancy report for orphan meters checkbox to enable orphaned meters to appear in the discrepancy report. An orphaned meter is a meter that is assigned to a transformer but is not considered a peer of other meters on that transformer. The default value is disabled, meaning that orphaned meters do not appear in the discrepancy report.
  2. Select the Disable discrepancy report for phase discrepancies with missing DEH checkbox to prevent Location Awareness from reporting discrepancies for service points that are missing DEH phase assignments. The default for this checkbox is selected (phase discrepancies for missing DEH are disabled).
  3. Select the Enable auto rejecting discrepancies that are no longer valid checkbox to enable discrepancies based on old data to be automatically rejected if newer data resolves the discrepancy. The default value is enabled.
  4. In Minimum GIS Correlation % to create discrepancies, enter the minimum percentage of meters that have a correct transformer assignement so that discrepancies can be reported with sufficient confidence. If the GIS correlation percentage is less than the threshold set in the Admin Portal, two dashes (--) are shown for the Transformer ID in the Location Awareness user interface. The default value is 60%.
5. Under Voltage event settings, the settings control how the DI App Platform processes the voltage events for meter-to-equipment relationships. When voltage changes at a feeder or substation bank, all meters downstream of the equipment see the corresponding voltage change.
  1. In Allowed time shift threshold (seconds), enter the allowable change in voltage event timing (in seconds) to be considered the same voltage event across the equipment and the meter. For example, if an equipment experiences a voltage event, and a meter experiences a similar voltage event within this amount of time, they are considered a valid relationship. The default value is 15 seconds.
  2. In DeltaV tolerance (Volt), enter the allowable change in voltage event size (in voltage units) to be considered the same voltage event across the equipment and the meter. For example, if an equipment experiences a voltage event, and a meter experiences a similar voltage event within this size (above or below), they are considered a valid relationship. The default value is 2 voltage units.
  3. In Voltage correlation threshold, enter the percentage of voltage events that must be experienced by all meters assumed to be on the same equipment. The default value is 70%.
  4. Voltage correlation number of days. The default value is 1.
    
    Recommended: 8
  5. Voltage correlation minimum DeltaV threshold. The default value is 19.
    
    Recommended: 14
  6. Voltage correlation maximum DeltaV threshold. The default value is 50.
    
    Recommended: 16
6. Under Configuration change request (CCR) settings, the settings control how the DI App Platform manages short IDs (SID) for devices. Although devices are typically identified by their MAC address, location awareness uses SIDs because they are three bytes of data instead of the MAC address' eight bytes. The SID is assigned by the back office through a configuration change request (CCR) and sent to the device via configuration management system (CMS). SIDs are location based, so if a device is moved, then it gets a new SID.
  
  Important! Do not change these settings.
  1. In Update interval (minutes), enter how often CCRs for SID updates can be sent. The default value is 60 minutes.
  2. In Maximum limit for update interval, enter the maximum number of CCRs that can be sent in the update interval. For example, if this is set to 10,000 and the Batch size is set to 100, then it will allow 100 batches of 100 CCRs (100*100=10,000). The default value is 10,000.
  3. In Batch size, enter how many meters can be included in a CCR batch. The default value is 100.
7. Select the Enable automatic updates to transformer/service point connections checkbox to enable Itron Analytics to automatically update transformer-to-service point hierarchy definitions that meet enabled and defined prerequisites. The default setting is enabled.
  
  The recommended setting is disabled.
  
  If the Enable automatic updates to transformer/service point connections checkbox is selected, the following additional settings appear under the Automatic update criteria section:
  1. Select the Service length less than (ft) checkbox and enter a distance in feet to enable this criterion for automatic updates. Valid values are integers from 1 to 10,000. The default value is 300.
  2. Select the Ratio service length/median service length less than checkbox and enter a ratio to enable this criterion for automatic updates. This is comparing the ratio of the service length for the service point and the suggested transformer and comparing it to the median service length of all other service points on the suggested transformer. Valid values are numbers with up to two decimal places from 0 to 1,000. The default value is 3.00.
  3. Select the Distance to median service point location less than (ft) checkbox and enter a distance in feet to enable this criterion for automatic updates. This is comparing the location of the service point to the averaged location of all other service points on the suggested transformer. Valid values are integers from 1 to 10,000. The default value is 200.
  4. Select the Maximum service points per transformer less than checkbox and enter a service point count to enable this criterion for automatic updates. Valid values are integers from 1 to 1,000. The default value is 20.
Click Update.