
[2023年11月11日] 有効な1z0-1091-22テスト解答1z0-1091-22試験PDF問題を試そう
有効なMeter Data Management 1z0-1091-22問題集はあなたの合格を必ず保証します
質問 # 12
Different validation, estimation, and editing (VEE) rules can be applied based on the VEE roles that categorize the source of the measurement data.
Which THREE VEE roles are provided as part of the base product?
- A. Estimation
- B. Manual override
- C. Retry
- D. Initial load
- E. Customer provided
正解:B、D、E
解説:
Explanation
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.
質問 # 13
Which statement is true about usage transaction?
- A. 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.
- B. 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.
- C. It is created by an external source or Meter Data Management (MDM), which uses the usage calculation engine to generate usage values.
- D. It must be created by an external system and it must be stored in the database.
正解:A
解説:
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.
質問 # 14
Which step should you perform to configure commands in a SaaS environment?
- A. Configure the following processing methods: Unit of Measure (UOM) Translation, Initial Measurement Creation, and Device Event Mapping.
- B. Create key rings and key pairs.
- C. Configure File Storage Configuration (Fl-RleStorage) extendable lookup.
- D. Configure outbound and inbound communications (Request/Response model).
- E. Create Object Storage locations (or buckets).
正解: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. According to the Oracle Utilities Smart Grid Gateway User Guide, one step that should be performed to configure commands in a SaaS environment is:
* Create Object Storage locations (or buckets). These are containers that store files and data in OCI Object Storage. Object Storage locations can be used to store command requests and responses between Oracle Utilities Meter Data Management and Smart Grid Gateway.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.4: Command Configuration
質問 # 15
A small building with five metered apartments has common areas used by all residents. The common areas are metered separately, and the common usage needs to be spread evenly across residents.
How should you configure the solution to bill each resident accurately?
- A. Calculate the usage for each apartment by using customer information system (CIS).
- B. Set up a virtual meter to include the apartment usage and 20% of the common areas.
- C. Use a derivation algorithm to include 20% of the common areas with the apartment accounts.
- D. Each apartment's usage subscriptions must have two service paints, one for the apartment and one for
20% of the common areas.
正解:B
解説:
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.
質問 # 16
Which THREE Validation, Estimation, and Editing (VEE) rules are provided by the base Meter Data Management (MDM) product that you can include in a VEE group?
- A. Negative consumption check
- B. High/low check
- C. Positive consumption check
- D. Estimate data based on nearby addresses
- E. Interval averaging
正解:A、B、C
解説:
Explanation
The base Meter Data Management (MDM) product provides several Validation, Estimation, and Editing (VEE) rules that you can include in a VEE group. A VEE group is a collection of VEE rules that are used to validate, estimate, and edit measurements based on certain criteria. Some of the VEE rules that are provided by the base MDM product are:
* Positive consumption check: This is a rule that checks if the consumption value of a measurement is positive. If the consumption value is negative, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
* Negative consumption check: This is a rule that checks if the consumption value of a measurement is negative. If the consumption value is positive, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
* High/low check: This is a rule that checks if the consumption value of a measurement is within a predefined range. If the consumption value is above or below the range, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
Estimate data based on nearby addresses is not a VEE rule that is provided by the base MDM product. This is a custom VEE rule that can be developed by using Groovy scripting language or Java programming language.
Interval averaging is not a VEE rule that is provided by the base MDM product. This is a usage calculation rule that is used to calculate derived values from interval measurements by averaging them over a certain period.
質問 # 17
You want to create Smart Grid Gateway (SGG) Payload Processing extendable lookup values. Which Groovy Library Method would you configure in the User Exit Interceptors section?
- A. Events Set Parser and Set Transformer
- B. Initial Measurements and Device
- C. SOAPSNDRand RTHTTPSNDR
- D. Get Parser and Get Transformer
正解:A
解説:
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.
質問 # 18
Which TWO functions can the service point-measurement cycle relationship of Meter Data Management (MDM) perform?
- A. Initiate push of bill determinants ta subscribing systems.
- B. Create optimal meter reader routes by measurement cycle.
- C. Create hand-held download read activities.
- D. Initiate request of bill determinants from 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.
質問 # 19
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 only generate TOU data for minute TOU maps.
- B. To generate TOU data for 6G-, 15-, and 5-minute TOU maps.
- C. To generate TOU data for 120-minute and 1440-minute TOU maps.
- D. To generate TOU data for 120-minute TOU maps.
- E. To only generate TOU data for 30-minute TOU maps.
正解:A
解説:
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
質問 # 20
From where is the final measurement condition code created?
- A. Condition code sent from head-end system (HES)
- B. Post-VEE condition code
- C. Raw condition code
- D. Pre-VEE condition code
正解:B
解説:
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
質問 # 21
Devices are often added to Meter Data Management (MDM) via a synchronization process. Device configuration business objects (BOs) can be configured to use Synchronization Add BO to determine the appropriate BO for the new device.
What is Synchronization Add BO associated with?
- A. Options on Dl-Device Configuration BO
- B. Business service associated with Dl-Device Configuration BO
- C. Validation algorithm on Dl-Device Configuration BO
- D. Lifecycle algorithm on Dl-Device Configuration BO
正解:D
解説:
Explanation
Synchronization Add BO is associated with the lifecycle algorithm on Dl-Device Configuration BO. A lifecycle algorithm is a custom logic that can be developed by using Groovy scripting language or Java programming language. A lifecycle algorithm is used to perform certain actions or validations when a business object is created, updated, or deleted. Synchronization Add BO is a parameter that can be configured on the lifecycle algorithm on Dl-Device Configuration BO. Synchronization Add BO is used to determine the appropriate business object for creating a new device based on certain criteria, such as device type or device configuration type.
Synchronization Add BO is not associated with the business service associated with Dl-Device Configuration BO, which is a component that provides the functionality and logic for processing data related to device configuration. Synchronization Add BO is not associated with the options on Dl-Device Configuration BO, which are configurable values that can be used to define business rules or relationships for device configuration. Synchronization Add BO is not associated with the validation algorithm on Dl-Device Configuration BO, which is a custom logic that can be developed by using Groovy scripting language or Java programming language. A validation algorithm is used to perform certain checks or validations on the data entered for device configuration.
質問 # 22
You need to set up a configuration that allows service points to be used with various meters. This configuration should support interval, time of use, and scalar devices.
How would you meet this requirement?
- A. Configure one service point type and three device types, and then configure the three valid device types on the service point type.
- B. Configure one service point, three devices, and set any one of the three devices to be related to the service point as required by the data scenarios.
- C. Configure one service paint, one device, and three measuring components to be related to the service point as required by the data scenarios.
- D. Configure three service points and set any one of the three devices to be related to the service point as required by the data scenarios.
正解:C
解説:
Explanation
A service point is a record that represents a physical location where a utility provides service to a customer. A service point can have one or more devices associated with it to measure the usage of the service. A device is a record that represents a physical meter or other equipment that records usage data. A device can have one or more measuring components associated with it to represent different types of usage data, such as interval, time of use, or scalar. According to the Oracle Utilities Meter Data Management Business User Guide, to set up a configuration that allows service points to be used with various meters and support interval, time of use, and scalar devices, one way to meet this requirement is:
* Configure one service point, one device, and three measuring components to be related to the service point as required by the data scenarios. This can be done by creating a service point record and associating it with a device record that represents the meter. Then, creating three measuring component records that represent different types of usage data (interval, time of use, and scalar) andassociating them with the device record. Depending on the data scenarios, different measuring components can be used to collect and process usage data for the service point.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 3: Asset Management, Section 3.1: Service Points; Section 3.3: Devices; Section 3.5: Measuring Components
質問 # 23
How do you configure the derived values that are relevant for a device?
- A. Configure the derived values on the device type for the derived values to be defined on the device.
- B. Configure the derived values on the measuring component for the measuring components to be defined on the device.
- C. Configure the derived values on the measuring component type for the measuring components to be defined on the device.
- D. Configure the derived values an the final measurement type for the measuring components to be defined on the device.
正解:C
解説:
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.
質問 # 24
In which THREE situations would you use a dynamic option?
- A. A consumer receives credit for consumption during a critical peak period (CPP) event that is lower than their "normal* consumption.
- B. The utility has a program that credits customers for conservation during critical peak periods.
- C. 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.
- D. The scalar meter-read download process creates an activity each time a scalar measuring component is scheduled to be read.
- E. The utility has a program where customers can optionally participate in demand response (DR) programs.
正解:B、C、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
質問 # 25
Which TWO functions can the service point-measurement cycle relationship of Meter Data Management (MDM) perform?
- A. Initiate push of bill determinants ta subscribing systems.
- B. Create optimal meter reader routes by measurement cycle.
- C. Create hand-held download read activities.
- D. Initiate request of bill determinants from 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.
質問 # 26
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. Set up the new usage calculation group to be identified dynamically by plug-in logic supplied on the usage subscription's type.
- B. Write a custom algorithm to determine the proper rate.
- C. Add the TOU mapping rule to the existing usage calculation group.
- D. Add a new usage calculation group with a TOU mapping rule.
- E. Add an extendable lookup value containing the new device configuration type and the new usage calculation group.
正解: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.
質問 # 27
Which THREE statements are true about the Subtractive Interval Data functionality?
- A. It converts engineering units into reads.
- B. It validates consumption in initial measurement data (IMD).
- C. The IMD load processes calculate consumption in engineering units.
- D. A new reading condition field ensures that you do not lose the reading quality when a meter's consumption is estimated.
- E. You can optionally validate for rollover exceptions and negative consumption calculations.
正解:C、D、E
解説:
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.
質問 # 28
If a project is setting up meter commands with a head-end system (HES), which TWO components should you configure to support the inbound responses from HES?
- A. Outbound message type
- B. Master configurations
- C. Message sender
- D. Inbound web services
正解:C、D
解説:
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 inbound and outbound communication between the two systems using web services and message queues. According to the Oracle Utilities Smart Grid Gateway User Guide, if a project is setting up meter commands with a head-end system (HES), two components that should be configured to support the inbound responses from HES are:
* Inbound web services: These are web services that are exposed by SGG to receive messages from HES.
Inbound web services can be used to receive responses from HES for commands that were sent by SGG or other systems.
* Message sender: This is a component that sends messages from SGG to other systems using message queues. Message sender can be used to send responses from HES to Oracle Utilities Meter Data Management or other systems.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 2: Architecture Overview; Chapter 3:
Communication; Chapter 4: Commands
質問 # 29
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. Customer class profile
- B. Like premise
- C. Neighbor
- D. Weather data
正解:D
解説:
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
質問 # 30
A customer needs to validate high or low tolerances such that exceeding in either direction must not allow the reading to be finalized. In addition, all other validation rules that are configured must be applied to the readings.
Which exception severity should you configure in Validation, Estimation, and Editing (VEE) rules?
- A. Terminate
- B. Critical
- C. Informational
- D. Issues
正解:B
解説:
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.
質問 # 31
Which THREE are best practices for measurement retention?
- A. Derive time-of-use (TOU) values with interval data to prevent storing extra data.
- B. Derive demand from interval data to prevent storing extra data.
- C. Use Information Lifecycle Management (ILM) processes to help archive data.
- D. Keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes.
- E. Keep scalar measurements in the customer read tables to stay consistent.
正解:A、B、C
解説:
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.
質問 # 32
......
1z0-1091-22問題集でリアル試験問題でテストエンジン問題集でトレーニング:https://www.passtest.jp/Oracle/1z0-1091-22-shiken.html
1z0-1091-22テスト問題集とオンライン試験エンジン:https://drive.google.com/open?id=1PehC56L-L0I759NvW17aoCzOJcvUw3Tm