Notes from the field, not a newsletter.
Written by whoever on the team had something worth documenting, usually right after a fire season turned up something worth remembering.
A Red Flag Warning covers a huge area. Fire risk doesn't respect its boundary evenly.
The National Weather Service issues Red Flag Warnings at a regional scale, and appropriately so — that's the right tool for regional public awareness. But treating a single regional warning as uniform risk across an entire utility service territory is exactly the assumption dense station networks exist to correct.
Wind gusts, not sustained wind speed, are usually what actually matters.
A circuit can sit at a calm sustained wind speed and still see the gusts that bring a branch into a line. Station networks that only report sustained averages miss the specific measurement most predictive of an ignition event, which is part of why raw station count matters less than what each station actually measures.
The stations most likely to fail are the ones in the areas that need them most.
Remote, high-risk terrain is hard on hardware — the same wind, heat, and isolation that make an area fire-prone also make it hard on sensors and communications equipment. We schedule maintenance around risk level, not just distance from a service depot, because the correlation between "hard to reach" and "important to keep online" is not a coincidence.
Operator trust in a new network builds slower than the network itself gets built.
Deploying stations and integrating a console can happen in months. Getting a control room team to genuinely trust circuit-level data over the regional judgment calls they've relied on for years takes at least a full fire season of shadow-mode comparison, and we've never seen that trust build faster by skipping the comparison period.
Wondering how dense your own service territory's weather coverage actually is? Get in touch — that's usually how the first conversation starts.