Skip to content
Service & spare partsAgricultural Machinery

ISOBUS: will the implement run on this tractor?

Dealers ask whether implement and tractor terminal work together. demi answers from field tests, software versions and service cases.

Today

Before a purchase and in the middle of the season, dealers and farmers ask the same thing: does the spreader run on this tractor's terminal, does section control work, can the joystick be assigned? The answer depends on the terminal, the software version of the implement's control unit and the equipment. It sits in test records, old tickets and with the one colleague in factory service who knows every combination. Until he calls back, the dealer waits, and so does the farmer in the field.

An example

A dealer asks Landrik whether the ZW 3,000 l fertiliser spreader with serial number 21-0847 can use section control on the terminal of a new tractor. demi finds the control unit with software version 3.2, a test record from the March field test with this terminal and two service cases in which the sections only switched cleanly after the update to 3.4. The answer: operation on the terminal works; for section control, install the released update 3.4, with links to the test record and the release note.
Fictional company, typical workflow.

Your data, wherever it lives

Test records from field tests sit today as spreadsheets and PDFs on the drive, software versions in the PLM, release notes as PDFs, service cases in the ticket system and in factory service's e-mails. demi reads, understands and links it per serial number, with your rights. So the dealer gets the answer in minutes instead of after a call-back, and your team decides which combination is released.

Where the data lives today

  • Tickets
  • E-mails
  • Phone & voice
  • PLM
  • Office files
  • PDFs
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the ticket system, e-mail, PLM, spreadsheets and PDFs. demi replaces nothing and links every machine by serial number to its equipment and the software version of its control unit, your test records from field tests with tractor terminals, the release notes of every software version and the service cases with their solution. So every combination of implement, terminal and software version has its evidence.

  2. 2 · PermitPermission Layer

    Dealers see answers on their own machines and the notes factory service has released for dealers; internal test notes stay in-house. demi recommends a software update only if it is released for that machine, and the workshop installs it.

  3. 3 · ActIntelligence Layer

    The agent reads serial number, tractor and terminal from the request, finds the machine's equipment and software version and looks for matching test records and service cases. It answers per function, such as operation on the terminal, section control or joystick, with sources, and says plainly when a combination has never been tested instead of guessing.

How it runs

  1. 1

    A dealer asks by e-mail, phone or dealer portal, with serial number and tractor

  2. 2

    demi finds the machine's equipment and software version

  3. 3

    Find test records, release notes and service cases for this combination

  4. 4

    Answer per function with sources, with a released update if needed

  5. 5

    Factory service checks new combinations and adds the evidence

What changes

  • Dealers get an answer with evidence instead of a call-back

  • Less downtime in the field over operating questions

  • Knowledge of combinations no longer rests on one colleague

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+180 hfreed per year

Assumptions and calculation

demi answers each request from test records, software versions and service cases; your team checks new cases.

20 min → 14 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

150 ISOBUS requests × 20 min × 30% × 1.0 (manual) × 12 months = 10,800 min = 180 h

Value per year, before demi costs

Freed per year+180 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$11,700

gained per year

180 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Does demi replace official ISOBUS testing?

No. demi shows what your machine can do and what you have tested with which terminal, every statement with its source. Which functions are tested and certified is in your records, and demi repeats it exactly as it is written there.

What if a combination has never been tested?

Then demi says so plainly and names what exists: tested terminals of the same series, service cases with similar software. The question goes to factory service, and its answer becomes the evidence for the next request.

Can dealers ask themselves?

Yes, in the dealer portal or by e-mail. Each dealer sees only their own machines and the notes released for dealers.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases