Field notes

Useful things learned the expensive way.

Candid notes about sensor deployments, customer-owned data, architecture, hardware, and the gap between a successful demo and a healthy operation.

Publishing queue

The first notes are being prepared.

These are real topics, not AI-authored customer stories. Full articles will be published as they are written and reviewed.

Data architecture

What one-minute data changes

A practical look at volume, retention, rollups, alert windows, and why “only a few thousand sensors” can be a misleading sizing statement.

Draft planned

Network resilience

A gateway should expect the WAN to fail

Store-and-forward, replay, idempotency, and the operational signals needed to turn a connectivity gap into a recoverable event.

Draft planned

Customer ownership

Own the data path, not only an export button

The difference between receiving periodic exports and controlling the environment where operational history is stored and governed.

Draft planned

Field validation

A packet arrived. Is the measurement true?

Why identity, wiring, scaling, units, timestamps, topology, and commissioning evidence matter after connectivity is proven.

Draft planned

Cloud economics

Compare architectures, not cloud logos

How managed services, egress, redundancy, support, operations, and staff time change an apparently simple monthly comparison.

Draft planned

Fit decisions

When not to build a platform

Cases where an existing tool, a focused integration, or a better operating process may be more useful than new software.

Draft planned

Start here

Have a hard deployment question?

It may become a useful field note—with your identity and sensitive details kept out of it.

Start a conversation