Page Comparison

Page Properties Reportlabelrequirementsanalytics-keyrequirementscqllabel = "requirements" and space = currentSpace ( )Goals

Farmstack should help organizations and individuals across the agriculture value chain to share data and realize more value, more here

Strategic fit

• DG is established partner in various state government’s agriculture programs in digital learning space involving video dissemination/ digital advisory

• Data sharing infrastructure augments and leverages on the existing efforts in digital advisory and fits with the mission

Assumptions

• Orgs don’t trust DG or any other org to host data

  • validated for orgs like ATA (counter: Coalition of Willing but limited to research)

• Orgs see value in data sharing for knowing more about farmers

  • signals that complete farmer profile not available with anyone including govt

• Current initiatives fail to provide necessary trust across ecosystem

  • signals of mistrust between departments within the ministry

Customer Development Process

• Customer interaction process

• Customer Interactions

User concerns - User requirement Matrix

Further Questions

1. Who owns Farmstack (p2p data exchange tool)?

   1. DG owns farmstack during bootstrapping phase and provides service for implementing farmstack (~2 years)

   2. Farmstack then maintained by MoA or other govt body with ability for people to own p2p data exchange tool

2. What policy based usage controls are required immediately (6 months)?

   1. Ability to prevent data to be downloaded

   2. Ability to expire data

   3. Use data for processing but not available for further use

   4. Ensure that data is being processed/consumed within the geographic limits

3. What level of user friendliness is required in defining usage policy?

   1. In near and mid term, we provide the service and encode it

   2. In future, suite of policies that can be selected as well as option to easily define usage policy for specific cases

4. What is the level of security?

   1. Entry point should be security by obscurity - have virtual environments

   2. Build security gradually with near complete system by the time FS is handed over (~ 2years)

5. Who are the power users?

   1. Those who are willing to participate in use cases and test out, eg - Shayashone

Overall Plan

• Track 1: Tech development focussed on priority a) p2p data exchange, b) policy based usage control and c) data discovery

• Track 2: Use case development with customers (focus on diversity in value chain, data patterns, applications that help farmers in some way)

• Track 3: Applications for use case (try to exit in the long run unless it adds value to FS)

• Track 4: Evangelization, RnD and collaboration related to backend

Not Doing

• Security centric design: Stick to security by obscurity as starting point and then see what else is required

• Compliance driven use case: Strict adherence to GDPR or such policy, let it be needs driven if the power user wants compliance as the top goal

• Application heavy use case: eg, a novel application that involves AI

• P2P Ag Data marketplace: Not now - let it evolve

• Improving data: eg, combining weather or soil data to give better estimate than individual sets of data - let such applications come into being