Most Recent Oracle 1Z0-1091-22 Exam Questions & Answers

A time-of-use (TOU) template is used to define the start and end times of TOU periods for different days of the week and seasons of the year. A TOU template has an interval size that controls the values allowed as start and end times. For example, if the interval size is 60 minutes, then the start and end times must be multiples of 60 minutes, such as 00:00, 01:00, 02:00, and so on. A TOU template can be used to generate TOU data for TOU maps whose seconds per interval (SPI) is divisible by the template's SPI. For example, if the template's SPI is 3600 (60 minutes), then it can be used to generate TOU data for TOU maps whose SPI is 3600, 1800 (30 minutes), 1200 (20 minutes), 900 (15 minutes), 600 (10 minutes), 300 (5 minutes), and so on. Therefore, the correct answer is D.

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.

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.

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.

To create Smart Grid Gateway Payload Processing extendable lookup values, you should configure the Events Set Parser and Set Transformer methods in the User Exit Interceptors section. These methods are used to parse and transform event data from payload files into a common format that can be processed by Oracle Utilities Meter Data Management.

You do not need to configure Get Parser and Get Transformer methods, which are used to parse and transform measurement data from payload files. You do not need to configure SOAPSNDR and RTHTTPSNDR methods, which are used to send SOAP or HTTP messages to external systems. You do not need to configure Initial Measurements and Device methods, which are used to initialize measurement data and device information from payload files.