FarmSentinel

FarmSentinel
Your 24/7 Farm Monitor Against Crop-Damaging Tiny Pests
  
  
Project Brief
  
The Pea Weevil, a tiny pest measuring 0.3-0.5 cm, causes severe damage to pea crops, reducing their value by over 70% and leading to significant financial losses each spring and summer. In Eastern Washington, farmer Andrew Nelson manages over 7,500 acres, owns the largest pea farm in the state, but the weevil's small size and rapid reproduction make it difficult to control. During peak seasons, Andrew’s team spends extensive time patrolling fields almost daily, consuming substantial labor and resources. They urgently need an automated monitoring system.

To address this, our team developed FarmSentinel, an automated monitoring solution based on Microsoft's FarmVibes project series. Using computer vision, we built an integrated hardware-software system. As team lead, I secured the project, conducted contextual inquiries, participated in low-fi & hi-fi interfaces design, managed usability testing, and led iterative design sprints using agile methodology.

The final product won "2nd Best Product Design" among 18 teams and was presented at the IEEE International Conference on IoT and Intelligence Systems (IoTaIS 2024).
Sponsored By
  
  
  
My Role
  
Team Lead
UI/UX Designer
Front & Back-end Developer
Project Type
  
To B Team Project
Sponsored by
Microsoft FarmVibes
Time Frame
  
March - June 2024
Tools Used
  
VScode, React Framework, Flask Server, Figma, Adobe Photoshop, Protopie
Quick View of Deliverables 🌟
  
How Does The System Work?
Unified Dashboard
This is the primary interface users engage with most frequently. Given that a significant portion of our users are over 35, including a notable number of seniors, we designed the Dashboard (set as the Homepage) to visually and concisely display all key data collected from the field in real time.

It provides a clear, at-a-glance view of essential field data and pest status. Call-to-actions (CTA), such as viewing device details and accessing the pest Warning List, are prominently displayed to minimize cognitive load and ensure ease of use.
Data Analysis
Device Management
Rather than driving all day between fields, users can simply click on devices with pest detections from a list or map to view the latest photos and pest counts. They can also access all related photos and data, adjust detection intervals, and remotely control the device to capture real-time images.
Intro Video
Links
  
Design System
  
Desktop App Grid (1440 x 1024 px standard)
  
  
  
Hardware Device Prototype (Team Work)
  
More Details
Problem Scope
  
Secondary Research (Team Work)
  
Question: Is the problem our sponsor encountered a unique case, or is it a common issue nationwide?
  
Answer: It is a common issue. Agile and real-time pest monitoring has nationwide potential.
Contextual Inquiry (Team work)
  
We interviewed 11 farms in Washington State, and visited 3 of them to conduct Contextual Inquiries.
  
  
Here's the qualitative data we collected:
  
  
Empathy Map & Affinity Diagram
  
  
Triangulated Insights
  
Key user pain points:

        1. No existing effective pest control methods, especially for tiny pests.
        2. Device and maintenance cost is too expensive.
        3. Labor cost and shortage increase year by year.
  
Based on all the data we have gathered, we developed the user Persona for our sponsor:
  
  
Persona
  
Design Question
  
How can we leverage IoT devices                                                                                                                                               --> How 
in spring and summer 
                                                                                                                                                               --> When
to help 20–50-year-old farmers on western Washington,                                                                                  --> Who & Where
constantly monitor pest infestation in farm fields                                                                                                       --> What   
thereby saving them time and money while reducing economic losses caused by pests?                                      --> Why
Key Metrics
  
Unlike B2C’s user-centric and experience-driven approach, B2B products prioritize business needs, internal use, and efficiency. Key considerations include:
   > Business-Centric: Emphasis on business operations over user experience.
   > Efficiency: Focus on operational efficiency.
   > Repetitive Design: Greater attention to reusable design patterns.
   > Simplified and Unified Design: Reducing development complexity and costs.
   > Data Structure: Clear presentation of complex data structures.
  
Based on the design question and B2B design perspective, we have developed key metrics to guide us in generating effective solutions
Competitive Analysis & Ideation (Team work)
  
  
  
