VEE Recommendations

  • The High-Low VEE Rule is very “heavy” in terms of performance. This rule has an intensive hit on performance of the Initial Measurement loading process. Customers are encouraged to use the Usage High-Low rule, which has a less significant performance impact. If the VEE rule version is being used, the historic pre window should be set as low as possible based on business needs.
  • Each VEE Rule included in VEE processing can have an impact on overall performance. The table below summaries the relative costs in terms of performance for several commonly used VEE Rules. Using this table when designing your VEE groups and rules can help identify potential performance challenges.
  • For example, using "Minimal Impact" rules will likely have little to no significant impact on performance, while using several "Moderate Impact" rules could result in performance challenges, and using the High Low Check rule is very likely to introduce noticeable impacts to VEE processing performance.

Relative Cost

VEE Rules

Minimal Impact

(0% - 5%)

Interval Interpolation

Interval Replacement Rule

Interval Size Validation

Interval Spike Check

Negative Consumption Check

Scalar Replacement Rule

UOM Check

Moderate Impact

(5% - 20%)

Final Measurement Validation

Interval Adjustment From Scalar

Interval Averaging

Multiplier Check

Scalar Calculation From Interval

Scalar Proration

Sum Check

Significant Impact

(20%)

High/Low Check
  • Consumption sync processes should only be run on devices where the difference in consumption is outside the defined tolerance as dictated by the sum check tolerance. In a production environment, running consumption sync for two percent of devices or less is advisable.
  • For cloud implementations, custom rules must be written using Groovy or Oracle Utilities Application Framework scripting.
  • Run performance testing on all configuration changes performed that impact portions of Oracle Utilities Meter Data Management with high transactional processing.
  • Any VEE Rules, whether provided as part of base product or custom developed, should be configured to query no more than 30 cumulative days of historical data (i.e. High/Low) to help optimize the data loading process
  • A good way to troubleshoot a VEE Rule is to use the Trace section of the IMD Log. When an IMD is in Pending status, the Trace On button can be used to trace all VEE Rules fired during IMD processing. Once processing is complete, view the Log tab of the IMD and review the results in the IMD Trace Log section. For any custom developed VEE Rules, the average run time should be no longer than the average run time of other base product VEE Rules. Also, the impact of different configuration can be checked through this method as well.

  • Load initial measurements and perform VEE processing every 4 to 6 hours to optimize performance.