1z0-1091-22 Sample Questions Answers

To build a new Service Order process that includes meter commands, you need to configure the following options:

• Measuring component type: This defines the type of measurement that a device can record, such as scalar, interval, or event. You can associate meter commands with measuring component types to perform actions on devices that have those types1.
• Activity type: This defines the type of work that needs to be performed on a service point or device, such as installation, removal, or inspection. You can associate meter commands with activity types to trigger actions on devices when an activity is completed1.
• Communication type Message sender: This defines the communication channel and protocol that is used to send meter commands to devices. You can configure message senders for different communication types, such as AMI, AMR, or manual1.

You do not need to configure device configuration type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number1. Device configuration type does not affect meter commands.

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

A dynamic option is an option that is assigned to an entity at run time based on a characteristic value. Dynamic options are used to provide flexibility and customization for different scenarios. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, some examples of dynamic options are:

• The utility has a program where customers can optionally participate in demand response (DR) programs. A dynamic option is specified on a usage subscription to allow different DR programs to be applied depending on a characteristic value such as customer class or rate schedule.
• An option is specified on a service point to allow Validation, Estimation, and Editing (VEE) processing to dynamically invoke a group of VEE rules depending on a characteristic. For example, if the service point has a characteristic indicating that it is part of a net metering program, then a different set of VEE rules may be applied than for a regular service point.
• The utility has a program that credits customers for conservation during critical peak periods. A dynamic option is specified on a usage subscription to allow different credit calculations to be applied depending on a characteristic value such as customer class or rate schedule.

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 2: Options and Characteristics, Section 2.1: Options

To convert natural gas volume to energy at the measuring component level, you should perform the following configuration steps:

• Set up a factor to hold the conversion values: A factor is a value that is used to adjust or convert measurements based on certain criteria. You need to set up a factor to hold the conversion values that are used to convert natural gas volume to energy. For example, you can set up a factor that holds the heating value of natural gas in different units of measure (UOM).
• Configure a value derivation algorithm by using Groovy: A value derivation algorithm is a rule that is used to calculate derived values from raw measurements based on certain factors or formulas. You need to configure a value derivation algorithm by using Groovy scripting language to define how natural gas volume is converted to energy by applying the conversion factor.
• Create value identifiers for the energy UOM on the measuring component type: A value identifier is an attribute that is used to store measurement or derived values in different UOMs. You need to create value identifiers for the energy UOM on the measuring component type that is used for natural gas devices. For example, you can create value identifiers for energy in British thermal units (BTU) or kilowatt-hours (kWh).

You do not need to create value identifiers for the energy UOM on the device, which is an instance of a device type that is installed at a service point. Value identifiers are defined at the measuring component type level, not at the device level.

You do not need to configure a value derivation algorithm by using Java, which is a programming language that is used to develop custom applications or extensions. Value derivation algorithms are configured by using Groovy scripting language, not Java.

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.

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 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

The client requests to design and set up data necessary to support an electric meter that is installed at a customer’s service point with solar panels. The meter has two channels that measure the kWh that was consumed from the grid and the kWh that was generated. Using the Math usage rule, usage transactions that take the difference between the consumed and generated channels must be created and stored. According to the Oracle Utilities Meter Data Management Business User Guide, some statements that are true about this scenario are:

• The two channels need distinct service quantity identifiers (SQIs) to differentiate between the generated and consumed kWh. SQIs are codes that identify different types of usage data, such as kWh, kVARh, or kW. SQIs can be used to specify which usage data should be used for calculation or validation purposes.
• Net consumption SQI is required. This is a code that identifies the usage data that represents the difference between the consumed and generated kWh. Net consumption SQI can be used to store and name the difference value and export it to other systems.
• You must set “Save Derived Vector” to Yes in the Math usage rule. This is a parameter that indicates whether the derived curve that results from the Math usage rule should be saved or not. Setting this parameter to Yes can be used to store the derived curve that represents the net consumption.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 3: Asset Management, Section 3.5: Measuring Components; Chapter 8: Usage, Section 8.4: Usage Calculations

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.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 9: Communications, Section 9.4: DataConnect

A virtual meter is a meter that does not physically exist but is used to represent the usage of a group of meters or a portion of a meter. A virtual meter can be used to perform various calculations or adjustments on usage data, such as aggregation, derivation, allocation, or net metering. According to the Oracle Utilities Meter Data Management Business User Guide, to bill the university correctly for a new fast food restaurant that is being installed at the center of the university and whose usage will also be included in the university’s master meter, the correct step is:

• Use derivation algorithms to exclude the restaurant’s usage from the master meter. This can be done by creating a virtual meter that represents the master meter minus the restaurant’s meter and applying a derivation algorithm that subtracts the restaurant’s usage from the master meter’s usage. The virtual meter’s usage can then be used for billing the university.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 3: Asset Management, Section 3.4: Virtual Meters

In a SaaS environment, Oracle Utilities Meter Data Management and Smart Grid Gateway are deployed on Oracle Cloud Infrastructure (OCI) and use OCI Object Storage to store files and data. OCI Object Storage is a scalable and secure service that allows users to store and access data from anywhere using REST APIs or web consoles. According to the Oracle Utilities Smart Grid Gateway User Guide, one step that should be performed to configure commands in a SaaS environment is:

• Create Object Storage locations (or buckets). These are containers that store files and data in OCI Object Storage. Object Storage locations can be used to store command requests and responses between Oracle Utilities Meter Data Management and Smart Grid Gateway.

References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.4: Command Configuration

A usage subscription is a record that defines how usage data are collected, processed, and exported for a service point or a device. A usage subscription can have various components that specify the logic and parameters for performing various operations on usage data, such as validation, estimation, editing, calculation, or export. According to the Oracle Utilities Meter Data Management Business User Guide, one example of a component that can be configured in a usage subscription is:

• Eligibility criteria: These are rules that determine whether a usage subscription generates a usage transaction or not. A usage transaction is a record that contains usage data that are ready for export to other systems, such as customer information system (CIS) or settlement system. Eligibility criteria can be used to filter out usage subscriptions that do not meet certain conditions or requirements for generating usage transactions.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.1: Usage Subscriptions