The Data Exchange template file in the above link contains all of the columns defined by the Data Exchange Specification v9.8.2. When filling it out, remember that each row of data represents a single service configuration and that the data in those rows must conform to the maximum lengths and formats defined in the Data Exchange Specification.
Things to keep in mind:
- Successive imports overwrite previous imports when data fields overlap.
- When importing meter histories, the row containing the latest entry for a particular service configuration must come after the row with the earliest entry for that service configuration, otherwise previous meter, endpoint and service agreement history will be overwritten. During import validation, such backdated entries trigger warnings.
- Leaving fields blank will not delete data previously recorded in BEACON. For example, Customer A moves out of a location and a Customer B moves in. Customer A used a PO Box as a billing address. Customer B wants the bill sent to the primary location address. When creating a Data Exchange file to record the new Account details for Customer B, be sure to enter primary location address as the billing address or simply put _CLEAR_ (be sure to include the underscores and capitalize CLEAR exactly as shown) in the field to remove Customer A’s billing address.
NOTE: Putting _CLEAR_ in a field will remove previously recorded data from any but the following fields in the Data Exchange Specification for Accounts and Assets:
Account_ID, Location_ID, Service_Point_ID, Meter_ID, Endpoint_SN
Fields that cannot be empty
Service_Point_Type, Meter_Manufacturer, Meter_Model, Meter_Size, Meter_Size_Unit, Meter_Continuous_Flow, Register_Number, Register_Unit_Or_Measure, Register_Resolution, Endpoint_Type
SA_Start_Date, SA_End_Date, Meter_Install_Date, Meter_Install_Start_Read, Meter_Removal_End_Read, Endpoint_Install_Date, Endpoint_Removal_Date
Account_Email, Account_Autopay, Account_BillerAutoPay
Field that default to other values when ‘_CLEAR_’ is applied
Service_Point_Timezone – value defaults to the utility timezone
Read_Sequence – Defaults to Zero (0)
Alert_Code – Defaults to N/A
High_Read_Limit – Defaults to N/A
Low_Read_Limit – Defaults to N/A
- Previously, entering a blank space replaced data from a field. That workflow is no longer supported.
- Account and Asset IDs act as keys, so they behave differently from other fields.
- Changing or correcting Account and Asset IDs while preserving service configurations requires a special file called an ID Update file.
- Currently, utilities must have Data Exchange enabled to use Data Exchange.
When you have completed the spreadsheet file, save it in comma-separated values (CSV) format and follow the instructions to bring the data into BEACON.