Connectivity & automation
Connect the belt scales, PLCs, tank sensors, and weather feeds you already run. STRATA turns their readings into audited records — and automated data supersedes a manual entry only with a visible variance flag.
The reading pipeline
Nothing posts silently. A reading earns its way onto the record.
Feed-belt scales feed the yield engine, so configured-vs-actual yield is measured, not estimated. Calibration records — zero and span tests, tolerance, certification — travel with the numbers, and every yield figure carries a calibration-state flag.
PLC tags from bagger lines and feed belts — counts, weights, run state — arrive on a defined adapter contract. PLC data supersedes manual entry with an audit trail and a variance flag, so the automated number and the human number are always reconcilable.
Monitored bulk tanks report level, percent, timestamp, and quality on an adapter contract with a staleness threshold. STRATA shows a live level bar with the reading source and freshness — and falls back to a manual dip, also source-tagged, when a feed goes stale.
A dedicated weather and lightning data service feeds the per-site radar and the policy engine that suspends outdoor work. The integration runs on a defined data contract — and a feed-down fail-safe falls back to a conservative manual stop rather than assuming clear skies.
The integration fabric
Idempotency keys and retry on every outbound write — a record is never lost or duplicated by a dropped connection.
Failed exchanges land in a visible queue where a person can correct and resend — never swallowed.
Connection credentials rotate on a procedure, not a memory — with expiry visible per connection.
Per-connection mapping configuration for exports — your codes on their side, our record on ours.
Integration categories
Categories, not product names — the devices are yours; the record is the point. Programmatic access lives on the Developers page.
Every automated reading is attributed to its source and can be reversed by a person.
An automated value supersedes a human entry only with an audit entry and a variance flag.
Stale feeds, invalid readings, and failed writes land in someone's queue — never in the dark.