Twin
A field you can query
Per-plant locations and history in an Omniverse-based twin.
Measure · Acreon
Acreon aggregates Folira's detections and Targis's actions into a twin of each field, plant by plant, and keeps the outcome ledger: what was done to which plant, and what happened next.
ExampleCounts are illustrative, for one example pass.
Capabilities
Twin
Per-plant locations and history in an Omniverse-based twin.
Ledger
Each action linked to its result on the follow-up pass.
Planning
Weed pressure and stress maps for the next pass and for Agrona.
Records
As-applied maps and per-field summaries for your own records (planned).
API
Read access for farm management systems and equipment makers.
Analytics
RAPIDS analytics over millions of plants and passes.
How it works
1
Edge units sync detections and actions.
2
Every record lands on its plant in the twin.
3
The next pass adds the outcome.
4
Exports and API serve your other systems.
Specification
| Item | Planned |
|---|---|
| Granularity | Per plant, per pass |
| History | All seasons you keep |
| Exports | GeoJSON, Shapefile, ISO-XML (planned) |
| API | REST, read-only first (planned) |
| Twin format | OpenUSD |
| Retention | Set by the grower |
Status
Nothing on this page is shipping today. Items marked planned are on the draft roadmap.
Place in the loop
Acreon is the measure step and the memory of the loop. Its outcome labels tell Synora what data is missing and give Agrona the ground truth to plan from.
Questions
An agronomist or an engineer reads every message, not a sales queue.
The grower. Service providers and equipment makers see only what the grower shares.
Yes. Folira detections alone already build the twin; outcomes then come from scouting passes.
No. It feeds it, through exports and the API.
Next step
Send us one pass. We run it through Cropite and send back a per-plant report, labelled as an early example.