The Other Model in the Room: Building Utility-Grade Evidence Before Interconnection Review
Photo: utility grid interconnection study solar engineers reviewing load flow model, via images.ctfassets.net
An interconnection request is often treated as a administrative milestone: submit the forms, pay the fee, wait for the study, respond to the results. That framing understates what actually happens. When a utility reviews a solar project, it does not simply check whether the paperwork is complete. It runs its own models of the project, the feeder, and the broader system. Those models may use different assumptions, different data, and different software than the developer's engineering package.
The developer sees the study result. The utility sees the assumptions that produced it. That asymmetry is one of the most persistent sources of delay and disagreement in US interconnection today.
Two Models, One Queue
A developer's model is typically built to estimate production and support financial forecasts. It may focus on irradiance, layout, inverter loading, and expected annual energy. A utility's model is built to answer a different question: can the system be interconnected without compromising safety, reliability, or power quality? That requires load-flow analysis, short-circuit evaluation, voltage regulation studies, protection coordination, and hosting-capacity assessment.
The two models can be technically valid and still diverge. A developer may assume a certain power factor strategy; the utility may apply a default. A developer may model inverter clipping based on its own settings; the utility may assume a different reactive capability curve. A developer may use a generic feeder impedance; the utility may use its own records, which can be older or more detailed. None of these differences is necessarily an error. But each can change the study outcome.
Where Divergence Begins
The most common gaps appear in four areas. The first is project representation. Utilities often model a solar system as a simplified injection at a point of interconnection, while developers model the full array topology. If the utility's representation omits inverter-level behavior or aggregate plant controls, the study may not reflect how the project will actually operate.
The second is load and generation profiles. A utility may use its own historical feeder data or a standardized profile. A developer may use a different time series, a different resolution, or a different assumption about coincident load. The result can be a different hosting-capacity conclusion even when both parties believe they are studying the same project.
The third is protection and voltage assumptions. Utilities are responsible for reliable service, so they often apply conservative defaults. Developers may not know those defaults until a study returns with a required upgrade or a operating constraint.
The fourth is data vintage. Feeder models, transformer ratings, and protection settings are not always current. A utility may be working from records that predate recent load growth or nearby generation. The developer may have newer site-specific data but no formal channel to incorporate it before the study begins.
The Evidence Package
Closing the asymmetry does not mean demanding the utility's internal model. It means preparing a submission that answers the questions a utility is likely to ask before it asks them. A utility-grade evidence package should include a clear single-line diagram, project specifications, inverter and plant controller settings, expected reactive power capability, protection philosophy, and a production model with documented assumptions.
It should also include a narrative of operating behavior. How will the plant respond to voltage excursions? What power factor range will it maintain? How will it ride through frequency events? These are not marketing details. They are inputs to the utility's reliability assessment.
A useful practice is to run the project through a load-flow screen before submission, using conservative assumptions and documenting the results. The developer's screen will not match the utility's study exactly, but it can reveal obvious constraints early. If the project is likely to trigger a voltage or protection issue, the developer can address it in the application rather than wait for a study cycle to surface it.
Pre-Submission Modeling
Pre-submission modeling is not about guessing the utility's answer. It is about reducing the number of unknowns. Developers can build a feeder-level representation using publicly available data, utility planning documents, and prior study results. They can test sensitivity to power factor, voltage setpoints, and inverter loading. They can identify the conditions under which the project moves from benign to problematic.
This work also improves the quality of the developer's own assumptions. If a project only passes under an optimistic reactive power assumption, that is a risk worth knowing before the application is filed. If it passes under a range of conservative assumptions, the developer can present that robustness as evidence.
Contract and Process
Engineering evidence is only part of the solution. Interconnection agreements and study processes should define what data the utility will use and how discrepancies will be resolved. Developers can request pre-application meetings, clarify the utility's modeling conventions, and document agreed assumptions. In some jurisdictions, technical conferences or dispute-resolution procedures provide a formal venue for reconciling model differences.
These steps are not adversarial. They are a recognition that interconnection is a shared technical exercise. The developer who arrives with a well-documented model and a clear operating narrative is easier to study, easier to approve, and less likely to be sent back for revision.
The utility will always have its own model. The developer's task is to make sure the two models are close enough to support a productive review, and to preserve the evidence that explains why.