Customer Classification File

The customer classification file lists the customers and their respective classifications. The table below defines the elements that must be included in the columns of the customer classification file.

Note: If the Oracle Utilities Opower system encounters any classifiers that have not been already defined in the Customer Classifier Definition file, the corresponding rows in the Customer Classification file will be rejected.

Column	Format	Can be empty?	Definition
customer_id	varchar	No	Unique identifier for the customer. This customer ID should be the same customer ID that is sent in the billed usage files, as described in Customer Fields.
premise_id	Varchar	No	Identifier for the premise with which the customer is currently associated. This premise ID should be the same premise ID that is sent in the billed usage data files, as described in Customer Fields.
classifier	varchar	No	Key identifying the classifier. The classifier should be the same as one of the classifiers already listed in the corresponding definition file.
value	varchar	No	Value for the classification. The value should be the same as one of the allowed values already listed in the corresponding definition file.
start_date	datetime (YYYYMMDD HHmm)	Yes	The date and time at which the customer is classified according to the classifier/value. This is useful for classifers that are time-sensitive. For example, this could be used if a customer is part of a low-income group for a certain period and then is removed from the group. If left blank, the start date is assumed to be the date of file import.
end_date	datetime (YYYYMMDD HHmm)	Yes	The date and time at which the customer is no longer classified according to the classifier/value. If left blank, the classification value is assumed to be true indefinitely. If the value for a customer’s classification is changed, and the end date is not explicitly sent by the utility, the end date will be set to the date prior to the start date of the new classification.