Project description
The heart of the system is an inspection journal. Approaching a hive, we want to open the colony on a phone or tablet and record exactly what we actually check: whether we saw the queen or only eggs, how many frames of brood and stores, the bees' mood, signs of swarming, mite infestation and any treatments given with dose and date. Each record should automatically link to the hive, date and person and line up in a feed by colony, so at a glance we can tell if the colony is developing, lost its queen or is sliding into trouble. On top of this we need honey extraction accounting: how much honey each hive and each apiary yields per extraction, by frames or by weight, so by year's end we know actual productivity and understand which queens deserve breeding from. Colony health should highlight alarms by itself when a hive misses inspections, is marked sick again, or drops below our thresholds.
Around this core we need seasonal task planning tied to the calendar and to each apiary: the system should remind us about spring buildup, splits, adding supers, mite treatment windows, supplemental feeding and winter prep. And a simple equipment inventory—supers, frames, honey supers, containers and gear so we don't run short of hives during peak flow. All this should work normally without internet in the field and sync when we get signal, keep clear records for our own accounting and provide data export. We are beekeepers, not programmers, so using this needs to be truly simple—with frozen hands and a smoker in the other.
— Registry of hives and colonies with inspection feed for each colony
— Inspection journals: queen, brood, stores, temperament, disease, treatments
— Extraction accounting and productivity per hive and per apiary
— Health alarms for colonies and seasonal reminders for apiaries
— Equipment inventory, offline operation and data export