Product requirements
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 and people don’t trust DG or any other org to host data
validated in discussion with different people and also reports of farmers mistrust
Orgs see value in data sharing for knowing more about farmers
signals that relevant farmer profile not available with anyone and it helps build better solution
Current initiatives fail to provide necessary trust across ecosystem
signals of mistrust with the initiatives that tend to be centrally orchestrated
Customer Development Process
User concerns - User requirement Matrix
User concerns | Possible answer - user requirement | Priority rating (1-5)
Total: (E+N)*I |
Trust
|
|
T: 24 |
Data security while handling data
|
|
T: 21 |
Incentive
|
|
T: 21 |
Data Policy
|
|
T: 21 |
Search data
|
|
T:14
|
Quality assurance
|
|
T: 14 |
Open Data but lot of effort spent in pre-processing data |
|
T: 5 |
Further Questions
Who owns FarmStack (p2p data exchange tool)?
FarmStack is operated by Stewards and participants based on the open source repository
DG owns FarmStack open source repository with community of participating members
What policy based usage controls are required immediately (6 months)?
Ability to prevent data to be downloaded
Ability to expire data
Use data for processing but not available for further use
Ensure that data is being processed/consumed within the geographic limits
What level of user friendliness is required in defining usage policy?
Suite of policies that can be selected as well as option to easily define usage policy for specific cases
What is the level of security?
Entry point should be security by obscurity - have virtual environments
Depending on the criticality of use cases, security can be addressed
Who are the power users?
Those who are willing to run the network
Those who are willing to manage the connectors
Overall Plan
Track 1: Tech development focussed on priority a) p2p connectors, 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: 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
Application heavy use case: eg, a novel application that involves AI
P2P Ag Data marketplace: FarmStack is not a marketplace
Improving data: FarmStack is not a tool for improving quality of data