Sense
Works when the link is up, and when it is down
Mesa is the software a Field Agent runs: a set of components on the box at the site. It reads the equipment, keeps its own history, runs inference locally, and reconciles with the cloud when the connection comes back. A satellite outage should cost you latency, not data.
The part most platforms skip
Anything can forward MQTT while the network is good. What matters is the hour it is not.
A real historian on the Field Agent
A local time-series database subscribes to every producer on the box and stores what they publish. It is not a ring buffer sized to a guess. It is a database with retention and compression, on disk, at the site.
Replay on reconnect
When the link returns, the rows the cloud missed are replayed rather than dropped. The gap closes by itself, and nobody has to work out afterwards which hours are missing.
Inference where the data is
Vision models run on the Field Agent's accelerator against local camera streams, with per-camera zones and rules. Video does not have to leave the site for a detection to be useful, which matters for both bandwidth and for what you are allowed to send.
The asset model, pushed down
Sensor definitions and parent-child links are synchronised from the cloud into a local store, so the Field Agent knows what it is looking at even while it is offline and can label readings correctly on its own.
What it speaks
Each has a deployed component behind it. The list is short on purpose. We would rather name eight things that work than thirty that might.
If your plant runs something that is not on this list, that is a real answer rather than a soft one. Ask us and we will tell you whether it is a week of work or a no.
Cameras and video
Discovery, control and events
ONVIF discovery, pan-tilt-zoom control including vendor quirks that standard implementations get wrong, and event subscription, against cameras you already own rather than cameras you have to buy from us.
Recording that keeps the run-up
Event-triggered recording with preroll, scheduled stills, and streaming to cloud video storage when you want a clip to outlive the Field Agent.
What the vision models look for
People
Personnel counting, restricted-area monitoring and safety-zone intrusion, on camera streams you already own. Detection runs on the Field Agent, so what leaves the site is an event rather than the footage.
Vehicles
Classification and entry-exit patterns across gates and perimeters, with number-plate reading where the camera angle supports it. Plates that are not read confidently go to a review queue rather than being guessed at.
Faces, if you want them
Face matching for access control, with the face database held on the device. No biometric data leaves the Field Agent. This one is off unless you ask for it. It carries obligations in most of the jurisdictions our customers operate in.
Per-camera zones and rules
Each camera carries its own zones, its own detection policy and its own model override, because a loading bay and a perimeter fence are not the same problem.
Fleet operations
Updates as jobs, verified
Firmware and component updates are dispatched as jobs against a device cohort, downloaded through a time-limited link and checked against a hash before anything is written. A failed download is a failed job, not a bricked box.
Health you can see from the office
System, power, storage and bus health published on a schedule, plus a local diagnostics page on the Field Agent itself for whoever is standing in front of it with a laptop.
Being precise about the hardware
Current production Field Agents are the R2200 and R2245. A Raspberry Pi CM5 with a Hailo-8 accelerator. NVIDIA Jetson boards are supported and still deployed in the field, but new installations go to the R2200.
Compiling vision models for the Hailo accelerator runs as a cloud pipeline today; running those compiled models on the device is still being brought up, and Jetson remains the path for inference workloads in the meantime. Components for Philips Hue, Delta Dore and Enphase exist in the tree but are not deployed. Treat them as lab work, not product.
Ask what happens during an outage
It is the question that separates edge software from a forwarder, and we are happy to walk through exactly what the Field Agent does for the hour the link is gone.