Oracle 1Z0-1091-22 Exam Questions

Usage transactions can contain date breaks, which are dates that divide a usage period into sub-periods based on certain criteria or events. Date breaks are used to supply date breaks for usage transactions. Date breaks are specified by the requesting system or user input when requesting a usage transaction. A requesting system is an external system or service provider that requests bill determinants from MDM. A user input is a manual entry of data by a user.

Usage subscription BO is not used to supply date breaks for usage transactions. A usage subscription BO is a business object that defines the relationship between a service point and a subscribing system.

Usage subscription type is not used to supply date breaks for usage transactions. A usage subscription type is a configuration that defines the properties and rules for a usage subscription.

Deferred monitor calculation algorithm is not used to supply date breaks for usage transactions. A deferred monitor calculation algorithm is a custom logic that can be developed by using Groovy scripting language or Java programming language. A deferred monitor calculation algorithm is used to perform certain calculations or validations on usage transactions after they are created.

To set up the Cloud Service Payload Processing configuration, you should perform the following steps:

File system directory SFTP setup: This is used to configure the secure file transfer protocol (SFTP) settings for transferring files between Oracle Utilities Smart Grid Gateway and Oracle Utilities Meter Data Management. You need to specify the SFTP host name, port number, user name, password, and directory path for inbound and outbound files.

Key rings and key pairs: This is used to configure the encryption and decryption settings for payload files. You need to create key rings and key pairs for each communication type and associate them with message senders and receivers.

Object Storage locations: This is used to configure the object storage settings for storing payload files in Oracle Cloud Infrastructure. You need to specify the object storage URL, bucket name, user name, password, and encryption key for each communication type.

You do not need to set up head-end systems (HES), which are external systems that communicate with smart meters and devices. Head-end systems are configured in Oracle Utilities Smart Grid Gateway, not in Oracle Utilities Meter Data Management.

Some of the best practices for measurement retention are:

Derive time-of-use (TOU) values with interval data to prevent storing extra data: Time-of-use (TOU) values are scalar values that are calculated from interval data based on different TOU periods. Interval data is measurement data that is recorded at regular intervals, such as every 15 minutes or every hour. To prevent storing extra data, you can derive TOU values with interval data instead of storing them separately.

Derive demand from interval data to prevent storing extra data: Demand is a value that indicates the maximum power or load that is consumed or generated during a certain period. Demand can be calculated from interval data by using certain methods, such as block demand or rolling demand. To prevent storing extra data, you can derive demand from interval data instead of storing them separately.

Use Information Lifecycle Management (ILM) processes to help archive data: Information Lifecycle Management (ILM) processes are features that enable MDM to manage the lifecycle of measurement data based on certain policies or rules. ILM processes can help archive data that is no longer needed or used by moving them to different storage tiers or deleting them.

You do not need to keep scalar measurements in the customer read tables to stay consistent, which are tables that store measurement data that is entered by customers or meter readers. Scalar measurements are measurement data that are recorded at certain events, such as billing cycle end or meter exchange. You can store scalar measurements in different tables based on their source or status.

You do not need to keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes, which are records that store the raw measurement data that is received from smart meter systems or other sources. Final measurements are records that store the measurement data that has been validated, edited, and estimated. You can keep IMD for a shorter period of time than final measurements based on your business needs or requirements.

Oracle Utilities Meter Data Management normalizes measurements during the Create the Final Measurements stage of loading interval initial measurement data. Normalization is the process of converting interval measurements into a common format that can be processed by Oracle Utilities Meter Data Management. Normalization involves storing each interval measurement as a single record for a specific date and time, regardless of how they are received from smart meter systems.

Oracle Utilities Meter Data Management does not normalize measurements during other stages of loading interval initial measurement data, such as Load the Initial Measurements stage or Validation, Estimation, and Editing (VEE) stage. Normalization is not done for other purposes, such as validation or intervalization.

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 require any 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.