Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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 shown in Table 1.0 below

About Farmer

About Input Demand

About Output Supply

Name

Seeds e.g. Maize, Ladyfinger

Crop

Phone Number

Plant Nutrition e.g. Urea, DAP

Quantity for self consumption

Gender

Plant Protection e.g. Neam oil

Quantity for sale to FPO

Crops grown

Equipment e.g. Conoweeder

Quantity for other commitments

Land area under cultivation for each crop

Quantity

Expected harvest date

Table 1.0: Data fields in PG officer app

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

  • No labels