Most Recent Oracle 1Z0-1091-22 Exam Dumps

Usage calculation groups are used to define how usage data are calculated, validated, and exported for different purposes, such as billing, settlement, or analysis. Usage calculation groups can have different components that specify the logic and parameters for performing various operations on usage data. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of components that can be configured in usage calculation groups are:

CIS rates: These are rate schedules that are defined in the customer information system (CIS) and imported into Oracle Utilities Meter Data Management. CIS rates can be used to specify which bill determinants or usage calculations should be applied for different rate schedules or customer classes.

Bill determinants or usage validations: These are rules that check the quality or accuracy of usage data and assign condition codes or flags to indicate any issues or errors. Bill determinants or usage validations can be used to ensure that usage data meet certain criteria or standards before they are exported to CIS or other systems.

Bill determinants or usage calculations: These are rules that perform various calculations or adjustments on usage data, such as dividing usage into time-of-use periods, applying factors or multipliers, or deriving net usage. Bill determinants or usage calculations can be used to generate different types of bill determinants for billing purposes.

The base Meter Data Management (MDM) product provides several Validation, Estimation, and Editing (VEE) rules that you can include in a VEE group. A VEE group is a collection of VEE rules that are used to validate, estimate, and edit measurements based on certain criteria. Some of the VEE rules that are provided by the base MDM product are:

Positive consumption check: This is a rule that checks if the consumption value of a measurement is positive. If the consumption value is negative, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.

Negative consumption check: This is a rule that checks if the consumption value of a measurement is negative. If the consumption value is positive, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.

High/low check: This is a rule that checks if the consumption value of a measurement is within a predefined range. If the consumption value is above or below the range, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.

Estimate data based on nearby addresses is not a VEE rule that is provided by the base MDM product. This is a custom VEE rule that can be developed by using Groovy scripting language or Java programming language.

Interval averaging is not a VEE rule that is provided by the base MDM product. This is a usage calculation rule that is used to calculate derived values from interval measurements by averaging them over a certain period.

A usage subscription is a record that defines how usage data are collected, processed, and exported for a service point or a device. A usage subscription can have various components that specify the logic and parameters for performing various operations on usage data, such as validation, estimation, editing, calculation, or export. According to the Oracle Utilities Meter Data Management Business User Guide, one example of a component that can be configured in a usage subscription is:

Eligibility criteria: These are rules that determine whether a usage subscription generates a usage transaction or not. A usage transaction is a record that contains usage data that are ready for export to other systems, such as customer information system (CIS) or settlement system. Eligibility criteria can be used to filter out usage subscriptions that do not meet certain conditions or requirements for generating usage transactions.

Different validation, estimation, and editing (VEE) rules can be applied based on the VEE roles that categorize the source of the measurement data. A VEE role is an attribute that indicates how measurement data was created or modified. Some of the VEE roles that are provided as part of the base product are:

Manual override: This is a role that indicates that measurement data was manually entered or edited by a user.

Initial load: This is a role that indicates that measurement data was loaded from an external source or system.

Customer provided: This is a role that indicates that measurement data was provided by a customer.

Retry is not a VEE role that is provided as part of the base product. Retry is an action that can be performed on measurement data that has failed VEE rules.

Estimation is not a VEE role that is provided as part of the base product. Estimation is a process that can be performed on measurement data that is missing or invalid by using VEE rules.

An activity type is an Oracle Utilities Application Framework (OUAF) admin data that should be created for a custom Service Order Management process. An activity type defines the type of work that needs to be performed on a service point or device, such as enable service or disable service. An activity type also defines the following attributes:

The status and priority of the activity

The business object and algorithm that are used to process the activity

The fields and validations that are required for the activity

The notifications and escalations that are triggered by the activity

The dependencies and relationships that exist between different activities

An activity type is used to create and manage service orders, which are records that store the details and outcomes of the work performed on a service point or device.