Call Center Data Version History

The following table lists updates to the call center data specification by version number and date. The latest version number should be used in the file name that you send to Oracle Utilities. See File Name Conventions for more information.

Update Specification Version Number Date

Update File Naming Conventions to be clearer about file name length limit and what file name components are required.

v1-11-0

04/11/2022

Update table in Data Specifications to use two-column format. Clarify that zip files should only contain one file each.

v1-10-0

11/23/2021

Move information about the file retention policy to a more prominent place.

v1-9-0

TBD (when another edit needs to happen)

Clarify file extension requirements and expectations.

v1-8-0

11/12/2019

Edit sections and headings to simplify content. No substantive changes to technical specifications.

v1-7-0

12/21/2018

Updated file retention section to reflect regional differences.

v1-6-0

05/08/2018

Added statement about valid end-of-line separators.

v1-5-0

03/19/2018

Updated description of file transfer process. Added information about correcting file upload errors and Oracle file retention policy.

v1-4-0

03/02/2018

Added a statement about the utility's data obligations.

v1-3-0

03/31/2017

Added document number and updated branding. v1-2-0 02/09/2017

Added legal notices. Updated document branding.

v1-1-0

01/11/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

10/27/2016

Made the csr_id field required. Clarified that either the end_time or duration field is required, though one can be empty if the other is filled in. Minor updates to document formatting and organization.

Not applicable.

06/16/2016

Updated document formatting and organization. Added new rows for phone_number, wait_time, talk_time_wrap_time, and hold_time. Made customer_id and premise_id optional.

Not applicable.

05/10/2016