Device Installation Fields

The device installation entity represents the installation lifecycle of a device at a service point. The lifecycle reflects a business process consisting of commands to commission, connect, disconnect, and decommission the device. Rules for this process include:

The removal_date field must be null or must be strictly later than install_date.
Once specified, fields about the device cannot be changed other than setting the removal_date to indicate the device is no longer in service. This ensures that any fields on the device used for calculating values displayed to a customer do not impact historically displayed values. If a change is needed, the existing device should be taken out of service and a new device with the appropriate values should be created in its place.
Device installation and removal periods may not overlap for a service point.

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
install_event_id	The unique ID of the install event. Type: VARCHAR(80) Can Be Empty?: No. Primary Key.
device_installation_external_id	The ID used by the external system to identify the install event. Type: VARCHAR(60) Can Be Empty?: Yes.
device_installation_status	The installation lifecycle stage of a device at a service point. The lifecycle reflects a business process consisting of commands to commission, connect, disconnect, and decommission the meter. Example Values: Pending Connected / Pre-Commission Pre-Connected / Commissioned Connected / Commissioned Connected / Decommissioned Disconnected / Commissioned Disconnected/ Decommissioned Remove Type: VARCHAR(40) Can Be Empty?: No.
arming_status	A Boolean value that indicates if the device has been armed or not. Some AMI devices have special arming switches that require manual manipulation before the commodity can flow through the device. Devices that require arming (those with an Arming required flag set to Arming Required) must be armed before they can be connected. Allowed Values: Any supported Boolean values. Armed (Default) The device is armed and ready to be connected. Not Armed The device is not yet armed. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: Yes.
device_on_off_status	A Boolean value indicating the status of the device. Allowed Values: Any supported Boolean values D1ON The device is on. D1OF The device is off. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: No.
installation_constant	A value other than 1 used to indicate that when calculating consumption, the installation requires that measurement data be multiplied by this value to get accurate results. This installation constant is used for all device measuring components. The application includes two multipliers: this installation constant and a measuring component register multiplier. These multipliers can be used individually or together to adjust measurements. Type: DECIMAL(12,6). See Supported Decimal Formats for details. Can Be Empty?: No.
install_datetime	The date and time of the installation. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: No.
removal_datetime	The date and time of the installation. Leave null to indicate that the meter is in service. Note: There can be only one active device at a service point. The `removal_datetime` field should be populated for any device that is not active. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes.