Cloud Management Systems | New release

Pest & Disease Management System

Pest pressure you can see,
a pre-harvest interval you can calculate.

Traps count automatically, so you know first when pest numbers rise. The system works out what you applied and when you can harvest, and blocks you when it is too early.

The Pest & Disease Management System is a cloud system developed by YenProtek with technology transferred from a leading Taiwanese university. It connects fruit fly trap monitoring, field weather, plant doctor diagnosis and pesticide pre-harvest interval (PHI) management. If the PHI has not ended, the harvest entry is blocked.

  • Phone, tablet, computer
  • 6 interface languages
  • Dark mode
  • No installation
  • Real-time push notifications
Pest & Disease Management System monitoring overview screen (dark mode): farm-wide pest severity, trap catch by trap site, hotspot map and diagnosis cases
Monitoring overview screen on a phone (dark mode): farm-wide pest severity card and trap sites stacked in order
7-day baseline
Compare with your own past 7 days
Rising pest numbers are obvious at a glance
2collaborating roles
Farmer and plant doctor work in parallel
and talk within the same case
5trap sites
Four corners plus center (Z1–Z5)
Each site recorded and compared separately
6languages
Traditional Chinese, English, Japanese, Thai, Vietnamese and Malay
Each user picks their own

Why pest control in orchards is always a step behind

You find the pests when they arrive,
and worry about the spray after you apply it.

You only know pests are heavy when fruit drops

How the daily trap catch changes reveals rising pest numbers earlier than any single day's number. The system tallies it daily and compares it with the past 7-day baseline.

Can this pesticide be used on this crop?

The system checks the crop and target pest against the pesticide's registered use range. If they are outside the range, it warns you first, and then you decide whether to log the application.

When can I harvest?

You would have to look up and calculate the pre-harvest interval yourself. The system calculates the earliest harvest date from the pesticide use record, and harvest cannot be logged before then.

Function

Pest numbers, pesticide use and harvest, tracked in one system

Trap counts upload automatically, reports and diagnosis run in the same case, and pesticide use is checked against registration data. The pre-harvest interval is calculated and enforced.

Trap monitoring overview

Trap catch from each trap site uploads automatically. Farm-wide pest severity is read as "flies per trap per day (FTD)" and the size of the increase is compared with the past 7-day baseline. Lure age and replacement deadlines and node status are on the same page.

  • Grading uses the farm-wide average FTD, not the cumulative total count
  • Hotspot map: upload a site layout map and the dot size shows trap catch, so you can see which direction the pests come from
  • Field weather: air temperature and humidity, soil temperature, moisture, EC and light on one page; a prompt appears when temperature and humidity stay in the favorable range for outbreaks
  • Expired lures, abnormal single-time increases and counter resets are flagged automatically

Reports and diagnosis

Farmers report with a phone photo. The photo's GPS fills in the location automatically, and the system attaches that day's weather summary. A plant doctor accepts the case, schedules a field visit and issues the diagnosis report. After the case is closed, it can no longer be edited.

  • Case status: reported, accepted, diagnosed, closed
  • Cases not accepted, or accepted but not diagnosed, escalate with reminders when overdue
  • Recommended materials in the diagnosis report can be pulled from the pesticide master file, with amount and dilution ratio

Trends and history

Daily FTD bars with the past 7-day baseline; the dates of lure changes and equipment changes are marked on the chart, so values before and after are not compared by mistake. The farm-wide daily summary, daily tables by trap site and events can be downloaded as CSV.

Materials and pre-harvest interval

Scan the barcode on the bottle to look up the registration number, active ingredient, registered use range and PHI. When you log an application, the crop, target pest, application interval and number of applications are checked, and the earliest harvest date is calculated.

Live video

Live view from orchard cameras, available right after login. When there is no signal, the last frame is shown.

Events and alerts

Node offline, abnormal counts, expired lures, favorable outbreak conditions, overdue cases and unregistered use all open events, graded as notice, warning or critical, with a handling method you can record. Thresholds have global defaults, and each site can override them.

How It Works

From trap counts to alerts on your phone

Trap sites upload cumulative trap catch to the cloud, which is tallied daily into flies per trap per day (FTD), compared with the past 7-day baseline, graded and pushed to the screen.

  1. Trap counting Cumulative trap catch from each trap site uploads automatically, and an abnormal single-time increase is marked as suspect
  2. Daily FTD summary Flies per trap per day is tallied daily, and the farm-wide average is calculated
  3. Versus past 7-day baseline Compared with the median of your own past 7 days to see the size of the increase
  4. Grading Three levels: notice, warning, critical; thresholds are calibrated for the site, season and crop
  5. Notification The screen updates in real time and opens an event, which is marked as handled when resolved

Trap catch is an index of male fly density, so read the trend rather than a single point. Values after a lure change or equipment change are not compared directly with earlier values.

