1z0-1091-22 Exam Dumps - Oracle Certification Questions and Answers

Smart Grid Gateway (SGG) is a product that provides integration between Oracle Utilities Meter Data Management and various head-end systems that communicate with smart meters. SGG supports different types of commands that can be sent to smart meters to perform various actions, such as reading, pinging, connecting, or disconnecting. According to the Oracle Utilities Smart Grid Gateway User Guide, some examples of commands that are supported by the SGG adapters are:

• On-demand reading: This is a command that requests a smart meter to send its current or historical usage data to the head-end system. On-demand reading can be used for billing purposes or for verifying meter readings.
• Ping meter: This is a command that tests the communication between the head-end system and the smart meter. Ping meter can be used for troubleshooting purposes or for checking meter status.
• Connect: This is a command that enables the service at a smart meter. Connect can be used for activating service for a new customer or for restoring service after a payment.

References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.1: Command Types

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.

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 4: Time-of-Use Data Management, Section 4.1: Time-of-Use Templates

The service point-measurement cycle relationship of Meter Data Management (MDM) can perform the following functions:

• Initiate request of bill determinants from subscribing systems: A subscribing system is an external system or service provider that receives bill determinants from MDM. A bill determinant is a value that is used to calculate a bill for a service point or device. The service point-measurement cycle relationship can initiate a request of bill determinants from subscribing systems based on the measurement cycle schedule. A measurement cycle schedule defines the dates on which devices are scheduled to be read for a given measurement cycle. A measurement cycle defines the schedule for manual meter reading of devices at service points in that cycle.
• Initiate push of bill determinants to subscribing systems: The service point-measurement cycle relationship can also initiate a push of bill determinants to subscribing systems based on the measurement cycle schedule. This means that MDM can send bill determinants to subscribing systems automatically or on demand.

The service point-measurement cycle relationship cannot perform the following functions:

• Create optimal meter reader routes by measurement cycle: A meter reader route is a sequence of service points or devices that are assigned to a meter reader formanual meter reading. A meter reader route is not created by the service point-measurement cycle relationship, but by using other configurations, such as route type or route sequence.
• Create hand-held download read activities: A hand-held download read activity is an activity that downloads measurement data from a hand-held device to MDM. A hand-held download read activity is not created by the service point-measurement cycle relationship, but by using other configurations, such as activity type or activity status.

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.

The Measurement Reprocessing functionality is a feature that enables MDM to reprocess measurements based on certain criteria or events. Some of the statements that are true about the Measurement Reprocessing functionality are:

• When a meter multiplier changes retroactively, measurements are reprocessed, triggering billing adjustment notifications that are sent to the customer information systems: A meter multiplier is a value that is used to adjust measurements based on certain factors, such as device accuracy or calibration. When a meter multiplier changes retroactively for a meter, measurements are reprocessed by applying the new meter multiplier value and triggering billing adjustment notifications that are sent to the customer information systems (CIS) to correct any billing errors or discrepancies.
• Derived measurements are recalculated based on new data: Derived measurements are values that are calculated from raw measurements based on certain rules or factors. When new data is available for raw measurements, such as corrected or estimated values, derived measurements are recalculated based on the new data.

When an installation constant changes retroactively for a meter, measurements are not automatically reprocessed, triggering billing adjustment notifications that are sent to the customer information systems. An installation constant is a value that is used to adjust measurements based on certain factors, such as device configuration or installation. When an installation constant changes retroactively for a meter, measurements are not automatically reprocessed, but require manual intervention by using the Reprocess Measurements batch process.

Measurement reprocessing is not executed by users manually, which imports corrected initial measurement data (IMD) records. Measurement reprocessing is executed by MDM automatically or by using batch processes, which reprocess existing measurement data based on certain criteria or events.

To validate high or low tolerances such that exceeding in either direction must not allow the reading to be finalized, and also apply all other validation rules that are configured, you should configure critical as the exception severity in Validation, Estimation, and Editing (VEE) rules. An exception severity is an attribute that indicates how severe an exception is when a measurement fails a VEE rule. Critical is an exception severity that prevents a measurement from being finalized until it is corrected or overridden by a user.

Issues is not an exception severity that can be configured in VEE rules. Issues is an attribute that indicates if there are any unresolved exceptions or errors for a measurement.

Terminate is not an exception severity that can be configured in VEE rules. Terminate is an action that can be performed by a VEE rule when a measurement fails the rule. Terminate means that the VEE process stops and does not apply any further VEE rules to the measurement.

Informational is not an exception severity that can be configured in VEE rules. Informational is an attribute that indicates if there are any informational messages or warnings for a measurement.

To configure the solution to bill each resident accurately for a small building with five metered apartments and common areas, you should set up a virtual meter to include the apartment usage and 20% of the common areas. A virtual meter is a configuration that defines how measurements from multiple devices or service points are aggregated or disaggregated. A virtual meter can be used to create new measurements from existing ones based on certain rules or factors. By setting up a virtual meter to include the apartment usage and 20% of the common areas, you can ensure that each resident is billed for their own usage and their share of the common usage.

You do not need to set up each apartment’s usage subscriptions to have two service points, one for the apartment and one for 20% of the common areas. A usage subscription is a relationship that defines the external system or service provider that will receive the bill determinants, the usage calculation group that will be used to calculate the bill determinants, and the service points that will provide the measurement data for the bill determinants. A usage subscription can have only one service point, not two.

You do not need to calculate the usage for each apartment by using customer information system (CIS), which is an external system that manages customer accounts and billing information. CIS does not calculate usage for each apartment, but receives bill determinants from MDM.

You do not need to use a derivation algorithm to include 20% of the common areas with the apartment accounts, which is a custom logic that can be developed by using Groovy scripting language or Java programming language. A derivation algorithm is not used to create new measurements from existing ones, but to create new measuring components from existing ones.