Get 1z0-1091-22 Dumps : Verified Oracle Utilities Meter Solution Cloud Service 2022 Implementation Professional

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

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

The Vector and Service Quantity Math usage rule facilitates the configuration of complex vector calculations. It is based on a series of underlying services with vectors configured as input to the calculations. Some typical uses of the usage rule are:

• Finding coincident peaks: This is a calculation that finds the highest demand value for each interval across multiple service points or devices.
• Performing Array math: This is a calculation that performs arithmetic operations on arrays of interval data, such as addition, subtraction, multiplication, or division.
• Performing math formulas on interval data: This is a calculation that performs mathematical functions on interval data, such as logarithm, exponentiation, square root, or trigonometry.

Finding max values is not a typical use of the Vector and Service Quantity Math usage rule. Finding max values is a simple calculation that finds the highest demand value for each service point or device.

Converting interval data to scalar reads is not a typical use of the Vector and Service Quantity Math usage rule. Converting interval data to scalar reads is done by using other usage rules, such as Interval Data Scalar Read Rule.

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.

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.