Skip to main content

Add Fuel Sub Infrastructure Cost Fields to Claim Specification

Feedback20262026 Claim Spec Update QueueClaim Spec

Background: CPUC introduced fuel sub‑infrastructure cost reporting requirements in PY2023 for Kiteworks submission. Although PAs have been submitting these costs to Kiteworks along with the PII Site and Contact data, these requirements have not been incorporated into the claim specification in CEDARS.

Ask: Add the fuel sub‑infrastructure cost reporting requirements outlined in the attached CPUC excel template to the claim specification. https://cedars.cpuc.ca.gov/claims/specification/

FS Infra Costs Data Collection - Interim Draft v4 (1).xlsx

17.5 KB• Spreadsheet

Select the module in CEDARS
Posted by Roopa Reddy ·
Status: Completed17 comments

Log in to comment and vote

Comments17

  • cedars team

    Team•

    Jul 2

    Hi @Roopa Reddy & @Amy.reardon@cpuc.ca.gov

    I've mocked up the Fuel Sub table for PII data.

    Could you please take a look and let me know if you're happy with:

    • Its placement alongside the other PII data in the Claim Spec.

    • Whether the table name is appropriate.

    • Which fields should be required.

    • Whether any of the field descriptions could be improved.

    https://www.figma.com/proto/djSwjUOnQmtJGgHy5wcHbk/Claim-Specification-Update-2026?node-id=7396-2524&viewport=569%2C152%2C0.5&t=ad77ck1d3Kj4poE7-1&scaling=scale-down-width&content-scaling=fixed&page-id=7396%3A2523



    Thanks,

    Sonja

    • Roopa Reddy

      Team•

      Jul 2

      @cedars team @Amy.reardon@cpuc.ca.gov @Jake Richardson (PG&E)

      Hi Sonja,

      I appreciate the work that’s gone into this so far.

      Here are my comments for your review:

      • The table name and its location within the spec look good to me.

      • I do, however, have a correction regarding the notes: the Fuel Sub Infrastructure Cost table contains only non-PII information, even though it is submitted alongside the PII data.

      • This file is currently being submitted in Excel as part of the zip file. It might be worth assessing any downstream impacts to stakeholders before switching to a pipe-delimited CSV format.

      I also have a few updates for the fields:

      • For MeasureID, this shouldn’t be marked as a required field since there are cases like custom claims where it wouldn’t apply.

      • For PanelEquipCost, please correct the description to: “Equipment cost of panel upgrade.”

      • For InfraCustomerRequestDate, please correct the description to: “If infrastructure was upgraded, when did the customer begin seeking the upgrade?”

      • For InfraCustomerCompleteDate, edit the description to: “If infrastructure was upgraded, when was the upgrade completed?”

      • Lastly, for consistency, please update all instances of “FS measure” to “fuel substitution measure” throughout the descriptions.

      PG&E suggests changing the datatype to a text for these fields, since sometimes multiple panels are listed.

      Thank you!

      • cedars team

        Team•

        Jul 6

        Hi @Roopa Reddy, @Amy.reardon@cpuc.ca.gov, & @Jake Richardson (PG&E)

        We've applied your feedback to the prototype and would appreciate another review — specifically regarding your comment that “the Fuel Sub Infrastructure Cost table contains only non-PII information, even though it's submitted alongside PII data.”

        Changes to the PII card on the specifications page:

        • PII Data Rules → PII and Fuel Sub Infrastructure Data Rules

        • View PII Data Rules → View Data Rules

        • Download PII Data Rules → Download Data Rules

        Page descriptions updated to:

        “The reporting of Personally Identifiable Information (PII) data and Fuel Sub Infrastructure Cost data is completed outside of Cedars at the same time as Cedars claim submissions. In aggregate, PA submissions are expected to align exactly with that year's cumulative Cedars claim data.


        The submission includes:

        • Two PII data tables.

        • One Fuel Sub Infrastructure Cost table containing non-PII information.


        All files are packaged together in a single .zip file for submission.
        The two PII tables must be provided as pipe-delimited (|) CSV files with unquoted text values. Fields must be listed in the exact order shown in the specification.”

        As for this comment — "This file is currently being submitted in Excel as part of the zip file. It might be worth assessing any downstream impacts to stakeholders before switching to a pipe-delimited CSV format." — I'll add this to the agenda for Sonja to cover during the next dev-demo meeting, once she's back in office.

        Here’s the link to the prototype again:

        https://www.figma.com/proto/djSwjUOnQmtJGgHy5wcHbk/Claim-Specification-Update-2026?node-id=7396-2524&viewport=569%2C152%2C0.5&t=ad77ck1d3Kj4poE7-1&scaling=scale-down-width&content-scaling=fixed&page-id=7396%3A2523

        Thank you,

        Erika

        • Amy.reardon@cpuc.ca.gov

          Team•

          Jul 6

          Hi @Erika Miller When do you need feedback by? I’d like to make sure the ex ante team gets a chance to review.

          • cedars team

            Team•

            Jul 7

            Hey @Amy.reardon@cpuc.ca.gov ,

            Since the UAT for the 2026 Claims Spec begins on July 15, feedback sooner rather than later would be ideal.

            Do you know if the ex ante team has visibility into this Featurebase ticket? If not, I'd be happy to reach out to them if you could share their contact information. Also, are they currently attending the dev demo meetings, and should we extend an invite for the next one?

            Thank you,

            Erika

        • Roopa Reddy

          Team•

          Jul 6

          @cedars team @Amy.reardon@cpuc.ca.gov @Jake Richardson (PG&E)

          Hi Erika, Thank you for the follow-up.

          I can confirm that the completed changes align with PG&E's feedback and address all requested updates. Regarding the Fuel Sub Infrastructure Cost file format, we can certainly discuss it during the next dev-demo meeting. Thanks for adding this to the agenda.

          Thank you!

  • Roopa Reddy

    Team•

    Jun 10

    Here is the link to the CPUC request posted in Basecamp back in 2023: EE Reporting & Data Management PCG: Fuel Substitution Infrastructure Costs

  • GGolden42

    •

    Jun 10

    I don’t think this should be added to the claims table for many reasons. not the least of which the number of fields are becoming extremely burdensome and we are getting push back for the details from our implementers.

    • Roopa Reddy

      Team•

      Jun 10

      This ticket requires documenting the current reporting requirements on the CEDARS claim specification page. The proposal does not include adding fuel-sub cost fields to the claim table. Hope this is helpful.

      • GGolden42

        •

        Jun 10

        Yes, thank you.

  • cedars team

    Team•

    Jul 9

    Hi @Roopa Reddy & @Amy.reardon@cpuc.ca.gov

    I’ve put together a quick mock-up the User Guide to include information regarding the Fuel Substitution Infrastructure data.

    Could you please review it and let me know if you have any feedback on:

    • The description for “What is Fuel Sub Infrastructure Data?”.

    • The guidelines for formatting and naming the Fuel Substitution Infrastructure Cost file.

    https://www.figma.com/proto/djSwjUOnQmtJGgHy5wcHbk/Claim-Specification-Update-2026?node-id=7532-621&t=Lk3AL8WhJQib6xTY-1&scaling=min-zoom&content-scaling=fixed&page-id=7396%3A2523

    Thank you,

    Erika

    • Roopa Reddy

      Team•

      Jul 10

      @cedars team @Amy.reardon@cpuc.ca.gov

      Hi Erika,

      The user guide instructions look good to me.

      We were provided with one additional submission instruction that should be incorporated into the guidance:

      PII data and Fuel Sub Infrastructure Cost data should be submitted to the Energy Division (ED) Reporting Lead, Amy Reardon, via the CPUC’s Kiteworks SFTP server https://kwftp.cpuc.ca.gov/ at the time quarterly claims are submitted. If assistance with Kiteworks is needed, users may use the Help button within the application to contact the CPUC IT Support team or contact the ED Reporting Lead directly via email.

      Thank you!

      • cedars team

        Team•

        Jul 13

        Hi @Roopa Reddy,

        I’ve incorporated this guidance to the top of the “Preparing your Claims PII and Fuel Sub Infrastructure file” section of the User Guide. Please let me know if you think there’s a better place for it.

        Thank you,

        Erika

        • Roopa Reddy

          Team•

          Jul 13

          Thank you, Erika.

  • Roopa Reddy

    Team•

    Jul 30

    @cedars team @Jake Richardson (PG&E)

    I noticed that, as part of the Fuel Sub Infrastructure Cost data, we have been including the Application Code in our submissions to date. I’m not sure whether this requirement was added later, as it was not part of the original specification.

    Could you please verify whether all PAs have been including the Application Code as part of these cost submissions through Kiteworks?

    I’m also checking internally to gather any historical context on how this requirement originated.

    Thank you!

    • Derya Gumustel

      Team•

      Aug 3

      Hi @Roopa Reddy, as far as I can tell not all PAs have been including the Application Code field in their Fuel Sub Infrastructure Cost data submissions. Let us know if you need any more detail or have any follow-up questions.

      • Roopa Reddy

        Team•

        Aug 4

        @cedars team

        Hi Derya,

        Since the Application Code field is not included in the current CPUC specification on the website (Fuel Sub Infrastructure Costs Data Collection Template), and the information can already be cross-referenced using the Claim ID, we believe it is appropriate to follow the published specification and not require the Application Code field as part of the Fuel Sub Infrastructure Cost submission.

        Thank you for looking into this. No further action is needed at this time.