...
Option 1: KDE | Option 2: MRV | Option 3: AgNext | Option 4: KDE + CoCo | Option 5: Fasal | |||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | FPO uses aggregated data to negotiate w buyers | VRP gathers tracks practices and other indicators, and this is used to estimate GHG emissions | Agnext generates a quality assessment report, DG accesses the report and sends farmers advisories detailing how they can improve their grade | PG officer gathered data shared with VRP to improve production practices | Fasal IoT sensors gather a bunch of farm specific data and use it to deliver advisories | ||||||||||||||||||||||||||||||
Data Flow | Farmer → PG officer → FPO → Buyer (aggregated) | Farmer → VRP → DG → DNDC → DG → JEEViKA (in the form of an aggregated dashboard) | Farmer → AgNext → DG → Farmer | Farmer → PG officer → FPO → DG → VRP → farmer | Fasal (through IoT) → farmer → Third Party | ||||||||||||||||||||||||||||||
Pros and cons |
Low hanging fruit Value to farmers immediate and tangible
More like app permissions than data wallet Seems like a force fit |
Individual farmer’s data Multiple stakeholders and processing
Value prop to farmers not concrete today Added complexity |
Individual farmer’s data Already being piloted and interesting potential (advisory)
Who plays what role? Not concrete as of now Added complexity |
Individual farmer’s data Low hanging fruit as both systems in DG
Value prop to farmers not immediate and tangible No external party |
Individual farmer’s data Maybe the use case in place already
IoT streaming data is unchartered territory Value prop | ||||||||||||||||||||||||||||||
Estimated effort |
|
|
|
|
| ||||||||||||||||||||||||||||||
Ratings top three (A:Ashu, V: Vineet) | A: 1 V: 2 | A: 3 V: 3 | A: 2 | V: 1 |
Action items
- Feedback from ashok (Unlicensed) and Ashu Sikri (Unlicensed) on the feasibility of option 4
- Value prop/ user journey