Exploring Elements of an RTP Interface

The diagram gives an overview of the components of the RTP interface. The following slides describe the individual components in greater detail.

The settings for the RTP interface are made in three central areas:

• Header data
• Result Parameter
• RTP components

At a more detailed level, the RTP-Interface is made up of several elements:

• RTP Components
  • RTP components define the structure of parameter allocations in the RTP interface.
  • This structure links input, output and result parameters.
  • Different RTP components are required because different periods (such as summer and winter) are usually required for parameter allocations.
  • You can allocate various time groups, such as season groups, day groups and time-of-use groups to an RTP component.
• Formula
  • The formula reproduces the calculation algorithm required for RTP billing.
  • Input and output parameters are defined for a formula
• Result Parameter: The formula works with the individual values in the profile. The result function evaluates the results of formula calculation and summarizes the information to form discrete values, which are passed on to billing via the facts.

• The example illustrates the use of RTP components.
• You can use RTP components to allocate different input parameters to one formula.

Other profiles are allocated to the same formula in a different component.

The icons in the preceding image are used in the RTP interface.

In the Header Data, three elements are defined:

• Formula: used to perform profile calculations
• Interval Length: interval between two values in a profile (for example, 15 minutes, 30 minutes, 60 minutes).
• Division: company-internal key for the division category.
  • Predefined by the Utilities Industry (IS-U) component.

• Formula
  • basis of the profile calculation wherein the RTP calculations take place.
  • allocated to an RTP-Interface
  • Contains a fixed number of input and output parameters to be supplied. (Input and output parameters always refer to those of the formulas allocated to the RTP interface.)
• Formulas predefined by SAP, for example:
  • ACCU_TO_BALANCE: Convert cumulative values to balanced values.
  • COPY01: Copy one profile into two output profiles.
  • INTEGRAL01: Integral creation with resetting function.
  • LIMIT01: Value determination above and below demand limit.
  • MULTI01: Multiplication of demand profile by a factor.
  • SUM01: Addition of profiles (quantities).

• A formula contains a fixed number of input and output parameters. This occurs when a formula is created in the system.
• Formula LIMIT01 has 3 Input Parameters and 4 Output Parameters:

  I01: Measured Load Profile: Quantity O01: Below baseline 1: Quantity

  I02: Baseline 1: Quantity O02: Above baseline 1: Quantity

  I03: Baseline 2: Quantity O03: Above baseline 2: Quantity

  O04: Above baseline 1: Demand

• The formula LIMIT01 allocated to an RTP-Interface will look as follows on the next slide.

• When a formula is allocated to the RTP interface, those Input and Output Parameters from the formula are available to be allocated. However, although all parameters are defined, not all Input and Output Parameters must be allocated within the RTP interface.
• The number of input and output parameters is dependent on the formula chosen. This means that different parameters can be supplied for each RTP component. However, the maximum number remains unchanged.
• Note that in the above example, Input Parameters 1 and 3 are allocated, whereas Input Parameter 2 is not. Output Parameters 1, 2 and 4 are allocated.

Interval Length: intervals between two values in a profile. Defines the number of intervals per day and the time period of the interval.

Predefined By SAP:

• 5 minute intervals - 288 per day
• 10 minute intervals - 144 per day
• 15 minute intervals - 96 per day
• 30 minute intervals - 48 per day
• 60 minute intervals - 24 per day

• Result Number and Description: Identify the result parameter
• Result Function:
  • Allocated to Result Parameters.
  • Define how profile values for a certain period are analyzed.
  • Used to calculate a single value such as a sum, minimum or maximum value.
• RTP Operands: used in RTP rates to transfer the results of the RTP interface to the RTP rate in IS- U-BI.
• Operand Category: fixed predefined characteristic that is allocated to an operand - the Operand Category must match the category of the RTP operand in the Rate Facts.
• Unit of Measurement: Unit of measurement for the consumption profile values (kW, kWh, mWh, and so on.)
• Prorations: Prorations to the RTP operands may be taken into consideration when the RTP-Interface is executed

• Result functions calculate the value that is passed to the result parameters in the RTP-Interface. Result functions define how profile values for a certain period are analyzed and used to calculate a single value such as a sum, minimum or maximum value. Result functions are defined with a description and a function module that performs the calculation.
• When a result parameter is defined, the result function, unit of measurement, and operand categories must also be assigned.
• Result functions can be customized. The following result functions are supplied by SAP:
  • MINIMUM: Minimum Profile Value
  • PEAK: Maximum Profile Value
  • SUM: Total of Profile Values

