Working of KDE

PG Officer App

User: PG Officer or CRP to capture data for a farmer group (~25 members)

Goal: Streamline data capturing mechanism

Data field : Fields Captured are given below

  • About Farmer

    • Name, Phone Number and Gender

    • Crops Grown and area under cultivation

  • About Input Demand

    • Seeds e.g. Maize, Ladyfinger

    • Plant Nutrition e.g. Urea, DAP

    • Plant Protection e.g. Neam oil

    • Equipment e.g. Conoweeder

    • Quantity

  • About Output Supply

    • Crop and it’s expected harvest period

    • Quantity for self consumption

    • Quantity for sale to FPO

    • Quantity for other commitments

Data mentioned above can be captured in offline as well as online mode and it get automatically synced with the system in presence of internet. The collected data reflects on the FPO dashboard as shown below.

 

FPO Dashboard

User: CEO of the FPO

Goal: Data aggregation and analytics to support procurement process and input-product inventory management

Features:

  • Provides overall top level summary

  • Group wise consolidated results of the captured data

  • Information of farmers and their specific data for each crop

  • Download reports to detailed analysis

 

Buyer Interface

User: Institutional buyers and End consumers

Goal: To increase visibility of the FPO and provide easy access to the customers to connect with FPO and place orders directly.

Features:

  • Lightweight Content Management System for easy updates

  • Digital catalog to easily engage B2B and B2C buyers

  • Payment integration available

  • Streamlined discovery for buyers

  • Buyer transparency to FPO products and production process

  • Reach to a wider market

 

 

 

 

 

 

 

 

The working of the complete system could be experienced in this short video: https://www.loom.com/share/270d3e49f5ca4054a6e1bbf9bc9c34f6

Related pages