Explanation
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.

Explanation
The Subtractive Interval Data functionality is a feature that enables Meter Data Management (MDM) to process interval data from devices that do not provide interval readings, but only cumulative readings. The Subtractive Interval Data functionality performs the following actions:
* The IMD load processes calculate consumption in engineering units: The IMD load processes are batch processes that load initial measurement data (IMD) records from smart meter systems or other sources into MDM. The IMD load processes calculate consumption in engineering units by subtracting consecutive cumulative readings and applying conversion factors.
* A new reading condition field ensures that you do not lose the reading quality when a meter's consumption is estimated: A reading condition field is an attribute that indicates the quality or status of a measurement, such as valid, invalid, estimated, or substituted. A new reading condition field called Original Reading Condition is added to store the original reading condition of a cumulative reading when its consumption is estimated by using VEE rules.
* You can optionally validate for rollover exceptions and negative consumption calculations: You can configure VEE rules to check for rollover exceptions and negative consumption calculations when processing subtractive interval data. A rollover exception occurs when a cumulative reading reaches its maximum value and resets to zero. A negative consumption calculation occurs when a cumulative reading decreases instead of increasing.
It is not true that it validates consumption in initial measurement data (IMD), which are records that store the raw measurement data that is received from smart meter systems or other sources. Subtractive Interval Data functionality does not validate consumption in IMD, but calculates consumption from cumulative readings.
It is not true that it converts engineering units into reads, which are values that are recorded by devices at certain intervals or events. Subtractive Interval Data functionality does not convert engineering units into reads, but calculates consumption in engineering units from cumulative readings.

Explanation
To validate high or low tolerances such that exceeding in either direction must not allow the reading to be finalized, and also apply all other validation rules that are configured, you should configure critical as the exception severity in Validation, Estimation, and Editing (VEE) rules. An exception severity is an attribute that indicates how severe an exception is when a measurement fails a VEE rule. Critical is an exception severity that prevents a measurement from being finalized until it is corrected or overridden by a user.
Issues is not an exception severity that can be configured in VEE rules. Issues is an attribute that indicates if there are any unresolved exceptions or errors for a measurement.
Terminate is not an exception severity that can be configured in VEE rules. Terminate is an action that can be performed by a VEE rule when a measurement fails the rule. Terminate means that the VEE process stops and does not apply any further VEE rules to the measurement.
Informational is not an exception severity that can be configured in VEE rules. Informational is an attribute that indicates if there are any informational messages or warnings for a measurement.

Explanation
To create Smart Grid Gateway Payload Processing extendable lookup values, you should configure the Events Set Parser and Set Transformer methods in the User Exit Interceptors section. These methods are used to parse and transform event data from payload files into a common format that can be processed by Oracle Utilities Meter Data Management.
You do not need to configure Get Parser and Get Transformer methods, which are used to parse and transform measurement data from payload files. You do not need to configure SOAPSNDR and RTHTTPSNDR methods, which are used to send SOAP or HTTP messages to external systems. You do not need to configure Initial Measurements and Device methods, which are used to initialize measurement data and device information from payload files.

Explanation
Momentary outages are very short-term outages where an outage event is sent and a restoration event is received in less than a few minutes. These outages may not requireany action from the utility and may be ignored for reporting or analysis purposes. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, two system components that can be configured to ignore momentary outages are:
* Device events: These are events that are sent by smart meters to indicate various conditions or situations, such as outages, tampering, or alarms. Device events can be configured with a minimum duration parameter that specifies the minimum time difference between an event start and an event end for the event to be processed. If the event duration is less than the minimum duration, the event is ignored.
* Activities: These are tasks that are created by the system or by users to perform various actions, such as meter reading, installation, or maintenance. Activities can be configured with a momentary outage threshold parameter that specifies the maximum time difference between an outage event and a restoration event for the activity to be created. If the outage duration is less than the momentary outage threshold, no activity is created.
References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 5: Device Management, Section 5.2: Device Events; Chapter 6: Device Installations, Section 6.4: Activities