About Program Subscriptions

Program subscriptions represent a customer's enrollment in a program, and link a customer with a program and (in most cases) a device location. Customers can have separate program subscriptions for different device locations and programs.

Metered service records serve as a parent to individual program subscriptions for each of a customer's programs and/or device location. If multiple program subscriptions are associated to the same device location, one can be defined as a "parent" program subscription. Program subscriptions are most often created as a result of the customer enrollment process, but can be created on an ad-hoc basis if needed.

Program subscriptions are defined by the following:

  • Program Subscription Type: The program subscription type associated with the program. Program subscription types define certain parameters and attributes of a class of program subscriptions.

  • Metered Service: The metered service record that serves as a "parent" for the program subscription.

  • Parent Program Subscription: (Optional) A program subscription that serves as a "parent" for the program subscription.

  • Settlement Group: A metered service for the Main Customer associated with the program subscription, used to group program subscriptions for customer settlement transactions.

  • External Account ID: An ID used to identify the program subscription in external systems.

  • Main Customer: The program contact for the customer associated with the program subscription.

  • Status: The current status of the program subscription.

  • Start and End Date/Time: The date and time on which the program subscription record started, and ended (if applicable).

  • Time Zone: The time zone associated with the program subscription.

  • Device Location: The device location associated with the program subscription. This defines the devices for which the customer is enrolled in the program.

  • Program: The program in which the customer is enrolled.

  • Program Enrollment Source: The source of the customer's enrollment in the program. Options incude:

    • Bring Your Own: The enrollment was created as a result of the customer installing their own controllable device.

    • Contact Center: The enrollment was created by the customer contacting the utility's contact center. This includes enrollments created via the Customer Enrollment Process Flow.

    • Self Service: The enrollment was created via an online customer self service portal.

  • Bill Cycle: The bill cycle associated with the program subscription, used when calculating program incentives and fees via batch processing. If defined for the parent metered service, the Bill Cycle is defined by default on all program subscriptions for the metered service.

  • Transaction Calculation Groups: One or more effective dated program calculation groups that contain program calculation rules used to calculate scores for devices associated with the program subscription. If more than one group is defined on the program subscription, the group with the latest effective date/time is used.

  • Fallback Transaction Calculation Groups: A list of one or more effective dated program calculation groups used if a program calculation group is not defined on the program subscription (from the program subscription type).

System Data

Program subscriptions are based on the following system data:

Data Type

Description

Maintenance Object

Usage Subscription (D1-US)

Business Object(s)

Program Subscription (X1-ProgramSubscription)

Creating Program Event Settlement Transactions

Program event settlement transactions can be created via the "Initiate program event settlement for completed program events" (X1-INIPES) monitor algorithm defined on the program subscription business object. This algorithm is triggered by the Program Subscription BO Periodic Monitor Process (X1-PSPMB) batch process (see below).

This algorithm scans program events and event participation records related to the program subscription looking for program events that have been in the "Complete" status for a number days (defined as a parameter on the algorithm) with related event participation records that are in either the "Successful participation" or "In-flight override" states. The algorithm creates program event settlement transactions for each program event/event participation found.

Program event settlement transactions are created in the "Pending" state, and are processed by the Process Program Settlement (X1-PREVS) batch process which transitions the transaction to a specific state depending on the type of program event settlement transaction. See About Program Event Settlement Transactions for more information.

Batch Processing

Program subscription processing is supported by the following monitor batch processes:

  • Program Subscription BO Periodic Monitor Process (X1-PSPMB): Used to trigger monitor algorithms on the program subscription.

Use the Batch Control portal to learn more about the parameters used by these batch processes.