• Result parameters are assigned in the RTP interface. Result parameters store discrete values. Output parameters are allocated to the result parameters. The result parameters are allocated to the RTP rate in order to facilitate the billable quantities being passed to the IS-U-BI component.
• In the above example, the following result parameters are being defined:
  • Off-Peak Consumption (1)
    • Summer/Weekend/Off-Peak
    • Summer/Weekday/Off-Peak
  • On-Peak Consumption (2)
    • Summer/Weekend/On-Peak
    • Summer/Weekday/On-Peak

• An operand is an assigned value used as input and output parameters in variant programs.
• The operand category classifies the operand for the variant programs.
• RTP operands must first be defined in order to allocate result parameters to operands in the rate facts.
• The operand category must also be defined.
• The operand category must match the category of the RTP operand.

• RTP components define the structure of parameter allocations to the RTP interface and allow you to model the individual calculations in RTP billing.
• Activation defines the dates and time periods for which the RTP component is active. The RTP components can be activated individually. This means that if there are two RTP components in the RTP interface, one can be allocated individually (at the installation level) and one can be allocated generally. When the RTP components are activated, the parameters allocated to the RTP component are used when the interface is executed.
• Input parameter: Profiles are allocated to the input parameters based on the business function (formula).
• Output parameter: Profiles are allocated to the output parameters based on the business function.
• Parameter template: Only defined if the activation type is Use and Activate Individually or Use Individually and Activate Generally. This means that profiles can only be allocated to the input parameter at the installation.

These are typically composed of a Day, TOU and/or Season Group. This structure links input, output and result parameters. Different component codes are required because parameter allocations require different period patterns (such as summer and winter). Different periods can be allocated (such as Season, Day and TOU Groups) to an RTP component. The RTP components allow you to model billing for different parts of a profile in the RTP interface. For example, a separate RTP Component for on- and off-peak periods and an RTP component that determines the maximum demand for the entire period.

• RTP components define the structure of the parameter allocations in the RTP interface. This structure links the input, output and result parameters. This structure also defines the period for billing. Some RTP components are based on time groups such as:
  • Season groups
  • Day groups
  • Time-of-use groups
• Various RTP components may be required to support different periods (such as summer and winter) for parameter allocations. You can allocate various time groups, such as season groups, day groups and time-of-use groups within an RTP component. You define the structure of RTP components by allocating these time groups. You define season, day and time-of-use groups in Customizing (see the cookbook on basic Customizing settings or unit Synthetic Profiles of IUT225).

• Different RTP components allow you to slice the profile in different ways in order to calculate amounts for billing. For example, peak demand, on-peak consumption and off-peak consumption all need to be calculated. To calculate the total peak demand, you do not want to include any time periods such as on-off peak. In the above example, there are 2 RTP Components. One RTP component is used to look at the entire profile (regardless of time period) and the other RTP component to slice the profile into on- and off-peak periods.
  • RTP Component 1 PEAK: Determines peak demand for the entire time period and is not dependent on any day, TOU or season group
  • RTP Component 2 ON-OFF: Determines the on- and off-peak consumption based on a TOU group.
• Priorities are defined for each RTP component. These allow you to define which RTP component is used if there is more than one activation period.
• When RTP components are allocated to the RTP interface, it is possible to distinguish between activation types. In order to bill customer-specific agreements, for example, you can individually allocate and activate an RTP component called Allocate and activate individually. In other words, you would allocate the RTP components only to those installations that you want to bill. Valid periods are defined for the agreement at the RTP interface level.

• The RTP components slice the measured profile as shown above by creating a virtual on-peak and off-peak profile (output parameters). It is important to note that these profiles are not stored in the database but are only used as input to the result function.
• The result function adds the results of the on- and off- peak virtual profiles to determine on- and off- peak consumption.
• The result parameters are en passed via the rate facts into input operands of the rate steps.

There are three possible activation types for the RTP Component:

• Use and activate generally:
  • Allows for definition of input parameter allocations at the level of the RTP interface
  • Allows for activation of the RTP component at the level of the RTP interface
• Use and activate individually:
  • Allows for definition of input parameter allocations at the installation level.
  • Corresponding parameter templates can also be defined at the RTP interface level.
  • Output Parameters can also be allocated at the RTP interface level.
  • The RTP Component can also be activated at the installation level.
• Use individually and activate generally:
  • Allows for definition of input parameter allocations at the installation level.
  • Corresponding parameter templates can also be defined at the RTP interface level.
  • The RTP component can also be activated at the RTP interface level.

RTP Components can be activated at the rate, where they are generally assigned to numerous customers, or at the installation where they are individually assigned to a customer.

