Populate Customer Table

To implement Responder, a Database Administrator will need to populate the customer table in the Responder database.

Some of the fields in the Responder tables utilize domains. Domains may be edited in the DatabaseSchemaConfig.xml file.

The customer table must be populated to use Responder. The Responder database consists of additional Responder tables which may be modified to customize Responder Explorer, as well as history tables and archive tables.

TIP: You can check the data architecture of each Responder table (i.e., field data type, field length) by viewing the SQL implementation scripts in your Miner and Miner\Responder\Developer Resources\Implementation Scripts directory.

RX_CUSTOMERS

Populate this table with your existing CIS data. The Account field is the primary key for the table and must be restricted to NOT allow duplicates. Duplicate account numbers will cause errors in Responder and prevent the user from accessing the Edit Incident form.

Field Name

Description

ACCOUNT

The customer's account number. This field is the primary key for the table. Duplicate account numbers may NOT be allowed.

ACCOUNT_TYPE

Indicates the type of account. Uses the Account_type domain.

METER

The customer's meter number.

FIRSTNAME

The customer's first name.

LASTNAME

The customer's last name.

STREET

The customer's street address.

CITY

The customer's city.

STATE

The customer's state.

POSTAL_CODE

The customer's zip code.

TELEPHONE

The customer's telephone number. The area code of a phone number may not begin with a 1 or 0.

TELEPHONE2

An alternate telephone number for the customer. The area code of a phone number may not begin with a 1 or 0.

TELEPHONE3

An alternate telephone number for the customer. The area code of a phone number may not begin with a 1 or 0.

TELEPHONE4

An alternate telephone number for the customer. The area code of a phone number may not begin with a 1 or 0.

CALLBACK_NUMBER

Preferred number for contacting the customer. The area code of a phone number may not begin with a 1 or 0.

DEVICE_OID

The object ID of the device to which the customer is associated (e.g., service point or transformer). This field links to the OID field in your geodatabase.

DEVICE_FCID

The feature class ID of the device to which the customer is associated (e.g., service point or transformer). This field utilizes the DEVICE_FCID domain.

CONNECT_STATUS

Indicates the status of the user's connection (connected/disconnected). This field uses the CONNECT_STATUS domain.

CRITICAL

Indicates if the customer site is critical. This field uses the CRITICAL_TYPE domain.

PRIORITY

Indicates if the customer site is priority. This field uses the PRIORITY domain.

TIME_DISCONNECT

Indicates the time the customer was disconnected.

TIME_RECONNECT

Indicates the time the customer's power was reconnected.

USER_CREATED

This field is not currently used by Responder. You may customize Responder to populate this field with the name of the user who created the record.

USER_UPDATED

This field is not currently used by Responder. You may customize Responder to populate this field with the name of the user who updated the record.

REGION

Indicates the region in which the customer resides. This field uses the REGION domain.

COUNTY

Indicates the county in which the customer resides.

FEEDER_ID

The ID of the feeder to which the customer is attached.

The remaining tables in the Responder database are populated by Responder.

QR code for this page

Was this helpful?