To build a new Service Order process that includes meter commands, you need to configure the following options:

Measuring component type: This defines the type of measurement that a device can record, such as scalar, interval, or event.You can associate meter commands with measuring component types to perform actions on devices that have those types1.

Activity type: This defines the type of work that needs to be performed on a service point or device, such as installation, removal, or inspection.You can associate meter commands with activity types to trigger actions on devices when an activity is completed1.

Communication type Message sender: This defines the communication channel and protocol that is used to send meter commands to devices.You can configure message senders for different communication types, such as AMI, AMR, or manual1.

You do not need to configure device configuration type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number1. Device configuration type does not affect meter commands.

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 allow an implementation to send bill determinants to CIS based on the requirements, you should set up the following usage subscription or usage calculation group configuration options:

Scalar usage calculation rule with a valid usage group: This defines how scalar consumption values are calculated from measurements and sent to CIS. You can define scalar usage calculation rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

TOU usage rule with a valid usage group: This defines how TOU consumption values are calculated from measurements and sent to CIS based on specific TOU periods. You can define TOU usage rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

You do not need to set up scalar specific group as a fallback VEE group or TOU usage group as a fallback VEE group. A fallback VEE group is used when there is no matching VEE group for a measurement based on its characteristics. A VEE group is a collection of VEE rules that are applied to measurements to validate, estimate, and edit them

The customer needs to create a single measuring component type to store the 15-minute interval readings along with the daily scalar register reading. A measuring component type defines the type of measurement that a device can record, such as scalar, interval, or event.A measuring component type can store multiple measurement types, such as interval and scalar, for different purposes, such as billing, load research, and presentment1.

The customer does not need to create separate measuring component types for each measurement type or each use case purpose.This would result in unnecessary duplication of data and complexity of configuration1.

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.