A microgrid controller that has never been tested under load doesn't know it's broken until the grid goes down and it needs to island. By then it's too late — the hospital, the data centre, or the industrial campus it was supposed to protect finds out the hard way. Microgrid and DER O&M is different from conventional plant maintenance because the assets aren't in one building — solar PV, BESS, diesel gensets, and EV chargers are scattered across a site, each on its own service contract, each ageing at its own rate. Sign up to bring every DER asset, islanding test record, and IEEE 1547 compliance log into one CMMS.
Why It Matters
A microgrid's whole value proposition is that it can carry critical load when the utility grid can't. That only works if the controller firmware is current, the transfer switch has been exercised under real load, and the battery's state-of-charge estimator hasn't drifted. None of that shows up on a walk-through inspection — it only shows up during an islanding event, which is exactly the wrong moment to discover a gap. O&M programs for microgrids exist to close that gap before the grid ever forces the question.
Three Pillars Of A Microgrid O&M Program
A microgrid isn't one asset — it's a coordinated system of controller, storage, and generation that all have to work together the moment the grid drops. A working O&M program has to cover all three at once.
Controller & Islanding
Firmware currency, transfer switch testing under load, and scheduled islanding drills that prove the microgrid actually does what it's designed to do.
IEEE 1547 Compliance
Documented interconnection performance testing at defined intervals, so the site can prove ride-through and protection settings still meet the standard.
Distributed Asset O&M
Solar PV, BESS, gensets, and fuel cells each on their own service cadence, tracked as one fleet instead of separate vendor silos.
Controller readiness confirms the microgrid can switch modes, IEEE 1547 testing proves the interconnection is still compliant, and distributed asset O&M keeps every individual DER healthy enough to contribute when the controller calls on it.
The Microgrid O&M Layer Stack
| Layer |
What It Covers |
Typical Task |
| Controller |
The logic that decides when and how the microgrid islands |
Firmware updates and transfer switch load testing on schedule |
| Storage (BESS) |
The buffer that keeps critical load powered during transition |
State-of-health checks and state-of-charge estimator calibration |
| Generation Fleet |
Solar PV, gensets, and fuel cells that supply islanded load |
Preventive maintenance against each OEM's own service interval |
| Interconnection |
The legal and technical link back to the utility grid |
IEEE 1547 ride-through and protection testing at defined intervals |
One Fleet, Not Five Vendor Silos
Oxmaint tracks solar PM contractors, BESS OEM service agreements, and internal genset maintenance against one auto-generated schedule, so nothing falls through the gap between them. Sign up for a free trial to run it on your own DER fleet, or book a demo to see it configured for your microgrid.
Where Microgrid O&M Programs Break Down
Islanding Never Tested
Transfer switch works on paper but has never been exercised under real, full-site load
Controller Firmware Stale
A vendor patch sits unapplied for months because no one owns the update task
BESS SOH Drift Missed
A battery's real capacity quietly falls below what its rating sheet promises
Vendor Contracts Siloed
Solar, BESS, and genset service records held by three different contractors
IEEE 1547 Records Missing
Interconnection test dates that can't be produced when the utility asks for them
VPP Dispatch At Risk
One degraded site can cause an aggregated fleet to miss a grid services obligation
Frequently Asked Questions
Q
Why is microgrid O&M different from ordinary power plant maintenance?
A conventional plant maintains one physical asset in one location. A microgrid maintains a heterogeneous, physically distributed fleet — solar, BESS, gensets, fuel cells — that has to switch between grid-connected and islanded operation and still perform as one unit.
Q
What does IEEE 1547 actually require from an O&M standpoint?
It requires tested, documented interconnection performance at defined intervals — proof that ride-through behaviour and protection settings still match what was certified at commissioning, not just a one-time approval.
Q
Why does a Virtual Power Plant raise the stakes for DER O&M?
When multiple sites are aggregated into a VPP, each asset has to be individually reliable for the aggregate to deliver its contracted dispatch. One BESS site down for emergency repair can cause the whole VPP to miss a grid services obligation.
Prove Every DER Was Ready Before The Grid Went Down
Oxmaint keeps controller firmware status, islanding test dates, BESS state-of-health, and IEEE 1547 compliance records tied to their evidence in one auditable log, so proving your microgrid was ready doesn't mean chasing five vendors. Sign up for a free trial to run it on your own sites, or book a demo to see it configured for your fleet.
.png)
