Digital Agriculture And The Internet Of Things In Practice
The archived IASSIST 2017 conference, held at the University of Kansas in Lawrence from 23 to 26 May 2017, examined how research data can become a common language across disciplines. Its sessions on big data, deep learning, digital agriculture and global food security remain useful because they frame connected farming as a data problem as much as a technology problem. Sensors, satellites, farm machinery and analytical models are valuable only when their outputs can be understood and used by growers, scientists, advisers and policymakers.
For Australian audiences, the subject has a particularly practical edge. A grain grower in Western Australia, a cotton producer near Moree or a cattle operator in Queensland may manage enormous distances, unreliable connectivity, seasonal labour and tight margins. The conference insights offer a way to assess the Internet of Things in agriculture without treating every new device as a solution. They point towards interoperable records, trustworthy measurements and decisions grounded in local conditions.
| Digital agriculture layer | Typical IoT input | Useful farming decision | Australian relevance |
|---|---|---|---|
| Field sensing | Soil moisture, weather and nutrient probes | Irrigation, sowing and fertiliser timing | Valuable across dryland cropping and irrigated districts |
| Machine connectivity | Tractor telemetry, yield monitors and guidance systems | Fuel efficiency, maintenance and variable-rate application | Suits broad-acre farms where operators cover large areas |
| Remote observation | Satellite imagery, drones and aerial surveys | Crop stress, pasture condition and crop-health mapping | Helps monitor distant paddocks and drought impacts |
| Data services | Cloud platforms, forecasts and predictive models | Risk planning, traceability and market decisions | Depends on regional connectivity and compatible systems |
From Connected Devices To Shared Evidence
The Internet of Things in farming is a network of physical objects that collect, transmit or respond to information. A weather station records rainfall and leaf wetness; a soil probe measures moisture at several depths; a harvester logs yield and grain quality; a collar tracks livestock movement. Each device produces a stream of observations, yet those observations have limited value if they remain isolated in separate dashboards.
The IASSIST programme’s focus on “data in the middle” is a useful lens. Data sits between a physical event and a management decision. A reading of declining soil moisture becomes meaningful when it is linked to crop type, rooting depth, recent rainfall, irrigation access and a forecast. The same number can support different actions on a vineyard, a wheat paddock or a mixed farm. Context, metadata and clear definitions therefore matter as much as sensor accuracy.
This principle challenges the idea that digital agriculture is simply a matter of installing more equipment. A low-cost sensor can be useful when it is well placed, regularly checked and connected to a reliable workflow. A sophisticated platform can disappoint when it creates duplicate records or sends alerts that do not fit the operator’s routine. Australian farmers often describe a system as useful when it saves a run out to the back paddock, reduces a wasted spray pass or makes a contractor’s instructions clearer.
What The Conference Revealed About Crop Monitoring
Remote sensing and large-scale crop surveillance featured strongly in the conference’s wider discussion of big data and global food systems. Satellite imagery can reveal changes in vegetation, canopy temperature and ground cover over time. Combined with field observations, these images help identify areas that deserve inspection. The method shifts attention from checking every hectare equally to prioritising the parts of a farm where intervention is most likely to pay.
A relevant example is the global crop health case study, which demonstrates how large datasets can support monitoring across regions. Its significance extends beyond a single research project. For Australian agriculture, similar approaches can assist with drought assessment, biosecurity surveillance, frost impacts and the early identification of crop stress. They can also support national and international reporting where ground teams cannot visit every location at the same frequency.
The value of this approach depends on combining scales responsibly. Satellite data may show a pattern, while a grower or agronomist explains whether it reflects water stress, disease, soil variation or a recent management change. In the Murray–Darling Basin, for example, imagery can help inform irrigation planning, but a map cannot replace knowledge of allocation rules, local water availability or crop contracts. The most credible systems connect remote observations with people who understand the paddock.
Deep Learning Needs Agricultural Context
Deep learning can identify patterns in images, sensor streams and historical records that would be difficult to detect manually. Applications include recognising weeds in a crop row, grading fruit, estimating biomass and classifying disease symptoms. In livestock production, machine learning can combine movement, weight and environmental data to flag unusual behaviour. These tools are promising because agriculture generates repeated observations across seasons and locations.
The conference context also highlights a limitation: a model learns from the data it receives. If training images come mostly from one crop variety, soil type or climate, performance may fall in a different setting. A disease-recognition model developed in a humid environment may struggle with Australian light conditions, dust or varieties bred for local production. Reliable deployment requires testing across farms, seasons and management styles, with farmers able to review and correct questionable outputs.
This is especially important in Australia’s diverse production zones. A precision system designed for broad-acre wheat in the Western Australian Wheatbelt has different requirements from one designed for horticulture around Mildura or a cotton property on the Liverpool Plains. Australian English and local practice matter in user interfaces too: a “paddock” may be divided into management zones, a Bureau of Meteorology forecast can influence spraying decisions, and a service visit may involve travelling hundreds of kilometres. Technical design has to fit the operating environment rather than assume compact farms and constant broadband.
Connectivity And Interoperability Shape Adoption
Connected agriculture relies on communications infrastructure that can carry data from remote places. Farms may use cellular networks, long-range radio, satellite links, Wi-Fi around sheds or a combination of these. Coverage can change across a property, and a device that works near the homestead may fail beyond a rise or tree line. Store-and-forward systems, local gateways and offline functionality can keep basic operations running when a live connection is unavailable.
Interoperability is equally important. A grower may own machinery from several manufacturers, subscribe to a weather service and use an agronomist’s platform. If each system stores data in a different format, the farm may spend time exporting files instead of analysing them. Common identifiers for paddocks, crops, machinery and dates make it easier to combine records. Application programming interfaces and open standards can reduce dependence on manual transfers and help a farm retain control of its historical information.
The commercial environment makes this a serious issue. Australian farms often purchase technology through dealers, agronomy businesses, machinery networks or industry schemes rather than through a single universal provider. A platform may appear affordable at first but become costly when licences, connectivity, calibration and support are added. Producers need to know who owns the raw data, whether it can be exported, how long it will remain accessible and what happens if a supplier changes its business model.
Turning Data Into Farm And Food Security Decisions
The conference connected digital methods with global food security, a theme that broadens the conversation beyond yield per hectare. Reliable data can support earlier responses to drought, pests, disease and supply disruptions. It can improve estimates of production, guide resource allocation and help organisations compare conditions across regions. For a country exposed to drought, fire, floods and changing export conditions, these capabilities have practical public value.
At farm level, data may support variable-rate fertiliser, targeted weed control, irrigation scheduling and maintenance planning. In the Australian grains industry, yield maps can expose persistent low-performing zones that warrant soil testing rather than blanket inputs. In horticulture, temperature and humidity records can help manage cold-chain risks. For livestock, connected weighing, water monitoring and location data can reduce unnecessary mustering and provide evidence for animal-health decisions.
Food security also involves trust, governance and access. A model that forecasts crop output may be useful to a grower, a co-operative, a bank or a government agency, yet each user has different interests. Small producers should not be excluded because a platform assumes expensive equipment or specialist analysts. Farmers need transparent explanations of automated recommendations, sensible cybersecurity protections and clear consent when operational data is shared for research or commercial purposes.
Building A Practical Australian Digital Farm
The IASSIST 2017 discussions suggest that successful adoption begins with a clearly defined decision rather than a device purchase. A farm might start by improving water-use visibility, reducing chemical overlap or identifying machinery faults before harvest. That narrow purpose creates a basis for selecting sensors, communications equipment and analytics. It also makes the return easier to measure in litres saved, hours avoided, inputs reduced or tonnes protected.
Implementation then becomes an operational exercise. Sensors require calibration, batteries need replacing and field boundaries change. Someone must check unusual readings and decide whether an alert reflects a genuine issue or a faulty connection. In a family business, that responsibility may sit with the farm manager; in a larger enterprise, it may involve an agronomist, machinery dealer, data specialist and finance team. The technology works when these roles are agreed rather than left to chance.
Australian conditions make this grounded approach essential. A platform has to cope with patchy regional connectivity, long travel distances and production systems that may span cropping, livestock and contract work. It must fit the way decisions are made during a busy harvest, when people need a clear answer rather than another dashboard. The lasting conference insight is that digital agriculture becomes valuable when data travels reliably from the paddock into shared understanding, and from that understanding into timely action.
At the Conference
What attendees experienced in Lawrence
Plenary Sessions
Keynotes from Daniel Reed on data, technology, and culture, and Jennifer Clarke on digital agriculture and the Midwest Big Data Hub.
Workshops
Full-day technical workshops on Tuesday, May 23. Morning sessions ran 9:00–12:00 and afternoon sessions 13:00–16:00. Laptops were required.
Social Events
An opening reception at The Oread, a banquet, and an optional post-conference tour of Kansas City including Crescent Moon Winery.
Venue & Accommodations
Where the conference took place
Kansas Union
University of Kansas campus, Lawrence. Main conference venue with check-in on the 4th and 5th floor lobbies.
The Oread
1200 Oread Avenue, Lawrence. Hosted the opening reception and offered a room block for attendees.
The Eldridge
701 Massachusetts Street, Lawrence. A partner hotel with a reserved room block for conference guests.
Springhill & TownePlace Suites
Marriott properties in Lawrence with room blocks reserved under the "KU IASSIST Conference" name.
Program Highlights
Sessions and activities
Getting Here
Lawrence, Kansas
Kansas Union · University of Kansas
1301 Jayhawk Blvd, Lawrence, KS 66045
Kansas City International Airport (MCI) is approximately 50 minutes by car. Lawrence Transit Routes 10 and 11 served the area ($1 exact change).
Plan Your Stay
Accommodation options that were available
The Eldridge
701 Massachusetts Street, Lawrence, KS 66044. Room block now closed.
The Oread
1200 Oread Avenue, Lawrence, KS 66044. Room block now closed.
Springhill Suites
Marriott property. Room block reserved under "KU IASSIST Conference."
TownePlace Suites
Marriott property. Room block reserved under "KU IASSIST Conference."