The purpose of this section is to describe the views that support existing Oracle Utilities Network Management System software, and provide compatibility for this customer model with existing installations.

The ces_customers view (or table) is derived from the cu_customers, cu_service_locations, cu_meters, cu_service_points, cu_ders, and supply_nodes tables. It provides a flat customer view that is utilized by various Oracle Utilities Network Management System services and applications such as JMService, Web Call Entry and others.

The CES_CUSTOMERS table only holds active records, so the CES_CUSTOMERS_HISTORY was created to hold historical CES_CUSTOMERS records.

When first created, active CES_CUSTOMERS records will be copied to CES_CUSTOMERS_HISTORY and back-dated so that their birth values are January 1, 2000. This is to match potential historical outages for these records. A new death column is added as null for these records.

As the CES_CUSTOMERS changes, the active CES_CUSTOMERS_HISTORY record is set with a death date, and a new record is added with the current date.

Table NMS_ACCOUNTS_HISTORY maintains history of customer account information in NMS. This information is not used by NMS itself but can be useful for analytics tools.

The NMS_ACCOUNTS_HISTORY table always contains the following columns:

ACCOUNT_NUMBER: Account number. Populated from CES_CUSTOMERS_HISTORY.ACCOUNT_NUMBER

BIRTH: Date/time when this record became active

DEATH: Date/time when this record became inactive (special value '1/1/4000' indicates that the record is currently active)

PTN_DATE: Date/time used for partitioning

TO_DIE: Column used during incremental update procedure

Additional columns can be added to the NMS_ACCOUNTS_HISTORY table through configuration parameters in the CES_PARAMETERS table.

APP: 'BI'

ATTRIB: ACCT_HIST_COLUMN' followed by arbitrary string making the value unique

VALUE: Name of the column of the CES_CUSTOMERS_HISTORY table. Column with the same name will be added to the NMS_ACCOUNTS_HISTORY table.

If column configuration is changed, then the NMS_ACCOUNTS_HISTORY table needs to be dropped. Next execution of the nms-update-customers command will recreate and repopulate the table with the new set of columns.

Within Oracle Utilities Network Management System, the customer_sum view (or table) is used primarily by JMService to identify the number of customers, critical customers, etc. on each supply node. The customer_sum view/table is typically generated from the ces_customers table/view. It is simply a summation of the customer model and is designed to provide more efficient outage impact estimates.

Note: all of the following fields are required.