Distributed Energy Interconnection Readiness Calculator

Introduction

Interconnection is often the critical path for distributed generation and storage projects. Even when equipment is available and site control is secure, a project can still stall in the utility queue because a study cycle takes longer than expected, documentation comes back incomplete, or the internal team does not have enough time to respond quickly. This calculator provides a practical way to test whether your project team can finish the expected interconnection work within the remaining queue window and what the likely near-term cost exposure looks like while that work is happening.

The model is deliberately simple and management-friendly. It converts the remaining milestone plan into total internal hours, compares those hours with available weekly team capacity across the time left in the queue, and then summarizes cost exposure from study fees and potential utility upgrades. That makes it useful for project reviews, financing conversations, internal staffing discussions, and sensitivity checks such as asking what happens if contingency rises because the utility requests supplemental information.

How to use

1. Enter your system capacity in kW using the AC rating that appears in the interconnection package or that will be used for utility review.
2. Enter estimated study fees and potential upgrade cost. If one value is still unknown, you can enter zero for a rough staffing view, but the cost outputs will then be incomplete.
3. Estimate internal team hours available per week. This should reflect the people who actually move the application forward, such as project management, electrical engineering, utility coordination, legal review, and permitting support.
4. Estimate hours required per milestone and the number of major milestones still ahead. Typical examples include screening, impact or facility studies, agreement negotiation, construction coordination, witness testing, and final approval steps.
5. Enter utility queue days remaining until the deadline you care about most. That may be a tariff cut-off, a program milestone, a financing trigger, or a target commercial operation date.
6. Set a contingency factor to reflect expected rework, additional information requests, revised single-line diagrams, field inspection loops, or other non-ideal but common delays.
7. Select Calculate readiness to update the readiness summary and the queue pacing scenario table.
8. If you want a record for a project memo or lender package, choose Download readiness CSV to save both inputs and outputs.

Formula

The calculator uses a capacity-versus-demand framework. First it estimates the amount of internal effort still required. Then it compares that requirement with the working hours your team can realistically supply before the queue deadline. Costs are summarized separately because they affect project finance even when staffing looks sufficient.

• Base internal hours = hours per milestone × number of milestones
• Total internal hours with contingency = base hours × (1 + contingency/100)
• Weeks remaining = queue days remaining ÷ 7
• Available capacity hours = team hours per week × weeks remaining
• Hour gap = available capacity hours − total internal hours
• Total cost exposure = study fees + potential upgrade cost
• Cost per kW = total cost exposure ÷ system capacity

In MathML form, the internal-hours calculation is:

Here, M is the number of milestones, h is the average internal hours per milestone, and C is the contingency percentage. The readiness message is then based on whether the hour gap is positive or negative. A positive gap means your modeled staffing can keep up with the remaining work. A negative gap means that, under the assumptions entered, the team is likely to run short of time before the queue window closes.

Worked example

Suppose you are planning a 5,000 kW solar-plus-storage project and expect 6 major interconnection milestones remaining. Your team estimates 60 hours per milestone of internal effort, and you want a 30% contingency to cover re-submittals and additional utility questions. You have 95 hours per week of internal capacity and 56 queue days remaining, or roughly 8 weeks. You also expect $85,000 in study fees and $240,000 in potential upgrades.

• Base hours = 6 × 60 = 360 hours
• Total hours = 360 × (1 + 0.30) = 468 hours
• Weeks remaining = 56 ÷ 7 = 8 weeks
• Capacity hours = 95 × 8 = 760 hours
• Hour gap = 760 − 468 = 292 hours, which is a surplus
• Total cost exposure = 85,000 + 240,000 = $325,000
• Cost per kW = 325,000 ÷ 5,000 = $65 per kW

That result suggests the schedule is feasible from a staffing perspective, because the modeled team has more hours available than the remaining work requires. At the same time, the project still faces meaningful cash exposure from studies and upgrades. If you change contingency from 30% to 60% because the feeder looks more difficult than expected, the required hours rise quickly and the buffer shrinks. The calculator's scenario table is designed to make that kind of shift visible at a glance.

How to interpret the output in a real project review

A positive hour gap does not guarantee utility approval by a specific date. Instead, it means your internal team appears to have enough modeled capacity to keep up with the work that is still under your control. That distinction matters because many interconnection schedules slip before the utility reaches a final technical decision. Drawings arrive late, comments sit unanswered, legal review takes longer than expected, or engineers are spread across too many active projects. If your result shows a comfortable surplus, the next question is whether that capacity is also sequenced well enough to avoid idle time between utility requests.

A negative hour gap is usually best read as an early warning. In practice, it can point to overloaded engineering staff, weak document control, under-budgeted coordination time, or an unrealistic assumption about how quickly questions can be turned around. If the shortfall is small, the project may still recover by reallocating work, using outside consultants, simplifying design changes, or seeking clarification earlier in the process. If the shortfall is large, the result should trigger a broader schedule and budget reset rather than a minor patch.

The scenario table underneath the calculator is particularly useful for internal decision meetings. If the project remains feasible even after you add 20% or 40% more contingency, the plan is relatively robust. If a modest change in contingency flips the result from a surplus to a shortfall, the plan is fragile and depends on unusually smooth execution. That sensitivity often tells you more than the single headline result because it shows how narrow the true schedule margin may be.

Limitations and assumptions

• Linear effort assumption: the model treats work as if it can be distributed evenly across the remaining weeks. Real interconnection work is often lumpy, with intense bursts of activity followed by waiting on utility review.
• Milestone definition varies: one utility's milestone structure may be very different from another's. Use a consistent internal definition and update it as the project moves forward.
• External lead times are not explicitly modeled: equipment procurement, weather delays, third-party inspections, and construction sequencing can all affect final approval timing.
• Cost exposure is not the same as final net cost: some upgrade costs may be shared, reimbursed, or adjusted later under tariff rules. The calculator treats them as planning exposure today.
• Unknown inputs reduce reliability: if study fees or upgrade costs are placeholders, treat the result as directional and consider running low, medium, and high scenarios.

Use this calculator as a planning tool and communication aid, not as a substitute for utility guidance, the actual interconnection agreement, or professional engineering judgment.