Service Point Fields

The service point entity includes fields related to the device location where service is delivered.

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
service_point_id	The unique service point identifier in a utility's Customer Information System or other system of record. A service point identifies an unchanging device location where service is delivered. Type: VARCHAR(40) Can Be Empty?: No. Primary Key.
service_point_name	The name of the service point as displayed in the utility Customer Information System or other system of record, if applicable. Type: VARCHAR(40) Can Be Empty?: Yes.
service_point_type_description	A short description of the service point code. Example Values: Electric Commercial, Gas Residential, Water Industrial Type: VARCHAR(100) Can Be Empty?: Yes.
service_point_type_category	A flag that indicates the type of device installed at service points of this type. Allowed Values: D1MT Indicates that a single meter can be installed at service points of this type. D1IT Indicates that a single "badged" item can be installed at service points of this type. A badged item refers to objects like street lamps that have a unique ID. D1MI Indicates that one or more "unbadged" items can be installed at service points of this type. Type: VARCHAR(4) Can Be Empty?: No.
service_point_type_code	The service type provided by service points of this type. Allowed Values: E Electric G Gas W Water M Miscellaneous WW Waste water O Other Type: VARCHAR(2) Can Be Empty?: No.
service_agreement_id	The unique identifier of a service agreement. Type: VARCHAR(40) Can Be Empty?: Yes. Note: This field should only be populated if it will be used in the Oracle Utilities DataRaker solution. Otherwise it will be ignored.
service_point_start_datetime	The date on which the service agreement was associated with the service point. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes. Note: This field should only be populated if it will be used in the Oracle Utilities DataRaker solution. Otherwise it will be ignored.
service_point_end_datetime	The date on which the service agreement was disassociated from the service point. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes. Note: This field should only be populated if it will be used in the Oracle Utilities DataRaker solution. Otherwise it will be ignored.
service_cycle_code	The service point’s measurement cycle. A measurement cycle can define the schedule for manual meter reading of devices at service points, or it can define when to calculate bill determinants for usage subscriptions associated to service points in the cycle. Example Values: CYCLE01, CYCLE02 Type: VARCHAR(30) Can Be Empty?: Yes.
service_cycle_description	The description for the service cycle code. Example Values: Read Cycle 01, Read Cycle 02 Type: VARCHAR(300) Can Be Empty?: Yes.
service_route_code	The route used to collect measurements. Example Values: ROUTE-100, ROUTE-110 Type: VARCHAR(30) Can Be Empty?: Yes.
service_route_description	The description for the route code. Example Values: Route 100, Route 110 Type: VARCHAR(100) Can Be Empty?: Yes.
facility_level_1	The substation network node level closest to the service point. Type: VARCHAR(30) Can Be Empty?: Yes.
facility_level_2	The feeder or distribution circuits that carry power from the substations to the transformers closest to the service point. Type: VARCHAR(30) Can Be Empty?: Yes.
facility_level_3	The step down transformer closest to the premise. Type: VARCHAR(30) Can Be Empty?: Yes.
life_support_sensitive_load_code	A Boolean value that identifies whether the premise has life support or sensitive load equipment. Allowed Values: Y Premise has life support equipment. N Premise does not have life support equipment. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: Yes. If left empty, this field defaults to N.
status_code	The current status of the service point. Allowed Values: Active, Inactive Type: VARCHAR(12) Can Be Empty?: Yes.
source_status_code	A status code that identifies if the service point is connected or disconnected to the distribution network. Example Values: D1CN Service point is connected to the distribution network. D1DC Service point is disconnected from the distribution network. Type: VARCHAR(30) Can Be Empty?: Yes.
disconnect_location	A code that identifies whether the service is disconnected at the device or at a source such as a service pole. Example Values: D1DV Service is disconnected at the device. D1SR Service is disconnected at another source. Type: VARCHAR(30) Can Be Empty?: Yes.
remote_disconnect	A Boolean value to indicate whether to remotely disconnect a customer's service point from receiving service. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: Yes. If left empty, this field defaults to `FALSE`.
service_point_time_zone	The timezone of the service point. The value provided must conform to the specification in the Internet Assigned Numbers Authority database. Type: VARCHAR(32) Can Be Empty?: No.
disconnect_for_nonpay	A Boolean value to indicate whether to stop providing service to a service point due to the customer not paying bills. Type: BOOLEAN. See Supported Boolean Formats for more information. Can Be Empty?: Yes.