We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Collaboration activities - FIWARE Forge Wiki

Collaboration activities

From FIWARE Forge Wiki

Jump to: navigation, search

Contents

FIWARE is the Technology Foundation of the Future Internet PPP. Thus, by nature it can not run in an isolated way at all, being obvious that its most important success will be the adoption of the technology by the Use Case projects in a first stage and in a wider scope later on.

All of these instruments together give sense to a programme that should help Europe and all the companies involved in the projects to:

a) Increase innovation in the technology itself, helping to shape the future of the so called Future Internet (understanding this concept as a convergent view between different technological pillars that comprise networking aspects, but also Internet-of-Things, Data and context management, Cloud computing, Trust and Security and Internet of Services).

b) Increase the industrial competitiveness of business sectors in Europe whose impact in the economy is relevant enough so that we ensure that they do not lack behind other competitors, and furthermore that they go beyond them. The way the FI PPP will contribute to that is by bringing the technology to its adoption in those sectors.

FIWARE, as derived from this, is a crucial piece in this puzzle, and the collaboration with all the other projects of the FI PPP in this phase and the next ones is as important as the construction of the technology foundation itself.

The largest amount of efforts in collaboration so far have been invested in cooperation with the projects within the FI-PPP in order to fine-tune the strategy towards exploitable platform components in actual scenarios in different domains such as environmental care, transportation logistics of goods and people, agrifood, smartcities, etc.


Latest Collaboration Activities

This section summarizes the collaboration tasks happened during the last six months (until Jun 2013). The most remarkable one is definitely the ‘Software Architects week’ celebrated in April 2013, that is described in section 1.4. Another key one is described in sections 1.5 and 1.6.3, that show the win-win results obtained by the means of a deep technical cooperation with the Outsmart phase I use-case project.

The other sections focus on the sessions, exhibitions and collaboration tasks in the context of the FI-PPP and with external bodies, such as the IERC IoT cluster.

Safecity real-life trial in Madrid, relying on FIWARE enablers & testbed

Feb 2013 Proof of Concept trial of the SafeCity project was a remarkable culmination of a 2 year work. Further to the success of the 1st PoC in Stockholm, where they tested the appropriateness of their solutions in a disaster scenario in a railway tunnel, they embarked again on an exciting and challenging new test. This time, they once again decided to combine their technologies with FIWARE’s Core Platform to conduct an experiment that would assess the adequateness of both to deal with scenarios involving the police using advanced tools to track down criminals, detect suspicious objects, stop intrusions or deal with loitering.

The test was a fun exercise of members of SafeCity moving around Madrid in freezing temperatures and braving the pouring rain to play the role of “criminals” under the surveillance of the police. This exercise involved the use of cameras, different levels of video processing, video analytics, 3D video engines and crowd behavior simulation.

The relevance of the two tests performed by SafeCity is certainly high for FIWARE and shows well the cooperation results within the FI-PPP, as long as it means a real life validation of the project in the area of Safety and Security. Also, the infrastructure of the FIWARE testbed performed flawlessly.

Equally relevant was the exploitation of FIWARE’s Generic Enablers in combination with the technologies brought in by SafeCity. Particularly, this was the case with the IaaS Data Center Resource Management, the Complex Event Processing and the Semantic Application Support.

There was an immediate impact on the local media and a myriad of mentions on Internet pages (for instance, on the news agency Europa Press).


The FI-PPP projects exhibition at MWC-2013

The Internet is definitely going mobile as the impressive figures of the recent Mobile World Congress of Barcelona reveal: more than 1.700 companies, 3.400 journalists and, on the whole, over 72.000 attendees from 200 different countries.

FIWARE, in its role of leader of the creation of a Future Internet services ecosystem in Europe, set up an exhibition booth together with the other FI-PPP projects and organized a workshop within the parallel event on Thursday 25th and Friday 28th .

During the exhibition at the MWC, several FI-PPP use-case projects demonstrated and explained to experts and interested people how FI services are to transform existing sectors such as logistics, safety, smartcities, agriculture, e-health and e-content industry. In our case, FIWARE showed how to materialize such ideas in a faster, easier and cost-effective way with its proposal of Future Internet core-platform of generic enablers.

We did not only provide information and get the pulse of experts on our architecture and implementations but we’ve got proposals for collaboration on specific technologies and exploitation areas. Additionally, some datacenters appeared to be interested on the concept of FIWARE instances to enrich their service portfolio.


The FI-PPP event & exhibition in Barcelona

In the same week of the Bacelona 2013 Mobile World Congress, CONCORD FI-PPP project organized a two-days event hosted in the “Fira de Barcelona” for all FI-PPP projects to share their current status and results as well as existing demonstrations. FIWARE actively participated with several presentations and one exhibition booth, similar to the one showed the days before in the MWC’2013. A presentation from Outsmart project in the second day explained the results of the cooperation tasks described later on in a following section.

More info is available here.

The agendas of both days are included below.

DAY 1 (FEB 28TH): FI-PPP CONFERENCE DAY


DAY 2 (MARCH 1ST): FI-PPP STAKEHOLDERS DAY / BUILDING THE FI-PPP COMMUNITY


The FI-PPP Software Architects Week

This event was organized by FIWARE and hosted in April 2-5th 2013 in Madrid, at the Telecommunications Engineering School of the UPM.

The goal of the large meeting was to initiate the collaboration with the FI-PPP Phase II Use Case Trials from the very start (ever before their internal kick-offs) to ensure that we share a common view and the same objectives. FIWARE provided a holistic vision of the achievements and the methodology we use and the Use Cases gave us insights in their respective projects. The focus was mainly at architectural level but there was also room for organizational aspects. Overall, a lot of work for four whole days but we are pleased that we now understand each other rather well.

The meeting was attended by key members of cSpace, Finesce, FI-CONTENT II, FITMAN, FI-STAR and FIWARE projects.


Collaboration on joint exhibitions with OutSmart project

One of the key proposed values of FIWARE, beyond the Generic Enablers, is to expose them as a real ecosystem exploitable by the broad community of developers via the Open Innovation Lab (OIL).

For this ambitious goal to become true, FIWARE needs to enrich this ecosystem beyond the technology components with real data, events and resources that make the whole offering an attractive setting for thousands of developers. One way to achieve such an exciting ecosystem is to involve Smartcities, connecting their sensors, actuators and other data/event resources to the FIWARE Lab so that developers can build disruptive apps over those cities. This idea may make also much more attractive the hackathons planned for the future as part of the FiWARE 3rd Open Call objectives.

Taking the above as a goal, the FIWARE IoT team has established a deep collaboration with the FI-PPP phase I Use-case project Outsmart, specifically with their “SmartSantander public lighting PoC”. This Proof-of-concept involves 15 sensor nodes collecting presence, temperature, lighting level and battery level observations and two energy sensors and actuators connected to the public lights of a park in Santander city (“Parque de las Llamas”, Santander, Spain). This setting seems perfect for a first trial of FIWARE IoT GEs because of its size and because Outsmart was already using the core of the Backend Device Management GE. However, SmartSantander is today one of the most “sensorized” cities in Europe, as it hosts more than 4,000 sensors distributed all over the city, beyond the lighting Outsmart PoC. FIWARE IoT team is already exploring how to connect all city sensors and data beyond the PoC, once the first integration trials are validated.

This collaboration has concluded with as satisfactory OutSmart-FIWARE interconnected scenario that is depicted in the following picture and was shown in the recent Dublin FIA exhibition (see next section).


Additionally, this successful FIWARE IoT demonstration has been selected to complete the FIWARE overall demo (“Live demo”) to be shown in the next project review (Brussels, June 2013) and forthcoming events.


Dublin FIA FIWARE Workshops & Demos

The FIWARE projects has organized a couple of sessions and an exhibition collaborating together with different FI-PPP projects in the context of the latest Future Internet Assembly (FIA) event held in Dublin (May 7-10th 2013). Additionally, our team had the opportunity to attend several other projects sessions both within and out of the FI-PPP ecosystem and organize meetings with relevant initiatives, such as the IERC IoT cluster as described in the following section.


The FIWARE pre-FIA Workshop

The following frame depicts the pre-FIA workshop detailed agenda.


The FI-PPP plenary session

FIWARE representatives were in charge of organizing this one-hour workshop in the FIA plenary session of May 9th morning.

The FI-PPP was presented as a research and development initiative that takes FP7 research into innovation, notably in the need for strong cooperation among the participants and that it envisages results closer to the market. This way, today the Future internet PPP moves from the development into delivery model. The session itself was focused on the presentation of the current technology results: the Generic Enablers (GEs) and the Open Innovation Lab (OIL), a virtual place in the cloud where developers will be able to use the technology to build innovative services and apps. It is aiming as well to show how this technology can be applied in some usage areas such as energy efficiency, manufacturing to create smarter business processes and smarter cities.

