Skip to main content
Aria Knowledge Central

Manage Monetized Usage Data

When usage records process successfully, Aria Allegro creates a monetized usage record (transaction_unit) to capture rating results and future discounting. Monetized usage data follows the harmonized Allegro data model. The mediation mapping configuration converts raw usage data into the Allegro usage container model. The Usage Processing stream (rating) enriches this container, and the system stores the data in the monetized usage record.

Rating/Discounting Impact in a Monetized Usage

Aria Allegro currently supports rating usage records. The roadmap includes discounts for usage records, which require changes in core Aria to prevent double application—once in Allegro and once in core Aria. Additionally, catalog discounts must support Allegro.

During usage rating, the Allegro engine applies currency, accumulator, and allowance impacts as configured in the price plan. Understanding how Allegro applies and stores these impacts is essential.

The following steps outline the process, excluding complexities of various pricing models.

  1. Assume a usage record of quantity 100 rated across two tiers: 40 units at $1 and 60 units at $0.5. An allowance of 90 units is available, and the quantity accumulates in an accumulator.
  2. The rating engine applies impacts as follows:
    1. The first tier is evaluated, adding a currency impact of $40 for 40 units. The Impact Type is set to RATING, and the offer Type is set to PRICE to support future discounts, commissions, and revenue share. Tier min and max values are set.
      1. With 90 units of allowance available:
        1. An allowance impact of 40 is added. The remaining allowance is 50 units.
        2. A currency offset impact of –$40 is added for 40 units consumed by the allowance. The Impact Type is set to RATING, and the offer Type is set to ALLOWANCE. Tier min and max values are set. This results in a net first-tier currency impact of $0 ($40 – $40).
      2. An accumulator impact of 40 is added for the quantity, as configured in the price plan.
    2. The second tier is evaluated, adding a currency impact of $30 for 60 units at $0.5 each. The Impact Type is set to RATING, and the offer Type is set to PRICE. Tier min and max values are set.
      1. With 50 units of allowance remaining:
        1. An allowance impact of 50 is added. Remaining allowance is 0.
        2. A currency offset impact of –$25 is added for 50 units consumed by the allowance. The Impact Type is set to RATING, and the offer Type is set to ALLOWANCE. Tier min and max values are set. This results in a net second-tier currency impact of $5 ($30 – $25).
      2. An accumulator impact of 60 is added for the quantity, as configured in the price plan.
    3. The total impacts for the usage record are:
      1. Allowance impact of 90 (40 from first tier, 50 from second tier)
      2. Accumulator impact of 100 (40 from first tier, 60 from second tier)
      3. Net currency impact of $5 ($40 – $40 + $30 – $25)
    4. In future, when discounts are added, the Impact Type will be set to DISCOUNTING, and the offer Type to Discounts.

A sample screenshot (not the exact use case, but showing a flat price with allowance) is shown below:

MMU-01.png

View Monetized Usage Data

To view raw usage data and details for a file with suspended usage records, follow these steps:

  1. Click the Usage switch (Usage/Account toggle) in the navigation pane.
  2. Click the Usage Activity option to expand its sub-menu in the navigation pane.
  3. Click the Usage Data option in the navigation pane.
  4. Click the Monetized Usage Data option in the activity pane.
  5. The system displays the most recent monetized usage records (one page).

This is shown in the following screenshot:

MMU-02.png

View Monetized Usage Record Details

To view raw usage data and details for a file with suspended usage records, follow these steps:

  1. Refer to “View Monetized Usage Data” to access the monetized usage page.
  2. Click the Id Link for a monetized usage record in the field. This opens a drawer showing the record's details.
  3. The drawer displays these data sections:
    1. Header attributes—key attributes shown at the top of the drawer by default.
    2. Other Usage data—a minimize/maximize bar to view other usage container attributes. The rating engine enriches the usage container via the usage processing stream configuration, adding many attributes. The bar is minimized by default.
    3. Flexible attributes—Allegro supports up to 25 flexible attributes usable with mapping configurations. This is a minimize/maximize bar, minimized by default.
    4. Currency—a minimize/maximize bar. Monetized usage can have multiple currency impacts due to tiers, currency offsets for consumed allowances, and future discount offsets. The bar is maximized by default.
    5. Allowance—a minimize/maximize bar shown only when allowance is consumed for the usage record. Monetized usage can have multiple allowance impacts due to tiers and multiple available allowances. The bar is minimized by default.
    6. Accumulators—a minimize/maximize bar shown only when allowance is consumed for the usage record. Monetized usage can have multiple allowance impacts due to tiers and multiple available allowances. The bar is minimized by default.

