User: aborja, Location: New York
Asked on: Monday, October 6, 2025 at 2:28 pm EDT
Answered on: Monday, October 6, 2025 at 2:30 pm EDT
Question: Sample Single Line DiagramContext: The existing meter-main (service disconnect) feeds a Microgrid Controller (MGC)—e.g., Tesla Gateway 3, Enphase IQ Controller, etc. PV and ESS outputs land inside the MGC. The existing main-breaker load center becomes a protected/backup (or whole-home) panel downstream of the MGC.We’re trying to choose the correct NEC 705 interconnection method for this topology. We see two plausible readings:Option 1 — Busbar method: 705.12(B)(3), typically (B)(3)(3) “sum of all OCPDs”Interpretation:The power-source output connections (PV/ESS inverter outputs) land on the MGC’s internal bus via dedicated breakers. Therefore, evaluate that bus under 705.12(B)(3). The common path is (B)(3)(3): the sum of the ampere ratings of all OCPDs mounted on that bus (supply + load devices), excluding the OCPD that protects that bus, shall not exceed the bus rating.If the MGC is lugged-out (no load/output breaker on the MGC bus): the sum is typically just PV + ESS breakers (often well ≤ 200 A), so (B)(3)(3) passes.If the MGC does have a load/output breaker on the same bus, that breaker counts in the sum. In some whole-home cases, PV + ESS + load breaker can exceed the 200 A bus rating → (B)(3)(3) fails.PCS path: When the controller is listed as a PCS and configured to limit current, we would instead claim 705.13 (PCS) compliance—treating the PCS setting as the “power-source output current” for 705.12 calcs. That’s a separate compliance path (not making (B)(3)(3) true).Why this seems right to us:705.12 creates distinct methods for busbars vs feeders/taps. In this topology, the DER outputs don’t splice into feeder conductors; they terminate on the MGC bus. Thus the busbar method applies at the equipment where sources parallel the EPS.Option 2 — Feeder / Feeder-Tap method: 2023 705.12(A)Interpretation:Define the Point of Interconnection (POI) as the feeder landing at the MGC—i.e., “where the new equipment (the microgrid system) connects to the home's electrical system” Treat the microgrid system (MGC + PV + ESS) as a composite source exporting to the premises at that point. Because the POI is on the feeder, apply feeder/tap rules: ampacity ≥ 125% of source output current, or protect the downstream feeder segment with OCPD at the connection per the subsection options, etc.Why this seems plausible to others:Verbiage like “Where the power-source output connection is made to a feeder…” could be read as including a microgrid controller interface at the feeder as the “power-source output connection,” since the microgrid as a system exports at that point—even though the individual PV/ESS outputs terminate on an internal bus.Main QuestionFor applying 705.12, should “power-source output connection” be understood as the DER output(s) landing point (i.e., the MGC bus), or can the microgrid controller’s feeder interface itself be considered the “power-source output connection” for feeder methods?
This is a complex and nuanced interpretation of NEC 705, and the fact that there are two plausible interpretations highlights the need for clarity in the code. Here's a breakdown of my understanding and recommendation, addressing your main question
Your Question: For applying 705.12, should “power-source output connection” be understood as the DER output(s) landing point (i.e., the MGC bus), or can the microgrid controller’s feeder interface itself be considered the “power-source output connection” for feeder methods?
Answer: The most defensible interpretation of "power-source output connection" in this scenario is the DER output(s) landing point, i.e., the MGC bus. Therefore, Option 1 (Busbar Method) is generally the more appropriate approach.
Here's why: Precision of the Term "Output"
The term "output" strongly implies the point where the individual power sources (PV inverters, ESS inverters) deliver their power. These outputs directly connect to the bus within the MGC. The MGC then aggregates and manages those outputs. Thinking of the MGC's feeder connection as the power-source output blurs the lines and introduces ambiguity.
Logical Flow of Power
The power flows from the PV/ESS inverters to the MGC bus before it flows onto the feeder. The feeder is the output of the system (MGC + PV + ESS), not the output of the individual power sources.
Avoiding Double-Counting and Unnecessary Constraints
Treating the MGC's feeder connection as the "power-source output connection" for feeder methods could lead to overly conservative requirements and potentially require upsizing conductors and OCPD based on the aggregate capacity of the PV and ESS, even if the MGC is designed and certified to limit output current. This can be costly and potentially unnecessary.
Intent of 705.12
The purpose of 705.12 is to ensure that conductors and equipment are adequately sized to handle the potential backfeed of power from DERs. By focusing on the MGC bus, you're directly addressing the location where the power sources combine and the potential for overcurrent exists at that point.
Why Option 2 (Feeder/Feeder-Tap Method) is Less Appropriate (But Not Entirely Invalid)
You're right that the language "Where the power-source output connection is made to a feeder..." could be stretched to include the MGC's feeder interface. However, this interpretation relies on viewing the entire microgrid system as a single, composite power source, which isn't the most natural reading of the code.
Risk of Ambiguity
Interpreting the MGC's feeder connection as the "power-source output connection" opens the door to significant ambiguity and inconsistencies in applying 705.12. For example, if the MGC is replaced with a different model, would the entire feeder analysis need to be redone?
Potential for Misapplication
Applying feeder tap rules to the MGC feeder interface could lead to situations where the feeder is excessively over-sized or overly protected, hindering the cost-effectiveness of the installation without providing a significant increase in safety.
Recommendation and Clarifications
1.
Prioritize Option 1 (Busbar Method)
This is the most straightforward and generally applicable interpretation of 705.12 for this topology.
2.
Address Concerns About the MGC's Output
PCS Listing (705.13)
If the MGC is listed as a Power Conversion System (PCS) and configured to limit output current, you should definitely utilize 705.13. This provides a clear and defensible pathway to using the PCS's output limit as the "power-source output current" for 705.12 calculations. This is crucial for avoiding overly conservative requirements.
3.
MGC Load/Output Breaker
Be mindful of the MGC's load/output breaker. If the sum of the PV, ESS, and load breaker ratings on the MGC bus exceeds the bus rating, you need to address this. Options include:
PCS Listing (Best)
As mentioned above, using the PCS listing to limit the aggregate output is the preferred solution.
Derating
If PCS listing isn't available, consider derating the PV or ESS systems to ensure the sum stays within the bus rating.
Upgrading the MGC (Least Desirable)
In the most extreme case, you might need to select an MGC with a higher bus rating.4.
Document Your Interpretation
Regardless of which option you choose, thoroughly document your interpretation of 705.12 in your design documentation. This will be invaluable during permitting and inspection.
5.
Consult with the AHJ
The Authority Having Jurisdiction (AHJ) is the final arbiter of code interpretation. It's always a good idea to discuss your design and interpretation of 705.12 with the AHJ before you begin installation. This can help avoid costly rework later.
In Summary:
The busbar method (Option 1) is generally the more appropriate and defensible interpretation of 705.12 in this scenario, especially when coupled with a PCS-listed MGC that limits output current. Careful documentation and consultation with the AHJ are essential. Flag for review