Device Fields
The device entity includes fields related to the name, type, and description of a device.
Note: Although the fields below are described separately from the other fields in the premise data file, any premise data that you send to Oracle Utilities must be included in the same file, with all columns included in every row of the file. See Premise Data File Specifications for more information.
Field | Description |
---|---|
device_id |
The device or meter identifier in the source system. Type: VARCHAR(40) Can Be Empty?: No. Primary Key. |
device_name |
The device name as displayed to a user in the source system. Type: VARCHAR(40) Can Be Empty?: Yes. |
device_external_id |
The device identifier from an external system. If your utility has the Oracle Utilities DataConnect solution, this field can be used to map the external ID from the head-end system to the Type: VARCHAR(120) Can Be Empty?: Yes. |
device_type_code |
The type of device. Typically, devices are categorized into smart meters, manual meters, items, or communications components. The code used to denote the device type will vary by utility. Example Value: E-SMART-MTR Type: VARCHAR(30) Can Be Empty?: No. |
device_type_description |
A description of the device type code. Example Value: Electric Smart Meter Type: VARCHAR(100) Can Be Empty?: Yes. |
device_type_service_type_code |
The service type (electric, gas, water, etc.) provided by devices of this type. Allowed Values:
Type: VARCHAR(2) Can Be Empty?: No. |
manufacturer |
The short name or acronym of the manufacturer of the device. Example Values: GE, LG Type: VARCHAR(30) Can Be Empty?: Yes. |
manufacturer_desc |
The full name of the meter manufacturer. Example Values: General Electric, Landis+Gyr Type: VARCHAR(100) Can Be Empty?: Yes. |
model_number |
The specific model number of the device provided by the manufacturer. Example Values: I-210+c Type: VARCHAR(30) Can Be Empty?: Yes. |
model_desc |
The full name of the device model. Example Values: I-210+c Smart Meter Type: VARCHAR(100) Can Be Empty?: Yes. |
device_manufacture_date |
The date on which the device was manufactured. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes. |
dial_count |
The number of dials in a meter. Type: DECIMAL(5,0) Can Be Empty?: Yes. |
sub_meter_flag |
A Boolean value to indicate whether a device is a sub meter as opposed to a separate, independent meter. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: Yes. When left empty, the default value is FALSE. |
net_meter_flag |
A Boolean value to indicate whether a device uses net metering. This is typical for customers who generate energy using solar technology in addition to consuming energy. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: No. |
device_status |
The current status of the meter. Note: There can be only one active device at a service point. Allowed Values: The lifecycle status values configured for a meter in the Oracle Utilities Meter Data Management system. Example Values: ACTIVE, RETIRED Type: VARCHAR(12) Can Be Empty?: No. |
head_end_system |
The head-end system associated with the device. Head-end systems are systems that collect measurement data and meter events, and send command requests to meters. Example Values: Echelon, Itron, Sensus Type: VARCHAR(30) Can Be Empty?: Yes. |
head_end_registration_status |
A flag that indicates the registration status of the meter in the head-end system. This is used by smart meter commands and other processes to determine if the meter is currently registered in the head-end system. Example Values: D1DR, D1NR, D1RE
Type: VARCHAR(4) Can Be Empty?: Yes. |
device_classification |
A flag that indicates if devices of this type are processed as meters or items. Example Values: D1IT, D1MT
Type: VARCHAR(4) Can Be Empty?: Yes. |