Platform overview
One record, and everything else hangs off it
Most farm software is a collection of tools that happen to share a login. This is a single record — customer, farm, barn, flock, week — that production data, feed analysis, alerts, diagnostics and reports all attach to.
The hierarchy
Structured the way an operation actually is
A company runs several farms. A farm has several barns. A barn houses one flock at a time and remembers every flock before it. Every week of data belongs to exactly one flock cycle.
-
01
Customer company
The tenant boundary. Everything below belongs to it.
-
02
Farm / location
A physical site, with its region and the species it runs.
-
03
Barn / house
A housing unit. One active flock at a time for layers.
-
04
Flock
Genetics, placement, production type, feed and lifecycle.
-
05
Weekly data
Performance, environment, diet name and comments.
What the platform does
Nine capabilities, one set of numbers
Data capture
Validation
Calculation engine
Genetic standards
Peer benchmarking
Alerts
Feed intelligence
Reports
Diagnostics
Design principles
Decisions we made early, on purpose
Raw and calculated data are stored separately
What you entered is kept exactly as you entered it, with its unit and its source. Derived values are stored alongside with the formula version that produced them. That is what makes recalculation safe and reports reproducible.
Species is configuration, not code
Metrics, units, plausibility ranges, standards, templates and alert rules are data. Adding broilers or swine is product work, not a rebuild of the foundation.
Nothing is half-imported
A file with a blocking error imports zero rows. There is no partial state to reconcile later.
Unapproved science is not presented as science
Where a formula, threshold or scoring method has not been approved by our nutrition team, the platform says so rather than filling the gap with a plausible guess.
Bring a spreadsheet. We will show you what it reads.
The most useful demo is the one that runs against your own tracker.