What makes a pump alert actionable?
Persistence, fault class, ownership and verified closure.
OpenField Notes
Short entry points into the operational decisions behind remote water and infrastructure monitoring.
The most useful monitoring lessons are often small but consequential: a missing packet should not become a pump-failure ticket; a groundwater trend needs a stable datum; a connectivity map does not prove installed coverage; a solar pump can be technically healthy while abstraction pressure increases; and a dashboard should preserve unknown states instead of painting every asset red or green. The notes below link directly to the detailed procedure or guide where the decision can be tested. They are written for teams that need an implementation rule, a diagnostic sequence or an acceptance criterion rather than a technology slogan.
Why groundwater frequency matters
Choose cadence from the process the network must resolve.
OpenConnectivity is an installed-site test
Map coverage is only the start of a field decision.
OpenSolar pumping needs source context
Separate energy performance from groundwater sustainability.
OpenUnknown is a valid monitoring state
Do not turn missing telemetry into false service certainty.
OpenCommission the failure path
Force outage/recovery and a safe alert test before handover.
OpenHow to use this section
Use these notes as entry points, then follow the linked procedure before making a field change. The detailed pages show the variables to record, the failure modes that can mimic the observed problem and the acceptance evidence needed after a configuration change. This makes the notes useful for triage without turning a short observation into an unsupported universal rule.