A statement from the Registration Provider applicant certifying the reliability and accuracy of the Data Registry when used for registration of Compliance Documents in accordance with the requirements of Standards Section 10-103(a), Appendix JA7. Refer to the Data Registry Requirements Manual for additional guidance.

The template for the Registration Provider Certification Statement document may be published in the Data Registry Requirements Manual, and electronic versions of the Registration Provider Certification Statement template shall be made available to the Registration Provider applicant upon request.

Electronic copies of the results from the Registration Provider's document registration self-tests shall be provided.

Refer to the Data Registry Requirements Manual for additional guidance on performing and reporting self-tests.

A copy of the user manual for the Data Registry shall be provided in an electronic format that can be utilized by word processing software. Help screens from the Data Registry user interface, organized into an electronic document file with a table of contents is an acceptable alternative to the requirement for a user manual.

Username and password information shall be provided to allow access to the Data Registry for Energy Commission staff to perform acceptance testing of Data Registry functionality.

The Registration Provider's digital signature public key shall be made available such that the digital signature on registered documents produced by the Data Registry can be tested.

Data Registry approvals shall conform to all applicable requirements and procedures specified in Standards Section 10-109 and 10-110.

A working agreement document or contract shall be executed between a Registration Provider and an External Digital Data Source (EDDS) services provider as prerequisite to approval of the EDDS for use for transmittal of data to the Data Registry for Title 24, Part 6 document registration. The agreement shall describe the specifications of any Internet-based EDDS services or EDDS software utilized to store the compliance document data on behalf of authorized users of the Data Registry, including description of any Internet-based data gateway interfaces (such as an API) used for sharing the compliance data with third parties.

Applications for approval of a Data Registry to use EDDS services shall include documentation to disclose the details of the working agreement(s) or contract(s) between the Registration Provider and EDDS services Provider. This documentation shall include descriptions of the parties involved, and the technologies used for the data exchanges between the EDDS and the Data Registry.

A separate agreement is required for each working relationship between a Data Registry and an EDDS. EDDS services providers may be approved to provide services to any number of approved Registration Providers. Registration Providers may be approved for use of any number of EDDS services providers. Where a Registration Provider makes use of an Application Programming Interface (API), each EDDS that the API interfaces with must be approved.

Full approval by the Energy Commission shall be required when an applicant Registration Provider has not previously been approved by the Energy Commission.

Full approval by the Energy Commission shall be required whenever major changes are made to a Data Registry's functionality, security, or technology features that necessitate acceptance testing of more than 30% of the compliance document templates used in the applicant's Data Registry library.

Full approval by the Energy Commission shall be required when the Standards are updated (re-approval). When Data Registry re-approval is mandated by the Energy Commission, all Registration Providers shall be notified of the re-approval timetable. Refer to the Data Registry Requirements Manual for additional guidance on the re-approval process.

Full approval shall ensure the Data Registry conforms to all applicable requirements for functionality and security in Appendix JA7 including but not limited to:

1. Capability to produce and manage registered documents (JA7.5).
2. Electronic signature capability, and manage authorization of users (JA7.6.3.2.1).
3. Document data validation (JA7.6.3.2.2).
4. Signer review and signature actions (JA7.6.3.2.3).
5. Digital signature and digital certificate actions (JA7.6.3.2.4).
6. Capability to transmit secured documents and data to the Commission Compliance Document Repository (JA7.6.3.2.5).
7. Document retention capability (JA7.6.3.2.6).
8. Capability to receive and process electronic data using best practices for secure data exchange, using data sources and procedures approved by the Energy Commission for registering compliance documents (JA7.6.3.2.7; JA7.7).
9. Capability for data exchange with the compliance report generation services made available by the Energy Commission to generate formatted electronic documents (JA7.2, JA7.7).

Amendments and revisions to existing Data Registry software and services for which full approval by the Energy Commission is not required, may be approved by the Executive Director through a streamlined process.

Changes that qualify for streamlined approval include minor changes to the Data Registry document registration procedures, data input specifications and procedures, or registered compliance document output.

Any application for amendment or revision to existing Data Registry software and services shall be accompanied by a cover letter explaining the type of amendment or revision requested, and copies of any applicable documents that are necessary to fully describe and justify the proposed amendment or revision.

All items on the application checklist in section JA7.8.2 that are applicable to the proposed amendment or revision shall be submitted.

When Data Registry modifications qualify for streamlined approval, the following procedure shall be followed:

1. The Registration Provider applicant shall notify the Executive Director in writing to provide a description of the change and the reason for making the change.
2. The Registration Provider applicant shall prepare an addendum to the user manual describing the change to the Data Registry if applicable.
3. The Executive Director shall respond to the Registration Provider applicant in accordance with the procedures specified in Standards Section 10-110. The Executive Director response to the applicant may:
   1. Approve the modification;
   2. Request additional information;
   3. Refuse to approve the modification;
   4. Require the Registration Provider to submit results of additional acceptance tests applicable to the modification; or
   5. Require that the Registration Provider make specific changes to either the User Manual addendum or the Data Registry functionality.
