YarifyStart a conversation

Give farmers a governed door into their own telemetry

Modern tractors and implements already stream location, operating hours, fuel use and field-pass data over ISOBUS into the OEM's cloud. The Data Act turns the long-running right-to-repair argument over that closed telemetry into a binding EU access right — one a farmer or their chosen repair partner can actually exercise against a working API.

The farmer's right is live now

The Data Act has applied generally since 12 September 2025. The forward-looking Article 3(1) by-design duty reaches equipment placed on the market after 12 September 2026, broadly overlapping the Machinery Regulation's 20 January 2027 application date for machinery covering many tractors and implements.

RequirementStatus on review dateWhat it means on the farm
Farmer access-on-requestBinding since 12 September 2025Provide a request path for location, hours, fuel and field-pass data the machine already logs
Farmer-directed third-party sharingBinding since 12 September 2025Let a farmer route their own equipment data to an independent repairer or farm-management provider
Pre-contract data transparencyBinding since 12 September 2025Disclose what a new tractor or implement records and how it can be exported, before sale or lease
Accessible by-design architectureApplies to equipment placed after 12 September 2026New telemetry platforms should ship the access API rather than retrofit it after a complaint

ISOBUS already moves the data. The access layer decides who sees it.

Most tractors and implements already exchange telemetry over ISOBUS (ISO 11783) with AEF-certified compatibility between different manufacturers' equipment. That wiring doesn't change. What's missing today is a governed layer between the OEM's cloud and the farmer that turns "we have the data" into "here is your data, on request, with an audit trail."

Today: a closed loop

Product

Tractor / implement

Backend

Machinery OEM telemetry cloud

  • GPS & field boundaries
  • Operating hours
  • Fuel/energy use
  • Implement telemetry (rate, depth)

Only exit

Manufacturer's own app

  • No user-facing export or API
  • No route for the user to authorize a third party
  • No permissions model, so every request is a one-off exception
  • No audit trail if a user or regulator asks what was shared

With a Data Act access layer

Product

Tractor / implement

Backend

Machinery OEM telemetry cloud

  • GPS & field boundaries
  • Operating hours
  • Fuel/energy use
  • Implement telemetry (rate, depth)

New layer

Data Act access layer

  • Field catalog
  • User & device entitlements
  • Consent & grant registry

Customer export & portal

CSV/JSON, self-service, same quality as the manufacturer sees

Third-party API (OAuth)

Purpose-bound grant to a repairer, analytics or energy provider

Audit & compliance log

Request, decision, recipient and delivery evidence for review

Field groupTypical sourceDelivery format
GPS & field boundariesGuidance receiver / ISOBUS task controllerTrack export, GeoJSON or CSV per field pass
Operating hoursEngine control unit hour meterTime-series export aligned to service intervals
Fuel & energy consumptionCAN bus fuel-rate telemetryInterval export per operation or per field
Implement telemetry (rate, depth)ISOBUS task controller (seeder, sprayer, planter)Structured per-pass export with implement ID
Field-operation / yield recordsCombine yield monitor or task controller logGeoreferenced export tied to field and pass

Usually in scope

  • Location and field boundaries traversed during an operation
  • Operating hours, engine and drivetrain runtime
  • Fuel and energy consumption per operation
  • Implement telemetry: seed rate, application rate, working depth
  • Field-operation records including yield tied to a specific pass

Usually outside Chapter II

  • Proprietary yield-optimization or seed-placement recommendation models
  • Cross-farm aggregate benchmarking analytics the OEM runs internally
  • Guidance-system control firmware and calibration algorithms
  • Data the telemetry gateway never captured or cannot retrieve without disproportionate effort

What we implement, concretely

A farmer-facing telemetry API, an export path, a third-party sharing flow and an audit ledger — built on top of your existing ISOBUS gateway and telemetry cloud.

CapabilityWhat it does
Location & field-operation APIAuthenticated access to GPS tracks, field boundaries and per-pass operation records
Operating-hours & fuel exportScheduled or on-demand export sized for farm-management software ingestion
Implement telemetry feedStructured seed/application-rate and depth data linked to implement ID and field pass
Third-party sharing & OAuth grantsPurpose-bound, revocable access for an independent repair shop or farm-management provider
Entitlement & audit layerOwnership/lease/dealer-aware access control with a reviewable decision log

Trace the ISOBUS pipeline

Map every field from task controller through gateway, historian and analytics, and classify raw vs. derived.

Model entitlements

Connect equipment identity to ownership, lease and dealer-financing records, including end-of-lease handoff.

Design the farmer API

Define catalog, request, third-party grant and delivery endpoints separate from your internal fleet-management APIs.

Build the decision engine

Turn catalog, entitlement, trade-secret and privacy checks into explainable allow, partial and refuse outcomes.

Ship export and streaming

Deliver a historical export and, where useful, in-season streaming with stable schemas.

Test the edge cases

Run through mixed-manufacturer implements, dealer-financed transfers and disputed optimization-model fields.

Agricultural equipment Data Act FAQ

Is this the legal version of the right-to-repair fight over tractor telemetry?

It's the closest thing to it that EU law currently offers. Farmers and independent repairers have argued for years that closed telemetry locks them into the OEM's own dealer network. The Data Act doesn't rewrite repair law, but since 12 September 2025 it gives the operator a binding right to the operational data the machine already generates, and a right to route that data to whichever repairer or service they choose — the practical effect right-to-repair advocacy has been asking for, delivered through a data-access mechanism rather than a repair-parts mandate.

Is an independent repair shop an eligible third-party recipient?

Yes, in general. Article 5 lets the user direct their data to a third party of their choosing for purposes agreed with the user, and an independent repair shop is a normal example of that. The one carve-out is that a Digital Markets Act gatekeeper cannot receive data through this route — which is not a concern for a local repair business, but is relevant if the requested recipient turns out to be part of a large platform group.

Can the OEM withhold yield or precision-ag data as a trade secret?

Only for the specific fields that genuinely qualify, and only through the Act's structured process — proposing proportionate confidentiality measures, documenting the decision, and notifying the competent authority where required. Raw yield-per-pass and application-rate records tied to a field operation are operational data, not automatically the OEM's proprietary optimization model; the model that turns that data into a planting recommendation is a much stronger trade-secret candidate than the underlying readings.

How does entitlement work on leased or dealer-financed equipment?

The Data Act's user definition covers renters and lessees for the duration of their agreement, not just the registered owner. A leased tractor's access rights should follow the lease term, with a clear handoff back to the dealer or leasing company at end of term rather than access silently persisting with a former lessee or disappearing before the lease is up.

Who is the data holder when the tractor and the implement have different manufacturers?

Whoever actually receives and can lawfully make the combined telemetry available is the practical data holder for that flow, and this needs resolving contractually before a request arrives — not during one. A common pattern is the tractor OEM's telemetry gateway ingesting implement data over ISOBUS and becoming the de facto data holder for the combined dataset, which should be reflected in the implement manufacturer's own pre-contract disclosures.

Does this replace ISOBUS or the AEF certification program?

No. ISOBUS (ISO 11783) and AEF certification are the wiring: the standard that lets a tractor and an implement from different manufacturers exchange data on the same bus. The Data Act access layer sits a level above that — it decides which of the data already flowing over ISOBUS the farmer and their chosen third party get to see outside the cab, and under what entitlement and audit controls.

Send us your fleet's telemetry setup.

Tell us your equipment lineup, current ISOBUS/telemetry gateway, what you already log, and who's asking for access — a farmer, an independent repairer, or a dealer. We'll scope a pilot that proves one field-level access decision end to end.