The session was carried out by the following participants:

  • David Kennedy (Eurescom), CONCORD project
  • Fiona Williams (Ericsson Research), FINESCE project
  • Andreas Metger (University Duisburg-Essen) and Haluk Gökmen (Arcelik), FI-SPACE project
  • Carmen Mac Williams (Grassroots-arts), FI-CONTENT 2 project
  • Juanjo Hierro (Telefónica Digital), Future Internet PPP Chief Architect, FIWARE
  • Stefano de Panfilis (Engineering), FIWARE
  • Nuria de Lama (Atos Research), FIWARE

The FIWARE exhibition together with Outsmart FI-PPP project

Our recent exhibition in Dublin Future Internet Assembly (FIA, May 7-10th 2013) shows how FIWARE enablers truly expose open APIs & protocols embedding the technology complexity and, more important, real-time data and events of Smartcities.

The following picture shows this demo, based on the successful collaboration with the FI-PPP Phase I Outsmart project.


Outsmart SmartSantander public lighting scenario has built its services on top of DCA IDAS, the main asset in the FIWARE IoT Back-end Device management GE, that collects data of actual sensors in the "Parque de las LLamas" location.

Additionally, this FIWARE GE is translating sensor data into real-time OMA NGSI events, accessible to developers via the standard APIs of the Context Broker GE at the FIWARE Testbed in the cloud. In the terminal snapshot we observe the XML a developer receives whenever GPS-located presence sensors in the park are triggered. In this park there exist also lighting, temperature and public lights energy consumption sensors.

Developers will be also able to plug those NGSI events into other FIWARE enablers, and thus benefiting from other assets such as Bigdata, Complex Event Processing, Security APIs, etc. This way, FIWARE behaves like a kind of "Open Operating System of a Smartcity", ready for developers and entrepreneurs willing to make true totally new and creative Future Internet Apps exploiting Smartcities data and events.

Kicking off Collaboration with the IERC

At the recent Dublin FIA, the FIWARE IoT team had the opportunity to meet with the IERC IoT Cluster and discuss some collaboration tasks ahead.

The summary of the conclusions of this meeting are listed hereby: The FIWARE IoT chapter has implemented an architecture of enablers working today and suitable to be opened to a broad community of developers. Those developers will access this way data, events and resources to code new and disruptive apps. As good example is the integration of SmartSantander Outsmart scenario described in the previous section. The IERC has concluded a broad IoT architecture based on the IoT-A basics, some work might be needed to understand how FIWARE IoT elements map to such architecture. The following action points have been agreed:

  • 1. IERC to circulate links to the latest sources of their proposed architecture.
  • 2. FI_WARE to create a collaboration space in the Wiki and include links to the most updated references of the IoT architecture.
  • 3. IERC team to analyze FIWARE architecture to understand which new elements might be added in the future providing key features.
  • 4. FIWARE to analyze the overall IERC architecture to agree on terminology and map elements in both descriptions.
  • 5. Both teams to meet again in the forthcoming IoT Week of Helsinki (June 16-20th 2013).

Meeting with IERC during IoT Week in Helsinki

At IoT Week in Helsinki we had a meeting between the FIWARE IoT team and the IERC Activity Chain on "Architecture". We discussed the mapping of the FIWARE architecture to the IoT-A Architectural Reference Model and found an initial mapping. At the meeting, we also discussed the next steps of interactions between IERC and FIWARE and also the whole PPP.

  • There is now a stable version of FIWARE IoT GEs, so it is time to check whether there are additional assets from which FIWARE and the FI-PPP could benefit.

ACTION POINT: IERC projects need to check the FIWARE architecture and its mapping to the IoT-A ARM and evaluate whether there are assets not yet present that they could provide from which FIWARE could benefit. Please map to the IoT-A ARM for easier assessment. To be considered by FIWARE (or its follow-up) it is important that a GE based on such an asset could be provided also to external partners under FIWARE conditions, i.e. as open-source or under suitable commercial conditions.

  • IERC Activity Chain on (Semantic) Interoperability was identified as a further area of collaboration.

ACTION POINT: FIWARE will nominate a representative for interaction with the activity chain, who will try to attend their next meeting. There is the possibility of joint testing events.

  • The new FI-PPP application projects are relevant for the IERC Activity Chain on "Applications"
  • The IoT-A Architectural Reference Model will be sustained and further developed by the IoT Forum (www.iot-forum.eu), which was formally founded during IoT Week. This will enable all interested parties to contribute. The IoT Forum will also organize future IoT Weeks, the next one will be in London in June 2014.

FI-PPP Architecture Board Meetings

During this six months period, FIWARE chief architect, Juanjo Hierro has attended all the virtual and face-to-face Architecture Board meetings.

Previous Collaboration Activities

This section summarizes the collaboration activities happened before the period reported in the previous section (until Nov 2012).

It is remarkable the organization of two training weeks in different locations with the attendance of all Use-case projects. Use-case projects were also able to present their scenarios and clarify which FIWARE components are likely to be used first. We called these actions the 'FI-PPP Software Architects Weeks' (May 21st - 24th at ZHAW in Zurich & June 4th - 7th at ETSIT/UPM in Madrid).

Additionally, the project has ensured cooperation with key instruments within the programme such as Concord, with meetings in Madrid (Feb 20th 2012) and in Málaga ( Agenda ).

The following sections summarize the collaboration activities held until Nov 2012.

Collaboration with projects under the FI PPP umbrella

Overview

The collaboration with other projects under the FI PPP umbrella happens at two levels: strategic level and operational level.

  • The strategic level uses the PPP Steering Board as collaboration instrument.
    The Steering Board counts on two representatives of each of the projects under the PPP umbrella and its organization is supported by the CONCORD project. FIWARE representatives in that body are Mr. José Jiménez, from Telefónica R&D and Ms. Nuria de Lama, from Atos.
    The kind of discussion topics that fall under this category are: joint dissemination efforts including the definition and agreement on strategic communication messages that affect the set of projects as a whole, support to organize and attend relevant events for the PPP, issues related to time synchronization between the projects or analysis of overall performance of the programme (even though this one is at early stage and will be emphasized in the coming months), to name a few.
  • The operational level uses the PPP Architecture Board as collaboration instrument.
    The Architecture Board is composed of two representatives of each of the projects under the PPP umbrella and it's chaired by FIWARE. FIWARE representatives in that body are Mr. Juan José Hierro. from Telefónica R&D and Mr. Thomas Bonnert, from SAP.
    In this framework FIWARE informs other projects about the technical progress of the project as well as the tools available to support the continuous feedback among them. In the first period, for example, a complete environment to gather requirements from the Use Cases has been set up. This is based on a backlog that allows the tracking of each of the requirements pointed out by each of the Use Case projects. It is then a bilateral channel with a lot of potential to ensure that interests of the use case projects and FIWARE are well aligned. In the end, this will reflect the potential of FIWARE to satisfy their needs and make an impact at business level.

FIWARE in the FI-PPP Steering Board (SB)

FIWARE is participating at the FI-PPP Steering Board (SB). This body shall:

  • Act as the highest program-level decision making authority
  • Be responsible for decisions regarding Programme level vision and roadmap alignment, priority setting, standardisation requirements, as well Use Case Scenario evaluations and required standardization, licensing, methodological and other support needs
  • No escalate decisions, “must decide”, based on consensus
  • shall make recommendations for implementation in respective FI-PPP projects when required. If recommendations require changes of objectives and/or effort and budget allocation, a contract change has to be agreed and implemented together with the Commission

The Steering Board shall not be entitled to act or to make legally binding declarations on behalf of any Party

FI-PPP SB Meetings and agreements

Following is the list of face to face as well as virtual meetings hold by the FI-PPP SB

  • Initial f2f meeting May 19, 2011 in Budapest [Meeting minutes]
    Summary of main conclusions:
    • Constitution of SB
    • Creation of Dissemination WG
  • Second f2f meeting October 25, 2011 in Poznan [Meeting minutes]
    Summary of main conclusions:
    • Discussion on Advisory Board composition and functions
    • Future actions

FIWARE in the FI-PPP Architecture Board (AB)

The FI-PPP Architecture Board (AB) is the principal body for program-level coordination activities of all kinds of technical aspects and in between FIWARE, Use Case projects, CONCORD, INFINITY, and potentially further external stakeholders and communities covering a wider range of Usage Areas. This board meets on a monthly basis, either physically or virtually, and elaborates on issues related to program-level architectural and technological directions. The board is chaired by the FIWARE Chief Architect and each FI-PPP project is represented by two delegates. The overall mandate from a legal viewpoint is documented in the FI-PPP Program Agreement.

One major and immediate concern of the AB was to establish and maintain coordinated interactions between FIWARE, the Use Case projects, and other FIWARE-external stakeholders, including other projects in the same or different Usage Areas. In order to support such interactions in a sustainable and uniform manner two dedicated processes have been defined for:

  • FIWARE General Support
  • FIWARE Theme/Epic/Feature Requests

