Configure Custom Buckets - Asset

Facts and dimension attributes in the dimensional data model provided by Oracle Utilities Analytics Visualization may contain numerical attributes that become more useful when grouping them into categories that represent specific number intervals. This process is often referred to as "binning" or "bucketing." For example, an age attribute value may be assigned to an age bucket such as < 1 Year, 1-5 Years, 5-10 Years, 10-20 Years, or >=20 years.

Utilities business applications support a set of predefined bucket business objects that are used in Analytics Visualization. Intervals representing each bucket must be defined before the analytics solution can use bucket columns.

Note: Bucket configuration does not prevent the definition of multiple buckets for a predefined bucket business object. However, only one bucket definition per bucket business object is supported.

On this page:

Supported Buckets

Buckets must be configured by an administrator before they can be used by the Oracle Utilities Analytics Visualization solution. The following buckets are currently supported.

Dimension

Importance

Bucket Value Ranges (Examples)

Column with Value to Be Bucketed

Column Details

Dimension: Asset

Attribute: Condition Rating Bucket

Asset Condition rating is the assessment score that is calculated based on various assessments that are available for an asset.

Condition Rating Bucket will provide a meaningful illustration to users where condition rating can be structured in different buckets.

Example:

  • 0 to 1: Unrated
  • 1 to 2: Very Good
  • 2 to 3: Good
  • 3 to 4: Average
  • 4 to 5: Poor
  • 5+: Very Poor

W1_ASSET.CONDITION_RATING

Asset.Condition Rating

Bucket Column: Asset.Condition Rating Bucket

Business Object Name: Asset Condition Score Bucket Configuration

Business Object Code: W1-AssetConditionScoreBuckets

Dimension: Asset Location

Attribute: Criticality Bucket

 

Criticality defines the importance of the location in terms of the potential impact of having issues or problems at that location.

Criticality Bucket will provide a meaningful illustration to users where criticality can be structured in different buckets.

Example:

  • 0 to 4: Low
  • 4 to 7: Medium
  • 7 to 9: High
  • 9+: Critical

W1_NODE.CRITICALITY_FLG

Location / Organization.Criticality Flag

Bucket Column: Location / Organization.Criticality Flag Bucket

Business Object Name: Asset Criticality Bucket Configuration

Business Object Code: W1-AssetCriticalityBuckets

Dimension: Work Orders

Attribute: Work Priority Bucket

Work Priority defines the importance of the work in terms of the potential impact of not addressing issues. For example, emergency type work is a higher priority than routine maintenance work.

Work Priority Bucket will provide a meaningful illustration to users where work priority can be structured in different buckets.

Example:

  • 0 to 5: Low
  • 5 to 6: Normal
  • 6 to 7: High
  • 7 to 9: Urgent
  • 9+: Emergency

W1_WO.WORK_PRIORITY_FLG

Work Order.Work Priority Flag

Bucket Column: Work Order.Work Priority Flag Bucket

Business Object Name: Work Priority Bucket Configuration

Business Object Code: W1-WorkPriorityBuckets

Back to Top

Configure Custom Buckets

  1. Sign in to the Oracle Utilities application.
  2. In the search bar at the top of the screen, search for the "Bucket Configuration" menu and open it.

  3. In the Description field, enter the percent symbol (%) to search for any predefined buckets.

    Note: A newly installed application will not have any default configurations. If there are any records available, results will be displayed based on the search criteria. Select any of the bucket configuration records returned from search results to navigate and view the configuration.

  4. To add a new bucket configuration, click Add at the top right of the page.
  5. Select an option from the Bucket Configuration Business Objects menu. These options represent the placeholder for the bucket definition.
  6. In the Bucket Configuration field, define the bucket configuration code and its description. The code must be unique and should reflect the purpose of the bucket. For example, if the purpose of the bucket is for binning Asset Condition Scores, then your bucket configuration code could be CM-CONDITIONSCORE, where CM is a prefix that identifies that it is custom, and where CONDITIONSCORE represents that it is for binning Asset Condition Scores.
  7. In the Bucket Value Ranges section, define a sequence of intervals for the start and end ranges that represents how the data should be grouped or binned. In most cases, the ranges must be continuous, and the start range must be the end range of the previous interval. The existing functionality will assign the attribute being binned into a range using the formula: Start Range <= x < End Range, where x is the numerical attribute being binned. The intervals must include all possible values of the underlying attribute that is binned into buckets. It is best practice to use a high value for the last end range to ensure that a large value is included in the interval defining the default bucket.

Important Constraints: Follow these guidelines to avoid incorrect behavior of buckets.

  • Only one bucket configuration for each Bucket Business Object is supported by Analytics Visualization. Otherwise the application will return incorrect values and may double-count measures.
  • The bucket definition must have intervals that do not overlap and must cover all possible values. Otherwise, the application will return incorrect values and may under- or double-count measures.

Back to Top