This is shown in the following screenshot:

MMU-03.png

Filter Attributes for the Monetized Usage Data

  1. Account Number: Filter the monetized usage data using the account number. This is an exact search. Alternatively, you can use the Account Switch at the top and select the account to see the monetized usage only for the account.
  2. Bill Unit Id: Filter the monetized usage data using the bill unit id. Allegro creates a bill unit to keep track of all the usage records for a given billing cycle. This is an exact search.
  3. Start date: Enter or select the start date to search monetized usage. The start date is inclusive (>= 00:00:00 hours). This is a greater than or equal to filter.
  4. End date: Enter or select the end date to search monetized usage. The end date is exclusive (< 00:00:00 hours). This is a less than filter.
  5. Invoice Unit Id: This is for future use when if and when we can capture the invoice id from the billing application back in the monetized usage record.
  6. Service Type: Select the service type from the drop-down list to search monetized usage for that service type. This is an exact match filter.
  7. File Name: Enter the partial or full file name to search if you know the naming convention. This is a case-insensitive partial match filter.
  8. Service Id: Enter the service id for which to search the monetized usage record.  This is also referred to as the Client Plan Instance Id, provisioning id, fulfillment id.
  9. Source Platform: Select the source platform from the drop-down list to search the master usage data. This is an exact match filter.
  10. Usage Type: Enter the usage-type for which to search the monetized usage record. This is a case insensitive partial search filter.

Sort attributes for the monetized usage data

  • Id—Sort ascending or descending by the monetized usage record's id, not the usage id.
  • File Name—Sort ascending or descending by the filename linked to the monetized usage record.
  • Start Date—Sort ascending or descending by the monetized usage record's start date.
  • Usage Type—Sort ascending or descending by the usage type linked to the monetized usage record.
  • Net Amount—Sort ascending or descending by the monetized usage record's net amount.
  • Service Type—Sort ascending or descending by the service type linked to the monetized usage record.
  • Description—Sort ascending or descending by the monetized usage record's description, shown as the service name on the invoice.
  • Bill Unit Id—Sort ascending or descending by the bill unit id linked to the monetized usage record. Allegro assigns a bill unit id for each usage billing cycle, associating monetized usage accordingly.
  • Item Id—Reserved for future use.
  • Service Id—Sort ascending or descending by the service id linked to the usage record, also known as client plan instance id, provisioning id, or fulfillment id.
  • Time Unit—Sort ascending or descending by the time unit linked to the usage record. The time unit model is optional and evaluated only if transaction-attribute-based pricing applies.
  • Zone Unit—Sort ascending or descending by the zone unit linked to the usage record. The zone unit model is optional and evaluated only if transaction-attribute-based pricing applies.
  • Flexible attributes—Currently, the first five flexible attributes support ascending or descending sort.

Export Monetized Usage Data

Aria Allegro allows exporting monetized usage data as XML or PDF files. To export, follow these steps:

  1. Use “View Monetized usage data” to access the monetized usage data.
  2. Apply mandatory and optional filters to narrow the data for export. Large files may take longer or fail to process. For large files, use other methods.
  3. Scroll right in the search results using the horizontal scroll bar.
  4. Locate the 3 vertical dots in the table header on the right and click them to open a sub-menu.
    1. Use the Select columns option to choose columns and drag/drop them to arrange the sequence. The UI updates the table view automatically. This sequence and selection is saved for future access.
    2. Click the Export option to export the file as PDF or EXCEL. The UI creates and downloads the file automatically. The view paginates rows, but the download includes all data.
  5. Locate the file in the Download folder.
TOP
  • Was this article helpful?