2.2 Product Moonitoring

Before designing a database, service, or integration, it is important to understand the operational problem the product must solve. This page describes that problem and the intended outcome without prescribing a technical implementation.

2.2.1 Problem Context

Dairy farms already collect valuable information about their animals, but that information is fragmented across independent herd-management and sensor systems. Each provider may use different formats and interfaces, and some systems are available only from a Windows computer inside the farm network.

Farmers should not need to export and upload data manually every day. Farm computers and network connections also cannot be assumed to be continuously available or reliable, so incoming data may be delayed, duplicated, interrupted, or malformed. Any collected evidence must remain traceable to its farm, provider, and time of receipt, including enough information to understand processing failures.

Different providers may describe the same animal or real-world event in different ways. Moonitoring must preserve provider-specific evidence while producing common information that higher-level services can use, reconciling compatible facts without silently discarding conflicts between sources.

Core problem

Moonitoring must transform fragmented and unreliable farm data into a traceable, farm-scoped, and sufficiently uniform foundation without losing the original source evidence.

2.2.2 Product Objective

The product must automate the periodic collection of information from the provider systems configured for each farm, avoiding routine manual exports while remaining resilient to temporary connectivity and processing failures.

The resulting platform must isolate each farm's information, preserve raw evidence and processing history, and construct shared representations of animals and relevant events. This foundation can then support farmer-facing applications, analytics, machine-learning models, conversational tools, and risk-related services.

Scope of this page

This page defines the problem and product objective. It does not define databases, services, APIs, or data schemas; those implementation decisions belong in the Architecture and Data sections.