The first process, "FIWARE General Support", defines a concrete procedure for issuing any sort of technical request and how it will be processed by FIWARE. The tooling for this process is integrated into the FIWARE collaboration platform FusionForge and is a combination of Tracker (ticketing support system) and a Task Manager.

In order to issue a "FIWARE General Support Ticket" any external user needs to register a FusionForge account and has to request access to the FIWARE meta project hosted on FusionForge. Once access is granted the user can proceed to the "FIWARE General Support" tracker and issue a ticket by filling the provided form with context information along various aspects, like basic issuer information, relation to FIWARE Chapters, Generic Enablers, and many other features. As soon as the request was issued a ticket is generated and the Chief Architect and his team is requested to perform an initial screening. If the information provided is consistent and complete the Chief Architect will assign the ticket to a respective handler (e.g. a Chapter Leader or Chapter Architect) and in addition, creates an associated task with a start and expected end date which is then assigned to the ticket and the ticket owner. Once the new ticket/task owner is informed about the assignment, she/he will decide about appropriate measures to be taken in order to process the request. This could be, for instance, in the form of setting up a workshop with the ticket issuer in order to discuss the technical details of the ticket. A more straightforward example would be a simple reply with a comprehensive answer with respect to the information requested. The actual handling of each and any ticket may require several interactions and the system (tracker) supports this by different means that allow to document and track the interactions and measures taken. Even after the completion and closure of the final ticket / task the information will stay in the system's database and can be recovered at any later point in time. Obviously, this straightforward and unified approach provides a single point of access to any external stakeholder without heavy and uncoordinated interactions (e.g. by email and document exchanges via various channels). In addition, the system is configured such that a maximal level of transparency is maintained to all system users, that is FIWARE internal and external, which is considered by FIWARE as an important element for constructive, effective, and efficient collaboration.

The second major topic is related to the technical scope of FIWARE and individual projects in Usage Areas. The mission of FIWARE is to develop a generic platform that is holistic and complete. It should provide projects in Usage Areas with a basic Future Internet infrastructure and platform on top of which they can develop and operate domain specific applications and services. The FIWARE architecture should in addition provide support for domain specific extensions of any sort by projects in a given Usage Area. One obvious issue is therefore agreement on what features are "generic", that is what is in the scope of FIWARE and supported by FIWARE Generic Enablers, and what features are "domain specific" and thus out of the scope of FIWARE. Establishing common agreement on such discussions is one of the most central mandates of the AB. In order to support this mission a dedicated process was defined and implemented by respective support tooling. Here the Agile Development approach of FIWARE was adopted and extended as baseline methodology for the whole FI-PPP as it supports cross-team/-project collaboration along a synchronous roadmap. For this purpose a so-called Unclassified Features Backlog has been created in which projects linked to Usage Areas can insert their Features Requests towards FIWARE. Entries in this backlog are described in a commonly agreed format, the so-called FI-PPP Backlog Entry Format (see FIWARE Agile Development Methodology). Once the feature request is completely described and available in the Unclassified Feature Backlog, a similar procedure as for "FIWARE General Support" takes place. The requesting party submits a ticket by using the "FIWARE Theme/Epic/Feature Requests" tracker. Once the ticket is submitted, the FIWARE Chief Architect and his team is notified and requested to verify and validate the ticket. If the ticket is consistent and complete the Chief Architect will assign the ticket to a respective handler (e.g. a Chapter Leader or Chapter Architect) and in addition, may create an associated task with a start and expected end date which is then assigned to the ticket and the ticket owner. Once the new ticket/task owner is informed about the assignment, she/he will decide about appropriate measures to be taken in order to process the request. This could be, for instance, in the form of setting up a workshop with the ticket issuer in order to discuss the technical details of the Feature Request. A more straightforward example would be a simple reply with a comprehensive statement with respect to the nature of the feature requested, e.g. domain specific, generic, already covered by a FIWARE Generic Enabler, not yet covered by a FIWARE Generic Enabler but in consideration, or other states. The actual consensus establishment may require several interactions and the system (tracker) supports this by different means that allow to document and track the interactions and measures taken. At the very end there will be a decision about the nature of the requested feature. For the specific case that the requested feature will become part of the FIWARE technical roadmap the respective FIWARE Chapter will be identified and the requested feature will be transferred into the respective FIWARE Chapter backlog.

