Many modern machines are capable of interpreting digital instructions from a file adhering to the ISO 11783 communication protocol. This protocol is often called the ISOBUS protocol.
The most important reason to export tasks to ISOBUS is to automate the operation of machinery. The machine receiving the ISOBUS instructions will no longer rely on its operator to perform many actions. If a spraying machine receives instructions to spray specific values, on specific parts of specific fields the operator of the machine only has to drive the spraying machine over the fields it needs to spray. If taken one step further, the vehicle pulling the spraying machine could receive instructions containing the exact locations of the field and navigate over the field by itself. The 'driver' could oversee the actions from within the vehicle without having to actually do anything.
If a task can be exported to ISOBUS it will have the action to do so in the context menu of its node. Furthermore the window displaying the task properties will contain an export button. Starting the export action will open a file picker window that will ask you where the generated task data should be stored. Keep in mind that the exported task data will need to be imported by the machinery it contains instructions for. This can often be achieved by exporting the task data to a portable storage device.
Machines that support the ISOBUS protocol are not only capable of reading instructions but also producing statistics. These statistics are related to actions performed in the past and may include performance, maintenance and historical data. Import tasks