Application configuration

  1. Sign in to portal.itrontotal.com.

  2. Expand Administration > Application configuration.

  3. Select DI Application Config.

  4. Open the App licenses menu and select Location Awareness.

  5. Adjust the following settings as needed:

    • SNR Settings. These settings control how Location Awareness 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.

      • SNR threshold. 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.

      • Minimum SNR for valid phase-shift.

    • Discrepancy Settings. These settings control how Location Awareness determines discrepancies.

      • Enable discrepancy report for orphan meters. Select this check box 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. This is disabled by default, meaning orphaned meters do not appear in the discrepancy report.

      • Enable auto rejecting invalid discrepancies that are no longer valid. Select this check box to enable discrepancies based on old data to be automatically rejected if newer data resolves the discrepancy. This is enabled by default.

      • Minimum GIS Correlation % to create discrepancies. Enter the percentage of meters with a suspected discrepancy that needs to be over this threshold for a discrepancy to be reported. The default value is 60%.

    • Voltage Event Settings. These settings control how Location Awareness processes the voltage events for meter-to-equipment relationships. When the voltage changes at a feeder or substation bank, all the meters that are downstream of the equipment see the corresponding voltage change.

      • 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.

      • ΔV tolerance (volts). 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 0.2 volts.

      • 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 60%.

      • Voltage correlation number of days. The number of days that the voltage event must be experienced. The default value is 9.

      • Setpoint / Bandwidth Ranges.

        • Setpoint (%). Enter the desired setpoint percentage range.

        • Bandwidth (+/- volts). Enter the desired bandwidth (+/- volts).

        • Click Add row to add more rows to Setpoint / Bandwidth Ranges.

        • Click Delete () to delete a row.

    • Configuration Change Request (CCR) Settings. These settings control how Location Awareness 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.

      • Enable CCR submission. Select to enable CCR creation.

      • Update interval (minutes). Enter how often CCRs for SID updates can be sent. The default value is 60 minutes.

      • Maximum requests per run. 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.

      • Batch size. Enter how many meters can be included in a CCR batch. The default value is 100.

      • Update delay (minutes). Enter the number of minutes to delay between message processing and CCR creation. The default is 30 minutes.

    • Startup & Topology.

      • Startup delay (minutes). Enter the number of minutes to delay recovering Location Awareness data after cluster restart. The default is one minute.

      • Topology interval (minutes). Defines how often (in minutes) the platform processes Location Awareness results and updates the topology model. The default value is once per day.

      • UTC midnight offset (minutes). Defines the timing to update the Location Awareness topology model as offset from UTC midnight in minutes. The default value is nine hours, which should leave enough time to interrogate the meters and collect relationship data.

    • Relationship Settings.

      • Missing relationship data maximum days back. The maximum number of days to look back for missing relationship data.

      • Missing relationship data max days back (RF stability). The number of days to look back to calculate RF phase shift stability.

      • Long-drop service drop limit (meters). Enter the distance in meters.

    • Transformer Settings.

      • Transformer process enabled. Select to enable the transformer process.

      • Equipment process enabled. Select to enable the equipment process.

  6. Open the App licenses menu and select Service Point Reference.

    Location Awareness calculates the relative phase shift (in degrees) between service points and service transformers. To translate these relative angles to phase labels that are useful and that can be compared to utility records, locations with a known phase must be established. From the reference service points, Location Awareness can propagate the known phases to the rest of the transformers. For the recommended number of known phases, see Number of phase reference locations.

    1. Click Add row.

    2. Enter the Service Point ID and click Validate. You must click Validate to proceed. If the value entered is not a valid service point, you will not be able to proceed.

    3. (Optional) Enter a Description. A description is useful if you are managing many reference locations in a large service territory.

    4. Select a Phase Angle.

      • If the real-world phase for the service point is known, enter the phase angle that corresponds to the phase label.

      • If the real-world phase for the service point is not known, you can enter an arbitrary phase angle to see how well the value is propagated to the other meters and transformers in the grid.

        Important! If the real-world phase ID is not known, do not select the check box.

    5. Select the Select Label check box to populate the Phase Label value.

      Important! If you are entering a placeholder phase angle when a real-world phase is not known, do not check this box. Not selecting the check box allows you to review phase propagation through the network without creating errant discrepancies with GIS data.

    6. Click Save ().