Koldheim ยท Emerald

Field Trials

Agriculture

Trials in the field, with incidents raised by rule.

Catch a trial result that breaks a rule, the moment it is recorded.

Agricultural trials with seed drawn against the trial from a depot, and an incident raised the moment a result breaks a rule rather than at the end of the season.

The problem

“We run seed trials across many fields, seed bags go out and we cannot reconcile what was issued against what was planted, and a bad result is never properly reviewed.”

What it runs

What happens, in order

Every one of these is a step the service takes itself. Nothing in this list is somebody remembering to do it.

8 steps
  1. The trial is set up: type, variant, field, hectares, agronomist and bags requested.
  2. Seed bag stock is checked.
  3. If stock is short, procurement is alerted, a partial issue is sized arithmetically, the available stock is drawn down and a stock request is raised for the remainder.
  4. The trial goes to field.
  5. Results are captured and yield per hectare is computed.
  6. A rule asks whether too few bags were used for the hectares claimed.
  7. If so an incident is raised, the incident team is alerted, written assessments are collected and the trial closes flagged.
  8. Otherwise it closes clean.
It opens on these
  • Trials in field
  • Open incidents
  • Mean yield
  • Hectares under trial

Every figure opens what it counts and offers the next action. Nothing here is compiled at month end.

Try the rule

Record the harvest. Watch the rule.

Yield per hectare from tonnage and hectares, and the bag-usage rule: under 70% of the bags issued raises an incident for your incident team to assess.

One trial
Trial types, variants and seed rates are yours. These are the example farm's.
Under 70% of the bags issued raises an incident. The rule is authored with the service.
The result
8,7 t/haUnder 70% of bags used: incident raised

Bags issued
24
Bags used
16
Used of issued
66,7%
Incident below
16,8 bags, 70%
Yield
8,7 t/ha
Target, Maize Yield Trial
9,5 t/ha
  1. Trial set upMaize H1, 90 kg N/ha on 12 ha, 24 bags requested. The variant specifies 2 bags a hectare.
  2. Stock check: enough24 bags issued and drawn from the 40 on hand.
  3. Stock request raisedIt records 24 bags requested and 24 issued.
  4. Results captured16 bags used, 104,4 t harvested: 8,7 t/ha.
  5. Too few bags used: incident raised16 is under 70% of the 24 issued (16,8).
  6. Incident team alertedThe agronomy lead, operations manager and QA lead, or whoever you name.
  7. Assessments collectedAt least two written assessments of what happened and what should change.
  8. Closed, flaggedThe trial closes with its incident under review, and the agronomist and agronomy lead are told the final yield.
Who sets what

Yours to change, and ours

Most vendors are vague about this line. Yours is everything about how your organisation works. Ours is the shape of the process itself.

Your administrators change these

  • Trial types, variants and seed rates
  • Who is on the incident team

Authored with the service

  • The bag-usage rule that raises an incident

A change here is a draft, checked and published. Work already under way stays on the version it started on.

Where it stops

The part most pages leave out

A service that only ever says yes is not evidence. This is the place it deliberately refuses, and the suite that proves it still does.

Refuses, on purpose

It will not issue bags it does not have

Short stock is neither a block nor an over-issue. The partial issue is sized from what is actually there, the remainder becomes a stock request, and both are on the record.

Proof

Every claim here runs on each build

Not a policy, a suite. This one is npm run e2e, and it fails the build rather than a report nobody reads.

The rest of the collection

One stone, many cuts

Keep exploring

Where to next

See it with your own process.

Book a demo