Hardware & Software Architecture
  
Prototype - Hardware (Team work)
  
Prototype - Software
  
This app is developed under React Framework and has been deployed on Azure
  
  
  
  
Information Architecture
  
  
  
  
Low-fidelity Prototype (Team Work)
  
  
  
  
Usability Testing with Sponsor (Team Work)
  
Task 1: Add devices on the map.

Task 2: Data visualization view mode switch.

Task 3: Alert users when multiple pea weevils are detected and inform farmers about the pest count and severity.

Task 4: Allow users to quickly check the working condition of any devices.

Task 5: Remote real-time picture capturing and check severity.
Reflection
  
Challenge Navigating Negotiations and Securing the Project
This sponsored course project taught me invaluable lessons, particularly in communication and negotiation.
At the outset of the semester, our team, composed solely of three students with design backgrounds, faced stiff competition from groups with stronger CS expertise, all vying for the Microsoft FarmVibes collaboration. Given the project’s heavy emphasis on IoT devices, we were at a clear disadvantage. However, determined to seize this learning opportunity, I calmly assessed the situation and quickly mapped out the project's framework and technical roadmap. Leveraging my communication skills, I initiated negotiations with the project supervisor, articulating our clear vision and technical roadmap. Through strategic discussions, I turned our perceived weaknesses into strengths, and despite the odds, we emerged victorious, securing the project. This experience was a significant test of my abilities, as I had less than 30 minutes to strategize and execute the negotiation plan, ultimately leading to our success.
  
Overcoming Challenges and Leading the Team
The project’s 10-week timeframe was extremely tight, and we were tasked with solving complex problems. We had to start from scratch, learning everything from Raspberry Pi programming to database setup, front-end development, and data transmission. I invested considerable time in developing a streamlined, AI-assisted learning & working flow that allowed for rapid testing and iteration of our hardware. As the team leader, I also organized regular work sessions to address challenges collectively, fostering a supportive environment that kept the team motivated. Despite the daily hurdles, including persistent software bugs, no one gave up. Time management was another major challenge, but we managed it well. Our sponsor was highly impressed with our dedication and outcomes, and we were the only team to have our paper accepted for the GHTC conference. Our project exceeded expectations in both scope and completeness, earning us second place in the final evaluation among all sponsored projects in our department. Reflecting on this journey, I am proud of my relentless learning ability and my "Make it happen" mindset, which drove me to seek external help and expand my knowledge, successfully navigating the entire product development lifecycle. This experience also deepened my appreciation for how AI can significantly empower designers and engineers.
  
Project Limitations and Future Directions
Honestly, when we tested the third-generation prototype in the field, it didn’t perform as well as we had anticipated. Several factors contributed to this outcome. First, due to budget constraints, the IR sensors we used lacked precision. Reducing the monitoring frequency to meet energy consumption requirements further decreased sensor sensitivity, leading to some inaccuracies (as detailed in Experiment 3 of our paper). Second, material limitations meant that our prototype did not adequately address waterproofing, wind resistance, and high-temperature endurance. Third, the cost of the third-generation prototype was around $200 per unit, which needs to be reduced. Fortunately, by switching to a cheaper motorized Pi camera and a lighter microprocessor, we could potentially lower costs by nearly 50%. Despite these challenges, our project explored innovative solutions that were highly original. In an era dominated by Machine Learning models and LLMs, our decision to use a combination of DSP and computer vision, which are more cost-effective and user-friendly, was validated by the GHTC committee’s recognition. This project has laid a solid foundation for future iterations and improvements.
Future Plan
  
Enhancing Device Structure
Improve the physical design of the devices to ensure they are more robust and better suited for the challenging environments of large-scale farming.
  
Optimizing Front-End and Back-End Code
Refine the software architecture, enhancing both performance and cybersecurity measures to protect sensitive agricultural data.
  
Upgrading Material Quality
Prototype with more durable materials that can withstand the varied and often harsh conditions found in agricultural settings, ensuring consistent and reliable operation.