Data wallet use case

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Status	In progress
Impact	High
Driver	@Vineet Singh @Ashu Sikri (Unlicensed)
Approver	@rikin (Unlicensed)
Contributors	@Lokesh Garg (Unlicensed)
Informed	@saureen (Unlicensed) @Razak K M
Due date	May 11, 2021
Outcome

Background

Data wallet that can help farmers to control their data is a natural fit for DG with initiatives like MRV, KD enterprise, video extension and FarmStack.

Brainstorming of ideas associated with data wallet can be found here.

Relevant information

Options considered

	Option 1: KDE	Option 2: MRV	Option 3: AgNext	Option 4: KDE + CoCo	Option 5: Fasal

	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	Low	Large	large	medium	large
Ratings top three (A:Ashu, V: Vineet)	A: 1 V: 2	A: 3 V: 3	A: 2	V: 1

Action items

Feedback from @ashok and @Ashu Sikri (Unlicensed) on the feasibility of option 4

Dashboard created by DG which is giving details by VRP/ Video dissemination (form extension department): district, village, FPO, Average yield, crops, # farmers below average, action

optional: district, village, FPO, farmer, yield, request (about input/ improving yield),

can see farmer details who are below the average and contact them.

If we have CoCo data of that farmer, we can probably show that somehow (not initially).

Value prop/ user journey

Outcomes:

some significant percentage of farmers give consent that I want to get contacted for XYZ thing (input, market, disease management) and want to share the data for same
X number of new farmers got contacted by VRP
Out of X, Y% found the video or the advisory info relevant and what they wanted
Overall A farmers with B % who have found this useful

Fallback:

We go back on option 1 - covered in the effort

Process/ User journey:

UI/ UX part
1. basic wireframe will help
informed consent works
technical stuff - OTP, validating etc
Roll out and process

Follow up with @Lokesh Garg (Unlicensed)@Ashu Sikri (Unlicensed)@Vineet Singh

Feasibility:

Where?
1. VRPs to be mobilised
  1. Bihar: Jeevika has good cadre
  2. Odisha: CRPs good
2. FPOs have shown some interest - there is a resource institution attached
  1. Bihar - good FPOs
  2. AP: not sure
  3. Odisha: CYSD - good cadre
When?
1. Crops/ season:
  1. Bihar: Paddy/ Litchi: June/July
  3. Pulses/ millets: October
Who are the stakeholders we should speak to?
1. Program alignment
  1. Bihar - Jeevika
  2. Odisha - already interest from Nabard