4. Subject to approval by the Executive Director, the Registration Provider may make the modified Data Registry available for use for registration of compliance documentation, along with the modified user manual or addendum to the user manual, and shall notify authorized users of the Data Registry when modifications to the Data Registry have been made available.

1. All Data Registries are deactivated when the Standards undergo substantial changes, usually occurring with each Standards update. However, the Data Registry shall remain approved to provide document registration for projects that have been permitted under the prior versions of the Standards.
2. Any Data Registry can be deactivated by a letter from the Registration Provider requesting that the Data Registry be deactivated. The deactivation request shall briefly describe the reasons that justify the need for deactivation.
3. The Executive Director may at any time, including upon petition by any party or recommendation by Commission staff, initiate a review of a Data Registry approval according to the steps outlined in Section JA7.8.4.2 below. The intent is to provide a means whereby serious Data Registry errors, violations of JA7, flawed numeric results, or improper registered document output not discovered in the Data Registry approval process can be verified, and a corrective course of action determined. Also, the intent is to provide ample opportunity for the Commission, the Registration Provider, and all interested parties to evaluate any alleged errors in the Data Registry functionality.

A description of the process for challenging a Data Registry or initiating a deactivation procedure follows:

1. Any party may request a review of a Data Registry approval by submitting a petition to the Energy Commission's Executive Director. petition shall:
   1. State the name of the Data Registry that contains the alleged errors or violations of the Registration Provider’s obligations under JA7;
   2. Identify concisely the nature of the alleged errors or violations of the Registration Provider’s obligations under JA7 in the Data Registry that require review;
   3. Explain why the alleged errors are serious enough in their effect on document registration compliance to justify a deactivation procedure; and
   4. Include appropriate data electronically (in a format agreed to by the Executive Director) and/or information sufficient to evaluate the alleged errors or violations of JA7.
2. The Executive Director shall make a copy or copies of the petition or Commission Staff’s recommendation report available to the Registration Provider and interested parties within 30 days. Comments from interested parties shall be received within 60 days of the acceptance of the original application.
3. Within 75 days of receipt of the petition or recommendation report, the Executive Director may request any additional information needed to evaluate the alleged Data Registry errors or violations of the Registration Provider’s obligations under JA7 from the party who initiated the deactivation review process. If the additional information is incomplete, this procedure will be delayed until the initiating party submits complete information.
4. Within 75 days of receipt of the petition or recommendation report, the Executive Director may convene a workshop to gather additional information from the initiating party, the Registration Provider and interested parties. All parties will have 15 days after the workshop to submit additional information regarding the alleged Data Registry errors or alleged violations of the Registration Provider’s obligations under JA7.
5. Within 90 days after the Executive Director receives the petition or recommendation report or within 30 days after receipt of complete additional information requested of the initiating party, whichever is later, the Executive Director shall either:
   1. Determine that the Data Registry need not be deactivated; or
   2. Submit to the Energy Commission a written recommendation that the Data Registry be deactivated.
6. If the Energy Commission approves the Data Registry deactivation, it shall take effect 60 days later. During the first 30 days of the 60 day period, the Executive Director shall send out a Notice to Enforcement Agencies and Interested Parties announcing the deactivation.

All initiating parties have the burden of proof to establish that the review of alleged Data Registry errors should be granted. The deactivation process may be terminated at any time by mutual written consent of the initiating party and the Executive Director.

The Registration Provider may use the 180 to 210-day period outlined here to update the Data Registry, get it re-approved by the Commission, and make available for use by authorized users the revised version of the Data Registry that does not contain the errors or violations initially brought to the attention of the Commission.

This section shall discuss the Data Registry capabilities, providing explanation of how to access these capabilities, and the purpose for each of these features.

This section shall cover the basic use of the Data Registries to prepare each of the basic Compliance Document types, and should include a complete summary of all document creation methods or commands necessary to complete the required registered documents.

This section shall contain instruction for completing submittals of completed registered documents to enforcement agencies or other persons who require copies of completed registered documents. Instruction shall be given for all methods of submittal the Data Registry supports, including various methods for submittal of electronic copies of the registered documents, as well as for printing of paper copies.

This section shall include an example of a complete set of compliance documentation for a sample building. The building need not be overly complex, nor need it include every document type possible. The example should, however, include example documentation for all compliance document types that would normally be submitted for typical occupancy types administered by the Data Registry.

When a Data Registry is approved to make available use of EDDS features to authorized users of the Data Registry for data input during document registration procedures, the Data Registry user manual shall include instructions for use of those features. The instructions shall describe use of the Data Registry user interface for EDDS data input procedures. Additionally, if the EDDS services provider has a user interface or software application that the user is expected to access and operate that is independent of the Data Registry user interface, a copy of the EDDS service or software user instructions shall be included in the Data Registry User Manual. If the EDDS service or software user instructions contain proprietary information or intellectual property, the EDDS service or software user instructions do not need to be included in the Data Registry User Manual. However, the EDDS service or software user instructions must be made available to all authorized users that use the EDDS service or software.