Oracle 1Z0-1091-22 Exam Questions

Usage transactions can contain date breaks, which are dates that divide a usage period into sub-periods based on certain criteria or events. Date breaks are used to supply date breaks for usage transactions. Date breaks are specified by the requesting system or user input when requesting a usage transaction. A requesting system is an external system or service provider that requests bill determinants from MDM. A user input is a manual entry of data by a user.

Usage subscription BO is not used to supply date breaks for usage transactions. A usage subscription BO is a business object that defines the relationship between a service point and a subscribing system.

Usage subscription type is not used to supply date breaks for usage transactions. A usage subscription type is a configuration that defines the properties and rules for a usage subscription.

Deferred monitor calculation algorithm is not used to supply date breaks for usage transactions. A deferred monitor calculation algorithm is a custom logic that can be developed by using Groovy scripting language or Java programming language. A deferred monitor calculation algorithm is used to perform certain calculations or validations on usage transactions after they are created.

To configure equipment that attaches to an asset, such as a communication module attached to a meter, you should set up a component. A component is a part of an asset that can be installed and removed independently of the asset. You can define component types and associate them with asset types.For example, you can define a communication module component type and associate it with a meter asset type2.

You do not need to create a master child asset, which is a relationship between two assets that are installed at different service points but are functionally related.For example, you can define a transformer as a master asset and a meter as a child asset2. A master child asset is not suitable for equipment that attaches to an asset.

You do not need to add a sub-asset, which is an asset that is installed at the same service point as another asset but has its own measuring components and usage subscriptions.For example, you can define a meter as a sub-asset of another meter if they share the same service point but have different measurements2. A sub-asset is not suitable for equipment that attaches to an asset.

You do not need to add a constituent part, which is an attribute of an asset that cannot be installed or removed independently of the asset.For example, you can define a battery as a constituent part of a meter if it is embedded in the meter and cannot be replaced2. A constituent part is not suitable for equipment that attaches to an asset.

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.

The Smart Grid Gateway (SGG) is a middleware component that provides integration between Oracle Utilities Meter Data Management and smart meter systems. The SGG has three main uses:

Sharing event information with downstream systems: The SGG can process events from smart meter systems and send them to downstream systems, such as customer information systems (CIS), outage management systems (OMS), or distribution management systems (DMS). Events are occurrences that happen on devices or networks, such as tampering, low battery, or power outage.

Connecting to Smart Meter systems: The SGG can communicate with smart meter systems using various protocols and adapters. The SGG can support multiple smart meter systems simultaneously and provide a common interface for Oracle Utilities Meter Data Management.

Sharing outage information with outage management systems: The SGG can process outage events from smart meter systems and send them to outage management systems for analysis and restoration. Outage events are events that indicate a loss or restoration of power on a device or network.

The SGG does not share customer information or communicate directly with meters. Customer information is managed by Oracle Utilities Customer Cloud Service or Oracle Utilities Customer Care and Billing. Communication with meters is handled by smart meter systems that connect to the SGG.

An activity type is an Oracle Utilities Application Framework (OUAF) admin data that should be created for a custom Service Order Management process. An activity type defines the type of work that needs to be performed on a service point or device, such as enable service or disable service. An activity type also defines the following attributes:

The status and priority of the activity

The business object and algorithm that are used to process the activity

The fields and validations that are required for the activity

The notifications and escalations that are triggered by the activity

The dependencies and relationships that exist between different activities

An activity type is used to create and manage service orders, which are records that store the details and outcomes of the work performed on a service point or device.