Free Practice Questions for Oracle 1z0-996-22 Exam

The Fallback VEE Group is a configuration option that allows you to specify a VEE Group to be used when no other VEE Group is found for a measurement. This ensures that the measurement is processed by the VEE rules defined in the Fallback VEE Group, which can include estimation rules. The Fallback VEE Group is assigned to a VEE role, which is a logical grouping of VEE Groups based on the source and type of measurement data. For example, you can create a VEE role for estimated measurements and assign a Fallback VEE Group that contains the estimation rules you want to apply to them. This way, you can ensure that the estimated measurements are validated and edited according to your business requirements. References: Configuring VEE Roles, Understanding VEE Rules

The Get Scalar Details and Apply Formula usage rule is used to retrieve scalar measurements from the measuring components installed at the usage subscription’s service points and apply a formula to the total quantity1. This rule can be used to convert the total from one unit of measure to another by using a factor that has a Factor Class of “Number” and a Factor Type of "Conversion"2. For example, this rule can be used to convert the total consumption from cubic feet to therms by applying a factor that multiplies the cubic feet by a conversion rate2. Therefore, the correct answer is B. Get Scalar Details and Apply Formula. References:

Get Scalar Details and Apply Formula

Configuring Usage Calculation Rules

 The major entities that hold the key geographic, demographic, and financial information related to a customer who is financially responsible for a property are:

Account: An account represents the financial relationship between a customer and the utility. It contains information such as the account number, account type, account status, billing cycle, payment plan, and balance.

Customer Class: A customer class is a grouping of customers based on common characteristics, such as residential, commercial, or industrial. It determines the default values for various attributes, such as rate schedules, service agreements, and billing options.

Person: A person is an individual who is associated with an account, such as the account holder, a contact, or a guarantor. It contains information such as the name, address, phone number, email, and identification number of the person.

Premise: A premise is a physical location where a utility service is provided. It contains information such as the premise number, premise type, premise status, address, coordinates, and service point.

Service Agreement: A service agreement is a contract between a customer and the utility that defines the terms and conditions of the service, such as the service type, start date, end date, rate schedule, and billing frequency.

These entities are linked together in a hierarchical structure, as shown in the following diagram1:

References:

Oracle Utilities Customer Cloud Service Business User Guide, Chapter 2: Customer Information, Section 2.1: Understanding Customer Information

[Oracle Utilities Customer Cloud Service Administrative User Guide], Chapter 2: Configuring Customer Information, Section 2.1: Configuring Customer Information Entities

Device types define information about a class of devices, including properties that apply to all devices of a type1. For the AMI roll-out, the device type administrative data should consider the following aspects:

Valid head-end systems: A head-end system is a system that communicates with devices and collects measurement and event data from them2. The device type should specify a fallback head-end system and a list of valid head-end systems that can be used for the devices of that type1. This will allow the customer to choose the head-end system that best suits their needs and preferences.

Valid device configuration types: A device configuration type defines the configuration parameters and commands that can be applied to a device of a certain type3. The device type should specify the valid list of device configuration types that can be used for the devices of that type1. This will ensure that the devices are configured consistently and correctly to support the existing tariffs for billing.

Electricity service type: A service type defines the characteristics of a service that is provided to a customer, such as the commodity, the rate schedule, the bill cycle, etc4. The device type should specify the electricity service type that is associated with the devices of that type1. This will enable the system to calculate the usage and billing for the devices based on the service type. References:

1: Understanding Device Types

2: Head End Systems

3: Device Configuration Types

4: Service Types

According to the Oracle Utilities Customer Cloud Service User Guides, a device type is a configuration entity that defines the properties and behaviors of a device, such as what service it measures, what business object it uses, what characteristics it has, and what measuring components it supports1. Therefore, the following device type attributes are required to identify these device types:

A. Device Business Object. A device business object is a mandatory attribute that specifies the business object that is used to store and process the device data in the system1. Different device business objects have different fields, validations, and algorithms to handle different types of devices1. For example, the D1-ScalarDevice business object is used for scalar devices that measure a single quantity, such as a gas manual meter2, while the D1-IntervalDevice business object is used for interval devices that measure multiple quantities at regular intervals, such as an electric smart meter3.

B. Service Type. A service type is a mandatory attribute that specifies the type of service that the device measures, such as electricity, gas, water, or sewerage1. A service type also defines the characteristics and measurements of the service, such as the unit of measure, the measuring component type, and the service quantity identifier. For example, an electric smart meter can measure electricity service with kWh as the unit of measure, D1-ScalarMC as the measuring component type, and D1-Consumption as the service quantity identifier3, while a gas manual meter can measure gas service with m3 as the unit of measure, D1-ScalarMC as the measuring component type, and D1-Consumption as the service quantity identifier2.

The following device type attributes are not required to identify these device types:

C. Valid Measuring Component Types. Valid measuring component types are optional attributes that specify the measuring component types that can be associated with the device type1. A measuring component type defines the most important properties of a measuring component, such as what it measures, how regularly it measures it, and whether it should be connected to a physical device. If valid measuring component types are not specified for a device type, then any measuring component type can be associated with the device type1.

D. Manufacturer. Manufacturer is an optional attribute that specifies the name of the manufacturer of the device type1. This attribute can be used to filter or group device types by manufacturer, but it is not essential to identify the device type1.

E. Serial Number. Serial number is not an attribute of the device type, but an attribute of the device instance1. A serial number is a unique identifier that is assigned to each device by the manufacturer or the utility1. A serial number can be used to identify a specific device, but not a device type1.

References:

Configuring Device Types

D1-ScalarDevice Business Object

D1-IntervalDevice Business Object

[Understanding Service Types]

[Understanding Measuring Component Types]

 A change in rate schedule does not cause price proration, but rather calculation period proration, which is a different process that splits the bill segment into sub-segments based on the effective dates of the rate versions. A change in bill factor alone does not cause price proration, unless it is associated with a calculation rule that also changes during the bill period.

Change in Rate Schedule only: A change in rate schedule does not cause price proration, but rather calculation period proration, which is a different process that splits the bill segment into sub-segments based on the effective dates of the rate versions.

References:

Effective Dates and Price Proration

Calculation Period Proration

Consumption Period Proration

According to the Oracle Utilities Customer Cloud Service User Guide1, service points are physical locations at which a company supplies service and are used to store information describing the type of service supplied and how it is measured. Devices are installed at service points, and the relationship between individual service points and devices can change over time. However, a service point may only have one device. If multiple devices at a service point are required, a parent and child service point relationship must be defined to create a hierarchy of service points. On each service point, users can specify a parent service point. This feature can be used to link multiple devices to a single market service point ID or to represent different service types or measuring components at a service point. References: Oracle Utilities Customer Cloud Service - Get Started, About Service Points, Oracle Utilities Operational Device Cloud Service - Get Started

 A usage subscription is a relationship between a service point and an external system or a service provider that defines how usage data is exchanged and processed1. A usage subscription is required before creating bill determinants, as it determines the usage calculation group, the usage transaction type, and the usage subscription quantity type that are used to derive bill determinants from usage data2. A usage subscription also specifies the usage rule that is used to request bill determinants from the external system or the service provider3. Therefore, the correct answer is C. Usage Subscription. References:

Understanding Usage Subscriptions

Creating Usage Subscriptions

Requesting Bill Determinants