Explanation
To configure the solution to bill each resident accurately for a small building with five metered apartments and common areas, you should set up a virtual meter to include the apartment usage and 20% of the common areas. A virtual meter is a configuration that defines how measurements from multiple devices or service points are aggregated or disaggregated. A virtual meter can be used to create new measurements from existing ones based on certain rules or factors. By setting up a virtual meter to include the apartment usage and 20% of the common areas, you can ensure that each resident is billed for their own usage and their share of the common usage.
You do not need to set up each apartment's usage subscriptions to have two service points, one for the apartment and one for 20% of the common areas. A usage subscription is a relationship that 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. A usage subscription can have only one service point, not two.
You do not need to calculate the usage for each apartment by using customer information system (CIS), which is an external system that manages customer accounts and billing information. CIS does not calculate usage for each apartment, but receives bill determinants from MDM.
You do not need to use a derivation algorithm to include 20% of the common areas with the apartment accounts, which is a custom logic that can be developed by using Groovy scripting language or Java programming language. A derivation algorithm is not used to create new measurements from existing ones, but to create new measuring components from existing ones.

Explanation
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

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

Explanation
To configure the derived values that are relevant for a device, you should configure them on the measuring component type for the measuring components to be defined on the device. 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 also define the derived values that are calculated from raw measurements based on certain rules or factors. A measuring component is an instance of a measuring component type that is associated with a device.
You do not need to configure the derived values on the final measurement type, which defines how measurements are stored and processed in Oracle Utilities Meter Data Management. Final measurement types do not define derived values.
You do not need to configure the derived values on the device type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number. Device types do not define derived values.
You do not need to configure the derived values on the measuring component, which is an instance of a measuring component type that is associated with a device. Measuring components inherit derived values from their measuring component types.

Explanation
Oracle Utilities Meter Data Management (MDM) DataConnect is a feature that facilitates extraction of data for use in external applications such as energy management systems. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of data that can be exported in the MDM version of DataConnect are:
* Billing determinants: These are usage data that have been divided into time-of-use periods and applied with factors for billing purposes. Billing determinants can be exported to a billing system or a customer information system for generating bills or invoices.
* Usage measurement data: These are raw or processed interval data that have been recorded by smart meters or other devices. Usage measurement data can be exported to an analytics system or a demand response system for analysis or optimization.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 9: Communications, Section 9.4: DataConnect