Any testbed should be made available to the FIESTA-IoT consortium and to future external experimenters (either through subsequent (funded) open calls or (non‑funded) open access use of the extended FIESTA-IoT testbeds and software platforms), under the terms and conditions stipulated in the contract template for Extensions. Independent evaluations of the submitted proposals will be performed, in order to select the experiments that will be supported by the project. It is required that the extensions are performed by a single organization.

Integration of the new testbeds should be accomplished in maximum 6 months. Per proposal a budget can be made available up to a maximum of 50 k€ per extension.

Join Process

According to what has been described in section 3, extension providers will have to go over the following processes:

• Testbed registration. When any testbed wants to become part of the FIESTA-IoT federation, it MUST be first registered into the platform. Adequate registration interfaces are put in place through the FIESTA-IoT Portal.
• Registration of testbed’s resources. As long as a testbed wants to inject information (i.e. observations) coming from its different underlying resources, it MUST register them beforehand, thus allowing the platform to have a prior knowledge about the different elements that are actually catering with data. To do so, a semantically annotated description, compliant with the FIESTA-IoT ontology, has to be provided to the FIESTA-IoT platform. Testbed providers can decide whether they provide their resources description already annotated or make use of any of the existing available annotators. In this latter case, they will have to comply with the input format (not-semantic) required by each annotator.
• Management/Update of testbed’s resources: The initial description of a resource is prone to vary throughout its lifetime. For example, its legacy testbed provider may add/remove sensors at any time. Upon such dynamics occur, testbed providers have to keep their testbeds’ resources descriptions up to date.
• Implementation of testbed provider interfaces: In order to enable access to the observations and data provided by their testbeds’ resources each testbed provider has to implement the corresponding TPI interfaces (see section 3). Depending on the nature and internal behaviour (if it only supports request-response or subscription-based access to data) of the testbed it is possible that only a subset of the TPI interfaces at testbed level shall be implemented.

Benefits to Testbed

• Boost the sharing, reuse and repurposing of IoT facilities at an EU and global scale. FIESTA-IoT will showcase and validate this concept in the scope of enterprise applications/experiments, smart city applications/experiments and more.
• FIESTA‑IoT project will provide a global market confidence programme for extending the pool of interoperable facilities and testbeds that will comply with the project interoperability model.
• A range of best practices facilitating IoT platform providers and testbed owners/administrators to integrate their platform/testbed within FIESTA‑IoT
• The simplified application process compared to the one from the standard H2020 calls together with a rapid review process by independent external evaluators;
• An extra benefit is the dedicated support from skilled FIESTA-IoT members. This will include their general training on IoT interoperability in general and in FIESTA‑IoT interoperability in particular, targeted consulting services associated with the interoperability of their platforms/testbeds, as well as continuous support in their efforts to use the FIESTA‑IoT results/tools towards improving the level of interoperability of their systems and applications.