Skip to main content
Aria Knowledge Central

Time Model-Based Pricing

Time model-based pricing enables monetization by day of week, time of day, and holiday calendar attributes. In Aria Allegro, these are derived attributes based on configuration and are part of the Transaction Attribute-based models.

Expected Result:

Pricing based on usage records during weekend or weekday

Variants:

  • Pricing based on usage records during peak or off-peak
  • Pricing based on usage records during special hour windows like 'Premium AM Hours’, 'Premium PM Hours’, 'Night Hours.’
  • Pricing based on usage records during holiday periods
  • Pricing based on usage records combining any of the above.

Setup:

  1. Set up time model configurations under Configurations → Models → Time Model. Refer to the Time Model configurations section under "3. Allegro Configurations → Models → Time Model" for more documentation.
  2. Set up the plan, plan rate schedule, and plan services as required in core Aria.
  3. Set the price offer in Aria Allegro for usage services as follows:
    1. Select Pricing Model as Transaction Attribute-based or Composite, if combining with other models. This adds a section for Transaction Attributes in the UI.
    2. Select Day of week as required. Options include WEEKEND, WEEKDAY, or ANYDAY if day of week should not affect pricing.
    3. Select Time of day as required. Options include PEAK, OFFPEAK, custom hour windows, or ANYTIME if time of day should not affect pricing.
    4. Select Holiday as required. Options include configured holiday names or ANYHOLIDAY to apply pricing to any holiday.
    5. If the zone model is not be considered, then leave them blank.
    6. Add currency (rates), accumulator, and allowance as needed.
  4. Use Add Transaction attribute to add more groups of pricing combinations. Repeat steps 3 and 4 as needed. Please note 
    1. the order of multiple transaction-attribute groups matters. 
    2. For example, a usage record may qualify as PEAK hour and PREMIUM-AM Hours simultaneously. The order of attribute groups in the price offer affects rating.
    3. It is also advisable to configure a default pricing with ANYDAY, ANYTIME, ANYHOLIDAY for a default (fall-through) pricing.
  5. The rest of the setup and process remains unchanged.
TOP
  • Was this article helpful?