Questions and answers

The device keeps reading and sends when it reconnects, so the history fills back in rather than showing a hole. Loss of contact is itself an alarm condition. You find out that a site went quiet, which is usually the more useful signal.

Yes. Device health telemetry covers battery, cellular signal, Bluetooth link, ping, and device temperature, and it raises alarms on its own. Data-quality alarms cover the case where a device is online but the readings stopped making sense.

Yes, over Modbus. We map registers per device (VFDs, ESPs, pump-off controllers, PLCs, compressors, flow computers, and Lufkin well managers) with calibration held per device. You are not replacing what already works.

Always. There is a physical hand/off/auto switch on the controller, and it locks out remote control. Whatever the cloud wants, the switch in the field decides. Automation is also enabled per well, so you can run one lease on smart control and leave the rest on a timer.

Access runs Master Company to Company to Lease to Asset, with per-lease visibility and lease groups. Roles cover executives, field managers, pumpers, installers, and customer service, and permissions are enforced on every request rather than just hidden in the interface.

Readings stay queryable at full resolution and older data is archived for long-term history rather than discarded, so you can pull a card from years back when a well starts behaving the way it did then. [NEEDS SOURCE: the specific retention window we commit to contractually.]