Oracle 1z0-1091-22 Oracle Utilities Meter Solution Cloud Service 2022 Implementation Professional Exam Practice Test

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.

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 device events that are sent by smart meters to indicate various conditions or situations, such as outages, tampering, or alarms. SGG provides a set of standard device event types that cover common scenarios across different head-end systems and vendors. However, some head-end systems may have vendor-specific device event types that are not covered by the standard device event types. In order to manage these additional device events, SGG allows users to create new standard device event types and map them to the vendor-specific device event types. According to the Oracle Utilities Smart Grid Gateway User Guide, apart from creating the new standard device event type “admin data”, the other step that should be done to represent the new standard device events is:

• Extend the Landis + Gyr device event mapping extendable lookup such that it maps each of the Landis + Gyr specific device event names to the new standard device event names. This will ensure that SGG can recognize and process the vendor-specific device events and map them to the corresponding standard device events.

References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 5: Device Events, Section 5.2: Device Event Types; Section 5.3: Device Event Mapping

The Smart Grid Gateway (SGG) is a middleware component that provides integration between Oracle Utilities Meter Data Management and smart meter systems. The SGG has three main uses:

• Sharing event information with downstream systems: The SGG can process events from smart meter systems and send them to downstream systems, such as customer information systems (CIS), outage management systems (OMS), ordistribution management systems (DMS). Events are occurrences that happen on devices or networks, such as tampering, low battery, or power outage.
• Connecting to Smart Meter systems: The SGG can communicate with smart meter systems using various protocols and adapters. The SGG can support multiple smart meter systems simultaneously and provide a common interface for Oracle Utilities Meter Data Management.
• Sharing outage information with outage management systems: The SGG can process outage events from smart meter systems and send them to outage management systems for analysis and restoration. Outage events are events that indicate a loss or restoration of power on a device or network.

The SGG does not share customer information or communicate directly with meters. Customer information is managed by Oracle Utilities Customer Cloud Service or Oracle Utilities Customer Care and Billing. Communication with meters is handled by smart meter systems that connect to the SGG.

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

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 datebreaks 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 interval proxy day estimation VEE rule is a rule that estimates missing intervals by selecting interval data to average from a list of days that are most like the day being estimated. This is achieved by measuring the component comparison periods, which are periods of time that are used to compare different days based on certain criteria. According to the Oracle Utilities Meter Data Management Business User Guide, one factor that is used to define the proxy or the list of days that are most like the day being estimated is:

• Weather data: This is data that indicates the temperature or other weather conditions for a given day. Weather data can be used to select days that have similar weather patterns or variations as the day being estimated.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.3: Validation, Estimation, and Editing; Section 8.3.2: Interval Proxy Day Estimation

Some of the best practices for measurement retention are:

• Derive time-of-use (TOU) values with interval data to prevent storing extra data: Time-of-use (TOU) values are scalar values that are calculated from interval data based on different TOU periods. Interval data is measurement data that is recorded at regular intervals, such as every 15 minutes or every hour. To prevent storing extra data, you can derive TOU values with interval data instead of storing them separately.
• Derive demand from interval data to prevent storing extra data: Demand is a value that indicates the maximum power or load that is consumed or generated during a certain period. Demand can be calculated from interval data by using certain methods, such as block demand or rolling demand. To prevent storing extra data, you can derive demand from interval data instead of storing them separately.
• Use Information Lifecycle Management (ILM) processes to help archive data: Information Lifecycle Management (ILM) processes are features that enable MDM to manage the lifecycle of measurement data based on certain policies or rules. ILM processes can help archive data that is no longer needed or used by moving them to different storage tiers or deleting them.

You do not need to keep scalar measurements in the customer read tables to stay consistent, which are tables that store measurement data that is entered by customers or meter readers. Scalar measurements are measurement data that are recorded at certain events, such as billing cycle end or meter exchange. You can store scalar measurements in different tables based on their source or status.

You do not need to keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes, which are records that store the raw measurement data that is received from smart meter systems or other sources. Final measurements are records that store the measurement data that has been validated, edited, and estimated. You can keep IMD for a shorter period of time than final measurements based on your business needs or requirements.