Context
Operational context
Farm teams needed to distinguish and manage animals with similar physical characteristics while maintaining reliable histories for treatment, breeding, vaccination and production decisions.
Challenge
The problem
Paper and fragmented records made it difficult to answer basic questions about treatment, birth dates, milk production, weight and breeding history. Missed interventions, weak lineage visibility and incomplete production records exposed the farm to preventable loss and poor decision-making.
Constraints
- Records needed to remain understandable to users working in day-to-day farm operations.
- Each animal required a reliable identity and complete lifecycle history.
- Health, breeding, production and financial information needed to remain connected.
Architecture
System design
A server-rendered PHP application provides farm workflows and reporting, backed by MySQL as the system of record. HTML, CSS and JavaScript deliver the user interface, with animal identifiers linking health, breeding, vaccination, production and financial events throughout the lifecycle.
Solution
What was built
I designed and built a central cattle register with linked health, treatment, vaccination, breeding, pregnancy, milk, weight and financial records. The application makes each animal’s history easier to retrieve and gives farm managers a clearer basis for productivity and breeding decisions.
Engineering judgement
Decisions and trade-offs
Animal-centred record model
Context: Similar-looking cattle were difficult to distinguish
Decision: Link every event to a persistent animal identity
Trade-off: Accurate identification still depends on disciplined tagging and data entry
Integrated lifecycle history
Context: Health and production data were separated
Decision: Keep breeding, treatment, production and finance events in one relational model
Trade-off: Broader records require clear permissions and consistent field definitions
Operationally simple web interface
Context: Farm users needed quick access to records
Decision: Use focused server-rendered workflows with familiar forms and reports
Trade-off: The design prioritises reliability over rich client-side interaction
Contribution
My role
- Analysed farm record-keeping and animal lifecycle requirements.
- Designed the relational data model and application workflows.
- Built the PHP and MySQL application and web interface.
- Implemented health, breeding, production and financial reporting.
Product demonstration
See the system in use
Results
Operational impact
- Centralised animal histories from birth to farm exit.
- Made treatment, vaccination and breeding records easier to track.
- Improved visibility into milk, weight and financial performance by animal.
- Supported better-informed breeding and productivity decisions.
Reflection
Lessons learned
- Livestock systems depend on reliable animal identification as much as software design.
- Data entry has to align with the rhythm of farm work to stay complete.
- Connecting health and production histories reveals more than isolated record sets.