• When the RTP components are activated in the RTP interface, they are given a priority (1 – 99). This allows you to define which RTP component is used if there is more than one RTP component in one activation period.
• In the above example, there are 2 RTP components.
  • RTP component 1 has a medium priority
  • RTP component 2 has a low priority
• RTP component 1 and RTP component 2 are always activated because they are activated for the same period. In order to avoid conflict with regard to supplying the input parameters (or output parameters), the priority of the RTP component determines which value has precedence.
• RTP components with the same activation period are always prioritized by parameter. This means that parameter input 1 from component one is identical to parameter input 1 from component 2.
• In the above example, this means that:

Input1 is supplied values from component 1. Input 1 from component 2 is ignored due to its lower priority and the input parameters are exactly the same.

• The activated RTP component with the highest priority will be executed. The prioritization is used to determine which RTP Component is valid when several RTP Components have the same activation periods. In this case the RTP Component with the highest priority is valid
• In this scenario above, there are 2 RTP Components:
  • RTP Component 1 has a medium priority
  • RTP Component 2 has low priority
• RTP Component 1 is always executed because it has the highest priority, except for the case when RTP Component 1 is not active.

• In the preceding scenario, there are 3 RTP components.
  • RTP Component 1 has a medium priority and is activated generally at the RTP-Interface
  • RTP Component 2 has a low priority and is activated generally at the RTP-Interface
  • RTP Component 3 has the highest priority and is activated individually at the installation level.
• RTP Component 1 is executed in the first time block because it has the highest priority. RTP Component 2 is executed in the second time block because it is the only active RTP component. RTP Component 3 is executed in the third time block because it has the highest priority and is active. RTP Component 1 is executed in the last time block because it is active and has a medium priority (Over RTP Component 2).
• The active RTP component with the highest priority is always chosen, regardless of whether it is activated at the installation or the RTP interface.

Input parameters are defined in the RTP interface. Profiles are allocated to the input parameters in the individual RTP components. The values from these profiles are used for executing formulas. Profiles can be allocated to the input parameter according to the structure defined in the RTP component.

Different profiles can be allocated to one input parameter in different RTP components. The profiles are used according to the priority defined for the RTP component and its corresponding activation periods.

Profiles can also be allocated to input parameters indirectly using roles. The input parameter is supplied with profile values when the RTP interface is executed. These profile values are assigned to a profile with a specified role and are allocated to the interval meter to be billed. This enables the user to provide an input parameter with only those profile values that match the load shape of the meter to be billed. For example, if a role of ‚0001‘ (measured consumption) is assigned to the input parameter, when the interface is executed, the system will look for the profile attached to that device with a role of ‘measured consumption‘. This makes the process more flexible so the profile number is not hard-coded into the interface.

• When an RTP component has the activation type Use and Activate Individually or Use Individually and Activate Generally, it is possible to define input parameters as parameter templates. The advantage of parameter templates is that they allow the user to define input parameters via the installation. This means that profiles or roles can only be allocated to input parameters at the installation.
• In the example above, the SPOT component is activated at the installation. During the time the individual component is activated, the profile allocated to the installation will be used for this calculation.
• For example, if the parameter template was used, different limits can be defined for each customer, based on the customer-specific requirement. If input parameter 2 was a LIMIT value, then a different limit will be assigned for each customer:
  • Customer 1: limit = 25
  • Customer 2: limit = 30
  • Customer 3: limit = 45

Results parameters are assigned in the RTP interface. Output parameters are allocated to the result parameters. The result parameters are then allocated to the RTP rate to facilitate the billable quantities being passed to the IS-U-BI component.

• Within the header data, the formula defines the input and output parameters that will be allocated within the RTP components.
• RTP components allow flexible use of allocation to an individual installation or a group of customers.
• The RTP components allow slicing of the profile by different time allocations such as TOU, day or seasons.
• The output parameters are allocated to the result parameters.
• The result parameters are allocated to operand categories in the RTP interface. The result parameters are also allocated to operands in the rate facts. The operand category must match the category of the RTP operand.

• Before the RTP interface can be used, it must be allocated to a rate. This allocation is only possible for rates for which the Permitted for Interval Meters field has been selected. Within the RTP rate facts, individual rate step input operands can be allocated to result parameters of the RTP interface. This means that the appropriate operands are provided with result parameter values from the RTP interface during billing.
• It is only possible to allocate result parameters to operands in the rate facts if the RTP operands have been defined. The operand category must also be assigned. This is the operand category in which the RTP rate values in the RTP rate are to be processed. The operand category must match the category of the RTP operand.