1z0-1091-22 Practice Exam Questions with Answers Oracle Utilities Meter Solution Cloud Service 2022 Implementation Professional Certification

Derived values are values that are calculated from raw measurements based on certain rules or factors. Derived values can be used for different purposes, such as billing, analysis, or reporting. Some examples of derived values are:

• Value with a factor such as line loss applied: This is a value that is adjusted by applying a factor that accounts for the loss of energy or water during transmission or distribution. For example, a line loss factor can be applied to a meter reading to calculate the actual amount of energy or water that was delivered to a customer.
• Value converted from one unit of measurement to another: This is a value that is converted from one unit of measurement (UOM) to another based on a conversion factor. For example, a volume reading in cubic feet can be converted to a volume reading in gallons by multiplying it by a conversion factor.
• Interval data values created by “intervalizing” a scalar reading by applying a profile to it: This is a value that is created by dividing a scalar reading into smaller time intervals based on a profile that represents the usage pattern of a customer. For example, a daily scalar reading can be intervalized into hourly readings by applying a load profile that reflects the customer’s hourly usage.

Estimated value if the final measurement is too low or high is not a derived value, but an estimated value. Estimated values are values that are generated when raw measurements are missing or invalid based on certain criteria. Estimated values can be based on historical data, statistical methods, or other sources.

Comparison of normal versus actual usage is not a derived value, but an analysis result. Analysis results are values that are calculated by comparing or aggregating measurements or derived values for different purposes, such as revenue protection, load research, or customer engagement.

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

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 5: Device Management, Section 5.2: Device Events; Chapter 6: Device Installations, Section 6.4: Activities

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.

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

Asset and component specifications are used to describe design details and asset attributes that are common to a group of assets or components. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, some examples of smart meter specifications are:

• Firmware: The software version installed on the smart meter
• Asset type: The category of the smart meter, such as electric, gas, water, or heat
• Manufacturer: The company that produced the smart meter

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 3: Asset Management, Section 3.2: Asset and Component Specifications

Usage calculation groups are used to define how usage data are calculated, validated, and exported for different purposes, such as billing, settlement, or analysis. Usage calculation groups can have different components that specify the logic and parameters for performing various operations on usage data. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of components that can be configured in usage calculation groups are:

• CIS rates: These are rate schedules that are defined in the customer information system (CIS) and imported into Oracle Utilities Meter Data Management. CIS rates can be used to specify which bill determinants or usage calculations should be applied for different rate schedules or customer classes.
• Bill determinants or usage validations: These are rules that check the quality or accuracy of usage data and assign condition codes or flags to indicate any issues or errors. Bill determinants or usage validations can be used to ensurethat usage data meet certain criteria or standards before they are exported to CIS or other systems.
• Bill determinants or usage calculations: These are rules that perform various calculations or adjustments on usage data, such as dividing usage into time-of-use periods, applying factors or multipliers, or deriving net usage. Bill determinants or usage calculations can be used to generate different types of bill determinants for billing purposes.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.2: Usage Calculation Groups

Initial measurement data (IMD) are raw measurement data that are imported into Oracle Utilities Meter Data Management from various sources, such as head-end systems, meter reading systems, or manual entry. IMD can be viewed through the Measuring Component portal, but they are not ready for export or further processing until they pass validation, estimation, and editing (VEE) processing. VEE processing is a set of rules and algorithms that check and correct measurement data for any gaps, errors, or anomalies. According to the Oracle Utilities Meter Data Management Business User Guide, one type of VEE rule that IMD must pass in order to become final measurement data is:

• Critical validation: This is a rule that checks whether IMD meet certain minimum criteria for quality and completeness. Critical validation can be used to filter out IMD that are missing, duplicated, corrupted, or invalid.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 7: Measurements, Section 7.1: Measurement Data; Chapter 8: Usage, Section 8.3: Validation, Estimation, and Editing

A time-of-use (TOU) group is a set of TOU maps that define how usage is divided into different TOU periods for different days of the week and seasons of the year. A TOU group can have a work calendar associated with it to define holidays and other special days that may have different TOU periods than regular days. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, to configure a TOU group for“on peak”, “off peak”, and “shoulder” periods and have holiday consumption categorized as “off peak” regardless of the day on which it falls, the correct steps are:

• Add the work calendar to the TOU map template and set the Holiday TOU as “off peak”. This will ensure that any day marked as a holiday in the work calendar will have its usage assigned to the “off peak” period.
• Create a TOU map for each season using the TOU map template and define the start and end times for each TOU period (“on peak”, “off peak”, and “shoulder”) for each day of the week.
• Create a TOU group and add the TOU maps for each season to it.

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 4: Time-of-Use Data Management, Section 4.2: Time-of-Use Maps; Section 4.3: Time-of-Use Groups

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.

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.