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.

To configure the application to generate service investigative orders for revenue protection, you should perform the following tasks:

Set up VEE rules to look for low usage: VEE rules are used to validate, estimate, and edit measurements based on certain criteria. You can set up VEE rules to look for low usage patterns that may indicate theft or meter malfunction.

Configure service task type to look for Validation, Estimation, and Editing (VEE) exceptions, device events, and failed commands: Service task types are used to define the types of work that need to be performed on devices or service points. You can configure service task types to look for VEE exceptions, device events, and failed commands that may indicate theft or meter malfunction. You can also configure service task types to trigger service orders when these conditions are met.

Import device events related to theft: Device events are occurrences that happen on devices, such as tampering, reverse energy flow, or magnetic interference. You can import device events related to theft from smart meter systems using the Smart Grid Gateway or other integration methods.

You do not need to tune the AI engine to look for theft by using theft algorithms or configure case management. These are features of Oracle Utilities Revenue Protection Cloud Service, which is a separate product from Oracle Utilities Meter Data Management.

Derived values are values that are calculated from raw measurements based on certain rules or factors. Derived values can be used for different purposes, such as billing, analysis, or reporting. Some examples of derived values are:

Value with a factor such as line loss applied: This is a value that is adjusted by applying a factor that accounts for the loss of energy or water during transmission or distribution. For example, a line loss factor can be applied to a meter reading to calculate the actual amount of energy or water that was delivered to a customer.

Value converted from one unit of measurement to another: This is a value that is converted from one unit of measurement (UOM) to another based on a conversion factor. For example, a volume reading in cubic feet can be converted to a volume reading in gallons by multiplying it by a conversion factor.

Interval data values created by ''intervalizing'' a scalar reading by applying a profile to it: This is a value that is created by dividing a scalar reading into smaller time intervals based on a profile that represents the usage pattern of a customer. For example, a daily scalar reading can be intervalized into hourly readings by applying a load profile that reflects the customer's hourly usage.

Estimated value if the final measurement is too low or high is not a derived value, but an estimated value. Estimated values are values that are generated when raw measurements are missing or invalid based on certain criteria. Estimated values can be based on historical data, statistical methods, or other sources.

Comparison of normal versus actual usage is not a derived value, but an analysis result. Analysis results are values that are calculated by comparing or aggregating measurements or derived values for different purposes, such as revenue protection, load research, or customer engagement.

The Subtractive Interval Data functionality is a feature that enables Meter Data Management (MDM) to process interval data from devices that do not provide interval readings, but only cumulative readings. The Subtractive Interval Data functionality performs the following actions:

The IMD load processes calculate consumption in engineering units: The IMD load processes are batch processes that load initial measurement data (IMD) records from smart meter systems or other sources into MDM. The IMD load processes calculate consumption in engineering units by subtracting consecutive cumulative readings and applying conversion factors.

A new reading condition field ensures that you do not lose the reading quality when a meter's consumption is estimated: A reading condition field is an attribute that indicates the quality or status of a measurement, such as valid, invalid, estimated, or substituted. A new reading condition field called Original Reading Condition is added to store the original reading condition of a cumulative reading when its consumption is estimated by using VEE rules.

You can optionally validate for rollover exceptions and negative consumption calculations: You can configure VEE rules to check for rollover exceptions and negative consumption calculations when processing subtractive interval data. A rollover exception occurs when a cumulative reading reaches its maximum value and resets to zero. A negative consumption calculation occurs when a cumulative reading decreases instead of increasing.

It is not true that it validates consumption in initial measurement data (IMD), which are records that store the raw measurement data that is received from smart meter systems or other sources. Subtractive Interval Data functionality does not validate consumption in IMD, but calculates consumption from cumulative readings.

It is not true that it converts engineering units into reads, which are values that are recorded by devices at certain intervals or events. Subtractive Interval Data functionality does not convert engineering units into reads, but calculates consumption in engineering units from cumulative readings.

Usage transactions can contain date breaks, which are dates that divide a usage period into sub-periods based on certain criteria or events. Date breaks are used to supply date breaks for usage transactions. Date breaks are specified by the requesting system or user input when requesting a usage transaction. A requesting system is an external system or service provider that requests bill determinants from MDM. A user input is a manual entry of data by a user.

Usage subscription BO is not used to supply date breaks for usage transactions. A usage subscription BO is a business object that defines the relationship between a service point and a subscribing system.

Usage subscription type is not used to supply date breaks for usage transactions. A usage subscription type is a configuration that defines the properties and rules for a usage subscription.

Deferred monitor calculation algorithm is not used to supply date breaks for usage transactions. A deferred monitor calculation algorithm is a custom logic that can be developed by using Groovy scripting language or Java programming language. A deferred monitor calculation algorithm is used to perform certain calculations or validations on usage transactions after they are created.