Before the Oracle Utilities Network Management System attempts to optimize an area of the network, it checks to see which bellwether meters have had voltages updates within a configurable time period (the default is 15 minutes) since only up to date telemetry will be utilized. Once the list has been received, if any of the telemetered voltage values differ by a configurable percentage from the power flow calculated voltages, the optimization will not be run in that area because there is either a severe power flow data issue or an issue with telemetry accuracy; in either case, the optimization will not be run since the results could have a negative impact on the performance of the feeder. Utilizing only the valid telemetered voltages, the secondary impedance drop is estimated at each of the bellwether locations and used as input into the optimization algorithm. For example, if the solved voltage at a meter is 95 percent of nominal and the telemetered is 94 percent of nominal, the Oracle Utilities Network Management System knows there is a one percent discrepancy between actual and solved. Therefore, when running an objective (such as CVR), the algorithm will ensure that this difference is taken into account when ensuring a particular plan does not create low voltage conditions. The Oracle Utilities Network Management System captures a snapshot of the bellwether voltages before and after plan execution so you can review the results to determine the effectiveness of the plan and to assure you that low voltage conditions were not created.