ZetrixwebFarm Hierarchy
1 Land2 Lots87 Lines950 Palms
Case Study
Taryouvet Farm Management: turning a Sahara oasis date-palm farm into a data-tracked operation.
Managing a date-palm plantation by memory and paper logs breaks down fast once a farm crosses a few hundred trees - which palm was replanted, which lot is due for fertilization, which line has a disease outbreak. Zetrixweb built Taryouvet Farm Management, a role-based operations platform that turns a real oasis farm - 950 palms across 87 planting lines - into a structured, queryable system for owners, supervisors, and field agents alike.
950 palms tracked
Land → Lot → Line → Palm
4-role access model
Taryouvet Ledger
Live
Farm Size 150,000 m²
Ops Pipeline 11 stages
Region Sahara oasis
Executive Summary
A geospatial, role-based system built around how a real farm actually operates.
Land/Lot/Line/Palm hierarchy
Configurable 11-stage ops pipeline
4-role access control
Palm health & replant analytics
Taryouvet Farm Management gives a Sahara oasis date-palm operation the same operational rigor a modern warehouse or fleet business would expect - except the "assets" are living palm trees spread across lands, lots, and planting lines. The platform models the farm's real physical structure (currently one 150,000 m² land, split into 2 lots and 87 lines, holding 950 individually tracked palms), attaches every field action to a configurable operations pipeline, and gives owners, admins, supervisors, and field agents distinct, role-scoped views of the same data.
Challenge
Farm knowledge lived in one person's head, not in a system.
At real oasis-farm scale, informal tracking (notebooks, memory, verbal handoffs between field agents and supervisors) stops working - and the cost of getting it wrong is a dead or sick palm nobody caught in time.
Hundreds of individually meaningful assets
950 palms across 87 lines can't be managed as one undifferentiated block - each line, lot, and palm needs its own status and history.
Different roles need different views
A field agent needs "what's my task today," a supervisor needs "what needs attention across my lots," and an owner needs the farm-wide picture - one screen can't serve all three.
Every farm's operations pipeline is different
Planting, irrigation, fertilization, pollination, and harvest cadences vary by crop and farm - a hardcoded workflow wouldn't fit the client's actual process.
Discovery Phase
We mapped the farm before we wrote a line of code.
A farm operations platform only earns trust if it matches how the farm actually runs - so discovery focused on the physical structure and the people, not the software.
01
Map the physical farm
We walked the client's real farm hierarchy - lands, lots, planting lines, and individual palms - and modeled it directly, instead of forcing a generic "asset" abstraction onto it.
Land → Lot → Line → Palm02
Interview every role
Owners, supervisors, and field agents each work off different information - we scoped separate views and permissions for super admin, admin, supervisor, and agent from day one.
4 distinct roles03
Define the real operations model
Rather than hardcoding a workflow, we built the 11-stage operations pipeline (planting through cleaning & trimming) as configurable and reorderable, so it reflects this farm's actual practice.
Configurable, not fixed04
Prioritize for field reality
Dashboards were designed to answer "what needs attention right now" first - open issues, sick or dead palms, and recent replants surface before anything else.
Attention-first UISolution
A geospatial hierarchy, a configurable pipeline, and role-scoped dashboards.
The platform's complexity sits underneath a simple surface: every palm belongs to a line, every line to a lot, every lot to a land - and every action on a palm flows through the same configurable operations pipeline.
Taryouvet Farm
Farm Control
From a walked field to a role-scoped dashboard for every stakeholder.
Farm Explorer lets an admin drill from the farm's single land down through its 2 lots and 87 lines to any individual palm, cross-referenced with a live map view. Every operation - planting, irrigation, fertilization, hole treatment, pruning, pollination, fruit thinning, disease/pest monitoring, harvest, and cleaning - is logged against a configurable, reorderable 11-stage pipeline, with each stage tagged as manual, scheduled, or fully automatic. Health analytics track replant rate, active vs. marked-dead palms, and which varieties are most often used as replacements, while a role-based task system splits "Assign Tasks" (supervisors/admins) from "My Tasks" (field agents) so nobody sees more than their job requires.
Discovery
Mapped the real land/lot/line/palm hierarchy and interviewed every role to scope a 4-tier permission model.
Build
Delivered Farm Explorer, map view, the configurable operations pipeline, task assignment, and palm health analytics.
Launch
Live in production tracking 950 palms across 87 lines, with role management, security, and settings modules for ongoing admin.
950 palms across 87 lines, individually tracked
11-stage configurable operations pipeline
Replant rate and "needs attention" surfaced automatically
Farm Explorer & Map
Drill from land to a single palm
A hierarchical explorer plus a geospatial map view, so an admin can move from the whole farm down to one palm's history in a few clicks.
4-level hierarchy
Map view
Drill-down search
Operations & Task Assignment
A pipeline that matches how this farm works
An 11-stage, reorderable pipeline with manual/scheduled/automatic cadences, plus separate assignment and "my tasks" views by role.
Reorderable stages
Role-scoped tasks
Health & replant analytics
UI/UX Standards We Followed
Data-dense doesn't have to mean cluttered.
A farm operations dashboard lives or dies on whether a busy supervisor can find what matters in seconds - these are the standards we held the interface to.
Role-First Information Architecture
Navigation, dashboards, and permissions are scoped per role from the ground up - a field agent's "My Tasks" view is deliberately narrower than an admin's farm-wide dashboard.
4 role scopes
Least-privilege by default
Attention-First Dashboard Density
The overview screen leads with snapshot counts and a "Needs Attention" list, not a wall of raw data - dense information, but ordered by what to act on first.
Snapshot summary
Needs-attention surfacing
Light/Dark Theming, Built In
A theme toggle (with an auto mode) and a language switcher were built into the shell from the start, not retrofitted - field use happens at all hours and in bright outdoor light.
Auto/light/dark
i18n-ready shell
Configuration Over Hardcoding
The operations pipeline is reorderable and editable in Settings, not baked into the code - so the UI teaches the underlying model instead of hiding it behind a fixed workflow.
Reorderable stages
Editable cadences
Most Loved Features
The complexity we handle so the farm team doesn't have to.
Land → Lot → Line → Palm Explorer
A true geospatial hierarchy - 1 land, 2 lots, 87 lines, 950 palms - browsable and cross-linked with a live map view.
4-level drill-down
Map integration
Configurable Operations Pipeline
11 stages - planting, irrigation, fertilization, hole treatment, pruning, pollination, fruit thinning, protection, disease/pest monitoring, harvest, and cleaning - each independently reorderable and tagged manual, scheduled, or automatic.
11 stages
Reorderable
Role-Based Task Assignment
Supervisors and admins assign work through a dedicated "Assign Tasks" view; field agents see only "My Tasks" - keeping the field-facing UI simple by design.
Assign / My Tasks split
4-role permission model
Palm Health & Replant Analytics
Automatic tracking of replant rate, active vs. marked-dead palms, most-replaced varieties, and a "Needs Attention" list surfaced by land, lot, and line.
Replant rate tracking
Variety analytics
Have an operations platform for a physical, field-based business in mind?
Farms, plantations, and field-service operations all share the same problem: real-world hierarchy that most software flattens. We build for the hierarchy that's actually there.