Customer Classification Data Version History
The following table lists updates to the customer classification data document specification by version number and date. The latest version number should be used in the file name that you send to Oracle Utilities. See Customer Classification File Name Conventions for more information.
| Update | Specification Version Number | Date |
|---|---|---|
| Update Customer Classification File Name Conventions to be clearer about file name length limit and what file name components are required. | v1-12-0 | 04/11/2022 |
| Clarify that zip files should only contain one file each. | v1-11-0 | 11/23/2021 |
| Clarify file extension requirements and expectations. | v1-10-0 | 11/12/2019 |
Clarify that
data files must be in .tsv or .txt file format before being compressed
and sent to Oracle Utilities. Add an example to clarify when the
start_date field is useful.
|
v1-9-0 | 01/28/2019 |
| Edit sections and headings to simplify content. No substantive changes to technical specifications. | v1-8-0 | 01/10/2019 |
| Updated file retention section to reflect regional differences. | v1-7-0 | 05/08/2018 |
| Added statement about valid end-of-line separators. | v1-6-0 | 03/19/2018 |
| Updated description of file transfer process. Added information about correcting file upload errors and Oracle file retention policy. | v1-5-0 | 03/02/2018 |
| Added a statement about the utility's data obligations. | v1-4-0 | 03/31/2017 |
| Added document number and updated branding. | v1-3-0 | 02/09/2017 |
| Added legal notices. Updated document branding. | v1-2-0 | 01/11/2017 |
| Made stylistic updates to improve clarity and organization. Updated example data. Added a verification checklist. | v1-1-0 | 01/05/2017 |
| Added baseline specification version number to the document. Updated naming conventions to include instructions on how to specify a population token and specification version number in the data file. | v1-0-0 | 09/22/2016 |
| Updated document formatting. Updated inactive_date, start_date, and end_date field descriptions to say that YYYYMMDD is an acceptable format. Reorganized some sections to follow a more standard structure. Removed Appendix, which contained redundant examples of data. | Not applicable. | 06/16/2016 |