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.
Define the difference between navigation tracks, actual work status and billable area, including implement signals and field boundaries.
From field action to a complete record
- 01Bind machine and operator
- 02Dispatch fields and jobs
- 03Record position and work status
- 04Review worked area and settlement evidence
System integration & delivery responsibilities
Use machine, operator, field, assignment, work state, settlement evidence 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.
K70
Farm-machine guidance interfaceDisplay candidate for farm machinery and vehicles; validate with receivers, controllers and job software.
View platform and configurations ↗
K80
Machine & equipment displayVehicle and equipment display candidate; confirm configuration against mounting space and interfaces.
View platform and configurations ↗
T71
Mobile dispatch & job confirmationMobile and vehicle-workflow platform; evaluate location, capture and specialist application branches.
View platform and configurations ↗Pilot validation & procurement acceptance
Compare job completion, overlapping tracks, offline upload and operator corrections across fields and machine types.
- 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.
