Oracle 1Z0-1091-22 Exam Dumps

Momentary outages are very short-term outages where an outage event is sent and a restoration event is received in less than a few minutes. These outages may not require any action from the utility and may be ignored for reporting or analysis purposes. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, two system components that can be configured to ignore momentary outages are:

Device events: These are events that are sent by smart meters to indicate various conditions or situations, such as outages, tampering, or alarms. Device events can be configured with a minimum duration parameter that specifies the minimum time difference between an event start and an event end for the event to be processed. If the event duration is less than the minimum duration, the event is ignored.

Activities: These are tasks that are created by the system or by users to perform various actions, such as meter reading, installation, or maintenance. Activities can be configured with a momentary outage threshold parameter that specifies the maximum time difference between an outage event and a restoration event for the activity to be created. If the outage duration is less than the momentary outage threshold, no activity is created.

To allow an implementation to send bill determinants to CIS based on the requirements, you should set up the following usage subscription or usage calculation group configuration options:

Scalar usage calculation rule with a valid usage group: This defines how scalar consumption values are calculated from measurements and sent to CIS. You can define scalar usage calculation rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

TOU usage rule with a valid usage group: This defines how TOU consumption values are calculated from measurements and sent to CIS based on specific TOU periods. You can define TOU usage rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

You do not need to set up scalar specific group as a fallback VEE group or TOU usage group as a fallback VEE group. A fallback VEE group is used when there is no matching VEE group for a measurement based on its characteristics. A VEE group is a collection of VEE rules that are applied to measurements to validate, estimate, and edit them

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.

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.

Oracle Utilities Meter Data Management (MDM) DataConnect is a feature that facilitates extraction of data for use in external applications such as energy management systems. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of data that can be exported in the MDM version of DataConnect are:

Billing determinants: These are usage data that have been divided into time-of-use periods and applied with factors for billing purposes. Billing determinants can be exported to a billing system or a customer information system for generating bills or invoices.

Usage measurement data: These are raw or processed interval data that have been recorded by smart meters or other devices. Usage measurement data can be exported to an analytics system or a demand response system for analysis or optimization.