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

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.

Time-of-use (TOU) maps can be used by various functions in Meter Data Management (MDM). A TOU map is a configuration that defines how interval measurements are converted into scalar measurements based on different TOU periods. A typical scenario in which TOU maps are applied is to usage transactions and final measurements for billing and analytical purposes. A usage transaction is a record that stores the bill determinants and other usage information for a usage subscription. A final measurement is a record that stores the measurement data that has been validated, edited, and estimated. TOU maps can be applied to usage transactions and final measurements to calculate bill determinants or perform analysis based on different TOU periods.

TOU maps are not applied to initial measurement data (IMD) records for creating summarized TOU final measurements. IMD records are records that store the raw measurement data that is received from smart meter systems or other sources. IMD records are not converted into final measurements by using TOU maps, but by using VEE rules.

TOU maps are not used to determine the time a user worked on an incorrect measurement, which is a function that is performed by using audit trails or logs. TOU maps are not used to map usage data with geospatial applications, which is a function that is performed by using location data or coordinates.

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.

Dynamic aggregation is a feature that allows users to perform aggregation processes on usage data based on dynamic queries that are defined by administrative data. Dynamic aggregation can be used to generate aggregated usage data for different dimensions and criteria, such as customer class, rate schedule, or geographic area. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of the main components of dynamic aggregation are:

• Measuring Component Sets: These define the dimensions and criteria by which aggregation is performed. Measuring Component Sets specify which characteristics and values should be used to group usage data for aggregation purposes.
• Measuring Components: These represent “buckets” or unique combinations of dimension values that are generated by Measuring Component Sets. Measuring Components store the aggregated usage data for each combination of dimension values.
• Data sources: These store project-provided SQL for getting data from different sources, such as usage subscriptions, measuring components, or virtual meters. Data sources specify which data should be used as input for aggregation processes.

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 10: Aggregations, Section 10.2: Dynamic Aggregation