Trap site layout

Four corners plus the center,
each site viewed separately

The basic site setup uses five trap sites: four corners and the center (Z1 to Z5). Trap catch is recorded separately for each site and compared with the baseline separately. Together with the hotspot map, you can see which direction the pests come from.

Trap site layout schematic: four corners plus center (Z1–Z5)

System Screens

The screens you open every day

Monitoring overview

Monitoring overview screen: farm-wide pest severity, trap catch cards for each trap site, hotspot map and weather station summary

Actual system screen; data is sample data for demonstration

As soon as you open it, you see farm-wide pest severity, the trap catch of each trap site and its rate of change against the baseline. The hotspot map, weather station summary and diagnosis cases are on the same page.

  • Lure age and replacement deadline shown directly
  • Node connection status and signal strength
  • Switch between multiple sites in one click

Diagnosis cases

Diagnosis case screen: case progress bar, report details and diagnosis report

Actual system screen; data is sample data for demonstration

A progress bar runs from reported, accepted and diagnosed to closed. Report details, site photos, weather summary, field visit booking and the diagnosis report are all on one page, with a verification hash attached after closing.

  • Report details and photos, with the weather summary filled in automatically
  • Diagnosis report: pest or disease name, diagnosis, recommended control measures and materials
  • No edits after closing; the hash can be checked by third parties

Material use records

Material use record screen: pesticide use table, with the earliest harvest date and match result for each entry

Actual system screen; data is sample data for demonstration

Each application entry records the crop, target pest, material, amount and application method. The system checks the registered use range and calculates the earliest harvest date, and entries outside the range are flagged.

  • Earliest harvest date listed right on the record
  • Use outside the registered range is flagged and the plant doctor is notified
  • Material categories include biological control materials

Harvest entries

Harvest entry screen: a notice that the PHI has not ended, showing no harvest is allowed before a given date

Actual system screen; data is sample data for demonstration

Log the harvest date, quantity and destination. If the PHI has not ended, the screen tells you before which date you cannot harvest, and submission is blocked.

  • Shows the earliest harvest date and the reason for the block
  • No role can override it
  • Pesticides with no PHI on record are blocked using a conservative number of days

Pre-harvest interval (PHI)

The system works out when you can harvest, and blocks you before then

When you log a pesticide application, the system checks the pesticide registration data for the PHI of this pesticide on this crop and calculates the earliest harvest date. Harvest entries before that date are blocked, and no role can override it.

  1. Outside the registered range: confirm again first

    If the crop or target pest is not in the pesticide's registered use range, you must confirm again before submitting. Your confirmation is recorded and the plant doctor is notified.

  2. Intervals and counts: the system reminds you

    If the application interval is too short or the registered number of applications is exceeded, you are warned right when you log it.

  3. Revoked pesticides may not be used

    Pesticides whose registration has been revoked are marked in the master file, and you cannot log an application with them.

  1. Application date Log which crop and which target pest this pesticide was used on, and the system pulls up its PHI in days
  2. Harvest entry blocked Plus PHI days Harvest entries during this period are blocked, and the screen shows before which date harvest is not allowed; no role can override it
  3. Earliest harvest date From this date you can log the harvest date, quantity and destination

When the PHI cannot be found in the pesticide master file, the system does not let it through. It blocks harvest using the conservative number of days set by the administrator. This website does not list the days for any pesticide; the pesticide registration data is the reference.

Roles and workflow

Farmers and plant doctors
talk within the same case.

Accounts are created by administrators; self-registration is not available. Plant doctors and farmers are parallel roles, and farmers only see the sites they have joined.

  1. Farmer Report with a photo

    Attach at least one site photo and describe the damage. The photo's GPS fills in the location automatically, and the system attaches the weather summary for the report date.

  2. Plant doctor Accept and assign

    Accept the case after being notified; administrators can also assign a plant doctor from the queue of pending cases. Cases not accepted in time escalate with reminders.

  3. Farmer Confirm the visit time

    The plant doctor proposes visit time slots, and the farmer confirms to schedule the visit. Unconfirmed bookings are flagged.

  4. Plant doctor Issue the diagnosis report

    Pest or disease name, diagnosis, recommended control measures and recommended materials (which can be pulled from the pesticide master file), amount and dilution ratio.

  5. Plant doctor Close and lock

    After closing, the entire case (including photos and notes) can no longer be edited, and the content hash can be checked by third parties. If a follow-up diagnosis is needed, open a new case.

Administrator

  • Create sites, register nodes and trap sites
  • Create accounts, add members, assign plant doctors
  • Set lure cycles, thresholds and case deadlines

Plant doctor

  • Accept reports, schedule field visits, issue diagnosis reports
  • Automatically gets read access to the site after accepting a case
  • Receives confirmation notices for off-label pesticide use

