Add file name convention to PII data specification

Proposed changes under PII Data

Old:

The PII submission consists of two tables. Each table should be a .csv file, zipped together into a .zip file. The CSV data files must use the "|" character as the delimiter with unquoted text values.

New:

The PII submission consists of two tables. Each table should be a .csv file zipped together into a .zip file. The CSV data files must use the "|" character as the delimiter with unquoted text values. For processing to work correctly, fields must be listed in the exact order shown in the specification.

Proposed changes under User Guide - Preparing you Claims PII file

Old:
Your file must contain all tables and correct field names as headers as defined in the Claims PII specification; fields must be in the table in the order shown in the specification. The data in the tables must adhere to the rules specified in the specification, including the primary key rules for the PII tables. That is, the PII data submission should not include duplicate records, and each primary key should appear in the PII data only once. Primary key values are case-insensitive, which means that Customer123 is the same ID as CUSTOMER123.

Create a CSV file for each table and zip them together. Name each CSV file using your PA code and table name (e.g. SCE-Site.csv). The zip file should be named using your PA code and claim year quarter (e.g. SCE2023Q4.zip). Prepare the CSV using the pip or up-bar character as the delimiter.

New:

Your file must include all tables with correct field names as headers, listed in the same order as the Claims PII specification, to be processed. The data in the tables must adhere to the rules specified in the specification, including the primary key rules for the PII tables. The PII data submission must not include duplicate records, and each primary key should appear in the PII data only once. Primary key values are case-insensitive (e.g., Customer123 is considered the same as CUSTOMER123).

File formatting and naming:

• Create a CSV file for each table and zip them together.

• Use the pipe (|) or up-bar character as the delimiter.

• Name each CSV file using your PA code and table name, following this format: PA_site.csv (e.g., SCE_site.csv), PA_contact.csv (e.g., SCE_contact.csv)

• Name the zip file using your PA code and claim year quarter (e.g., SCE2023Q4.zip).

Does CEDARS Team have a preference to have claim year in the PII file names, e.g. PGE_2025_site.csv?
Either format (e.g. PGE_site.csv or PGE_2025_site.csv) will work for PG&E.

Also, I noticed a slightly different guidance on the PII file naming convention in the user guide https://cedars.cpuc.ca.gov/claims/specification/user-guide/#PreparingYourClaimsPIIFile. Notes must be updated for consistency.

Typo found in the User Guide under the section titled “Preparing your Claims PII file” - there’s a sentence that says “pip” instead of “pipe”.

Also add a note that the fields in the PII .csv files need to be in the order listed in the specification for processing to work correctly.