How to Add Utility Interconnection Process to Your Project Milestones
This article explains the specific steps to adding project milestones for tracking the Utility Interconnection process within your overall project milestone processes. See the Managing Your Company Processes Using Milestones article for general information. This article builds on that article for the specific Utility Interconnection process. Its a great example process to add for almost all SolarNexus companies.
Step 1 - Create "Utility Interconnection" Milestone Group
All milestones belong in a grouping that defines a sub-process within your overall project processes. It allows you to quickly filter and see the status of only the steps involved in the particular process you are interested in. The steps are simple:
- Go to the Administration > Project Milestones screen.
- At the top, click on the Show By Group radio button. You'll see the current groups (aka sub-processes) that are currently defined.
- Check that you haven't already defined a "Utility Interconnection" group.
- Click the "Add Group" button at the top of the screen. Enter "Utility Interconnection" for the name of the group and click "Save."
Now you have a container group to hold the milestones relevant to this sub-process.
Step 2 - Define Overview of Process Steps
Prior to inputting the individual milestones in SolarNexus, we recommend creating a quick overview list of your process steps first. Remember that a milestone is a distinct completion point in a process, marking when a next step can proceed.
Here's a typical set of process milestones for a Utility Interconnection process:
- NEM agreement and customer authorization submitted
- Interconnection application submitted
- PTO Granted
Step 3 - Define First Process Step, "Submit Interconnection Application"
After adding the Utility Interconnection group. Return to the top of the Milestones screen and click the "Show In Display Order" radio button. Now we can add individual milestones.
- Click the "Add Milestone" button
- Complete the milestone definition form for the first milestone:
- Completed Name - "NEM Agreement and Customer Authorization Submitted"
- Incomplete Name - "Submit NEM Agreement and Customer Authorization"
- Milestone group - Utility Interconnection
- Description and Criteria - Input a description that can tell your employee what is expected to be complete for this milestone to be considered complete. For example, "Agreement & Customer Authorization Form successfully submitted through the PG&E online application."
- Predecessor - If the utility requires the system size, and it can't be easily updated later, you will probably want to wait until after the permit design is complete, so select "Permit Application Submitted." Or if you can submit immediately following the sale, choose "Sold."
- Default User to assign - If you have a dedicated person on your team who does all of these, select that person. Whenever a project gets to this point in the process, that person will automatically be assigned and notified.
- Statuses - Pending
- Assign Project Roles Upon Completion / Results in a Scheduled Event are not applicable.
- Update Close Probability - This is disabled because the milestone's predecessor is after the sale.
- Milestone is a Scheduled Event - Not applicable.
- Set Completion Deadline - Do you have an expectation of how many days & hours this task should take to complete? If so, you can set a timeout so that if the milestone is not completed in the given timeframe, SolarNexus will notify somebody. The intent is to make sure that no key process steps are forgotten. Remember, that the clock only starts ticking at the point that the predecessor is completed. So in this case, if the predecessor was when the Permit Application is Submitted, then the clock will start ticking then.
- Third Party Notifications - Use this feature to notify your customer (or another party) when this milestone is completed. In this example for the PG&E utility, the utility's application uses Docusign to get the customer's signature. As the installer I want to send the customer an Email that explains to the customer that they need to E-sign the authorization from PG&E, and if they don't get it, to notify us immediately. To use this feature, we need to create the Email template using the Document Templates functionality.
- Project Inclusion - If all of your projects include PV, its fine to leave as "All." However, you may have some projects that don't require Interconnection steps. In that case, create a rule that only this milestone is relevant if "Sold Solution Scope" includes "Grid-Tie PV".
- Click the "Save" button.
Step 4 - Define Additional Milestones
Use the same process described above to define additional process milestones. We've provided sample recommended configurations in the table below for the milestones in our example process.
Process Order | Step 1 | Step 2 | Step 3 |
Incomplete Name | Submit NEM Agreement and Customer Authorization | Submit Interconnection Application | Wait on PTO From Utility |
Completed Name | NEM Agreement and Customer Authorization Submitted | Interconnection Application Submitted | Permit to Operate Granted |
Milestone Group | Utility Interconnection | Utility Interconnection | Utility Interconnection |
Description & Completion Criteria | "Agreement & Customer Authorization Form successfully submitted through the PG&E online portal." | "Interconnection Application successfully submitted through the PG&E online portal." | "Official Permit To Operate letter received from PG&E." |
Predecessor | "Permit Application Submitted," or "Sold" | "AHJ Approved" | "Interconnection Application Submitted" |
Default User | Specify your user, if desired. Otherwise can manually assign in Management Panel. | Specify your user, if desired. Otherwise can manually assign in Management Panel. | N/A, this is actually done by third party, only the receipt is done by your company. |
Statuses | |||
Assign Project Roles Upon Completion | Assume roles are already set. | Assume roles are already set. | Assume roles are already set. |
Results in a Scheduled Event | N/A | N/A | N/A |
Update Close Probability | N/A | N/A | N/A |
Milestone is a Scheduled Event | N/A | N/A | N/A |
Set Completion Deadline | Yes, 2 days | Yes, 1 day 12 hrs | Yes, 10 days |
Third Party Notifications | Yes, select Email template composed to tell customer to expect Email from utility and they need to E-sign the authorization agreement. | Yes, select Email template composed to tell customer that we're just waiting for PG&E to provide approval. | Yes, select Email template telling customer that the utility has approved operation, and will turn on the system. |
Project Inclusion | "All" (If some jobs don't include PV, define a rule) | "All" (If some jobs don't include PV, define a rule) | "All" (If some jobs don't include PV, define a rule) |