4 Colo. Code Regs. § 723-3-3541

Current through Register Vol. 47, No. 11, June 10, 2024
Section 4 CCR 723-3-3541 - Web Portal
(a) The utility shall make available a web portal that provide map-based and tabular data that is publicly available or access-restricted as further defined under this rule. Such web portal shall be designed to meet the objectives of the DSP and shall allow users to download data in tabular and geospatial formats
(b) The utility may only deny access to its web portal if visitors and/or registrants violate the terms of service or other agreed upon terms of access. To ensure the appropriate level of protection of sensitive information, the utility may require visitors to the web portal to take actions, including:
(I) requiring visitors to acknowledge terms of service associated with its use, provided those terms do not preclude academic or public policy purposes; and
(II) establishing registration processes, including the creation of a username and password, and/or the use of multifactor authentication for access to sensitive information.
(c) A web portal shall include at least the following information:
(I) consistent with subparagraph 3531(a)(II), the utility's hosting capacity analysis;
(II) publicly available summaries, data, or links to existing information on the utility's website related to programs approved by the Commission that address the deployment of DERs, including, without limitation, pilots, tariffs, and incentives; and
(III) any additional content as directed by the Commission.
(d) Implementation of the web portal.
(I) Prior to filing its first DSP application pursuant to rule 3529, the utility shall engage potential users of the web portal from multiple sectors to develop a proposal for implementation of the web portal to be filed with the application.
(II) In its first DSP application pursuant to rule 3529, the utility shall present a proposal and timeline for developing a web portal that meets the requirements of this rule and includes:
(A) a summary of its process for identifying and engaging potential users of the web portal and the results of that process;
(B) a description of use cases that will be implemented through the web portal to meet the objectives of DSP;
(C) an evaluation of the data required in a DSP application pursuant to rule 3529 that addresses what data will be provided on the web portal and at what level of granularity, an evaluation of the risks and benefits associated with providing such data, proposals for treatment of sensitive information, and identifying any data for which confidential or highly confidential treatment is sought under the process provided in paragraph 3540(c);
(D) a proposal for providing functionalities that enhance the user experience, such as color-coding of substations, circuits, and feeders or ability to change the year of the data being displayed;
(E) a proposal for what information is currently available and can be provided on a web portal and what information requires approval by the Commission for incorporation onto a web portal;
(F) a proposal for updating data provided through the web portal, specifically addressing the quarterly updating of the utility's hosting capacity analysis as described in subparagraph 3531(a)(II);
(G) a proposal for enabling Application Programming Interface (API) capabilities where reasonable and appropriate; and
(H) a proposal for collecting user feedback on an ongoing basis.
(III) In subsequent DSP application proceedings, the utility shall provide an update on the status of implementing the web portal and any proposed changes to functionality and treatment of data. Prior to each application pursuant to rule 3529, the utility is encouraged to engage with stakeholders including users of the web portal, to identify changes.
(IV) The utility shall file an annual compliance report in the most recent DSP application proceeding that provides an update on the status of implementing the web portal, summarizes user feedback, and describes how the utility addressed that feedback, including any updates or revisions to the functionality of the web portal that are anticipated to occur prior to its next DSP application filing.

4 CCR 723-3-3541

38 CR 17, September 10, 2015, effective 9/30/2015
39 CR 06, March 25, 2016, effective 4/14/2016
39 CR 08, April 25, 2016, effective 5/15/2016
40 CR 22, November 25, 2017, effective 12/15/2017
42 CR 03, February 10, 2019, effective 3/2/2019
42 CR 07, April 10, 2019, effective 4/30/2019
42 CR 09, May 10, 2019, effective 5/30/2019
43 CR 08, April 25, 2020, effective 5/15/2020
43 CR 12, June 25, 2020, effective 7/15/2020
43 CR 20, October 25, 2020, effective 11/14/2020
44 CR 13, July 10, 2021, effective 7/30/2021
44 CR 24, December 25, 2021, effective 1/14/2022
45 CR 18, September 25, 2022, effective 10/15/2022
46 CR 02, January 25, 2023, effective 2/14/2023