Set Up the Snapshot Fact Extracts

This page guides you in setting up the snapshot fact extracts that are included with Oracle Utilities Analytics Meter Data Analytics to capture several SP-based information.

Notes:

Taking weekly or monthly snapshots involves messaging or transforming the measurement data by applying a few core Oracle Utilities Meter Data Management functionalities, such as the conversion of scalar consumption to intervals, the axis conversion, and the time-of-use (TOU) mapping.
It is not easy to replicate in the BI data warehouse the huge volume of measurement data and the core Oracle Utilities Meter Data Management functionalities. Accordingly, these snapshots will be taken into Oracle Utilities Meter Data Management through idiosyncratic batch jobs that will write the results into download tables. These download tables are the ones that the ELT process will replicate and load into the data warehouse.

On this page:

Consumption Snapshot

The consumption snapshot allows KPIs that report on every service point's measured consumption. Weekly or monthly, the system applies a TOU map to the consumption of every active service point. Every resultant TOU code, quantity, and measurement condition results in a separate row on the Consumption Snapshot fact.

Set Up the Consumption Snapshot

These are the configuration steps required for a successful SP Usage Snapshot fact extract:

Navigate to the appropriate Service Point BO and ensure that the correct algorithm is plugged into the system event Usage Snapshot.
Note: This event controls if and how snapshots are taken for the service point. If there is no such algorithm plugged into the service point's BO, the service point is skipped.
1. Deactivate the algorithm Aggregate SP Usage Snapshot and Write to Flat File (D2-SPCA) if it is plugged in and has not been deactivated yet.
2. Plug in the algorithm Aggregate SP Usage Snapshot and Write to Download Table (D2- SP-USG-DL) for the system event Usage Snapshot.
  Note: If the Business Object Algorithm table's caching regime is configured to be Cached for Batch, it is necessary to clear the cache for the algorithm changes to take effect. This can be done by either restarting the thread pool worker or running the Flush All Cache (F1-FLUSH) batch job.
Set up the Usage Snapshot Type(s). See the BI Oriented Extendable Lookups section under BI Configuration portal for details on how to set up the data.
Configure the Service Point Type's usage snapshot configuration. The Service Point Type holds the information that controls the extract:
1. Usage Snapshot Type
2. UOM/TOU/SQI: These are used to define the source measuring component's value identifier that will be TOU mapped. If there are multiple measuring components linked to the service point with such a combination of UOM/TOU/SQI, all will be mapped. If the service point has no measuring components with this combination, it will be skipped.
  Note:
  - A given Service Point Type can have many Usage Snapshot Types for different ways to look at the monthly consumption. This is not limited to just TOU maps. This feature can also be used to create snapshots of different measured values. For example, if a measurement contains two values (actual and normally used), use this feature to create a snapshot of normal consumption, so it could be compared with a different snapshot of actual consumption.
  - If the Service Point Type does not have at least one entry in the Usage Snapshot Configuration list, it means service points of this type do not have their snapshot taken.

Extract the Consumption Snapshot

The Usage Snapshot fact has its own idiosyncratic batch process that takes the monthly or weekly consumption snapshot of all active service points in the system.

Run the Service Point Usage Snapshot Usage Download (D2-USGDL) batch process to retrieve the service point's consumption and populate the SP Usage Snapshot download table.

Service Point Snapshot

The Service Point Snapshot fact allows KPIs that report on the number of service points and devices that are installed over time. Weekly or monthly, the system takes a snapshot of every service point in the system, extracting service point-oriented information as well as information about the service point's install event and the snapshot date.

Set up the Service Point Snapshot

To configure a Service Point Snapshot fact extract:

Navigate to the appropriate Service Point BO and ensure that the correct algorithm is plugged into the system event Service Point Snapshot.
Note: This event controls if and how snapshots are taken for the service point. If there is no such algorithm plugged into the service point's BO, the service point is skipped.
1. In case the algorithm Take SP Snapshot and Write to Flat File (D1-SPSNAP-SE) is plugged in and has not been deactivated yet, deactivate it.
2. Plug in the algorithm Take SP Snapshot and Insert to Download Table (D1-SPSNAPDL).
  Note: If the Business Object Algorithm table's caching regime is configured to be Cached for Batch, it is necessary to clear the cache for the algorithm changes to take effect. This can be done by either restarting the thread pool worker or running the Flush All Cache (F1-FLUSH) batch job.
Set up the Days Since Last Normal Measurement. Refer to the BI Oriented Extendable Lookups section under BI Configuration portal for details on how to set up the data. This will be used to reference the dimension containing the specific age bucket that corresponds with the number of days since the last normal measurement of the service point was received.

Extract the Service Point Snapshot

The Service Point Snapshot fact has its own idiosyncratic batch process that takes the monthly or weekly snapshot of all active service points in the system.

Run the Service Point Snapshot Download (D1-SPSDL) batch process to extract service point's information and populate the SP Snapshot download table.

Service Point Unreported Usage Snapshot

