Open Calls FAQ
Vicinity Open Calls Frequently Asked Questions :
The size of required test scenarios depends on the complexity of the integrated infrastructures and the nature of the application (e.g. specific non-functional requirements). Also, it is important - independent on the size - that integrated infrastructure elements in the end have impact on the VICINITY platforms such as enabling new services, but also by addressing a broader and larger public.
Yes, it is possible to perform tests in a laboratory.
No, you do not have to connect the test scenario with an existing one. This is open. The existing uses cases are: Buildings and Smart Transport, Neighbourhood Smart Parking Assisted Living , Smart Energy and buildings, eHealth and Smart Building. However, possible connections might improve impact. For further information visit http://vicinity2020.eu/vicinity/content/pilot-use-cases
As maximum 4 proposals will receive funding. Proposals will be evaluated as submitted by reviewers and a panel according to the criteria mentioned in the call.
There is not YET a V2V use cases, but smart transport. Use cases proposed in the Open call are not constrained or limited to existing ones. This is open.
There is no constraint on the size of the infrastructure. Devices does not need to be commercialized, however their potential for commercialization and their maturity might have impact for VICINITY and other evaluation criteria.
Both options are elegible, VICINITIY will evaluate the compliance with the evaluation criteria; one of them is the impact on the VICINITY platform.
We are allow several options after the project life to guarantee the sustainabilty (Open community, education platform, etc.). The proposal might explain how sustainable impact of the action is achieved.
The next Open call will address value added services.
All kind of communication channels are accepted as long as the project implements an adapter to VICINITY. We already have several adapters that cover such low-level protocols.
In VICINITY project we address interoperability via adapters. We have in the backlog to provide the example of a FIWARE adapter.
The second call is to be described in summer. It addresses services on the VICINITY platform, taking profit of the platform and connected infrastructures.
VICINITY Nodes like many IoT nodes does not need to have permanent connectivity to platform. When a VICINITY Node is not connected its services is not available in peer-to-peer network.
Indirect costs should be included in the budget, you should take into account that the whole amount required should not exceed 60,000.00 Euros. To calculate indirect cost Horizon 2020’s rules apply “In all cases indirect costs will be covered by a flat rate of 25% of the direct costs”
You should demonstrate that you are involving external stakeholders in your proposal. You should show in which activities these stakeholders will be involved. You should explain how these external stakeholder are reinforcing your proposal and how they are participating in it. Also, it is expected co-creation activities with VICINITY partners.
It is not necessary to provide a value added service. We are interested in demonstrating interoperability capacity of Vicinity and integrate various infrastructures.
The meeting will be held in an European City, the date and the place is not closed yet. Aarhus in Denmark has been proposed but it is not closed yet.
You should demonstrate the impact of your proposal on VICINITY, note that you should demonstrate Long-term impact, then you explain what mechanisms are you using to obtain these impact. So, you should evaluate if you will obtain more impact with a single use case or with several use cases. Cross-domain use cases are interesting for demonstration purposes. E.g. how it enables new value-added services, how it opens new communities for VICINITY.
In case your company is managing infrastructures or installs these infrastructures to third parties, but does not own them. A full consent and collaboration agreement with the third party should be provided.
In the proposal you should explain how will you implement these tasks in the future project ( if your proposal is selected)
The link with the template to use is
Organizations qualified and compliant with the rules of participation H2020 are encouraged to participate. We have used F6S as it has been used successfully for other IoT Epi Projects.
Only one entity per proposal will be admitted, so activities in co-operation with other organizations will not be considered eligible. Third parties are external organizations involved in the IoT infrastructure, as you have to demonstrate the impact of your proposal, third parties will be the organizations impacted by your proposal.
Yes, Personnel costs are eligible.
It should be explained how your proposal is going to facilitate new business models in VICINITY and how your proposal is going to expand VICINITY business capacity.
You have to explain in detail , how you are going to test your project results.
This is way of showing that your IoT infrastructure awakes the interest of third parties.
The first VICINITY call focuses on infrastructures integration and does not cover costs related to infrastructures acquisition. We anticipate that infrastructure network of sensors and other types of equipment should be already installed or available. We recommend that the proposed budget for equipment should not exceed the 5% of the total budget for the project.
Yes, VICINITY architecture support this approach. Your algorithm, data which you would like not to share within peer-to-peer are hidden behind the VICINITY Adapter which should be provided by you.
Direct cost only, i.e. costs of an employee (salary) or traveling expenses. No 3rd party costs or subcontracting.
Invoices are needed for e.g. traveling costs or proof of expenses for salaries, same as for all EC projects.