From crop plan to invoice, on one governed model.
How a commercial greenhouse runs planning, tasks, climate monitoring, harvest, sales, finance and compliance on OYO AI: every plan activated atomically, every lot traceable in seconds, every promise checked against what can really be delivered.
What the greenhouse gets, in numbers.
Every figure here is enforced by the platform, not requested in a manual. Configured on OYO AI, not custom code, so it holds on day one and on day one thousand.
From seed supplier to customer invoice and back. A mock recall takes minutes, and the notification list is exported with it.
A disposal cuts what Sales can promise within one aggregation cycle, so nobody oversells a crop that no longer exists.
Expired certifications are refused by name and date, and a renewal task is generated 30 days ahead.
Online or offline. Work queued without signal syncs with idempotency keys, so there is never a duplicate record.
- 6 gates enforced automatically: PHI, REI, certification, credit, capacity, water
- 12-month cash projection, negative months flagged
- 1 open alert per zone, parameter and rule
- 4 h for a full mock recall, customer notification included
- 3 pay types in one payroll run
Two objects carry everything: the crop plan and the lot.
A greenhouse plans crops per zone, turns each plan into tasks, watches the climate through sensors, treats and harvests under food-safety holds, sells against what it can honestly promise, and closes every plan with its economics.
A plan is one variety, in one zone, over one date range, activated all or nothing. A lot is born at harvest with an immutable code and carries its whole history forward and back: seed batch, treatments, water tests, workers, orders, customers, invoices.
What the system can promise, and what it will not let through.
Available to promise, recomputed within one aggregation cycle of any disposal. Sales never sees a crop that no longer exists.
PHI and REI holds
A treatment computes its own pre-harvest and re-entry intervals. Harvest and task assignment are blocked until they expire, and any override is flagged on the compliance dashboard.
Certification and credit
A licensed task cannot go to an expired licence; an order cannot confirm beyond the customer’s credit limit without Finance.
Capacity and water
Plans cannot overlap beyond a zone’s productive area. A failed water test flags every lot harvested since the last passing test on that source.
The chain a crop follows.
- 01Crop plan
- 02Tasks
- 03Sensor readings and alerts
- 04Treatments with PHI / REI
- 05Harvest, creates the lot
- 06FEFO picking
- 07Sales order with ATP and credit
- 08Delivery
- 09Invoice and payment
- 10Plan economics
Ten modules, in the order of the release plan.
The core loop and harvest first, then sales and finance, then compliance and analytics, with water, energy and workforce alongside. Twenty use cases, each with its main flow, alternative flows, postconditions and the rules it enforces.
Module 1 · Crop planning and activation
- UC-01Create and activate a crop plan
- UC-02Apply a rotation template to a zone
Module 2 · Task management and mobile execution
- UC-03Bulk assign generated tasks
- UC-04Execute a task offline, on mobile
Module 3 · Environmental monitoring and IPM
- UC-05IoT anomaly detection and alert generation
- UC-06Record a treatment application with PHI / REI holds
Module 4 · Harvest, QC and lot management
- UC-07Harvest produce with the PHI gate
- UC-08FEFO picking with override
Module 5 · Sales and order fulfilment
- UC-09Place a sales order with ATP and credit check
- UC-10Handle a delivery rejection
Module 6 · Finance and invoicing
- UC-11Auto-generate an invoice and record payment
- UC-12View the 12-month cash flow projection
Module 7 · Compliance and traceability
- UC-13Run a traceability query (mock recall)
- UC-14Handle a failed water test
Module 8 · Analytics and strategic re-planning
- UC-15Review plan economics at completion
- UC-16Record a disposal and update ATP
Module 9 · Water and energy management
- UC-17Record an irrigation event with drain metrics
- UC-18Record the monthly energy meter reading
Module 10 · Workforce and payroll
- UC-19Process payroll with mixed pay types
- UC-20Assign a pesticide task to a certified worker only
Seven personas and a system that acts on its own.
Owner
Reads the cash runway and the plan economics, and holds the final override.
Manager
Assigns tasks in bulk, authorises IPM actions, confirms dispositions on rejections and disposals.
Agronomist
Designs and activates crop plans, applies rotation templates, records treatments and disposals.
Worker
Executes field, warehouse and driving tasks on mobile, online or offline, with photos where the rules ask for them.
Sales Manager
Places orders against available-to-promise stock and forecast, inside the customer’s credit.
Finance Officer
Records payments atomically, runs mixed-pay-type payroll, reads the 12-month projection.
QA / QC Officer
Grades the harvest, records water tests, runs mock recalls and real ones.
Gates the system enforces, each with a message.
Atomic activation
Rationale, capacity, task generation, seed reservation, notification and audit happen together or not at all. A retry is absorbed by its idempotency key.
PHI gate on harvest
A worker opening a harvest task under an active pre-harvest interval sees the exact release date and cannot proceed.
Grades must sum
Class A plus Class B plus waste must equal the total kilograms, or the lot is not created.
FEFO, or a reason
Lots are offered first-expired-first-out. Scanning another lot is refused; an override needs a reason and leaves an audit record.
Credit before confirmation
An order beyond the customer’s limit holds for credit review. Only Finance or the Manager can move it.
No document without substance
An invoice needs a complete company profile and at least one line. A document that itemises to nothing is not a document.
Offline, but never twice
Work queued without signal syncs with idempotency keys; the earliest start wins, the latest progress wins, and completion never reverts.
Certified hands only
A task that needs a licence cannot be assigned to an expired one, and a renewal task is generated 30 days before expiry.
A traceability query, answered in seconds.
A mock recall is scheduled every six months; a failed water test is the real thing. Either way, the lot code is enough. Both directions return within ten seconds and the customer notification list is exported.
Backward: where it came from
- Crop plan, zone, seed batch and seed supplier
- Every treatment with its PHI status
- Every irrigation event and the water tests covering them
- Every worker involved and every piece of equipment used
Forward: where it went
- Inventory transactions and picking
- Order items and orders
- Customers and deliveries
- Invoices, with the elapsed time recorded
The lot code is written once, at harvest, and never changed. That single decision is what makes the answer fast and the answer complete.
Get the full use-case specification.
The complete document, organised by module: every use case with its actors, preconditions, main flow, alternative flows, postconditions and the rules it enforces, plus the matrices a reviewer needs.
- All 20 use cases with flow diagrams, alternative flows and postconditions
- The persona and business-rule matrices, and the KPIs the system computes on its own
- The gates, the lot code and the available-to-promise formula, explained in one page
Also read the textile manufacturing use case: One roll, from delivery to unit cost.