Shared semantics
A standardized reference lets systems distinguish the meaning of a value from the local screen label, database column, or vendor API name around it.
ISO 11783 DATA & TASKS / PART 11
Mobile data
element dictionary
Part 11 establishes a shared reference for the meaning of mobile-machine process data so compatible systems can exchange data with an agreed semantic interpretation instead of relying only on local labels.
01 / Identity & role
A shared name for data
is not merely a shared label.
ISO 11783-11:2011 is titled Mobile data element dictionary. The referenced publication is the second edition, issued in 2011.
Its role is to provide standardized identifiers for data elements used in task-control process-data communication. In plain language, it helps connected systems agree on what a reported or requested value represents.
02 / The problem it solves
Numbers travel easily;
meaning does not.
A field operation can produce many values. If one system calls a value by a private name and another system interprets it differently, a technically successful transfer can become an operational error.
Part 11 creates a shared semantic reference for task-control workflows. It reduces ambiguity between implement functions, terminals, and farm-management systems without requiring each pair of products to negotiate a new private vocabulary.
03 / Position in the stack
Part 11 gives task data
a common semantic anchor.
It supports application-level task control and process-data exchange. It does not carry data by itself, command an implement, or replace the farm's own data model.
Farm review and decisionsUsers interpret records, compare operations, and make management decisions
Shared data semantics · Part 11A common reference helps compatible systems interpret process-data meaning consistently
Task coordination · Part 10Task-controller workflows exchange and document operational information
Machine application and network layersConnected control functions generate, consume, and transfer information
04 / Key concepts
Meaning, governance, mapping,
and version-aware interpretation.
System mapping
Products still need to map their sensors, controls, records, and user concepts to the shared meaning they claim to support.
Managed vocabulary
A common dictionary requires controlled maintenance so users do not treat unrelated concepts as equivalent or equivalent concepts as unrelated.
Version awareness
Interoperability depends on the applicable edition, maintained resources, product implementation, and supported workflow rather than the existence of a dictionary alone.
Data quality remains separate
A correctly identified value can still be wrong because of calibration, configuration, timing, unit conversion, missing context, or sensor failure.
05 / Who implements it
The implement creates data;
the ecosystem preserves meaning.
RoleDirect responsibilityData stewardship question
Tractor OEMExpose compatible tractor-side data where supportedHow is meaning preserved when tractor information is reused by terminals and task workflows?
Implement makerAssociate product process data with the correct shared semanticsDoes each supported value retain its intended meaning across the full operation and record lifecycle?
Terminal developerPresent and record compatible data without semantic driftHow are labels, units, context, and unavailable values made clear to the operator?
FMIS developerImport, store, map, and export operational information responsiblyCan the system preserve provenance, units, version context, and user-visible interpretation across integrations?
06 / Interactions
Part 11 helps records retain
meaning beyond one machine pass.
This is an original semantic-flow diagram. It contains no data-element entries, identifiers, dictionary content, message structures, or task-file definitions.
OBSERVE / MACHINEMachine functionA tractor or implement function produces or uses operational information
INTERPRET / P11Shared semantic referenceCompatible systems align on what the information represents
COORDINATE / P10Task workflowTask control uses meaningful operational context during work
REVIEW / FMISFarm recordInformation can remain interpretable for later management use
07 / Boundaries
A dictionary concept page
must never become a dictionary copy.
This page is not ISO 11783-11.Use the licensed official publication and the applicable maintained resources for any data-element identifier, definition, assignment, process-data implementation, or conformance work.
No dictionary content is reproduced.FieldCircuit intentionally contains no data-element entries, identifiers, numbers, definitions, mappings, tables, export structures, examples, or normative procedures.
Shared semantics do not guarantee successful interchange.Actual interoperability still depends on task-controller support, product versions, unit handling, software mappings, licenses, field context, and user workflow.
Semantic identity is not measurement validity.A value can be correctly identified yet be inaccurate, incomplete, stale, or unsuitable for the management decision being made.
08 / Evidence
Primary sources.
The official ISO catalog entry is the authoritative source for the 2011 publication identity and high-level scope. This original explainer deliberately contains no dictionary entries, identifiers, data-element numbers, or protected task-control structures.
01
ISO 11783-11:2011 — Mobile data element dictionaryInternational Organization for Standardization · Accessed 2026-07-11