PowerClerk Support Center

PowerClerk Program Launch

Submit the VersaForm at the bottom of this page to initiate the PowerClerk Program Launch procedure

Questions to ask yourself about your program launch:

When should the program launch?
Should the program allow self-registration?
How to receive support post-launch?

Ready, set, launch….!

Are you exploring this Support Center page because you are ready to launch your PowerClerk sandbox program to the Production environment and begin accepting applications? If so, you have come to the right place! We are just as excited as you are and will work to ensure everything goes smoothly.

PLEASE NOTE: Once ready, please use the VersaForm at the bottom of this page to initiate your program launch.

What does launching your program involve?

The process to launch a PowerClerk program entails three steps:

Step 1) Fill out the VersaForm below to start the process. A link to the full Project Launch Questionnaire will then be sent to you via email. Optionally, you can generate and save a .docx version of the questionnaire for internal discussion prior to completing Step 2.

Step 2) Follow the link from email to submit the Project Launch Questionnaire, which includes the program parameters as outlined below. This is your official request to launch your program.

Step 3) The CPR Support team will take a copy or ‘snapshot’ of your PowerClerk sandbox program configuration.

The program copy, along with the program parameters provided below, are then used to establish a new program within the secure PowerClerk production environment. The result is a program URL where end-users will access and administer the program going forward.

Required Information

General Program Launch Parameters

Figure 1: General Program Names and Prefixes

To create the production program, we will ask you within the Program Launch Questionnaire to provide information on the following launch parameters:

Agency Name: How your utility is referenced in PowerClerk (“Your Utility Name” e.g. “Clean Power Research”).

Agency Abbreviation: Used in PowerClerk where shortening the agency name is useful (e.g. “CPR”).

Logo: The official company logo to appear in the top left corner of PowerClerk (Format: .svg Size limit: 300 px wide and 100 px tall).

Program name: Will display as “[Agency Name] – [Program Name]” (e.g. “Clean Power Research – FERC Applications”).

URL prefix:

Will display as “[urlprefix].powerclerk.com” in production, e.g. “cprferc.powerclerk.com” – please note that percentage signs (%) or full stops (.) are disallowed.
It is recommended that this URL be descriptive in the event future PowerClerk programs are needed (e.g. a residential interconnection program and a commercial interconnection program; e.g. “cprres.powerclerk.com” & “cprcom.powerclerk.com”). We advise against just using your agency abbreviation e.g. “cpr.powerclerk.com”.

Project number prefix: The prefix for the PowerClerk Project Number which should be 2-6 characters, and all capital letters e.g. “CPR” to appear for projects as “CPR-00011”.

Time zone: Can be one of the following: “Pacific/Mountain/Central/Eastern/Hawaii/Alaska/Atlantic/Arizona/CentralMexico/CentralEurope“.

Desired Launch Date: Please aim for a date and time within regular CPR business hours (Mo-Fr 9:00 AM to 5:00 PM Pacific Time).

PV System Element Options

The following settings are only relevant for programs using PowerClerk’s PV System Specifications form element:

Figure 2: Configurable Parts of the PV System Form Element

PV Derate %: Default value is 10.

Input: Enable PV Array Description: yes/no. Allows applicants to type in a description.

Input: Hide Shading Information: yes/no. Select “no” to allow applicants to optionally enter shading information month by month.

Output: Display Inverter Nameplate Rating: yes/no.

Output: Display Estimated Production: yes/no. Shows annual estimated production in kWh

Output: Display Average Inverter Efficiency: yes/no.

Output: PTC Module Rating: yes/no.

Output: Display Monthly Production: yes/no. Shows annual estimated production in kWh

Learn more about enabling the PV System battery addition element on Forms.

Program Communication Settings

The following information will be gathered to denote Communication settings for your future production program.
By default, communications sent from PowerClerk programs in production come from DoNotReply@Powerclerk.com with the Display Name “PowerClerk Communications.” You can customize your Display Name. Leaving this blank will result in the default.

Communication display name: Used in Communication Emails sent out of PowerClerk.

(e.g. Figment Power DER Department)

As a default, the Communications do not include a Reply option. Responses will be received in an unmonitored inbox. You may prefer this default option in order to force all communication to happen within PowerClerk (for example, through the Project Inquiry Feature). However, if you would like email Replies to come to your email inbox, you can set a reply-to email address:

Communication reply-to email address: If supported by the applicant’s email provider, this setting pertains to the To: portion being automatically populated with the email address you wish to provide if the recipient clicks on their Respond/Reply button.