Farmer

  • Report with photos, confirm visit times
  • Log pesticide use and harvests
  • Only sees the sites they have joined

Viewer

  • View the monitoring overview and trends
  • View events and cases
  • Cannot edit any data

Getting started

Four steps to get started

  1. Create a site

    Orchard name, main crops, area and map coordinates. Upload a layout map or orthophoto to give the hotspot map a base map.

  2. Register trap sites and weather nodes

    The administrator registers nodes first; only then do trap sites and weather stations start uploading data.

  3. Add members and assign plant doctors

    Farmers join the site and the cooperating plant doctor is designated; each person logs in in their own language.

  4. Set lure cycles and thresholds

    Calibrate trap thresholds and lure replacement cycles for the crop and season, then check trends daily, report with photos, and log pesticide use and harvests.

Platform

Works on your phone, in each user's own language

Works on phones, tablets and computers

Just open it in a browser; no installation needed. You can also add it to your phone's home screen and open it like an app.

Six interface languages

Each user chooses their own interface language.

  • 繁體中文
  • English
  • 日本語
  • ไทย
  • Tiếng Việt
  • Bahasa Melayu

Dark mode

It follows the device setting or can be switched manually, so the screen is easy on the eyes on night rounds.

Permissions by role

Each role can view and edit a different scope. Accounts are created by administrators and self-registration is not available. When someone leaves or is replaced, the account is deactivated.

Screens update in real time

Sensor data and events are pushed to the screen with no need to refresh. Connection status is always visible, and disconnections are flagged.

Every change is logged

Every change to thresholds and important data is recorded, so there is a basis for audits.

Compatible Hardware

Sensing and control with YenProtek's own hardware

The field weather station, trap counters and cameras are all YenProtek's own products.

YenProtek trap counters and cameras

Traps count catches automatically and upload the data, and cameras provide live field video. Traps are placed at the four corners plus the center.

Frequently Asked Questions

What can the Pest & Disease Management System do?

Four things: pest monitoring, where traps count automatically and results are compared with the past 7-day baseline; field weather with prompts for conditions that favor outbreaks; a case workflow for farmer photo reports and plant doctor diagnosis; and pesticide use records checked against registered use ranges, with harvests blocked until the PHI ends.

Does the number of flies in the traps equal the number of fruit flies in the orchard?

No. Trap catch reflects male fly density and is used to read trends. The system compares the average number of flies per trap per day with the past 7-day baseline, and the size of the increase matters more than a single day's number. Values after a lure change or equipment change cannot be compared directly with earlier values, and the system marks these on the chart.

What is FTD (flies per trap per day)?

FTD is the average number of flies caught per trap per day. The system grades pest severity (notice, warning, critical) by the farm-wide average FTD rather than the cumulative total count. Thresholds are calibrated by a plant doctor for the site, season and crop.

What hardware do I need?

Field weather is measured by FarmerPack, and the trap counters and cameras are YenProtek's own products. Traps are placed at the four corners plus the center, and the number of traps is planned according to orchard size.

What is the pre-harvest interval (PHI)? How does the system calculate it?

The pre-harvest interval (PHI) is the number of days to wait between the last pesticide application and harvest, set for each crop based on pesticide registration data. The system adds this number of days to the application date to get the earliest harvest date, and harvest entries before that date are blocked. For pesticides whose PHI cannot be found, harvest is blocked using a conservative number of days.

What happens if a pesticide is used outside its registered range?

The system flags it as "outside registered use range," and you must confirm again before submitting. After confirmation, your confirmation is recorded and the plant doctor is notified. The system records what has already happened but does not encourage off-label use.

Can an administrator override the pre-harvest interval?

No. Until the PHI ends, no role can log a harvest, administrators included. For pesticides whose PHI cannot be found, harvest is also blocked using a conservative number of days.

Can diagnosis records be altered?

Once a case is closed, the entire case, including photos and notes, can no longer be edited, and a content hash is provided so you can verify it has not been altered. If a follow-up diagnosis is needed, open a new case.

Do I need to install an app?

No. Just open it in a browser. You can also add it to your phone's home screen and open it like an app. On a phone, you can take photos to report and scan pesticide barcodes directly.

Can it be used outside Taiwan?

Yes. The interface is available in six languages: Traditional Chinese, English, Japanese, Thai, Vietnamese and Malay. Trap monitoring, field weather and the report-and-diagnosis workflow work anywhere. The pesticide database currently supports Taiwan registration data; other markets need localization, so please contact us first.

Can I see an online demo first?

Yes, you can book an online demo. We will walk you through every screen using a demo system (the demo data is fictional sample data). Tell us about your crops, the number of orchards and your trap layout, and we will look at suitable settings together.

Tell us about your orchard and crops,
and we will help plan trap sites and rollout.

Start by going through every screen in the demo system, then decide together how to lay out the trap sites and who needs to join.