Dynamic aggregation uses dynamic queries for aggregation processes. These dynamic queries are based on the configuration of administrative data.
Which THREE statements are true about the dynamic aggregation main components?
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.
Which relationship must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM)?
A usage subscription is a relationship that must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM). A usage subscription defines the external system or service provider that will receive the bill determinants, the usage calculation group that will be used to calculate the bill determinants, and the service points that will provide the measurement data for the bill determinants.
You do not need to establish a usage factor, a usage transaction, or a usage rule with an external system or a service provider before creating bill determinants. A usage factor is a value that is used to adjust or convert measurements based on certain criteria. A usage transaction is a record that stores the bill determinants and other usage information for a usage subscription. A usage rule is a rule that is used to calculate, validate, or estimate bill determinants based on certain criteria.
If a project is setting up meter commands with a head-end system (HES), which TWO components should you configure to support the inbound responses from HES?
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 inbound and outbound communication between the two systems using web services and message queues. According to the Oracle Utilities Smart Grid Gateway User Guide, if a project is setting up meter commands with a head-end system (HES), two components that should be configured to support the inbound responses from HES are:
Inbound web services: These are web services that are exposed by SGG to receive messages from HES. Inbound web services can be used to receive responses from HES for commands that were sent by SGG or other systems.
Message sender: This is a component that sends messages from SGG to other systems using message queues. Message sender can be used to send responses from HES to Oracle Utilities Meter Data Management or other systems.
Service Order Management is used to orchestrate service order processes such as Enable Service and Disable Service.
Which Oracle Utilities Application Framework (OUAF) admin data should be created for a custom Service Order Management process?
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.
For a Meter Data Management (MDM) implementation, a customer requires specific bill determinants along with bill determinant calculation validations to be executed, before the determinant values are exported to their customer information system (CIS).
Which THREE factors should you consider while configuring usage calculation groups?
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 ensure that 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.
