Terminal service
The terminal provides the shared display and input environment used by compatible implement functions.
ISO 11783 OPERATOR CONTROL / PART 06
Virtual
terminal
Part 6 defines a common approach for an implement to present its operator interface through a compatible terminal, so the display is not limited to one permanent tractor-implement pairing.
01 / Identity & role
One compatible display,
many implement interfaces.
ISO 11783-6:2018 is titled Virtual terminal. The referenced publication is the fourth edition, issued in 2018.
Its role is to provide a shared operator-interface framework between an implement and a compatible terminal. The implement supplies its intended interaction model; the terminal presents it to the operator.
02 / The problem it solves
A new implement should not
always require a new display.
Agricultural operations can combine tractors, implements, and displays from different product families. A proprietary display for every implement increases cab clutter, training cost, integration effort, and the chance that an operator faces inconsistent controls.
Part 6 establishes a shared interface model. It makes it possible for a compatible implement to bring its controls and status views to a compatible terminal while preserving the implement maker's operational intent.
03 / Position in the stack
The virtual terminal sits
where people meet machine functions.
Part 6 is an application-level service. It depends on the communication foundation below it and turns implement information and commands into operator-visible controls.
Operator interface · Part 6A compatible terminal presents an implement-defined working interface
Machine application functionsImplement and tractor control functions provide the behaviors the operator uses
Network participation · Parts 3-5Control functions are reachable and communicate on the machine network
Physical connection · Part 2The shared medium connects terminal and implement
04 / Key concepts
Separate the interface
from the glass in the cab.
Working set
An implement supplies a structured description of the interface it expects the terminal to present.
Operator interaction
Keys, touch input, controls, feedback, and state changes must retain their intended meaning across the terminal-implement boundary.
Lifecycle
Startup, connection, updates, loss of communication, and recovery affect what an operator sees and can safely command.
Human factors
A technically compatible interface can still be difficult to use if layout, localization, alerts, or control behavior are poorly designed.
05 / Who implements it
Two teams share
one operator experience.
RoleDirect responsibilityDesign question
Tractor OEMIntegrate or supply a compatible terminal environmentWhich implement interface generations and functions are supported in this tractor?
Implement makerCreate the working interface and connect it to implement behaviorWill the interface remain clear and safe on supported terminal variants?
Terminal developerRender and operate working interfaces predictablyHow are presentation, input, warnings, lifecycle, and backwards compatibility handled?
FMIS developerUsually does not render the in-cab working setWhich machine tasks or records depend on a successful terminal interaction?
06 / Interactions
The terminal is a bridge
between intent and action.
This is an original learning flow; it is not a copy of any standard interface diagram.
JOIN / P03-P05Control functions participateTerminal and implement become reachable on the network
DESCRIBE / P06Implement interfaceA working set conveys the intended operator interaction
OPERATE / P06Terminal interactionThe operator sees state and provides commands
CONTROL / P07-P10Machine responseImplement, tractor, and task services act on the resulting intent
07 / Boundaries
A shared screen does not
guarantee a shared experience.
This page is not ISO 11783-6.Use the licensed official publication for object definitions, lifecycle behavior, version requirements, layouts, input semantics, and conformance work.
No interface objects are reproduced.FieldCircuit omits protected object lists, attribute tables, event definitions, data formats, examples, figures, and normative procedures.
ISOBUS labels are function-specific.A terminal and an implement can each support ISOBUS while their exact virtual-terminal functions, versions, licenses, or behaviors still differ.
Operator responsibility remains real.A virtual terminal does not replace safe machine setup, implement manuals, training, field awareness, or supervision.
08 / Evidence
Primary sources.
The official ISO catalog entry is the authoritative source for the publication identity and high-level scope. AEF public material provides industry context for the Universal Terminal function. Restricted interface content is not reproduced.
01
ISO 11783-6:2018 — Virtual terminalInternational Organization for Standardization · Accessed 2026-07-11