Weighted Customer Count
Introduction
Purpose
A utility might have a need in major events to prioritize work and make it visible to the dispatchers. Some utility customers may have a higher priority in restoration; these include 911 centers, hospitals, police stations, schools, etc. During major events, outages with larger numbers of customers may obscure these priority customers from the dispatcher’s view. With weighted customer count configured, the dispatcher could sort by the weighted customer count and dispatch the most important outages first.
Overview
The weighted customer counts feature is designed to address the problem of prioritizing work. Each customer has "weight" value associated with its account. The weighted customer count of an outage in the system is the sum of the "weights" of all customers affected by the outage. The weighted customer count for an outage is available in Work Agenda and can be used for sorting.
The customer weight value for an individual account can come from one of two sources:
1. Base Customer Weight Value
All customers are divided into groups based upon the value of a single column in the customer model. This column will be referred to as the base weight key. The customer weight value is determined by the group a specific customer belongs to.
2. Customer Weight Override
The customer weight value entered by administrator (via Configuration Assistant) for a specific account.
The customer weight override takes precedence, if available.
Configuration
Customer Schema
Project-specific additions to the customer model are required to support weighted customer counts.
1. Column WEIGHTED_COUNT must be added to the CES_CUSTOMERS view as an INTEGER. This provides the base weight of the customer.
2. Column WEIGHTED_COUNT must be added to the CUSTOMER_SUM view. It should be populated by adding together the base customer weight values of all customers on a supply node.
SRS Rules
The rule useWeightedCounts must be enabled.
Work Agenda Configuration
The column WEIGHTED_NUM_CUST can be added to Work Agenda (See Adding a Column in Work Agenda Configuration) and/or configured in pre-defined sorts.