Monitoring and a settings audit catch the electrical drift. The other half of an O&M visit is the physical condition of an array that nobody walks across between visits, and on a real commercial roof a recognisable set of problems turns up again and again. The visit exists to find them while they are cheap, before they show up as lost generation on a bill or, worse, as a fire risk.
Soiling, and why a shallow-pitch or coastal roof needs more cleaning than a buyer expects. Cleaning is a larger part of a commercial O&M plan than most buyers assume, and the sites that need the most of it are the ones a buyer expects to need the least. A shallow-pitch array does not let rain sheet the dirt off the way a steeper domestic roof does, so soiling settles and stays, and output drifts gently down without ever flagging as a fault. A coastal site compounds it: salt in the air plus more airborne soiling means the glass dirties faster and rain clears less of it. We do not put a fixed cleaning frequency on a page, because the right interval is set by how your roof actually soils, read off the monitoring trend and confirmed at the visit, rather than off a generic calendar. Where soiling is the dominant loss on a site, the detail of how and how often we clean is covered in the commercial solar cleaning guide.
Bird fouling, dead birds and the shaded cells they leave behind. Droppings and dead birds sitting on the modules are a routine find on a commercial roof, and they are not only an aesthetic problem. A fouled patch of glass soils like any other soiling, but a concentrated droppings deposit, or a carcass, shades the cells beneath it, and a shaded cell in an otherwise generating string runs as a hot spot that, left long enough, can damage the module. The visit clears the fouling and inspects the cells underneath for the heat damage it may already have caused.
Shattered and cracked modules. Modules break. Impact from debris or a dropped tool, hail, thermal cycling over the seasons and the microcracks that propagate from it all leave a panel cracked or shattered, and a damaged module can keep generating while it quietly underperforms and lets water in at the failure. Identifying the affected panels and replacing them is part of putting the array back to its design output. This is also where independent monitoring and a periodic performance audit earn their place: a single failed or cracked module rarely announces itself, and the audit is how the underperformance gets traced back to the panel that caused it.