Setting Up TOU Pricing Rate Components

This section describes how to define your TOU Pricing rate components. Refer to Time of Use Mapping and Pricing for background information.

Note:

Define Rate Schedule, Rate Version and other Rate Components. Before creating your TOU pricing rate component, you must set up a Rate Schedule. Refer to Setting Up A Rate Schedule for more information. You will also need to set up a rate version and possibly set up other types of rate components. Refer to Defining Rate Versions and Defining Rate Components for more information.

When you are ready to set up your TOU pricing rate component, open Menu > Rates > Rate Version Classic > Search. Choose the rate schedule and version that this component should belong to. Open its context menu, and select Go to Rate Component Classic > Add to add a new rate component.

Description of Page

Refer to Rate Component - Main Information for information about the common fields on this page. When defining a TOU Pricing rate component, additional fields become available to you. The following information will help you to set up your TOU Pricing rate components.

If the algorithm used by this rate component, only performs mapping and does not produce bill lines, indicate that this is FCPO.

The Value Type and Value Source are optional. If your algorithm performs pricing logic, then you will probably need to define a bill factor here. If your calculation algorithm only performs mapping, than you may not require any value here.

Indicate whether or not this rate component is Seasonal. Refer to Rate Component - Main Information for more information about seasonal rate components.

The UOM is available for use by your calculation algorithm. It could be used, for example, by a mapping algorithm to produce SQ quantities with a different unit of measure, assuming that the algorithm knows how to convert from one UOM to another. Note that the algorithms provided with the system do not use this field.

The SQI is available for use by your calculation algorithm. It could be used, for example, by a mapping algorithm to produce SQ quantities with a different SQI. Note that the TOU mapping and pricing algorithms provided with the system will use this field, if populated, to produce SQI quantities with this SQI value.

Measures Peak Qty and GL Statistical Qty behave the same way they do for SQ quantity rate components. Refer to How To Set Up Service Quantity Rate Components for more information.

The Error if No Value field is available for you to use in the calculation algorithm.

Indicate the Calc Algorithm that the system will use to map the interval quantities to time of use values.

  • The system provides the following classic TOU mapping/pricing algorithms that are available for use here: RCTMS performs mapping of time of use only and RCTMPS performs both mapping and pricing, producing the necessary bill calculation lines.

If these algorithms do not provide you with the logic you require, you will need to create a new algorithm (refer to Setting Up Algorithms). The above existing algorithms should be used as a sample if you have to write a new algorithm type.

Note:

The calculation algorithm's main purpose is to create bill calculation lines. However, the algorithm may populate other information for the bill, for example, it may add to the SQ or register read collection or it may overwrite the description on bill.

Indicate the Audit Algorithm to be used when a CSR wants to drill down into the details of a bill line that was calculated using this Rate Component.

  • The system provides the following audit algorithm that is available for use here: RCTPRS-ADT.

If this algorithm does not provide you with the logic you require, you will need to create a new algorithm (refer to Setting Up Algorithms). The above existing algorithm should be used as a sample if you have to write a new algorithm type.

Note:

The audit algorithm should produce the same results as the Calc Algorithm. They are separated because they have different responsibilities. For example, the Calc Algorithm should produce bill lines, but the Audit Algorithm should not. They share common logic related to accessing and processing the appropriate interval data records. As a result, it is recommended that these two programs share a common code which accesses and processes the interval data. The above algorithms, provided by the system, behave this way and should be used as samples.

Refer to Interval Billing Calculation Details to understand where a CSR may view the calculation details for a bill calc line, using this algorithm.

Indicate the Interval Profile Rel Type. This indicates to the system the profile, linked to the SA, which contains the interval quantities to be mapped. Refer to Business Role of Interval Data and Setting Up Profile Relationship Types for more information.

If the classic TOU map differs for different service agreements, indicate the TOU Map Relationship Type. The system uses this information to find the correct classic TOU map linked to the SA. Refer to Business Role of a TOU Map and Setting Up TOU Map Relationship Types for more information.

If ALL service agreements linked to the rate use the same map, indicate the classic TOU Map ID.

Enter the verbiage to appear on the customer's bill in Description On Bill and turn on the Print switch. Refer to Rate Version - Bill Print Info for more information about these fields.