Vendor Guidelines¶
Work in Progress
For demonstration purpose
General¶
- It is not allowed to use the HortiView platform to refer or to sell other services within modules.
Information provided for selling and promoting your modules e.g. in the module marketplace¶
- A module description in the HortiView Marketplace needs to be in English language even the application is targeting other countries and languages.
- Your module and module description should not include any reference, link or promotion of a foreign 3rd party software.
- Only accurate information about your module offering is accepted.
- Links to video platform...
Pricing¶
- If you publish a module on the HortiView marketplace you agree to the HortiView Customer Refund Policy
Vendor support and error management¶
- In case of errors or mistakes of the application the vendor is responsible for the support and solving the issue within an appropriate time frame.
- If the application is issued for free and without reliability this has to be clearly communicated to the user wihtin the marketplace. In this case the vendor decides on the service level.
Data Principles¶
In future we envision farmers to have an integrated approach to their farm generated data where the farmer is the owner of the data and where the data is managed and governed in his interest, even it is generated from multiple services. Having data managed and governed centrally enables all key players in the farm eco-system to access farm context data (master and transactional data) to deliver their services. HortiView is supposed to be the intermediate platform to enable farmers to collect, manage and govern farm data, easily share it with 3rd party solutions and make sure to receive data from 3rd party solutions as a basis for new services and analytics. The following data principles apply:
- The HortiView platform provides data driven services for an eco-system of farmers, foodchain and solution vendors
- The platform aims to overcome silo thinking in the industry and the enablement of data driven value creation beyond system barriers
- The farmer owns and controls the farm related master and transactional data.
- All parties on the platform are willing to standardize data models to easily exchange data and make use of the data in the eco-system
- All parties agree, that key farm data is to be persisted on the platform, so that farmers can continue using it independent of the related service
- The platform implements easy data sharing mechanisms which can be used by all parties
- The platform implements thorough measures to manage data access rights.
- All parties on the platform respect corresponding data related legal requirements e.g. the European Data Act, General Data Protection Regulation,…
Data Security¶
Consequences Breaching the terms¶
- Immediate consequences: Notfication of the vendor with information about the breaches. Changes will be reviewed and the module is revoked for publishment. If the vendor does not react the module and account can be temporary disabled.
- Ultimate consequences: Commissin is surpressed and the account could be closed.