(e.g. DER@FigmentPower.com)

Communication reply-to display name: If supported by the applicant’s email provider, this is the name that would automatically populate along with the email address you wish to provide if the recipient clicks on their Respond/Reply button.

(e.g. Figment Power DER Department)

In coordination with the manager of your company’s Domain Name Server, you may also set up a Sender Email Address belonging to your domain.

Sender Address, if applicable: : If you have worked with your IT Department to allow PowerClerk.com to send emails on behalf of your company’s Domain Name Server, please confirm the sender email address. File a Support ticket to find out more about the process, which is recommended but not required. Please note that the
Announcements feature will not be available without a non-PowerClerk sender address.

Project Inquiry Feature and Program Support Contact Info

Read about the Project Inquiry Feature and decide whether you would like it to be enabled.

If Project Inquiries is enabled, users in non-admin roles will see an “Ask a Question” or “Submit an Inquiry” button with customizable text, as shown below.

Figure 3: Contact Info Under Inquiry Button

If not enabled, they will see a question mark icon. In both cases, your program’s contact information is housed under those buttons so that users can contact you if they need help while using your PowerClerk program. The Program Support Contact Info settings are configurable via Admin >> Program Info within PowerClerk.

Figure 4: Program Info Help Button

Please be prepared to provide:

Support Contact Email Address: Specify the email address where applicants may send inquiries regarding your PowerClerk program. This address will also be added to our PowerClerk Program Locator Map.

Website: Where an applicant can find additional information about your PowerClerk program or company website.

Phone number (optional): Specify the phone number applicants should call for assistance with your PowerClerk program.

Additional Settings

Allow Self-Registration: yes/no. This setting will allow PowerClerk user accounts to self-register for your program in the respective role you denote eligible for self-registration (e.g. likely the Applicant role).

Lead Program Designer in the production program: This is the individual who will be granted the Edit Users Role privilege by PowerClerk’s Support Team to allow adding other administrative users to the production program.

This information can also be provided as a .csv file to import multiple users. Only include Roles already created in PowerClerk and ensure the Role names match exactly. The required import file format is shown below.

Figure 5: Required header columns to import multiple users via .csv

Please note: New users created via this method will not be notified by PowerClerk, so please plan to notify them separately that they should navigate to the program and use the “Forgot Password” button to set their passwords. This step is not necessary if the users already exist in another PowerClerk program.

A Word of Caution

Please note that any changes made in the sandbox after you initiate your program launch (starting from the time you submit the Program Launch Questionnaire up to day 5 of the 5-day launch process) will not be transferred to production. Hence it is advisable to either:

Complete all configuration work in the sandbox prior to requesting the production launch.

Stop making changes in the sandbox during the 5-day production launch procedure period and wait for CPR to give your team access to the production program. Then, make any needed configuration changes in the production instance.

Form to Initiate Program Launch

Ready for launch? Once you submit the following form, please pause configurations until the program launch has been completed.

Cookie	Duration	Description
CloudFlare CDN	4 weeks	The cookie is set by CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.
CookieLawInfo Checkbox Necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category ‘Strictly Necessary’.
CookieLawInfo Checkbox Performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category ‘Performance’.
CookieLawInfo Checkbox Personalization	11 months	This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category ‘Enhancements & Personalization’.
Viewed Cookie Policy	11 months	This cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Website Search Interaction	Session	This cookie is set by Site Search 360, our search engine for all Clean Power Research websites, to record search session preferences and performance.
Website Search Session ID	11 months	This cookie is set by Site Search 360, our search engine for all Clean Power Research websites, to record search session preferences.

Cookie	Duration	Description
Google Analytics Data Limiter	1 minute	This cookie is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites.
Google Analytics Page Visits	1 day	This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
Google Analytics Random Identifier	2 years	This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to identify unique visitors.
Marketo Tracking	2 years	This cookie is associated with an email marketing service provided by Marketo. This tracking cookie allows the website to link visitor behavior to the recipient of an email marketing campaign, to measure campaign effectiveness.

Cookie	Duration	Description
Wistia Videos	11 months	Set by Wistia to support video functionality that may be found throughout the website. In addition to keeping track of the website visitor's position in a video should playback be interrupted, this cookie also notes user behavior regarding the video itself.
Wistia Videos Data	10 months	This cookie collects visitor interaction data regarding Wistia video content so that such content can be made more relevant to the visitor.