Project fit & buying priorities
Machinery OEMs, guidance and automation integrators, agricultural software vendors and service organizations can assess the workflow, integration and ongoing support together. Operations should define tasks and exceptions, IT should validate interfaces and access, and procurement should compare complete configurations and service scope.
Distinguish produce barcodes, livestock tags and document reading. LF, HF and UHF protocols and tag forms are not interchangeable.
From field action to a complete record
- 01Create producer and lot IDs
- 02Capture harvest or dispatch records
- 03Link inspection and handover documents
- 04Record movements and investigate exceptions
System integration & delivery responsibilities
Use producer, lot, harvest event, tag, inspection document, handover record as the integration checklist. Define field ownership, required values and exception handling. Complete one representative job from terminal to API and backend review before scaling to more teams or sites.
SOTEN provides display terminals, interfaces and customization support. Machinery and solution partners own control algorithms, actuators, maps and agricultural workflows. The interface does not replace machinery control or safety systems.
Turn requirements into testable selection criteria
| Criterion | Confirm with the project team | Evidence to request |
|---|---|---|
| Use and configuration | Confirm capture methods, environment and operator interaction against the criteria above | Representative jobs, tags and peripheral list |
| Systems and interfaces | Machine control / job dispatch / farm management application version, fields, SDKs and protocols | Installable software, API specification and test account |
| Operations and support | Actual shifts, power, network, mounting and spare-unit plan | Full-shift test, installation drawing and support responsibilities |
Product platforms to evaluate
Select a platform by workflow, then confirm the branch, operating-system version and modules. The suggestions below do not mean every option is included in every configuration.
R36
Agricultural tag-protocol selectionRFID handheld family; confirm frequency, reader module and SDK for R36S, R36A or R36U.
View platform and configurations ↗
H61
Lot & handover scanningHandheld workflow candidate for mobile scanning roles that require frequent movement and one-handed interaction.
View platform and configurations ↗
H81
Field forms & capture optionsMultifunction tablet for business forms and capture options; select the system platform and module combination.
View platform and configurations ↗Pilot validation & procurement acceptance
Trace real lots and tags from production to handover, testing duplicate IDs, contaminated labels and offline entries.
- Operations: confirm completion, exception review and result retrieval against real workflows.
- IT / integration: verify fields, permissions, offline recovery and duplicate handling.
- Procurement / support: freeze the tested device, software and accessories, and agree delivery, spares and service terms.
Questions before the project starts
Can this connect to our existing system?
Machine control / job dispatch / farm management are integration targets, subject to application compatibility, interface access and SDK validation. Share the software version, API specification and an anonymized workflow sample for a device pilot. Agree device supply, integration and rollout as explicit work packages.
What should we prepare before selecting pilot devices?
Provide implements and controllers, communication protocols, positioning solution, map formats and real-field test conditions. Include deployment region, estimated quantity, project stage and intended rollout date to define candidate configurations and a test plan.
Traceability-data reference
For cross-stage traceability, software partners can use GS1 event and data-element concepts as a reference alongside project identifiers and interfaces.