The Unreported Usage Analysis Snapshot fact allows KPIs that show the consumption that has not appeared on usage transactions. Weekly or monthly, the system reviews all active service points and determines the consumption had since the most recent usage transaction in the Sent status.

Set up the Service Point Unreported Usage Snapshot

To successfully configure the Unreported Usage Analysis Snapshot extract, follow these steps:

Navigate to the appropriate Service Point BO and ensure that the correct algorithm is plugged into the system event Unreported Usage Analysis Snapshot.
Note: This event controls if and how snapshots are taken for the service point. If there is no such algorithm plugged into the service point's BO, the service point is skipped.
1. In case the algorithm Analyze Unreported Usage Snapshot and Write to Flat File (D2-SP-UT-AGE) is plugged in and has not been deactivated yet, deactivate it.
2. Plug in the algorithm Take SP Unreported Usage Snapshot and Insert to Download Table (D2-SPUT-DL).
  Note: If the Business Object Algorithm table's caching regime is configured to be Cached for Batch, it is necessary to clear the cache so the algorithm changes take effect. This can be done by either restarting the thread pool worker or running the Flush All Cache (F1-FLUSH) batch job.
Set up the Days Since Last Usage Transaction. This will be used to reference the dimension containing the specific age bucket that corresponds to the number of days since the most recent sent usage transaction of the service point. See the Unreported Usage Analysis Snapshot Type dimension for the setup instructions.
Set up the Unreported Usage Analysis Snapshot Type. See the Unreported Usage Analysis Snapshot Type dimension for the setup instructions.
Configure the Service Point Type's unreported usage analysis snapshot configuration. The Service Point Type holds the following information that controls the extract:
1. Unreported Usage Analysis Snapshot Type
2. UOM/TOU/SQI: These are used to define the source measuring component's value identifier that will be used to calculate the unbilled consumption in the various age buckets. If there are multiple measuring components linked to the service point with such a combination of UOM/TOU/SQI, all will be mapped. If the service point has no measuring components with this combination, it will be skipped.
3. Subscription Type: This is the type of subscription that the analysis will be performed on for this type of snapshot; if the service point is not linked to such a subscription, the fact will be linked to the None US, so that the analysis of consumption with no US can be performed.
4. The Days Since UT buckets and their corresponding descriptions: These are used to categorize the unbilled consumption into different age buckets. For example, if Bucket 1 is defined as 30; Bucket 2 is 45; and Bucket 3 is 60, then any unbilled consumption that is less than or equal to 30 days old will fall into bucket 1, any unbilled consumption that is older than 30 days but less than or equal to 45 days old will fall into bucket 2, and any unbilled consumption that is older than 45 days but is less than or equal to 60 days old will fall into bucket 3.

A separate snapshot can be taken for different subscription types so that a given service point can have multiple snapshots for a given month or week. If the Service Point Type does not have at least one entry in the Unreported Usage Snapshot Configuration list, it means that the service points of this type do not have their snapshot taken.

Extract the Service Point Unreported Usage Snapshot

The Unreported Usage Analysis Snapshot fact has its own idiosyncratic batch process that takes the monthly or weekly snapshot of all active service points in the system.

Run the SP Unreported Usage Snapshot Download (D2-UUSDL) to extract the service point's information and populate the SP Unreported Usage download table.

Service Point VEE Exception Snapshot

The Service Point VEE Exception Snapshot fact allows KPIs that report on VEE Exceptions. Weekly or monthly, the system looks at every service point and count the amount of initial measurement data with and without exceptions. For initial measurement data with exceptions, it further subdivides the count by VEE Exception Type, IMD Type, VEE Severity, VEE Group, and Rule. Every resultant subtotal will have a row on the VEE Exception Snapshot fact.

Set up the Service Point VEE Exception Snapshot

To successfully configure a Service Point VEE Exception Snapshot fact extract:

Navigate to the appropriate Service Point BO and ensure that the correct algorithm is plugged in on the system event SP VEE Exception Snapshot.

Note: This event controls if and how snapshots are taken for the service point. If there is no such algorithm plugged into the service point's BO, the service point is skipped.

In case the algorithm Aggregate SP VEE Exceptions and Write to Flat File (D2- SPVEEEXC) is plugged in and has not been deactivated yet, deactivate it.
Plug in the algorithm Aggregate SP VEE Exceptions and Insert to Download Table (D2-SPVEE-DL).
Note: If the Business Object Algorithm table's caching regime is configured to be Cached for Batch, it is necessary to clear the cache in order for the algorithm changes to take effect. This can be done by either restarting the thread pool worker or running the Flush All Cache (F1-FLUSH) batch job.

Extract the Service Point VEE Exception Snapshot

The Service Point VEE Exception Snapshot fact has its own idiosyncratic batch process that takes the monthly or weekly snapshot of all active service points in the system.

Run the SP VEE Exception Snapshot Download (D2-VEEDL) to extract the service point information and populate the SP VEE Exception download table.