A dynamic option is an option that is assigned to an entity at run time based on a characteristic value. Dynamic options are used to provide flexibility and customization for different scenarios. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, some examples of dynamic options are:

• The utility has a program where customers can optionally participate in demand response (DR) programs. A dynamic option is specified on a usage subscription to allow different DR programs to be applied depending on a characteristic value such as customer class or rate schedule.
• An option is specified on a service point to allow Validation, Estimation, and Editing (VEE) processing to dynamically invoke a group of VEE rules depending on a characteristic. For example, if the service point has a characteristic indicating that it is part of a net metering program, then a different set of VEE rules may be applied than for a regular service point.
• The utility has a program that credits customers for conservation during critical peak periods. A dynamic option is specified on a usage subscription to allow different credit calculations to be applied depending on a characteristic value such as customer class or rate schedule.

References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 2: Options and Characteristics, Section 2.1: Options

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 different types of commands that can be sent to smart meters to perform various actions, such as reading, pinging, connecting, or disconnecting. According to the Oracle Utilities Smart Grid Gateway User Guide, some examples of commands that are supported by the SGG adapters are:

• On-demand reading: This is a command that requests a smart meter to send its current or historical usage data to the head-end system. On-demand reading can be used for billing purposes or for verifying meter readings.
• Ping meter: This is a command that tests the communication between the head-end system and the smart meter. Ping meter can be used for troubleshooting purposes or for checking meter status.
• Connect: This is a command that enables the service at a smart meter. Connect can be used for activating service for a new customer or for restoring service after a payment.

References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.1: Command Types

In a SaaS environment, Oracle Utilities Meter Data Management and Smart Grid Gateway are deployed on Oracle Cloud Infrastructure (OCI) and use OCI Object Storage to store files and data. OCI Object Storage is a scalable and secure service that allows users to store and access data from anywhere using REST APIs or web consoles. Smart Grid Gateway adapters process usage and device event payloads via batch processing. Files are sent from a head-end system (HES) to an OCI Object Storage location, where they are batch processed. According to the Oracle Utilities Smart Grid Gateway User Guide, some operations that are performed by the Smart Grid Gateway processes are:

• Parse payload into individual usage readings/device events. This is an operation that extracts usage readings or device events from the payload file and converts them into individual records.
• Invoke IMD/Device Event Seeder (as appropriate). This is an operation that invokes a web service that sends usage readings or device events to Oracle Utilities Meter Data Management for further processing.
• Transform usage readings into standard (unified) format. This is an operation that converts usage readings from vendor-specific formats into a standard format that can be processed by Oracle Utilities Meter Data Management.

References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.4: Command Configuration; Chapter 5: Device Events; Chapter 6: Usage

The client has installed scalar devices to measure the solar energy generated (export) and the energy received (import) from the market. This data is stored in separate measuring components (registers). The validation rules are generally the same for both measuring components, but there is one exception: the negative consumption check applies only to energy received (import). According to the Oracle Utilities Meter Data Management Business User Guide, two configurations that ensure that the negative consumption check is checked for energy received (import) only are:

• Use eligibility criteria: These are rules that determine whether a VEE rule should be applied or not based on certain conditions or characteristics. Eligibility criteria can be used to apply the negative consumption check only to the measuring component that has a characteristic value indicating energy received (import).
• Use the Skip flag in the VEE rule: This is a flag that indicates whether a VEE rule should be skipped or not based on certain conditions or characteristics. The Skip flag can be used to skip the negative consumption check for the measuring component that has a characteristic value indicating energy generated (export).

References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.3: Validation, Estimation, and Editing

The service point-measurement cycle relationship of Meter Data Management (MDM) can perform the following functions:

• Initiate request of bill determinants from subscribing systems: A subscribing system is an external system or service provider that receives bill determinants from MDM. A bill determinant is a value that is used to calculate a bill for a service point or device. The service point-measurement cycle relationship can initiate a request of bill determinants from subscribing systems based on the measurement cycle schedule. A measurement cycle schedule defines the dates on which devices are scheduled to be read for a given measurement cycle. A measurement cycle defines the schedule for manual meter reading of devices at service points in that cycle.
• Initiate push of bill determinants to subscribing systems: The service point-measurement cycle relationship can also initiate a push of bill determinants to subscribing systems based on the measurement cycle schedule. This means that MDM can send bill determinants to subscribing systems automatically or on demand.

The service point-measurement cycle relationship cannot perform the following functions:

• Create optimal meter reader routes by measurement cycle: A meter reader route is a sequence of service points or devices that are assigned to a meter reader formanual meter reading. A meter reader route is not created by the service point-measurement cycle relationship, but by using other configurations, such as route type or route sequence.
• Create hand-held download read activities: A hand-held download read activity is an activity that downloads measurement data from a hand-held device to MDM. A hand-held download read activity is not created by the service point-measurement cycle relationship, but by using other configurations, such as activity type or activity status.