How does this project fit into your broader strategy?IDSA focuses on data sovereignty/ ownership. FarmStack wants to build software on top of the trusted connector and make use of the technology in the agriculture sector enabling farmers to control their data. This aligns with the government policies as well as DG’s broader vision. | TeamProject owner: Vineet Singh Team members: Razak K M Gerd Brost (Unlicensed) Michael Lux (Unlicensed) | Status
|
Problem Space |
...
Why are we doing this?
Problem statement:How we may enable farmers to assert control on their data? |
...
Farmers, specially small holder |
...
have to make multiple decisions that affects their livelihood directly. With agriculture tech ecosystem getting more focus, the importance of data is increasingly becoming important in aiding the decision making process. The data typically involves sensitive information and also transaction information which can’t be shared without consent from the farmers. Impact of this problem:Sharing this information unlocks potential of new services for the farmers as well as ecosystem actors as they can bundle services together leading to better experience of the farmers. |
How do we judge success? |
...
|
...
|
What are possible solutions?There are two broad ways to solve this problem:
|
...
|
Validation |
|---|
...
Ready to make it
...
What are we doing?
...
We have two use cases running in India. One in the state of Bihar and another in the state of Andhra Pradesh.
In use case 1, Digital Green provides coaching to farmers on climate smart practice. Digital Green already maintains database of farmers, the practices they have adopted and the crops they have grown. While showing the videos, the field worker gets the consent from the farmers to share their activity and field details to certifiers and buyers. If the farmers give the consent, the data is made visible.
In use case 2, Digital Green right now is operating the certification shops for chilli farmers where the produce grade is quantified and they get customised advisory to improve the quality and also to connect to the buyers who can give better price. In future this is to be operated by government owned shops where the details of the grade will be shared based on the consent of the farmers.
...
Why will a customer want this?
...
Use case 1:
Farmers don’t want to share details about their field size etc
Buyers need the outcome - a score of how their activity has impacted environment and not the field size and entire details so that they can offer prices to manage carbon credits
Government who is maintaining this data with digital green wants to impose necessary restrictions so that farmers data is
Use case 2:
Farmers who get lower grade may not want to share the data to the buyers as it gets lower price but they may want to share the details with an advisory service to know how they can improve their grades
The grade of the produce by the farmers is a sensitive information that needs to be managed by the government and they want necessary restrictions to be placed
...
Visualize the solution
...
Use case 1
The data of the farmers about their farm and farming activity (including history) is shared through trusted connector which runs the application to give the output of Greenhouse gas emission score against the farmer
The score of the farmers can be shared to a match making platform where buyers can contact farmers with good score
Consent manager is like a service that can be embedded in any application (like a payment service)
while showing videos to the farmers on benefits of climate smart practice, the field worker can mention interest.
While the data about the farmers who have seen video is entered, the consent manager asks for consent (using SMS/IVR + application) from farmers if they want to share their information to share their score to interested buyers.
The information shared for calculating score and shared to the buyers is told. Consent manager will have some interface to inform and educate farmers.
If the farmers give consent, a token is generate that defines the consent to share data to be used by an application.
The receipt of token triggers data sharing through the connector with a usage policy that allows processing data by the scoring application and if there is a valid token.
Use case 2
When the farmers get their produce verified they give consent to share what parameters they want to share for receiving advisory services to improve their quality and get better price.
The data for the farmers giving consent is shared through a connector that restricts usage of data by match making application, that is, matches content provider and buyer to the farmers and sends them a notification
...
Scale and effort
...
Use case 1:
Scale: currently in very initial scoping phase
Effort: high
Use case 2:
...
Scale: pilot done with 2000 farmers
...
Policy level signals/ insights:
|
...
What do we need to answer?
...
How does consent relate to usage policies? Right now, the consent typically involves sharing data and once data is shared it is lost. On the other hand usage policies restrict the use of data while sharing.
Come up with a use case that demonstrates the consent driven usage policies. Define clear value add for the farmers and orgs who want to use this.
Do farmers want it?
|
Further questions
|
Further reading
Additional resources
Depa book:
| View file | ||
|---|---|---|
|
...
Detail presentation of use case here:
...