A microgrid looks simple on a single-line diagram: solar, storage, a generator or two, a point of interconnection. What that diagram doesn't show is the second-by-second coordination problem underneath it, where every inverter has to agree on voltage and frequency the instant the grid connection drops, and where a battery reserve that looked adequate on paper can still leave a facility short during an actual islanding event. Operations directors managing distributed generation portfolios are watching dispatch economics, state of charge, generator readiness, and interconnection status across assets that were often installed by different vendors on different control platforms over several years, each reporting data in its own format on its own schedule. That fragmentation is exactly where a genuinely reliable microgrid quietly turns into one that only works when nothing goes wrong at the same time. Book a demo to see unified DER visibility built for a real, mixed-vendor site.
AI-Powered · Distributed Generation · Microgrid Coordination
Your DER Portfolio Was Built in Pieces. It Needs to Operate as One System.
iFactory unifies dispatch, state of charge, generator readiness, and interconnection status across your distributed generation and microgrid assets, so the coordination gaps between vendors and control platforms get closed before an islanding event finds them for you.
Two Operating States
Grid-Connected and Islanded Mode Ask Completely Different Things of the Same Assets
The same hardware has to perform two fundamentally different jobs depending on grid status, and a portfolio tuned well for one mode can still be poorly prepared for the other if that distinction isn't tracked separately.
Grid-Connected
Distributed generation exports or offsets load against a stable utility reference for voltage and frequency, with the main job being economic dispatch: running the lowest-cost mix of solar, storage, and backup generation while respecting interconnection agreement limits.
→
Islanded
The microgrid loses its utility reference and must generate its own voltage and frequency signal in real time, with every distributed energy resource coordinating load sharing through droop control while battery reserves cover the gap until generation catches up.
The transition between these two states, and the resynchronization back to grid-connected mode once utility power returns, is where most microgrid coordination failures actually happen, not during steady-state operation in either mode alone. A portfolio can run flawlessly in grid-connected mode for years and still fail its first real islanding test, simply because that specific transition was never exercised under realistic conditions.
Portfolio Architecture
What's Actually in a Modern Distributed Generation Portfolio
Four distinct asset classes, four different vendors in many cases, and one shared responsibility for keeping the whole system stable through every operating transition.
01
Renewable Generation
Solar PV and, at some sites, wind assets providing the lowest-cost generation whenever conditions allow, but intermittent enough that they cannot be relied on alone for dispatch commitments or islanded operation.
02
Battery Energy Storage
The asset that actually makes islanding possible, absorbing renewable variability and covering the seconds-to-minutes gap between a grid disconnection event and generator startup.
03
Backup and Standby Generation
Diesel, natural gas, or dual-fuel generators sized to sustain the site through extended islanded periods once battery reserves have been drawn down.
04
Microgrid Controller and Interconnection
The coordination layer that manages dispatch, islanding detection, and resynchronization, sitting at the point of common coupling with the utility grid.
A Vendor-Fragmented Portfolio Is a Coordination Risk You Can't See From Any Single Dashboard.
Bring dispatch, state of charge, generator readiness, and interconnection status from every DER vendor into one operational view.
Where Coordination Breaks
Five Failure Points That Rarely Show Up Until an Islanding Event
Each of these can sit invisible during steady-state, grid-connected operation, and every one of them has a track record of surfacing at exactly the wrong moment during a real transition.
Improper Load Sharing
Droop gains tuned for one DER capacity mix can leave inverters unevenly loaded when actual renewable output or battery capacity shifts from what was assumed at commissioning.
Undersized Reserve Margin
Battery state of charge that looks adequate on a summer afternoon can leave a real gap during a winter morning islanding event when solar output and reserve margin are both lower.
Generator Start Failure on Demand
A backup generator that hasn't actually cycled in months can fail to start exactly when the microgrid controller calls for it to cover a depleting battery reserve.
Voltage and Frequency Deviation
Insufficient DER capacity reserved for voltage and frequency regulation during the islanding transition can push the whole microgrid outside stable operating limits.
Failed Resynchronization
Reconnecting to the utility grid out of phase or at mismatched voltage can trip protection and stall the transition back to grid-connected mode, extending an outage that should have already ended.
Dispatch Reference
Common Portfolio Signals and What They Point To
These are the recurring patterns operations teams see across mixed DER portfolios, along with what each one usually means once it gets investigated.
| Signal |
Likely Cause |
Typical Response |
| Battery Depleting Faster Than Modeled |
Actual load profile or renewable output diverging from the dispatch model's assumptions |
Recalibrate the dispatch model against recent operating data and adjust reserve targets |
| Generator Failing to Reach Rated Load |
Fuel system issue, control fault, or extended idle time since last full-load run |
Schedule a load bank test and inspect fuel and control systems before the next dispatch need |
| Frequent Curtailment of Renewable Output |
Interconnection limits or insufficient storage capacity to absorb excess generation |
Review interconnection agreement terms and evaluate storage capacity against curtailment frequency |
| Voltage Excursions During Transitions |
Droop control settings mismatched to current DER capacity mix |
Retune droop gains against updated capacity data and retest the islanding transition |
How the Platform Works
From Fragmented Vendor Data to One Coordinated View
Closing the coordination gap doesn't require replacing any existing vendor equipment. It requires pulling what each one already reports into a single, continuously updated picture.
1
Multi-Vendor Data Unification
Dispatch status, state of charge, generator readiness, and interconnection data are pulled continuously from each DER vendor's existing control platform into one shared view.
2
Reserve Margin Modeling
Battery reserve adequacy is modeled against actual seasonal load and renewable output patterns, not a single fixed assumption set at commissioning.
3
Generator Readiness Tracking
Standby generator run history, load testing cadence, and fault codes are tracked continuously, so start-on-demand reliability is a known quantity, not an assumption.
4
Coordinated Alerting
Operations directors get a single alert when reserve margin, generator readiness, or interconnection status drifts outside safe operating range, instead of separate alarms from separate vendor dashboards.
Readiness Check
Six Questions to Ask About Your Microgrid Coordination Today
Most of the assets in a distributed generation portfolio are individually healthy. The risk almost always lives in the coordination layer between them, which these six questions are built to surface.
1Do you know your current battery reserve margin under worst-case seasonal load and renewable output, not just average conditions
2Has every standby generator in the portfolio been load tested to full rated output within the last quarter
3Are droop control settings current against your actual DER capacity mix, or still set from commissioning
4Would a resynchronization failure surface as a specific, actionable alert rather than a general islanding alarm
5Can you see dispatch, state of charge, and generator readiness from every vendor's platform in one place
6Has your team run a full islanding and resynchronization test in the last six months, not just simulated it on paper
From the Field
What a Facility Learned From an Islanding Event That Almost Went Wrong
Our microgrid had passed every commissioning test with room to spare, so when we actually lost utility power during a storm, we expected a clean transition. What we got instead was a battery reserve that drained faster than our model predicted, because the load profile that day skewed heavier than the seasonal average we had built the reserve target around, and our backup generator took longer to reach full load than its spec sheet suggested since it hadn't run a true full-load test in almost a year. We rode it out, but with less margin than anyone was comfortable with afterward. Once we had reserve margin modeled against actual seasonal data instead of a single commissioning assumption, and generator readiness tracked continuously instead of checked quarterly, our next islanding event during a planned interconnection maintenance window went exactly the way the original test predicted it should.
— Operations Director, Commercial Campus Microgrid
Conclusion
A Microgrid Is Only as Reliable as Its Weakest Coordination Link
Every individual asset in a distributed generation portfolio can be perfectly healthy and the system can still fail during the moment that actually matters, the transition into and out of islanded operation, because that transition depends on coordination between assets rather than the condition of any single one.
iFactory's AI-powered platform unifies dispatch, reserve margin, generator readiness, and interconnection status across every vendor in your portfolio continuously, so an operations director can see the coordination gap before an actual grid event exposes it. That continuous view also removes the guesswork of comparing readiness data formatted differently by each vendor's own platform, since everything is normalized into one consistent view regardless of which manufacturer's equipment is reporting it.
That unified view scales whether the portfolio spans a single commercial campus or multiple sites across a distributed footprint, keeping reserve margin and generator readiness visible from one place instead of reconstructed from separate vendor logins during an event when time to make a decision is already short. Book a demo to see it configured for your DER mix.
Frequently Asked Questions
Distributed Generation and Microgrid Management — What Operations Directors Ask
Why does a microgrid that passes commissioning tests still fail during a real islanding event?
Commissioning tests are typically run under a specific, favorable set of conditions, and a microgrid's actual performance during islanding depends heavily on the load profile and renewable output at the moment the grid connection is lost, which can differ substantially from the commissioning scenario. A battery reserve margin calculated against average seasonal conditions can look completely adequate on paper while still leaving a real gap during a higher-load, lower-generation day, and that gap only becomes visible when it is modeled continuously against actual operating patterns rather than checked once at commissioning. This is compounded by the fact that most sites experience their highest load and lowest renewable output during roughly the same seasonal window, so the worst-case scenario for reserve adequacy tends to cluster rather than spread evenly across the year.
Book a demo to see reserve margin modeled against your site's real seasonal data.
How often should standby generators actually be load tested?
A generator that only runs briefly at low load during routine exercise cycles can still fail to reach full rated output when a real dispatch event demands it, since issues like fuel system degradation, cooling system limitations, and control faults often only surface under sustained full-load operation. Most reliability-focused programs test to full rated load on a quarterly basis at minimum, and tracking that test cadence continuously rather than relying on a maintenance log entry is what actually confirms a generator's start-on-demand reliability when the microgrid controller calls for it. A generator that passed its last load test six months ago provides very little confidence about its readiness today, particularly for units that sit idle for long stretches between dispatch events.
Can this coordinate DER assets from different vendors on different control platforms?
Yes. Most distributed generation portfolios are assembled over several years from different vendors for solar, storage, and generation assets, each running its own proprietary control platform, and this fragmentation is exactly the gap the platform is built to close by pulling dispatch, state of charge, and readiness data from each vendor system into one unified operational view. This matters because the coordination problems that cause islanding failures happen between assets, not within any single vendor's equipment, so a unified view is necessary to actually see them coming. A solar inverter, a battery management system, and a generator controller can each report perfectly healthy status individually while the combination of their settings still produces an unstable transition, and that combination effect is invisible from any single vendor's dashboard.
Contact support to discuss your specific vendor mix.
Does this replace the need to physically test islanding and resynchronization?
No. Physical islanding tests remain the only way to confirm that protection settings, droop control tuning, and resynchronization logic actually behave as expected under real conditions, and no amount of continuous monitoring replaces that periodic validation. What continuous monitoring changes is how much confidence a team has going into that test, since reserve margin and generator readiness data collected beforehand tells you what to expect rather than leaving the physical test as the first real indication of whether the system will perform. Most operations teams find their test results become more predictable, not less necessary, once the underlying data is trusted, and a physical test that confirms what the data already suggested is a far more useful validation than one that surfaces a surprise the team had no warning about.
What data does a distributed generation portfolio need before this kind of coordination monitoring can start?
Most DER assets, including solar inverters, battery management systems, generator controllers, and microgrid controllers, already expose dispatch, state of charge, and status data through their existing vendor platforms as part of standard commissioning. In most cases, the platform connects to that existing vendor data rather than requiring new hardware to be installed on each asset, which means a typical portfolio can begin generating a unified operational view within the early weeks of connection. Sites adding new DER assets to an existing portfolio can bring the new vendor's data into the same unified view without disrupting monitoring on the assets already connected.
See Your Entire DER Portfolio as One Coordinated System.
Continuous dispatch, reserve margin, generator readiness, and interconnection monitoring across every vendor in your distributed generation portfolio.
