FI-WARE 2nd Open Call


The FI-WARE project has reserved a portion of the project budget to fund specific tasks to be carried out by a new beneficiary or beneficiaries which will join the consortium after start of the project. These later-joining beneficiaries are selected by means of a series of competitive Open Calls.

Each FI-WARE Open Call is focused on a number of topics. Proposers will be selected for each topic, with one or more successful proposer in each.  Each topic refers to a set of functionalities to be supported by GEs to be integrated in the FI-WARE Platform. Proposals should address the definition of open and royalty-free specifications, as well as the development of a reference implementation, of new GEs in the FI-WARE Platform that will cover these functionalities.

The FI-WARE project follows an Agile process to implement its work plan. Aligned with this, the set of functionalities to be covered by proposers to each topic are described in the form of Epics.

Regarding the FI-WARE Second Open Call, the topics to be covered are:

  • Advanced Web-based User Interface GEs

Many of the existing FI-WARE GEs mostly target server functionality with little and no user interaction. Yet, to become widely visible and adopted by end users, the Future Internet must also offer much improved user experiences as direct and immediate results of the FI activities. A number of Epics have been defined that bring together necessary technologies to make this possible: The objective is to significantly improve the user experience for the Future Internet by adding new input and interaction capabilities, such as interactive 3D graphics, immersive interaction with the real and virtual world (Augmented Reality), virtualizing and thus separating the display from the (mobile) computing device for ubiquitous operations, and more.

The Web is quickly becoming THE user interface technology supported on essentially any (mobile) device while offering advanced rich media capabilities. First devices are now becoming available that use Web technology as the ONLY user interface technology. The Web design and programming environment is well-known to millions of developers that allow quick uptake of new technology, while offering a proven model for continuous and open innovation and improvement. As a result, the Epics linked to this topic build upon but significantly extends HTML as a user interface technology. It is envisioned that materialization of these Epics needs to be done in collaborations with the standardization bodies in this area.

(Click here to find the 1st consolidated draft of Epics linked to this topic, final definition to be published by September 15th, 2012)

  • Stream-oriented GEs

Transmission of content and data streams over a network can be performed in a variety of ways. The type of content and data to be transferred and the underlying networks conditions determine the methods for communicating. From the common end user viewpoint, there is today the desire to access unlimited amounts of content/data, including highly accurate timing dependencies between the different sources. But there are also other needs for another category of applications in which the challenge is to transmit and store temporarily a huge number of streams coming from hundreds of moving stream sources (e.g., mobile device video cameras).

Initially, content streaming was mostly done over managed network using specific packaging of the payloads and specific transport protocols to guarantee the Quality of Service (QoS) requirements. This led to solutions such as DVB standards, piling RTP-RTSP over MEPG-TS or MPEG coding. But nowadays, things are changing and unmanaged network are utilized with HTTP protocols to perform adaptive streaming. More, streaming is not limited to unidirectional delivery but can be envisaged within interactive applications including complex processing operations. The Epics proposed linked to this topic should provide all the means to set up services based on the distribution or exchange of content and data in a streaming manner. A final target for this enabler could be to offer “Streaming as a Service”. Streaming thus should apply not only to media contents but also to streams of sensor data and many other forms of information within the FI-PPP.

(Click here to find the 1st consolidated draft of Epics linked to this topic, final definition to be published by September 15th, 2012)

  • Cloud Proxy Extended Development and Management Platform GE

The Cloud Proxy Extended Development and Management Platform (CPEDM) GE will provide common components that will be used by cloud-based applications designed to leverage local resources at the cloud edge, by hosting app components on the Cloud Proxy. Currently, the Cloud Proxy GE provides capabilities to host app components (packaged as LXC containers or OSGi bundles), which have access to resources within the local environment and within the cloud proxy itself.

The additional capabilities provided by this GE will make the development of such applications more simple and straightforward, by providing a set of common software components (libraries and services) that implement some common tasks typically performed by applications. Moreover, this GE will enable end-to-end automation of the life cycle of applications that have components designed to run on the cloud edge (orchestrated by the IaaS Service Manager GE).

(Click here to find the 1st consolidated draft of Epics linked to this topic, final definition to be published by September 15th, 2012)

Submitters to this Open Call should be legal entities that are established in an EU Member State, or FP7 Associated State.

Before responding an Open Call, we recommend that you:

Three Open Calls have been planned with a total grant devoted to all of them of 12,3 M€ (Million Euros).  Aprox. 2 M€ have been already assigned as a result of the already published and closed FI-WARE 1st Open Call.  The upper limit of funding for the three topics in the Second Open Call will be 6 Million €, of which a maximum of 2,75 Million € will be devoted to the Advanced Web-based User Interface topic, a maximum of 2,25 Million € will be devoted to the Stream-oriented topic and a maximum of 1 Million € will be devoted to the Cloud Proxy Extended Development and Management Platform topic. The rest of the grant will be assigned to the third Open Call.

The following documents include helpful information to prepare your proposal:

The planned schedule associated to the Second Open Call is shown below. 





Call publication on the project web site

1st August 2012

Deadline for proposals submission

7th November 2012

e-mails for acknowledgement of receipt

8th – 9th November 2012

Proposals evaluation

8th November 2012 – 23th November 2012

Sent report of the consensus view of the experts to all proposers

26th November 2012


Last week November 2012 –
Mid December 2012

Acceptance by FI-WARE Consortium

Mid December 2012

Acceptance by the Commission

January 2013

Signature of the Consortium Agreement

January-February 2013



Other interesting information:

Project acronym: FI-WARE
Project grant agreement number: 285248
Project full name: FI-WARE: Future Internet Core Platform
Call open: The call opens on 1st August 2012
Deadline: The call closes on 7th November 2012 at 17h00 (Brussels time)
Expected duration of participation in project: February 2013 to April 2014
Total EC funding available for new partners: up to 6 Million Euro.
Call identifier: FI-WARE: Open Call 2 for additional beneficiaries
Language in which proposals should be submitted: English
Web address for further information: this web page
Email address for submissions: (subject: “FI-WARE: Open Call 2 for additional beneficiaries”)
Email address for further information:


This announcement will also be broadcasted via our TwitterFacebook and LinkedIn channels.