Federated Interoperable Semantic

IoT/cloud Testbeds and Applications

Open Call 1
First FIESTA-IoT Competitive Call for Experiments and Extensions
Full title of your proposal
Acronym of your proposal (optional)
Call / category (for Experiments only) / Experiments or Extensions / Scientific
Identifier Excelence or Innovation by SME /
FIESTA-IoT-OC1-EXP-EXC or
FIESTA-IoT-OC1-EXP-SME or
FIESTA-IoT-OC1-EXT
Date of preparation of your proposal mm/dd/yyyy
Your organization name Your organization name
Name of the coordinating person Name of the coordinating person
Coordinator telephone number Coordinator telephone number
Coordinator e-mail address: Coordinator e-mail
[This is the email address to which the
Acknowledgment of receipt will be sent]

Note: Grey highlighted areas needs to be filled and/or removed as they are intended to
provide clarification on the expected content. Word template can be downloaded from
FIESTA-IoT project website (see http://fiesta-iot.eu/opencall/)
Section A Project Summary
(Maximum 300 words)

Summary of the proposed work

Remark: The information in this section may be used in public documents and reports by the
FIESTA-IoT consortium.

Section B Detailed description and expected results

(minimum 4 to maximum 8 pages)

This section describes the details on the planned experiment or extension: what does the
proposer hope to obtain, how, why is it relevant? This section should also include all information
with respect to the State-of-the-Art or a comparison to competing commercial applications and
services in case of experiments of category ‘Innovation by SME’ to show the innovative character
of the experiment, and the expected scientific or business impact.

B.1 Concept and objectives

Describe the specific objectives of the proposed experiment or extension, which should be clear,
measurable, realistic and achievable within the duration of the experiment or extension (not
through subsequent development). Show how they relate to the topic(s) addressed in the scope
of this competitive call and how and why FIESTA-IoT meta-platform is needed for realizing them.
Describe and explain the overall concept that forms the basis for your experiment or extension.
Describe the main ideas, models or assumptions involved.

B.2 Impact
For experiments of category ‘’Scientific Excellence”: Describe how this experiment fits in your
internal research roadmap, and to which extent the broader research community can benefit
from the results of the experiment.

For experiments of category ‘’Innovation by SME”: Describe how this experiment fits in your
activities, and how this experiment may strengthen the competitiveness of your business and the
growth of your company. Having close contacts with possible end-users during this experimental
phase might be used to illustrate the business impact of the experiment.

For extensions: Describe the potential that the extension will be used by future FIESTA-IoT
experimenters from the broader scientific community as well as developers from industry, in
particular individuals and SMEs, in subsequent (funded) FIESTA-IoT open calls or by (non-funded)
open access of FIESTA-IoT federated testbeds. Proposers should show the amplitude (number
and variety) of the testbed IoT resources, their nature (i.e. real or virtual resources), the testbed
availability and the accessibility to the testbed resources for FIESTA-IoT users during the whole
project duration and beyond.

For any experiment or extension: Show that the proposed experiment or extension has sufficient
sustainable benefits for the FIESTA-IoT project, meaning that there should be an added value for
the FIESTA-IoT project, after the proposer has finished his experiment or extension.
B.3 Description of the State-of-the-Art
For experiments of category ‘’Scientific Excellence”: Describe the advances the proposed
experiment would provide beyond the state-of-the-art, and the extent the experiment is
ambitious. Is this experiment expected to lead to ground-breaking results or rather incremental
results compared to existing work?

For experiments of category ‘’Innovation by SME”: Describe in detail how the proposed solution
compares with existing solutions in the field covered by the experiment. Are there similar
experiments, products, services, etc. on the market? Is this experiment incremental to existing
work?

For extensions: Describe how the testbed has been already useful to support experimentation
and how the domain of interest enabled by the testbed is currently mobilizing the scientific and
innovation communities.

B.4 Methodology and associated Work Plan

Provide a work plan. Provide clear goals and verifiable results, and also a clear timing.

The work plan involves at least the following phases:

1. Design of experiment or extension

2. Executing the experiment, or integration of the testbed
3. Analysis & feedback
 Analysis of the results of the experiment or testbed integration process
 Feedback on user experience
 Recommendations for improvements and/or future extensions of
FIESTA-IoT meta-platform and testbeds
4. Showcase: Set up of a showcase (demonstration) to be used for the evaluation
of the experiment or extension at the review meeting with the EC, and for further
promotion of FIESTA-IoT
5. Dissemination: Regular dissemination actions (journal publications,
conferences, workshops, exhibitions, FIRE events, advertising of results at
FIESTA-IoT website, etc.)
6. Final report, code and documentation
Section C Requested FIESTA-IoT testbeds, resources and/or datasets or
data-streams
(target length 1 page - fill the tables below)

For experimenters: Please visit the following websites to get details on the specific testbeds,
datasets and data-streams, and services available

 http://fiesta-iot.eu/fiesta-testbeds/
 http://fiesta-iot.eu/fiesta-services/

TESTBEDS Required (Yes/No)

SmartSantander
SmartICS
Comm4Innov
KETI

DATASET / DATA-STREAM HISTORICAL or CURRENT FREQUENCY

Identify the phenomena your
are interested in. (One per
row)
Identify the phenomena your
are interested in. (One per
row)
… …
VALUE
Do you require access to How often will you require
bunch of values in a given data from FIESTA-IoT?
time or just access to the
value at the moment of the
request?
Do you require access to How often will you require
bunch of values in a given data from FIESTA-IoT?
time or just access to the
value at the moment of the
request?
…

SERVICE / TOOL Required (Yes / No)

Experiment management tool
SPARQL endpoint (resources and observations)
Resource browser
REST access to datasets
Subscription-based access to data-streams

For extensions: this section should include a summary table of the resources that will be available
through it:

Domain Asset (physical phenomena, etc.)Resource Deployed devices

Type
Domain of Brief description of the physical Fixed Sensor / Number of
interest phenomena obtained by the sensing Mobile devices
devices Sensor /
Smartphone /
etc.
Section D Compliance check
The Open Call proposer needs to answer the scorecards available on the FIESTA-IoT Training Platform (http://moodle.fiesta-iot.eu/course/view.php?id=2).
Based on the answers, a feedback will be generated which should be included into the following tables.

If your proposal is for the FIESTA IoT OC1 EXT Category (i.e. new testbed), the questionnaires from the group “Scorecard for Extensions” must be answered; If
your proposal is for the FIESTA IoT OC1 EXP EXC or FIESTA IoT OC1 EXP SME Categories (i.e. experiment), the questionnaires from the group “Scorecard for
Experiments” must be answered. The proposer may delete the tables that do not apply to the proposal (actually the complete sub-section might be removed).

Each scorecard is divided into several questionnaires. The Scorecard for extensions is divided into 5 questionnaires, and the Scorecard for Experiments is divided
into 2. According to the combination of the answers given, an overall feedback (per questionnaire) is going to be generated which must be also included into
the corresponding table.

Please make sure you submit each set of answers, as only then, the feedback is automatically given. If help is needed, please refer to the “Scorecard
Instructions.pdf” available in the FIESTA-IoT Training Platform, or in case further assistance is needed, feel free to contact the FIESTA-IoT Open Call support
team, using the email address provided in the Training Platform front page.
1. Scorecards for Extensions feedback
This set of 5 tables need to be filled in case the proposal is for FIESTA IoT OC1 EXT Category
Testbed Data Models questionnaire
Name Feedback
Q1 - Does the testbed supports the SSN ontology?
Q2 - Does the testbed supports the FIESTA ontology?
Q3 - Does the testbed supports the IoT-lite ontology?
Q4 - Does the testbed supports other language to annotate data such
as SensorML, SWE?
Q5 - Does the testbed support a proprietary language to represent the
sensor data and/or sensor descriptions?
Q6 - Does the testbed provides the ability to extract data and/or sensor
descriptions in a document format (i.e. CSV, Excel, XML, RDF, JSON,
etc.)?
Q7 - Does the testbed store its data and/or sensor descriptions in a
Graph Database?
Q8 - Does the testbed store its data and/or sensor descriptions in a
Document Database?
Q9 - Does the testbed store its data and/or sensor descriptions in a
Relational Database?
Overall feedback
 Interfaces & Services questionnaire
Name Feedback
Q1 - Does the testbed offer a SPARQL (Graph DB) endpoint?
Q2 - Does the testbed offer an OMA Next Generation Service Interface?
Q3 - Does the testbed offer an Open Cloud Computing Interface?
Q4 - Does the testbed offer a Virtual Entity end point?
Q5 - Does the testbed offer a Relational DB endpoint?
Q6 - Does the testbed offer a document DB endpoint?
Q7 - Does the testbed offer Resource Discovery (filtered by location,
type, name, etc.)?
Q8 - Does the testbed offer direct access to sensors’ observations
through services (historical queries and/or event-based subscriptions)?
Q9 - Does the testbed offer access to sensors’ observations stored on a
database through services (historical queries)?
Q10 - Does the testbed offer actuation through offered services?
Overall feedback

Security questionnaire
Name Feedback
Q1 - Does the testbed offer secure encrypted communication channel
between all testbed interfaces and FIESTA Platform?
Q2 - Can the testbed trust FIESTA to identify and authenticate
experimenters on its behalf?
Q3 - Can the testbed determine who is using what features of the
testbed?
Q4 - Is the testbed able to specify access rights to specific resources?
Q5 - Can the testbed choose to perform local access control decisions
and enforcement?
Overall feedback
 Quality Auditing Aspects questionnaire
Name Feedback
Q1 - Do you control or set a threshold before which your testbed
must give a response to the received request?
Q2 - Do you control or set a threshold before which your testbed
must finish processing the request in the most complex case?
Q3 - Does your testbed implement any resource optimizing
mechanism?
Q4 - Does the Testbed support the execution of services with
different priorities?
Q5 - Do you define a ratio of failure time/working time that the
testbed must respect?
Overall feedback

Generic questionnaire
Name Feedback
Q1 - Does the testbed provide Documentation?
Q2 - Does the testbed provide development, deployment and
management tools?
Q3 - Can the testbed offer the ability to run third party software
(i.e. FIESTA adaptors)?
Q4 - Can the testbed replicate/annotate it’s current data to the
FIESTA format in a local Database?
Overall feedback
2. Scorecards for Experiments feedback
This set of 5 tables need to be filled in case the proposal is for the Open Call for extensions
Experiment Feasibility questionnaire
Name Feedback
Q1 - Does FIESTA-IoT currently provide all sensor data types need for
the experiment?
Q2 - Does the experiment need data from specific locations not
currently covered in FIESTA-IoT?
Q3 - Does the experiment needs to filter the data during
discovery/retrieve? Using which criteria?
Q4 - Does the experiment need external data to accomplish the goal?
Q5 - How will the experiment consume data?
Q6 - Does the experiment require third party tools?

Overall feedback

Experiment Feedback questionnaire

Name Feedback
Q1 - What tools do you need among the ones provided by FIESTA-IoT?
Q2 - How many FIESTA-IoT testbeds do you need to accomplish the
experiment?
Q3 - To what extend will the experiment use semantic data?
Q4 - Will the experiment generate new knowledge from the
requested data and provide it back to FIESTA-IoT knowledge base?
Overall feedback
Section E Background and qualifications
(maximum 2 pages)

This section describes the proposer and includes an overview of the activities, the proposer’s
qualifications, technical expertise and other information to allow the reviewers to judge the
proposer’s ability to carry out the experiment or in case of extensions, to carry out the federation
process, this is, implement the required interfaces and tools to make their testbeds complaint
with the FIESTA-IoT platform, as well as to support experimentation of subsequent (funded)
FIESTA IoT open calls or by (non funded) open access of FIESTA IoT federated testbeds.

Section F Expected feedback to the FIESTA-IoT Consortium

(maximum 2 pages)

This section contains valuable information for the FIESTA-IoT consortium and should indicate the
feedback that the FIESTA-IoT consortium can expect from the use of its software platforms
and/or testbeds after carrying out the experiment or extension. This information is essential in
view of the further improving the FIESTA-IoT software platforms, and the testbeds. Note that
providing this feedback is one of the key motivations for the existence of the FIESTA-IoT open
calls.
Section G Requested funding
(maximum 1 page)

This section provides an overview of the budgeted costs and the requested funding. A split is
made in personnel costs, other direct costs (travel, consumables, etc.) and indirect costs.

Besides the table below, extra information can be provided to support the requested funding and
which may help to judge the cost to the reviewers.

Please show your figures in euros (not thousands of euros).

Total PM Cost (€)

1. Direct Personnel costs
2. Other direct costs
3. Total direct costs (sum of row 1,2)
4. Indirect costs (25% of row 1+2)
5. Total costs (sum of row 3 and row 4)
6. Requested funding (up to 50.000 EUR)

In row 1, insert your personnel costs for the work involved.

In row 2, insert any other costs, for example equipment or travel costs. Please allocate sufficient
budget for participation at the final review meeting by the EC, and potential visit(s) to FIESTA-IoT
partners, in case this is required in view of advanced support by the Consortium.

In row 3, calculate the sum of your personnel and other costs.

In row 4, calculate the indirect costs that is 25% of the personnel costs (row 1) and other direct
costs (row 2). Indirect costs are all those eligible costs which cannot be identified by the
participant as being directly attributed to the project but which can be identified and justified
by its accounting system as being incurred in direct relationship with the eligible direct costs
attributed to the project. You should use a uniform 25% flat-rate of your eligible direct costs.

In row 5, calculate the total costs as sum of total direct and indirect costs.

In row 6, indicate the requested funding. You may request up to the total amount allowed by this
call for EC contribution for industrial experiments which is 50.000€.

The maximum funding which is allowed in this call is set at 50 000 € for an experiment of the
category ‘Scientific excellence’, 50 000 € for an experiment of the category ‘Innovation by SME’,
and 50 000 € for an extension.
Section H Use of proposal information
(maximum 1 page)

In this section the proposing party is asked to include some statements related to sharing
information of their proposal within the FIESTA-IoT consortium.

Proposals are treated in a confidential way, meaning that only successful proposals must be
disclosed to the FIESTA-IoT consortium. Open calls previously organized by other FIRE projects
were very successful and have revealed that many submitted non-granted proposals also contain
very interesting and valuable information that could be used for setting up collaborations or to
extract ideas for further improving the federated test infrastructures. Therefore the FIESTA-IoT
project would like to have the opportunity to collect more detailed information and further use
this information, also if the proposal is not selected for funding. In any case, the FIESTA-IoT
consortium will treat all information of a proposal confidentially.

Two types of information usage are envisaged:

 Information which is part of the Sections A, C, D and F will be used within the FIESTA-IoT
project as input for tasks related to testbed and software platform optimizations,
sustainability studies, etc. The same information can also be used in an anonymous way
to create statistics and reports about this first open call. All proposals submitted to this
competitive open call are obliged to allow this form of information access and usage.
 Other information belonging to this proposal might also be accessed by the FIESTA-IoT
consortium, if allowed by the corresponding proposer. Any use of such information will
be discussed and agreed upon with the proposers. Proposers have the freedom to select
if they wish to support this kind of information usage.

I allow that the material provided in Sections A, C, D and F

of this proposal may be accessed by the FIESTA-IoT
consortium, also if the proposal is not selected for funding.
In any case, the FIESTA-IoT consortium will treat all this
information confidentially. It will be used within the
Yes ☐
FIESTA-IoT project as input for tasks related to testbed and
software platform optimizations, sustainability studies,
etc. The same information can also be used in an
anonymous way to create statistics and reports about this
first open call.
Furthermore, I allow that the other parts of this proposal
may be accessed by the FIESTA-IoT consortium, also if the
proposal is not selected for funding. In any case, the
Yes ☐ No ☐
FIESTA-IoT consortium will treat all information of this
proposal confidentially. Any use of this information will be
discussed and agreed upon with the proposers.