2023年最新の1z0-1091-22問題集PDFで1z0-1091-22リアル試験問題解答
有効な1z0-1091-22テスト解答とOracle 1z0-1091-22試験PDF問題を試そう
質問 # 13
The client has installed scalar devices to measure the solar energy generated (export) and the energy received (import) from the market. This data is stored in separate measuring components (registers). The validation rules are generally the same for both measuring components, but there is one exception: the negative consumption check applies only to energy received (import).
Which TWO configurations ensure that the negative consumption rule is checked for energy received (import) only?
- A. Create two different VEE groups.
- B. Use eligibility criteria.
- C. Remove the negative consumption check from the VEE group.
- D. Use the Skip flag in the Validation, Estimation, and Editing (VEE) rule.
- E. Modify the base VEE rule.
正解：B、D
解説：
Explanation
The client has installed scalar devices to measure the solar energy generated (export) and the energy received (import) from the market. This data is stored in separate measuring components (registers). The validation rules are generally the same for both measuring components, but there is one exception: the negative consumption check applies only to energy received (import). According to the Oracle Utilities Meter Data Management Business User Guide, two configurations that ensure that the negative consumption check is checked for energy received (import) only are:
* Use eligibility criteria: These are rules that determine whether a VEE rule should be applied or not based on certain conditions or characteristics. Eligibility criteria can be used to apply the negative consumption check only to the measuring component that has a characteristic value indicating energy received (import).
* Use the Skip flag in the VEE rule: This is a flag that indicates whether a VEE rule should be skipped or not based on certain conditions or characteristics. The Skip flag can be used to skip the negative consumption check for the measuring component that has a characteristic value indicating energy
* generated (export).
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.3:
Validation, Estimation, and Editing
質問 # 14
A business needs a new Service Order process that includes meter commands. Which THREE options should you configure to build this process?
- A. Device configuration type
- B. Communication type Message sender
- C. Measuring component type
- D. Activity type
正解：B、C、D
解説：
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.
質問 # 15
When used with the SaaS Cloud services, the Oracle Smart Grid Gateway (SGG) adapters process usage and device event payloads via batch processing. Files are sent from a head-end system (HES) to an Oracle Cloud Object Storage location, where they are batch processed.
Which THREE operations are performed by the SGG processes?
- A. Invoke IMD/Device Event Seeder (as appropriate).
- B. Load reads into Object Storage.
- C. Load reads into a file directory.
- D. Transform usage readings into standard (unified) format.
- E. Parse payload into individual usage readings/device events.
正解：A、D、E
解説：
Explanation
In a SaaS environment, Oracle Utilities Meter Data Management and Smart Grid Gateway are deployed on Oracle Cloud Infrastructure (OCI) and use OCI Object Storage to store files and data. OCI Object Storage is a scalable and secure service that allows users to store and access data from anywhere using REST APIs or web consoles. Smart Grid Gateway adapters process usage and device event payloads via batch processing. Files are sent from a head-end system (HES) to an OCI Object Storage location, where they are batch processed.
According to the Oracle Utilities Smart Grid Gateway User Guide, some operations that are performed by the Smart Grid Gateway processes are:
* Parse payload into individual usage readings/device events. This is an operation that extracts usage readings or device events from the payload file and converts them into individual records.
* Invoke IMD/Device Event Seeder (as appropriate). This is an operation that invokes a web service that sends usage readings or device events to Oracle Utilities Meter Data Management for further processing.
* Transform usage readings into standard (unified) format. This is an operation that converts usage readings from vendor-specific formats into a standard format that can be processed by Oracle Utilities Meter Data Management.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.4: Command Configuration; Chapter 5: Device Events; Chapter 6: Usage
質問 # 16
You want to manage additional Landis + Gyr device events that are not covered by the set of standard device event types provided with Smart Grid Gateway (SGG).
Apart from creating the new device event type "admin data", what else should you do to represent the new standard device events that you want to manage?
- A. Add a record into the External Device Event Mapping table (Dl-E>ODVCEVNTMAP) for each new device event that you want to manage, specifying the standard device event to which it maps.
- B. Create a set of admin data to represent the Landis + Gyr specific device event types, ensuring that for each new device event type, the name of the corresponding standard device event business object is configured in the "Standard Device Event BO Map" characteristic.
- C. Extend the Landis + Gyr device event mapping extendable lookup such that it maps each of the Landis
-f- Gyr specific device event names to the new standard device event names. - D. Set up service providers for each new device event that you want to manage, and specify on each service provider the standard device evert to which it maps.
正解：C
解説：
Explanation
Smart Grid Gateway (SGG) is a product that provides integration between Oracle Utilities Meter Data Management and various head-end systems that communicate with smart meters. SGG supports different types of device events that are sent by smart meters to indicate various conditions or situations, such as outages, tampering, or alarms. SGG provides a set of standard device event types that cover common scenarios across different head-end systems and vendors. However, some head-end systems may have vendor-specific device event types that are not covered by the standard device event types. In order to manage these additional device events, SGG allows users to create new standard device event types and map them to the vendor-specific device event types. According to the Oracle Utilities Smart Grid Gateway User Guide, apart from creating the new standard device event type "admin data", the other step that should be done to represent the new standard device events is:
* Extend the Landis + Gyr device event mapping extendable lookup such that it maps each of the Landis + Gyr specific device event names to the new standard device event names. This will ensure that SGG can recognize and process the vendor-specific device events and map them to the corresponding standard device events.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 5: Device Events, Section 5.2: Device Event Types; Section 5.3: Device Event Mapping
質問 # 17
Service Order Management is used to orchestrate service order processes such as Enable Service and Disable Service.
Which Oracle Utilities Application Framework (OUAF) admin data should be created for a custom Service Order Management process?
- A. Device type
- B. Device event type
- C. Consumer contract type
- D. Activity type
正解：D
解説：
Explanation
An activity type is an Oracle Utilities Application Framework (OUAF) admin data that should be created for a custom Service Order Management process. An activity type defines the type of work that needs to be performed on a service point or device, such as enable service or disable service. An activity type also defines the following attributes:
* The status and priority of the activity
* The business object and algorithm that are used to process the activity
* The fields and validations that are required for the activity
* The notifications and escalations that are triggered by the activity
* The dependencies and relationships that exist between different activities An activity type is used to create and manage service orders, which are records that store the details and outcomes of the work performed on a service point or device.
質問 # 18
The Vector and Service Quantity Math usage rule facilitates the configuration of complex vector calculations.
It is based on a series of underlying services with vectors configured as input to the calculations.
What are THREE typical uses of the usage rule?
- A. Finding max values
- B. Performing Array math
- C. Finding coincident peaks
- D. Performing math formulas on interval data
- E. Converting interval data to scalar reads
正解：B、C、D
解説：
Explanation
The Vector and Service Quantity Math usage rule facilitates the configuration of complex vector calculations.
It is based on a series of underlying services with vectors configured as input to the calculations. Some typical uses of the usage rule are:
* Finding coincident peaks: This is a calculation that finds the highest demand value for each interval across multiple service points or devices.
* Performing Array math: This is a calculation that performs arithmetic operations on arrays of interval data, such as addition, subtraction, multiplication, or division.
* Performing math formulas on interval data: This is a calculation that performs mathematical functions on interval data, such as logarithm, exponentiation, square root, or trigonometry.
Finding max values is not a typical use of the Vector and Service Quantity Math usage rule. Finding max values is a simple calculation that finds the highest demand value for each service point or device.
Converting interval data to scalar reads is not a typical use of the Vector and Service Quantity Math usage rule. Converting interval data to scalar reads is done by using other usage rules, such as Interval Data Scalar Read Rule.
質問 # 19
A customer is starting an Advanced Meter Infrastructure (AMI) roll-out initiative and they plan to replace their legacy scalar time-of-use (TOU) meters with smart meters. They want customer information system (CIS) to continue to bill for the same TOU periods and they do not want to change the CIS rates.
In which THREE ways can you configure Meter Data Management (MDM) to support this requirement?
- A. Add the TOU mapping rule to the existing usage calculation group.
- B. Write a custom algorithm to determine the proper rate.
- C. Add an extendable lookup value containing the new device configuration type and the new usage calculation group.
- D. Add a new usage calculation group with a TOU mapping rule.
- E. Set up the new usage calculation group to be identified dynamically by plug-in logic supplied on the usage subscription's type.
正解：A、C、E
解説：
Explanation
To support the requirement of replacing legacy scalar time-of-use (TOU) meters with smart meters without changing the CIS rates, you can configure Meter Data Management (MDM) in the following ways:
* Add an extendable lookup value containing the new device configuration type and the new usage calculation group: This is used to map the new device configuration type that is used for smart meters to a new usage calculationgroup that will be used to calculate bill determinants for smart meters. An extendable lookup value is a configurable value that can be used to define business rules or relationships between different objects.
* Add the TOU mapping rule to the existing usage calculation group: This is used to map the TOU periods of smart meters to the TOU periods of legacy meters. A TOU mapping rule is a usage calculation rule that is used to convert interval measurements into scalar measurements based on different TOU periods.
* Set up the new usage calculation group to be identified dynamically by plug-in logic supplied on the usage subscription's type: This is used to determine which usage calculation group will be used for each usage subscription based on certain criteria, such as device configuration type or service point type. A plug-in logic is a custom logic that can be developed by using Groovy scripting language or Java programming language.
You do not need to write a custom algorithm to determine the proper rate, which is a complex logic that can be developed by using Groovy scripting language or Java programming language. The proper rate can be determined by using the existing CIS rates and mapping them to smart meter TOU periods.
You do not need to add a new usage calculation group with a TOU mapping rule, which is a collection of usage calculation rules that are used to calculate bill determinants from measurements. You can add the TOU mapping rule to the existing usage calculation group instead of creating a new one.
質問 # 20
The interval proxy day estimation Validation, Estimation, and Editing (VEE) rule estimates missing intervals by selecting interval data to average from a list of days that are most like the day being estimated. This is achieved by measuring the component comparison periods.
What is used to define the proxy?
- A. Neighbor
- B. Weather data
- C. Customer class profile
- D. Like premise
正解：B
解説：
Explanation
The interval proxy day estimation VEE rule is a rule that estimates missing intervals by selecting interval data to average from a list of days that are most like the day being estimated. This is achieved by measuring the component comparison periods, which are periods of time that are used to compare different days based on certain criteria. According to the Oracle Utilities Meter Data Management Business User Guide, one factor that is used to define the proxy or the list of days that are most like the day being estimated is:
* Weather data: This is data that indicates the temperature or other weather conditions for a given day.
Weather data can be used to select days that have similar weather patterns or variations as the day being estimated.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.3:
Validation, Estimation, and Editing; Section 8.3.2: Interval Proxy Day Estimation
質問 # 21
Which relationship must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM)?
- A. Usage factor
- B. Usage rule
- C. Usage subscription
- D. Usage transaction
正解：C
解説：
Explanation
A usage subscription is a relationship that must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM). A usage subscription 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.
You do not need to establish a usage factor, a usage transaction, or a usage rule with an external system or a service provider before creating bill determinants. A usage factor is a value that is used to adjust or convert measurements based on certain criteria. A usage transaction is a record that stores the bill determinants and other usage information for a usage subscription. A usage rule is a rule that is used to calculate, validate, or estimate bill determinants based on certain criteria.
質問 # 22
Which TWO functions can the service point-measurement cycle relationship of Meter Data Management (MDM) perform?
- A. Initiate request of bill determinants from subscribing systems.
- B. Create hand-held download read activities.
- C. Create optimal meter reader routes by measurement cycle.
- D. Initiate push of bill determinants ta subscribing systems.
正解：A、D
解説：
Explanation
The service point-measurement cycle relationship of Meter Data Management (MDM) can perform the following functions:
* Initiate request of bill determinants from subscribing systems: A subscribing system is an external system or service provider that receives bill determinants from MDM. A bill determinant is a value that is used to calculate a bill for a service point or device. The service point-measurement cycle relationship can initiate a request of bill determinants from subscribing systems based on the measurement cycle schedule. A measurement cycle schedule defines the dates on which devices are scheduled to be read for a given measurement cycle. A measurement cycle defines the schedule for manual meter reading of devices at service points in that cycle.
* Initiate push of bill determinants to subscribing systems: The service point-measurement cycle relationship can also initiate a push of bill determinants to subscribing systems based on the measurement cycle schedule. This means that MDM can send bill determinants to subscribing systems automatically or on demand.
The service point-measurement cycle relationship cannot perform the following functions:
* Create optimal meter reader routes by measurement cycle: A meter reader route is a sequence of service points or devices that are assigned to a meter reader formanual meter reading. A meter reader route is not created by the service point-measurement cycle relationship, but by using other configurations, such as route type or route sequence.
* Create hand-held download read activities: A hand-held download read activity is an activity that downloads measurement data from a hand-held device to MDM. A hand-held download read activity is not created by the service point-measurement cycle relationship, but by using other configurations, such as activity type or activity status.
質問 # 23
Which THREE are best practices for measurement retention?
- A. Derive demand from interval data to prevent storing extra data.
- B. Keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes.
- C. Derive time-of-use (TOU) values with interval data to prevent storing extra data.
- D. Keep scalar measurements in the customer read tables to stay consistent.
- E. Use Information Lifecycle Management (ILM) processes to help archive data.
正解：A、C、E
解説：
Explanation
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.
質問 # 24
Which TWO Validation, Estimation, and Editing (VEE) rules are typically configured on a project for consumption synchronization processes?
- A. Low check: Check for invalid low usage.
- B. Interval adjustment from scalar: Adjust the interval curve to the register consumption.
- C. Sum check: Ensure the two measuring components are in sync.
- D. Unit of Measure (UOM) check: Ensure UOMs are correct.
正解：B、C
解説：
Explanation
Consumption synchronization is a process that ensures that the usage data from different measuring components (such as interval and scalar) are consistent and aligned. Consumption synchronization can be performed using various methods, such as adjustment, estimation, or derivation. According to the Oracle Utilities Meter Data Management Business User Guide, two types of VEE rules that are typically configured on a project for consumption synchronization processes are:
* Interval adjustment from scalar: This is a rule that adjusts the interval curve to match the register consumption. Interval adjustment from scalar can be used to correct any discrepancies between interval and scalar usage data due to factors such as clock drift or multiplier errors.
* Sum check: This is a rule that ensures that the usage data from two measuring components are in sync.
Sum check can be used to compare the usage data from different measuring components (such as import and export) and flag any differences or errors.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.3:
Validation, Estimation, and Editing; Section 8.5: Consumption Synchronization
質問 # 25
3. For a Meter Data Management (MDM) implementation, customer information system (CIS) requires the following bill determinants:
* For scalar meters, scalar consumption values will be sent to CIS.
* For interval meters, billed on time-of-use (TOU) rates, consumption values will be provided based on the specific TOU periods, for example: on-peak, off-peak, and shoulder.
Based on these requirements, which TWO usage subscription or usage calculation group configuration options should you set up to allow an implementation to send bill determinants to CIS?
- A. Scalar specific group as a fallback Validation, Estimation, and Editing (VEE) group.
- B. TOU usage group as a fallback VEE group.
- C. TOU usage rule with a valid usage group.
- D. Scalar usage calculation rule with a valid usage group.
正解：D
解説：
Explanation
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
質問 # 26
A time-of-use (TOU) template's interval size controls the values allowed as start and end times. A template can be used to generate TOU data for TOU maps whose seconds per interval (SPI) is divisible by the template's SPI.
For what can you use a 60-minute template?
- A. To generate TOU data for 120-minute and 1440-minute TOU maps.
- B. To only generate TOU data for minute TOU maps.
- C. To generate TOU data for 6G-, 15-, and 5-minute TOU maps.
- D. To only generate TOU data for 30-minute TOU maps.
- E. To generate TOU data for 120-minute TOU maps.
正解：B
解説：
Explanation
A time-of-use (TOU) template is used to define the start and end times of TOU periods for different days of the week and seasons of the year. A TOU template has an interval size that controls the values allowed as start and end times. For example, if the interval size is 60 minutes, then the start and end times must be multiples of
60 minutes, such as 00:00, 01:00, 02:00, and so on. A TOU template can be used to generate TOU data for TOU maps whose seconds per interval (SPI) is divisible by the template's SPI. For example, if the template's SPI is 3600 (60 minutes), then it can be used to generate TOU data for TOU maps whose SPI is 3600, 1800 (30 minutes), 1200 (20 minutes), 900 (15 minutes), 600 (10 minutes), 300 (5 minutes), and so on. Therefore, the correct answer is D.
References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 4: Time-of-Use Data Management, Section 4.1: Time-of-Use Templates
質問 # 27
From where is the final measurement condition code created?
- A. Pre-VEE condition code
- B. Raw condition code
- C. Post-VEE condition code
- D. Condition code sent from head-end system (HES)
正解：C
解説：
Explanation
Measurement condition codes are codes that indicate the quality or status of measurement data, such as raw, estimated, edited, validated, or final. Measurement condition codes are assigned at different stages of processing measurement data and can affect how measurement data are used for billing or analysis purposes.
According to the Oracle Utilities Meter Data Management Business User Guide, the final measurement condition code is created from:
* Post-VEE condition code: This is the condition code that is assigned after validation, estimation, and editing (VEE) processing has been performed on measurement data. VEE processing is a set of rules and algorithms that check and correct measurement data for any gaps, errors, or anomalies. The post-VEE condition code reflects the outcome of VEE processing and determines whether measurement data are ready for export or further processing.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 7: Measurements, Section
7.2: Measurement Condition Codes
質問 # 28
Which statement is true about usage transaction?
- A. It is created by an external source or Meter Data Management (MDM), which uses the usage calculation engine to generate usage values.
- B. It is created by an external source or MDM, which uses the usage calculation engine to generate a final value. VEE can be configured and usage transaction is saved.
- C. It must be created by an external system and it must be stored in the database.
- D. It is created by an external source or MDM, which uses the usage calculation engine to generate a final value. Valuation, Estimation, and Editing (VEE) can be configured but when called in real time, usage transaction may not be saved.
正解：B
解説：
Explanation
A usage transaction is a record that stores the usage information for a usage subscription. A usage transaction can be created by an external source or MDM, which uses the usage calculation engine to generate a final value. VEE can be configured and usage transaction is saved.
It is not true that a usage transaction is created by an external source or MDM, which uses the usage calculation engine to generate usage values. Usage values are intermediate values that are used to calculate the final value.
It is not true that a usage transaction is created by an external source or MDM, which uses the usage calculation engine to generate a final value. VEE can be configured but when called in real time, usage transaction may not be saved. VEE can be configured and usage transaction is always saved.
It is not true that a usage transaction must be created by an external system and it must be stored in the database. A usage transaction can be created by MDM and it can be deleted from the database.
質問 # 29
In which THREE situations would you use a dynamic option?
- A. The utility has a program that credits customers for conservation during critical peak periods.
- B. The utility has a program where customers can optionally participate in demand response (DR) programs.
- C. A consumer receives credit for consumption during a critical peak period (CPP) event that is lower than their "normal* consumption.
- D. The scalar meter-read download process creates an activity each time a scalar measuring component is scheduled to be read.
- E. 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.
正解：A、B、E
解説：
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
質問 # 30
Time-of-use (TOU) maps can be used by various functions in Meter Data Management (MDM). Which of the following is a typical scenario in which TOU maps are applied?
- A. To map usage data with geospatial applications.
- B. To initial measurement data (IMD) records for creating summarized TOU final measurements.
- C. To usage transactions and final measurements for billing and analytical purposes.
- D. To determine the time a user worked an an incorrect measurement.
正解：C
解説：
Explanation
Time-of-use (TOU) maps can be used by various functions in Meter Data Management (MDM). A TOU map is a configuration that defines how interval measurements are converted into scalar measurements based on different TOU periods. A typical scenario in which TOU maps are applied is to usage transactions and final measurements for billing and analytical purposes. A usage transaction is a record that stores the bill determinants and other usage information for a usage subscription. A final measurement is a record that stores the measurement data that has been validated, edited, and estimated. TOU maps can be applied to usage transactions and final measurements to calculate bill determinants or perform analysis based on different TOU periods.
TOU maps are not applied to initial measurement data (IMD) records for creating summarized TOU final measurements. IMD records are records that store the raw measurement data that is received from smart meter systems or other sources. IMD records are not converted into final measurements by using TOU maps, but by using VEE rules.
TOU maps are not used to determine the time a user worked on an incorrect measurement, which is a function that is performed by using audit trails or logs. TOU maps are not used to map usage data with geospatial applications, which is a function that is performed by using location data or coordinates.
質問 # 31
......
1z0-1091-22試験問題集でPDF問題とテストエンジン：https://www.passtest.jp/Oracle/1z0-1091-22-shiken.html
実際に出る1z0-1091-22試験問題集には正確で更新された問題：https://drive.google.com/open?id=1PehC56L-L0I759NvW17aoCzOJcvUw3Tm