Curious about Actual Oracle Cloud (1Z0-1091-22) Exam Questions?

Correct : B

A time-of-use (TOU) group is a set of TOU maps that define how usage is divided into different TOU periods for different days of the week and seasons of the year. A TOU group can have a work calendar associated with it to define holidays and other special days that may have different TOU periods than regular days. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, to configure a TOU group for ''on peak'', ''off peak'', and ''shoulder'' periods and have holiday consumption categorized as ''off peak'' regardless of the day on which it falls, the correct steps are:

Add the work calendar to the TOU map template and set the Holiday TOU as ''off peak''. This will ensure that any day marked as a holiday in the work calendar will have its usage assigned to the ''off peak'' period.

Create a TOU map for each season using the TOU map template and define the start and end times for each TOU period (''on peak'', ''off peak'', and ''shoulder'') for each day of the week.

Create a TOU group and add the TOU maps for each season to it.

Correct : A, B, C

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.

Correct : B, C, E

To support the requirement of replacing legacy scalar time-of-use (TOU) meters with smart meters without changing the CIS rates, you can configure Meter Data Management (MDM) in the following ways:

Add an extendable lookup value containing the new device configuration type and the new usage calculation group: This is used to map the new device configuration type that is used for smart meters to a new usage calculation group that will be used to calculate bill determinants for smart meters. An extendable lookup value is a configurable value that can be used to define business rules or relationships between different objects.

Add the TOU mapping rule to the existing usage calculation group: This is used to map the TOU periods of smart meters to the TOU periods of legacy meters. A TOU mapping rule is a usage calculation rule that is used to convert interval measurements into scalar measurements based on different TOU periods.

Set up the new usage calculation group to be identified dynamically by plug-in logic supplied on the usage subscription's type: This is used to determine which usage calculation group will be used for each usage subscription based on certain criteria, such as device configuration type or service point type. A plug-in logic is a custom logic that can be developed by using Groovy scripting language or Java programming language.

You do not need to write a custom algorithm to determine the proper rate, which is a complex logic that can be developed by using Groovy scripting language or Java programming language. The proper rate can be determined by using the existing CIS rates and mapping them to smart meter TOU periods.

You do not need to add a new usage calculation group with a TOU mapping rule, which is a collection of usage calculation rules that are used to calculate bill determinants from measurements. You can add the TOU mapping rule to the existing usage calculation group instead of creating a new one.

Correct : C

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.

Correct : A, B, C

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.