fi-ppp / fi-ware...basis – base platform for future service infrastructures presenter/s: name/s on...

FI-PPP / FI-WARE Open Calls

Pascal Bisson (Thales), Henk Heijnen (Technicolor)

The FI-WARE Project – Base Platform for Future

Service Infrastructures

Open Calls

Reserved 12M Euro of project budget for distribution among new partners

New partners selected through Open Calls to allow for responding to

emerging user needs not identified or known at the start of the project (e.g., due

to new usage areas, new technologies, new economic conditions)

Specific budget parts reserved for SMEs and Research Centers

Selection of new partners done according to the procedure issued

by the European Commission

Topics discussed and agreed at FI-PPP AB (selection of topmost

priorities for FI-WARE & UC Projects – candidate topics also proposed by

TWPs)

3 Open Calls – 1st closed, 2nd open, 3rd not yet announced

1 FI-WARE Technology Foundation: The FI-PPP Core Platform Paris,09/10/2012

European

Commission

23 October

2009v1a

Guidance note for project coordinators planning a competitive call

for additional beneficiaries in an ICT Integrated Project or Network

of excellence



Open Calls

http://www.fi-ware.eu/open-call/

Three Open Calls (total grant 12,3 M€). First (2M €), Second (7-

8M €). Third (the rest) .

1,25 Million €

750 K€

2 Topics for the 1st Open Cal (published Feb 1st 2012)

KIARA – SELECTED PROPOSAL from ZHAW (+DFKI,USAAR-CISPA, EPROS) FOR MIDDLEWARE

Total costs 1.583 MEur – EC Contrib 1.248 MEur

BEMES – SELECTED PROPOSAL from IBBT FOR BM&BE

Total cost 852 KEur – EC Contrib 656 KEur

five new partners are going to join FIWARE (amendment undergo)






https://forge.fi-ware.eu/docman/view.php/7/624/FI-WARE+High-level+Description+Product+Vision+11-11-16.pdf



FI-WARE 2nd Open Call http://www.fi-ware.eu/open-call/









Funding: upper limit 6 MEur

Topics of the 2nd Call:

• Advanced Web-based User Interface GEs (< 2.75 MEur)

• Stream-oriented GEs (< 2.25 MEur)

• Cloud Proxy Extended Development and Management Platform GE (1 MEur)

Published: 1st August 2012

Deadline: 7th November 2012









The Cloud Proxy Extended Development

and Management Platform (CPEDM) GE

• Common set of SW

libraries and services

• End to End life cycle

management automation

(under control of IaaS)



Example: Flickr+ app

Proxy component running on CP.

Proxy used to cache photos catalog and photos being viewed

The cloud-based part of the Flickr++ app is deployed and running in the cloud (using

the regular Cloud GEs -- DCRM, SM, etc).

A user accesses Flickr++ app in the cloud (e.g., via a browser), the Flickr++ client

code (e.g., in JavaScript) is downloaded and executed on the client device (e.g., mobile

phone, tablet, PC).

Flickr++ client checks whether a CP device exists in the local env. If not -- proceeds

with 'legacy' Flickr client.

Optionally, Flickr++ client asks the user to approve the resources/privileges

associated with the Flickr++ Proxy bundle (specified in the corresponding manifest)

Flickr++ client notifies CP that it needs Flickr++ Proxy bundle, passing to the CP a

URL (served by the cloud-side part of the app) where this bundle can be downloaded.

If Flickr++ Proxy bundle is not already installed on CP, CP downloads it using the

provided URL, installs and executes it, and finally returns back to Flickr++ client a URL

(e.g., IP:port) at which the Flickr++ Proxy can be accessed.

Flickr++ starts normal operation, working both with the cloud-based app component

and the Proxy component (as described in the summary above).




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:

Read the Overall FI-WARE Vision, where definition of main concepts

(GE, FI-WARE Instance, FI-WARE Testbed and Open Innovation Lab, etc)

are provided and the current chapters of FI-WARE are described.

•Read the Architecture and Open Specifications in FI-WARE

Understand how FI-WARE is applying Agile because new beneficiaries

joining the FI-WARE Consortium will have to follow defined processes

and tools.

Analyze which Generic Enablers FI-WARE partners are currently

implementing in their effort towards Materializing the FI-WARE Vision.






http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Overall_FI-WARE_Vision





http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Architecture_and_Open_Specifications

http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Agile_Development_Methodology



http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_the_FI-WARE_Vision



Backup slides



Project fact sheet

26 partners

5 Universities

4248 Person Months (except

open calls)

Total Funding 41 M€

Open calls 12,3 M€

Total budget 66,4 M€

Start: 1st May 2011

Duration: 3 years

Main data

FI-WARE CATALOG

http://catalogue.fi-ware.eu/






FI Core Platform Architecture: main chapters

Op

era

tio

ns

Se

cu

rity

, P

riva

cy &

Tru

st

Fu

nc

tio

na

lity

Developer

tools

Apps & service

ecosystem

Cloud Hosting

Internet

of Things Data & context

Management

Interface to the Network and devices



Main milestones in FI-WARE

18

We are here (almost mid-term)

* FI-WARE – Follow Agile Methodology



Time schedule

First year

Second year

Third year

June/September 2011: High level architecture

description

November 2011: first major release of FI-

WARE requirements backlog

January 2012: First open call issued

May 2012: Reference implementation

June 2012: Open call closes

September 2012: First FI-WARE testbed

January 2013: Second open call issued

May 2013: Reference implementation

June 2013: Open call closes

September 2013: second FI-WARE testbed

January 2014: Reference implementation

May 2014: FI-Ware final release



FI-PPP Governance structure

20



Milestones & deliverables

D2.1a,b FI-WARE Requirements Backlog (M7,M12)

D2.2 a,b FI-WARE High-level Description (M2,M5)

D2.3 a FI-WARE Architecture (M9)

D2.4a FI-WARE technical roadmap (M9)

D2.5a Third Party Innovation enablement

D11.4a Standardisation Plan and Report (M9, M12)

D11.1a Market and Competition Analysis (M12)

D11.2a Exploitation Strategy (M12)

D11.3a Market and Policy Regulation Awareness Report (M12)

D12.2b Report on Communication and Dissemination activities (M12)

D12.3.b Report on Collaboration activities (M12)

D3-8.1.a FI-WARE v1. GE Open Specifications (M12)

D3-8-5.a (x=3-8) FI-WARE v1. Reference Implementation

of GEs and accompanying documentation (M12->M14)

FI-WARE Testbed M15 (V1.1) – M17 (V1.2)

fi-ppp / fi-ware...basis – base platform for future service infrastructures presenter/s: name/s on...

Documents