Oracle 1Z0-1091-22 Exam Dumps

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.

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.

Different validation, estimation, and editing (VEE) rules can be applied based on the VEE roles that categorize the source of the measurement data. A VEE role is an attribute that indicates how measurement data was created or modified. Some of the VEE roles that are provided as part of the base product are:

Manual override: This is a role that indicates that measurement data was manually entered or edited by a user.

Initial load: This is a role that indicates that measurement data was loaded from an external source or system.

Customer provided: This is a role that indicates that measurement data was provided by a customer.

Retry is not a VEE role that is provided as part of the base product. Retry is an action that can be performed on measurement data that has failed VEE rules.

Estimation is not a VEE role that is provided as part of the base product. Estimation is a process that can be performed on measurement data that is missing or invalid by using VEE rules.

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.

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.