Meanwhile both processes and the respective tooling is operational. In order to facilitate uptake and to lower entry barrier, a comprehensive set of tutorials and other supporting documents were written and are publicly available on the public FIWARE Wiki (http://wiki.fiware.org):

As mentioned previously, the AB meets on a monthly basis and is hosted on a rotating basis by AB members organizations. Following is the list of meetings celebrated so far:

AB Kick-Off Meeting, Co-located with the Future Internet Assembly, May 19 2011, Budapest, Hungary ( Agenda, Minutes)
  • Major outcomes:
    • High-level introduction of the persons projects, and organizations involved in the AB
    • FIWARE Roadmap and Agile Approach introduced in great detail
AB Virtual Meeting, June 19 2011 ( Agenda, Minutes)
  • Major outcomes:
    • Introduction of the FI-PPP Backlog Template (Agile Approach)
    • Discussion and identification of potential collaboration support tools (e.g. AgileFant, FusionForge, Trac, etc)
    • Discussion on methodologies for requirements engineering (processes, tools)
AB Meeting, July 11-12 2011, Madrid, Spain ( Agenda, Minutes)
  • Major outcomes:
    • Agreement on the FI-PPP backlog template
    • Rules for on-demand expert invitatin to AB
    • Collaborative tools for Agile discussed (AgileFant and FusionForge for Agile Development)
AB Virtual Meeting, August 25 2011 ( Agenda, Minutes)
  • Major outcomes:
    • Process for "FIWARE General Support" presented and agreed
    • AgileFant droped in favor of FusionForge/Tracker/Wiki
AB Meeting, Sept 21-22 2011, Paris, France ( Agenda, [Minutes under review])
  • Major outcomes:
    • FIWARE Product Vision presented and agreed
    • Collaboration space "FIWARE FusionForge" presented and accepted
    • FIWARE Tutorials for collaboration introduced
AB Meeting, Co-Located with Future Internet Assemply, Oct 2011, Poznan, Poland ( Agenda, [Minutes under review])
  • Major outcomes:
    • Status on INFINITY Capacities DB
    • FIWARE Apps/Services Framework presented to Usage Areas (follow-up requested)
    • FIWARE Feature Request Process and Unclassified Backlog introduced and accepted
    • Timeline towards 1st FIWARE OpenCall agreed
AB Meeting, January 18-19 2012, Nice, France (provisional minutes)
  • Major outcomes:
    • General organizational & strategic agreements
    • Organization and communication of more general aspects of FIWARE’s 1st Open Call
    • Triggered the start of a reflection process after which the expectations for the Capacity Building project will be better defined. INFINITY to lead a white paper to be produced in conjunction with FIWARE
    • Technical presentations and following discussions
      • Uncertainty & Trust in Data
      • 3D User Interfaces and Augmented Reality
      • Streaming
AB Virtual Meeting, February 16 2012 (Minutes – under review)
  • Major outcomes:
    • Agreements to resynchronize deliverables between FIWARE & UC Projects
    • Agreement to produce Capacity Building White Paper in the context of the AB ( INFINITY produces the initial draft but the result will come out of the AB)
    • General updates in several areas
AB Meeting, March 28-29 2012, Zurich, Switzerland (Agenda and provisional Minutes under review)
  • Major outcomes:
    • General update on the status of individual PPP Projects
    • Discussion and finally better understanding of the needs for the Capacity Building Project
    • Feedback for UCs to FIWARE
    • Revision of UC requests to FIWARE
AB Virtual Meeting, April 12 2012 (Provisional Minutes + Agenda - Part 1 and Part 2)
  • Major outcomes:
    • Agreed schedule of Next steps regarding paper describing points to take into account in phase 2 and 3 of the FI-PPP program
    • Agreement to take measures for improving interaction with UC projects
    • More preparatory work towards the organization of the Education Sessions
    • FIWARE puts forwards a proposal for rescheduling
AB Meeting, Co-Located with Future Internet Symposium, May 29-30 2012, Espoo, Finland (Agenda and minutes under review)
  • Major outcomes:
    • Update on status of individual PPP projects
    • Measures for improving interaction between UCs and FIWARE
    • Early feedback on the FIWARE Testbed
    • Briefing on the 1st Open Call & planning of the 2nd Open Call
AB Virtual Meeting, June 14 2012 (Provisional Minutes + Agenda )
  • Major outcomes:
    • General coordination actions between PPP Projects
    • Advancements in the definition of the topics for the 2nd call
    • Communication of the Expectations for the Testbed
    • General review of the PPP status

FIWARE and other WGs under the FI PPP umbrella

While FIWARE will increase dissemination and communication activities around its own results in the next period of the project when first components are released, the first 6 months, however, have been a joint effort to provide a coherent message around the overall PPP. CONCORD has facilitated the understanding and agreement among the different parties.

FIWARE has used CONCORD to open many dissemination channels. These channels can be classified mainly into two types:

  • Dissemination media, such as the website, where a description of FIWARE together with main contact data are reflected, as well as the newsletter (PPP snack ), to name the most important ones. FIWARE has also provided a general presentation for overall communication purposes that can be used by CONCORD at any time to promote the project and let other communities know about our activities. Further info under the newsletter section in Communication activities
  • Presence of FIWARE in Relevant Events. Some examples are:
    • Future Internet European Summit (FIS 2011 in Lux)
    • The 3rd European Innovation Summit: official session held at The European Parliament (Brussels) on October 11th (”Future Internet - Smart Cities - Coming your way".)
    • OPEN DAYS 2011: side event to the official programme of the Open Days held at the Committee of the Regions (Brussels) on October 13th
    • etc

Check the complete list under Dissemination_activities

FIWARE Technical cooperation with Use-case Projects: 'FI-PPP Software Architects Weeks

The organization of the 'Fi-PPP Software Architects weeks' has meant a great effort within the FI-PPP to align architectural views, improve the mutual understanding on requirements and pave the way for a much more pragmatic and realistic exploitation plan. For the FIWARE project, the outcomes of these sessions are a truly reality-check in order to target components to the actual expectations of stakeholders in various Future Internet domains, including environmental care, transportation logistics of goods and people, agrifood and, citizens cooperation and smartcities. This is an obvious cornerstone for a project developing a core-platform to be exploited first by those agents and later on for any interested 3rd party beyond the FI-PPP umbrella.

The event was held in two different weeks and different locations in order to be able to target as most architects and developers of the use-case projects as possible. This way, the first edition was hosted by ZHAW in Zurich (May 21st - 24th) and ETSIT/UPM in Madrid (June 4th - 7th).

The agenda was organized in a simple way: mornings parallel sessions were devoted to describe FIWARE components while the afternoon sessions were booked for the Use-case projects to tell the FIWARE team (and other interested UCs) the details of their scenarios. From the FIWARE perspective the presentations of both weeks were identical so UCs attendees could easily choose one or the other. On the other hand, UCs presentations were spread among the two weeks.

A detailed agenda of the event and the list of attendees is accessible in the following Googledoc [1]

The material presented and referenced during the 1st week sessions is available in the following placeholder: FI-PPP Software Architects Week Presentations and References

The outcomes of all these meetings are an impressive number of action points for all participating projects that will be gradually implemented. From a holistic perspective, the FIWARE project has now evidence of which GEs will be used first and for what concrete scenarios and purposes. Requirements and constraints have been revised. On the other hand, use-case projects have understood the scope, benefits, actual Open specifications and APIs of FIWARE GEs. There are many successful case where UCs came back with more FIWARE candidate GEs for the implementations. In some other cases, FIWARE GEs clarifications lead to higher doubts on usage and thus FIWARE is entitled to modify its strategy or keep its bet without that specific exploitation line.

The statistics on the events themselves are quite impressive and meant a real success to establish links among the projects in the face to face meetings and 'hall discussions'. Some relevant statistics are:

For the second edition: - 72 participants from the Use-case projects - 34 participants from FIWARE - 3 participants from Infinity

  • Total: 109 participants

In the first edition: - 17 participants from the Use-case projects. - 38 participants from FIWARE

  • Total: 55 participants

The snapshot below show the Agenda scheduled for the second week edition:

FI-PPP Software Architects Week Agenda - 2nd Edition


The following guidelines communicated to all FIWARE presenters to ensure homogeneous GEs presentations were:

  • FIWARE chapters are expected to present to the UCs attendees the basic concepts and the specific GEs to ease their exploitation within UC scenarios.
  • Each chapter will prioritize those GEs to be delivered in FIWARE first release and those with a higher rating score as provided by UCs at:

https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdC1zSUdlVjJ2WldESHZmZU13bTdjT3c#gid=0

  • For the GEs presentations, the following structure is suggested:
  • x) GE presentation (25-40')
  • x.1) Overview and reference architecture (5')
  • x.2) Basic concepts & Main Interactions (15-25')
  • x.3) REST APIs & tools for developers (5-10')

For the UCs presentations, the following guidelines were communicated to all presenters:

  • The overall idea is to present to the FIWARE team a number of selected scenarios (x) to understand the applicability of FIWARE GEs.
  • The presentations can be as follows:
  • 1 Description of Scenarios (x*20)
  • 1.x.1 story-line (5')
  • 1.x.2 High level description of the architecture (15')

- Diagram with all the components (provided by the UC or not) involved in the scenario. - Role of each component and basic interactions.

  • 2 Individual components description (technical approach, expectations, constraints) (60')
  • 2.1 For the components to be developed by the UC: why they are domain specific & functionality in detail.
  • 2.2 For FIWARE components, expectations & constraints.

Considering a total of 3-5 scenarios. UCs should generally need 120-160 min."


The FIWARE project and the Use-case projects under the FI-PPP umbrella have agreed to strength their mutual knowledge and cooperation at the technical level by the means of an event where all them will fill in the gaps as identified by the other party.

FIWARE chapters will be describing the basic concepts, architecture and APIs of its Generic Enablers, prioritizing those that have been previously rated with a higher score by UCs.

UCs projects will present to members of all chapters in FIWARE a number of selected scenarios, including the story-line, services, architecture of components, FIWARE GEs already identified as exploitable and testbed requirements (to be able to deploy UCs trials at the FIWARE testbed).

Due to the number of people to involve in this event and the commitments and availability of all projects, these Workshops will be conducted in two separate weeks. The content of both weeks will be the same from the FIWARE perspective (all slots are repeated from one week to the other), while UCs presentations will NOT be repeated.

Technical Meetings and Actions with Specific FI-PPP projects

The following list depicts examples of technical interactions between FIWARE work packages & FI-PPP use case projects and is not considered complete.

FIWARE and INFINITY

INFINITY is the project in charge of the Capacity Building. This means that they are identifying all the infrastructures where Use Cases could be deployed in the second phase of the PPP. These experimental infrastructures will be characterized and evaluated for the purpose of maximizing their benefit for the PPP and Europe in general.

Even though INFINITY is present in the main governance bodies of the PPP (Architecture Board and Steering Board) some meetings have been organized by the project to discuss the specific needs of the different projects with respect to these infrastructures. This includes the deployment requirements of FIWARE. Physical meetings have been held in Brussels (June 2011) and Poznan (October 2011).

There was a meeting in March 2012 in Madrid to align thoughts and come to a common understanding in relation with a White Paper that would delve into the complexities of managing infrastructures and deployment strategies for the coming stages of the PPP Programme. FIWARE produces a draft that in turn was taken up by INFINITY as lead editors. A final version was produced in close collaboration between INFINITY and FIWARE and finally submitted to the Architecture Board for their review.

Our Technical Leader took part in the 2nd INFINITY concertation meeting in Zurich (March 27th 2012). The event delved into a variety of topics of common interest. More details can be found on 2nd Infinity ConcertationBoard Minutes(access restricted to PPP members & EC)

FIWARE and INFINITY have ensured continued communication and part of the team are members of both projects. This facilitates mutual understanding and a better grasp of each other's needs.

FIWARE organized a series of Infodays in October, 2012 to promote FIWARE's 2nd Open Call. We offered INFINITY the possibility of having a timeslot to promote their Call for Tender. They took it in all three events (Madrid, Paris and Trento) and had a dedicated timeslot. The agendas are available under FIWARE's 2nd Call infodays

FIWARE and FINSENY

FIWARE has conducted two meetings in Berlin (February 2012) and Madrid (March 2012) where requirements, roadmaps and architecture views have been exchanged and discussed. The experience gathered in those discussions paved the way to organize the Software architects' weeks with all the other UCs, including Finseny.

Additionally, FIWARE actively participated in the FINSENY external stakeholders meeting in Berlin (February 2012).

FIWARE and OUTSMART

Outsmart has participated in the virtual meetings on requirements for the synergic integration of PubSub, CEP and Bigdata GEs. As a result some pragmatic usage scenarios have been drafted and Outsmart pushed those requirements via the FIWARE dedicated backlog. These activities are expected to have impact in the developments of those components for Release 2.

We have also conducted a series of joint actions to ensure communication and a mutual undestanding. The activity was kicked off back in July 2012 (minutes of meeting on [2]) and has been followed up on subsequent occasions (minutes of meeting of Sept 2012 on [3]).

FIWARE and FINEST

FIWARE Apps chapter and FINEST initiated a collaboration on

  • How to utilize Linked-USDL in order to describe specifc logistics services
  • Mapping the FIWARE GE (e.g. Repository, Marketplace) the FINEST architecture and use cases.

A couple of informal conference calls where conducted. The goal is to come up with sample domain specific service descriptions and a consolidated architecture showing potential use of FIWARE GE.

FIWARE and ENVIROFI

FIWARE Apps chapter and ENFIROFI initiated a collaboration on

  • How to utilize Wirecloud in order to build a flexible Web UI dashboard for managing environmental observations
  • Paper accepted for presentation in “EnviroInfo 2013 (http://www.enviroinfo2013.org)” Conference with the participation of the Apps Chapter: D. Havlik, J. Soriano, S. E. Middleton, H. van der Schaaf, J. Pielorz, C. Granell, A. Berre, “Future Internet enablers for VGI applications”, in Proceedings of the , Hamburg, September 2nd-4th 2013.

A couple of informal conference calls and a dedicated webinar on Wirecloud were conducted. There is also a dedicated mailing list. The goal is to come up with a live demonstrator showing potential use of FIWARE GEs.

Collaboration with other ICT projects and Initiatives

Challenge 1 projects and the Future Internet Assembly

FIWARE does not start from scratch, but capitalizes on many works done by other projects, funded both internally by partners in the consortium, but also by the European Commission. In this last case, technologies related to FIWARE are mainly related to Challenge 1 of the ICT work programme. For those that are not familiar with this wording we can say that Challenge 1 integrates research in the domain of Pervasive and Trusted networks and service infrastructures. Basically, this agglutinates the following topics: networks, cloud computing, internet of services and advanced software engineering, internet connected objects, Trustworthy ICT, networked media and Future Internet Research and Experimentation.

In the first 6 months, FIWARE has mainly focused its attention on those projects that are relevant for the definition and consolidation of Generic Enablers. This involves a list of projects where many partners are working and that feed the technological base of FIWARE.

Besides those initiatives we have been keeping an eye on projects running in parallel to FIWARE. The main intention is to identify potential (additional) enablers and technologies that could be considered by FIWARE but also to coordinate efforts leading to a better result for Europe. For example, some projects are defining roadmapping exercises that could help FIWARE in the future Open Calls, or they may be suggesting communication protocols (to give an invented example) where FIWARE should be involved. Based on the current status of the project we are working in the phase of exploring, understanding and opening communication channels that allow us to collaborate further in the coming months.

One of the roots used for that is the participation in FIA (Future Internet Assembly). Partners in FIWARE have been active in the editions held so far in Budapest (May, 2011): [4] and Poznan (October, 2011): [5]. Check some of the presentations made by FIWARE in this context in the corresponding dissemination section.


FIWARE has also been present in the Concertation and Collaboration meetings organized by the projects in some of the relevant research areas of the project. Specific examples are the ones of:

  • Internet of Services 2011 Collaboration Meeting for FP7 projects (28-29 September, Brussels) [6]
  • Future Networks 8th FP7 Concertation Meeting (6-7 October 2011, Brussels) [7]


While in some cases the collaboration is really tigth reporting FIWARE results periodically and influencing when possible those projects (that could be the case of the EFFECTS+ CSA, in the Security Area), in some other cases the collaboration is at its early stage and under analysis so that we can focus our resources on those ones that will really make an impact.

FIWARE will analyse the possibilities of concrete collaboration with projects represented there besides the ones already identified. For example, we have already started discussions with the CSA Project SOFI to make use of their dissemination activities and channels, as well as with the CSA project HOLA, both of them from the Software and Service Architectures and Infrastructures area. A different kind of collaboration could be triggered by SEQUOIA, which has defined a methodology for impact assessment. We are still at the point of cheking if our impact indicators could be aligned with such methodology and, as soon as some of the GE are released, this work will be revisited to evaluate the possible application of SEQUOIA in the framework of FIWARE.

Even though we have not proceeded with the deployment and testing phase, this will be crucial in future milestones of FIWARE and then we will intensify our relationship with the FIRE Community. Check below connections already made as first attempt to collaborate with this community.

For those interested in more concrete collaborations at technical level with some of the projects that are part of our baseline or detected as future source for collaboration you can visit the specific sections of the wiki created for each technical chapter of FIWARE or read some of the notes that we have compiled below for you:

Do you want to know about related Research projects? Go on reading...

  • In the case of the Service marketplace, we focus our attention on those projects that have been taken as starting point for the FIWARE assets.
    • Asset:USDL
      • The TEXO project within the THESEUS pogram initiated by the German Federal Ministry of Economics and Technology (BMWi)
      • German Federal Ministry of Education and Research projects (BMBF) Premium Services
      • EU European Commission, DG INFSO projects FAST, RESERVOIR, MASTER, SERVFACE, SHAPE, SLO@SOI, and SOA4ALL
      • The Australian Smart Services GRC.
    • Asset: USDL Markteplace OS: The marketplace was used and further developed in the projects
      • TEXO, Premium Services.
      • Internet of Services Marketplace
      • Premium Services Homepage
    • Asset: Premium-Services Pricing Strategies Simulator
      • PREMIUM Services homepage
    • Asset: Revenue Sharing System
      • 4CAAST
      • BlueVia
    • Asset: Wirecloud Mashup Platform: The Wirecloud Mashup Platform has been used and further developed in the following projects:
      • The EzWeb and Nuba projects within the Avanza I+D program initiated by the Spanish Ministry of Industry, Tourism and Trade.
      • The EC FP7 FAST, RESERVOIR, and 4CaaSt projects.
    • Asset: LighSemantic-enabled Design Time Semi-automatic Service composition
      • Oryx Editor
      • SOA4All Advanced Prototype For Service Composition and Adaptation Environment
FIRE Projects

FIRE is the community associated to the topic 1.6 of the work programme, and stands for Future Internet Research and Experimentation ([8]). The main idea of the FIRE projects is to enable early experimentation and testing in large scale environments.

As you know, FIWARE will set up a testing infrastructure in the project that will be available for third parties to test our components. The test bed will contain an instance of all the GE implemented by the project. But FIWARE will go beyond that by setting up what we have called the Open Innovation Lab. This one will be composed by the FIWARE Testbed plus the FIWARE development Environment. Besides that, Open Innovation methdologies and tools will facilitate that third parties (including SMEs) that are not so technically-skilled can make use of the FIWARE technology and build applications and services on top of the results of the project. This Open Innovation Lab will be available after the second year of the project, and, as you can realize, it will be a joint effort between different Work Packages of the project, involving people working in the development environment, developers community, Open Innovation and exploitation or the testing infrastructure, to name the main teams.

This long term work will take advantage of the efforts of the FIRE community, where some partners of FIWARE are active members.

Some concrete steps have already been taken and are briefly illustrated below:

  • Liason with existing IoT-related FIRE experimental testbeds

FIWARE believes that it would be very relevant for the FIWARE testbed to connect to different IoT-related experimental testbeds, so that applications hosted on the FIWARE testbed can connect and gather data on sensors or act upon actuators that are deployed by these IoT-related experimental testbeds. For this to happen, discussions have already been initiated with OpenLab: [9]. Some of the OpenLab testbeds already under analysis are: [10] and [11]

  • Service experimentation

Even though not explored yet, there are direct roots from FIWARE to the two main projects representing service experimentation and thus covering the different layers of IaaS and PaaS. These projects are TEFIS: [12] and BONFIRE: [13], coordinated by Thales and Atos respectively, both of them partners of the FIWARE consortium.

  • Other FIRE projects

Other projects that may serve for the purpose of testing and experimentation that will be analysed as part of the collaboration roadmap of the project are Experimedia: [14], focused on experiments in live social and networked media experiences and SmartSantander: [15], which provides a relevant experimentation platform where IoT supports the concept of smart cities, in this case deployed in the Spanish city of Santander. Once again this bilateral channel should be easy to manage thanks to the presence and active participation of some common partners, such as Atos and Telefónica respectively. While in the case of OpenLab, TEFIS, BONFIRE there is a clear relationship with the experimentation of the technology of FIWARE, experimentation platforms like SmartSantander or Experimedia may be used for testing through Use Cases projects that fall under the relevant domains they represent (that could be the case of OutSmart and FI-Content). This is not clear yet to us and therefore this is an ongoing analysis that will be pursued later in the project.

The FInES Cluster

FInES ([16]) stands for Future Internet Enterprise Systems. This cluster was generated in the framework of RFID and Interoperability projects that were originally funded by the current topic 1.3 of the WP. Since recently it has been moved to the environment of Factories of the Future (FoF) projects (and specifically topic 7.3 of the WP). Wherever its position is in the set of projects funded by the European Commission the important issue is that it aims at enabling enterprises, including SMEs, by means of ICT, to exploit the full potential of the Future Internet. That falls directly under the main goal of FIWARE. Based on that, collaboration with them is for us mandatory.

From a technological viewpoint, FInES has a strong focus on cross-domain co-operation (web semantics, web content technologies, grids, collaborative environments, service oriented architectures, eGovernment, etc.), and it maintains natural links with standardisation bodies (CEN's eBIF, ICT Standardisation Study, ETSI, etc). Some partners have already made presentations of FIWARE in subsequent meetings (SAP, Atos...) even if contacts are managed through Engineering, which is an active member of the Community. This ended up in a fruitful participation of FIWARE in the Samos 2011 Summit: "Future Internet: The power to change society".

At this moment in the project, the main motivation behind the collaboration with FInES can be summarized as follows:

  • Contribute to the FInES Research Roadmap by reflecting some of the technological challenges identified by FIWARE that will not be solved by the project in its current definition (it may be done through the Open Calls though)
  • Maximize the use of the great channel of FInES towards SMEs. It is the intention of FIWARE to involve SMEs already in the Open Calls (25% of the budget expected to be asigned to this type of organizations, even if it is only an estimation). Besides that, SMEs will play a crucial role in the testing phase of the project regarding the validation and acceptance of the technology. Furthermore, the Open Innovation Lab has been conceived as a tool to promote Open Innovation on top of the APIs released by FIWARE, and here SMEs should be an integral part of this Open Innovation ecosystem.
  • Finally, the impact of the FInES work in several audiences, such as the European Commission, makes this cluster a suitable vehicle for policy contributions

All these activities will be further explored in the coming months and will be extended according to their feasibility and potential impact. It is undoubtful that FIWARE will also keep an eye on the works and publications not only of the integrating projects, but also of the FInES clusters (the complete list can be found in [17].

The AAL (Ambient Assisted Living) Community

It is not a secret that Ambient Assisted Living (AAL) is an interesting application domain that could greatly benefit FIWARE with respect to the process of gathering requirements. It impacts the Internet of Services field, but also comprises many aspects related to Trust and Security and undoubtely it is the perfect showcase for technologies of the so called IoT (Internet of Things).

AAL is not part of the initial set of projects retained by the 1st Call for Proposals of the FI PPP programme as it not eHealth either. Both of them are considered by FIWARE a main source of requirements but also good deployment environments that could really make an impact in terms of FIWARE adoption.

From a technical point of view both of them have very strong requirements in terms of integration, IoT and security. This is complemented by the political and business relevance. While other sectors are fighting to remain competitive to their customers or "invent" new ones, AAL and eHealth do not have to find customers. The Old Europe is providing them for free, and growing continuously. That is the reason why the EC decided to set up Active and Healthy Ageing as the first pilot of the EIP (European Innovation Partnership) instrument.

FIWARE has looked for collaboration with both communities. With respect to AAL many discussions have taken place with the AAL Forum since FIA Budapest. Besides exchange of e-mails and phone calls more active collaboration has taken place, including physical meetings (October 2011) and joint participation in events with the goal of reaching a common understanding about the developments of both communities.

  • The starting point was the presence of FIWARE and AAL in the Third Usage Area Workshop organized by the CONCORD and EX-FI projects (June 2011, Brussels). There FIWARE made two presentations (see dissemination section; speeches by Thierry Nagellen, Orange-FT and Nuria de Lama, FIWARE) and AAL contributed to the discussion trying to check the way both platforms -FIWARE and the one pushed by the AAL community- could be made interoperable.
  • This interaction has a follow up these days in Amsterdam, thanks to the participation of FIWARE in the "Workshop on Integration of AMI and AAL Platforms in the Future Internet Initiative" (November 16, Amsterdam). This invitation by AAL brings FIWARE to the forefront of the discussions and one of the FIWARE representatives (Thierry Nagellen, from Orange-FT will present FIWARE GEs to the audience and will participate in the two panels: one of them focused on technical aspects while the other one will be more generic by addressing wider opportunities of collaboration between AAL and FI.

Check further information about this in the dissemination section of the wiki, where you can find links to the presentation and panels and in [18]

The CELTIC Cluster

FIWARE has established an special collaboration agreement with CELTIC projects. This collaboration is assured by the presence of several representatives at the PCC of FIWARE and at the CELTIC Steering Board.

This collaboration allows CELTIC projects to contribute effectively to the process of Materializing the FIWARE Vision due to direct access to the FIWARE log-book (process still under definition).

At present, the collaboration with the PISCES project is the first example, but it is expected new projects in the coming CELTIC call will extend the use of the FIWARE platform.


  • The PISCES Project: seed for CELTIC collaboration

PISCES is a collaborative project aiming to Promote future Internet Solutions in health EnviromentS. It complements then other use cases funded by the PPP by bringing some requirements that are specific of this sector. It also adds to the collaboration already in place with the AAL community. The project has partners that represent different countries, such as Turkey, Spain, Germany, Slovenia and Hungary. Its main objectives can be summarized as follows:

  • A comprehensive set of detailed technical functional and non functional specifications
  • The identification of enablers and architectural requirements to deliver FI applications in the health domain
  • Development of conceptual prototypes
  • Drafting of a strategy towards contributing to standardization in the respective application fields defined by the project

As it can be seen, its results are expected to be relevant for the PPP in general and FIWARE in particular. The project was defined taking into consideration the collaboration process of FIWARE, the same milestones and the same kind of interactions. Collaboration should be eased by this, but it has not been effective till now because the consortium is still waiting for a response by the Turkish Administration. Meanwhile, FIWARE has provided some general information to them to keep PISCES in the loop.

ETP (European Technology Platforms)

Several actions have been taken so far with respect to European Technology Platfoms having two goals in mind:

  • Collaboration in terms of technical development, it is to say, it is especially important that FIWARE uses the channnel of the ETPs to synchronize research roadmaps and to get information about developments that could be interesting for FIWARE coming from the different initiatives. The other direction is also valid, since FIWARE results have to be promoted in those environments to:
  • Motivate the use of the APIs created by the project (for business and validation)
  • Get the interest of the development community to FIWARE (engaging new stakeholders and increasing the community around the project)
    • The last point is related to the motivation of third parties to participate in the Open Calls

ETPs have big communities behind them, and as such, they are powerful tools for dissemination and policy actions (for example, most of them have opportunities to talk in the Parliament and even to explain their ideas to the Commissioner for the Digital Agenda Mrs. Neelie Kroes).

FIWARE has specifically worked with NESSI (European technology Platform on Software and Services), Net!Works (European Technology Platform for communications networks and services, formerly called eMobility) and ISI (the Integral SatCom Initiative) .

While channels with the networking and services aspects are clear in FIWARE it is more difficult to establish the collaboration with the satellite community. So far it has been based on sending information and informing organizations about what FIWARE is about, its progress and the coming Open Call. Their main motivation is to get involved in Future Internet and we will analyse in the future if satellite communications are needed in this environment. At this very moment that is not envisaged and we believe different use cases should enter the game to make that sensible (such as disaster management, earth observation or applications such as ehealth or education in remote areas, where satellites could provide a more reliable infrastructure that could act as back up for mobile networks. An illustrative example of situation where this could be useful is the disaster happened in Fukushima, where communication infrastructures were seriously damaged because of the tsunami and the nuclear disaster).

See related presentations in the dissemination section of the wiki.

  • Net!Works General Assembly (5 October, Brussels): presentation of FIWARE and its relation to the Usage Areas ([19])
  • 4th ISI SatCom Day (18-19 October, Brussels): presentation of FIWARE in the First Panel titled "ISI & Future Internet: Is there a role for Satellite in Future Internet?”

You can also stay tuned about FIWARE in the newsletters published by some of these initiatives: See for example last newsletter published by NESSI: [20]

EnoLL (European Network of Living Labs)

The collaboration with EnoLL is expected to happen mainly when first technical results of FIWARE are available (at least first release of the GE). EnoLL is once again, as described in some of the previous initiatives a good channel for several purposes:

  • Increasing the audience and interest about FIWARE (therefore good for dissemination and wider adoption of the results)
  • Involve and engage SMEs
  • And finally, applying some of the experiences acquired by EnoLL regarding user involvement in the Innovation process.

Some discussions have already taken place in the context of the methodologies that could be applied in FIWARE to involve final users early enough in the process and therefore ensure the rigth validation of the technology and its adoption afterwards, which will clearly be based on the acceptance by the user. This knowledge will be applied to the definition and setting up up of the Open Innovation Lab. FIWARE relies on CONCORD to define the collaboration agreement that makes possible in an easy way a further exchange of information with external communities. Even though most results are public, still a collaboration agreement regulates the responsibility and nature of the collaboration between companies, projects and initiatives. EnoLL is very experienced in this and we are confident that it will be a very valuable source of information for the coming project phase.

We may mention the following concrete interactions:

  • Future Internet PPP: Opportunities for Smart Cities and SMEs
    • Description: we had a meeting with the Malaga Town Council to show the opportunities that the programme offers to cities and SMEs. Málaga became an ENoLL member in the ENoLL 5th wave (2011), as publically announced during the Future Internet Week in Budapest in May 2011
    • Date: March 20th 2012
    • Location: Malaga City Council, Innovation and New Technologies Department
    • Agenda: Málaga Town Council Agenda
    • Presentations: Malaga Town Council Presentations
    • Partners involved: TID,ATOS

EIT ICT Labs

EIT ICT Labs KIC ([21]) was designated as a Knowledge and Innovation Community by the EIT's Governing Board on 16 December 2009 in Budapest. The priority area which the ICT Labs KIC addresses is future information and communication society. The initiative focuses from an operational point of view on education, promotion of innovation, coordination of research and development actions and business. In order to open up this business ecosystem and the developed technologies to organisations, notably SMEs, external to the FI-PPP initiative, some of the FI-PPP members decided to set-up a close collaboration between the EIT ICT Labs initiative and FIWARE. This collaboration will build on top of existing synergies between research and business innovation in the European ICT sector. The combination of the EIT ICT Labs and FI-PPP initiatives will support in an optimal way a concrete and broad adoption of the existing technological solutions by SMEs external to the FI-PPP programme. The outcomes of this approach aim at boosting the adoption of Future Internet technologies within SMEs, Public Administrations, and visionary individuals with the goal of creating new innovative businesses and new job opportunities.

The EIT ICT Labs - FI-PPP Liaison project is designed to provide the access and support the usage of FIWARE technologies within three phases:

  • Phase 1: Adoption of the FIWARE technologies as a playground where to inject new technologies (notably service marketplace at large, cloud computing, security, interface to network devices) and build new services on top of those
  • Phase 2: Instantiation of the FIWARE Testbed in specific territorial or living labs where to run real and highly impacting use cases.
  • Phase 3: Organization of dedicated workshops with entrepreneurs, notably SMEs, researchers and other relevant ICT stakeholders


Goal

The EIT ICT Labs - FI-PPP Liaison project intends to establish mutually beneficial links between the FI-PPP and the EIT ICT Labs initiatives. The current version of the FIWARE Testbed focused predominantly on the “research related evaluation” of the FIWARE Technologies. The link with ICT Labs initiative will enable the establishment of a FIWARE Testbed that allows for a “business”-based evaluation of FIWARE Technologies within well focused domains, including “Cloud-Computing” and “Smart Cities” to form the EIT-Testbed. The project will open the EIT-Testbed to SME partners and allow a complete and realistic business integration of the FIWARE technologies into their business solutions so as to provide new Future Internet Applications or new Business Model Approaches within the given domains.

Promising ideas of how the FIWARE WP3 Application and Services Generic Enablers can be used in the cloud computing area already exist and may be evaluated by external project partners with special focus on suitability for mass adoption. A first demo scenario making use of SAPs service marketplace technologies was already defined and implemented prototypically.

PanlabII Project

PanlabII [[22]] addresses the need for large-scale testing facilities in the communications area by implementing an infrastructure for federating testbeds. The PanlabII project uses the concept of European innovation clusters and builds on the existing testbeds that are supporting scientific and technological endeavour within these clusters. The central objective of PanlabII is to create a testbed federation among these regional innovation clusters in Europe. This will enable companies participating in these clusters to test new communication services and applications across Europe. The testbed federation includes four core innovation clusters and three satellite clusters.

The PanlabII tools might be a good infrastructure and environment to interconnect the several trial and test sites of FIWARE. Therefore it is not necessary to ship physical nodes to other locations of FIWARE partners and Use Case project partners. Especially it is necessary in “Interface to Network and Devices” to have such an environment because the implementations are done and will work on different partner locations.

Several meetings took place in spring 2012. The discussion is on-going and is not finalised.

Normal 0 false false false EN-US X-NONE X-NONE

ETICS Project

ETICS [[23]] aims at creating a new ecosystem of innovative QoS-enabled interconnection models between Network Service Providers allowing for a fair distribution of revenue shares among all the actors of the service delivery value-chain. The project will analyse, specify and implement new network control, management and service plane technologies for the automated end-to-end QoS-enabled service delivery across heterogeneous carrier networks. ETICS includes a large number of partners that, participating to several key projects, have matured strong expertise. ETICS prototypes on control, management, and service planes will also leverage an important background on implementations and performance assessment. They will allow demonstrating and testing the effectiveness of new business models as well as how agile network service creation, activation, monitoring and billing for interconnected fixed and mobile operators will improve time to market of new services and reduce operational costs and complexity.

In the framework of the cooperation, the FIWARE/I2ND-Team (especially the network control tasks) and the ETICS team have started a discussion. Goal is to get an understanding for the interfacing between different network service providers and to check the possibility to use implementation of ETICS in FIWARE.

The first round table discussion took place in Berlin, Germany, 22-26 October, 2012. The cooperation and discussions are ongoing.

MEDIEVAL Project

MEDIEVAL (MultiMEDia transport for mobIlE Video AppLications) is a 'Small or medium-scale focused research project' (STREP) of the 7th Framework Programme of the European Commission, addressing the core of the strategic objective "The Network of the Future". MEDIEVAL aims at evolving the Internet architecture for efficient video transport. To achieve this, a cross-layer design is followed. The project has started on 01.07.10 and will last 3 years.

Important means to enable efficient video transport over the Internet are network protocols suitable to make applications aware of the situation in a network, e.g. reachability or traffic load. In this context, the MEDIEVAL project actively contributes to the development and standardization of the IETF ALTO protocol. The ALTO protocol provides guidance to applications that offer the choice among several application endpoints to trade resources with, on which endpoint to select.

Through the collaboration of FIWARE and MEDIEVAL, the development of interface functionalities in task 7.3 of FIWARE will benefit from work already performed on ALTO protocol client functionality within the MEDIEVAL project. On the other hand, MEDIEVAL will benefit from feedback on and improvements of the ALTO protocol client functionality gained in the course of the integration into the FIWARE Generic Enabler and from application tests performed in the FIWARE testbed.

Webinos

Webinos ([24]) is an FP7 Call 5 ICT Project which aims to deliver a platform for web applications across mobile, PC, home media (TV) and in-car (IVI) devices. It has over twenty partners, both industrial and academic. The project is due to conclude in August 2013.

Both Webinos and FIWARE’s Connected Device Interface (CDI) Generic Enabler (GE) have overlapping goals. Both intend to bring a common platform for application developers to many device types. FIWARE and Webinos recognise the opportunities to collaborate, specifically that FIWARE can utilise the code and other deliverables provided by Webinos as a major building block for the FIWARE CDI GE.

As the CDI GE builds upon Webinos the CDI team will introduce new extensions, modifications, and changes to ensure that the resulting output meets all the use cases and requirements already laid out for the CDI team.

During this process the CDI team will learn more about Webinos, and identify areas in which Webinos could be extended. It is envisaged that this knowledge will be shared back with the Webinos team in the form of combination of informal verbal feedback, and more formal communication of suggested additional API, specifications, and code.

FIWARE / Webinos Engagement History
  • October 2011: FIWARE made contact with Webinos and exploratory conversations took place.
  • December 2011: The CDI team formally signalled to the I2ND task lead of the team’s intention to introduce Webinos assets into the FIWARE project. The CDI team request and obtain consent from FIWARE project lead.
  • March 2012: The CDI team provided Webinos with an updated version of the Webinos Contacts specification document which provided additional functionality.
  • May 2012: Webinos provide the FIWARE team (CDI) with access to the Webinos source code repository
  • June 2012: FIWARE attend official Webinos public release meeting (Ghent)

MSEE (Manufacturing Service Ecosystems)

The IP-Project "MSEE" (Manufacturing Service Ecosystems) [25] in the "Factories of the Future (FoF)" Call of the 7th Framework Programme / Objective 7.3 "Virtual Factories and Enterprises") works in the area of new Virtual Factory Industry Models and Future Internet Enterprise Systems and has been inspired by FINES Cluster activities. MSEE develops concepts, platforms, and technology for service ecosystems in the manufacturing domain. MSEE builds on the notion of a Future Internet Service Platform as developed by the FIWARE project.

We collaborate with MSEE by providing information on the relevant Generic Enablers which are relevant for re-use in the MSEE project. The idea is to evaluate if and how generic enablers (and their reference implementations) can be used in the MSEE project to realaize novel technologies on top of them with an added business value in the manufacturing context. In MSEE, USDL language and USDL-based tools were evaluated.

In the reporting period, the LinkedUSDL Editor was extended to allow imports of MSEE models for the generation of USDL service description skeleteons. The usage of store and marketplace are planned in MSEE. Prior to that (reported in last quarter also), in this context, several tutorials on USDL technology (Linked USDL description language, USDL editor, and other related tools) have been given by the FIWARE team (FIWARE WP3 Apps and Services - SAP). MSEE requests for detailed information have been answered by the providers of the generic enablers of interest.

Broker@Cloud (Enabling Continuous Quality Assurance and Optimization in Future Cloud Service Brokers)

As enterprises increasingly adopt the model of cloud computing, their IT environments are transformed into a matrix of interwoven infrastructure, platform and application services delivered by multiple providers. To deal with the complexity of consuming large numbers of cloud services from diverse sources, enterprises will need assistance from specialised cloud service delivery intermediaries. These will need to offer an array of sophisticated brokerage services which will go far beyond the kinds of intermediation capabilities available today.

The challenge taken up by the FP7 project Broker@Cloud is to research and to develop solutions with respect to some of the most valuable and technically demanding types of brokerage capabilities foreseen for future enterprise cloud service brokers.

The brokerage framework, most of which will be released as Open Source Software, will comprise the following core building blocks:

  • Capabilities for cloud service governance and quality control (lifecycle management, dependency tracking, policy compliance, SLA monitoring, certification testing)
  • Capabilities for cloud service failure prevention and recovery (event monitoring, reactive and proactive failure detection, adaptation analysis and recommendation)
  • Capabilities for continuous optimization of cloud services (optimization opportunity detection and analysis based on cost, quality, or functionality preferences)
  • Interfaces and methods for platform-neutral description of enterprise cloud services (technical, operational and business aspects, static and dynamic views)

LinkedUSDL is considered as the favorite candidate for the main anchor interlinking different aspects of enterprise cloud services descriptions in a platform-neutral fashion. Service description aspects specific to Broker@Cloud framework and not already covered by Linked USDL specification will be addressed through extensions.

Joint efforts between Future Internet Initiatives at National and International Level

TrustedCloud

TrustedCloud is an initiative of the German Ministry of Economics to support secure and safe cloud computing for small and medium enterprises and public sector. Part of this initiatives are 14 projects tackling various aspects of secure cloud computing for SME. Five of the projects have a need for a unified service description language and components of a business platform. SAP (Dr. Torsten Leidig) presented USDL and FIWARE GE in a keynote at the TrustedCloud Standards Workshop on May 9th, 2012 at the Karlsruhe Institute of Technology (KIT). Part of the workshop was also a breakout session on standards for service description where the requirements and the potential use of USDL and FIWARE technology was discussed. Namely the projects Value4Cloud, goBerlin, SensorCloud, TRESOR expressed their interest in furter collaboration and contribution to linked-usdl.org and therefore working together with FIWARE WP3 (Applications and Services Ecosystem). A follow-up workshop took place on 29.08.2013, in which partners of the PeerEngergy-Cloud, TRESOR, CLOUDWerker, Value4Cloud and cloud4health projects as well as representatives form the German Ministry of Economics (BMWi) and Deutsche Luft und Raumfahrt (DLR) particpated to discussed aspects of extension and integration of dedicated vocabularies for Cloud Services into Linked USDL. Furthermore the FIWARE Open Innovation Lab was presented.

German Software-Cluster

The German Software-Cluster (http://www.software-cluster.com/en/) is based in the southwest of Germany. Numerous universities, companies and research institutions work closely together in and around the key software development centers within this region, which includes Darmstadt, Karlsruhe, Kaiserslautern, Saarbrücken and Walldorf. Together they develop trend-setting corporate software for the future. The Software-Cluster has already won an accolade in relation to the "Leading-Edge Cluster" competition initiated by the German Federal Government. One of the main objectives of the Software-Cluster projects is the enablement of small- and medium enterprises (SME) to play an essential role in business related software development. Here, especially, the development and distribution of innovative software services are in the focus. The projects within the Software-Cluster realized that USDL is very important for describing services in a comprehensive fashion, both for exploitation purposes but also for making the services comparable to each other. Based on requirements (coming from the software industry and the logistics domain, in cooperation with representatives from a partner cluster) an cloud-based editor has been developed that fulfills the special needs of SMEs. The work here was accompanied by various activities, for instance common workshops of partners representing different expertise and domains (see http://www.linked-usdl.org/node/227 as an example) - such as logistics or software engineering. Furthermore technical mechanisms for (semantic) service discovery, service storage and service publication will be implemented in order to easen the exploitation capabilities of services. FIWARE contacts: WP3 (Applications and Services Ecosystem)

es.Internet

FIWARE has established a collaboration with the Spanish Platform es.internet whose objectives are

  • Ensuring coherence of action and avoid fragmentation of efforts economies of scale to have a sound competitive position
  • Promoting the collaboration between industry and academia ensuring better planning, with special focus on SMEs, who could benefit of the traction effect
  • Guaranteeing continued funding from the public administration allow a long-term investment in R+D+i reducing the associated risks.
  • Raising awareness of the importance of the development of Internet showing the applicability of the net in many social services which might greatly enhance their quality of life.
  • Improving the regulatory framework, Ensuring interoperability of systems, terminals and networks facilitating the standardization work.
  • Promoting internationalization of Spanish industry participation in international R&D programmes.

Particular attention is given to the promotion of PPP activities within Spain and try to assure the maximum impact of the results into the Spanish industrial landscape. A list of Spanish projects and actions related to the PPP has been produced[26]


This industrial platform was formed several months ago and already counts with a very important participation of Spanish Industry with more than 400 members.

The platform has recently held the IV General Assembly in a very significant event with presence of the highest representatives of the Spanish administration [27]. A central element of the event was the three presentations made by FIWARE [28], [29] [30] where the main objectives and current activities were summarized

Latin American Platforms and Future Internet

The last edition of FIA (Poznan) was quite useful for FIWARE to initiate further cooperations that were not initially considered in the project. That has happened for example around Future Internet Initiatives in Latin American countries. The EU-funded project FIRST ([31]) promotes the cooperation between Europe and Latin America in the field of Future Internet and ICT components. Poznan gave us the opportunity to express our views in the second session of the FIRST meeting (Session 2: The European Perspective on the International Cooperation with Latin America; check further information in [32]).

This opens the following potential channels for FIWARE (even if they have to be explored to check the alignment with the FIWARE strategy):

  • PLATA: The Argentine Future Internet Technology Platform ([33])
  • MACHI: The Chilean Technology Platform of Future Internet ([34])
  • RECIIF: The Colombian Future Internet Technology Platform ([35])
  • BRA-FIP: The Brazilian Future Internet Technology Platform ([36])
  • the Mexican Future Internet Technology Platform (still under definition)


LoFIP - Logistics Future Internet Platform

The German Hightech.NRW project "LoFIP - Logistics Future Internet Platform" has the goal of developing a software platform enabling an easy realization of software-based, federated control centers for operative logistics processes, based on innovative Future Internet technologies.

The FIWARE WP3 Application and Services Chapter is supporting LoFIP in adopting SAPs Marketplace Generic Enabler for a logistic-specific use case which demonstrates how challenges during daily tours of parcel collection at business customers can be better solved with the means of FI-enabled Control Centers, thus e.g. including the resolution of ad hoc transport needs through integration of access to spot markets for transport capabilities into the control center

Further information can be found under: http://www.lofip.de

Other

As it can be seen in the Dissemination section some presentations have been made at International level. FIWARE has not yet defined an strategy for International cooperation, has it has been mentioned in this document, but all the opportunities that are appearing make us believe that there could be a good business case there. So far we have accepted invitations to disseminate and promote the projects and its results so that we can keep the interest and the attention of the research community that could be -later on- contacted for the purpose of evaluation and validation of the FIWARE GE and APIs.

Brazil seems specially interesting for this (so far, besides the connection through the Latin American platforms our collaboration has been triggered by research in Trust and Security: see presentation made at the BIC Workshop in the IWT 2011). [37]

In the remaining part of 2011 there are plans to present our activities in the coming BIC workshops that will be held in South Africa ([38]) and India ([39]).

Other interesting topic that FIWARE has followed in the last months is the one of Smart Cities. We think that the technology and the platform provided by FIWARE will be a very relevant asset for the development of Smart Cities applications. Furthermore, some of the technology pillars of FIWARE are the ones that people usually associate to this Smart City concept (ex. IoT). In the last months there have been events around a possible EIP on Smart Cities. This iniative as such is mainly run by DG Energy and DG TRANSPORT, even if DG INFSO is the third "leg" of the "animal". FIWARE will try to work at political level to make an impact on the current development of that concept and make it become a more generic one, where applications on energy efficiency and transport are complemented by egovernment services to citizens and public servants, services on education, tourism, safety and many other fields that take place in the context of cities and their citizens. Integration, interoperability and Interaction are words starting with "I" that make clear that another word starting with "I", ICT, should be the basis for all these developments. FIWARE will go on pushing these ideas in the future.

Personal tools
Create a book