Define the purpose before choosing the machine
Write the task in terms of an outcome that a person can review. “Capture usable observations across the flagged area and its comparison strip” gives the planner a purpose. “Visit waypoint seven” describes movement but says little about why that movement matters or whether the inspection succeeded.
Attach a task identifier and version. Record the source observation and the person or role that authorized the work. If a boundary changes, issue a clear revision rather than editing a live instruction invisibly. A machine returning after a communications gap must be able to distinguish its accepted plan from a newer proposal.
Make the operating envelope explicit
Specify the permitted area, access route, exclusions and conditions that invalidate the task. These may include unsuitable ground, visibility limits, unavailable supervision or an unresolved positioning problem. Values must come from the machine documentation and the farm’s assessed procedure, not from a general website or a planner’s convenient default.
The envelope includes the implement and payload, not merely the vehicle footprint. A camera mast, trailing implement or turning maneuver may require space beyond the route centreline. Check access at gates and headlands before dispatch. A task can be correctly located yet physically unsuitable for the available machine.
The handoff ladder
- Evidence accepted: retain its source and limitations.
- Purpose agreed: inspect, defer or refer for advice.
- Resources checked: machine, sensor, energy and supervisor.
- Plan authorized: boundary, route and exception rules.
- Completion reviewed: evidence returned, not just distance covered.
Assign by capability, not availability alone
The nearest idle machine may lack the required sensor, ground clearance or approved operating mode. Match the task against declared capabilities and current state. Include sensor readiness, energy margin, positioning availability and maintenance status. A resource should not be considered ready merely because it appears online.
Consider the opportunity cost of movement. Repeated short dispatches may consume headland capacity or interrupt another operation. Combining observations can be sensible, but only if the resulting task remains timely and its evidence remains interpretable. Batching should not make an urgent inspection wait behind convenient but unrelated work.
Interoperability needs a checked agreement
ISO 11783, commonly associated with ISOBUS, addresses agricultural machinery communications. It does not mean that any two products can exchange every task, control function or fleet instruction. The Agricultural Industry Electronics Foundation provides resources on supported functionalities and compatibility; check the specific combination rather than relying on a general label.
ISOXML task data and AgGateway’s ADAPT ecosystem are useful reference points for data exchange. In practice, confirm field identifiers, units, coordinate systems, boundary interpretation and acknowledgment behavior. A successful import is only one test. The recipient must interpret the data as intended and report which version it accepted.
| Agreement | What it establishes | What it does not establish |
|---|---|---|
| Data exchange | Records can be transferred and interpreted | Permission to move or treat |
| Task authorization | A defined job is approved within limits | That every future condition is acceptable |
| Machine readiness | The system reports required capabilities available | That the field will remain unchanged |
Build acceptance into the task
Define what evidence must return: coverage, timestamps, quality flags, interruptions and any unobserved area. The machine might traverse the whole route while producing unusable imagery. Conversely, it might gather enough useful evidence before a blocked section prevents full coverage. These outcomes need different completion states.
Keep “completed,” “partially completed,” “cancelled” and “requires review” distinct. A cancelled task should not be automatically recreated without checking why it was cancelled. When tasks are split between machines, the planner must preserve the relationship between parts so gaps and duplicate work remain visible.
Prepare the handoff to movement
The final task packet should contain a bounded purpose, an accepted plan version, an assigned capable resource and an accountable supervisor. It should also state how the machine requests entry to shared areas and how the task is suspended. This is the bridge from a useful observation to coordinated field work.
Exception note: a newer observation contradicts the task
Flag the conflict and use the approved process to pause or revise the task. Do not overwrite evidence or assume that a machine has received an update until its acknowledgment is checked.
Next: coordinate the working fleet
Reference points: International Organization for Standardization, Agricultural Industry Electronics Foundation and AgGateway. Consult applicable editions and product documentation for implementation details.