From milk cooling tanks to grain bins, timely information helps farmers keep operations running smoothly. Explore how Solvative worked with Paul Mueller Company and OPI Systems to bring connected monitoring into everyday farm work.
.png)
.png)
Farmers have always carried risk that most people never see. Grain spoiling silently in a bin forty feet off the ground. Milk is warming in a tank while the herd is still being milked. These are not edge cases; they are Tuesdays. The question is whether anyone finds out in time to do something about it.
A dairy farmer's day starts before sunrise and rarely ends before dark. There is no clock-out, no handover to a night shift. The operation, the animals, the tanks, the cooling systems, and the grain stores run continuously, and it runs on the assumption that nothing critical has gone wrong while nobody was watching. That assumption does not always hold true.
Across the American agricultural landscape, the gap between when something fails and when a farmer finds out about it has historically been measured in hours, sometimes days. And in farming, the cost of that gap is not abstract. It is measured in gallons of milk that cannot be sold, in bushels of grain graded down or rejected entirely, in years of work and investment quietly lost to a failure that nobody saw coming because nobody could see inside the system at all. This is the problem that Paul Mueller Company and OPI Systems set out to solve. And it is the kind of problem that, in our experience, reveals what separates yesterday's guesswork from today's visibility.
The numbers are large enough to be worth stating plainly. The USDA estimates that postharvest losses to corn and wheat alone from insects and spoilage amount to as much as $2.5 billion annually in the United States. Globally, a peer-reviewed analysis of grain supply chains found that storage losses due to toxin contamination, temperature failures, and moisture buildup account for hundreds of millions of tons of grain annually. Grain stored on-farm in the US is routinely held for months at a time. The USDA reported over 7.66 billion bushels of corn stored on farms as of December 2024, and every day of that storage is a day something can go wrong quietly and compound before anyone detects it.
Dairy is no different. Raw milk must be cooled to 45°F (7°C) or below within a specified window after milking, as required by the Pasteurized Milk Ordinance. Any excursion above that threshold, whether from a compressor failure, a power interruption, or a control system fault, can render an entire tank unsaleable. Bacterial populations in milk can double every 20 minutes at elevated temperatures; what starts as a mechanical fault quickly becomes a food safety event. A milk recall at the processor level averages $10 million in direct costs. On the farm, the math is simpler and more personal: thousands of gallons, weeks of work, gone.
For most of the history of commercial farming, the answer to 'How do you know what is happening inside your grain bin?" was "You climb up and check." Grain bins on commercial farms commonly stand 60 to 120 feet tall and hold anywhere from 50,000 to over a million bushels. Physically climbing them to connect a handheld reader to each sensor cable, gather readings, and descend again is time-consuming, physically demanding, and genuinely dangerous. It is also infrequent by necessity, which means conditions inside the bin can shift significantly between checks.
Dairy monitoring had an analogous gap. Temperature and system data were logged manually on paper, with no digital trail, no historical analysis, and no capacity for remote visibility. A farmer who was tilling a field, attending a livestock auction, or simply asleep had no way to know that the compressor in the milk house was struggling until they walked in the door and saw the readout.
The legacy systems were not failing the farmers who used them. They were simply the best available tool for a monitoring problem that had not yet been solved at the hardware and software level. The question was what happened when better tools became available and whether those tools could be built in a way that worked for the people who actually needed to use them.
The technology could not just work. It had to work for someone who had been on their feet since 4 am, who does not consider themselves a technology person, and who has thirty other things competing for their attention.
When OPI Systems, a global leader in grain management technology trusted across more than 75 countries, came to Solvative, the brief was specific: replace the climb. Replace the handheld reader and the physical ascent with something a field operator could use from the ground. The OPI BLUE Lite sensor device was already deployed in bins. The question was how to connect it to the people responsible for the grain inside them.
The answer was a cross-platform mobile application, built natively for iOS and Android, that connected to the OPI BLUE Lite via Bluetooth Low Energy. A field operator could walk to the base of a bin, open the app, and pull live temperature and moisture readings without ever leaving the ground. The data were automatically transmitted to OPI’s cloud infrastructure and surfaced on a web dashboard, where historical trends, alerts, and cross-bin comparisons were visible in one place.
Two aspects of this project say everything about what it means to build technology for real working conditions rather than controlled environments. The first was offline functionality. Grain bins are frequently in remote locations where cellular connectivity is unreliable or absent. Solvative built local caching directly into the app so that readings captured with no internet connection was stored and synchronized automatically whenever a connection became available days or weeks later if necessary. The farmer’s data never went missing because the signal did.
The second was conflict resolution. Users could create and name grain bin sites both through the mobile app and through the web dashboard. If a site was created offline in the app at the same time a similar site was created online, the sync could result in duplicate records. Solvative built a detection and resolution flow that surfaced conflicts to the user and let them decide which version to keep clean, accurate data without requiring any technical knowledge to maintain it. The result: what was a physically demanding, time-consuming climb became a few minutes of work from the ground. A grain operator monitoring a dozen bins no longer needed a full morning and a head for heights. They needed a phone and a Bluetooth connection.
The Paul Mueller Company engagement began with a similar question, approached from the dairy side of agriculture. Paul Mueller Company, headquartered in Springfield, Missouri, and manufacturing the stainless steel bulk milk cooling tanks used by dairy farmers across the United States and internationally, wanted to modernize its HiPerForm III control system into something that could communicate, alert, and be managed remotely. The result of that partnership was MilkSecure, an IIoT platform built on AWS that gave dairy farmers real-time visibility into their cooling systems from any connected device. Temperature, volume, system health, and wash cycle status accessible on a phone anytime, anywhere.
The Solvative and Paul Mueller teams visited multiple dairy operations to watch how farmers actually worked, how milk moved from the milking parlor to the bulk tank, how cooling cycles ran, and how haulers interacted with the system at pickup. The resulting interface was built around that workflow, not around what a software team imagined the workflow might look like. Touchscreen navigation with intuitive icons. Automated alerts that did not require a farmer to know what a normal system state looked like in order to recognize an abnormal one. Not long after the platform went live, an alert fired. A temperature spike in a bulk milk tank. The kind of reading that, without MilkSecure, might not have been noticed until the next manual check, by which point the milk inside would have been unsalable.
Our Solvers drove to Springfield; they traced the fault, addressed it, and preserved the milk. Thousands of gallons. The kind of volume that represents not just dollars, but weeks of a farmer’s labor, the output of an entire herd over days, and the thing that the whole operation exists to produce. The alert system worked exactly as it was designed to. But what that moment also revealed is something harder to build into a spec document: the difference between technology that reports a problem and technology that gives someone enough time to solve it. The farmer should be able to be tilling their field, pull up their phone, and know that everything inside the milk house is exactly where it should be. If it isn’t, they should know that too.
Both of these projects began with the same thing: the Solvative team going to where the farmers were. For the Mueller engagement, that meant visiting dairies and watching operations firsthand before a single line of code was written. For OPI, it meant working directly with hardware and firmware engineers to understand the embedded logic of the physical device so the software communication layer could interpret sensor output accurately and reliably. This is what we mean by alignment between a technology partner and a client.
It is not about shared terminology or matching slide decks. It is about shared understanding of the problem, what is actually happening in the field, what a farmer needs to do, what breaks down under real conditions, and what a successful outcome looks like for the person operating a grain bin at dusk or a dairy at 4 am. The features that resulted in BLE connectivity, offline sync, cloud alerts, remote wash cycle management, electronic time and temperature recording, and a touchscreen interface designed around error-free operation were not a list someone generated in a product meeting. They were the answers to specific problems observed in specific places.
There is an image worth holding onto. A farmer on a tractor, mid-field, somewhere in the middle of a long working day. They pull out their phone. Not to make a call or scroll something but to check. Temperature in the milk chiller: normal. Grain moisture in bins two and three: within range. The alert from this morning: resolved. They put the phone back and keep going. That is what this technology is actually for. Not the dashboard, not the cloud architecture, not the BLE protocol or the offline sync engine, though all of those things had to be built correctly for any of it to work. The point is that moment of confidence. The ability to know, without stopping what you are doing and driving somewhere to check, that the operation is running as it should.
Agriculture has always been a discipline of managing things you cannot fully control. Weather, markets, disease, equipment. What technology can do when it is built the right way, for the people who actually use it, is narrow the category of things you cannot see. It does not eliminate risk. It moves the farmer from discovering a problem after the fact to having the information to prevent it or respond to it while there is still time. That is what Paul Mueller Company and OPI Systems understood when they came looking for a partner. And that is what we built.
.jpg)
