large-scale integrated project (ip) · private public partnership project (ppp) large-scale...

Private Public Partnership Project (PPP)

Large-scale Integrated Project (IP)

D.11.2.3: FIWARE Exploitation plan including IPR Management

Project acronym: FIWARE

Project full title: Future Internet Core Platform

Contract No.: 285248

Strategic Objective: FI.ICT-2011.1.7 Technology foundation: Future Internet Core Platform

Project Document Number: ICT-2012-FI-285248-WP11-D.11.2.3

Project Document Date: 2014-31-12

Deliverable Type and Security: PP (Private)

Author: Juan Bareño

Contributors: FIWARE Consortium

Future Internet Core Platform

D.11.2.3: FIWARE Exploitation Plan including IPR Management 1

1.1 Executive Summary

This deliverable, and the final iteration of the Market Analysis D11.1.3, fit the full roadmap for FIWARE

sustainability development and together with the Third Party Innovation and the State of the Art will

represent our blueprint to make FIWARE a sustainable service with a thriving community.

Deliverable 11.2.3 Exploitation Plan elaborates on discussion among partners regarding exploitation and

sustainability plan of FIWARE and on the Market Analysis main outputs or conclusions.

The structure of this deliverable is the following:

- Firstly, based on the State of the Art described in D11.1.3 we described the main features and

advantages:

- Per building block that FIWARE brings.

- As a whole, platform positioning.

- Secondly, FIWARE Exploitation Strategy Definition based on Market Analysis inputs

- Definition of the main pillars

- Ecosystem creation: the desired ecosystems described in the Market Analysis

- Community Building: attract a large community of developers and users

- Useful Tools: feedback (JIRA), involvement through Social Networks (Campuseros)

- Third, FIWARE LAB modus operandi:

- Open Source Business models, which might fit with FIWARE, have been evaluated and a

discussion has been initiated within the consortium to share a common view on FIWARE

exploitation plans.

- IPR Management: FIWARE will exploit components relationships also for allowing a more

efficient and accurate analysis of licence compatibility and to provide well founded legal

argumentation

- Finally, a first set of sustainability strategies are presented together with some indication that

should inform the action to develop a working community around FIWARE. A very successful and

proven model is the concept of a Foundation

Furthermore, we provide the individual exploitation plans from the partners focusing on commercial

launch, trying to reflect the more tangible business view of the industrial partner and a lot more

substantive in describing the planned integration of the FIWARE outcomes into the mainstream business

of the industrial partners

On the whole, the success of FIWARE is likely to depend on whether or not the main participants to the

project will become the magnets that will attract a large community of developers and users. FIWARE

participants are among the largest IT technology providers and spenders in Europe and comprise a few of

the largest systems integrators and application developers. Therefore if they were to use extensively the

deliverables of this project, then their suppliers, developers, users etc. would have to follow, creating

the desired ecosystems described in the Market Analysis



1.2 About this Document

This document uses the market and competition analysis of D 11.1.3 as a basis for preparing an overall

strategy for the exploitation of the project’s results. This strategy is essential to coordinate the

exploitation of the individual partners’ achievements and results.

This deliverable also matches the periodic release of exploitation plans, including the overall approach of

the project as well as individual exploitation plans.

Final part of the exploitation strategy is the setting up of an Open Innovation Lab around the FIWARE Test

bed, and secondly analysis and definition of sustainability models for FIWARE beyond the boundaries of

the PPP.

1.3 Intended Audience

As this deliverable contributes to defined FI-PPP Programme level activities the perspective and needs of

FIWARE and the FIWARE consortium and related stakeholders are the addressed audience. As the

dissemination level is "PP" (FI-PPP private) there is no plan to release this document to external parties.

1.4 Context of Chapter WP11 Exploitation

This work package focuses on a series of activities that identifies, create and work towards the

exploitation and standardization opportunities of the FIWARE project results. This work package

approaches exploitation of the FIWARE results from the point of view of the partners of the FIWARE

consortium, both individually and as a project. It does not intend to replace or overlap exploitation

activities at the Future Internet Public Private Partnership Programme level, but to complement in a

synergetic way the work that other projects within Usage Areas will do in terms of take up of the generic

enablers provided by FIWARE., therefore complementing the perspectives of the partners of this project

and the related stakeholders in the ecosystems they represent.

The exploitation of FIWARE results is not based on a purely technological approach (technology push) but

on the needs and requirements of the future “customers” and “users” of FIWARE enablers. As a result,

both supply and demand are meet within this WP.

With that in mind the project’s exploitation activities have as main objectives the:

- Definition of project outcomes from an exploitation point of view, including identification of

stakeholders and different typologies of users that will make use of FIWARE

- Systematic analysis and continuous monitoring of market situation and trends

- Definition of overall and individual exploitation plans

- Definition of a framework for IPR and licensing management

- Definition of a Sustainability Plan for FIWARE results

- Policy and Regulation Considerations

- Feedback of adjustments to project plan if necessary and promotion of the FIWARE Testbed as an

Open Innovation Lab

- Business oriented communication and training activities to increase market awareness and

impact

- Definition and implementation of a standardization strategy that will enable adoption and

achievement of the project goals and ambitions

- Definition of impact indicators and management of those along the project duration



This WP also supports and runs the project-level Standardization Committee that is in charge of the

overall strategy, planning and execution of the Standardization activities.

1.5 Acknowledgements

The current document has been elaborated using a number of collaborative tools, with the participation

of Working Package Leaders and as well as those industrial partners’ business people in their teams they

have decided to involve.

1.6 Keyword list

FIWARE, PPP, Market Analysis, Generic Enabler, I2ND, Cloud, IoT, Data/Context Management,

Applications/Services Ecosystem, Delivery Framework , Security, Developers Community and Tools , ICT,

IPR, Sustainability, Exploitation, Business

1.7 Changes History

Release Major changes description Date Editor

0.1 Table of Contents 19/03/2014 Juan Bareño (Atos)

0.2 First Version 30/03/2014 Juan Bareño (Atos)

0.3 Contribution from Leaving Partners 30/05/2014 All leaving partners

0.4 Second Version 30/06/2014 Juan Bareño (Atos)

0.5 Third Version 30/09/2014 Juan Bareño (Atos)

0.6

Contribution from Security Chapter 05/11/2014

Daniel Gidoin, Pascal

Bisson, O. Bettan, Cyril

Dangerville (THALES)

0.7 Contribution from Apps Chapter 25/11/2014

Alessandra Toninelli (E-

IIS) as chapter leader

0.8 Contribution from I2ND Chapter 12/12/2014

PierAngelo Garino

(Telecom Italia)

0.9 Contribution from IoT Chapter 15/01/2015

Thierry Nagellen

(Orange)

0.10 Fourth Version 23/01/2015 Juan Bareño (Atos)

0.11 Final Review

29/01/2015 Juan Bareño (Atos) and

Miguel Carrillo (TID)

0.12 Final Deliverable 30/01/2015 Juan Bareño (Atos)



1.8 Table of Contents

1.1 EXECUTIVE SUMMARY ............................................................................................................................................................. 1 1.2 ABOUT THIS DOCUMENT ......................................................................................................................................................... 2 1.3 INTENDED AUDIENCE .............................................................................................................................................................. 2 1.4 CONTEXT OF CHAPTER WP11 EXPLOITATION .............................................................................................................................. 2 1.5 ACKNOWLEDGEMENTS ............................................................................................................................................................ 3 1.6 KEYWORD LIST ....................................................................................................................................................................... 3 1.7 CHANGES HISTORY ................................................................................................................................................................. 3 1.8 TABLE OF CONTENTS ............................................................................................................................................................... 4 1.9 TABLE OF FIGURES .................................................................................................................................................................. 5 1.10 TABLE OF TABLES ................................................................................................................................................................... 6

1. GENERAL INTRODUCTION AND BACKGROUND......................................................................................................................... 7

2. WHAT IS FIWARE? ...................................................................................................................................................................... 9

2.1. CLOUD HOSTING .................................................................................................................................................................... 9 2.1.1. Main Packages/Bundles ............................................................................................................................................. 10 2.1.2. Business Capabilities ................................................................................................................................................. 11 2.1.3. Market Positioning ..................................................................................................................................................... 12 2.1.4. Potential Usage Scenarios .......................................................................................................................................... 13

2.2. DATA CONTEXT MANAGEMENT .............................................................................................................................................. 14 2.2.1. Main Packages/Bundles ............................................................................................................................................. 18 2.2.2. Business Capabilities ................................................................................................................................................. 18 2.2.3. Market Positioning ..................................................................................................................................................... 19 2.2.4. Potential Usage Scenarios .......................................................................................................................................... 20

2.3. INTERNET OF THINGS ............................................................................................................................................................ 22 2.3.1. Main Packages/Bundles ............................................................................................................................................. 23 2.3.2. Business Capabilities ................................................................................................................................................. 24 2.3.3. Market Positioning ..................................................................................................................................................... 25 2.3.4. Potential Usage Scenarios .......................................................................................................................................... 26

2.4. APPLICATIONS ..................................................................................................................................................................... 27 2.4.1. Main Packages/Bundles ............................................................................................................................................. 28 2.4.2. Business Capabilities ................................................................................................................................................. 29 2.4.3. Market Positioning ..................................................................................................................................................... 30 2.4.4. Potential Usage Scenarios .......................................................................................................................................... 32

2.5. INTERFACE TO NETWORKS AND DEVICES ................................................................................................................................... 41 2.5.1. Main Packages/Bundles ............................................................................................................................................. 43 2.5.2. Business Capabilities ................................................................................................................................................. 43 2.5.3. Market Positioning ..................................................................................................................................................... 44 2.5.4. Potential Usage Scenarios .......................................................................................................................................... 45

2.6. SECURITY............................................................................................................................................................................ 46 2.6.1. Main Packages/Bundles ............................................................................................................................................. 48 2.6.2. Business Capabilities ................................................................................................................................................. 49 2.6.3. Market Positioning ..................................................................................................................................................... 50 2.6.4. Potential Usage Scenarios .......................................................................................................................................... 51

2.7. FIWARE PLATFORM POSITIONING ......................................................................................................................................... 52 2.7.1. FIWARE Platform ..................................................................................................................................................... 53 2.7.2. FIWARE Business Canvas and SWOT ...................................................................................................................... 53 2.7.3. Market Positioning ..................................................................................................................................................... 55 2.7.4. Value Proposition: Why FIWARE? ........................................................................................................................... 57

3. FIWARE EXPLOITATION STRATEGY: OPEN APIS FOR OPEN MINDS ........................................................................................ 59

3.1. FIWARE IS THE CORE PLATFORM ........................................................................................................................................... 60 3.2. FIWARE-LAB: A TRUE OPEN INNOVATION ECOSYSTEM .............................................................................................................. 61 3.3. FIWARE OPS TO EXPAND GEOGRAPHICALLY THE FIWARE LAB ................................................................................................... 63 3.4. FIWARE TOOLS .................................................................................................................................................................. 63 3.5. FIWARE BUSINESS ECOSYSTEM MODELLING ............................................................................................................................ 64 3.6. FIWARE TARGET.............................................................................................................................................................. 68 3.7. FIWARE COMMUNITY ......................................................................................................................................................... 69

4. FIWARE LAB: IPR MANAGEMENT ............................................................................................................................................ 71



4.1. FIWARE LICENSING STRATEGY .............................................................................................................................................. 71 4.2. MULTI LICENSING ................................................................................................................................................................. 72 4.3. LICENSE STATUS OF FIWARE GEIS ON FIWARE LAB ................................................................................................................ 72

4.3.1. FIWARE Catalogue ................................................................................................................................................... 73 4.3.2. FIWARE Tools .......................................................................................................................................................... 74

5. FIWARE BUSINESS MODEL ....................................................................................................................................................... 75

5.1. SERVICE/PLATFORM PROVIDER............................................................................................................................................... 75 5.2. BUSINESS CASE .................................................................................................................................................................... 76 5.3. BUSINESS MODEL ELEMENTS ................................................................................................................................................... 76

6. ACTION PLAN FOR PLATFORM SUSTAINABILITY ..................................................................................................................... 78

6.1. GOVERNANCE RULES ............................................................................................................................................................ 79 6.2. PHILOSOPHICAL APPROACH .................................................................................................................................................... 80 6.3. MISSION ............................................................................................................................................................................ 81

7. CONCLUSIONS .......................................................................................................................................................................... 82

ANNEX 1 INDIVIDUAL EXPLOITATION PLANS.................................................................................................................... 84

1. TELEFONICA I+D ....................................................................................................................................................................... 84 2. SAP AG ................................................................................................................................................................................. 89 3. IBM RESEARCH - ZURICH ......................................................................................................................................................... 116 4. THALES COMMUNICATIONS & SECURITY SA (EX THALES COMMUNICATIONS SA) ................................................................................ 125 5. TELECOM ITALIA S.P.A. ........................................................................................................................................................... 140 6. FRANCE TELECOM SA ............................................................................................................................................................... 146 7. NOKIA SOLUTIONS AND NETWORKS MANAGEMENT GMBH, NOKIA SOLUTIONS AND NETWORKS KFT ......................... 148 8. DEUTSCHE TELEKOM AG .......................................................................................................................................................... 151 9. TECHNICOLOR R&D FRANCE SNC ............................................................................................................................................... 152 10. ATOS SE (SOCIETAS EUROPEA) ............................................................................................................................................. 153 11. ENGINEERING - INGEGNERIA INFORMATICA SPA ....................................................................................................................... 161 12. ALCATEL-LUCENT DEUTSCHLAND AG & ALCATEL-LUCENT ITALIA S.P.A. ....................................................................................... 166 13. SIEMENS AG ..................................................................................................................................................................... 169 14. INTEL RESEARCH AN INNOVATION IRELAND LIMITED .................................................................................................................. 171 15. NEC EUROPE LTD ............................................................................................................................................................... 173 16. FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWANDTEN FORSCHUNG E.V (FRAUNHOFER) ................... 176

GLOSSARY ........................................................................................................................................................................................ 179

REFERENCES ..................................................................................................................................................................................... 183

1.9 Table of Figures

Figure 1: FIWARE Cloud Hosting Architecture............................................................................................... 10

Figure 2: FIWARE Data/Media Context Management chapter architecture ................................................ 15

Figure 3: Data Collection, Processing and Publication .................................................................................. 21

Figure 4: Media Processing ........................................................................................................................... 22

Figure 5: IoT GEs Usage Vision –Phase/Generation I .................................................................................... 23

Figure 6: IoT GEs Usage Vision –Phase/Generation II ................................................................................... 24

Figure 7: Usage scenario with multiple deployment options in the Business Framework ........................... 34

Figure 8: RSS relationships with other GEs and actors .................................................................................. 35

Figure 9: GEs interacting with multiple service providers ............................................................................. 38

Figure 10: Application Mashup GE Usage Scenario ...................................................................................... 39



Figure 11: The four groups of GEs of the Advanced Web-Based UI chapter and their relationships ........... 42

Figure 12: FIWARE Business Canvas .............................................................................................................. 54

Figure 13: FIWARE SWOT .............................................................................................................................. 55

Figure 14: FIWARE Major differential features ............................................................................................. 57

Figure 15: FIWARE Lab .................................................................................................................................. 62

Figure 16: FIWARE Smart City Standardization Essentials ............................................................................ 68

Figure 17: FIWARE Open APIS for OPEN MINDS ........................................................................................... 69

Figure 18: Open Source Community Pattern, Walli S, the Outercurve Foundation, 2013 ............................ 80

Figure 19 TID´s unified horizontal architecture approach ............................................................................ 86

Figure 20 TID´s Open Data for Developers .................................................................................................... 87

Figure 21 Timeline of SAP's FIWARE exploitation activities .......................................................................... 93

Figure 22 Adoption of WP3 GEs in FIWARE use case projects phase 1 and phase 2 .................................. 101

Figure 23 FIWARE target groups and channels ........................................................................................... 114

Figure 24 Thales R&T process Map ............................................................................................................ 128

Figure 25 Thales R&T Activity flow diagram ............................................................................................... 130

Figure 26 – THALES CYBELs Security Operational Center ............................................................................ 133

Figure 27- Thales Cyber Security for Thales ................................................................................................ 133

Figure 28– Thales CYBELs Security Operation Centre ................................................................................. 134

1.10 Table of Tables

Table 1 Ingredients needed to build a sustainable ecosystem for Smart Cities ........................................... 65

Table 2 Smart City Applications on FIWARE .................................................................................................. 66

Table 3 FIWARE Catalogue Summary ............................................................................................................ 73

Table 4 Tool Licenses ..................................................................................................................................... 74

Table 5 SAP’s FIWARE results (software components) and their exploitation approach ............................. 96



1. General Introduction and Background

Over the last 30 months, as a part of the ambitious European FI PPP program, FIWARE has started to

materialize as a powerful foundation for the Future Internet. FIWARE is an innovative, open cloud-based

infrastructure for cost-effective creation and delivery of services, at a scale not seen before. FIWARE is

now well underway to successfully achieve its goals of boosting the effectiveness of creating new services

of high economic and societal value, reinforcing EU competiveness and bringing opportunities for high

growth entrepreneurs and SME players.

Now, following an intensive period of research, development and experimentation, the FIWARE

Consortium aims to complete the FI-PPP vision and support a truly open innovation ecosystem around

FIWARE-Lab, a working instance of FIWARE that is distributed across multiple datacenters in Europe and

is effectively operated using the suite of FIWARE-Ops tools.

A key element for fostering uptake will be wide ranging extension and operation of FIWARE-Lab

supported with the promotion of FIWARE-Ops for managing and operating FIWARE-Lab nodes and

FIWARE Instance deployments. The ambition of FIWARE is to extend FIWARE-Lab across entire Europe

and to promote this beyond by means of hackathons, interop-dev meetings, industry fairs, and similar

events targeting developer communities. This will be complemented by an extensive training and

support offer provided, by FIWARE, tailored to SMEs, Web-Entrepreneurs, and also industry players

across the ICT and Non-ICT sector.

Purely technological continuity is paralleled by operational continuity. More precisely, this means that

FIWARE GEris are deployed and operated in FIWARE-Lab, via the FIWARE-Ops approach, and are

published in the FIWARE Catalogue. The same applies to tooling, such as the FIWARE Jira Instance which

is dedicated to support and interaction with Use Case projects and Use Case Expansion projects, SMEs

and Web-Entrepreneurs, the FIWARE Wiki, FIWARE distributed software development tools, and FIWARE

eLearning tools.

This way, FIWARE, FIWARE-Ops and FIWARE-Lab will be a globally competitive foundation for Europe's

economy.

Regarding exploitation advances so far; we started to build a strong value proposition around FIWARE.

This value proposition has shown to be particularly strong in the vertical domain of Smart Cities and also

in the IoT (Internet of Things) space. FIWARE is actually experiencing a great momentum in both areas.

- In the case of Smart Cities, rumours say that the EC may soon publish a series of recommendations

and best practices in which FIWARE would be explicitly mentioned.

- In the case of IoT, discussions are taking place within EIRC (European Research Cluster on Internet of

Things) community to adopt FIWARE as common foundation for an IoT platform. We have also

started promotion of FIWARE results in GSMA.

- One of the unique selling points in our value proposition is the FIWARE Lab. 2014 has not only been

the year at which expansion in Europe has started but also when countries beyond Europe have

arrive to us willing to join and expand the footprint of FIWARE Lab in their countries.

- Relevant to mention is the recent incorporation of Mexico. Interestingly enough, some

organizations are starting to approach us showing their interest to join the FIWARE Lab by



contributing their resources (without that requiring funding from FIWARE). The experience

demonstrates that there is a lot of potential to engage other countries/regions.

- Another complementary angle is the one of data. Developers get access to data sets when they

register in FIWARE Lab, but no info is provided prior to that step…

Additionally, the FIWARE Acceleration Programme was launched last September. This was cornerstone

in the now called FIWARE PPP (formerly known as Future Internet PPP). Thanks to the active role of

FIWARE Accelerator projects, but also the support provided by the FIWARE partners, particularly through

the series of Start-up Weekend FIWARE special edition events, FIWARE has raised a lot of interest among

entrepreneurs in Europe.

- The results of the first Open Calls launched by the FIWARE Accelerator Projects have gone beyond

the initial expectations.

- This means there will be soon hundreds of SMEs/Start-ups working with FIWARE technologies, many

of them experimenting on the FIWARE Lab. We have to provide them the necessary training,

coaching and support has to be one of our first priorities!

- All 2014 were sprinkled with our presence in many events. An excellent summary can be found in

the blog post with which we closed 2014. We have to be able to combine both global relevant events

as well as events focused locally in each country in 2015.

- Besides our presence in Campus Party Brazil in a matter of weeks, we will make a strong bet for a

highly visible presence both at 4YFN (the entrepreneurs-oriented event linked to the Mobile World

Congress in Barcelona) and CEBIT.

- Regarding events focused locally, the multi-site event co-organized with the Ministry of Industry in

Spain was instrumental in gaining a strong endorsement of the Government in Spain but also reaching

a high awareness among Spanish Entrepreneurs (as a proof of this, it happened that a rather large

number of SMEs/start-ups from Spain submitted their applications to the FIWARE Acceleration

Programme). We should seek for similar events in other countries in Europe. At least in Germany,

France, Italy and Finland, Israel as well. I encourage partners in those countries to come up with the

design of a local-focused event.



2. What is FIWARE?

FIWARE provides enhanced OpenStack-based cloud hosting capabilities plus a rich library of added-

value functions offered “as a Service”. These components, called Generic Enablers (GEs), provide

open standard APIs that make it easier to connect to the Internet of Things, process data and media

in real-time at large scale, perform Big Data analysis or incorporate advanced features for the

interaction with users.

Availability of an open source reference implementation of each FIWARE GE will accelerate

availability of multiple commercial FIWARE providers, all supporting the same set of APIs. This means

that you will be able to decide who will operate the environment where your application and, even

more important, your data will be hosted. As a result, FIWARE becomes an open alternative to

existing proprietary Internet platforms.

On the whole, FIWARE is an open architecture which acts as an alternate solution to the various

proprietary platforms that already exist. Due to the open nature of the infrastructure, we view this as

having a similar impact to the role Linux and Apache played in the development of an open web.

The following chapter delves into the most recent technological advances per FIWARE domain, as well

as innovative market disruptions and business trends that may impact or are already impacting the Future

Internet.

2.1. Cloud Hosting

Cloud Hosting will be an integral part of the FIWARE platform and together with the Apps/Services

Ecosystem, Data/Context Management Services, Internet of Things Service Enable and Interfaces to the

Network and Devices will offer a complete solution for: application development that automatically

resolves hosting, deployment and scalability, provides the necessary interfaces and services so that

applications can leverage the Internet of Things, provide intelligent connectivity all through the stack to

guarantee QoS, resolve common needs like data storage and analysis, access to context and

monetization, allow the delivery of applications through a rich ecosystem that enables the

implementation of flexible business models and allows user driven process creation and personalization.

Cloud Hosting is building upon existing virtualization technologies, FIWARE will deliver a next generation

CloudStack that will be open, scalable, resilient, standardised, and secure, and will enable Future

Internet applications by providing service-driven IaaS and PaaS functionalities and extending the reach of

the cloud infrastructure to the edge of the networks, much closer to end users.

The Cloud Generic Enablers are able to cater for the needs of companies that may require IaaS Cloud

hosting capabilities, PaaS Cloud hosting capabilities or both, meeting the requirements for the provision

of cost-efficient, fast, reliable, and secure computing infrastructures “as a Service”.The basic principle to

achieve a cost-efficient infrastructure is the ability to share the physical resources among the different

users, but sharing needs to be done in a way that ensures isolation (access, control and performance)

between these users. These seemingly contradictory requirements can be met by an extensive use of

virtualisation technology.

Virtualization capabilities are the cornerstone of any IaaS Cloud Hosting offering because they enable

both high utilization and secure sharing of physical resources, and create a very flexible environment

where logical computation processes are separated and independent from the physical infrastructure.

FIWARE’s base functionalities will include a virtualization layer that will enable secure sharing of physical



resources through partitioning, support migration without limitations, and provide a holistic system-wide

view and control of the infrastructure. Basic management of the resulting virtualised infrastructure will

automate the lifecycle of any type of resource by providing dynamic provisioning and de-provisioning of

physical resources, pool management, provisioning, migration and de-provisioning of virtual resources,

on-going management of virtual capacity, monitoring etc.

The following figure summarizes the reference architecture of FIWARE Cloud Hosting chapter:

Figure 1: FIWARE Cloud Hosting Architecture

2.1.1. Main Packages/Bundles

Virtualisation technologies, such as hypervisors or OS containers, enable partitioning of a physical

resource into virtual resources that are functionally equivalent to the physical resource. Moreover,

virtualisation creates a very flexible environment in which logical functions are separated from the

physical resources. IaaS Cloud hosting providers can leverage this capability to further enhance their

business.

- For example live-migration of virtual resources, enable the cloud hosting providers to optimize the

resource utilization.

- However, running different workloads on a shared infrastructure, hosted by a 3rd party, introduces

new challenges related to security and trust. FIWARE will address these challenges by leveraging

generic enablers defined in the FIWARE Security chapter.

In addition to virtualisation and the management of it, cloud hosting providers need a layer of generic

enablers that deal with the business aspects of optimally running their operation.

- Existing IaaS Cloud Hosting technologies and commercial offerings represent a big step forward in

terms of facilitating management of compute infrastructure by completely virtualising the physical



resources used by software, but still do not fully address all the needs of both IaaS Cloud Hosting

Providers and Application and Service Providers.

- IaaS Cloud Hosting Providers need grouping and elasticity, policy-driven data centre optimisation

and placement, billing and accounting, more control over virtualised Network Resources.

- Application and Service Providers need the infrastructure management decisions to be directly

driven by Service Level indicators and not compute parameters as is the case today.

Typically existing IaaS Cloud Hosting solutions are based on a centralised infrastructure deployed usually

on a few data centres distributed geographically. However, some Future Internet applications may

require reduced latency and high bandwidth that this approach and current network realities cannot

always meet. This becomes especially problematic when the users of the hosted applications and services

are using their home broadband connections.

- Stricter privacy requirements that favour local-only storage of data may be an additional obstacle

to the current approach, as it would place data even further away from the computational

infrastructure.

- To address these challenges, FIWARE will explore the possibility to extend the reach of the IaaS

Cloud Hosting infrastructure to the edge of the networks by incorporating a device located at the

home of an end user, the Cloud Proxy that can host part of the virtualised resources, applications and

data, thereby keeping data closer to the user.

Application Providers may rent from IaaS Cloud providers dynamic infrastructure resources to deploy

service components, but they are on their own in terms of coming up with the deployment architecture,

managing and deploying enabling SW components, managing and maintaining the software stacks

installed on each virtual machine and controlling the scalability of the virtualised infrastructure resources.

- FIWARE will build on top of robust virtualisation-based IaaS technologies to create a Platform as a

Service offering that provides a higher level of abstraction for service provisioning where the platform

itself provides development tools, application containers, integrated technologies (libraries, APIs,

utilities, etc.) and automatic scalability tools, allowing the Application Providers to deploy applications

by means of providing just the description of their Application Components. The delivery of standard

interfaces and reference implementations for the above elements are both in the scope of the

FIWARE.

- In order to simplify management of hosted resources FIWARE will provide a self-service portal

where Application and Service Providers will be able to select, configure, deploy and monitor their

whole applications and services through graphical tools. Application Blueprints and Service Level

Agreements will be used by Cloud Hosting providers to drive automatic provisioning and dynamic

management of the virtualized resources.

Trust and consequentially security concerns are one of the top obstacles that hinder Cloud Computing

adoption today.

- FIWARE will work towards embedding security, privacy and isolation warranties, which can be

achieved through use of standard security techniques (authentication, authorization, encryption, etc.)

and partitioning technologies that warranty isolation, to all layers of its Cloud Hosting platform.

2.1.2. Business Capabilities

The Cloud Hosting Chapter provides capabilities to host compute, storage and network resources

required by Future Internet applications and services, so that they can be consumed “as a service”,

typically on a pay-per-use basis or some similar manner.



- This allows Application/Enabler Service Providers, even though they represent small companies, to

deliver services without large initial capex while still being able keep OPEX (Operational

Performance Expenses) still under control, so only the resources that are required to handle an

increasing and variable amount of service requests, data or number of customers are allocated.

Based on their specific needs, cloud consumers can choose between multiple abstraction levels of

provisioned resources. These are provided by different core Generic Enablers. This includes:

- Individual virtual machines and associated resources (IaaS Resource Management GE),

- Objects and associated metadata (Object Storage GE),

- Application containers (PaaS Manager and Software Deployment and Configuration GEs) or cloud

proxy appliances (Cloud Proxy GE), which can be deployed forming complex topologies of multiple

resources, elastically allocated (by the Policy Manager).

Different stakeholders, who are involved in the life cycle of Future Internet applications and services, can

use the various Cloud Hosting capabilities for different purposes.

- For example, cloud providers can use Cloud Hosting GEs to offer cloud capabilities to their customers.

- Application developers can use cloud hosting capabilities (provided by a cloud provider) during the

development cycle, to develop and test their applications.

- Moreover, service providers can use cloud resources along the various phases of the service life cycle,

testing, migration, staging, ‘production’, disaster recovery, etc.

Generally we can say that the FIWARE Cloud Services reduce the following barriers for 3rd parties:

- The entrance threshold for new players on the market, especially if they provide applications and

services for smaller consumer groups is reduced since the support of the cloud enablement

supersedes the investment into expensive infrastructure.

- On the other hand, a dynamic market for cloud services can provide a competitive environment that

encourages the development of new kinds of hosting services for smaller groups of services providers

with more specific needs.

2.1.3. Market Positioning

OpenStack is emerging as the de facto open source cloud framework. All the GEs in the Cloud chapter

are standardized on OpenStack APIs, and together comprise a powerful cloud platform, going beyond

competition. Moreover, many key European companies are also adopting OpenStack, and are building

products and offerings around it. This includes Ericsson, Alcatel Lucent, Bull, Cloudwatt, eNovance, France

Telecom, Deutsche Telekom, Thales, Telefonica, Intel, SAP, and others.

Additionally we outline the added value introduced by Openstack

- The most disruptive and notable trend in the IaaS space is the evolution of OpenStack – the rapidly

growing open source 'infrastructure as a service' cloud middleware, jointly developed by hundreds of

commercial companies across industrial sectors, and rapidly adopted by many vendors for both public

and private cloud offerings (notably Rackspace, HP, IBM, and many others).

- While most of the solutions above are proprietary, this market segment undergoes significant

changes with the introduction of orchestration capabilities in OpenStack, and their growing wide

adoption and support by the vendors who are invested in OpenStack ecosystem.



- Being open source, OpenStack shifts the business model of many vendors from focusing fee-based

value-add features to emphasis on services and support (which is a common practice in the open

source world).

Additionally, security will continue to be a key issue. Cloud vendors and corporations will struggle to

keep pace with the rapidly changing threats.

- The growing interest in container-based computing will speed application development, but also

create new security holes.

- There will be more emphasis on connecting cloud services so companies can effectively manage

their assets. Integration and consulting services will thrive and OpenStack will emerge as the leader

in this space.

Regarding Open Data, discussion with cities and governments around the world indicate that at present,

many use internal storage systems to manage their data, but where cloud-based storage is used,

Amazon monopolizes current practice.

- Some Swiss government departments store primary data on Amazon S3.

- Data UK maintains internal hardware systems, mostly because of political issues rather than

technical decisions, demonstrating the lack of trust many governments may have for commercial

data servers, like Amazon.

- Hosting data servers creates trust for governments and cities to open up data and one of the things

FIWARE is enabling it is choice around what data center will be used.

FIWARE is the European alternative to Amazon and other platforms APPs with the following special

features:

- It is fully open and royalty free.

- It also has a laboratory, FIWARE-Lab, where entrepreneurs can develop their ideas and find customers

and investors seeking applications

- Better positioning of vendors given the strict EU regulations in many industries.

Moreover, although Amazon, Microsoft and Google that can spend $5 billion on something in a

heartbeat, the following FIWARE features do not exist in AWS:

- The hosted managed private cloud model, provided now by such vendors as IBM and Rackspace (the

client gets a dedicated installation of OpenStack, at provider's premises, managed & administered by

the provider)

- Bare-metal cloud (providing bare-metal machines rather than VMs), provided now by such vendors as

IBM, Rackspace and Internap .

2.1.4. Potential Usage Scenarios

Improve development and life cycle management of traditional applications. Cloud hosting can

significantly improve the entire life cycle of applications – starting from development and testing, and up

to ongoing management in 'production', including deployment, upgrades, etc.

- Most of the improvements result from the easy of provisioning in virtualized environments, ability to

do it in a fully programmatic and automated manner leveraging elasticity of the cloud infrastructure,

as well as from the growing popularity of tools aimed at automated orchestration of deployment

and configuration management tasks in cloud environments, such as Chef and Puppet.



- GEs that would be typically involved in providing such capabilities are IaaS Service Management,

PaaS Management, Monitoring and Software Deployment and Configuration GEs, as well as DCRM,

Cloud Portal and Identity Management.

Continuous development and delivery of new, cloud-centric, applications. Once organizations start

realizing the benefits of the cloud paradigm, it often becomes clear that applications must be designed

differently in order to fully utilize the capabilities provided by the cloud. These applications would

typically be horizontally scalable to address changing demand, tolerant to (potentially frequent) failures of

individual components, able to run on distributed environments to leverage capacity available at different

locations as well as to optimally meet requirements related to proximity to data or to end-users.

- Such applications are likely to be hosted in environments that comprise DCRM GE and PaaS

Management GE, as well as many of the capabilities described in the previous section dealing with

automation and DevOps approach. The cloud-centric applications are likely to use Object Storage GE

to store fixed content, and they may also use Cloud Proxy GE and Edgelets Management GE to

leverage resources closer to the end-user. There is also a growing trend to use many open source

tools in architecting the end-to-end solution, which become mature enough for production

environments.

- The applications are often offered using 'as-a-service' model to the customers of the application

provider, comprising large portion of the SaaS market – which is the dominant part of the cloud

computing market as a whole.

2.2. Data Context Management

The Data/Media Context Management chapter provides a number of generic enablers that fulfil the

requirements of many and diverse applications and systems. They provide support for gathering,

analyzing or publishing either near real time data, static data, and media.



Figure 2: FIWARE Data/Media Context Management chapter architecture

The most important generic enabler is the Context Broker GE, a context management middleware based

on OMA’s NGSI9/10. Using this API, clients can either query/update context information (context entities,

and their attributes) in a synchronous way or subscribe to it, so they are notified about context

information in an asynchronous way when some condition happens (e.g. in a regular time interval or

when a given context element has changed). The Context Broker GE will be the communications bus in

most of the interactions among GEs, and enables a real decouplement among consumers and providers of

information, and thus, among systems, subsystems, applications and GEs.

The Big Data GE provides functionality to deploy, manage and easily use clusters of big data processing,

including map & reduce batch analysis and real time analysis of data streams. In the described scenario,

the

Big Data GE stores, according to a specified configuration, the received data as files in HDFS. This data,

together with other datasets available through the Open Data Portal or acquired from external databases,

is available then for further analysis based on the map reduce pattern. It can also be used for real time

analysis of the streams of data to, for instance, work out real time KPIs based on the incoming data. As a

result of this analysis, the Big Data GE will generate new insights that can be either stored or published as

new context events through the Context Broker GE.

On the other hand, the context events can be processed by the Complex Event Processing (CEP) GE in

real time, analyzing and detecting patterns of events that make up a situation. Whenever a situation

defined by a developer is identified, the CEP triggers a programmed action and eventually generates a

response that can be sent or stored in the Big Data GE, or even more usual, published as a new event

through the Context

Broker GE.

The Stream Oriented GE filters and analyzes media content, among other possibilities. It provides a

framework devoted to simplify the development of complex interactive multimedia applications through

a rich family of APIs and toolboxes. It provides a media server and a set of client APIs making simple the

development of advanced video applications for WWW and smartphone platforms. The Stream Oriented

GE features include group communications, transcoding, recording, mixing, broadcasting and routing of

audio visual flows. It also provides advanced media processing capabilities involving computer vision,

video indexing, augmented reality and speech analysis. The Stream Oriented GE’s core element is a

Media Server, responsible for media transmission, processing, loading and recording. It is implemented in

low level technologies based on GStreamer to optimize the resource consumption. It provides the

following features:

- The applications deployed in this GE receive real time information about the media analyzed.

- The Compressed Domain Video Analysis GE consists of a set of tools for analysing video streams in

the compressed domain, i.e., the received streams are either directly processed without prior

decoding or just few relevant elements of the stream are parsed to be used within the analysis. The

target users of the Compressed Domain Video Analysis GE are all applications that want to extract

meaningful information from video content and that need to automatically find characteristics in

video data. The GE can work for previously stored video data as well as for video data streams (e.g.,

received from a camera in real time).



- The Media-enhanced Query Broker GE provides a smart, abstracting interface for retrieval of data

from the FIWARE data management layer. This is provided in addition to the publish/subscribe

interface (e.g. Context Broker (Publish/Subscribe Broker) GE) as another modality for accessing data.

Principal users of the Media-enhanced Query Broker GE include applications that require a selective,

on-demand view on the content/context data in the FIWARE data management platform via a single,

unified API, without taking care about the characteristics of the internal data storage and DB

implementations and interfaces.

The Location platform GE provides location based services both to mobile end users and third party

services and clients. The Location GE in FIWARE targets any third-party application (GEs in FIWARE, or any

complementary platform enabler) that aims to retrieve mobile device positions and area events. The

Location GE is based on various positioning techniques such as A-GPS, Wi-Fi and Cell-Id intelligently

triggered whilst taking into account the end-user privacy.

The Metadata Preprocessing GE is typically used for preparing metadata coming from a data-gathering

device for subsequent use in another device (i.e., another GE or an application or another external

component). The data-gathering device can be a sensor, e.g., the analytics component of a surveillance

camera. Depending on the manufacturer of the camera, different metadata schemes are used for

structuring the metadata. The Metadata Preprocessing GE generally transforms the metadata into a

format that is expected by a subsequent component, e.g., a storage device. In addition to performing the

transformation of the metadata format (e.g., defined by XML Schema), also some elements of the

metadata can be removed from the stream by a filtering component. This is especially useful in case these

elements cannot be interpreted by the receiving component.

The Semantic Annotation GE may be used in the augmenting of content (news, books, etc.) with

additional information and links to LOD. It provides filtering and search based on LOD resources used as

categories/tags. Target users are all stakeholders that want to enrich textual data (tags or text) with

meaningful and external content.

The Semantic Web Application Support GE aims at providing an effective environment for developers to

implement and deploy high quality Semantic Web-based applications. It provides:

- An infrastructure for metadata publishing, retrieving and subscribing that meets industry

requirements like scalability, distribution and security. From now and so on, we will refer to this

infrastructure as SAS Infrastructure.

- A set of tools for infrastructure and data management, supporting most adopted methodologies and

best practices. From now and so on, we will refer to these tools as SAS Engineering Environment.

In a first stage, the functionalities set provided by each one of the GEs within the Data/Context

architecture are considered meaningful standalone and as such they are delivered to other chapters and

third parties exploiting FIWARE. However, some tasks have been already started to identify scenarios

involving smart combinations of Data/Context GEs into GE packages thus providing synergic features to

other chapters and customer applications beyond FIWARE framework. In Figure 3, the most prominent

interactions among GEs are depicted. They all are based on the NGSI APIs of FIWARE, and take the

Context Broker implementations as core of the integration.



Figure 3: Data/context NGSI-based GE integration

The most important NGSI integrations in FIWARE are:

- Context Broker - Complex Event Processing. The CEP implements specific NGSI adaptations of the

REST connectors to allow the reception and generation of notifications of context events. This

integration is only based on ONCHANGE notifications. This integration has been implemented and

tested as part of FIWARE live demo.

- Context Broker - Big Data Analysis. An adaptor has been implemented to automatically store all the

context notifications related to a context entity into the Big Data storage. This data can be used later

for Map&Reduce analysis from raw files or loaded into external tables (Hive).

- Context Broker - Location. The Location GE generates location information about mobile devices,

which can be considered context entities. The Architecture of LOCS GE describes how this integration

has been designed.

- Stream Oriented (Kurento) . The Stream Oriented GE filters and analyzes media content, among

other possibilities. The applications deployed in this GE receive real time information about the media

analized. Through Java componets, it is foreseen to push NGSI context notifications to the Context

Broker.

- IoT Broker (IoT Chapter). Through this GE the Data chapter Context Broker can receive notifications

about context information generated and published by IoT devices. This integration is fully

implemented.

- Apps Mahups (Wirecloud implementation). Through a Javascript library, the widgets implemented in

wirecloud can interact with the Context Broker both for receiving and delivering context information.

And last but not least, other applications and components can use NGSI as a way to communicate

context information. For instance, it is possible to send/receive context information from apps running in

smartphones or other devices (e.g. Raspberry Pi).

In short, the GEs of this chapter and their combinations offer a great number of possibilities for

developers to create new applications and systems. Moreover, the possibility to deploy in the cloud

infrastructure the GEs standalone, or usual combinations of then will make even easier the adoption by

developers.




Context information is generated in many situations from IoT Generic Enablers (data from sensors), IT

systems integrations and context data publication through NGSI APIs. This context data can be consumed

directly by applications, but there are several use cases where it is useful to further exploit and process

this data by using the functionality provided as part of the FIWARE GEris and Cygnus component

mentioned before. The Data Context Streams bundle enables to do this in a quick and efficient manner..

“Data Context Streams Bundle”

The Data Context Streams bundle allows to generate, distribute, store, analyze and use context

information and is offered collaboratively by TID (lead), IBM , NaevaTec and URJC (Universidad Rey Juan

Carlos). The bundle Data Context Streams provides an instalable set of GEris packaged together. These

GEris are offered in an integrated way so that they can be easily deployed in FIWARE LAB and used by

developers:

- Orion Context Broker: It is the key element and mandatory GEri of this bundle. It allows publishing

and consuming context information through the NGSI APIs. Other GEs in the bundle will publish or

consume context information from Orion Context Broker.

- Cygnus storage: Although it is not a generic enabler, Cygnus is a complementary piece of software for

Orion Context Broker that can be used to store historical information from the Orion Context Broker

both in Cosmos Big Data storage and Open Data portal.

- PROTON Complex Event Processing: This GEri is able to receive Context information through NGSI

subscriptions, detect complex situations based on preconfigured rules, and generate new context

information to be published in the Context Broker or other types of output.

- Cosmos Big Data: This GEri is the destination of the Context Broker data through Cygnus component.

All the context historical information will be stored in the GE for later analysis through map & reduce

applications or Hive based queries.

- Kurento Streams-Oriented GE: This GEri is offered optionally as part of the bundle. There are

scenarios where the result of analysis of media can generate context information to the Context

Broker, as detecting objects in an area of an image (fences), or analyzing a given situation from the

video (e.g.: people detection).

A blueprint for this bundle, with the installed and pre-integrated GEri instances mentioned before is

configured and available. In FIWARE LAB, users can deploy this blueprint and also create their own image

instances in order to use the bundle.

The Data Context Streams bundle package has also been published within the FIWARE Catalogue.


Nowadays, several well-known free Internet services are based on business models that exploit

massive data provided by end users. This data is exploited in advertising or offered to 3rd parties so that

they can build innovative applications. Twitter, Facebook, Amazon, Google and many others are examples

of this.

The Data/Context Management FIWARE chapter aims at providing outperforming and platform-like GEs

that will ease development and provision of innovative applications that require management,

processing, publication and exploitation of context information as well as data streams in real-time and at



massive scale. Combined with Enablers coming from the Apps Chapters, Application Providers will be

able to build innovative business models such as the ones described above and beyond.

In a nutshell, FIWARE Data/Context Management GEs will enable to:

- Record, subscribe for being notified about and query for context information coming from different

sources (NGSI and CML)

- Model changes in context as events that can be processed to detect complex situations that will lead

to generation of actions or the generation of new context information (therefore, also treatable as

events).

- Processing large amounts of context information in an aggregated way, using map reduce

techniques, in order to generate knowledge that may also lead to execution of actions and/or

creation of new context information.

- Process data streams (particularly, multimedia video streams) coming from different sources in order

to generate new data streams as well as context information that can be further exploited.

- Process metadata that may be linked to context information, using standard semantic support

technologies.

- Manage some context information, such Location information, in a standardized way.

- Manage semantic information, in particular, managing ontologies, annotating web content as

semantic information and access to context information through semantic endpoints (SPARQL)

The availability of advanced platform functionalities dealing with gathering, processing, interchange

and exploitation of data at large scale is going to be cornerstone in the development of intelligent,

customized, personalized, context-aware and enriched application and services beyond those available on

the current Internet. These functionalities will foster the creation of new business models and

opportunities which FIWARE should be able to capture.


Context information may come from many different sources, ranging from IT systems and mobile apps

to sensors and all of these, in turn, can use different interfaces and protocols, some of which can even be

proprietary.

- This increases the complexity for creating internet enabled services and applications that require

using and consuming this context information in order to be updated and offer their value added

capabilities.

- It also restricts the creation of these services and applications to a reduced group of developers who

are required to deal with the different interfaces and protocols used by the context information

sources, in order to build a customized service or application using them.

The Context management approach followed in FIWARE allows to overcome this problem by creating a

common open standard interface (based on OMA NGSI), which allows developers to focus on actually

using the context information received, without having to worry on when and how to receive it. This

common open NGSI interface enables application to query on context information or subscribe to

changes in context information that will be received through notifications. It also enables applications or

other to modify the context information.

In other words, FIWARE, and in particular, the Orion Context Broker GEri hides the complexity of

accessing to the information provided by the multiple and heterogeneous context sources by offering a

single set of NGSI APIs which the applications can use to consume and update the information from all



context sources, in the same way. This facilitates developers to access easily the context sources and the

data attributes of their interest, reducing dramatically the development effort and time to market

required for the applications and services they are building.

However, this is not the only step FIWARE has adopted to enable rapid and open innovation for Future

Internet services among the developers’ communities. The Context Management approach is also

complemented by providing the open and royalty free tools for enabling the publication in real time of

this context information as Open Data, and developers can use it combination with Wirecloud and other

GEris from the Application chapter to build their service or application.

Note the Open Data approach in FIWARE is not limited to just allow publishing historic non real time

context information as other proprietary open Data solutions in the market offer, but it actually allows

real time context information to be published as Open Data.

Context information can also be both stored and analysed at a massive scale by using the Hadoop

based Big Data Analysis enabler (Cosmos is its GEri) from FIWARE. So both historic context data (e.g: file

based) and real time context data (the one managed by the Context Broker) can be stored, processed and

analysed using the Big Data enabler and its storage connector(Cygnus). This analysis may, in turn,

generate updated context information that the applications and services can consume through the

common NGSI standard interface from the Context Broker, and also publish it as open Data if required.

There are other GEs that FIWARE offers to use and manage the Context Data and that allow providing a

complete context data management ecosystem that developers can use:

- Complex Event Processing (CEP PROTON is its GEri in FIWARE) allows to perform some processing on

available context information. This way, instead of building a service or application just based on the

received context information at a particular time, applications can identify and react to patterns over

the contexts of several sources or over a context that was changed over time by using this GE,

allowing to increase substantially the range of possibilities for value added services implementation

by the developers, when compared to simple publish/subscribe solutions offered in the market.

- Real-time Multimedia Stream processing GE (reference implementation Kurento) allows developers

to easily integrate multimedia information as part of their applications. Multimedia information

comprises audio and video data, which is commonly used for the exchange of complex information

among humans (i.e. video conferencing, video-clip sharing, multimedia instant messaging, etc.) In

addition to this, in the last few years, cameras and microphones are often used as advanced sensors

that, combined with computer vision and other analysis techniques, may generate rich information

useful in different application areas including eHealth, smart cities, security and defense,

entertainment, etc. Incorporating such features can be done using this enabler from FIWARE.

In conclusion, the integration of all these Data Context management enablers mentioned before allows

FIWARE to offer extensive capabilities for developers in order to create their internet enabled

applications and services and to position itself as a key and enhanced alternative to other proprietary

context management solutions in the market.


In the scenario depicted in Figure 4, one of the most usual scenarios that can be found in Smart Cities,

Logistics or Manufacturing environments, to name a few, is based on near real time gathering of streams

of context information through the Context Broker GE.

- One of the most important sources of context information are IoT chapter Generic Enablers, as

explained in the next section, what allows to gather data from different types of sensors and devices.



- Context data can be also gathered from other NGSI compatible systems and devices, as mobile

phone applications or NGSI adaptors to external systems or social networks.

Figure 3: Data Collection, Processing and Publication

The data is published and available for different GEs and applications to be used:

- Big Data for storage and analysis,

- Complex Event Processing for events patterns detection and action triggering,

- Event Driven Orchestration for processes orchestration, and

- Open Data Portal for cataloguing and publication

Finally, Figure 4 depicts the usage of the Media Stream Oriented GE to handle, analyze, enrich and

produce media content. This GE supports the analysis, creation or transformation of media content

leveraging a number of media based applications like interactive interpersonal communications (e.g.

Skype-like with conversational call push/reception capabilities), human-to-machine media features (e.g.

Video on Demand through real-time streaming) and machine-to-machine multimedia capabilities (e.g.

remote video recording, multisensory data exchange).

In addition, the GEs need to interoperate with common multimedia technologies including HTML5.0,

smartphone video capabilities and the IP Multimedia Subsystem (IMS).



Figure 4: Media Processing

The Media Stream Oriented GE enable application developers to analyze the incoming or stored media

implement or reuse media filters to detect different situations in the media (objects, movements, sounds,

etc.) and generate context notifications through the Context Broker GE.

- This GE will serve also as a media store that, in combination with the Open Data Portal metadata

management, can enable the publication of open media content to external stakeholders.

- On the other hand, it will interact with the Apps Mashup GE and the UI and augmented reality GEs

from the Advanced Web Based User Interfaces chapter to enrich their content, analyze the media

they capture, and all in all, to create rich multimedia applications. Additionally, augmented reality

applications can also benefit from the Data Aggregation GE, as a source of additional information

related to the entities managed by them.

2.3. Internet of Things

Internet of Things real-life scenarios map to environments that is intrinsically complex and

heterogeneous due to the number of M2M technologies and protocols, gateway definitions and

platform implementations. Diversity is illustrated by the fact that there is no single consolidated

standard but a wide range of specifications defined by different standardization and industry-driven

bodies.

In this respect, the approach taken in the FIWARE IoT chapter does not increase complexity but brings

simplicity by a combination of different means.

- First, it will define an architecture that provides a single convergence point for gathering of data

based on the NGSI evolved standard. The basics for this have already been established in FIWARE. As

a result, application developer can rely on a powerful information model and a set of well-defined

and powerful APIs.

- Second, it provides a modular and evolving framework where application developers or solution

integrators can really pick-up the necessary GEs addressing their requirements, avoiding

unnecessary complexity and performance load. As a result, not only simple sensor devices can be

included, but complex System-of-System. This strategy means an agile way-of-thinking which can be

applied for building up trials within the FI-PPP, experiments in any other research/pre-commercial

environment and, finally, commercial solutions.

- Additionally, the FIWARE IoT chapter will go one step further by enabling a new type of devices

(NGSI enabled) and the connection to complex system-of-systems (vast collections of devices or

standalone smart systems such as consumer devices or robots) by means of providing a higher

abstraction level and the needed processing and actuation methods.

Regarding handling of data from devices, FIWARE allows the accommodation to multiple scenarios and

their evolution over time. The following picture depicts a first kind of scenarios, where every kind of

M2M devices is considered. This is the kind of scenarios that are envisioned to happen in a first phase and



it is currently supported in FIWARE. This includes legacy technologies but also the newest trends such as

WebofThings devices, i.e., IETF CoRE/CoAP compliant.

Figure 5: IoT GEs Usage Vision –Phase/Generation I


This level represents other FIWARE GEs that will be interconnected to IoT ones by means of a FIWARE

Context Broker thanks to the usage of FIWARE NGSI. The diagram represents some FIWARE GEs that are

expected to be widely used in IoT Applications (such as Bigdata and CEP) but it may include any other.

Additionally, final Application components (User Interface and App Backend in the picture) will be

interconnected by the means of a FIWARE Context Broker.

The full integration of Internet of Things with Data and Context management facilitates service creation

using Big Data technologies using sensors networks which open the door for market impact on all sectors,

building cross sectors services using sensors from one area, merging collected data with the one from

another sector and proposing innovative services.

The following picture describes a second kind of IoT scenarios that will complement the previous one.



Figure 6: IoT GEs Usage Vision –Phase/Generation II

Finally the unique bundle created so far is the full integration of Gateway Data Handling GE

(EspR4FastData) and Zigbee Protocol Adapter (ZPA) inside the Cloud Proxy (Techniclor Box) using a

dedicated OSGi bundle. It is available on the FIWARE catalogue under EspR4FastData webpage.

Integration tests of the following GE are also available to use in a common implementation:

- Backend Device Manager GE (IDAS)

- Configuration Manager GE (Orion part or IoT Discovery GE)

- IoT Broker

- EspR4FastData


The chapter for Internet of Things (IoT) Service Enablement (IoT Chapter, for short) aims at fostering

innovation by supporting powerful, connective and generally applicable everyday Internet of Things use

cases. For this purpose it offers a framework of suitable Generic Enablers that support such connection.

The envisaged architecture will support the connectivity for several families and standards of devices

and smart objects, as well as the management of the huge amount of information that machines and

people will exchange in a near future.

The FIWARE IoT architecture is based on two fundamental ideas:

- Provide the right abstraction level to deliver the relevant functionalities that simplify the

development of your own Internet of Things application. This is done by means of providing simple

yet powerful APIs for management of IoT-related information as “context” information but also by

providing means for composing services “on the fly”.

- Enable a physical infrastructure which will be able to provide the same access to different kind of

sensors, actuators, devices based on their own standardized interfaces. This infrastructure includes

gateways as smart things which bridge between several technologies but also host management

features for things and information.

We identified the following major differential features:

- Easy plug&play of devices using multiple protocols

- Automated Measurements/Action ��Context updates




Many new industrial Open Source initiatives have merged on the market in 2014 like:

- AllSeen Alliance led by Linux Foundation with Qualcomm Alljoyn support. AllJoyn is a SDK provided

by Qualcomm which source code has been released in Open Source to the Linux Foundation in the

context of the AllSeen Alliance. First presentation of AllJoyn happened inat the Mobile World

Congress 2011, first year of FIWARE project and mainly targets devices. The AllJoyn software

framework and core system services let compatible devices and applications find each other,

communicate and collaborate across the boundaries of product category, platform, brand, and

connection type. Target devices include those in the fields of Connected Home, Smart TV, Smart

Audio, Broadband Gateways, and Automotive.1

o AllSeen Alliance proposes a cross-platform effort, supporting all major desktop and mobile

operating systems, initially including Linux, Android, Arduino, iOS, OS/X, Windows, etc…

Allseen appears to be looking at the long haul and the higher end of the market of devices.2

- Open Interconnect Consortium (OIC) lead by Intel, Samsung and Dell. OIC will focus on creating an

open-source standard for wirelessly connecting devices to one another and to the Internet.

o There are currently few details on this initiative and source code should be published later on.

Intellectual Property concerns happened which lead to Broadcom withdrawal of this

community. It is also clear that this association was launched because of IP concerns

regarding Qualcomm technology.

o This community is also focused on software device integration which should lead to another

SDK.

- Google “”Open Web of Things” program. This is not the first initiative from Google in the area of

Internet of Things but this is the last one, building a programme inviting academics partners to submit

research proposals3

o More specifically, Google wants proposals that address things like user interface and

application development, privacy and security, and systems and protocols.

Both initiatives, AllSeen and OIC are proposing Open Source for community members only and are

focusing on devices more than on application development. In parallel, industrial solutions are emerging

every day but no real free Open Source initiative has emerged along the last three years regarding what

FIWARE proposes concretely

- IoT middleware platforms continued to gain momentum in 2014 as a critical element in the IoT

solution enablement and nowhere are this trend more evident than in the Application Enablement

Platform (AEP) market.

- The core value proposition of these platforms is to ease connectivity, device management, and data

collection activities of any IoT solution.

- The year 2014 saw three important trends which are validating the value of these platforms: first,

the number of AEP vendors has expanded and some of the longstanding players, ILS, Axeda, and

1 http://en.wikipedia.org/wiki/AllJoyn

2 http://linuxgizmos.com/open-source-iot-inititiative-taps-qualcomm-alljoyn-framework/

3 https://drive.google.com/a/venturebeat.com/file/d/0B-ybA8_Lt-gwc2RUWnN5eFFoekE/view?pli=1



ThingWorx, were acquired demonstrating AEP market value and momentum; secondly, GE recently

announced it would make its Predix platform available for 3rd party use further demonstrating the

value of IoT middleware platforms for the Industrial Internet.

Finally, the Third Industrial Revolution is picking up speed as Open standards in the Internet of Things

(IoT) are challenging closed platform approaches.The following improvements has achieved by FIWARE:

- During the last 2 years, oneM2M was launched and succeed to propose what we could consider like a

first evolution of ETSI M2M standard. It is too early to envisage what could be the industrial impact of

this standard on future commercial offers (products and services) but FIWARE has launched a first

action with one M2M to study potential convergence with FIWARE NGSI implementation based on

OMA NGSI 9 and 10 technical specifications.

- FIWARE Unique Selling Point: Open Source Generic Enablers using the same OMA NGSI API , focusing

on applications and services development without any IP constraint.


In the past year, the connected home market has been able to spur a new wave of economic growth

because of one key enabler: open APIs. Prior to this, connected home devices were each seeking to

provide proprietary solutions that forced users to choose a hardware manufacturer and stick with them.

As a result, the idea of a connected home where your lights, garage door, heating and cooling,

entertainment and appliances could speak to each other never really took off. Once manufacturers

began offering open APIs that let developers create integrated solutions and apps that connected the

thermostat to home surveillance, for example, the connected home market began to surge. Now, even

devices like Nest that had originally wanted to ringfence their market entry by forcing consumers to stick

to their product range are opening developer platforms to let their devices communicate and share data

information with other, non-Nest products.

FIWARE wants to take this open API model and apply it to other core segments of the IoT landscape,

particularly smart cities, but also to the idea of the smart factory, to agricultural systems, and to other IoT

realms.

FIWARE enabling smart cities. While not discounting the potential of using FIWARE for other IoT

endeavors, a key part of the current project’s workload has been to engage with city governments to

assist them to use the platform for the management of their smart city infrastructure. 'Smart cities' is

often a catch-all term to refer to the twin goals of using sensor technologies to better manage city

infrastructure, and to the publishing of government data on open data platforms, all with the aim of

increasing city efficiencies, fostering new business opportunities, and encouraging greater civic

participation and conviviality.

Smart Cities is the most promising business case because there is an actor of the value chain who has

benefits to push openness between vertical sectors. Because they are not business actors and cannot

increase easily their revenues, Smart Cities have also to manage their investment in an optimal way. They

are currently the first customers who claim for multi-standards platforms to monitor sensors and collect

data in a homogeneous way: from pollution to noise, from traffic to smart grid, from waste to water

sewage. But Smart cities have to deal with suppliers who prefer end-to-end solutions to limit the risk to

lose partially some activities in this specific market.

- Connectivity is the first challenging point for Smart Cities to use a common infrastructure to collect

data and monitor all sensors but the connectivity solution should integrate existing architecture



(proprietary and/or dedicated to a standard) with new technology to assume an investment for more

than 3 years.

- Coupling several technologies in the same architecture is an opportunity for integrators to propose

new platforms and applications taken into account the diversity of data and devices.

- Surfing on big data and open data waves, Smart Cities expect to share some of these data, this data

should be integrated in new services for citizens. These new services would happen when the new

platform will be in place or under special conditions offer by a city to use quickly some of these data,

proposing a first Open Data market and facilitating emerging applications for citizens.

- The major advantage of Smart Cities market is that a kind of competition between Smart Cities will

accelerate this emerging market and creativity would always emerge because of some local specific

needs from cities and citizen

Lessons learnt from the last two years based on one hand prototypes defined by Use Case projects

dedicated to eHealth, Manufacturing, or Smart Agriculture, and on the other hand through startups

weekend and first calls from FIWARE Accelerators, FIWARE IoT technologies could be used in many

different environments to deliver services where connected objects are involved. The feedback

provided through these different channels shows that the availability of a “free” gateway not linked to

any kind of vendor or dedicated to a unique technology is perceived like a competitive advantage to

build new services.

2.4. Applications

The FIWARE Apps/Services delivery framework offers support tools to access and handle services linked

to processes, ‘things’ and contents uniformly, enabling them to be mashed up in a natural way. A set of

Generic Enablers support managing services in a business framework infrastructure eventually support

the whole service live cycle from creation and composition of services to provisioning and distribution,

finally leading towards monetization and revenue sharing. This allows experimenting with new business

models in an agile and flexible way within the Future Internet.

The overall application services ecosystem framework also incorporates the necessary composition and

mashup tools that will empower users, from developers to domain experts to citizens without

programming skills, to create and share in a crowd-sourcing environment new added value applications

and services adapted to their real needs, based on those offered from the available business frameworks.

With gateway/mediator functionality the needed backend connectivity wiring of services is supported

in order to increase interoperability. The provisioning of services towards consumers and other service

providers as well as the monetization of services is targeted. Among these enablers there is a store, a

marketplace, a repository, a registry, a revenue sharing engine and business modelling and business

elements component.

The GEs in our chapter are organized to support multiple usage scenarios:

- Exploring new business models with the Business Framework

- Revenue sharing

- Supporting service composition and crowd-sourcing

- Supporting Interoperability with Mediation

- Supporting a Data Market

- Supporting an Enterprise Digital Assets Store

- Monitoring and configuration of cloud infrastructures through dashboards




To complement the supported usage scenarios in the Apps chapter, we additionally offer two newly

defined FIWARE bundles where a set of GEs is bundled together to support common use cases for the

customers as a form of re-distributable assets:

The bundles are ready with its development and they are currently being published within the FIWARE

Catalogue. The production leads are responsible for publishing the defined packages with the support of

all contributing partners.

1) Bundle 1: “Business Framework Consumption Bundle” (focus is on consumption)

This bundle groups the following GE into this business package: Store GE, Marketplace GE, Repository GE,

RSS GE, and Identity Management GE. The bundle is offered collaboratively by UPM (production lead),

TID, and SAP. A recipe-based installation mode is supported for automatic VM image creation according

to recipes configuration scripts. In FIWARE-LAB, users can create their own image instances and work with

them immediately.

Using this bundle, a user has access to an ecosystem that supports the monetization and revenue

sharing of applications and services by using the different GEs that make up the FIWARE Business

Framework.

- The Identity Management is integrated as a global instance, since this bundle is intended to be

deployed in FIWARE-LAB, and provides support for all the considered scenarios.

- The revenue sharing system RSS GE is integrated as a “Global instance” running separately.

This bundle helps the user to install, configure and integrate the entire FIWARE business framework GEs

in in the FIWARE-LAB, and provides a single point of installation and configuration of all of them.

Therefore, its availability helps reduce the time of deployment and also demonstrates a common scenario

of use for the business framework GEs.

2) Bundle 2: “Wirecloud Monetization Bundle”

This bundle groups the following GEs into this business bundle: Application Mashup GE, Store GE,

Repository GE, RSS GE and Identity Management GE. The bundle is offered collaboratively by UPM

(production lead), TID and SAP. A recipe-based installation mode is supported for automatic VM image

creation according to recipes configuration scripts. In FIWARE-LAB, users can create their own image

instances and work with them immediately.

The supported scenario integrates an additional GE to the previous bundle and it aims to provide a more

specific usage scenario. The focus of this bundle is set on presenting a specific use case of the Business

Framework to show its potential to monetize the digital assets of a GE: the Application Mashup. The

Identity Management is integrated as a global instance, since this bundle is intended to be deployed in

FIWARE-LAB, and provides support for all the considered scenarios. The revenue sharing system RSS GE is

integrated as a “Global instance” running separately.

As a summary, the Apps chapter provides its GEs and GE composition bundles along seven major usage

scenarios outlined above and additionally offers two FIWARE bundles for customers. These offerings

allow for a set of business benefits as described above and generally speaking support the customers to

handle applications and services and the commercial aspects of using services for business offerings

with a lower total cost of development and deployment and, subsequently, lower cost of ownership.

Additionally, the Apps and Services Ecosystem and Delivery Chapter deal with the creation of the

FIWARE Apps-Service-Data ecosystem.



- Such ecosystem will be composed on three different frameworks, namely the FIWARE Business

Framework, the FI Application Mashup Framework, and the Data Visualisation Framework (the latter

started to be considered as a “first-class citizen” of the chapter during the extension period of the

project), which all together in close cooperation offer a number of features that make the ecosystem

rather unique:

o The implementation of highly configurable dashboards based on data- and event-based

wiring of widgets for the creation and operation of cockpits to monitor and create composite

FI applications. Key feature is the integrated and seamless way datasets are visualized and

used by the various FI applications, this includes the way the applications change their

behavior according to new data comes into the datasets.

o The ability to allow potential customers to search, using different criteria, and to discover

products (both innovative services and datasets) that fit their own needs throughout

different providers. The search results allow the objective comparison of existing offerings

based on customizable filters

o The capacity to monetize FI applications, services and datasets allowing the creation of

flexible pricing and revenue sharing models and managing the offerings though the entire

lifecycle, including features such as access grant or automatic deployment of purchased

applications in FIWARE Lab


The Application and Services Ecosystems delivery framework chapter in FIWARE (Apps Chapter, for

short) will provide the infrastructure that enables the provision, composition, and trading of services on

the Future Internet. Both services and applications encompass technical, business and operational

perspectives. In order to make a service tradable, all of the relevant aspects such as its general

description, provided interfaces, terms and conditions, pricing, SLA conditions, should be described in an

open and very generic format. For this purpose, we have decided to use Linked-open-Data USDL4, which

is flexible enough to fulfil these needs.

The Apps Chapter provides central GEs for Repositories, Registries, Marketplaces, Stores, Business

Models and Elements, Revenue Sharing as well as Service Mediation and Service Composition.

The delivered implementations of the Generic Enablers defined in the Apps Chapter provide ensembles of

interacting services. These ensembles and their interaction can be seen as blueprints of the architecture

that we envision for the Future Internet and that will act as catalyser of completely new, flexible and

innovative service ecosystems. Through these blueprints it becomes clearer for 3rd parties to understand

the intended interaction of GEs; this helps them to build their own applications and services in

combination with those of other 3rd party providers and in compliance with the general FIWARE

architecture. The key feature in this respect is the capability to compose services coming from different

parties and published on the Marketplace in order to build completely new innovative offerings.

This open and flexible framework supports 3rd party innovation at 5 different levels:

- The FIWARE composition and business framework facilitates the introduction of simple service

compositions by 3rd party providers without undue technical implementation efforts.

4 In the following we will use the shorter expression USDL instead of Linked-open-data USDL for the sake of better

readability.



- Implicitly the FIWARE Apps Chapter provides an architecture blueprint that describes how the

fundamental Enablers such as Marketplace, Repository, and Service Composition interact with each

other. Therefore, 3rd party providers can build on this core. They can introduce their own Services

and Applications as extension of this core within the platform framework of GEs provided by FIWARE.

- The chapter does not only drive technological innovation but also fosters innovative business

approaches including novel business models, based on the combination of existing service business

models. The business framework supports such combinations of business models respecting the

existing revenue sharing and SLA management.

- Finally, the current FIWARE project partners already form the core of future service ecosystems that

are open for new 3rd party players to participate and to further develop this ecosystem with respect

to new domains and technologies.

The Unified Service Description Language (USDL) enables the general description, beyond specification

of technical interfaces, of instances of the different FIWARE Generic Enablers. We expect USDL to realise

universal exchangeability of information between services. Based on the use of USDL, we see the FI-PPP

partners as the core of a future community of practice that exploits the full capacity of this language in

various domains. In particular the Linked Open Data extension of USDL prevents adoption of USDL to

become a bottleneck. Instead it rather invites partners from multiple domains to develop their own

specific extensions. This approach enables 3rd parties to bring in their own specifics such as their domain

knowledge to extend USDL towards their concrete needs while retaining the principle interoperability of

Services and Applications

The Linked USDL service description used within FIWARE is filling the gap of a language for easy-to-use

description of business and operational aspects, which also allows linking any kind of related information

on the Web. The proposed and specified Generic Enablers Registry and Repository provide a light-

weighted approach for an important core functionality of a Business Framework Platform for storing

service descriptions, business models and other metadata as well as information about the runtime

configuration. The Open Specifications for these GE is unifying the generic functionality and provide

RESTful Web APIs for easy consumption.


In FIWARE, the monetization of Applications and Services will be supported by a Business Framework

responsible for providing support for the implementation of business models in an agile and flexible

way. The Business Framework should address the definition of business elements, such as pricing models,

revenue sharing models, promotions, policies and SLAs by taking into account also cloud hosting aspects

(SaaS, PaaS, and IaaS Monetization). In particular, the Business Framework has to address Revenue

Sharing for calculating the distribution of revenues between all parties involved in a given service

offering.

Therefore, an innovative aspect of the FIWARE Business Framework is the way in which the revenues

are split up among the different stakeholders of the product. Contrary to other application

marketplaces, FIWARE will share revenues not only between the platform and the service provider, but

among any provider in the value network.

Besides, widely used marketplaces like Google Play rely on simple revenue sharing rules like a fixed

percentage of the incomes generated by an application. FIWARE will further analyse the use of more

complex revenue sharing models which also take into account additional business parameters, like

application type. Besides, revenue sharing models in FIWARE will adapt to business conditions over time

either by supporting more complex algorithms or by tuning the revenue share parameters according to

different criteria like accumulated revenue or number of purchases per service provider.



To address this challenges, FIWARE will research and develop a Revenue Sharing Engine responsible for

calculating the incomes and revenue shares among parties according to specified Revenue Sharing

models (linear and complex models), and XaaS oriented (integrating SaaS, PaaS, IaaS). This Revenue

Sharing Engine will be tightly integrated with the Business Model and Store components in order to

provide an overall business framework to FIWARE users.

While a store like Apple, Google, and Amazon is owned by a store owner who has full control over the

specific (limited) service portfolio, a marketplace is a platform for many stores to place their offerings to

a broader audience and consumers to search and compare services and find the store, where to buy. A

Marketplace usually covers all stores in a certain market. FIWARE will fill this gap by defining generic

enablers for marketplaces and providing reference implementations for them together with allowing

Telco (latent) capabilities available to third -party service providers (Identity and authentication,

marketing advertising, payments, customer care. For better modularization we separated marketplace

functionality and store functionality by introducing two separate Generic Enabler Open Specifications.

Many the products below have “Marketplace” in their name. However, in the definition of FIWARE, they

are rather stores or they combine marketplace and store functionality

One competitive advantage of the FIWARE Store GE will be the availability of a viable ecosystem of

related services and components and a fully-fledged business framework. Service providers will find in

FIWARE several valuable assets to create a killer application platform that would be attractive to the

developer and content partner community. The design of the Store GE will not focus on consumer-centric

mobile apps, but on selling enterprise-level digital assets such as apps, datasets, APIs and cloud services

that will leverage the FIWARE platform in general and its business framework in particular. Its integrated

support for pricing (including subscriptions, pay-as-you-go, etc), accounting, charging, billing and

revenue sharing models will position it one step ahead of the current market. Additionally, by providing

a one-stop, integrated shop, datasets can be offered jointly with views, apps, and other resources

through a single portal, enhancing their respective value.

Moreover, the Store GE can be offered as an “enterprise store” where different organizations can offer

their corporate digital assets to their own workers while maintaining a high level of control and security.

In this way, enterprises can increment productivity by providing custom digital assets that satisfy the

needs of their employees and that can be directly accessed and used while maintaining access control and

user permission.

Regarding App Mashup, despite rapidly increasing interest in mashups over the past years,

comprehensive development tools and frameworks that assist end users (ranging from unskilled ones to

tech-savvy ones) to mash up their own Web applications without needing programming skills are still

lacking, and in most cases mashing up a new application implies a significant manual programming effort.

The Application Mashup GE and its reference implementation Wirecloud aim at development paradigms

that do not require programming skills and, hence, target end users (being them business staff, customers

or citizens). They also help to leverage innovation through experimentation and rapid prototyping by

allowing their users:

- (a) to discover the best suited mashable components (widgets, operators and prefab mashup-lets) for

their devised mashup from a vast, ever-growing distributed catalogue,

- (b) to visually mash them up to compose the application, and

- (c) to share them with other users.

One competitive advantage of the FIWARE Application Mashup GE (the Wirecloud platform) will be the

availability of a number of libraries and APIs specifically designed to help web client developers (i.e.

javascript developers) to access different FIWARE GEs from the MAC (widgets, operators) code. This

includes the Identity Management (IdM), the NGSI-9/10 context broker, the pub/sub broker, the object



storage and much more. Additionally, the Wirecloud platform will be fully integrated with the FIWARE

business framework, specifically with the Store and the Repository GEs in order to offer a fully-fledged

store of mashable components.

Another competitive advantage will be the comprehensive approach taken to application mashups, which

considers the mashup process at both the data and the UI level. The visual editor will offer support for

wiring (i.e. communicating widgets) and piping (i.e. accessing and manipulating data sources and services

with processing elements called operators and connecting the result to widgets), and will offer support

for lightweight semantic recommendation.

The web browser (formerly the single point of entry to online services) is increasingly being replaced by

individual apps that provide tailored access to specific services. IPhone and Android apps are the most

well-known examples of this novel type of applications. Developers and providers of FI applications

therefore need to develop such hybrid “products”, i.e. mashups able to be run both in the web browser

and as a standalone app. Indeed, when executed in an app context, some parts of the mashup could be

executed as html+javascript code like they will do in a web browser, whereas other parts will require to

be executed as native code for the sake of a better user experience (e.g. maps are a good example of the

latter).

None of the existing mashup platforms offer support for these mobile platforms, and FIWARE addresses

this gap through the Application Mashup GE, which supports application mashups able to be run both in a

web browser and in a mobile device (e.g. a tablet). The proposed architecture avoids to exacerbate the

fact that app development today is a highly platform-specific endeavour, and opts for allowing multi-

platform app development by extending the current functionalities and services offered by platforms

such as Titanium, Phonegap, Cordova or Xamarin.


The GEs in our chapter are organized to support multiple usage scenarios:

- Exploring new business models with the Business Framework

- Revenue sharing

- Supporting service composition and crowd-sourcing

- Supporting Interoperability with Mediation

- Supporting a Data Market

- Supporting an Enterprise Digital Assets Store

- Monitoring and configuration of cloud infrastructures through dashboards

All GEs of the Apps chapter together support these usage scenarios with a set of unique features:

- A first group of benefits relates to functionality offered to end users. First, the implementation of

highly configurable dashboards based on data- and event-based wiring of widgets for the creation and

operation of cockpits to monitor and create composite FI applications. Key feature is the integrated

and seamless way datasets are visualized and used by the various FI applications, this includes the

way the applications change their behavior according to new data comes into the datasets.

- Second, the ability to allow potential customers to search and to discover products (both innovative

services and datasets) that fit their own needs throughout different providers is important. The

search results allow the objective comparison of existing offerings based on customizable filters.

- As a third benefit, the capacity to monetize FI applications, services and datasets allowing the

creation of flexible pricing and revenue sharing models and managing the offerings though the entire



lifecycle, including features such as access grant or automatic deployment of purchased applications

in FIWARE-LAB is supported.

- Fourth, the support to service providers to either delegate the management of their offered APIs

offered in order to perform business tasks such as accounting or to allow service providers to define

complex use-based pricing models is offered.

- Fifth, the capacity to visualize data in innovative way taking into consideration the need for the end

users to define the way they want to visualize and analyze different datasets. Such needs include

summarization and simplicity as driving forces is supported.

In the sequel, the four usage scenarios for the GE collection of the Apps chapter are detailed:

1) Usage scenario A: Exploring new business models with the Business Framework

The key objective of FIWARE’s Business Framework (BF) is to build and support an ecosystem of apps and

services that is sustainable and fosters innovation as well as cross-fertilization. The business framework

usage scenario is comprised of a set of GEs like: service-based tools (marketplace GE, repository GE,

registry GE), revenue sharing engine, mediator, and business elements and models (BEMES). The set of

interrelated components supports managing apps services in the business framework across their whole

lifecycle: from creation and composition, to monetization and revenue sharing.

The set of Generic Enablers (GE) identified here are described also:

- The Repository GE is used to store service descriptions, which might later be published (uploaded) in

a service registry, a store, or a marketplace, or the other components of the business framework.

- The Registry GE stores service descriptions, but for a different purpose – for maintenance,

administration, and retrieval of services in the service delivery framework environments. Here,

runtime information such as service endpoints or service instance information is handled which can

be accessed by the consumers of the registry. For example, service endpoints can be stored here and

located here by the store or composition framework GEs.

- The Marketplace GE and Store GE, where stores are used to collect a catalog of services which are

then offered by a store provider while marketplace can store collections of the offer collections from

different multiple stores. Usually, all buying transactions are handled in a Store and not in a

marketplace. There are existing Internet sales platforms that actually have marketplace and store

functionality combined.

- The Business Elements and Models Provisioning System with its Business Modeler GE and Business

Calculator GE handle the monetization of services or applications as well as their

compositions/aggregations. Pricing schemes are modelled in business model definitions. While the

published service description represents the public view of the business model offered to the

customer, the business model definition defines the way in which customers pay by application and

services and the way in which the incomes are to be split among the involved parties. The information

in these business model definitions is stored and handled in the rating/charging/billing systems.

- The Revenue Settlement and Sharing System GE support the distribution of the revenues produced

by a user’s charges for the application and services consumed. These charges can be distributed and

split among different actors. The Revenue Settlement and Sharing System serves to the purpose of

splitting the charged amounts and revenues among the different services providers.

- The Mediator GE offers interoperability support to its users. Despite the data representation

heterogeneity in the market, a common way of handling the business processes to request data

mediation functionality is offered by the Mediator as a gateway component by dynamic mediation

techniques such as data mediation or protocol mediation.



The following figure shows how these GEs can be interconnected and used by multiple companies in

order to support multiple deployments. For example, a service provider in company A stores service

descriptions in a repository instance. In company B, this repository can be accessed by one or many

marketplaces where a services index catalogue is established. A revenue sharing system instance can be

used to process incoming data (e.g. upon selling of services) using a connection with marketplaces (and

through this indirectly with the repositories). Services from these marketplaces can be used e.g. in

Company D within a composition mashup environment of Apps chapter (see below), or in a Company C

such services can be accessed by a mediator system that is in use in this company. Likewise, a service

provider in Company C can store his own service descriptions in an own instance of a repository in turn.

This deployment scenario highlights that the GEs in the business framework can be used in many

instances which are interconnected and by various stakeholders at the same time (called “a game of

many”).

Figure 7: Usage scenario with multiple deployment options in the Business Framework

There are several value propositions stemming from this business framework scenario for potential users:

Because the tools implement a generic way of structuring, storing, and exchanging service information

data between stores, marketplaces, repositories and registries, and other tools, a significant

simplification of the implementation effort needed by adopters is achieved. The tools interoperate with

each other and therefore the tool integration as well as the concept integration is much simpler as if

many store providers, marketplace providers, and other stakeholders would need to harmonize their

efforts and their implementation plans. Likewise, service providers can advertise their services in one

service description format to many stores or marketplaces at the same time and thus increase their

market reach.

Using a single service description format, multiple services can be easier combined with each other in

offerings for an added-value of the single services of which they are composed. The service



implementations need to be integrated with each other technically, of course, but the service offerings in

the stores and marketplaces can be easier assembled.

The revenue sharing concepts in the Apps chapter allow for an easier adoption and experimentation

with new business / pricing models that allow for the sharing of revenues between multiple stakeholders

after a set of services has been bought by a customer (e.g. the revenues can be shared among the

different service providers of a service composition offering).

The revenue sharing systems are implemented as Apps Chapter GEs and as such they can be reused

instantly with only configuration efforts (instead of implementation of a similar functionality) thus

lowering the total cost of development (TCD) and total cost of ownership (TCO) significantly.

2) Usage scenario B: Revenue sharing

The revenue sharing usage scenario is comprised by the RSS GE. The RSS GE offers advanced revenue

management capabilities which enable the proper monetization of applications and services. Together

with the rest of the FIWARE's business framework GEs, it creates a powerful trading environment which

will help developers and service providers reach and interact with a large amount of customers while

requiring very little effort. In addition, sophisticated analytics and reporting tools will help service

providers better understand customers’ behaviour and business trends.

The RSS GE is part of FIWARE's Business Framework and thus can work in close cooperation with other

GEs like the Store GE and the Business Elements & Business Models GE. However, it can also work in a

standalone way. The following figure shows how the RSS GE interacts with others GEs in the business

framework:

Figure 8: RSS relationships with other GEs and actors

The RSS receives CDRs (Charging Data Records) from the Store GE containing the information of one

charging event (subscription or use of a service, including refunds if needed). This information is stored in

the RSS Repository and will be used to calculate the revenue sharing between involved actors according

the RSS models provided by the Repository GE. The information from the service providers is obtained

from the Registry GE.



Moreover, the Store GE uses the expenditure limit management functionality implemented in the RSS

GE that helps in the prevention of fraud. Application providers can limit the amount of money spent

using the services by a customer in a specific time interval by providing a maximum limit that cannot be

exceeded and a user notification limit. For each charging event, the accumulated balance is checked and

updated. Once the limit is exceeded, it will not be possible to purchase anything until next period of time.

The RSS GE offers also two web interfaces for RSS and Store administrators allowing them to perform the

following operations:

- Management of settlement process, files and transactions

- Management of RS models

- Management of stores and application providers

- Access to graphical reports

There are several value propositions stemming from this scenario:

- As other scenarios in FIWARE, RSS capabilities are offered as open APIs freely available in open

ecosystem architecture. The enablement of these APIs simplifies the deployment of new services and

applications into stores lowering TCD and TCO for involved parties.

- Thanks to the enablement of more advanced business models could increase revenues. Service

providers can receive a share of the revenues generated by their applications in a more advanced

way that usually shown in other Marketplaces as it support advanced revenue sharing mechanisms.

Revenue sharing is based on a set of business models (revenue sharing models), which dictate how to

distribute revenues based on a combination of parameters such as product class. For instance, the

revenue sharing model used to calculate payments to a given Service Provider for music may be

different from the one used for applications.

- Easy access to business information for service providers, store owners and marketplace providers:

These players have access to market analysis and reports on their revenue information and how these

revenues are shared between the involved actors in the application or service that could help them in

their business decisions. Example of these reports can be the quantity of amounts received in a

period, number of transactions per application provider, or information regarding the most purchased

applications

- Help to prevent fraud by controlling the expenses for customers thanks to the Expenditure

management functionality available in the RSS GE. Today, it has been a big growth in the number of

electronic transactions involving payments. A priori, neither providers nor customers are completely

trusted about the authenticity of each of these transactions. Due to a fraud risk or due to the

customer could take the control on his/her expenditures; functionality about the expenditure control

is useful and can be integrated in the RSS generic enabler. Thanks to this new functionality, a

customer or provider is able to establish expenditure limits for a given period of time (monthly,

weekly …). So, each of the transactions that a customer intends to do is previously checked in order to

see if the limit has been reached, allowing the transaction or not. Customers will not be able to buy a

service or product until the next defined period of time. This way, the impact of a possible fraud is

minimized and customers are not able to control their expenses. The expenditure limits could be

fixed for any user in application providers or specific users in any application provider. Additionally,

through the expenditure limit functionality, some umbral information can be given in the way that

the payment system can launch notifications when the umbral are reached, providing additional

information to the user for a better management of their expenses.



3) Usage scenario C: Supporting service composition and crowd-sourcing

The application services ecosystem framework offers 4 GEs for composition and mash-up:

- An application mash-up supports end users to integrate heterogeneous data sources, application

logic, and UI components (widgets) sourced from the Web to rapidly create new coherent and value-

adding composite applications for common routine situational or instant tasks. The end user

composes a set of off-the-self widgets and data sources into a lightweight application mash-up.

- A service mash-up targets telecommunications-related services mashups and supports end users

without programming know-how to compose and operate their own telecommunication service

mash-ups for their immediate needs in the special application domain of communication,

organization and information. Composition is supported by a data-driven UI based on a set of pre-

configured services.

- A lightweight semantic-enabled service composition editor supports business analysts to design

domain specific business processes in the form of as service compositions by describing them using

domain specific vocabularies (lightweight semantics) without deep technical expertise. This generic

enabler will help to reduce the existing gap between the business analyst and the service integration

roles and improve the communication among them. This will in turn lead to a more efficient and

effective business processes creation workflow. Additionally, this enabler will enable business

modelers and service providers to work with a common vocabulary for annotating the processes and

discovering the most appropriated services to accomplish their tasks.

These GEs enable the composition of new value added services and new mash-up applications, based

on the ecosystem of applications and services. The ultimate goal is to build a complete ecosystem, where

stakeholders can both build value added services, as well as offering them. Published resources, services

and widgets can be then reused within the ecosystem, thus fostering the collaborative development of

applications (crowd-sourcing).

The following diagram shows how these GEs and the Business Framework Consumption Bundle can be

interconnected and used by multiples services providers in order to create new added values services,

based on the existing ones through the composition and the mash-up services. In this scenario, we can

found different actors, the involved GEs and their relationships.



Figure 9: GEs interacting with multiple service providers

This scenario highlights that these GEs in the business framework allow to consolidate an

heterogeneous ecosystem, facilitating the process of obtaining needed services or content by soliciting

contributions from a large group of stakeholders. There will be more services at their disposal to compose

different functionalities and then getting more value from Internet.

There are several value propositions stemming from this framework.

- The capabilities of composition and mash-up allows the developers and service providers to build up

applications from the composition of existing services, which can be part of the ecosystem or not.

They can build their applications easily combining different services and reusing the services

functionality that cover part of their requirements. Accordingly, they will do this job in less time to

market and saving costs by reusing existing services instead of developing new ones.

- Service providers and developers can reduce the cost of the development with the assisted visual

design and execution of service composition for technical and non-technical user, allowing to non-

technical people to create added value services by composition of basic services. Besides, through the

available tools the service providers can reduce the existing gap between technical and business

teams, working with a common vocabulary for describing and discovering the most appropriated

services and improve the communication among them. This will in turn lead to a more efficient and

effective business processes creation workflow and they can build complex applications more

valuable in less time, hence reducing cost.

- Besides, service providers and developers can advertise their new composed services in the

ecosystem to many stores or marketplaces at the same time, and thus increase their market reach.

Likewise, they can take advantage of the same value proposition of the Business Framework, since they

will be part of the same ecosystem as the revenue sharing concepts in the Apps chapter (easier adoption

and experimentation with new business / pricing model), easy access to business information for service

providers and store owners and marketplace providers and single service description format to

interchange services and data. This scenario allows the collaborative development of application (crowd-

sourcing) and makes more extensive the use of services through this offer-demand ecosystem that

facilitate the population of services in Internet. Indirectly, the massive usage of service (composed or not)

will cause the increment of the services demand caused by easier access of common stakeholders to



service composition. Hence, the market for services provider will also increase and they will have more

business challengers to be achieved, enlarging their services portfolio.

In the remainder of the section we provide some details about application mashup. The following figure

describes a common usage scenario of the Application Mashup GE:

Figure 10: Application Mashup GE Usage Scenario

As shown in the figure, a developer creates a number of widgets to support the UI of some back-end

services and data. These widgets are conceived from the very beginning of their inception as the building

blocks for a number of possible dashboards and, once developed, they are made available to other

developers and to end users though a shared catalogue provided by the Store GE. End users, without

programming skills (e.g. domain experts), use the widgets made available by the developers to easily and

visually build operation or monitoring dashboards, useful to accomplish with their concrete tasks. In doing

so, they use Wirecloud to discover the widgets of interest, visually arrange them to compose the

dashboard with the desired layout, and interconnect those widgets to allow the interchange of data and

events. Once built, the new dashboard can be shared with other users through the Store. The end users

can also wrap these dashboards in external portals and web pages,

There are several value propositions stemming from this framework:

- Wirecloud (the Application Mashup GE Reference Implementation) builds on cutting-edge end-user

development, RIA and semantic technologies to offer a next-generation end-user centred web

application mashup platform aimed at leveraging the long tail of the Internet of Services. Web

application mashups integrate heterogeneous data, application logic, and UI components

(widgets/gadgets) sourced from the Web to create new coherent and value-adding composite

applications. They are targeted at leveraging the "long tail" of the Web of Services by exploiting rapid

development, DIY, and shareability. They typically serve a specific situational (i.e. immediate, short-

lived, customized) need, frequently with high potential for reuse. Is these “situational” characters

which preclude them to be offered as 'off-the-self' functionality by solution providers.

- Web application mashups can be manually developed using conventional web programming

technologies (e.g. see http://programmableweb.com). But this fails to take full advantage of the



approach. The Application Mashup GE aims at development paradigms that do not require

programming skills and, hence, target end users, being those citizens, knowledge workers, portal

designers, etc. It allows end users to easily connect widgets in a mashup to create a full-fledged

dashboard with RIA functionality. It also allows end users to easily connect widgets to back-end

services or data sources through an extendable set of operators, including filters, aggregators,

adapters, etc.

- The Application Mashup GE fosters innovation through experimentation by choosing the best suited

widgets, operators and prefab mashup-lets for your devised mashup from a vast, ever-growing

distributed catalogue

- The Application Mashup GE allows end users to share their newly created mashups with other

colleagues and users, as well as to comment them, tag them and rate them to foster discoverability

and shareability

- Finally, the Application Mashup GE helps both developers and end users to build a strong

community by sharing widgets, operators and newly created mashups with other colleagues and

users/customers, as well as by commenting, tagging and rating others' widgets, operators and

mashups.

4) Usage scenario D: Supporting Interoperability with Mediation

The Mediator GE allows centralizing and abstracting the access towards the heterogeneity of devices

and applications, exposing capabilities through different protocols, interfaces and data models. The

Mediator GE offers orchestration capabilities, too.

- The Mediator supports interoperability at different levels, namely: between GEs, between external

Applications, and between GEs and external Applications.

- The Mediator GE can be configured to implement the needed functionalities, including:

- Exposing a uniform interface and data model towards a plethora of heterogeneous devices and

sensors.

- Routing incoming messages towards the right target device or service based on the content of the

message (or other criteria).

- Splitting a course grained task into many specific items that shall be executed by different actors

(device or applications), dispatching the split tasks and aggregating all results in order to return the

whole result to the caller.

- Performing the role of event broker: a client application interested on events from a particular set of

devices or other applications can subscribe to them using a particular service exposed by the

mediator where all relevant event sources are configured.

The last two scenarios are only introduced, as they are intended for the second phase of FIWARE.

Nevertheless they are mentioned as they imply some value propositions stemming from the Business

Framework and the App Mashup GEs, respectively.

5) Supporting a Data Market

Being one of the portals deployed in FIWARE-LAB the Store GE represents the main showcase of the

project for offering digital assets. Therefore, it is the best way for advertising your datasets and makes

them available for prospective users. However, this is not the only advantage of publishing the data in the

Store GE since you will also get the possibility of:

- Managing the users that can access your data: This is very important since in some cases you have

confidential information that cannot be spread.



- Forcing the users to accept some terms for using your data: in some cases, you will want the users of

your data to accept some terms for using it (i.e. you want to offer your data for free but you have to

ensure that this data is not used with commercial purposes).

- Charging the users for accessing your data: there are some conditions (conflicts of interest, security,

competence,...) that force you to publish data with cost. In those cases, you can use CKAN and the

Store together to charge the users for using your data. You are able to choose different payment

models:

o Single payment: Users pay once.

o Subscription: Users are forced to pay periodically (daily, monthly,...) for using your data. In

addition, users will be able to cancel the subscription but they won’t be able to access the

data anymore.

o Pay per use: Users pay based on the amount of information consumed.

6) Monitoring and configuration dashboards for cloud infrastructures

- The Application Mashup GE can be used for creating monitoring and configuration dashboards for

cloud infrastructures. Those dashboards can provide single node or multiple node management

operations depending on the role of the administrator (global or local to a node). Functionalities

provided by those dashboards can be categorizing into resource management and maintenance

features:

- Resources management. This set of tools should support the management of resources inside the

cloud infrastructure. For example, taking as example the FIWARE-Lab environment, those resources

would include: design flavour of VMs, management of overcommit rates for the nodes, policy

definition for resource usage by users (e.g. insulate a tenant on a specific server), management of

pools (leveraging the mechanism of Nova host aggregates) incl. repurposing, support for workload

mobility between nodes (user/admin-initiated, or due to node failure), etc.

- Node maintenance. For example, synchronising the image and software catalogue across node,

backup node configuration (files and DBs), scheduling and notify maintenance operations.

2.5. Interface to Networks and Devices

In order to become widely visible and adopted by end users, the FIWARE Future Internet platform must

not only offer server functionality but must also offer much improved user experiences. The Advanced

Web-based User Interface chapter contains a set of GEs providing advanced user experience using a Web

based UI approach based on an extended version of HTML-5.

The technology in this chapter is based on the Web technology stack, as the Web is quickly becoming THE

user interface technology supported on essentially any (mobile) device while already offering advanced

rich media capabilities (e.g. well-formatted text, images, video). First devices are becoming available that

use Web technology even as the ONLY user interface technology. The Web design and programming

environment is well-known to millions of developers that allow quick uptake of new technology, while

offering a proven model for continuous and open innovation and improvement. We leverage this

development and extend HTML with a number of new capabilities that can be used to significantly

enhance the UI capabilities and improve the user experience.

The GEs of this chapter are grouped into four main groups that together provide a comprehensive set of

services for application to implement advanced, highly-interactive user interfaces:



- The Client Core provides the core functionality for creating and JavaScript based applications. The GE

provides three core tools which help any developer create a modern mobile centric distributed

application. These are: (1) Enhanced functionality allowing JavaScript code to take advantage of

native device features. (2) Easy development of both server (cloud) and client (mobile) code into a

single release, with an easy to use communication mechanism. (3) Integrated OoE measurement, and

adjustment via network QoS management.

- The Server Core mainly provides a scalable synchronization server that allows multiple Advanced

Web-UI instances running on different clients to synchronize in real-time. A key element is the use

of a highly flexible and highly scalable design that will enable the dynamic repartitioning of the 3D

environment for different server functionality like scripting, physics, and others. A SceneAPI is used to

offer remote services to connect to a 3D environment and modify it in real-time.

- The Supporting Services provides services that are commonly being used when creating Webbased

user interfaces. They include services such as Cloud Rendering that allows for rendering complex

scenes on servers and streaming the results using common video streaming functionality, Display as a

Service (DaaS) that virtualizes displays by connecting them to applications over the Internet, GIS (geo

data) and POI (point of interest) data providers that offer access to 3D geographic data in various

forms of the entire earth as well as the ability to define 3D entities in the world together with their

metadata such as Augmented Reality markers or (dynamic) 3D content representing the entities, as

well as services for capturing 2D and 3D data from the real world to be used in the 3D UI experience.

- The Application-oriented Services operate on the application level. They provide tools for Augmented

Reality (AR) via hardware-accelerated basic image and computer vision processing necessary for

adding virtual content to real world scenes, for Real-Virtual Interaction that allows users to directly

interact with sensors and actuators of the Internet of Things (IoT), as well as for defining and

controlling Virtual Characters in 3D scenes. An Interface Designer allows users to interactively edit 3D

world in the same browser environment that is also used to run an application.

The set of GEs in the Advanced Web-based User Interface chapter and their relationship is shown below:

Figure 11: The four groups of GEs of the Advanced Web-Based UI chapter and their relationships




The GEs of this chapter form the basis for developing advanced user interfaces for applications. They

can be used alone, together in almost arbitrary selections, as well as together with other GEs from the

FIWARE platform.

- For example the Streaming GE can be used for uploading captured data to a data store for including

video as textures in dynamic 3D scenes. Data from other GEs can be visualized and placed within the

3D world around us using the Augmented Reality, GIS, and POI functionality provided by this chapter.

- Additionally, virtual objects can be used to visualize and control the real world, e.g. through IoT

sensors and actuators.

Additionally the followed Packages have been published in FIWARE Catalogue

1) Package 1: “EPC Framework Package“

Partners: DT, FOKUS

Used GEs: components of S3C

Delivered to be offered at partner’s premises as “dedicated instances”

Publication in FIWARE Catalogue

2) Package 2: “Proxy-OSGi and IoT Adapter Package“

Partners: Technicolor, ORANGE, TI

Used GEs: Cloud Edge, Esper4FastData, ZigBee Adapter

To be offered at user’s premises as “dedicated module” (the could Proxy is a hardware box)

Publication in FIWARE Catalogue

Package 1 and 2 would not be continued through FIWARE follow-up project since no evolvement of GEs

delivered was foreseen.


The focus of I2ND GEs inside the FIWARE platform is to exploit functionalities from the connected

devices, the network and the end termination towards the applications and services providers.

Therefore it is possible to create an additional set of 3rd party applications incorporating the special

functionalities of such Generic Enablers. Via special APIs, the 3rd party applications and/or services are

able to retrieve network status information, set up application based QoS parameters, exploit

functionalities of an end-terminal or from the network side and put processing power as well as storage

capacity towards the network-cloud-edge. Four GEs are defined in the I2ND architecture:

- CDI (Connected Device Interface): It is a GE which provides a set of runtime APIs available to

application developers. The CDI GE provides two main types of API, on-device API which is available to

Developers who create applications which execute on the device (like an installed application), and

off-device API which is available to Developers who create cloud hosted (server hosted) applications,

which need to interact with connected devices, similar to a network service API. The APIs provide

access to device specific features, such as local hardware, and integrate with the network through

which the devices are connected to provide advanced QoE (Quality of Experience) by monitoring user

interactions and using that data to drive changes in any network dependant QoS (Quality of Service)



configuration. . Additionally CDI provides a distributed compute API which allows developers to create

mobile client to server implementations without worrying about the underlying communication

mechanism.

- CE (Cloud Edge): This GE can be seen as a “super gateway”. It is located at the edge of the home, in

between the WAN (xDSL, cable ...) and the LAN (Ethernet, WiFi, home-automation networks etc.). It

has the capacity to locally execute downloadable applications in virtual machines (or in containers),

thus giving the 3rd party application developers an easy and wide access to all the features of a

machine that is located at the user’s premises (a Linux computer in fact).

- NetIC (Network Information and Control): The API of this GE is intended to facilitate access to network

information and network control features for a wide range of 3rd parties. This will facilitate the

operation of a new class of services which require a tailored quality of service for optimum service

delivery; on the other hand the network operators retain all network control needed to maintain safe

operation of their networks.

- S3C (Service, Capability, Connectivity and Control): The API of S3C is intended to facilitate the access

to information and control of the services offered by a Future Internet network as well as to the

means for managing the connectivity parameters. The new API enables the application platforms and

the services to dynamically adapt their delivery parameters through the specific network while the

control of the network is maintained in the operator exposing the API. The parameters that can be

adapted and exposed through the specific API, address the telecom application adaptation, mediation

and exposure, the device connectivity and remote management and the exposure of connectivity

parameters such as location, resource reservations, subscription profiles and charging.

In summary, the I2ND GEs address the needs of several 3rd party innovators targeted by the FIWARE

platform, Application Developers and Service Providers being the prevailing ones.

- New or enhanced services can benefit of the additional functionality from the network side to

improve their existing services or even create completely new ones.

- On the Application Developer side, it is possible connecting via the CDI GE to a homogeneous

Interface and obtain and set settings of the end user’s device while interacting to a service which is

simultaneously able to obtain the network status, request flow/application based QoS parameters,

receive additional information from the network side and will therefore be capable to adapt the flow

settings and content specifications of its application.


On one side, regarding exploiting device features. Applications have evolved from stand along software

installed on PC, tablet or mobile phone to complex distributed software system spanning client devices

and cloud (server) installations. While application architecture has changed, the tooling and libraries used

for software development have not kept pace. Developers continue to develop separate applications for

each platform, and then integrate them into a single whole experience, rather than developing the

application as a single unified vision of functionality. The user experience of modern applications is at the

whim of the supporting network connections between client and cloud components. Bad network service

can result in a poor user experience.

- MBaaS (Mobile Backend as a service)’s like FeedHenry or Appcelerator aim to resolve part of this

problem by providing a HTML based mobile back end. Applications which are written using web

technologies for the client then experience a single technology space across both the client and

server. However rather than providing a distributed compute environment FeedHenry provides a



remote procedure call interface between client and server. This means that developers still need to

create their applications in logical silos, one for the client and one for the server.

- CDI addresses this by providing a single development environment for both sets of code, which is

provisioned to client / server dynamically at run time, thus allowing a developer to create their

application in a single logical block.

- Client side HTML technologies like Phone Gap or Titanium provide a web technology based

development environment for their customers. However they do not address the needs of modern

applications which operate in a distributed way with cloud based components.

On the other side, regarding exploiting advanced network features. Today the enterprises need easy to

use, efficient and reliable networks. This means that network management should be as transparent and

flexible as possible. The network programmability is a key enabler for a medium-to-big ICT company.

- Consequently, widespread of SDN-NFV will require easy to use configuration and maintenance tools

devoted to simply the network management while guaranteeing high network services availability,

QoS and QoE.

For enterprises and their service providers, it matters how quickly users can access applications or get

services. This means that network environments need to be as flexible and responsive as cloud computing

environments. The network must provide policy-driven connectivity to support applications placed

anywhere in the infrastructure, and be instantaneously reachable by users. This consolidation and

automation of network services is the goal of software-defined networking.

- As a result, increasingly rapid adoption of SDN is prompting enterprises and service providers to

rethink traditional network practices. They are seeking best of breed tools that can ensure an open

multivendor SDN approach to joining their network and cloud infrastructures, while ensuring

compatibility with existing environments.


Existing enterprises are increasingly releasing mobile applications as a way to capture consumer

attention. There is no greater way to remind a customer of the benefits of your product, than by having

an app installed on a device they check more often than their own wallet. In such a world time to market

is important for the enterprise. CDI’s technologies which allow an application to be created in a single

logical block, using the same open technologies both on the cloud and on the client, and with a reliable

communications link provide real advantages.

- The simplified development tasks, and single skill base reduce development cost, application

complexity and can reduce development time.

- The integration of QoE monitoring and QoS correction ensure that the applications projecting the

enterprises brands do so reliably and do not alienate their customers with applications with poor

usability

Nokia Networks is committed to support network function virtualization. Dynamic management of

networking resources both in transport networks and in cloud infrastructure is necessary to support NFV.

- The "Orchestrator" functionality of the NFV MANO architecture uses an interface similar to the NetIC

interface to manage the network resources.



- The VNP GEi is used in demonstrations (e.g. at Mobile World Congress in 2014) and in PoCs as a

network resource manager both for datacenter internal network and for transport network

connecting datacenters.

The Virtualized Services Platform (VSP) product by Alcatel-Lucent/Nuage is an open SDN networking

solution designed to address the key network constraints that limit the capabilities of the cloud

environment.

- The VSP eliminates the constraints that have held back the responsiveness and efficiency of the

network. The VSP coupled with the Nuage Networks Virtualized Services Gateway (VSG) provides

control, automation, and visibility across cloud environments without replacing all legacy systems.

- The VSP and VSG policy control framework can manage across both virtualized and non-virtualized

environments.

- In the context of this development NetIC GEs can play a role enabling network users to customize

the network for their needs.

2.6. Security

The Security Chapter deals with the creation of the FIWARE Security ecosystem. Such ecosystem

comprises a set of generic enablers for cybersecurity, Identity and Access Management, Privacy and

Trust and Trustworthiness for creation, delivery, and usage of security solutions and services for the

Future Internet, which offer several features:

- The capacity to customers to visualize the security level of their Information Systems, i.e. the

existing exploits targeting system and application vulnerabilities, automatically collected by an

embedded scanner, to detect early critical attacks with a business impact perspective, and to mitigate

the risks by implementing efficient remediation.

- The capacity to system administrators and service operators, to make user identities management in

cloud-based applications and services easier, as well as smarter access control where sensitive data

and resources in general are at risk.

- The ability for users to protect their privacy, allowing them to use digital identities without exposing

them to privacy threats such as traceability, linkability, unsolicited marketing and loss of control over

personal data and identity theft.

- The support to service providers to increase trust and confidence of users of business platforms,

particularly, to exploit an application development environment that enhance trustworthiness and an

application certification process that guarantee the production of trustworthiness evidence.

- The capacity to improve the trustworthiness of cloud ready application developed for OpenStack

cloud environment, through an embedded security features.

Cyber Security

To benefit from the current FIWARE Security Monitoring GE, our goal is to deliver a compact tool,

depending on customers' preferences, embedding a scanner tool, an Attack Paths Engine, a Scored Attack

Path and a Remediation component, easy to implement by an SME, without high skills in security

management. The major innovations introduced by the Cyber Security GE are:

- Security toolset with low security expertise requirements;



- Nessus and OVAL Scanner connectors;

- OSSIM and LogLogic SIEM connectors allowing at operational time to quickly stop an attack, using a

SIEM alert targeting an asset and, at design or forensics times, to create new SIEM correlation rules

taking into account the vulnerability paths;

- Visualization of the level of security according to the user’s preferences for risk metrics : business

impact and vulnerability severity colored scale;

- Automated remediation selection and evaluation of any counter measures initiated by the system

administrator.

- Privacy Preserving data sharing: Based on the principles of Multi-Party Computation (MPC), the Cyber

Security GE should enable its users to execute computations on data they are otherwise unwilling to

share;

- Tuning to take advantage of shared data through statistics to increase performance of the Cyber

Security GE.

Identity and Access Management

The major innovations introduced by the IAM GE are:

- The consideration of new demands or demands not yet answered (e.g. identity management of

things);

- The Compliance of the Identity management with IETF System for Cross-domain Identity

Management (SCIM) 2.0 Specification, making to manage user identities in cloud-based applications

and services easier;

- An Access Control more advanced and flexible Target matching capabilities, integrating new customer

attribute categories, dynamic Obligations and Obligation in rules;

- The Compliance of the Access Control with XACML v3.0 Core and Hierarchical RBAC Profile v1.0;

- LDAP Attribute Finder, resolving attributes from an LDAP v3 directory;

- JDBC Attribute Finder, enabling the XACML PDP to resolve attributes from a JDBC-compliant relational

database.

Advance Privacy

The major innovations introduced by the Advance Privacy GE are:

- The extension of the Issuance Service to support bridging of P2ABCE and identity source: a process

will offer the capacity to redirect a user without a valid P2ABCE-credential to the IdM GEri or another

identity source such as LDAP;

- The extension of the Verification Service to derive presentation policies from access control policies;

- The extension of the User Service for user-friendly management of credentials and profiles;

- The user de-anonymization, e.g. if he is strongly suspected to have committed a criminal act using PE

credentials;

- The revocation of the credentials of an user if he is suspecting his credentials have been stolen;



- The exploitation of the Advance Privacy GEs to contribute to trustworthiness of an app/service.

Trust & Trustworthiness management

The major innovations introduced by the Trust & Trustworthiness management GE are:

- A trustworthiness-driven (Java) development platform, permitting to instantiate easily the

trustworthiness constraints and to produce the related evidence;

- A specific development platform, dedicated to the development of applications for the trustworthy-

by-design execution platform;

- A Trustworthy Application Certification Platform supporting certificate editing, signature and binding

(“code labelling tool”).

OpenStack Security Service

The major innovations introduced by the OpenStack Security Service GE are:

- The adaption of cloud OpenStack modules for promoting their use in the development of trustworthy

apps in particular for security features;

- To make sure that security features embedded in the application use security modules of OpenStack:

i.e. Barbican, Heat/Murano, and Keystone.


We report hereafter on the main packages trough which FIWARE Security GEs Phase 1 were delivered and

from which Security GEs to be continued in Phase 2 would be built upon.

1) Package 1: “Security Monitoring“

- Partners: THALES (leader), FT, ATOS, INRIA

- Used GEs: Service Level SIEM, MulVAL Attack Paths Engine, Scored Attack Paths, Remediation, Botnet

Tracking, IOT Fuzzer, Android Vulnerability Assessment

- Delivered to be offered in FI-LAB

- Publication in FIWARE Catalogue

Package 1 would be continued through FIWARE follow-up project through Cyber Security GE that would

rely on a number of Security Monitoring GE features (namely attack paths engine, scored attack paths and

remediation) evolving them and developing new ones.

2) Package 2: “Generic Security Services: Identity Management, Authorization and Usage Control

Policies, Privacy and Trust, Data Handling”

- Partners: SAP, IBM-CH, THALES, FT, NSN-G1 (leader), DT, ATOS INRIA

- Used GEs: Identity Management, Access Control, Privacy, Data Handling

- Delivered to be offered in FIWARE-LAB




Package 2 would be continued through FIWARE follow-up project with same GE but being evolved and

open source.

3) Package 3: “Context-Based Security and Compliance”

- Partners: SAP, THALES, ATOS (leader)

- Used GEs: Context-based Security & Compliance



Package 3 would not be continued through FIWARE follow-up project since no evolvement of GE


4) Package 4: “Optional Generic Security Services”

- Partners: SAP (leader), THA, DT, INRIA

- Used GEs: DB Anonymizer, Content-based Security, Malware Detection, Secure Storage Service



Package 4 would not be continued through FIWARE follow-up project since no evolvement of GEs


If GEs in scope of package 3 & 4 were not planned to be evolved, in FIWARE follow-up project there would

a package to accommodate new GEs on Trust and Trustworthiness since it is highly demanded and so far

not covered.


The Security Chapter aims at answering the most prominent security needs on which each and every use

case can agree. For that, the Security Chapter has designed a number of Security GEs for Security, Privacy

and Trust, ranging from Security Monitoring to Context-based Security & Compliance, but also including

Identity Management, Privacy and Data Handling.

Each of these GEs has been designed to deliver the key functionalities requested by FIWARE stakeholders.

Their design takes into account the most recent security standards but also aims at facilitating evolution

of security functions, e.g., for the sake of flexibility and changeability.

In addition to that and to what these Security GEs can already offer to 3rd party innovation (e.g., Security

By Design, Security by Default) the Security Chapter has extended this initial set of GEs by another set of

Enablers, called Optional Security Enablers, in order to offer additional security services which may also

be drivers of innovation for 3rd parties. This generic approach has been successfully demonstrated in the

Security Chapter so that a number of optional security Enablers/services have already been provided and

new ones are being planned.

The innovation resulting from the use of Security GEs by the stakeholders of the other Chapters (i.e.

Cloud Hosting, Data/Context Management …) is also an innovation factor 3rd parties will take advantage

of. They will actually get rid of the burden derived from securing the solutions delivered in other FIWARE



Chapters. On the other hand, Security services advertised on FIWARE Catalogue and those described in

USDL-SEC, will become an opportunity for 3rd parties who may adopt them to secure their own services.

In this respect, we expect that innovation will be driven by contributions from 3rd parties implementing

either FIWARE GEs or their own Applications/Enablers, both being able to come up with novel security

usage concepts based on Security GEs, individually or in combination with other services.


In this section we explore the current state of the most relevant technologies involved in Security

Services, how these technologies are positioned in the current market and the added-value introduced

by FIWARE. We identified the following major differential features:

- Security Monitoring

- Built-in Identity/Access Control/Privacy Management

In the context of the Future internet, the Security Monitoring covers the whole spectrum from

acquisition of events up to display, going through analysis but also going beyond thanks to an assisted

decision support in case of cyber-attacks.

The Internet is omnipresent and companies have increasingly put critical resources online and thus have

been exposed to security flaws. This has given rise to the activities of cyber criminals, and virtually all

organizations face increasing threats to their networks and the services they provide. Traditional intrusion

prevention techniques, such as firewalls, basic access control and encryption, have failed to fully protect

networks and systems from increasingly sophisticated attacks and malwares.

To monitor IS "management" or industrial, current SIEM are based on a NAC model type (Normalize,

Aggregate, Correlate) processing events emitted by probes (or logs) with the same characteristics than big

data flow: varied variables, dense and structured. However, many events from complex and targeted

attacks do not exhibit simple structure, so that the definition of an attack signature remains a burden. The

use of expert knowledge is then essential.

It is therefore desirable to use a toolset that will detect, identify and characterize complex attacks. This

model is one of the main obstacles to the development of security monitoring solution, as the attackers

themselves also benefited flows of "Big Data" to significantly refine their procedure. Especially for the

social engineering phase, one key factor of their success, they can develop targeted attacks in context,

distributed in time and space to make them stealthier. Such attacks have become formidable and speak in

favor of centralized management of security events and smarter access control to the asset of the

company.

The performance of a security monitoring solution is generally estimated by the rate of false positives and

/ or false negative; it depends entirely on the accuracy of the rules and more generally its knowledge

model. Knowledge involved in the monitoring, diagnostic and remediation activities of security experts.

They can be grouped into two categories:

- (A) Anomaly detection - learned from AI tools, e.g. heuristic anti-virus, and

- (B) Designed or configured by human experts - the signatures, firewall rules or anti-virus.

For a SIEM, knowledge of "signature" or "rules" type is gained from prior experiments or external

knowledge:

o Laws (duration of logs preservation),

o Standards (recommendations or good practices, ISO 27001),

o Observatories such as CERT vulnerability bulletins.



To express the rules, the expert uses programming and security-domain skills, which usually makes their

development costly in time and resources, error-prone and without guarantee their expected return on

investment. Allowing the design of SIEM rules thanks to FIWARE GE would thus be a significant

improvement.

We are convince that in the current threat environment, rapid communication and analysis and

automation of threat information is the key to quickly detecting, responding and containing targeted

attacks.

In addition to Security Monitoring, FIWARE Security GEs also address the market of Identity and Access

Management (IAM), and Dynamic Authorization Management (DAM). Therefore, to make a fair

comparison, we look at leaders in both markets. Based on Forrester’s evaluation of IAM suites in 2013

and KuppingerCole report on DAM solutions in 2014, we find Oracle and IBM as the only leaders in both

markets, and therefore the ones that can compare with the full set of FIWARE Security GEs. In the next

paragraphs, we look briefly at potential strengths and/or opportunities, as well as weaknesses and/or

threats of the market leaders vs. FIWARE in the aforementioned markets.

Like Oracle and IBM, FIWARE IdM GEis support the main standards in Identity and Management such as

SAML, OpenID, OAuth, SCIM. The Access Control GEi supports the main standard for dynamic

authorization based on attributes, i.e. XACML. Like the two market leaders, IdM GEis support LDAP and

SQL queries for managing user attributes in external identity stores. The Access Control GEi also supports

LDAP and SQL queries for getting attributes from external attribute sources, and then uses these

attributes during authorization policy decision. Regarding technology, we have a much less feature-rich

user interface for access control policy administration (a.k.a. PAP, i.e. Policy Administration Point) in

FIWARE, compared to Oracle and IBM. However, the latter have made such an effort to support very

complex policies that their respective PAPs target mostly trained security-aware administrators rather

than business users.

Last but not least, Oracle and IBM tend to follow a “suite” approach, where you have to add an extra

Oracle or IBM product to enable or add a specific feature in most cases, and it gets quite difficult to

integrate with another vendor for the same features. In the end, a full working solution from either of

these two requires a significant and relatively expensive infrastructure, compared to the other vendors in

the IAM market, and, a fortiori, FIWARE. In short, it is reasonable to claim that Oracle and IBM focus

mainly on the large corporate market. On the contrary, the FIWARE Security Chapter and FIWARE in

general make significant efforts to address the needs of SMEs (Small and Medium Enterprises). In

particular, we follow a more vendor-independent approach where FIWARE partners design or adapt

GEis to be compatible with GEis from other partners, especially when required by SMEs in specific

FIWARE use cases. For instance, Thales Access Control GEi now integrates with all IdM GEs, i.e. NSN

Digital Self, Deutsche Telekom’s GCP, etc. Besides, a significant part of the Security GEs are provided as

free and/or open source or will be in the FI Core continuum.


The Service Level SIEM through the processes included in that topology, allows detecting service level

alarms from a business perspective. The Attack Path Engine is an end-to-end framework and reasoning

system that conducts multihost, multistage vulnerability analysis on a network. MulVAL Attack paths

Engine shows what attacks are possible and captures the interactions among all attack possibilities in

your system and captures the interactions among all attack possibilities in a classic infrastructure or cloud

environment. The Scored Attack path is a tool business-oriented. It provides tools to security operators

for assessing the risk and impact of attack paths. Similarly, the remediation application provides tools to

security operators for proposing cost-sensitive countermeasures to mitigate cyber-attacks and reduce

the risk level. The Botnet detection application takes DNS traffic as input for the analysis. Perfectly



adapted to the Future Internet context, it is designed for large networks, handling thousands to millions

of devices. LowFuzzer, the reference implementation of the IoT Fuzzer, is a software testing technique

that involves providing valid, invalid, unexpected or random information as input of an application. In the

case of Internet of Things devices, the target application is either the protocol implementations or the

applications that reside on a remote device. With regard to the Android Vulnerability Assessment Tool, it

is an OVAL (Open Vulnerability and Assessment Language) interpreter for Android devices.

The Core Generic Enabler components provide baseline identity and access management as well as

privacy and trust. Identity Management encompasses a number of aspects involved with users' access to

networks, services and applications, including secure and private authentication from users to devices,

networks and services, Authorization & Trust management, User Profile management, Single Sign-On

(SSO) to service domains and Identity Federation towards applications. The Access Control manages

authorization policies, making better use of identity and resource attributes; it is in this way that the

number of policies can be reduced The FIWARE Privacy Enabler is software that enables application

developers to create privacy-preserving authentication systems on the basis of attribute-based

credentials. For its part, the Data Handling GE is a privacy-friendly attribute-based access control

system, which targets mainly sensitive data. It permits to store information together with an attached

privacy policy, which regulates its usage.

The role of the Context-based Security & Compliance is to provide the security layer of FIWARE with

context-aware capabilities to support additional security requirements through the optional security

enablers developed in FIWARE (DBAnonymizer, Secure Storage Service, Malware Detection Service,

Android Flow Monitoring, It also provides, together with optional security services search and

deployment, run-time reconfiguration that will allow Use cases both deal with unpredictable context

changes and ensure the compliance with the security requirements.

DB Anonymizer is a database re-identification risk evaluation and anonymization service; it can be used

as a support tool in case of dataset disclosure operations. It deals with the estimation of the re-

identification risk associated to information disclosures, which is the risk that an attacker can reconstruct

exactly a dataset's content. Content-Based Security refers to the concept of protecting data (by meaning

encrypt and/or digitally sign data) and its metadata at its source and integrating access control in a

managed way. It provides services that protect and remove protection from data. The Malware Detection

Service, “Morphus", is a software capable of extracting (partly) a morphological signature from binary

code, that corresponds to the behavior of malware. Doing so, it may by-pass some standard encryption

techniques. The malware detection service provides a mechanism for determining if the submitted

executable binary file is sane or infected by a malware. The Secure Storage Service provides a storage for

labelled (i.e. XML DSIG protected) data. It comes with an application-level filter which authorizes read

access in function of the identity of the authenticated requester (for example, a service provider) and in

function of the sensitivity of the data.

2.7. FIWARE Platform Positioning

A new digital revolution is coming: this revolution consists of the integration of a lot of technologies we

have been using in the last couple of years; they are part of a radical change in what we understand the

Internet is. Our applications are going to need to be found and be available in any gadget and to be able

integrate with the Internet of Things. We are going to be capable of treating a lot of data, analysing it,

and extracting knowledge in order to manage things like Smart City processes.

FIWARE is the Open API platform that provides a catalogue of open-source tools to enable integrations

and connections for IoT and Smart City application design.

- FIWARE wants to become the core infrastructure that will empower our connected future.



- FIWARE promises to support smart city infrastructure, enable intelligent factories and precision

agriculture, and help entrepreneurs to carve out viable market share in a connected, IoT-enabled

world

- FIWARE-Lab is the meeting point that encourages a community of developers and entrepreneurs to

share their experiences developing applications, ask questions, and test prototypes in a sandbox

environment.

In addition to speeding up opportunities for cities to integrate smart city infrastructures, the generic

enablers also allow developers and entrepreneurs to create new applications that have commercial value.

In this way, FIWARE also acts as a business development platform. In fact, it is funding business

accelerators to help small and medium sized enterprises to create commercial opportunities using the

open source tools on the platform.

2.7.1. FIWARE Platform

FIWARE will be open, based upon a series of elements (called Generic Enablers) which offer reusable

and commonly shared functions serving multiple areas of use across various sectors. FIWARE Generic

Enablers are classified into the following main FIWARE Technical Chapters:

- Cloud Hosting Internet of Things (IoT) Services Enablement:

o The fundamental layer which provides the computation, storage and network resources on

top of which services are provisioned and managed.

o The bridge where FI services interface and leverage the ubiquity of heterogeneous, resource-

constrained devices in the Internet of Things.

- Data/Context Management Interface to Networks and Devices (I2ND):

o The enablers easing access, gathering, processing, publication and analysis of data at large

scale, transforming it into valuable knowledge available to applications.

o The enablers making it easy to take the most of underlying network infrastructure

capabilities.

- Architecture of Applications / Services Ecosystem and Delivery Framework Security.

o The frameworks to co-create publish cross-sell and consume applications/services, addressing

all business aspects.

o The mechanisms which ensure that the delivery and usage of services is trustworthy and

meets security and privacy requirements.

- Advanced Middleware and Web-based User Interface.

o A set of enablers that make it easy to incorporate 3D & Augmented Reality capabilities in

web-based user interfaces, plus the most efficient backend middleware ever.

2.7.2. FIWARE Business Canvas and SWOT

FI WARE offers and advanced OpenStack based cloud + rich library of enablers — each driven by open,

standard APIs — which offer reusable and commonly shared functions (Context Management, Internet of

Things, Advanced networking and middleware……) serving multiple areas of use across various sectors



Key partners

• EU Government

• Technology Providers

• Developers

• Entrepreneurs

• Data Providers

• Smart Cities

Key activities

• FIWARE, an open and

interoperable platform for

the use of large data to

create applications in a

connected, IoT-enabled

world.• Free Cloud capacity

enabling entrepreneurs to

test their apps.

• Ability to experiment with

real data coming from cities

Value proposition

• Avoid vendor lock-in:• APIs (Application

Programming Interfaces)

are open and royalty-free.

• Portability across platform

providers

• Interoperability of apps on

top of different providers

• Modularity• Non-intrusive, allow

different business models

• Connection to the

Internet of Things, • Processing of Data and

Content at large scale in

real time, performing Big

Data analysis, had never

been easier to tap into.

• Integration with standard

open data platform

Customer relationship

• FIWARE LAB

• FIWARE Accelerator

projects

• Feedback Through JIRA

• Social Networks -

Campusero

• Hackathons/FIWARE

challenges

• Campus Party

• Contribution to

Community of OSS

Developers

Customer

segments

• A two sided

market• Developers

(SMEs)

• End Users

(Enterprises,

Smart Cities

Cost Structure

• Tools: Computer cost, developer registration fees

and tools licenses.

• Maintenance: Typically 10% of the initial app cost,

on an annual basis

• Relevant Investments in Marketing

Channels

• Developers• The FIWARE catalogue (http://catalogue.fi-

ware.org/enablers)

• An innovation environment called FIWARE Lab

(https://account.lab.fi-ware.org/

• An e-learning platform (http://edu.fi-ware.org/)

• National Platforms which have their own SMEs

ecosystems

• FI Accelerator Programme

• Through FIWARE Foundation

• End Users• Use FIWARE partner´s existing customer

relationships.

Key resources

• The technology: Openstack

based cloud + rich library

of enablers

(FIWARE)

• A single meeting point

where innovative ideas are

incubated globally: FI-Lab

• Funding and assistance to

entrepreneurs: the FIWARE

accelerator program

• Global footprint: strong

liaisons with other regions

Revenue Streams

• As software component provider to build Generic Enables (GE,

through licensing)

• Revenues for development tools, and professional services for

customization and solution consulting

• Revenue Share: advertising

Figure 12: FIWARE Business Canvas

FIWARE gives application developers opportunities that current platform technologies do not supply

because they are usually based on different technologies, different standards, missing an overall usage

model that describes how they can be used together:

- The possibility to easily aggregate services and applications, saving efforts and costs; the adoption of

a common aggregation model by the backbone reduces the complexity of this task;

- The response to obvious market requirements regarding secure, stable and cost-efficient products;

the definition of a common standard backbone covering most of the Generic Enablers, which are

needed to develop Future Internet applications, 3rd parties are encouraged to integrate available

FIWARE services that disburden them from developing essential but expensive services on their own;

this removes a significant barrier for new 3rd parties with limited financial resources;

- The opportunity for Application Developers to focus their efforts on the actual differentiation of

their products from those of their competitors; this means a particular chance for small and medium

sized service providers to concentrate on what is crucial for their for business success.

FIWARE addresses the specific currently existing requirements and business constraints in order to

realize these business enabling factors:

- FIWARE offers royalty-free, open and standardized access points to essential services and

technologies, developed in the different FIWARE chapters, thus protecting the investment of

Application Developers;

- The architecture of FIWARE ensures the general interoperability (interplay) between the different

applications and services and, overall, the ability to combine offerings from different FIWARE Instance

Providers.



- 3rd parties become part of the FIWARE ecosystem as long as they follow the FIWARE standards but

without being forced to use all defined FIWARE GEs.

• APIs (Application Programming Interfaces) are

open and royalty-free.

• Modular design, packaged distributions and

interoperable, compatibility with AWS and MSN.

• Supported by major IT vendors and Telco

providers avoiding vendor lock-in

• Availability of experimentation

capacities/infrastructure

• Deployed by some cities in production projects

• Still perceived as an experimental platform

• Lack of standards is still one of the main

barriers for the deployment

• A low base of user for potential awareness and

understanding

• AWS enjoys a first-mover advantage allowing

an entire ecosystem of start-ups to proliferate

• IoT Momentum: Broadening service offers in

areas like M2M and context management

• Smart City potential unleash on Open

Standards and Open Data Initiatives

• Data sovereignty issues (Snowden case) that

have kept some European companies out of the

public cloud

• Acceleration programme is helping to spread

the technology and connect cities to FIWARE

Lab

• Branding issue (Who is behind FIWARE?)

• Performance and reliability is a must for cities .

• Lack of agreements from providers on an

interoperability framework like FIWARE

• Policy fragmentation

STRENGHTS WEAKNESSES

OPPORTUNITIES THREATS

Figure 13: FIWARE SWOT


The 3rd Platform is transforming not just the technology industry; but every industry on the planet. IDC

Examples include alternative payment networks in financial services, expansion of IoT technologies into

city safety, public works and transportation systems, and the expansion of location-based services in the

retail industry. The number of industry platforms – industry-specialized cloud-based data and services

platforms, usually created by leaders within the industry –will expand rapidly, easily doubling in 2015

The European Commission and the major ICT companies share the diagnosis of a digital revolution now

looming, based incorporate technologies that have been developed in internet as cloud, big data, the

internet of things and make applications that transform both do business as the daily lives of people.

We have created FIWARE so that European companies are able to capture the opportunities that will

arise in this environment.

- FIWARE want to create an open alternative that allows multiple suppliers for SMEs arise, the

application developer can choose where to deploy the application or environment in which your data

is also staying. And you can switch from one provider to another if the service offered is not

satisfactory, without having to change large parts of the application because it is based on common

standards



- At first it sound good, Generic and modular libraries to become standards, so you can switch between

providers without problems. For example, you could switch between the cloud platform of Amazon

and Microsoft without having to change any of the code of my application

- FIWARE will be able to offer this platform as cloud environment technologies, using a pay per use.

Entrepreneurs who have developed these applications in the test environment FIWARE and want to

make money, you have warranty seek appropriate support, with 24 hour service, seven days a week.

The platform is generic and therefore can be applied to different sectors, which makes sense to offer

solutions to connect things to the network, sensors, handle large volumes of data, where real time is

important and which has to do an analysis of big data.

- For example, the activity of smart cities, which are beginning to pull the platform. Others, such as

the factories of the future, about the proper execution of processes in a production line. Also in the

agro-food sector, which play role sensors for irrigation, or health.

- FIWARE offers a catalogue of ‘generic enablers’ each driven by open, standard APIs — aimed at

helping developers, and government information and data architects, to remove the complexity

involved in trying to integrate a variety of smart cities-related systems.

There are currently two large platforms that compete with FIWARE. On the one hand, is Amazon Web

Services and, second, Google. Both are private. The concept that created the European version is to open

to any developer anywhere in the world environment. Experts said the network will be revolutionized

with concepts such as the Internet of Things, i.e. any object has sensors that are connected to the

network and provide information. There will also be a host of applications that run on the cloud,

allowing extract data by analysing what is known as big data. This should lead to many new businesses.

FIWARE is the European alternative to Amazon and other platforms APPs with a very special feature: it

is fully open and royalty free. It also has a laboratory, FIWARE-Lab, where entrepreneurs can develop their

ideas and find customers and investors seeking applications

- The main feature and the added value of FIWARE is that it is a platform whose components

guarantee APIs (Application Programming Interfaces) open and royalty-free.

- The program has developed also a FIWARE Lab: Open meeting point where entrepreneurs can realize

their ideas and show their work to clients and investors who might be interested in the applications

developed

- An innovative aspect of the FIWARE Business Framework is the way in which the revenues are split

up among the different stakeholders of the product. Contrary to other application marketplaces,

FIWARE will share revenues not only between the platform and the service provider, but among any

provider in the value network. Apple, Google, and Amazon is owned by a store owner who has full

control over the specific (limited) service portfolio, Google Play rely on simple revenue sharing rules

like a fixed percentage of the incomes generated by an application

- FIWARE´s integrated support for pricing (including subscriptions, pay-as-you-go, etc), accounting,

charging, billing and revenue sharing models will position it one step ahead of the current market.

Additionally, by providing a one-stop, integrated shop, datasets can be offered jointly with views,

apps, and other resources through a single portal, enhancing their respective value.

- What FIWARE also brings new is that public authorities can turn their data into the platform for

companies to develop applications in the field of intelligent cities or electronic health. In fact, Neelie

Kroes, European Commissioner for Telecommunications, made in September last year calling on cities

to publish data in this service.

- One of the things we are enabling with FIWARE is choice around what data center is being used.

Europe in this moment is deciding what its role is in the future society, and things like energy control,



and the control of digital information, are very important. Where does Europe host this large volume

of numbers, values and parameters? In a server on the Amazon cloud?

We are not just limited to Europe and we are actively trying to reach agreement with other regions that

may share a similar view in regards to open source platforms and open data storage

2.7.4. Value Proposition: Why FIWARE?

The unique feature of FIWARE is its holistic approach and enables FIWARE to become the Operating

System of the Internet-Computer.

- It provides advanced Cloud capabilities and a library of Generic Enablers providing Open APIs that

enable innovative applications in multiple sectors.

- It provides connection to the Internet of Things, gathering, publishing and processing of Data and

Content at large scale in real time, performing Big Data analysis, application cross-selling and creation

all of these ICT-enabled innovations have never been easier to tap into.

FI-WARE major differential features

9

• Federation of infrastructures (private/public regions)

• Automated GE deployment and scalability managementCloud

• Context Management and Open Data Standard APIs

• Real-time Context/Media-stream Processing and BigData analysis

Data

• Easy plug&play of devices using multiple protocols

• Automated Measurements/Action ��Context updatesIoT

• Visualization of data (operation dashboards)

• Publication of datasets/servicesApps

• 3D and AR visualization of context

• Advanced KIARA middleware supporting real-time communications

MiWi

• Security Monitoring

• Built-in Identity/Access Control/Privacy ManagementSecurity

• Exploiting advanced network features (e.g., SDN)

• Interface to smart devices (e.g., robots)I2ND

Figure 14: FIWARE Major differential features

On the whole, FIWARE is an open platform for the use of large data to create applications in a

connected, IoT-enabled world:

- FIWARE offers and advanced OpenStack based cloud + rich library of enablers

- Free Cloud capacity enabling entrepreneurs to test and host a permanent showcase of their

applications.

- Ability to experiment with real data coming from cities (not just open historic datasets but real-time

data).



FIWARE will be the European alternative to Amazon and other platforms APPs with very special

features:

- APIs (Application Programming Interfaces) are open and royalty-free, saving efforts and costs

- Offers a Data Center alternative to the incumbent players (i.e. AWS)

- Modular design, packaged distributions and interoperable, compatibility with AWS and MSN.

- Non-intrusive, support of different business models

The next battle will be to dominate the Operating System of the computer in which the Internet will

transform. Unless a collaborative effort is made, this battle will be dominated by the existing incumbent

players (e.g., Google or Amazon) with their own proprietary platforms. The FIWARE goal is to make sure

that an open platform alternative will exist around which a sustainable open innovation-driven

ecosystem can be created. The same way, existence of technologies such a Linux or Apache has been

crucial in how the Internet and the Web looks today, existence of an platform alternative like FIWARE can

be crucial in how the Internet and the Web may look like in the Future.

The existence of an open platform alternative will ensure that application providers will be able to

choose who will provide and operate the environment where their applications will be hosted. Data

providers, including Open Data providers, will also be able to choose who will provide and operate the

environment where their data will be hosted and exploited. Their decisions can be driven not just based

in economic savings but the trustworthiness of the platform provider. Applications and Data providers

can also better protect their investment because of the ability to port applications and data to an

alternative platform provider if a given platform provider stops meeting their requirements, thus avoiding

getting locked in a given platform provider.



3. FIWARE EXPLOITATION STRATEGY: Open APIs for Open

Minds

A new digital revolution will take place as a result of applying a number of technologies that have

emerged recently, mainly Cloud, Big Data and Internet of Things technologies. All applied in a secured

manner and complemented with technologies that enrich the user experiences (3D, augmented reality).

The goal of the Future Internet Public-Private Partnership is helping ICT companies and

businesses/organizations in Europe and in other regions who wish to join Europe in this endeavour, to

capture the opportunities that will emerge in multiple sectors due to the new digital revolution that is

coming.

The approach to reach these goals consists in creating a sustainable innovation ecosystem engaging

application/solution providers (not only traditional integrators but also new and existing SMEs), ICT

infrastructure providers and domain stakeholders (the businesses and organizations ultimately

transforming their processes). Such ecosystem should bring value to all these actors. In other words,

there should be a clear benefit for them to become part of the ecosystem. The value proposition of this

target ecosystem is built around four major pillars:

- The technology: FIWARE is an innovative, open, interoperable, platform that is device and network

agnostic composed of Cloud Hosting, Applications and Services Ecosystem, Data-Context

Management Services, Internet of Things Service Enabler and Interfaces to the Network and Devices

that offers a complete solution for cost-effective creation and delivery of versatile digital services,

providing high QoS and security guarantees

- A single meeting point where innovative ideas are incubated globally: FIWARE-Lab

- Funding and assistance to entrepreneurs: the FIWARE accelerator program and several development

tools for training support, webinars and e-learning platform, edu.FIWARE.eu

- Global footprint: strong liaisons with other regions. The ambition of FIWARE is to extend FIWARE-Lab

across entire Europe and other regions and to promote this beyond by means of hackathons, interop-

dev meetings, industry fairs, and similar events targeting developer communities. This will be

complemented by an extensive training and support offer provided, by FIWARE, tailored to SMEs,

Web-Entrepreneurs, and also industry players across the ICT and Non-ICT sector.

The FIWARE technology foundation is the cornerstone of the Future Internet PPP and its slogan very

well summarizes the spirit: “Open APIs for Open Minds”. This slogan tries to capture two ambitious goals:

- The creation of standard open technology foundation: that is FIWARE.

- The creation of an open innovation ecosystem around the technology

According to D 11.1.3 Market Analysis, software vendors lack the perspective to develop software

within a software ecosystem. The success of a software product depends not only on the quality of the

functions it provides but also on the success of its interdependent hardware, software, and other players

within its ecosystem. The software ecosystem studied thus far has largely ignored the importance of the

market, which is the ecosystem's energy source.

The market affects all players in the ecosystem, determining whether the software product can succeed.

But more than anything else, perhaps, is the need to create a developer community, or to connect with

existing ones.

- At a technical level, developers want simple ways to integrate their software with a platform



o Give developers a technical reason to commit to a platform (help me get great software

done better) as well as a business reason (with financial reward just one of the issues).

o Platforms allow developers to make money the obvious way, by helping to get software

into customers' hands. They do that by creating popular app stores, helping with

marketing, creating awareness, and of course by selling a lot of devices or host apps.

- FIWARE Lab should comprise all what is needed to stimulate awareness among target

application providers and users so that they feel attracted to participate and build a

community. It also is planned to facilitate:

o Tech support, Code, Training and Community

o Tools helping members of the community to share their experiences, needs, etc.

o The creation of new business models. Experimenting with ways to combine products,

services and data to create entirely new businesses often with software playing a critical

role in enabling these new models

o Tools to ensure users' trust in the interoperability and re-usability of the results (e.g.,

clear licensing models to encourage early adoption of technologies and their rapid

integration into commercial products

3.1. FIWARE is the Core Platform

FIWARE is the Core Platform of the Future Internet that eases the creation of innovative applications,

lowering the costs and complexity of serving large numbers of users globally and handling data at a large

scale.

- FIWARE seeks to provide a truly open, public and royalty-free set of open specifications that will

allow developers, service providers, enterprises and other organizations to develop products that

satisfy their needs while still being open and innovative.

- FIWARE will dramatically increase Europe’s Information and Communications Technology

competitiveness by introducing an innovative infrastructure that enables cost-effective creation

and delivery of versatile digital services, high quality of service and security guarantees.

- FIWARE will be open, based upon a series of elements (called Generic Enablers) which offer

reusable and commonly shared functions serving multiple areas of use across various sectors.

Nevertheless marketing a platform to developers isn't like selling to customers. Developers are not a

business model, you pay them or your customers pay them.

- The most important thing is to make developers believe that they are building for the next

ubiquitous, exciting platform.

- Vendors need to treat their APIs as a product that is marketed to the developers they want to

attract. This relies on the ability of an API to be discovered and marketed appropriately, but once

you've cleared this hurdle you need to really quickly provide an easy on boarding process for

developers to start using it.

- Developer recruitment efforts can use all the traditional ways to get attention (free t-shirt or

coffee mug) but some think more creatively.

Some elements of a developer program are almost checkbox items.Among them:

- Self-service access to developer materials, such as API documentation

- Developer programs available 24x7



- Lots of sample code that's simple to try out

- Quality tech support (specific to developer issues) with quick turnaround, by e-mail, phone, and

other media (such as IRC).

One important option is computer-based and classroom training, or at least face-to-face developer

gatherings where developers can help each other, share ideas, and socialize. But more than anything

else, perhaps, is the need to create a developer community, or to connect with existing ones. The latter

is an option especially for those trying to get developers to write for non-traditional platforms.

3.2. FIWARE-LAB: A true open innovation ecosystem

There is a free experimentation environment called FIWARE Lab ( https://lab.fi-ware.org/). This

environment allows you to deploy GEs and try them. We are progressively incorporating automated

deployment facilities to easily install instances of our software on top of your virtual infrastructure on

FIWARE Lab. The FIWARE-Lab environment will not only be where developers can put FIWARE at work

and materialize their ideas. It will become the pillar of global Open Innovation Ecosystem bringing

attractive incentives to the different stakeholders. Entrepreneurs, Developers

- Ability to test with real data

- Ability to run trials with real users

- Visibility, promotion

- Hosting of permanent showcases

- Connection to potential customers

- Acceleration of product development Application sponsors (business, cities, etc)

- Connect to innovators

- Put their data at work

- Costs saving

- Better service to customers

- Corporate Reputation FIWARE Instance Providers

- Providing added-value beyond cloud infrastructure

- Connecting to entrepreneurs

- Innovative Business Models



Figure 15: FIWARE Lab


supported with the promotion of FIWARE-Ops for managing and operating FI-Lab nodes and FIWARE

Instance deployments. The ambition of FIWARE is to extend FIWARE-Lab across entire Europe and to

promote this beyond by means of hackathons, interop-dev meetings, industry fairs, and similar events

targeting developer communities. This will be complemented by an extensive training and support offer

provided, by FIWARE, tailored to SMEs, Web-Entrepreneurs, and also industry players across the ICT and

Non-ICT sector.

Availability of the FIWARE Testbed per se does not guarantee innovation as such, therefore the FIWARE

Lab should comprise all what is needed to stimulate awareness among target application providers and

users so that they feel attracted to participate and build a community.



3.3. FIWARE OPS to expand geographically the FIWARE Lab


supported with the promotion of FIWARE-Ops for managing and operating FI-Lab nodes and FIWARE

Instance deployments. The ambition of FIWARE is to extend FIWARE-Lab across entire Europe and to

promote this beyond by means of hackathons, interop-dev meetings, industry fairs, and similar events

targeting developer communities. This will be complemented by an extensive training and support offer

provided, by FIWARE, tailored to SMEs, Web-Entrepreneurs, and also industry players across the ICT

and Non-ICT sector.

FIWARE Ops is a suite of tools that eases the deployment, setup and operation of FIWARE instances by

Platform Providers. It is designed to help expanding the infrastructure associated to a given FIWARE

instance by means of federating additional nodes (data centers) over time and allowing cooperation

among multiple Platform Providers. FIWARE Ops is the tool used to build, operate and expand the

FIWARE Lab

Some South American and Asian countries have been particularly interested in FIWARE. We are not just

limited to Europe and we are actively trying to reach agreement with other regions that may share a

similar view in regards to open source platforms and open data storage. International Cooperation

working on Mexico, Brazil and Chile. Opportunity to submit a proposal for a workshop in ICT Africa (May

2015)

- The FIWARE mundus programme, which aims at promoting FIWARE around the world, trying to

make the above pillars present in any region, enabling local FIWARE ecosystems to flourish. You

can learn more about the FIWARE mundus programme.

- Despite born in Europe, FIWARE is designed with a global ambition, aiming at expanding to

other regions. As a first step, partners in several countries of Latin America (Mexico, Brazil, Chile)

have decided to join the FIWARE programme, working on the setup of FIWARE Lab nodes in their

countries and promoting FIWARE locally.

3.4. FIWARE Tools

Purely technological continuity is paralleled by operational continuity. More precisely, this means that

FIWARE GEris are deployed and operated in FIWARE-Lab, via the FIWARE-Ops approach, and are

published in the FIWARE Catalogue. The same applies to tooling, such as the FIWARE Jira Instance which

is dedicated to support and interaction with Use Case projects and Use Case Expansion projects, SMEs

and Web-Entrepreneurs, the FIWARE Wiki, FIWARE distributed software development tools, and FIWARE

eLearning tools.

The Developer Community and Tools chapter aims at offering a comprehensive environment that enable

Future Internet Application Developers to use the FIWARE outcomes (i.e. GE Implementations and

FIWARE Instances) in a more efficient, easy and effective way. This includes, for instance, tools that

support 3rd party Application Developers to manage the development lifecycle for their applications.

Additional and detailed information on architecture choices and features of the tools are available from

the Developer Community and Tools section from the public wiki of FIWARE

The main focus of the tools provided by this chapter is the developers of Future Internet applications and

services. One service that goes beyond this focus is the FIWARE Catalogue.

- It does not only provide information about available GEs implementations to

Application/Enabler Developers but also to interested parties in other roles.



- In addition to this, and independently from the role of the stakeholder, the FIWARE eLearning

platform, (FIWARE Academy - http://edu.fi-ware.org/), provides training material in order to

support and simplify the access to, and adoption of, the FIWARE technology. The training offering

is organized reflecting the FIWARE chapters in order to ease the navigation of the contents that

also reflects the FIWARE Catalogue structure

New http://www.fiware.org/developers/guide web page served from fiware.org (WordPress) which will

work as table of contents with icons-titles corresponding to each of the subsections of the "Quick FIWARE

Tour Guide for developers. It will be basically structured in the following sections:

- "What's FIWARE?

- "Want to start quickly using FIWARE?

- Section which provides a link to the Quick FIWARE Tour Guide for developers page

- "FIWARE on the road" section which helps to discover next events linked to boot camps,

workshops, hackathons, challenges, etc and info from previous events.

- FIWARE Live Demos, examples and use cases on how to use FIWARE.

Finally, the exploitation of FIWARE will include relevant tools to ensure users' trust in the

interoperability and re-usability of the results (e.g., clear licensing models to encourage early adoption of

technologies and their rapid integration into commercial products). FIWARE will put a strong focus on

establishing these tools, which are crucial for reinforcing confidence in the overall FIWARE results, and

specifically in the quality and sustainability of each GEris and the business opportunities they provide.

3.5. FIWARE Business Ecosystem Modelling

Going forward, the biggest challenge FIWARE faces will be the uptake of its platform. For the FIWARE to

achieve its goals, it is necessary to bring together:

- Applications, e.g. service providers, consumers, sponsors and developers of the software they

use;

- Infrastructure capacity, e.g. networks, data centers, sensors and devices, connected to relevant

locations and/or communities, and their operators and investors;

- A platform, enabling the applications to access the infrastructure via commodity services in a

consistent, portable and easily programmed fashion.

Any successful Future Internet application will therefore exist within an ecosystem of interconnected

actors. Each actor may be a provider and/or a consumer of services, and many actors will be

intermediaries who provide some services by composing other services provided to them. To avoid

confusion, and better denote the relationships involved, we will introduce two terms:

- A resource is a service seen from the perspective of its consumer, i.e. something that can be

composed and used;

- A supplier is the provider of a service as seen from the perspective of the service consumer, i.e. a

provider of a resource.

Thus the most general type of actor therefore acts as an intermediary, providing services to its

consumers by composing resources from its suppliers. There are two aspects that must therefore be

considered when analysing Future Internet business models:



- Individual actor perspectives, reflecting their engagement as intermediaries with suppliers and

consumers;

- The value network, reflecting actors and roles (and their interactions) in a FI ecosystem.

Therefore, an ecosystem-oriented approach is key. However, ecosystems won’t emerge and sustain out

of the blue. They actually require mixing the right ingredients. The following table summarizes what are

the ingredients needed to build a sustainable FIWARE ecosystem for Smart Cities:

Ingredient What is needed to build the ecosystem?

Platform

technologies

Open specs of APIs, driven by implementation (open source reference

implementation).

Non-intrusive, support of different business models

Sustainable investment over time.

Experimental

environment

Ability to experiment with real data coming from cities (not just open historic

datasets but real-time data).

Free Cloud capacity enabling entrepreneurs to test and host a permanent

showcase of their applications.

Incentives to join

the ecosystem

Value proposition for all involved stakeholders: technology providers,

entrepreneurs, data providers, customers.

Funding for entrepreneurs joining the ecosystem.

Relevant investments in marketing (promotion and dissemination) activities.

Global footprint Helping entrepreneurs and technology providers to create opportunities in

multiple regions (Europe, Latam, Asia and, why not, USA).

Table 1 Ingredients needed to build a sustainable ecosystem for Smart Cities

The initiative is intended to help build healthy ecosystems and ensure that the Internet of Things is not

controlled by a small number of large companies. For example:

- Cities will be able to publish their open data on the online FIWARE sandbox, FIWARE-Lab, so

developers can create smart applications using this data and standard FIWARE APIs.

- Smart city applications developed and tested in one city can be replicated and amended in

other cities, creating scale opportunities for developers. In fact, there are several cities already

working to deliver their Open Data (both historic and real-time) on FIWARE-Lab. This includes

Lisbon (Portugal), Trento and Torino (Italy), Espoo (Finland), Santander, Sevilla, Malaga, Valencia,

Las Palmas de Gran Canaria, and Sabadell (Spain).

In this context, the majority of Smart City applications were developed using a mix of the following

three types of approaches: deploying datasets through the open data platform, based on CKAN [CKAN];

integrating city sensors with the FIWARE IoT platform and their consumption through the NGSI context

API (Next Generation Service Interfaces - FIWARE Open RESTFul API Specification); and finally, integrating

dynamic and/or structured information through the context API. The current status of this work is

summarized in the table below.



City Country IoT Open

Data

Context Prototype

Amsterdam Netherlands

✔ ✔

Barcelona Spain

✔

Espoo Finland

✔ Energy consumption dashboard

Helsinki Finland

✔ Participation dashboard (CitySDK-

Open311)

Las Palmas Spain

✔ ✔ Port management dashboard

Lisbon Portugal

✔

Mobility and social networks

Lleida Spain

✔ ✔ Public transport and accessibility

Logroño Spain

✔ ✔ Smart watering, City App

Malaga Spain ✔ ✔ ✔ Citizen as a sensor

Rotterdam Netherlands

✔

Santander Spain ✔

✔ Big Data / Open Data publication of IoT

Sevilla Spain ✔ ✔ ✔ Fountain water management, Crowd

detection

Torino Italy

✔

Security & participation

Trento Italy

✔

TBC

Valencia Spain

✔ ✔ Smart Taxi

Vigo Spain

✔ ✔ City App

Porto Portugal ✔ ✔

Environment, Open Data on Tourism

and Smart Metering Water

Table 2 Smart City Applications on FIWARE

FIWARE as an open platform, developed with the contribution of hundreds of developers across Europe

and supported by reference industrial players, universities and research institutions the FIWARE platform

may play a key role in the cities of the future. Its massive adoption may help to speed up the replication

of key components for setting up and consolidating the smart city ecosystem. However, for succeeding in

such an endeavor it is of utmost relevance to be aware of the potential limitations of the present

platform with the aim of identifying a set of actions for overcoming them. For this purpose we will define

the following action plan:

- Identify the needs, which are or not yet fulfilled by the platform, in terms of the ecosystem

requirements. This study will rely on the feedback provided directly by some of the cities through

a questionnaire circulated by the European Commission as well as any other valid source.



- In the case of cities already using FIWARE, to identify the key features which need to be

improved from a technical and commercial perspective to ease their adoption.

- To identify the reference use cases highlighting the positive impact achieved by using the

FIWARE platform in the city context.

Plans for standardisation activities based on the assumption that most EU cities will manage their

Smart Cities by means of a shared platform (be it FIWARE or another platform) would benefit from being

supplemented by a market analysis of who the main global suppliers in the Smart Cities sector are, what

financial investment they have in the field and whether the existence of standards is consistent with their

commercial interests and ability to deliver and sustain proprietary applications.

City Platforms will require to build the relevant Generic Enablers for Internet of Things Service

Enablement, in order for things to become citizens of the Internet – available, searchable, accessible, and

usable – and for the City Platforms services to create value from real-world interaction enabled by the

ubiquity of heterogeneous and resource-constrained devices.

- The Internet-of-Things (IoT) will be an integral component of the Future Internet (FI) and

therefore should be smoothly integrated within FI service delivery models and the emerging

utility based cloud computing paradigms. To-date several researchers have described the benefits

of a pervasive (sensor-based) distributed computing infrastructure without however providing a

systematic and structured solution to the formulation and management of utility based IoT

environments.

- IoT is a major component of smart city infrastructures. It is subject of the development of

architectural models (e.g. ITU), several are competing at this stage. Europe has moved forward

with FI-PPP and open IoT, and smart city is a good umbrella to further secure European

developments in this field.

- The standardisation of IoT is still a subject of studies, and of choice. The recently launched

exercise with ETSI will provide outputs not only related to implementation, of vertical siloes, but

also making possible cross use case capabilities. TC M2M is the forum of choice to progress the

issue in Europe.



Figure 16: FIWARE Smart City Standardization Essentials

One essential factor that can determine the successful adoption of FIWARE by customers and the

creation of a market-pull, and ultimately the proliferation of ecosystems is the establishment of FIWARE

as a standard in any given sector of application.

- Public policies may have a big impact on the establishment of a standard. If well it’s true that

publicly endorsed initiatives get wider attention by the community, there are potential issues that

need to be taken into consideration.

- Lack of coordination within policy makers could result in several incompatible approaches. In

the case of Smart Cities, for example, each municipality could endorse FIWARE as a standard for

its current, concrete needs, but other applications and systems would then have to be reviewed

afterwards to leverage and profit from the FIWARE ecosystem.

- Lacking a holistic view of the FIWARE initiative in all of its extension, could eventually lead to

barriers. Dissemination of FIWARE and its adoption is essential to unleash its full pot

3.6. FIWARE TARGET

The FIWARE programme is not only about providing open technology alternatives but also creating an

ecosystem that brings better opportunities to all the stakeholders:

- Application Providers, with special emphasis on SMEs and start-ups

- Application Customers, some of which also play the role of Data Providers

- Technology Providers





there should be a clear benefit for them to become part of the ecosystem.

FIWARE in general make significant efforts to address the needs of SMEs (Small and Medium

Enterprises). In particular, we follow a more vendor-independent approach where FIWARE partners

design or adapt GEis to be compatible with GEis from other partners, especially when required by SMEs

in specific FIWARE use cases.

- Fostering the joint creation of value by involving start-ups, IT SMEs, individual developers,

startup communities (i.e. Wayra), etc through dissemination initiatives, in parallel with

established sales processes at local Business Units or Digital

- Configuring the negotiated revenue share values at different variables: application type, target

customer, used APIs, workload, stakeholder (cities, industries, etc)



Figure 17: FIWARE Open APIS for OPEN MINDS

Regarding Smart Cities, It depends very much on the city, but what we typically face when we start a

conversation with a city that wants to connect with FIWARE AND FIWARE-Lab is:

- First, we find out (and encourage) that they publish a large number of open data.

- The second scenario is when a city is already managing a sensor-based system, for example,

public transport buses may be collecting data that is valuable that we would like to make

available in real-time. So what we are doing with them is creating adaptors for the data sources

and sensor technologies that the city already has in place. Then they can inject that data into a

context broker, and that context broker component will offer standard APIs to allow anyone to

consume real-time data. Previously, there was no standard API to manage real-time data for

cities.

- Third, we look to cities who have some sensor networks and we help them make those available

on the FIWARE platform

3.7. FIWARE Community

It is a challenge to establish a project community. All communities start with users, attracted by the

software’s packaging and branding, or word–of–mouth recommendations. A real community building can

happen and take place from the moment the platform/system is ready, presentable, and usable

The first step must be the identification of target groups. At this stage, two possible communities are

foreseen:

- A community interested in using the platform. A concrete example here is an institution

interested in open source software development by reuse of existing components and therefor to

solve the compatibility problem of different license usage.

- A community interested in providing a platform service to the public and further developing the

operating system or building some added value services on top of it. This category includes

consulting and support enterprises, software forge providers, as well as Research and

Development institutions willing to use the platform for their own business, research, and

development activities. Examples of these institutions and enterprises are:

o Consulting & Support: Black Duck Software, Bull, O’Reilly, OpenLogic, etc.

o Open Source Distributors: Red Hat, SUSE, Ubuntu, Debian, etc.



o Software Forges: Sourceforge, GitHub, Google Code, CodePlex, LaunchPad, OW2, etc.

o Research & Development: Atos, Engineering.

Open Source Community will take steps to build a sustainable community. There are many models for

building and sustaining online communities, and there may not be a fit for all solution. Different models

and community orientations that are particularly relevant to FIWARE will be taken in consideration

The task is tightly related to other activities including dissemination, exploitation and validation

workshops. Depending on which of those communities come into closer consideration for the final

community building, or in which direction the project wants to go, the strategies of community building

will differ, as is shown in the following chapters.

By using software forge coordinated designing, programming, testing, documenting, commenting and

reviewing of platform open source software is supported on different platform communities. Typically,

software forges provide the following features which foster the building of platform communities:

- Issue tracker support the reporting of bugs and the tracking of following error correction process-

JIRA

- Software repositories with version control capabilities. Furthermore, SCM tools allow to get the

current state of platform development, as well as to restore older software versions which are

needed to reproduce and understand reported bugs.

o A document management system for collaborative, distributed creation of documents

o Provision of screenshots and demonstration material

o Management and deployment of software releases

o Mailing lists to support asynchronous communication

o Forums to support and structure themed discussions within the developer community

o Task management allows the planning and arranging of development tasks

For foster Community Building it is Key to use of Social Networking. An essential part of fostering a

community building process is to generate attention for the new platform/ system with its main

functions. The channels to attract users for platform/ system and services are social networks, such as

Facebook, Google+, Twitter, LinkedIn, etc. Therefore appropriate sites and groups for the platform/

system and services in the relevant social networks should be established.

An important step would be identifying the FIWARE success stories, by defining a process to identify the

best apps and a kind of template to facilitate gathering information, i.e benefits in terms of cost

reduction, from the different sources:

- Apps from Campus Party and FIWARE challenges

- Apps resulting from Accelerators

- Apps from complementary contests and activities (ex. ICT-Labs)

Regarding FIWARE, by delivering Campuse.ro, we expect our users to be able to get in touch with other

individuals and organizations with technological interests alike while at the same time promoting

contents, activities and talent-search for future tasks and developments on top of the FIWARE

architecture. When all functionalities are in place, a great experimental environment for promotion,

cooperation and business development will be ready, gathering thousands of strategic players

(developers, creative minds, internet leaders, opinion leaders, bloggers, social media influencers,

entrepreneurs, start-ups, big companies, public institutions, media, universities etc) that will contribute

to create and support dynamic ecosystems around the FIWARE results.



4. FIWARE LAB: IPR Management

Since the partners of the consortium will develop software jointly, it’s important to select the most

suitable licensing model in advance to avoid misunderstandings and to clarify the exploitation chances of

the produced results.

- The exploitation of FIWARE will include relevant tools to ensure users' trust in the

interoperability and re-usability of the results (e.g., clear licensing models to encourage early

adoption of technologies and their rapid integration into commercial products).

- FIWARE will put a strong focus on establishing these tools, which are crucial for reinforcing

confidence in the overall FI-PPP results, and specifically in the quality and sustainability of each

GEris and the business opportunities they provide.

4.1. FIWARE Licensing Strategy

The FIWARE system itself will be Open Source Software, which, thanks to the offered features, is

expected to facilitate software development based on the Open Source paradigm in a global context. The

FIWARE project is expected to give a considerable contribution in terms of:

- Enabling software developers to use an intuitive and advanced searching platform with an

advanced service frontend allowing the easy identification of the more suitable Open Source

solutions needed;

- Providing the analysis of code dependencies, software structures, and potential license

infringements at a global level instead of within single projects;

- Facilitating the publication of the description of Open Source Software as Linked Data and the

production of new tools for software analysis and development that leverage this semantic data;

- Allowing a faster adoption and integration of Open Source components and libraries, mitigating

issues related to licensing incompatibility;

- Strengthening the European community of Open Source developers as it will increase quality of

Open Source Software, reducing time to market/use and establishing a validated path to integrate

Open Source components among them and without the risks linked to the complexity and liability

hidden in incompatible licensing.

The decision of which open source license to use on new software project should not be taken lightly, in

many ways it expresses and shapes the development goals of the project and its possible sustainability in

the long run. It is interesting to refer to the work of Rosen “Open Source Licensing” (2004) where he

refers on how license are chosen within Floss communities and which are the main questions that need

an answer:

- How can we make money from distributing this software under an open source license? In

essence, can our license help us sell free software?

- How can we prevent others from making money unfairly from our open source software? This is

the so-called free-rider issue, where licensees reap all the benefits of others’ work with no return

obligations?



4.2. Multi licensing

Common understanding defines dual licensing as the simultaneous licensing of software under both

open-source and proprietary licenses. A more accurate definition is that dual licensing is simply the

licensing of one software product fewer than two different licenses, where one license allows for free

distribution and the other allows for license revenue.

- The biggest motivation for using the dual licensing model is to make money through price

discrimination by monetizing intellectual property.

- Another important reason to use dual licensing is to ensure compatibility with other licenses.

- The first prerequisite of dual licensing is that the licensor needs to have control over all the

copyrights or at least enough control to be able to pick the license terms.

Choosing the license is not easy because if the licensing model includes the GPL we might get in a

situation where the copy left version is better than the proprietary version. It may be that the software

released under the GPL version has a superior modification, developed by the community, that is not

found in the proprietary version, finally, dual licensing may lead to other companies starting a competing

project (forking) using the GPL'ed or other open-source software. At the end dual licensing could be seen

as antithetical to open-source principles, which is why to some open source advocates, the dual licensing

model is just a way for commercial companies to reap the fruits of open sourcing without sharing the

benefits.

- In order to avoid any issue, regarding GPL (or AGPL), FIWARE GEri owners who have decided to

release their software using a GPL or AGPL license are required to make a public statement that

says: “Please note that software derived as a result of modifying the source code of this software

in order to fix a bug or incorporate enhancements is considered a derivative work of the product”.

Software that merely uses or aggregates (i.e. links to) an otherwise unmodified version of existing

software is not considered a derivative work.

For FIWARE the fundamental requirement of control over software and copyrights preludes to the

setting up of a managing organization for the control and commercial distribution of the FIWARE software

suite. The mix of private commercial organizations and research ones is an important hurdle to overcome

given the different strategies and long term objectives. Moreover a detailed business case would be

needed to justify the financial viability of this model which needs the setup of a proper business

structure.

FIWARE will exploit components relationships also for allowing a more efficient and accurate analysis of

licence compatibility and to provide well founded legal argumentation. FIWARE will integrate legal

analysis and compliance testing into its global view of available solutions and interdependencies, as well

as offer an interactive interface for development teams and their legal counterparts. The result can

strengthen an organization’s OSS governance & compliance policies, helping to alleviate potential

liability risks that can manifest with open source code adoption

4.3. License Status of FIWARE GEis on FIWARE LAB

There will be always an open source reference implementation (a FIWARE GEri) for all the FIWARE GEs

that are part of the FIWARE Reference Architecture.

Intellectual Property is different from Access Rights. The Intellectual Property of a given FIWARE GEri

belongs to the organizations that have contributed to its development. However, any FIWARE GEri is

released under a well-known open source license, enabling its usage, modification or distribution

without paying any license fee.



You can check the “Terms and Conditions” tab of the entry associated to a given FIWARE GEri in the

next licenses tables per domain, in order to learn what is the open source license under which the

FIWARE GEri have been released.

4.3.1. FIWARE Catalogue

Finally after the refinement of the licenses to provide all the Geri/GEis under open source, the FIWARE

Catalogue gathers information about:

- FIWARE GEris (already there), i.e., products offered as reference implementations of FIWARE GE

specifications. They are all open source and there is a commitment to support them by FIWARE

active contributors.

- FIWARE GEis, i.e., products that claim to be compliant with FIWARE GE specifications and look for

a place for raising awareness.

Chapter GE GEri / GEi name

(see note 1)

Owner Entry in Catalogue

/ comments

Open Source

License (see note

Catalogue Status

(see note 3)

Availability on

FIWARE LabIaaS Data Center

Resource

IBM http://catalogue.fi-

ware.org/enablers/iaa

Apache License

Version 2.0

Published Yes (as part of the

infrastructure of FI-Self-Service

Interfaces

Cloud Portal UPM http://catalogue.fi-

ware.org/enablers/sel

MIT License Published Yes (as part of the

infrastructure of FI-Object Storage Intel http://catalogue.fi-

ware.org/enablers/obj

Apache License

Version 2.0


infrastructure of FI-Software Deployment

And Configuration

Sagitta TID http://catalogue.fi-

ware.org/enablers/sof

Apache License

Version 2.0


infrastructure of FI-PaaS Management Pegasus TID http://catalogue.fi-

ware.org/enablers/pa

Apache License

Version 2.0


infrastructure of FI-Monitoring TID Not yet published GNU Affero General

Public License,

Draft Planned in 4Q14 (as

part of the Policy Manager Bosun TID http://catalogue.fi-

ware.org/enablers/pol

GNU Affero General

Public License,

Draft Planned in 4Q14 (as

part of the Identity Management KeyRock UPM http://catalogue.fi-

ware.org/enablers/ide

GNU Affero General

Public License,


infrastructure of FI-Access Control Access Control Thales http://catalogue.fi-

ware.org/enablers/ac

Only proprietary

license as temporary


infrastructure of FI-Security Monitoring MulVAL-Attack-

Paths-Engine

Thales http://catalogue.fi-

ware.org/enablers/se

Which concrete

Open Source

Published Planned in 4Q14 (as

part of the Security Monitoring Remediation App Thales http://catalogue.fi-


Which concrete

Open Source


part of the Security Monitoring ScoredAttackPaths Thales http://catalogue.fi-


Which concrete

Open Source


part of the Privacy Preserving

Authentication

IBM - Zurich It is provided as

basis of the Privacy

Apache License

Version 2.0

Archived

Publish/Subscribe

Broker

Orion Context Broker TID http://catalogue.fi-

ware.org/enablers/pu

GNU Affero General

Public License,

Published Yes (instantiable

GEri)Complex Event

Processing

IBM Proactive

Technology Online

IBM http://catalogue.fi-

ware.org/enablers/co

Apache License

Version 2.0


GEri)BigData Analysis Cosmos TID http://catalogue.fi-

ware.org/enablers/big

Apache License

Version 2.0

Published Yes (single global

GEri)Stream Oriented GE Kurento URJC/Naevatec http://catalogue.fi-

ware.org/enablers/str

GNU Library or

"Lesser" General


GEri)Short-term Historic

Open Data

CKAN OKFN OKFN is a partner in

FI-Core so CKAN will

GNU Affero General

Public License,

Planned in FI-Core Planned in 4Q14

(instantiable or single Backend Device

Manager

IDAS TID http://catalogue.fi-

ware.org/enablers/ba

GNU Affero General

Public License,


GEri)Backend IoT Broker IoT Broker NEC http://catalogue.fi-

ware.org/enablers/ne

4-clause BSD

Licence

Published Planned in 4Q14

(instantiable or single Backend

Configuration

Orion Context Broker TID http://catalogue.fi-


GNU Affero General

Public License,


GEri)Backend

Configuration

IoT Discovery UNIS http://catalogue.fi-


GNU Affero General

Public License,


(instantiable or single Gateway Data

Handling

EspR4FastData Orange http://catalogue.fi-

ware.org/enablers/gat

GPLv2 Published Planned in 4Q14

(instantiable or single Gateway Protocol

Adapter

MRCoap SAP http://catalogue.fi-

ware.org/enablers/pro

3-clause BSD

License

Published

Gateway Protocol

Adapter

EPCGE Orange Not yet published Which concrete

Open Source

Draft

Gateway Device

Manager

OPEN MTC fokus Negotiating - if not

open source, these

(see comments in

column F)

Archived

Gateway Protocol

Adapter

ZPA TI Negotiating - if not

open source, these

(see comments in

column F)

Archived

Template Handler Template Handler SAP Not enough tested,

may evolve to

3-clause BSD

License

Archived

Application Mashup Wirecloud UPM http://catalogue.fi-

ware.org/enablers/ap

GNU Affero General

Public License,


GEri)Repository Repository RI SAP http://catalogue.fi-

ware.org/enablers/rep

3-clause BSD

License


GEri)Marketplace Marketplace RI SAP http://catalogue.fi-

ware.org/enablers/ma

3-clause BSD

License


GEri)Revenue Settlement

and Sharing System

Revenue Settlement

and Sharing System

TID http://catalogue.fi-

ware.org/enablers/rev

GNU Affero General

Public License,


(instantiable or single Store WStore UPM http://catalogue.fi-

ware.org/enablers/sto

European Union

Public License


GEri)Data visualisation SpagoBI Engineering SpagoBI will become

an integral part of the

Mozilla Public

Licence v2.0 (MPL

Planned in FI-Core Planned in 4Q14

(instantiable or single 2D-UI Adminotech Not yet published Which concrete

Open Source

Draft Planned in 4Q14

(instantiable or single 3D-UI XML3D DFKI http://catalogue.fi-

ware.org/enablers/3d-

MIT License Published Planned in 4Q14

(instantiable or single 3D-UI Web Tundra Playsign http://catalogue.fi-

ware.org/enablers/3d

Apache License

Version 2.0


(instantiable or single Synchronization Ludocraft http://catalogue.fi-

ware.org/enablers/sy

Apache License

Version 2.0


(instantiable or single Cloud Rendering Adminotech Not yet published Which concrete

Open Source


(instantiable or single GIS Data provider Cyberlightning http://catalogue.fi-

ware.org/enablers/gis-

GPLv2 Published Planned in 4Q14

(instantiable or single POI Data provider UOULU/CIE http://catalogue.fi-

ware.org/enablers/poi-

Apache License

Version 2.0


(instantiable or single 2D-3D Capture Cyberlightning Not yet published Which concrete

Open Source


(instantiable or single Augmented Reality UOULU/CIE Not yet published Which concrete

Open Source


(instantiable or single Real/Virtual

Interaction

Cyberlightning http://catalogue.fi-

ware.org/enablers/rea

Apache License

Version 2.0


(instantiable or single Virtual Characters Ludocraft http://catalogue.fi-

ware.org/enablers/virt

Apache License

Version 2.0


(instantiable or single Interface Designer Adminotech http://catalogue.fi-

ware.org/enablers/int

Apache License

Version 2.0


(instantiable or single Network Information

and Control

OFNIC-Uniroma UniRoma http://catalogue.fi-

ware.org/enablers/net

GPL v3.0 Published TBD (Only

meaningful KIARA Advanced

Middleware

KIARA (KIARA

component)

DFKI Not yet published Which concrete

Open Source


(instantiable or single KIARA Advanced

Middleware

KIARA (RPC over

DDS component)

eProsima Not yet published Which concrete

Open Source



Middleware

KIARA (RPC

over REST


Open Source



Middleware

KIARA (Fast Buffers

component)


Open Source


(instantiable or single

Notes:

1 -

2 -

3 -

4 -

5 -

Some of the GEris will be available only as

single global instances in order to handle Robotics is a new area addressed within

FIWARE under execution of the FI-Core

Cloud

Security

Data/Media Context

Management

IoT Services

Enablement

Apps/Data Delivery

Advanced Web-

based UI

GEi = Generic Enabler implementation

productGPL or AGPL licenses are accompanied

with the following statement to secure there Descrition of the different values for this cell

follows:

Advanced

middleware, Interface

to Networks and

Robotics

(see note 4)

Table 3 FIWARE Catalogue Summary



4.3.2. FIWARE Tools

Tool License

FIA Project Management Plugin EPL v1.0 Open Source license

FusionForge Connector EPL v1.0 Open Source license

NGSI10 TestServer BSD Open Source license

PROSA EPL v1.0 Open Source license

PROSA-IDE EPL v1.0 Open Source license

REST Client Generator EPL v1.0 Open Source license

SoPeCo BSD Open Source license

SoPeCo-IDE BSD Open Source license

Trace Analyzer Plug-in binaries

Unit Functional Testing

Framework

EPL v1.0 Open Source license

FIWARE Catalogue Based on Drupal (GPLv2 or later)

Table 4 Tool Licenses



5. FIWARE Business Model

Open Source has expanded use of software and changed the landscape of software development and

distributions as it facilitated sharing, and in doing so, has undermined established ‘business models’. It’s

clear that Open Source by itself cannot be considered a business model and that there is the need to

exploit a range of different routes to market and sustainability. Common models are:

- The community model: the costs of sustaining the product or service are covered by building a

community of users and industry partners who agree to cooperate on development work and

maintenance because of their shared interest in an extended life for the product. Products

maintained in this way tend to have a wide applicability, such as Apache.

- The subscription model: users pay subscription costs to an external body in order to support

central maintenance and support. SAKAI and Linux Red Hat software are supported in this

fashion.

- The commercial model: users choose to adopt and pay for a 'commercialised' version of a piece of

software, normally to gain guaranteed support, maintenance and service models.

- The central support model: a central body provides robust releases and support for open source

products that are of strategic importance to its community. This is often an interim solution,

whilst other sustainability models are under development. The UK OMII and the Globus Alliance

are example of this model.

The different ways of generating revenue can be roughly split into the following areas:

- Offering an alternative paid license to FIWARE

- Providing services and support around FIWARE

In the sustainability and exploitation plan FIWARE can be provided as a service to developer teams but at

the same time it will improve the service provisions of forges and increase inter forge collaboration.

Nevertheless entrepreneurs come with their startups and they teach us: they come with a business

model already mapped out. For example [FIWARE Challenge winner] FoodLoop came to us with their

business model already mapped out. This is why we opened this platform

5.1. Service/Platform Provider

A more complex scenario for FIWARE is to provide directly the advanced search service developed in the

project. In this case FIWARE serves as a foundation for a SaaS offering. The general understanding is that

the Software as a Service (SaaS) is seen as an alternative model to Open Source Software (OSS), but in our

scenario they can be considered as independent and even complementary paradigms.

Open Source SaaS are seen as a new paradigm of Open Source software distribution and relevant market

case do exist like Zimbra or SugarCRM. It’s indeed becoming harder to discern between open-source and

SaaS companies. Their revenue looks increasingly similar, as their business models. In the domain of SaaS

and Open Source several service providers have moved to the freemium model according to this model,



a company releases software under an open source license and sells premium features on top, and the

owners of the code can just chose not to release certain features.

We have identified an initial suite of paid services that can be offered to paying customers:

- 1. Process certification

- 2. OS components' selection

- 3. Risk assessment

- 4. Improved performance and services (i.e. number of queries, analysis, license compliance)

- 5. Open Source Governance Services

- 6. Mobile support

5.2. Business Case

In FIWARE the business model simulation will focus on higher level modelling and cost estimations

based on those models for the different relevant costs and revenues for a new business proposition.

- In this context, an intuitive and reusable modelling language for network, equipment and

software will be constructed.

- Dedicated proof-of-concept editors for each of will help business architects to work with those

new languages.

Within FIWARE the business model editor will be based on Ballon’s business modelling ontology and

develop an intuitive business modelling language for editing and communication. The final step within the

FIWARE business model editor and simulation will be in the integration of both levels into one intuitive

platform for modelling and estimation of costs and revenues and for visualization of the outcome of the

business opportunity for the different actors and their responsible roles.

As such the FIWARE toolset will empower consortia to envisage, develop and check a novel business

opportunity before deployment. Even beyond this point, and out of the realm of the business modelling

and simulation, the FIWARE toolset also enables a more rapid deployment of this new product or service,

and clearly the technical details of this deployment can be fed again to the business modelling and

simulation allowing for fine-tuning and follow-up simulations.

5.3. Business model elements

To build-up a viable business model, key elements should be taken into account. These refer to different

domains: business, technical, financial and service. Applying a Strategic Fit CANVAS-like approach the

main elements of FIWARE´s business model would include:

- Business Architecture: Business architecture includes main FI-PPP stakeholders-partners, the roles

that they are going to take and the way they cooperate within the future FI-PPP value network. It

also includes the strategy to expand and exploit the FI-PPP ecosystem, attracting entrepreneurs

and innovators. Key elements thus are:

o Ecosystem management: building and expanding the FI-PPP ecosystem, exploiting the

opportunities of multi-sided markets shaped by the FI-PPP; partner management.

o Business Roles: Identification and assignment of roles to players within the business

architecture. Who does what?



o Customer relationship: Building, managing and maintaining customer relations. This

element will also be covered in the organisational architecture.

o Implementing the business architecture requires organisational, legal, managerial

arrangements.

- Technical architecture and activity structure: Refers to the technical structure of the service

operation and the way different partners provide and integrate different parts of the service. It

includes the FI-PPP activity structure in terms of infrastructures, resources and processes

generating the services offering.

o Ownership of components: Systems, platforms and artifacts that connect to each other

for service provision.

o Intra-operability (within the system): This refers to the particular distribution, control and

functionality of components across the system in order to deliver a specific application or

service.

o Inter-operability (outside the system): It refers to the ability of systems to directly

exchange information and services with other systems.

o Activity structure: the processes and activities of FI-PPP’s value chain as a service

business, including service offering, customer relations, logistics, management and other.

- Financial architecture: The financial architecture deals with the financial arrangements between

the partners in terms of cost structure of FIWARE’s activities and revenue generation based on

pricing and licensing strategies. It is essential that the financial architecture exploits the inherent

multi-sidedness.

o Cost structure: Relating to the activity structure, the provision of resources and the

business roles, costs need to be made in order to implement all the roles required for the

value network.

o Revenue sharing: The revenues come in at the customer side, but all partners need to be

compensated. The compensation does not need to be proportional to the costs made,

but it should at least cover them for each partner.

o Revenue model: There are many ways to create revenue: direct sales to customers, some

kind of two- or multi-sided market scheme, freemium, cross-selling, advertisements, etc.

Here, different pricing and licensing models should be considered as well.

- Service Architecture: This is about the offering of products and services by FIWARE and the value

offered to the customer. Underlying is the identification of customer groups and their needs to be

addressed by FIWARE’s services, including market analysis.

o Value proposition: The value proposition is about the FIWARE product and service offering

and their value added: the reasons why customers should acquire the service.

o Positioning: Often, there are many solutions to the same problem. FIWARE service needs

to differentiate itself from competitive offerings. I.e. Open-source

o Customers: Target customer segments and their needs. FIWARE as B2B service-platform.

o Engagement: End-customers can be offered varying degrees of involvement.



6. Action Plan for Platform Sustainability

The main objective of this chapter is to define the actions to ensure sustainability of the core platform

and of domain-specific platform developments in terms of usage and further evolution beyond the FI-

PPP lifetime, including exploitation planning, standardization, interoperability, IP arrangements and other

measures maintaining their availability in the longer-term.

It is necessary, but not sufficient, to define the FIWARE value proposition and business model. In order

to be viable, we need to ensure continuity through practical organisational, managerial and legal

arrangements ensuring FIWARE’s existence after 2016. Thus, we need to launch a “business creation”

activity. Future Sustainability of the FIWARE after its lifetime (2016) rests on two crucial elements:

- A viable business model around the FIWARE value proposition, allowing stakeholders in the FI-

PPP value network to realize gains via extended economies of scale and scope provided via GE

and SE and infrastructures.

- A set of organizational arrangements aimed at igniting a sustainable ecosystem for innovation

by stimulating, providing incentives and reducing barriers for development of innovative

applications and services.

The Action Plan will describe:

- Organisational architecture: how to implement the FIWARE business model in practical terms of

business creation, in terms of organisational, managerial, legal, contractual and administrative

arrangements as well as customer relations, business development and ecosystem management.

- The Action Plan also should lay out a roadmap for achieving sustainability: a pathway to

implement the various aspects of the business and organisational model.

For purpose of further discussions we may bring up some very first principles and ideas:

- FIWARE could transform into a light-weight organisational structure of a European-level

Association or Foundation.

- It could be built upon a consortium structure, with membership on different levels.

- It may need a Governing Board, staff, work groups …

- It would need a day-to-day operations office with functionalities such as marketing, PR, events,

training, knowledge network, business development, business relations, contracting,

administration and other.

- It may require provisions for management of the technical infrastructure

Ensuring the sustainability of the FIWARE results is a critical challenge for FIWARE – which requires

analysis of:

- Existing governance models,

- Communities involved in this Project (i.e. OpenStack), and

- The tools which could be used to support the attractiveness of these results and on-going

activities.

The sustainability challenge has led us to define a long-term industrial vision and strategy which

prescribe



- (1) how a larger community can learn from the technological improvement provided by the

FIWARE results,

- (2) how to improve them to increase business, and

- (3) How to spread the worldwide adoption of the innovative technologies.

As a starting point, we realized that we should account for sustainability across several classes of actors

which comprise the Future Internet PPP community: big and small ICT players, enterprises form several

vertical sectors such as Transport and Logistics, Manufacturing, Health, Content, Safety and many

Universities and Centre of Research.

Based on the initial objective of the PPP programme to involve all parties who could benefit from Future

Internet technologies for new businesses, governance bodies and rules were put in place to ensure a

strong coordination and to determine the appropriate technical choices.

FIWARE, going one step farther, will propose a new model to go beyond technical activities. This model

is based on two pillars:

- Governance rules and Exploitation, detailed below.

- FIWARE, FIWARE-Lab and FIWARE-Ops. FIWARE´s sustainability activities will also rely on the

involvement and feedback of many SME from across Europe.

6.1. Governance Rules

FIWARE aims first at defining a sound governance model that fits the ambitious industrial development

envisioned by the FI-PPP Community and to ensure the necessary sustainability when projects will end.

- A very successful and proven model is the concept of a Foundation, like for instance the Apache

Foundation, the Linux Foundation, or the OpenStack Foundation.

o A key principle of these foundations is to protect and foster the innovation potential of

Open Source Software communities while at the same time providing enterprise grade

structures and thus trust to industry and users.

o Typical elements covered in the Foundation governance model is the definition of clear

roles, responsibilities, and respective accountabilities. In particular, the latter is a very

important element when it comes to building trust with external parties that consider

investing in a piece of technology.

o Besides roles and accountabilities, technical governance and leadership has to be put in

place and is one primary concern of a Foundation. Only this will allow maintaining

direction and coherent evolution of a technology basis (e.g. the FIWARE Platform) along a

certain vision and roadmap.

o A third dimension to this is outreach, consisting of Marketing, Branding, and Training. The

multi-stakeholder background of the FI-PPP, FIWARE, and FI-Core renders this as

indispensable.

- FIWARE will create and put in place a governance model with clear rules for the various types of

community contributors, addressing management issues for technical roadmap, evolution of

existing specifications and API, IPR, Branding, Training, and eventually adoption of FIWARE,

FIWARE-Lab and FIWARE-Ops results. First and foremost, this governance structure will be

concerned with the direction and ownership of the FIWARE, FIWARE-Lab, and FIWARE-Ops

innovations and assets. It will maintain the product vision, including the technical scope and its



evolution, technical quality assurance, and timely advancement and delivery. It will define,

monitor, and enforce rules for technical contributions and quality.

o All this will be supported by respective processes and tools, in particular what concerns

contributions of new innovations and finally software.

o Along with this, it will define rules, conditions, and stakes associated with different types

of membership, and respectively influence.

o And the entire issue of IPR will be under the leadership of this FIWARE Foundation.

Governance of the community is obviously an important part of our sustainability strategy. Governance

needs to be aligned to software maturity and clear licensing and trademark management. At this stage is

too early to provide a clear strategy for community governance. The following picture highlights in one

single view the complex and articulated patterns that makes an open source project a success in

building communities of users, developers, and contributors, and eventually commercial contributors to

enable an project ecosystem.

Figure 18: Open Source Community Pattern, Walli S, the Outercurve Foundation, 2013

6.2. Philosophical Approach

The FIWARE Legal Entity (FLE) will provide a permanent legal home for the assets and governance of the

FIWARE community. The key objective is to preserve and to improve the FIWARE Culture

- Technical people making technical decisions

- Marketing the success and contributions of community members

- A strong ecosystem of companies and academia who can succeed and fund further progress

- Encouraging and rewarding contribution in all forms, such as testing, documenting, translating,

integrating, extending, educating, financing, training, supporting, facilitating, evangelizing,

designing, operating at scale or art making.



An important part of the "FIWARE Culture" is the proper balance between the individuals who invest

their time and effort, the companies who build businesses on FIWARE and the Future Internet Application

developers who build and deploy new applications based on FIWARE technologies.

- The structure of the FLE should encourage all forms of contributions and provides safeguards

against losing the balance between the various members of the community.

FIWARE is a very rapidly growing community which has added thousands of participants and produced

regular software releases in a relatively short start-up period. The open nature of the development

processes and inclusive policies around contributing help to spur this growth.

- Technical decision making has to be placed in the hands of technical leaders who strive to put the

interests of the projects and software ahead of corporate affiliation.

6.3. Mission

The FLE is an independent body providing shared resources to help achieve the FIWARE Mission by

Protecting, Empowering, and Promoting FIWARE technologies and the community around them,

including users, developers and the entire ecosystem. Community wide goals the FLE helps achieve are:

- Make FIWARE the ubiquitous platform to be used to build Future Internet Apps on top of it

- Deliver high quality software releases that companies can rely on to run their business

- Ensure interoperability among FIWARE Node instances

- Nurture a healthy community, with broad participation and a sharp focus on the FIWARE Mission

- Grow the ecosystem around FIWARE to strengthen the platform and provide opportunity

- Build and protect the FIWARE brands to the benefit of the community's participants

One of the FLE's main purposes is to empower and coordinate the resources of the community

effectively, providing leadership in key areas that are required to fulfil FIWARE's mission:

- Development process and release management

- Developer, user and ecosystem community management

- Meet the needs of real world users by producing great software, and fostering their involvement

in the community to provide feedback and direction

- Brand management (PR & marketing, trademark policy)

- Event management (Twice-annual Summit & Conference, meet ups etc)

- Legal affairs (CLA process and docs, trademark defense)



7. Conclusions

The European Commission and the major ICT companies share the diagnosis of a digital revolution now

looming, based incorporate technologies that have been developed in internet as cloud, big data, the

internet of things and make applications that transform both do business as the daily lives of people.

We have created FIWARE so that European companies are able to capture the opportunities that will

arise in this environment.

- FIWARE want to create an open alternative that allows multiple suppliers for SMEs arise, the

application developer can choose where to deploy the application or environment in which your data

is also staying. And you can switch from one provider to another if the service offered is not

satisfactory, without having to change large parts of the application because it is based on common

standards

- At first it sound good, Generic and modular libraries to become standards, so you can switch between

providers without problems. For example, you could switch between the cloud platform of Amazon

and Microsoft without having to change any of the code of my application

- FIWARE will be able to offer this platform as cloud environment technologies, using a pay per use.

Entrepreneurs who have developed these applications in the test environment FIWARE and want to

make money, you have warranty seek appropriate support, with 24 hour service, seven days a week.

The platform is generic and therefore can be applied to different sectors, which makes sense to offer

solutions to connect things to the network, sensors, handle large volumes of data, where real time is

important and which has to do an analysis of big data. For example, the activity of smart cities, which are

beginning to pull the platform.

The unique feature of FIWARE is its holistic approach and enables FIWARE to become the Operating

System of the Internet-Computer.

- It provides advanced Cloud capabilities and a library of Generic Enablers providing Open APIs that

enable innovative applications in multiple sectors.

- It provides connection to the Internet of Things, gathering, publishing and processing of Data and

Content at large scale in real time, performing Big Data analysis, application cross-selling and creation

all of these ICT-enabled innovations have never been easier to tap into.

The goal of the Future Internet Public-Private Partnership is helping ICT companies and

businesses/organizations in Europe and in other regions who wish to join Europe in this endeavour, to

capture the opportunities that will emerge in multiple sectors due to the new digital revolution that is

coming.





there should be a clear benefit for them to become part of the ecosystem.

FIWARE is the Core Platform of the Future Internet that eases the creation of innovative applications,

lowering the costs and complexity of serving large numbers of users globally and handling data at a large

scale.



- FIWARE seeks to provide a truly open, public and royalty-free set of open specifications that will

allow developers, service providers, enterprises and other organizations to develop products that

satisfy their needs while still being open and innovative.

- FIWARE will dramatically increase Europe’s Information and Communications Technology

competitiveness by introducing an innovative infrastructure that enables cost-effective creation

and delivery of versatile digital services, high quality of service and security guarantees.

- FIWARE will be open, based upon a series of elements (called Generic Enablers) which offer

reusable and commonly shared functions serving multiple areas of use across various sectors

The next battle will be to dominate the Operating System of the computer in which the Internet will

transform. Unless a collaborative effort is made, this battle will be dominated by the existing incumbent

players (e.g., Google or Amazon) with their own proprietary platforms. The FIWARE goal is to make sure

that an open platform alternative will exist around which a sustainable open innovation-driven

ecosystem can be created. The same way, existence of technologies such a Linux or Apache has been

crucial in how the Internet and the Web looks today, existence of an platform alternative like FIWARE can

be crucial in how the Internet and the Web may look like in the Future.

The existence of an open platform alternative will ensure that application providers will be able to

choose who will provide and operate the environment where their applications will be hosted. Data

providers, including Open Data providers, will also be able to choose who will provide and operate the

environment where their data will be hosted and exploited. Their decisions can be driven not just based

in economic savings but the trustworthiness of the platform provider. Applications and Data providers

can also better protect their investment because of the ability to port applications and data to an

alternative platform provider if a given platform provider stops meeting their requirements, thus avoiding

getting locked in a given platform provider.

One essential factor that can determine the successful adoption of FIWARE by customers and the

creation of a market-pull, and ultimately the proliferation of ecosystems is the establishment of FIWARE

as a standard in any given sector of application.

Finally FIWARE aims first at defining a sound governance model that fits the ambitious industrial

development envisioned by the FI-PPP Community and to ensure sustainability of the core platform and

of domain-specific platform developments in terms of usage and further evolution beyond FIWARE

lifetime, including exploitation planning, standardization, interoperability, IP arrangements and other

measures maintaining their availability in the longer-term. A very successful and proven model is the

concept of a Foundation.



Annex 1 Individual Exploitation Plans

Annex I has been updated to reflect the more tangible business view of the industrial partner and a lot

more substantive in describing the planned integration of the FIWARE outcomes into the mainstream

business of the industrial partners.

- Engagement FIWARE outcomes with their corporate strategy. Regarding your own GEs or in

combination with other GEs (Instances).

- In which ecosystems/sectors are the industrial partners going to focus or prioritize?

- Especially at the industrial partner level, leading to concrete plans for fit-for-deployment FIWARE

instances and other productization opportunities

- FIWARE LAB exploitation or utilization within your company.

- Describe a control mechanism for verifying FIWARE adoption

- Identify a responsible for the adoption and dissemination of FIWARE, within the organization and

with sufficient seniority.

- Identify the potential policy issues and impact on the specific exploitation activities of FIWARE

partners

1. Telefonica I+D

Organization Profile

Telefonica is one of the world leading integrated operators in the telecommunication sector, providing

communication, information and entertainment solutions, with presence in Europe and Latin America. It

operates in 24 countries. As of December 2012, Telefonica’s total number of customers amounted to

315.7 million.

Telefonica has one of the most international profiles in the sector with more than 60% of its business

outside its home market and a reference point in the Spanish and Portuguese speaking market. In Spain,

the Group has over 80 years’ experience since its constitution in 1924, providing services to more than 41

million customers at December 2013. In Latin America, Telefonica gives service to more than 224 million

customers as of the end of December 2013 becoming the leader operator in Brazil, Argentina, Chile and

Peru and has substantial operations in Colombia, Ecuador, El Salvador, Guatemala, Mexico, Nicaragua,

Panama, Puerto Rico, Uruguay, Venezuela and Costa Rica. In Europe, on top of the Spanish operations,

the Company has operating companies in the United Kingdom, Germany, , providing services to more

than 50 million customers as of the end of December 2013.

Telefonica has a regional and integrated management model. The key to company's structure lies in

extending its client focus, its leveraging scales and its strategic and industrial alliances.

Telefonica I+D is the research and development company of the Telefonica Group. Telefonica I+D was

founded in 1988, its mission is to contribute to the Group ́s competitiveness and modernity through

technological innovation through applying new ideas, concepts and practices in new products and

advanced services. It is one of the first private R&D centres in Spain as regards activity and resources,

having been the first company on the continent by number of European research projects in which it

participates. It currently collaborates with technological leaders and many organizations from 40

countries. It also participates in the most important international forums on technological knowledge of



the ICT sector, creating one of the largest European innovation ecosystems. Over the last few years,

Telefonica I+D have grown to become a network of centres of technological excellence. At the same time,

it is working for the companies in the Telefonica Group in the rest of Europe and America. Telefonica I+D

activity materialises in a portfolio of patents that increases every year, but also in some of the most

innovative products that the Telefonica Group has launched in recent months.

Activities of Telefonica I+D are now included into a new transversal organization. This reorganization of

Telefonica, will assure a significant role for Telefonica I+D specialized offering and is a major movement to

increase the market connection to the products developed by Telefonica I+D.

Telefonica has a global business division whose mission is to seize the opportunities within the digital

world and deliver new growth for Telefonica through research & development, venture capital, global

partnerships and digital services such as cloud computing, mobile advertising, M2M and eHealth. A

number of existing, innovative digital businesses are also included in the Telefonica family, including

Jajah, Terra, Media Networks, TokBox and giffgaff

Telefonica’s vision is to make the possibilities offered by the new digital world real and to be one of the

leaders in this area. One of the steps the company has taken to get ahead of its competitors was the

creation of different global product and service development units, covering, among others, cloud

computing, eHealth, financial services, M2M (machine-to-machine connections), video and digital home,

applications and security. These units are the pillars of a globalized innovation model which is designed to

capture as much of this growth in the telecommunications sector as possible. Telefonica will deliver these

innovative products and services to 300 million customers as well as leveraging the power of the internet

to enter new markets.

Identification of main project outcomes

Telefonica has amongst its top priorities its reconversion into a “digital Telco” capable of getting value

downstream in the new digital economy value chain, which would ultimately position it as a relevant

player in the global Internet ecosystem.

The Future Internet technology related to FIWARE is one of the pillars for Telefonica’s transformation into

a key player in the digital world, as one of the first steps is the development of a set of essential enablers.

Non-surprisingly, these are closely related to Telefonica’s FIWARE GE’s:

• Cloud Hosting enabler:

o Telefonica has been strongly focused in Cloud Computing over the last few years, even

investing in related tech companies

o Telefonica I+D together with FIWARE partners are developing a suite of components

aimed at Cloud hosting

o The interest for Telefonica in FIWARE is using the developed components (IaaS, PaaS,

Resource Monitoring) both internally (for our own data centres to increase efficiency) and

externally (for our Cloud Computing service portfolio to be enriched)

• Internet of Things (IoT) enabler:

o IoT is about collecting large amounts of data on “things” as sources of information,

transforming data flows into sensible information through massive data processing and

analysis, and finally providing user applications with that information through APIs; also,

users can interact with this IoT environment by sending automated or manual commands

to the devices



o Telefonica is developing a comprehensive platform for handling IoT over M2M

communications: this open operational platform is particularly applicable for service

delivery in the Smart City context, as external developers and other collaborating

companies are enabled to build applications on top of this open platform

o A number of elements in that platform are also incorporated in the FIWARE architecture:

especial attention is paid to modules dealing with sensor abstraction

• Data Context management enabler:

o Telefonica is developing a Big Data Platform aimed at enabling massive data ingestion,

storage and analysis, allowing data analysis and dynamic decision making, to overcome

manual and offline suboptimal processes limitations

o This platform is an extension of Open Software solutions

o A significant number of FIWARE elements developed in the Data Context management

work package are already part (or will become part) of Telefonica Digital offering

• Applications and Services Ecosystem and Delivery Framework enabler:

o Telefonica has been building a business framework focusing in payment enablers and

revenue settlement and sharing systems over the last few years.

o Telefonica I+D together with FIWARE partners are developing a suite of components

aimed at solving the issues related to the business aspects and trading of applications

developed with FIWARE enablers.

o The interest for Telefonica in FIWARE is using the RSS developed component both

internally (for our own business processes) and externally (for our business services

portfolio to be enriched)

We are going to go deeper inside this topic, working around 3 axes: technical, commercial and strategic.

From a technical point of view, these are the keys for the exploitation of the project results:

• Building (and deploying and operating) a commercial instance under the formula of Public

Private Partnership together with local administrations in Spain, offering a unified horizontal

architecture instead of disparate physical infrastructures (see below):

Figure 19 TID´s unified horizontal architecture approach

• Adapting and then adding other assets out of the FIWARE scope, in order to be quicker and more

attractive to market, like:



o Assets from our platform portfolio, like BlueVia infrastructure (developer portal, business

framework), very much enriched with the APIs provided by this project

o Assets from our strategic program, like Open Web Device for easier cross-platform mobile

development

o Assets from our innovation program, like Thinking Things for seamless sensor connection

to the IoT

o Assets from external sources, like certain city Open Data made available to developers for

the applications of specific developers to be built on top of these elements (see below):

Figure 20 TID´s Open Data for Developers

From a commercial point of view, this is bringing about value to Telefonica:

• According to one of the different business models:

o Exploiting global digital results from a centralized unit at Telefonica Digital, directly

addressing end users (B2C), most probably under the global brand “Tu”

o Offering a platform to different customers (B2B) that serve final users (i.e. city councils,

car manufacturers, etc)

o Transferring the assets to any of our many local Business Units for their ultimate fine-

tuning to meet local expectations and local exploitation under different local brands and

strategies (B2B or B2C, etc)

• Either way, following a multi-sided approach where third party apps can be built on top:

o Fostering the joint creation of value by involving startups, IT SMEs, individual developers,

startup communities (i.e. Wayra), etc through dissemination initiatives, in parallel with

established sales processes at local Business Units or Digital



o Configuring the negotiated revenue share values at different variables: application type,

target customer, used APIs, workload, stakeholder (cities, industries, etc),…

And from a strategic point of view, this is bringing value to Telefonica due to:

• Permanent beta showcase to enable for strategic partnerships with Public Administrations to

position Telefonica towards the future

• Third parties applications to minimize our investment and risk, and at the same time maximize

our joint success chances

• Removing operational restrictions to move faster and gain a neutrality brand (helpful in some

vertical app domains such as eHealth or smart cities) at the same time.

Implementation of the project results

There is a huge opportunity in the conversion of different sectors into connected, smart & open. The

buzzwords “Smart Cities” have become a staple in the current plans of many companies, as a cornerstone

of a sector where many technologies, interests and use cases converge, but it is not the only focus of

Telefonica in relation with FIWARE technologies:

• Smart Cities / Regions:

o Currently, at Telefonica there is a number of ongoing Smart City experiences in Europe

and Latin America

o Telefonica won the public contest for Valencia Smart City, which will be FIWARE

compliant, and leverage on FIWARE programme ecosystem to provide greater value to

citizens and authorities.

o In Seville, Telefonica will participate in the FIWARE-based Smart Port initiative, in the

logistics of cargo, ships and trains

o In Brazil, Telefonica had announced the first Brazilian Smart City at Aguas de Sam Pedro,

and it will take it one step further making it the first Brazilian FIWARE city

o In Las Palmas de Gran Canaria, in the Canary Islands, in cooperation with the University of

Las Palmas de Gran Canaria, Telefonica is working on a Smart Campus project and the

Smart Port which accounts for 70% of the economy of the island

o Transversal to Smart Cities and Regions, are different applications such as tourism, e-

administration, learning, etc.

• Smart Agro, Industry:

o The next big step in the Telco business will be the conversion in “Smart” of the different

industrial sectors.

o There is a big gap in businesses and geographies where ICT has not permeated to the

level that is now possible with current technologies. As an example the mining industry

now combines standards in sensors, actuators, communication and systems from dozens

of providers, and most of the times, integration has to be done specifically on a per-

project basis.

In Chile, Telefonica launched a new R&D centre with market focus on Chile and expansion plans to other

Latin America countries. The technical activities of this new unit will have a twofold approach:

• Smart Cities, starting with Santiago area and/or neighbouring regions, and moving on to other

cities with support from the Chilean Municipalities Association



• Smart Industry, with initial focus on the mining industry in Chile, probably in partnership with

relevant mining companies, which are leaders player in mining industry worldwide

The new centre is already hiring employees, and is expected in 2014 to reach 16 full-time researchers,

mainly recruited locally, and two technical managers who will be current managers at TID participating in

FIWARE, in order to ensure the alignment of the solutions deployed in Chile with our development

strategy. Ambition is for TID Chile to organically grow to 45 FTEs by the end of 2015

The person in charge of the design of the new R&D centre is D. Luis Ignacio Vicente del Olmo, senior

manager at Telefonica I+D, who has been involved in FIWARE programme since its inception, is

responsible in TID for the participation in public programmes. He is also promotes the Latin American

operations involving FIWARE.

Potential Policy Issues and Barriers

One essential factor that can determine the successful adoption of FIWARE by customers and the creation

of a market-pull, and ultimately the proliferation of ecosystems is the establishment of FIWARE as a

standard in any given sector of application.

Public policies may have a big impact on the establishment of a standard. If well it’s true that publicly

endorsed initiatives get wider attention by the community, there are potential issues that need to be

taken into consideration.

Lack of coordination within policy makers could result in several incompatible approaches. In the case of

Smart Cities, for example, each municipality could endorse FIWARE as a standard for its current, concrete

needs, but other applications and systems would then have to be reviewed afterwards to leverage and

profit from the FIWARE ecosystem.

Lacking a holistic view of the FIWARE initiative in all of its extension, could eventually lead to barriers.

Dissemination of FIWARE and its adoption is essential to unleash its full pot

2. SAP AG

In this section the Individual Exploitation Plan for FIWARE of SAP AG is described.

After an executive summary, the business strategy of SAP is described and FIWARE is put into this context.

The main part is comprised of the description of the main outcomes and the description of the Generic

Enabler and tool contribution results from SAP and their exploitation results. Finally, the background of

the contributions in the overarching exploitation process is given.

Executive Summary

For SAP, the aim of building a next generation business platform and a services ecosystem is a pillar in

SAP’s overall strategy and SAP’s corporate investments in this area clearly exceed a billion euros.

Within this strategy, the participation in the FIWARE project plays an important role for SAP as part of its

activities to identify and codify best practices for enabling secure, dependable and trusted business

ecosystem around services.

The methodology behind FIWARE is well aligned with SAP’s proven methodology of developing products

and functionality as well as services by co-innovation together with partner and customers in a

cooperative way which allows SAP to expose concepts and technical artefacts to the wider community in

order to drive their uptake. Gathering experience by evaluating the uptake by stakeholders, use cases etc.

is also beneficial for SAP to design future best practices into SAP offerings.

In order to realize this co-innovation approach in FIWARE, SAP drives a two-fold exploitation strategy for

the developed FIWARE results:



- Engage with communities and ecosystems to drive adoption of GE

- Exploit FIWARE concepts and results to foster SAP-internal innovation

Of course, the main focus in on the first topic of engaging with communities and ecosystems in order to

gather feedback on the usage of our software in order to be able to learn and develop improved future

business offerings for our customers. SAP provides enabling technology which can be used by 3rd parties

to adopt the offered concepts within customer and partner settings. SAP envisions high potential for

novel business ecosystems across company, cultural and domain boundaries coming out of and enabled

by the FIWARE results.

FIWARE provides an ideal framework for such an ecosystem because of its concept of Generic Enablers

and well-defined APIs and data formats for interaction in a Future Internet application. SAP provided the

Generic Enabler definition and interfaces for the main business framework enablers, which drive internal

innovations (see below). The used uniform service description language Linked USDL is already adopted

by a number of other projects (e.g. FINEST, Value4Cloud, Deutsche Digitale Bibliothek, MSEE, FIspace,

FITMAN, FI-CONTENT, ENVIROFI, OUTSMART, SMARTAGRIFOOD, IoT-A, Broker@Cloud, and GEYSERS) and

formed a community of users and contributors.

All of SAP’s contributed FIWARE Generic Enabler Open Specifications are released under the “FIWARE

Open Specification Legal Notice (essential patents license)”5. This essential patents license has been

defined in the FIWARE consortium by agreement among the partners and this license has been adopted

by other FIWARE partners also.

As a key to wide adoption by communities and ecosystems, the delivery of a reference implementation as

Open Source software free of charge to developers and key users has been instrumental for SAP.

Consequently we have released most of our GE implementations as open source software for developers

and 3rd parties who want to build competitive offerings under a permissive BSD-like Open Source license.

This license scheme allows them to use and easily onboard with the free-to-use and commercially-

exploitable enablement technology. We strongly believe that the Open Source approach is the best

solution to let our GEs being used and adopted by a wider community.

SAP has released 7 GEs (of 7 planned) and 2 tool contributions (of 2 planned) as Open Source software

with a very permissive BSD license to allow for commercial exploitation of our GEs by 3rd party

developers of any kind. Many research projects in the FI-PPP context and beyond have been involved in

their uptake and evaluation. In total, all 7 GEs and 2 tools are available in the FIWARE Catalogue and they

are installed in the FI-PPP-internal FIWARE Testbed as well as in the FIWARE-LAB infrastructure.

With respect to SAP-internal innovation, the concepts and technology coming out of FIWARE already

influenced and will further influence SAP’s own activities and offerings to support trusted business

ecosystem around services in many ways: Concepts and technologies derived from SAP’s FIWARE GEs and

other FIWARE contributions are to be evaluated by SAP departments and to be transferred within transfer

activities into SAP-internal products or SAP product offerings and business ecosystems. Application

domains have been significantly reshaped such as logistics and public services. Several product and

development groups have already adopted or are starting to adopt selected developed FIWARE concepts

and technologies for SAP-internal development processes and upcoming SAP offerings and platforms and

business ecosystems (e.g. SAP HANA Platform groups, an upcoming M2M/IoT platform, and others).

5http://forge.FIWARE.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Open_Specification_Legal_Notice_%28essential_patents_license%2

9



As a summary, for SAP the FIWARE project and the FIWARE results like GE blueprint specifications, GE

open specifications, GE reference implementations, and software tools provided by us are highly useful

for evaluating and evolving concepts in open, research-related contexts as well as in industrial settings in

co-innovation with third parties.

FIWARE Contribution to SAP Strategy


SAP has grown to become the world‘s leading provider of e-business software solutions. With 253,500

customers in 180 countries, an external software ecosystem of more than 3,000,000 developers, and

more than 11,500 partners, SAP is the world‘s largest inter-enterprise software company and the world‘s

third-largest independent software supplier, overall. SAP solutions help enterprises of all sizes around the

world to make them a best-run business, e.g., by improving customer relationships, enhancing partner

collaboration and creating efficiencies across their supply chains and business operations.

SAP Business Strategy

SAP’s co-innovation with customers and partners

SAP’s business goal is helping the world to run better and improve people’s lives through codifying best

practices around business processes. This is typically done in a joint co-innovation process of SAP with its

customers and partners. Analysis focuses on what the business actor at the customer needs in order to

solve a business problem. SAP provides standardized products derived out of these joint innovations and

maintains and evolves a stable platform successfully for 30+ traditional product and service industries.

SAP’s mission for a secure, dependable, and trusted future business ecosystem

As part of the company’s ambition to expand from its traditional enterprise base, it has launched efforts

to build a 3 Billion $/year Cloud business until 2017 (Source: Corporate Fact Sheet). SAP’s corporate

investments in this area clearly exceed a billion euros which exemplifies the importance of this topic for

SAP. In order to better understand the business challenges and opportunities for itself, its customer and

partner ecosystem in the “new world” of Internet of Services/Future Internet, SAP is taking a multi-

pronged approach. On one hand, SAP is systematically building and acquiring SaaS (Software as a service)

assets operated by SAP, while on the other hand SAP is enabling its vast customer base to offer services

by themselves - based on the capabilities of the SAP software running within the customer enterprises.

SAP’s mission in this context is to cultivate a secure, dependable and trusted business ecosystem

around services - with the vast existing SAP customer base as the starting point for this transformation.

Co-innovation for FIWARE

Given the nature of the particular market that SAP tries to address, the only approach that can get the

necessary widespread adoption is the already proven methodology of SAPs past: Co-innovation with

partners and customers.

SAP applies its co-innovation methodology also in the context of the FIWARE project in order to identify

common ground and collaboratively work on the needed transformation: Creating a network effect

around services in the internet which offers benefits for all involved parties. Taking technology aside,

ecosystem design and enablement of domain specific ecosystems are key aspects.

FIWARE contribution to SAP strategy

Through the means of the FIWARE project, SAP can enlarge the reach and range of types of partners,

customers and use cases the company can address. SAP can drive awareness and potentially enable the

network effect within the FI-PPP community by providing enabling technologies through multiple

channels.



SAP’s activities in FIWARE correspond to this strategy, for example, in terms of topics such as Applications

and Services Ecosystem, IoT, Security, Privacy, Trust, and Development Environments.

Beside this, the FI-PPP Program and especially the FIWARE project provide a great opportunity to design

and evaluate new business approaches for SAP itself.

As described below, SAP drives a two-fold exploitation strategy for SAP’s FIWARE results:

- (Main focus) Engage with communities and ecosystems to drive adoption of GEs


Of course, the main focus is on the first topic of engaging with communities and ecosystems in order to

gather feedback on the usage of our software in order to be able to learn and develop improved future

business offerings for our customers. Therefore, SAP provides enabling technology which can be used by

3rd parties to adopt the offered concepts within customer and partner settings. SAP envisions high

potential for novel business ecosystems across company, cultural and domain boundaries coming out of

and enabled by the FIWARE results. Figure 21 shows an overview timeline of SAP’s activities according to

this two-fold exploitation strategy in FIWARE as explained below.

At first, numerous exploitation activities are aiming at involving new communities and ecosystems to use

the developed SAP FIWARE contributions within a set of different use cases and application domains, e.g.

FI-PPP use case projects of phase 1 and phase 2 as well as other EU research projects or further initiatives

that are interested in using our FIWARE results. Examples are domain-specific communities, the USDL

community, the FIWARE Catalog, the FIWARE-LAB, and the FI-PPP internal test beds). An interesting

recent activity worth mentioning on top of the already described activities is to bring FIWARE results into

the Helix Nebula initiative which we pursue very actively.

For this engagement with communities and ecosystems, SAP selected the FIWARE project as one of our

flagship projects to provide most software results as Open-Source Software to be able to serve several

communities and target groups across different application domains as well as to the FI-PPP use case

projects and other projects.

All of SAP’s FIWARE Generic Enabler Open Specifications are released under the “FIWARE Open

Specification Legal Notice (essential patents license)”6. This essential patents license has been defined in

the FIWARE consortium by agreement among the partners and this license has been adopted by other

FIWARE partners also.

For the selected Open Source exploitation strategy, the enabling technology assets are free to use and

commercially exploitable as Open Source for all developers (even SAP competitors), this is fully supported

in an open community approach. It is worth to highlight, that SAP is one of the few FIWARE partners

having selected such a permissive (open) (BSD-like) software license scheme to make their results

available for broad uptake. Since SAP is mainly interested in broad uptake of the GE’s to leverage the

resulting network effects, the usage of the GE’s is free of charge.

At the final M36 milestone, SAP has delivered all of its planned results. SAP has released 7 GE reference

implementations and 2 tool contributions as Open Source software with a very permissive BSD-license

to allow for commercial exploitation by 3rd party developers of any kind. Many research projects in the FI-

PPP context and beyond have been involved in their uptake and evaluation.

6http://forge.FIWARE.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Open_Specification_Legal_Notice_%28essential_patents_license%2

9



With respect to FIWARE infrastructures, in total all 7 GEs and 2 tools are available in the FIWARE

Catalogue, the FI-PPP-internal FIWARE Testbed, and the FIWARE-LAB infrastructure.

Figure 21 Timeline of SAP's FIWARE exploitation activities

At second, with respect to exploiting FIWARE concepts and results to foster SAP-internal innovation, the

following results of the FIWARE project contribute to this SAP strategy and they form the main pillars for

our on-going exploitation in line with the overall SAP product and cloud strategy.

Several product and development groups have already adopted or are starting to adopt selected

developed FIWARE concepts and technologies for SAP-internal development processes and upcoming SAP

offerings and platforms (e.g. SAP HANA Cloud Platform groups, and others). A report on these SAP-

internal innovation activities is given in the following Sections 0, 0 and 0ff.

Application areas for results from FIWARE

As described below in Sections 0 until 0 in detail for all work packages and their results, the following

target business units in SAP have been addressed:

- Software/application platforms and related ecosystems results (WP3 & WP9) are already used

within SAP for service-related products and offerings and they have been contributed to the most

recent public offering of the SAP HANA Cloud Platform. The Service industry has become the

biggest employer in Europe and tends to be a critical force to ensure economic growth. Our work

within FIWARE contributes to the expansion of the service economy by creating an IT

infrastructure for Business Services where services become accessible, discoverable, easily

deployable, and ultimately tradable on the Internet. In doing so, our work helps the service sector

to generate new value added services, develop innovative business models, and establish new

business value chains. Furthermore, work results are currently in the process of being transferred

to the next generation of the SAP Ariba Business Network and other similar ecosystem activities,

as detailed below.

- IoT results (WP5) are currently targeted for being transferred in the area of M2M application

domains to an upcoming SAP IoT/M2M platform with some promising outcomes as described



below. One of the core components of SAP’s upcoming M2M platform, the middleware for device

integration, was developed in close cooperation with the FIWARE project with the WP5

architecture being closely aligned with the architecture of the middleware for device integration.

Members of the team working on FIWARE were also working on the middleware for device

integration. Due to several constraints within SAP’s architectural design, the Protocol Adapter GE

cannot be directly incorporated into the application; however, conceptually there is a strong

overlap.

- Security solutions (WP8) are adopted to be transferred to a new service offering within the SAP

HANA Cloud products with first results. Product security is one of the SAP core values. The

attention on security features of SAP products and on new trends and menaces requires constant

research and innovation activities. No security products are part of the SAP portfolio to be offered

to customers directly, therefore the visibility of these efforts can perhaps be observed only in an

indirect way. In the line traced by the product security research activities, the Security Data

Handling GE allowed SAP to develop and extend some innovative approaches and contributions of

interest for large industrial scenarios and in particular for the Cloud: notably, an optimized

declarative access (and usage) control for the cloud and the “sticky policy” concepts. Essentially,

they allow expressing access and usage control conditions on cloud resources and a number of

optimizations developed for its exploitation are being adopted by security departments

responsible for the SAP HANA product, to be transferred to a new service offering within the SAP

HANA Cloud products. For security reasons, not much detail on such activity can be disclosed,

essentially not to divulgate information that could be even indirectly exploited by attackers.

Clients and business partners for results from FIWARE

The results of FIWARE are adopted within SAP in several business units in SAP and are evaluated and

transferred to become a part of our efforts to serve customer’s needs with our products in different ways

– with different strategies available in our organization applied as supervised by the respective SAP

management:

- Software/application platforms and related ecosystems results (WP3 & WP9) target service-

related products and offerings for a wide range of clients. For example, the results in the FIWARE

EIT FI-PPP project have led to the follow-up internal plan to evaluate similar infrastructure cloud

service marketplaces. Besides the concepts and with the encouraging learnings derived from the

customer interviews in the Helix Nebula ecosystem network giving feedback to the service

marketplace prototype, SAP is now deciding if we want to produce an internal Proof-of-Concept

of a similar infrastructure service marketplace. For WP9, the results for SoPeCo are targeted for

transfer to the HANA platform by middle 2014 with adoption also in several SAP HANA units as

well as the SAP HANA platform units.

- For IoT (WP5), both of the generic enablers from the Internet of things domain are clearly aimed

at SAP’s M2M clients. As analysts expect that by 2020, 30 billion assets will be connected globally,

IoT / M2M is a strategic market for SAP. SAP is uniquely positioned in this space, as SAP can

provide end-to-end integration and process automation from the asset to the backend systems.

The Protocol Adapter GE fits into SAP’s future M2M offering from PI Mobile M2M Engineering

from the lower levels of the protocol stack, enabling CoAP and NGSI interfaces that are currently

not present in SAP’s technology stack (and that were a strong focus of the entire FIWARE PPP).

Likewise the BPMN extensions utilized in the Template Handler GE fits to the higher levels of the

stack, effectively linking enterprise systems such as SAP’s R3 to the Internet of things. This is

relevant for practically all SAP customers that deal with real-world integration, such as logistics,

retail, or manufacturing. Regarding both of the Internet of Things GEs we have already been in

close contact to the PI HANA Plat I/O BPM unit (Patrick Schmidt and his team) in order to evaluate

the transfer of the results into the next generation of BPM offerings. Likewise, we are in constant



exchange with PI Mobile M2M Engineering for inclusion of the results into the next generation of

SAP’s M2M platform. To prove the value for both of the target organizations, we have already

transferred the results to the Global Co-Innovation Lab (COIL) in Regensdorf where they are

tested for both inclusion into our existing landscapes and shown to SAP customers to raise their

interest and increase the pressure for inclusion in our next generation offerings based on

customer demand.

- For Security (WP8), the identification of customers for concepts developed in WP8 Data Handling

GE coincides with the customers of existing SAP products, and of the SAP HANA Cloud teams in

particular; especially, those having specific needs for imposing advanced control conditions on

cloud-hosted resources. For instance, personal information covered by the EU Directive on Data

Privacy EU-95/46/EC and the new upcoming Regulation on the same topic can well represent a

relevant use case for a large part of industrial customers operating in the EU. Data Handling GE

concepts and in particularly the “sticky policy” idea can be used to enforce automatically access

and usage control policies compliant with the legal framework, thus relieving application

developers from the burden of implementing programmatically some ad-hoc mechanism. On the

same line, developers can take benefit of the optimized declarative approach for the cloud to

manage in an easier and performing way any resource. In order to facilitate the adoption of Data

Handling GE concepts, it was chosen to pursue collaborative approaches, involving FIWARE WP8

SAP team together with relevant SAP product development/security teams. In particular, the SAP

Hana security team is involved in the transfer of concepts to SAP Hana product and its

development teams.

Control mechanisms for adoption

As control mechanisms for the adoption in such collaborative research projects, several alternatives

depending on the nature and context of the results to be used are followed in SAP.

The planning and selection of effective mechanisms to enable the adoption of concepts, experiences,

results, or learnings in the course of FIWARE is decided due to the nature of the different results in each

single case by the SAP management – our Co-innovation approach (as described above).

A main route to adoption is the transfer of concepts and results in exchange with SAP business units. It is

decided by SAP business units which results have the potential to be exploited in the near future, for

example, when a concrete customer demand is known, or if some results and knowledge is exploited

later. Such route to adoption has been chosen, for example, for WP results in the context of service

marketplaces.

In order to evaluate the value of software components that are already at or near productive state, SAP

has established its Global Co-Innovation Lab (COIL) Network, which is a globally distributed set of teams

and lab facilities aimed at driving and facilitating innovative projects. This strategy is only applicable in

special contexts. For example, work results from WP5 (Template Handler GE and the MRCoAP Protocol

Adapter) are already in the process of being transferred to the COIL laboratory in Regensdorf

(Switzerland) in order to evaluate the inclusion into existing SAP systems (and to demonstrate them to

customers). The results of the COIL evaluation in this case - also in terms of customer interest – are a key

factor for verifying potential adoption. The respective manager at COIL is Pascal Hagedorn with who we

are in constant exchange.

Taking WP8 as an example, the collaborative approaches are generally structured as follows: First, the

FIWARE WP8 SAP team together with the security team of the target SAP product studies together the

feasibility and the applicability of FIWARE-developed concepts and contributions. Secondly, a transfer

strategy is designed, and executed in partnership by the joint team. The objective of such strategy may

vary, but in general it affects the evolution of a product’s security features. Regular calls are in general

scheduled for the joint team, in order to review the status of the activities and to recalibrate the strategy



execution. Besides these two examples of how adoption is verified, the adoption of possible product ideas

is driven by the SAP business units.

Managements Contacts

The following management contacts supervise our work and the adoption of work results in different

innovation areas and with different adoption and dissemination strategies:

- Platform and Software development contributions: Mr. Peter Giese, HANA Platform – Head of

Operations & Development.

- IoT contributions: Dr. Carsten Magerkurth – Manager HCI PI BIT

- Security contributions: Mr. Volkmar Lotz, Head of Product Security Research, part of the SAP P&I

ACES Organization (Architecture, Communication, Education and Security).

Main project results and exploitation

We describe the exploitation of the project results, the GE’s, and other contributions.

As described, the main focus of our FIWARE contribution is on engaging with communities and

ecosystems in order to gather feedback on the usage of our software in order to be able to learn and

develop improved future business offerings for our customers. SAP provides the enabling technology

which can be used by 3rd parties to adopt the offered concepts within customer and partner settings.

These 3rd parties can create commercial or non-commercial FIWARE instances and they can use SAP’s

Generic Enablers and other contributions in FIWARE in these FIWARE instances.

SAP has planned from the project start, how the set of FIWARE results should be exploited and how an

appropriate route to its exploitation for each FIWARE result should look like – be it for external uptake in

user communities or company-internal uptake. During the runtime of FIWARE, this plan has been

continuously reviewed and adapted wherever necessary.

The different exploitation approaches for SAP’s concrete results in FIWARE are shown in Table 5.

Table 5 SAP’s FIWARE results (software components) and their exploitation approach

WP FIWARE Result Description of SAP’s

Exploitation Approach for

FIWARE result

Availability in

FIWARE

Current State of Exploitation

GE and GEi and Tools – Open Source (sorted by WP)

WP3 Service

Description

Repository GE

Service Registry

GE

Marketplace GE

including the

Pricing Simulation

Decision Support

Published as Open Source

using a BSD-like software

license for a very wide

adoption and commercial

exploitation by 3rd parties

free of charge; SAP-

Internally exploitation using

different approaches.

Pricing Simulation Decision

Support features published

as binary software to the FI-

PPP consortium and

interested external parties

Available in FIWARE

Catalogue, Github, FIWARE

Forge & WIKI with full

software documentation

Available as global instance

in FIWARE Testbed

Available in FIWARE-LAB as

configured images

Pricing Simulation Decision

Support available to FI-PPP

members in FIWARE

Testbed as-a-Service &

available to FI-PPP

Illustrated by a list of projects

adopting the SAP GE’s in the

Applications Services Ecosystem

section.

Within SAP, for the marketplace we

have conducted together with a 3rd

party a marketplace-oriented

project (EIT 2013 umbrella project,

described below). For

confidentiality reasons, the

company name is available on

request.

Pricing Simulation Decision Support

has been demonstrated to several



members & external parties

as binary software for

experiments

SAP product and solution

management groups with strong

business interest.

WP5 Test and

evaluation server

environment for

NGSI (Tool

Component)


using a software license

(BSD) for a very wide



free of charge

Available in FIWARE

Catalogue with full


Available in FIWARE

Testbed


configured image

Component was picked up e.g. by

FI-STAR use case project

SAP-internal: targeting to transfer

concepts / key results into an

upcoming IoT/M2M platform.

WP5 Template Handler

GE






free of charge

Available in FIWARE

Catalogue with full


Available in FIWARE

Testbed


configured image

GE is developed in close

collaboration with the IoT-A project

Within SAP, underlying IoT

extensions were discussed with

BPMN experts and have now been

published at

http://www.iot4bpm.de/ as

extensions to the standard.

WP5 Protocol Adapter

GE






free of charge

Available in FIWARE

Catalogue with full


Available in FIWARE

Testbed


configured image

Within SAP, we are targeting to

transfer the protocol stack to an

upcoming SAP IoT/M2M platform.

WP8 Data Handling GE

- PPL

Publish as Open Source





free of charge

Available in FIWARE

Catalogue with full


Available in FIWARE

Testbed, GITHUB, FIWARE

Forge,


configured image

The GE has been positively

evaluated and adopted in their PoC

by a number of UC projects

(SMART AGRIFOOD, INSTANT

MOBILITY, FINESENY and FINESCE).

Within SAP, some concepts and the

sticky policy approach are adopted

by SAP departments to be

transferred to a new service

offering within the SAP HANA

Cloud products

The Open Source release of the

Data Handling GE is officially

adopted by two running FP7

Projects that are: A4Cloud and Co

Co Cloud

WP8 DB Anonymizer

GE

Publish as Open Source





Available in FIWARE

Catalogue with full


Available in FIWARE

The GE is being evaluated and

customized for the inclusion in the

FINESCE PoC.

GE was also considered for

inclusion in PoC by FINEST and



free of charge. Testbed, GITHUB, FIWARE

Forge.


configured image

INSTANT Mobility UC projects,

however due to lack of resources

the integration of DB Anonymizer

had to be cancelled.

WP9 SoPeCo Software

Performance

Cockpit (Tool)






free of charge.

Within SAP, exploitation

extends the framework for

use with strategic SAP

products.

Available in FIWARE

Catalogue with full


Available in FIWARE

Testbed


configured image

Within SAP, we are targeting the

integration into the development

environment of the SAP HANA

Platform. Already, the following

solutions have taken up the

framework: SAP Liquidity Risk

Management Powered by SAP

HANA, SAP Fraud Management

Powered by SAP HANA, the SAP

HANA Live for SAP Business Suite

and the SAP HANA Cloud platform.

Further Contributions (sorted by WP)

WP3

WP5

WP8

Open Specs, API

description,

roadmaps,

architectures

Defined the blueprint

specifications of the API

and other software details

as open specifications to a

broad audience.

Available in FIWARE Forge,

FIWARE WIKI, and further

locations in the FIWARE

portal landscape

Use case projects and other

projects have evaluated the GE

documentation and are using them

to assess possible adoption. Several

projects have adopted our GEs.

WP3

WP8

USDL Language

and

USDL-SEC

(an extension of

the USDL

Specification)

Co-developed with USDL

community and support

broader adoption (e.g. in FI-

PPP use case projects, USDL

community projects)

Available in USDL Websites

and in FIWARE WIKI

Illustrated by a list of projects

adopting Linked USDL in the


section.

Within SAP, USDL and USDL-SEC

were investigated in a cooperation

project on USDL-SEC s w.r.t. SAP

offerings (e.g. SAP Store), and in

other evaluation activities in SAP.

USDL-SEC is currently adopted by

the Security Compliance GE to

describe all security GEs in FIWARE.

USDL-SEC and USDL were adopted

by the FP7 Assert4SOA7 and OPTET

8

projects.

Within SAP, a joint effort with the

Assert4SOA team is currently in

progress to transfer to SAP

marketplaces (for instance to the

SAP Store) innovative marketplace

methods and technologies for

dealing with security requirements

described by USDL-SEC and other

relevant artifacts.

7 http://www.assert4soa.eu

8 http://www.optet.eu



In the following Sections 0 until 0, the outcomes are described ordered by the FIWARE chapters WP3,

WP5, WP8, and WP9 with respect to a common overview, licensing, pricing FIWARE infrastructures,

uptake of the GEs and tools in communities and ecosystems as well as within the company.

Detailed Results of Applications Services Ecosystem

The main contribution in the Applications Services Ecosystem (WP3) chapter to the FIWARE project is the

careful design and blueprint of a new inter-company business framework with adequate security and

trust.

SAP actively supports 3rd

parties to build upon this blueprint and support them to adopt the developed

concepts, software artefacts and related material in their business domain and software. These concepts

are tailored to streamline related internal and external processes around services and allow

simplifications and cost reductions.

SAP provides enabling technology to programmatically and easily adopt these concepts within customer

and partner settings (including test suites for basic compliance testing for alternate implementations).

Finally SAP envisions high potential for novel business ecosystems crossing company, cultural and domain

boundaries coming out of and enabled by the FIWARE Applications and Services Ecosystem concepts, as

within the FI-PPP use case projects of phase 1 and phase 2 or in SAP’s own ecosystems, for example.

Marketplace GE, Service Description Repository GE, Service Registry GE

Licensing:

The SAP GE’s for business frameworks (marketplace, service description repository, and service registry)

were decided to be made available as Open Source components with the goal to allow for a very easy and

promising adoption and experimentation by 3rd parties. Therefore, a BSD-like open source license was

finally selected since it allows for a very easy and unproblematic usage of the software by 3rd parties so

that they can build on the GE software and use them for commercialization. The Pricing Simulation

Decision Support (PSDS) supports the decision-making processes, i.e. when a software provider company

in the FIWARE environment must decide about competitive pricings for its offerings. Any such provider -

who uses the FIWARE marketplace to sell his/her products - can employ the FIWARE Pricing Simulator to

conduct a pricing analysis and to take pricing decisions with regard to the software and services he/she

sells through the FIWARE marketplace. It is not exposed as a service but as a Rich Internet Application,

accessed through the end user's Web browser, and it was released to all FI-PPP members for

experimentation. In order to protect our IP rights, SAP released the pricing simulator as a binary software

component and not as open source software (the same decision approach is actually followed by various

other FIWARE partners). The software related to the Pricing Simulation Decision Support Tool is provided

on request to anyone for the project lifetime of the FI-PPP and on request up to three years later under

“most favorable” FRAND (Fair, Reasonable And Non-Discriminatory) licensing terms. Once SAP releases a

related product offering, the availability of this product does apply, upon inauguration of the product.

This means that it is accessible by the partners of the FIWARE-PPP Projects and external parties under a

bilateral agreement, which is to a minimal considered FRAND, or deemed granted under better

conditions, if others provide a better deal.

Pricing:

For these GE’s (marketplace, repository, registry), SAP has chosen to release them free of charge to 3rd

parties as open source products in order to facilitate uptake by a wider community audience. Developers

and even competitors can use this software asset. Also for the Pricing Simulation Decision Support (an

optional GE extension), SAP has chosen to release them free of charge as a binary component to the FI-

PPP-internal community as Software-As-a-Service for inspection and experimentation.



FIWARE Infrastructures:

The Marketplace GE including the Pricing Simulation Decision Support, the Repository GE, and the

Registry GE are available in the FIWARE Catalogue, FIWARE Forge, and the FIWARE WIKI. The Marketplace

GE, Repository GE, and Registry GE are available as open source on GITHUB.

The software documentation for all software results (e.g. open specification, installation guide,

programmer documentation, software description) is publicly available in the FIWARE WIKI.

Marketplace GE, Repository GE, and Registry GE are available to the FI-PPP members in the FIWARE

Testbed as global instances for evaluation and experimentation. Likewise, the Pricing Simulation Decision

Support Tool is available as a binary software component in the FIWARE Testbed since May 2013.

Marketplace GE, Repository GE, and Registry GE are available to the public in the FIWARE-LAB

infrastructure since September 2013 as configured images for evaluation and experimentation by third

parties.

FIWARE Packages:

In WP3, three software “FIWARE packages” are part of the offerings of all FIWARE partners in WP3.

The Marketplace GE and the Repository GE are bundled together with other FIWARE GE’s in two of these

three “FIWARE packages” offered by WP3 in the FIWARE Catalogue (publication is pending).

1) Package 1: “Business Framework Provisioning Package“

- Partners: ATOS (Lead), UPM, SAP

- Used GEs: COMPEL, Store, Marketplace, Repository

- Delivered to be offered in FIWARE-LAB as “dedicated instances”


2) Package 2: “Name: “Business Framework Consumption Package”

- Partners: UPM (Lead), TID, SAP

- Used GEs: Wirecloud, Store, Marketplace, Repository, RSS, Identity Management

- Delivered to be offered in FIWARE-LAB as “dedicated instances”


These two packages are currently in production: The software package has been developed and only the

publication in FIWARE Catalogue is pending as of end of April 2014 (M36). The final publication effort will

be led by ATOS and UPM during the extension phase.

Uptake of the GEs and results:

Regarding uptake by FI-PPP use case projects of phase 1 and phase 2, our WP3 GE’s have been evaluated

and been used in a number of projects (a complete list is available in FIWARE deliverables). Further details

about the evaluations of these GEs in the use case projects are described in the WP10 deliverables on

validation (for example, D10.5.2b).

Figure 22 shows a list of the adoption of SAP’s WP3 GEs in the FIWARE use case projects of phase 1 and

phase 2. As a prominent example for phase 1, the WP3 SAP GEs were adopted in the Finest use case

project with the aim to optimize freight forwarding with multitude of involved partners, e.g. dispatching

of hazardous goods. The aim there was to improve efficiency & lower TCO in logistics with an optimization

in relation to time, quality, and price. Here, the Marketplace, Repository (& USDL Editor) have been

evaluated for usage while another focus was on defining a domain specific USDL contribution for the



logistics domain in relation to logistics services. Besides that, Smart Agrifood used the repository and the

marketplace for some of their POC demonstrators. Envirofi and InstantMobility investigated the usage of

repository and marketplace in their architectures, while Finseny evaluated the marketplace for the design

of their architectures. For examples of phase 2 uptake, FISPACE works with the Repository (Nadeem Bari

from Paluno - The Ruhr Institute for Software Technology, University of Duisburg-Essen). FITMAN works

with the Repository for its phase 2 trials (Adam Blackaller from TANet, Coventry University). FINESCE

works with the Repository in experimentation (Padraic McKeever, RWTH Aachen).

Figure 22 Adoption of WP3 GEs in FIWARE use case projects phase 1 and phase 2

Regarding uptake by FI-PPP external projects, several activities are:

- Support of "LoFIP - Logistics Future Internet Platform" in adopting the Marketplace Generic

Enabler for a logistic-specific use case. The use case 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 [D.12.3.3

Report on Collaboration activities].

- Support of Broker@Cloud research project (FP7): Together with the adoption of Linked USDL (see

below) the project is (as planned) currently analyzing the usage of Registry GE and Repository GE

for usage in the project. Please see more details below for the Linked USDL adoption report

below.

- Support of “InDiNet” – “Innovative Services in the future Internet” for SME in adopting Linked

USDL and the Repository GE and Marketplace GE.

Uptake in FI-PPP EIT ICT liaison project - SME co-innovation with communities and ecosystems:

An example that illustrates SAP’s approach of collaborating with an SMEs in a co-innovation setting in

order to explore possible future business software offerings is the FI-PPP EIT ICT liaison project during

2013 until December 2013 in cooperation of SAP and an SME (name upon request, funded from EIT ITC

Labs). The 3rd party SME has strong ties to the Helix Nebula initiative as one of its core members, and the

services-based Helix Nebula ecosystem (cloud-related services) is comprised of several companies which

have strong business ties to SAP within our SAP ecosystem. The main goal of this FI-PPP EIT ICT liaison

project collaboration with the SME was to develop together the concept of a new service marketplace for

cloud-related infrastructure services that would connect service providers and service consumers in this

vertical application domain of infrastructure services for IT platforms. The marketplace was built as a

prototype case study in collaboration of SAP and the SME.



For this EIT project, an “SME workshop” was held in Paris on 17.09.2013, (funded by EIT project – not

FIWARE) with participation of 9 SMEs. Two webinars were held during the project for the SME

demonstrating the GEs of the business framework and in particular marketplace GE and repository GE at

that time to the SME (using a dedicated legal framework to grant necessary access rights for

experimentation purposes) which had been installed on the (additional) “EIT Trento Testbed” FIWARE

instance. The service marketplace case study allows to experiment with different aspects of offering and

trading infrastructure services published by the SME, and after its software development this marketplace

prototype was evaluated by several selected customers of the SME. The EIT project was completed in

time in December 2013.

After this successful collaboration and other activities in the Helix Nebula project/network, SAP now is

investigating first possible follow-up activities w.r.t. a service marketplace as a SAP-internal proof-of-

concept for some traded data and its related services based on an implementation using SAP products like

the SAP Hana database platform and potentially the SAP Ariba business network platform. The

investigation is ongoing in the respective SAP business unit with an open result at time of writing end of

April 2014.

Summing up, this FI-PPP EIT ICT liaison project serves as an excellent example of how SAP can exploit

FIWARE results following its co-innovation approach in order to gather feedback to learn and develop

improved potential future business offerings for our customers.

This project highlights the innovation process where after a community & ecosystem – related co-

innovation project with an SME in a known service-based ecosystem (here: Helix Nebula network) some

of the achieved learnings, results and experiences are used for SAP-internal follow-up activities within a

SAP business unit.

Linked USDL Uptake:

With regards to the uptake of the Linked USDL modelling language, it is evaluated and even extended by

possible users as a first step with a subsequent evaluation by the users as well. In most cases, the USDL

evaluations take place in conjunction with partners who are interested to use one or more of our WP3

GEs. For a list of FI-PPP use case projects or FI-PPP projects which currently use or consider to use Linked

USDL, please refer to the list of projects using our GEs (marketplace, repository, and registry) given above.

A set of projects beyond the FI-PPP umbrella are currently known for the adoption of Linked USDL:

- In the MSEE project, Linked USDL plays an important role in the servitization of manufacturing

products. It is used to describe services as well as their building blocks, namely tangible and

intangible assets. In the course of the project, SAP created a mapping between MSEE modeling

artifacts and Linked USDL and developed an extension to SAP’s FIWARE’s Linked USDL editor that

implements the mapping by automatically deriving skeleton service descriptions from imported

MSEE modeling artifacts (Heiko Witteborg). This work was supported by Thorsten Leidig, who also

provided training on the extension concept of the Linked-USDL editor to the MSEE consortium.

Additionally, import and export function for Linked USDL were created in the MSEE Toolbox

(based on the Eclipse Modeling Framework). In general, MSEE benefitted from FIWARE’s work on

the Future Internet Service Platform which was adopted and tailored to the specifics of the

manufacturing domain.

- Broker@Cloud (FP7) selected Linked USDL as the Service Description Language for describing

business aspects of cloud services and applications in brokerage ecosystems in a platform-neutral

fashion (A. Friesen, SAP). Broker@Cloud project uses Linked USDL for service descriptions

provided by service providers to a cloud service brokerage platform during the service onboarding

process for service assessment and certification. Broker@Cloud project focuses on quality



assurance and optimization of brokered services and apps. Linked USDL SLA module specification

has been adopted and extended to provide support for Broker@Cloud quality assurance,

continuous optimization, and failure prevention and recovery mechanisms. Furthermore,

additional Linked USDL modules have been specified: Linked USDL Testing and Linked USDL

Preferences. Linked USDL Testing module provides support for classification and transport of

testing models and instructions within Linked USDL service description including their grounding

to WDSL, REST and web apps to enable testing automation. Linked USDL Preferences module

provides support for expressing consumer preferences on services and service categories offered

on a cloud service brokerage platform and therefore enabling automated reasoning about service

descriptions based on consumer preferences. Broker@Cloud project has been supported by

FIWARE (Torsten Leidig, SAP) in order to better understand and assess Linked USDL concept.

- Supporting the TrustedCloud initiative of the German Ministry of Economics with USDL workshop

and collaborations: AG Standards (Christian Janiesch, FZI Karlsruhe), PeerEngergy-Cloud (Jörg

Baus, DFKI), TRESOR (Mathias Slawik, TU Berlin), CLOUDWerker (Thomas von Bülow, 1&1),

Value4Cloud (Wollersheim, Fortiss), cloud4health (Wolfgang Ziegler, Fraunhofer).

- Supporting “InDiNet” – “Innovative Services in the future Internet” for SME in adopting Linked

USDL and the Repository and Marketplace GE.

- Further cooperation projects about Linked USDL / USDL include a collaboration with the German

software-cluster on description of services with USDL, a cooperation with the University of

Coimbra (Jorge Cardoso, Jorge Aroujo, Catarina Ferreira da Silva) on USDL modeling, with the

Open University UK (Carlos Pedrinaci, Ricardo Lopes) who are implementing a new Linked USDL

tool, with the GreenClouds project (Hector Fernandez, Vrije University of Amsterdam), an

evaluation for use in an upcoming project (Antonio Filograna, Engineering), and a collaboration

with T-Systems on Linked USDL for Legal Vocabulary (Erwin Schuster, T-Systems). More details on

these activities can be given and they are partly described in existing FIWARE deliverables.

SAP-internal uptake:

For the WP3 results in the context of service marketplaces, the results of the FI-PPP EIT ICT liaison project

(until December 2013) are to be used within SAP for a possible transfer into the context of the SAP HANA

platform and the SAP Ariba business network as the follow-up. The SAP Ariba business network supports a

huge network of companies that are interconnected with each other forming SAP’s global procurement

network. Within a design analysis activity and functional proof-of-concept prototype it shall be

investigated how several core business process functions offered by the SAP Ariba procurement platform

can be used from a (new) service marketplace for cloud related services. The results of this activity can

provide useful further insights for SAP with respect to integration capabilities of the SAP Ariba offering

with existing 3rd party business systems which are operated by companies as part of the SAP Ariba

business network.

The Pricing Simulator Decision Support as part of the marketplace was demonstrated to several SAP

solution and product management groups (in the area of consumer products) in several internal meetings

until February 2013. Some groups had indicated their interest and had stated that the functionality of this

tool qualifies as a possible differentiator (candidate) for existing software in the market. With this result,

SAP has decided with respect to protecting its IP rights, that the software was not be released as open

source, but it can be used (a) free-of-charge by FI-PPP members in the FIWARE testbed for

experimentation and testing and (b) free-of-charge by all external parties using a FRAND license scheme

who can obtain a binary component to experiment with it – as described in the above sections on

licensing and pricing. So despite the fact that some of the domain knowledge about this Pricing Simulation

was taken up by SAP in the form of its Intellectual Property, the tool was in parallel released also (as a

binary component) to FI-PPP and publicly under certain conditions with a FRAND-like licensing scheme.



Detailed Results of Internet of Things (IoT)

Within WP5 (IoT), SAP is providing tools to support developers with the following results:

• Test and evaluation server environment for NGSI (Next Generation Service Interface):

• Template Handler GE - Execution Environment for IoT-aware business processes

• Protocol Adapter GE for the COAP protocol based on MoteRunner

All three results complement the work performed in WP5 around IoT technologies which are considered

as highly relevant for SAP in the future. For example, SAP has released its own IoT management platform

and will extend this platform on an on-going basis (detailed below).

Test and evaluation server environment for NGSI

Within WP5 (IoT), SAP is providing a test and evaluation server environment for NGSI. The server allows

testing software that interacts with various IoT Generic Enablers using the FIWARE NGSI10 binding, such

as the IoT Broker Generic Enabler. Such software can be other FIWARE GEs as well as clients of FIWARE

GEs, e.g., from use case projects.

- Licensing and Pricing: For this GE, SAP has chosen to release them for no costs to 3rd parties as

open source products in order to facilitate uptake by a wider community audience. Developers

and even competitors can use this software asset with the best available license for this purpose.

- FIWARE Infrastructures: The test environment has been deployed for test use in the FIWARE

Testbed and was correspondingly published in the FIWARE Catalogue and in FIWARE-LAB.

- FIWARE Packages: As a tool, the test server is not part of any package. It works autonomously due

to its nature as a test tool.

Uptake of the GE:

The test server was used by members of the projects BUTLER and FI-STAR during the development of

their software. From a temporal perspective, now that the server is deployed and ready for use, SAP waits

for feature requests and feedback. The target group for the software is basically anyone who plans to

interact with FIWARE components and enablers using FIWARE NGSI. SAP recommends that anybody who

develops a client interacting with a GE server should test its NGSI interface using the test server. It is quite

likely that many partners from use case projects and even outside the PPP have used the test server

already, as there is no setup/ integration involved. One can simply check his own NGSI implementations

for correctness.


NGSI might become a highly relevant service interface for the IoT in the future. Therefore, we aim for

offering parts of the tool to the product group developing SAP’s future IoT / M2M platform.

Template Handler GE

SAP has implemented a Generic Enabler (GEi) for the execution of IoT-aware Business Processes, the

Template Handler GE. The Template Handler GE was previously defined by Ericcson.

SAP has released the GE as an execution environment for IoT-aware business processes that complements

our work in the Applications Services Ecosystem with the capability of executing business processes and

services that take the idiosyncrasies of the Internet of Things into account.

The execution environment is capable of interpreting and running process models based on BPMN

extensions. These extensions specifically include core IoT modelling constructs such as entities, actuation



or sensing tasks that are derived from the Internet of Things-Architecture (IoT-A) reference architecture.

The execution environment allows for leveraging modern BPM modelling constructs in order to provide a

robust integration of IoT technologies into the enterprises of the future.

Licensing and Pricing:

For this GE, SAP has chosen to release them for no costs to 3rd parties as open source products in order

to facilitate uptake by a wider community audience. Developers and even competitors can use this

software asset with the best available license for this purpose.


The Template Handler GE has been deployed for test use in the FIWARE Testbed and was correspondingly

published in the FIWARE Catalogue and in FIWARE-LAB.

FIWARE Packages:

Due to its nature as a backend component within IoT architecture, the Template Handler GE is part of the

WP5 Backend Package.

Uptake of the GE:

The target groups are enterprises who have to deal with the Internet of things and it needs to bridge their

enterprise systems with low level IoT systems in order to gain an insight on the shop floor. Due to the IoT

extensions being “real” extensions to the BPMN standard, SAP has released the extensions as such and

the Template Handler software as Open Source.


The underlying IoT extensions have already been discussed with BPMN experts within SAP, and have been

made available as BPMN extensions to the BPMN 2.0 standard. The extensions can be freely downloaded

at http://www.iot4bpm.de.

Protocol Adapter GE

Within FIWARE, SAP has also developed one of the Gateway Protocol Adapter GE instances (the MRCoAP

Protocal Adapter). This protocol adapter implementation allows Moterunner devices to communicate

with FIWARE; in particular it can act as an NGSI Event Producer. The Gateway Protocol Adapter GE is one

of the primary adopters of WP5, as it allows for integrating real devices.

Licensing and Pricing:

For this GE, SAP has chosen to release them for no costs to 3rd parties as open source products in order

to facilitate uptake by a wider community audience. Developers and even competitors can use this

software asset with the best available license for this purpose.


The Template Handler GE has been deployed for test use in the FIWARE Testbed and was correspondingly

published in the FIWARE Catalogue and in FIWARE-LAB.

FIWARE Packages:

Due to its nature as a gateway component within an IoT architecture, the MRCoaP Protocol Adapter GE is

part of the WP5 Gateway Package.

Uptake of the GE:



With respect to uptake in FIWARE use case projects, depending on how CoAP as a protocol will be

successful, we expect an uptake of the protocol adapter when respective hardware devices need to be

integrated.

SAP-internal Uptake:

Within SAP, we are currently also investigating the usage of the Protocol Adapter GE within our own

upcoming SAP M2M platform offering.

Detailed Results of WP 8 - Security

Some of the challenges that the Security Chapter in FIWARE addresses are of interest for SAP: the need

for adequate protection of (personal) information in Cloud applications, where multi-tenant

environments can obfuscate information control and responsibilities; the expression of security features

of cloud services, in a way that can assist service discovery activities through advanced reasoning

capabilities.

As a relevant player in the Cloud market, SAP looks at FIWARE results as possible blueprint for upcoming

security functionalities of its services, thus addressing European stakeholders’ demands in terms of

privacy assurance, data protection and the opening of new market perspectives in serious-large scale

cloud applications, though service offerings that are more explicit in term of security functionalities and

capabilities.

SAP contributes to the Security WP with two GEs (Data Handling GE, DB Anonymizer GE) as well as the

USDL-SEC specification contribution.

Data Handling GE and DB Anonymizer GE

Licensing:

We strongly believe that the Open Source approach is the best solution to let our GEs being used and

adopted by a wider community. The choice of proposing our GEs available as Open Source was to permit

to all the open source community to get benefit of our software and help us to enhance the

functionalities and share it with other communities (academic and industrial).

Pricing:

SAP releases the Data Handling GE and DB Anonymizer GE as GEs free of charge to 3rd parties as open

source products in order to facilitate uptake by a wider community audience. Developers and even

competitors can use this software asset with the best available license for this purpose (a BSD license).

For example, the Data Handling GE offers an XACML coupled with a PPL enforcement engine and a PPL

that is unique in the domain. As outlined below, we got some interest from the academic and the

industrial world to use this opens source release for their own purposes.


The Data Handler GEs and the DB Anonymizer GE are available with all information about the GE with

regards to the guidelines, the endpoint URLs, the source code, and the license in the public FIWARE

Catalogue, the FIWARE Forge, and the FIWARE WIKI.

Data Handler GE and the DB Anonymizer GE are available on GITHUB9.

9 https://github.com/fdicerbo/fiware-ppl and https://github.com/fdicerbo/fiware-dba



Both GEs are currently deployed in the FIWARE Testbed (V1 and V2) and therefore accessible to all the FI-

PPP consortium users. Moreover, they are also available in the FIWARE-LAB infrastructure.

Uptake of the GEs:

The Data Handling GE was integrated by three phase 1 use case projects Instant Mobility10, Smart

Agrifood11, Finseny

12. We received very good feedback from these projects especially with regards to the

offered functionalities and the support that we gave them during the integration duties. Concerning the

second phase of the UC, we worked on the integration of the GE into the FINESCE13 project in one of their

demo.

The DB Anonymizer GE was tested and positively appreciated by two phase 1 use case projects Instant

Mobility and FINEST - also with positive evaluations. However due to resource and time constraints they

did not adopt it into their prototypes. Currently the DB Anonymizer GE is being integrated by the phase 2

use case project FINESCE.

The Data Handling GE is also adopted in the EIT-KIC Trust in the Cloud project 2013 (where FIWARE is a

carrier project) as study system for performance measurement in the cloud. It also been proposed as a

starting point concept for the new FP7 CO CO CLOUD (ICT-10-1.4) project starting in November 2013 and

officially adopted by the FP7 A4Cloud project.


Within SAP, some concepts from the Data Handling GE and especially the sticky policy declarative

approach are currently exploited by SAP departments for definition of a new functionality in the SAP

HANA14

product. This internal transfer concerns the design of a solution based on declarative policies for

supporting Authorization migration to the SAP HANA platform as defined in a SAP-Internal white paper15

that was released in SAP’s ecosystem community “SCN”. SCN is SAP’s public social network for SAP

professionals to stay up to date with the latest SCN news, projects and features and it is sponsored by

SAP.

USDL-Sec specification extension

USDL-SEC is a Linked Data vocabulary that supports the description of security features of software. It can

be used effectively in conjunction with USDL, in order to produce comprehensive descriptions of

software, for instance in a software marketplace, to describe the different characteristics of offerings

(from price to SLA, up to description of security features).

Pricing:

For the USDL-Sec contribution, no pricing is needed since this contribution is an extension of the USDL

specification. Nevertheless, SAP released it free of charge to 3rd parties in order to facilitate uptake by a

wider community audience. Developers and even competitors can use this specification asset.


10

http://instant-mobility.com/index.php/public-documents/public-deliverables-2.html?download=98:fippp-instant-

mobility-barcelona-feb-2012&start=40 11

http://www.smartagrifood.eu/sites/default/files/content-files/downloads/SAF-D200.3-

ValidationArchitecture%26SystemSpec-V1.0_Final.pdf 12

http://www.fi-ppp-finseny.eu/wp-

content/uploads/2013/04/D1_11_Security_Elements_for_the_FINSENY_Functional_Architecture_v1_0.pdf 13

http://www.finesce.eu/ 14

http://www.saphana.com/welcome 15

http://scn.sap.com/docs/DOC-40587



The USDL-Sec specification is available on GITHUB16.

Uptake of the GEs:

The USDL-SEC specification was adopted and integrated in two EU projects FP7 OPTET (ICT-8-1.4),

ASSERT4SOA (ICT-2009.1.4).

The USDL-SEC is currently adopted on the FIWARE project level by the Security and Compliance GE

offering a configuration dashboard for all the Security GEs developed in FIWARE.

For SAP, having developed a synergy with the ASSERT4SOA team for the development of their PoC, the

USDL-SEC development team joined the exploitation effort of ASSERT4SOA, thus presenting and

proposing the developed concepts to stakeholders of SAP Marketplaces.

Detailed Results of WP 9 - Developer Tools

As part of the dependable engineering of services and service delivery, one focus is on sizing and

certification of performance and capacity properties of service endpoints.

In the context of WP9 (Tools), SAP is offering the Software Performance Cockpit (SoPeCo) framework for

systematic performance evaluations of software systems. The SoPeCo framework provides a toolset for

GE and FIWARE Application developers to support the definition and execution of systematic goal-

oriented performance measurement scenarios.

SoPeCo is expected to facilitate understanding of service endpoint performance issues and ultimately help

in improving the performance of existing solutions.

Software Performance Cockpit (SoPeCo) framework

Licensing:

SAP decided to release the SoPeCo component framework with its developed functionality for

performance measuring and evaluations as an Open Source component. The reason for this was SAP’s

intention to be able to gather experiences and feedback w.r.t. two important audiences:

- Uptake and adoption by the general public and user communities / ecosystems of relevance for

SAP (like the performance community) and e.g. for uptake by FI-PPP use case projects or alike,

- Demonstration to several interested SAP-internal groups which had signalled their interest to

evaluate, adopt (and extend) the software component within these respective SAP departments.

Therefore, SAP has released SoPeCo as Open Source under the BSD license in Q1 2013 so that SoPeCo is

publicly available now. This step reflects SAP’s strategy to tap into the performance community by

fostering collaboration in the context of EU IST and national projects.

Pricing:

For the SoPeCo component framework, SAP has chosen to release them free of charge to 3rd parties as

open source products in order to facilitate uptake by a wider community audience. Developers and even

competitors can use this software asset with the best available license for this purpose.


SoPeCo documentation has been made available in the FIWARE Catalogue (Tools section). SoPeCo has

also has been made available in the FIWARE Testbed and a configured image for the FIWARE-LAB has

16

https://github.com/fdicerbo/usdl-sec



been created in order to enable experimentation by 3rd parties. Furthermore it is already available as

open source at http://www.sopeco.org/.

FIWARE Packages:

SoPeCo is not part of a FIWARE package because WP9 has not defined any FIWARE packages.

Uptake of the GEs:

SoPeCo is used in the following research projects:

- In the CloudScale project, SoPeCo is used for the projects goal to find and solve scaling problems

for cloud applications.

- In a cooperation project with the Karlsruhe Institute of Technology (KIT), SoPeCo is used and

installed as a publicly accessible Software-as-a-Service instance to experiment with application

performance measurements for performance engineering.

- SoPeCo was also used on FIWARE project level to measure & improve the performance of the

Repository GE (see Appendix of deliverable D9.2).


Within SAP, the exploitation plan is to transfer SoPeCo as an enhancement of the development

environment of the HANA platform by middle 2014.

As a first step, SoPeCo already has been instrumental in performance regression testing and performance

analysis of complex SAP HANA queries for products like the SAP Liquidity Risk Management Powered by

SAP HANA, SAP Fraud Management Powered by SAP HANA, or the SAP HANA Live for SAP Business Suite

solution for real-time operational reporting (which went into general-availability on August 13th, 2013).

For the last mentioned SAP solution, SoPeCo is also used in the business unit for reporting the

performance regression results to management. Besides the on-premise solutions, SoPeCo was used in

SAP departments as a framework (based on the SoPeCo Open Source component) for establishing a

performance regression framework for platform services of the SAP HANA Cloud Platform offering.

Background: The overarching exploitation process

In the following section, further aspects of our business exploitation plan and report for FIWARE are

explained for a number of different perspectives - answering specific reviewer requests for M24. We keep

these answers here for information purposes and have updated them to reflect the current state as of

M36 where necessary.

Sustainability beyond the FIWARE lifetime

For SAP, the aim of building a next generation business platform and a services ecosystem is a pillar in

SAP’s overall strategy. SAP intends to foster novel business ecosystems and uptake in communities across

company, cultural and domain boundaries coming out of and enabled by the FIWARE Applications and

Services Ecosystem concepts. SAP has selected this strategy according to our general company-wide co-

innovation strategy, where new concepts functionality and business offerings are developed in close

cooperation with customers and partners.

For FIWARE, this co-innovation approach has been followed by having our software adopted in FI-PPP use

case projects, further projects beyond the FI-PPP scope, and even within SAP ecosystems and within

product departments.

For this purpose and in order to achieve a high degree of sustainability of our efforts, SAP leverages as a

primary vehicle the FIWARE infrastructure to allow for our FIWARE software assets to be located,

browsed, instantiated, and used. Our SAP GEs and tools are available for 3rd parties in the FIWARE

Catalogue. Installations of our GEs are available in the FIWARE-LAB or in the FIWARE Testbed.



SAP has released our Generic Enablers open specifications under IPR rules that allow for an exploitation

and sustainable usage both in Open Source as well as proprietary, closed source products to maximize

adoption. This is achieved by releasing all of SAP’s FIWARE Generic Enabler Open Specifications under the

same “FIWARE Open Specification Legal Notice (essential patents license)”17. This essential patents

license has been defined in the FIWARE consortium by agreement among the partners and this license has

been adopted by other FIWARE partners also.

Our SAP GEs and tools are released to the public as Open Source software with a very permissive BSD

Software License to allow for a wide adoption in communities and ecosystems (with the exception of a

feature set of the marketplace GE for Pricing Simulation which is released as a binary software

component under a special license schema – as described in detail above).

It is to be noted, that with this very open licensing approach, SAP is one of the few FIWARE partners that

enable a very permissive access and usage of the FIWARE results for 3rd parties and for their subsequent

commercial exploitation by these 3rd parties. They can adopt our software, adapt it to their business

settings, and run installed versions of these GEs on their own or other hosting infrastructures – even for

commercial purposes.

In more detail, for the software results used by developers and 3rd parties who want to build competitive

offerings, SAP has contributed the following reference implementations of its Generic Enablers or the

following software tools:

WP3:

- Software associated to the Marketplace - SAP RI product is provided as open source under a BSD

License. Please check the specific terms and conditions linked to this open source license at

https://github.com/service-business-framework/Marketplace-RI/blob/master...

- Software associated to the Repository - SAP RI product is provided as open source under a BSD


https://github.com/service-business-framework/Repository-RI/blob/master/...

- Software associated to the Registry - SAP RI product is provided as open source under a BSD


https://github.com/service-business-framework/Registry-RI/blob/master/...

WP5:

- Software associated to the Test and evaluation server environment for NGSI is provided as open

source under a BSD License. Please check the specific terms and conditions linked to this open

source license at https://github.com/iotsap/ngsi10testserver

- Software associated to the Template Handler GE is provided as open source under a BSD License.

Please check the specific terms and conditions linked to this open source license at

https://github.com/iotsap/FiWare-Template-Handler

17http://forge.FIWARE.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Open_Specification_Legal_Notice_%28essential_patents_license%

29



- Software associated to the Protocol Adapter GE is provided as open source under a BSD License.

Please check the specific terms and conditions linked to this open source license at

https://github.com/iotsap/mrcoap

WP8:

- Software associated to the Data Handler PPL – GEi product is provided as open source under a

BSD License. Please check the specific terms and conditions linked to this open source license at

https://github.com/fdicerbo/fiware-ppl

- Software associated to the DB Anonymizer DB – GEi product is provided as open source under the

BSD License. Please check the specific terms and conditions linked to this open source license at

https://github.com/fdicerbo/fiware-dba

- Software associated to the USDL-SEC specification is provided on Github. Please check the specific

terms and conditions linked to its open source license at https://github.com/fdicerbo/usdl-sec

WP9:

- Software associated to the SoPeCo - SAP RI product is provided as open source under a BSD


https://github.com/sopeco/Software-Performance-Cockpit/blob/master/ and

https://github.com/sopeco/SoPeCo-WebUI/blob/master/.

For some other FIWARE contributions (Linked USDL, USDL-SEC, Pricing Simulator), SAP has ensured that

the USDL-related specifications are open and accessible to the USDL community (e.g. in the USDL web

sites from SAP). As an example of how we achieve such sustainability in communities, the USDL

community is enabled to work on its own behalf, after SAP has (together with other companies) invested

efforts to start and ramp-up this community for exchange and development of USDL in the community

that is interested in its exploitation.

Besides this, the efforts for SAP-internal adoption of FIWARE results have been described above in the

Sections 0 until 0 above in detail for all work packages and their results.

Focussed exploitation into distinct environments

The Service industry has become the biggest employer in Europe and tends to be a critical force to ensure

economic growth. Our work within FIWARE contributes to the expansion of the service economy by

creating an IT infrastructure for Business Services where services become accessible, discoverable, easily

deployable, and ultimately tradable on the Internet. In doing so, our work helps the service sector to

generate new value added services, develop innovative business models, and establish new business

value chains.

In order to realize its general co-innovation approach in FIWARE, SAP drives a two-fold exploitation

strategy for the developed FIWARE results:

- Engage with communities and ecosystems to drive adoption of GE:


Here we concentrate on results and activities for the first strand due to SAP’s main focus within FIWARE

is on the application of the concepts towards domain specific communities and ecosystems (partially

defined by FI-PPP use case projects e.g. FINEST, FINSENY, ENVIOFI, Instant Mobility, SmartAgriFood).

Other EU-funded and national-funded projects are adopting USDL or USDL-SEC for their specific

ecosystems (ASSERT4SOA, OPTET, MSEE, TrustedCloud). The results of both kinds of activities impact

different aspects of both SAP’s technology platform as well as the various application business units (e.g.



logistics, public services). As a key to cater for a wide adoption by communities and ecosystems, the

delivery as Open Source software free of charge to developers and key users has been instrumental for

SAP. SAP-internally, technical assets and concepts around USDL are continuously evaluated for their

fitness and timing to be fed into SAP products with a couple of successfully completed transfer activities

such as SAP HANA Cloud Platform, M2M platforms, and others.

One key component is the realization of service marketplaces that are expected to become increasingly

relevant for Business Software companies such as SAP. While more static business networks and service

chains are already a reality, highly flexible and more automated approaches to setting up, operating and

optimizing such interconnected business networks and business ecosystems are needed. If this fails, only

few such chains can be realized in practice due to prohibitive cost and complexity. A major building block

for addressing this problem space is a unified approach to describe services with concepts such as the

Unified Service Description Language (USDL). Instead of only addressing functional properties this allows

advanced business tools to adequately support the complete business service lifecycle. As illustrated with

the example of service marketplaces, GEs like service description repository, registry, and further

components are based on USDL as its underlying service description approach.

The Linked-USDL initiative updates the underlying standards foundation of USDL to current IT trends. The

scope of security aspects as they are covered by USDL-SEC is being expanded, in order to respond to the

need of explicit information regarding the security features of services, thus addressing requirements

coming from large-scale, sensitive application developers and providers. The short term plan aims at the

specification of a standard, the long term focus on an integration of the results into new business

ecosystems. As a joint WP5/WP3 effort, Linked USDL is evaluated with respect to its usability in an

embedded IoT-environment. In this IoT context, Linked USDL and SSN are combined to drive self-

descriptive smart items, which will allow an easy integration of these items into the USDL environment.

Furthermore, SAP pursued a strategy for achieving standardization of comprehensive service description

in line with the concepts of USDL. However, given early experience in the market and in the

standardization bodies has caused a revision of the strategy for achieving this goal.

In 2010/2011 SAP tried to drive USDL in an incubator group at W3. Although the group generally gave

quite positive remarks, the standardization effort was finally put on hold, being judged as premature

considering the current situation of the market. SAP sees the uncertainty and dynamics of the market as

the main inhibitors to pursue standardization at the current state of the market. Secondly, in particular

the more operation-centric facets of USDL partially overlap with competing standards. Since we still need

the full scope of the information model contained in USDL but recognize when other, more mature

standardization efforts partially can meet our requirements, we have modified our approach accordingly.

The new dual-pronged tactic which is currently in place is: Solidify the core of USDL to make it ready for

standardization, eventually drop overlapping facets and influence the partially overlapping standards to

address our needs. As a consequence SAP continued to promote USDL as a concept and as enabling

technology and start to actively build communities of practice to evolve USDL facets towards market

readiness. The actual standardization creation will follow, based on the respective communities’

feedback. An updated list of our Linked USDL activities has been given above in Section 0 on results of the

WP3 chapter “Applications Services Ecosystems” in this document.

For the second strand of SAP-internal uptake, detailed information is given above in Sections 0 until 0

above for all work packages and their results.

Customer profiles

SAP’s enabling technologies target a variety of potential users and customers, who can consume and use

the technology in their current business domain. To illustrate this, the following list focuses on the

potential main consumers and their envisioned roles.

For example, for the apps and services chapter the following customer roles are relevant:



- The service provider or business partner mainly participates in an ecosystem enabled with FIWARE

technology through provisioning, consuming or discovering of services in relation to his business.

A service provider is in general active in one business domain where his main business model is

residing, but potentially is enable to be active in other business domains, enabled through

FIWARE technology. As a sub-role the value-added service provider will be enabled to build

innovative services and apps on top of the offerings out of the ecosystem.

- Service platform operators or FIWARE instance providers will use, operate and/or enhance USDL

enabled technologies provided by SAP potentially a subset of the following components:

Marketplace, Repository and Registry.

- Customers will be indirectly addressed by the components provisioned by the other stakeholders

as the envisioned components target mainly B2B2C (Business to Business to Consumer) scenarios.

- Developers can consume the provided enabling technology in order to adopt the concept in their

own implementations and consume components which are based on this technology.

- Domain experts will be given the opportunity to understand the general concepts behind the

technology and will be enabled to adapt them to their given business domain. This can have

implications on the other involved roles and fosters the applicability of the technology towards a

specific domain.

For further work areas in FIWARE, similar role definitions for target users are important. Further role

definitions can be found in FIWARE Wiki in the “Materializing” sections and the FIWARE Architecture

documents as well in the document 3rd party innovation enablement in relation to the chapters, where

SAP is actively involved.

A report of the customer communities and ecosystems with interest for SAP with respect to FIWARE is

given in Section 0

Channels and channels customer segments

SAP uses mainly existing FIWARE channels in order to distribute concepts, design, enabling technology

and results coming out of the FIWARE project. Figure 23 shows these channels (not limited to this list):

FIWARE collaboration bodies like architecture board, scientific council; FIWARE use cases; FIWARE

Catalogue, FIWARE website, FIWARE Wiki, FIWARE twitter channel; FIWARE Testbed, FIWARE-LAB,

FIWARE webinars, virtual architecture sessions and other events that are part of consortium wide

activities.

Additionally, SAP supports community-enabling channels such as http://www.linked-usdl.org and

http://www.internet-of-services.com.

Furthermore, existing national and international channels where SAP (Research) is actively involved are

engaged with positioning FIWARE technology and potential benefits. Some of them are: national funding

bodies, existing funding projects among them MSEE, LOFIP, Effizienz Cluster Logistc Rhein/Ruhr,

SoftwareCluster (Indinet), TrustedCloud, Deutsche Digitale Bibliothek); European Cloud Expert Group,

W3C), OPTET (ICT-8-1.4), ASSERT4SOA (ICT-2009.1.4).

Finally, SAP-internally the results from FIWARE have been and are considered for enhancing existing

products in order to suit our customer’s needs (e.g. SAP HANA Cloud Platform and other potential future

SaaS solutions offered by SAP) with concepts and concrete software assets in order to leverage existing

channels of SAP to reach its own ecosystem and customer base.



These channels complement all the other business service ecosystem activities from SAP. They specifically

address aspects which are more innovative than the mainstream business.

Figure 23 FIWARE target groups and channels

Specific benefits along customer segments

SAP closely monitors benefits and potential value propositions coming out of FIWARE in order to integrate

them in relevant material, presentations and provide them to interested parties.

In general SAP sees the potential of cost cutting and lowering the TCO (total cost of ownership) and TCD

(total cost of development) for the involved stakeholders, taking part in an integrated ecosystem around

services, there are a number of individual benefits, that will be outlined below for the various involved

roles and stakeholder groups. Finally the actual costs need to be closely monitored in order to validate

the assumptions and further estimate realistic return on investment assumptions, which can be

furthermore be part of subsequent communication. This eventually will lead to a lower entry barrier.

Second, main benefits for all involved parties and companies are currently foreseen to further strengthen

their position in the highly competitive Future Internet world. This will lead eventually to a plural

constitution of the business ecosystem “Internet”.

The service providers and business partners mainly benefits from the benefits coming out of the

ecosystem around services. He/she can streamline the (internal and external) processes in relation to

service provisioning, consumption and discovery. Service providers have increased transparency and can

potentially provide services within various domains with less spend and efforts than before. By adding

FIWARE capabilities to their infrastructure, they can position themselves in the “Future Internet” and will

be able to explore new business models and revenue channels for their existing businesses.

Service platform operators or FIWARE instance providers will be enabled to host and operate future

internet platforms and domain specific ecosystems as primary or secondary revenue channels to their

current infrastructure provisioning business. Enhancing existing service platforms with USDL enabled

technology enables a high degree of cross domain business opportunities, taps into new markets and

opens new business opportunities and channels for their existing assets.



Customers will benefit from cost-cuttings at the service and infrastructure provider sides and will

potentially have access to a larger selection of tailored since the barrier to do so is lowered significantly.

Customers can furthermore benefit from greater competition and higher transparency, as other

stakeholders in the market will expose more competing services.

Developers can add value to their existing products or come up with new products, enabled through USDL

technology, which can add new revenue streams and customer groups, that weren’t reachable before at

all or at least not with sustainable margins.

Domain experts ideally would benefit from USDL enhancements of other domains and increase

transparency and processing costs within their existing business domain. Eventually they will be enabled

to broaden their reach and scope and tab into new business domains or enabled their current domain

participants to tab into new domains much easier, than with proprietary and non-standard measures.

Sales proposition

Depending on the concrete addressable roles and stakeholder, related (sales) channels will be used,

mostly leveraging the existing channels named before and tightly integrated in the overall communication

planning.

SAP has made all of SAP’s FIWARE Generic Enabler Open Specifications publicly available and usable

under the “FIWARE Open Specification Legal Notice (essential patents license)”18. This license has been

defined by agreement of partners in the FIWARE consortium and has been used by other FIWARE

partners also. It allows for exploitation and sustainable usage both in Open Source as well as (if planned

by a 3rd party for their own product) proprietary, closed source products to maximize adoption.

For developers and parties who want to build competitive offerings, SAP contributed all reference

implementations of our Generic Enablers under permissive BSD-like Open Source licenses.

Additional knowledge material (e.g. training material), papers and publications are used to position and

furthermore strengthen the uptake within the existing SAP partner and developer ecosystem.

Sales process

Following the two-fold exploitation strategy, the community uptake of our GEs and usage of concepts and

technologies in future or existing SAP products is chosen along two different routes:

First, for developers and competitors, the Generic Enablers and the tools from SAP are free at no cost to

use and commercially exploitable, this is fully supported in an open community approach. Since SAP is

mainly interested in broad uptake of the enablers to leverage the resulting network effects, no dedicated

sales process will be used here.

Second, for the route through adoption into existing and future SAP offerings, the existing sales processes

(direct, telemarketing and web based, depending on product group) will be used as per decision of the

SAP business units, if needed. For these activities, sales-related data cannot be given in a straightforward

way, because a huge set of influencing factors needs to be taken into account and the direct relation of

FIWARE concepts or technologies cannot be separated out for illustration or reporting purposes in this

context.

Globalization of the exploitation plan

18http://forge.FIWARE.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Open_Specification_Legal_Notice_%28essential_patents_license%

29



The global reach of SAP as company is considered constantly while engaging within FIWARE or related EU

public funded project. SAP ecosystem is addressing approximately 11.500 partners, 3.000.000 developers

and over 253.500 customers in 180 countries. With very few exceptions, all SAP products are offered

globally, enhancing them with FIWARE concepts will not diminish that. Already today and in the past the

envisioned domain specific ecosystem use case projects within FI-PPP are tailored to multi-nationality.

Involved technology was selected to support global reach and the ability to be consumed by third parties

even more, namely by reusing state-of-the-art technologies (Linked Open Data, current programming

languages, et al).

SAP reuses state-of-the-art hosting and community tooling (forge, wiki, github, etc.) to furthermore

onboard communities across the globe for collaboration across domain and language/cultural boundaries.

3. IBM Research - Zurich


IBM has the world's largest IT research organization, with more than 3,000 scientists and engineers

working at 8 labs in 6 countries. IBM invests more than $5 billion a year in R&D and is the world’s leader

in patent filings. In aggregate, the company holds nearly 37,000 patents worldwide.

IBM strives to lead in the creation, development and manufacture of the industry's most advanced

information technologies, including computer systems, software, networking systems, storage devices

and microelectronics. IBM participates in and contributes heavily to the work of standards consortia,

alliances, and formal national and international standards organizations. Where appropriate, IBM adopts

consensus technologies in order to maintain openness, interoperability, and application portability. IBM

Research is a leading research institution in the world and contributes significantly to the research

community.

IBM Israel Science and Technology Limited is better known as IBM Research – Haifa. Since it first opened

as the IBM Scientific Center in 1972, the Haifa lab has conducted decades of research that have proved

vital to IBM’s success. The lab is one of five research laboratories located outside of the United States,

and has close working relationships with IBM Israel and its twin research laboratory in Zurich. In Haifa, 25

percent of the technical staff has doctorate degrees in computer science, electrical engineering,

mathematics, or related fields. Employees are actively involved in teaching in Israeli higher education

institutions and in supervising post-graduate theses. R&D projects are being executed today in areas such

as storage systems, cloud computing, healthcare and life sciences, verification technologies, business

transformation, information retrieval, programming environments, optimization technologies, and

analytics. The IBM Research – Haifa lab has four departments, two of which are contributing to FIWARE:

- The System Technologies and Services department develops leading-edge system and storage

technologies for IBM's advanced IT products and services. The team is particularly strong in the

areas of system software and architecture, and system design and optimization tools, providing

support for IBM’s server and storage systems product lines and IBM Services business units. The

department has in-depth expertise in the emerging field of cloud computing and our work in

system software focuses on the areas of virtualization and systems management, which we

believe will be primary enabling technologies to make cloud computing a marketplace reality. We

also develop advanced system and I/O architectures designed to deliver performance

breakthroughs to IBM and the industry. The department’s work in the area of storage systems

focuses on developing new functions for data protection and availability, storage security, long-

term data preservation, and storage power management as it relates to IBM's green technology

initiative. A special focus area of the team is storage support for cloud computing. This project



investigates the architectural challenges of designing a highly scalable and cost-effective storage

infrastructure, allowing easy storage and access to data objects, and the ability to mobilize them

across the cloud.

- The Software and Services department develops software technologies to exploit advances in

computing infrastructure that benefit both traditional IT businesses as well as the system

engineering and embedded software development space. The department's technology areas

include: application development tools, new design, programming languages and models for

business architects and embedded software development, software lifecycle management,

product line engineering, software evolution via refactoring and reverse engineering of complex

systems, and governance of software development. Additional areas of activity include complex

event-based systems and solutions, distributed middleware with a focus on high availability

solutions, high throughput low latency messaging technologies, and new technology and business

models such as SaaS (Software as a Service). The department also has a strong focus on business

optimization, workforce management, business transformation and optimization, and business

transformation targeting various business design methodologies.

IBM-IL Assets and Generic Enablers in FIWARE – Overview

IBM developed assets in 3 technical chapters of FIWARE: Cloud, Data and Tools.

Majority of IBM effort in FIWARE is concentrated in the Cloud chapter, where we provide an advanced

IaaS cloud infrastructure based on OpenStack, including multiple enhancements developed by IBM. The

DCRM GE is the foundation of all present and future FIWARE instances, including the various FIWARE Lab

nodes across Europe used by Use Case projects and by the broader community (including Phase 3

Accelerator projects, as well as various events, hackatons, etc). This document elaborates on IBM's

exploitation of OpenStack as a whole, as well as of individual extensions which are part of our DCRM GE

implementation.

In the Data chapter, we deliver an implementation of Complex Event Processing GE, successfully used by

majority of applications developed and demonstrated on the FIWARE platform, including multiple Use

Case project applications, all the FIWARE demonstrations (including those at events, project reviews, etc),

as well as applications expected to be developed by the Accelerator Projects during Phase 3 of the FI-PPP.

In the Tools chapter, we deliver Trace Analyzer, providing the application developer a convenient tool to

spot resource bottlenecks and optimize their applications built on top of FIWARE GEs.

Moreover, as part of the transition between FIWARE and FI-Core projects, we are making adjustments

following the sustainability goals in FI-Core – namely transition to a fully open source reference

implementation of the FIWARE platform. As part of this transition IBM's effort in FI-Core will be focusing

on the open-source implementation of the GEs we own. The proprietary components and enhancements

developed in FIWARE are still available to the European community (under the terms agreed in the FI-PPP

Collaboration Agreement), but will be phased out from the reference implementation maintained and

evolved in FI-Core. This includes the Trace Analyzer, as well as DCRM PIVOT scheduler.

1) IaaS Data Center Resource Manager (DCRM) – OpenStack

Overview

IBM's implementation of DCRM GE is based on OpenStack – an emerging open source project, becoming a

de-facto implementation across rapidly growing number of companies joining the OpenStack community

(as of December 2014, above 440 companies are actively contributing to the OpenStack ecosystem).

IBM is a platinum member of the OpenStack community, one of the 3 leading code contributors, and has

made a strategic decision to leverage OpenStack in all its future cloud products.

Main project outcomes



As part of FIWARE, IBM team is contributing code to the OpenStack community, and also develops value-

add capabilities, some of which remain proprietary and are shipped as part of IBM's commercial offerings

based on OpenStack. The main contributions are to the Compute Service (Nova project) and to the

Storage Service (Cinder and Swift projects, providing block storage and object storage capabilities

respectively).

Value proposition

OpenStack comprises multiple projects, each focusing on particular aspect of cloud management. The

main components are:

- Nova: provisioning and management of virtual machines

- Glance: management of virtual machine images

- Cinder: provisioning and management of persistent storage volumes

- Neutron: provisioning and management of virtual networks between VMs, as well as additional

network services

- Keystone: identity service, service catalogue, authentication and authorization service

- Heat: workload orchestration

These components together provide a powerful holistic IaaS cloud platform.

Potential users/customers

OpenStack is being commonly used as part of several kinds of solutions:

- IaaS public cloud (e.g., by Rackspace, HP)

- IaaS private cloud (e.g., IBM, Red Hat, Cisco, Canonical, and many other vendors)

- IaaS community cloud (e.g., CERN)

- As a basis for a continuous delivery platform for a dedicated cloud-based SaaS platform (e.g.,

Comcast, Best Buy, eBay, etc)

- and many other modes

Exploitation channels

- Open source: OpenStack is available under Apache V2 open source license. There are multiple

vendors that develop pre-canned distributions of OpenStack, also providing commercial support

and services (conceptually similarly to Linux distributors).

- IBM products: IBM has made a strategic decision to build all its future cloud products and

offerings on OpenStack. In particular, this includes:

o IBM Cloud Manager with OpenStack (ICM) – the primary OpenStack-based private cloud

product by IBM, used to manage private clouds on customer's premises, hosted on IBM

Cloud, or following a hybrid approach combining both. ICM is fully compatible with

OpenStack APIs, and is currently based on OpenStack Juno release (as of December 2014).

In additional to 'vanilla' OpenStack capabilities, it provides support for IBM-based

hypervisors (such as Power and zVM), hybrid cloud scenarios (with multiple OpenStack

regions), IBM's professional support, and more.



o IBM Cloud OpenStack Services – a novel hosted managed private cloud offering, providing

clients a deployment of OpenStack on dedicated hardware hosted on IBM SoftLayer,

managed by IBM. The offering uses ICM as the underlying OpenStack implementation.

o IBM Cloud Orchestrator – the advanced OpenStack-based private cloud solution, adding

on top of ICM capabilities to manage complex application patterns in an automated

manner.

� OpenStack is also used as an embedded component in several IBM's products,

such as IBM PowerVC and IBM PureApplication.

- Other (e.g., other EU projects): OpenStack is being widely used by numerous research activities in

which IBM is involved, including such FP7 projects as VISION Cloud and CloudWave, as well as

Horizon 2020 projects such as Mikelangelo, Beacon, IOStack.

Joint exploitation opportunities

All the GEs in the Cloud chapter are standardized on OpenStack APIs, and together comprise a powerful

cloud platform, going beyond competition. For example, this includes GEs developed by Telefonica

dealing with management of application blueprints.

Moreover, many key European companies are also adopting OpenStack, and are building products and

offerings around it. This includes Ericsson, Alcatel Lucent, Bull, Cloudwatt, eNovance, France Telecom,

Deutsche Telekom, Thales, Telefonica, Intel, SAP, and others.

In addition, it was agreed with XiFi partners that they will standardize their node deployment on

OpenStack, and will promote it across the wide ecosystem of companies that will be building their

applications on top of XiFi infrastructure (merging into FIWARE Lab).

Another venue for joint exploitation currently under evaluation by IBM and Telefonica is around hosting

of FIWARE commercial deployment on top of IBM’s commercial OpenStack hosting offering, namely the

IBM Cloud OpenStack Services, hosted on IBM’s SoftLayer bare-metal cloud infrastructure.

Summary

OpenStack is a truly unique open source community, developing a rapidly maturing IaaS cloud middlware.

IBM is taking a leading role contributing to the community, enabling a wide range of vendors to leverage

the results of the community work for a wide variety of usage scenarios. Moreover, IBM is using the

community code a strategic foundation for all its future products and offerings in the area of IaaS cloud,

which can be used to offer FIWARE services in production.

2) IaaS Data Center Resource Manager (DCRM) – PIVOT

Overview

The PIVOT scheduler delivers scheduling automation for clusters of virtualization hosts called "System

Pools". The PIVOT architecture is open and flexible, allowing for integration of multiple domains of pool

management. Each domain – performance, security, availability, etc. – can inject its own policies and

participate in the pool automation control.

PIVOT has been successfully integrated in IBM's VMControl product, and consequently impacted

additional products exploiting VMControl for virtualization management automation, such as Smart Cloud

Entry and others.

PIVOT development efforts in FIWARE revolved around OpenStack integration, DCRM development and

adding features (both to OS and PIVOT).




The following outcomes are related to PIVOT:

- PIVOT as an advanced scheduler of OpenStack Nova, providing:

o Optimization flow – re-shuffling VMs to match the pool to a predefined goal. The

optimization flow is particularly useful in cases of acute imbalance among hosts, e.g.,

when adding new hosts to improve overall performance or recovering failed hosts.

o Predictable VM resiliency (w/VMHA) - VMs can be tagged a-priory as HA and have

backup locations assigned to them in an intelligent fashion that consumes less resource

space than trivial shadowing on alternative hosts, by exploiting overlap. Consequently,

upon host failure, VMs can have guaranteed safe havens at which they can be recovered

– unlike the default scheduler, which delivers best-effort recovery.

o Improved multi-deploy – PIVOT reserves resources for the deployed set a-priori, thereby

avoiding resources being "stolen" by later deployment requests, which is a risk faced by

using the ‘vanilla’ filter scheduler.

- Binaries and documentation available for FIWARE exploiters wanting to deploy their own cloud

- Training for XiFi partners on how to deploy and configure PIVOT in the DCRM

Value proposition

PIVOT is a powerful scheduler, with capabilities far beyond the default filter scheduler of OpenStack. It is

capable of computing global placement changes and optimization, relying on the state-of-the-art solver of

ILOG CPLEX. As a result, it is able to overcome local issues such as missing resources on a given host by re-

arranging more VMs around the OpenStack pool. However, PIVOT also carefully considers costs of

relocating VMs to avoid upsetting the VMs too much.

Adding PIVOT to a pool, replacing the filter scheduler, yields several clear benefits as listed in the previous

Section.

Due to closed-source nature of ILOG CPLEX, PIVOT will not be part of the DCRM reference

implementation maintained in FI-Core.


Any provider / administrator that uses FIWARE to build an IaaS cloud foundation is a user of PIVOT.

Additional customers are companies wishing to establish custom IaaS solutions (or even custom resource

allocation solutions), with or without OpenStack. Additional (indirect) users of PIVOT are users of the IBM

products integrating PIVOT.


- IBM products: As noted above, PIVOT is already used in IBM's VMControl product and additional

products relying on VMControl, such as Smart Cloud Entry. Future-wise, IBM intends to further

exploit PIVOT in newer platform managers relying on virtualization automation based on

OpenStack. Additional venues being explored include integration with PaaS platforms, such as

CloudFoundry. PIVOT is also intended for expansion to match hardware virtualization capabilities

in IBM's POWER platforms.

- Joint exploitation opportunities: Joint exploitation opportunities for PIVOT are similar to those of

OpenStack, described in section 4.6.

3) IaaS Data Center Resource Manager (DCRM) – DOVE

Overview



Network virtualization capabilities in DCRM GEri are based on IBM's Distributed Overlay Virtual nEtwork

(DOVE) technology – a network virtualization solution centred on the SDN paradigm and employing

overlays to achieve data plane isolation. In addition to the overlay data plane and the centralized control

plane, DOVE provides a novel intent-based network management abstraction that allows defining

network blueprints capturing all the connectivity aspects of the application in one place. With DOVE

deployed in a FIWARE Cloud infrastructure, users are able to define and manage networking aspects of

their workloads in simple high level terms and with no need to interact with the infrastructure owners.

DOVE is fully integrated with OpenStack Neutron, and the capabilities are surfaced to the user via

OpenStack Neutron APIs.


The project outcomes include a working DOVE components adapted to FIWARE use cases and

requirements, integrated into the OpenStack-based FIWARE DCRM reference implementation. Moreover,

major parts of the effort were targeting contribution of DOVE to the OpenDaylight open source

community (OpenDOVE), which is now generally available under Apache V2 license.

Value proposition

Integrating DOVE into FIWARE infrastructure allows for multiple isolated and independent networks to

co-exist over a shared physical interconnect, so that different exploiters can define and manage their

network using OpenStack Neutron APIs, independently of the other exploiters and of the infrastructure.


FIWARE workloads requiring network connectivity will explicitly or implicitly use DOVE system if it is

deployed in the infrastructure. Some FIWARE users will use DOVE explicitly by invoking self-service APIs

when they deploy their workloads. Other FIWARE users will use DOVE implicitly when they deploy ready

application templates, to be prepared and made available for use as part of the orchestrated

management. Of course, teams preparing the application templates will use DOVE explicitly by invoking

the APIs, to create DOVE network blueprints for the new applications.


- Open source: DOVE network virtualization solution has been contributed to the Open Daylight

OSS project. FIWARE use cases and requirements have driven features into the DOVE system that

be leveraged by all the users of Open DOVE as part of OpenDaylight deliverable.

- IBM products: DOVE technology has become a foundation of IBM SDN VE project – IBM network

virtualization software.

- Other (e.g., other EU projects): HRL team is going to further develop and expand the technology

as part of the future EU projects, e.g. COSIGN, where DOVE can become one of the use cases

deployed upon the next generation all optical data center to be created, as well as Beacon – an

Horizon 2020 project dealing with software defined networking.


Joint exploitation opportunities for DOVE are similar to those of OpenStack, described in section 4.6.

Summary

Over the past years, the DOVE technology has made a long way from a research idea to the working

system ready to be exploited by many parties through Open Source Project (Open Daylight) and the IBM

product (SDN VE). In the context of FI-Core and the evolution of FIWARE Lab, the FIWARE Lab nodes

owners will be able to leverage OpenDOVE in their environments, depending on the specific requirements

and preferences of the individual nodes.



4) Object Storage

Overview

Object Storage GE in FIWARE is based on OpenStack Swift, which is the leading open source object store

solution and is presently in active use by enterprises and service providers alike. Thanks to Swift, IBM, HP,

Rackspace and other providers presently offer public cloud services using a common API, common set of

clients, common services and co-developing their service offerings in an open and transparent way,

facilitating user requirements to enable data mobility between cloud providers. Such data mobility free

customers from being locked to a single provider and allows a healthy competitive environment.

The benefits of Swift includes simple horizontal scaling, low cost, high performance for both writes and

reads, high availability and high tolerance for faults. Swift's fault tolerance enables the use of commodity

hardware when building the storage cloud. To achieve all that, Swift compromises on consistency and

offers an eventual consistency model in which at some rare failure cases, the latest version of the data

may be inaccessible for a limited time and until the system consistency is restored.

Value proposition

Together with others in the Swift community, IBM is enhancing and improving Swift based on the

requirements from our clients. Making Swift a unified object store solution for both private and public

clouds, offers significant advantages to users. First and foremost, using Swift for a private cloud enables

natural mobility between private and public object store services with unified APIs and without changing

the application clients. Such a development lend itself well to considering the public cloud service as a

natural extension of the private cloud, offering maximal power and flexibility to the enterprise and

governmental users of private clouds.

Further, like in the case of the public cloud, Swift for private clouds help free customers for being locked

to a system provider. At the same time Swift as an open source project offers an expedited path for

community innovation to help overcome enterprise and governmental user needs and allows users to

gain control over the code used.


Object store cloud services, either public or private offer the best cost performance ratio for a verity of

vertical market segments including; Healthcare, Media, Telecom and Government. The main use case of

Object Store, unlike the one for traditional file systems is the storage of unstructured objects that are

typically written once and never modified. Prime examples of such objects include images, videos and

recordings which together constitute the majority of the new age media that needs to be stored. Such

information, either born in the cloud or imported (e.g archiving, backup) is best suited to be stored in

Object Stores.


- Open source: As an OpenStack project, Swift is developed under the Apache V2 license and can be

used or changed for free by anyone. Most work done for Swift as part of FIWARE is offered either

via GitHub as extensions to core Swift or offered upstream as part of Swift.

- IBM products: Swift is offered as a commercial public service by a number of vendors including

IBM via SoftLayer, Rackspace and HP. Swift is also part of IBM’s private cloud product portfolio. In

particular, Swift is offered as part of the IBM Cloud Manager with OpenStack product, as well as

the IBM Cloud OpenStack Services offering (hosted on IBM SoftLayer infrastructure and managed

by IBM).




Joint exploitation opportunities for PIVOT are similar to those of OpenStack, described in section 4.6.

Summary

Swift was developed primarily as a public cloud service. Adjusting Swift to meet the private cloud

requirements offers significant advantages to users and is required as part of FIWARE, and is envisioned

to be used by variety of IBM clients and partners, as well as in the broader FIWARE ecosystem.

5) CEP – IBM Proactive Technology Online

Overview

The Complex Event Processing (CEP) GE is intended to support the development, deployment, and

maintenance of Complex Event Processing (CEP) applications.

The CEP GE analyses event data in real-time, generates immediate insight and enables instant response to

changing conditions. While standard reactive applications are based on reactions to single events, the CEP

GE reacts to situations rather than to single events. A situation is a condition that is based on a series of

events that have occurred within a dynamic time window called processing context. Situations include

composite events (e.g., sequence), counting operators on events (e.g., aggregation) and absence

operators.


The main project outcome is a FIWARE CEP GE open specification and a reference implementation called

IBM Proactive Technology Online. The IBM Proactive Technology Online is a scalable integrated platform

to support the development, deployment, and maintenance of event-driven applications.

The IBM Proactive Technology Online engine is a runtime tool that receives information on the

occurrence of events from event producers, detects situations, and reports the detected situations to

external consumers.

The IBM Proactive Technology Online includes means to integrate it with other components through REST

interfaces. The IBM Proactive Technology Online supports events in the NGSI format, and is integrated

with other FIWARE GEs such as the Context Broker GE through events in the NGSI format.

Value proposition

The IBM Proactive Technology Online implementations of the CEP GE provides means to expressively and

flexibly define and maintain the event processing logic of the application, and in runtime it is designed to

meet all the functional and nonfunctional requirements without taking a toll on the application

performance, removing one issue from the application developers and system managers concerns.


In today's world, many applications react to events coming from different sources such as sensors,

devices, user interactions and more. In many cases the arrival of a single event is meaningless, while a

combination of events arriving over time is significant. Any user that needs to identify such patterns over

incoming events is a potential user for the IBM Proactive Technology Online. Using the IBM Proactive

Technology Online, the user doesn't need to program the patterns, and it can use a web user interface to

declare the patterns using high level constructs. This allows better maintenance, in case of changing

patterns, and allows business users, with no programming skills to define and change the patterns.




- Open source: The IBM Proactive Technology Online asset is available as is, under Apache V2 open

source license.

- HRL offering: The IBM Proactive Technology Online is available as is, under Apache V2 open

source license, and can be freely used or modified for experimental or commercial use. IBM Haifa

Research Lab can be contacted with requests for professional services related to IBM Proactive

Technology Online (on commercial terms), such as code extensions, education, deployment and

customization, support, etc.

- Other (e.g., other EU projects)

o The FIspace EU project deals with the business-to-business collaboration of business

processes. The FIspace project extends the IBM Proactive Technology Online towards

predictive event-driven computing. These extensions are offered as paid services to any

other interested partner outside the FIspace consortium.

o The SPEEDD EU project deals with proactive event-driven computing. The SPEEDD project

extends the IBM Proactive Technology Online towards proactive event-driven computing

by incorporating uncertainty aspects. These extensions are offered as paid services to any

other interested partner outside the SPEEDD consortium.

o The FERARI project deals with real-time Big Data technologies. The FERARI project

implements the IBM Proactive Technology Online on top of the Storm platform to make it

scalable and distributed. This offering will be open-source in March 2105.


Since the IBM Proactive Technology Online supports events in the NGSI format, it has high synergy with

the Context Broker GE, allowing applications to subscribe to CEP output events through the Context

Broker GE, and allowing the CEP to be subscribed to various context updates.

Summary

There are three exploitation channels we anticipate for the IBM Proactive Technology Online. The first is

through an open source license, the second is through paid services offered by IBM-HRL per request, and

the third is through services for predictive or proactive capabilities.

6) Trace Analyzer

Overview

Trace Analyzer is a framework for collecting, analyzing, and visualizing performance data to identify

bottlenecks. It works with a variety of performance data sources, such as the Linux tools sar, tcpdump and

several SystemTap scripts. Additionally, Trace Analyzer can be extended to work with other data, such as

application instrumentation logs.

Trace Analyzer graphically presents the data as one or several charts (both line charts and bar charts are

supported), with navigation such as zooming and scrolling synchronized among the charts. This combines

the use of a separate chart for each thread or core on a multi-core system, when convenient, with the

ability to focus on a certain time interval for all the threads or cores. Thresholds can be visualized, and

aggregations such as maximum or average can be shown alongside the original series.

Trace Analyzer also provides other ways to analyze the input data. The data can be browsed record by

record, while the selected record's fields can be viewed. The user can also search the data for records

with certain properties. A useful addition to the graphical view is a fully configurable statistics view,

allowing the user to define and view various aggregations of the trace data, such as the average load of a

processor core or the overall time each thread spent on the CPU. This can also serve to quickly test for the



presence of performance anti-patterns, such as percentage of packets of suboptimal size transmitted over

the network.


The main project outcome is a framework for collecting, analyzing, and visualizing performance data to

identify bottlenecks such as networking bottlenecks, inefficient resource utilization, and synchronization

inefficiencies.

In addition, techniques for displaying coherently big data were developed in this project as well as

techniques for highlighting suspicious and/or outliers in the data.

Value proposition

The Trace Analyzer tool can help developers that develop or use the FIWARE platform to monitor the

performance of their applications and services, identify bottlenecks, and analyze them.


Trace Analyzer is primarily used by teams dealing with development, deployment and operation of

network and/or system intensive applications where performance is critical, including those building on

FIWARE GEs (e.g., Big Data, CEP, multimedia, etc).


- HRL offering: Beyond the availability for experimental use within the FI-PPP, Trace Analyzer tool is

offered for licensing on commercial terms (as per the FI-PPP Collaboration Agreement).

- Other (e.g., other EU projects): Trace Analyzer is used in CloudWave FP7 project, as part of

adaptive framework for optimization of application performance under changing environment

conditions.

Moreover, Trace Analyzer is used internally by IBM developers, as a performance optimization tool.


Trace Analyzer is offered to all developers who use the FIWARE GEs in order to optimize resource

utilization, network, and concurrency. By using Trace analyzer the GEs users may create more efficient

services that will scale to a larger number of concurrent users over the Future Internet.

Summary

IBM will promote the usage of the Trace Analyzer tool internally, by IBM customers and by FIWARE GEs

users. Trace Analyzer users benefit a higher quality of their software with less performance bottlenecks.

4. Thales Communications & Security SA (ex Thales

Communications SA)




Thales is a global technology leader for the Aerospace & Space, Defence, Security and Transportation

markets. World-class technologies and the combined expertise of 67,000 employees in 56 locally based

country operations make Thales a key player in assuring the security of citizens, infrastructure and

nations. Within FIWARE, Thales Communications & Security leads the Thales participation, with Thales

Services SAS, Thales Alenia Space, Thales SA and Thales UK (Research & Technology) as third parties.

Thales Communications & Security has been formed by Thales, combining the expertise of Thales

Communications and Thales Security Solutions & Services in the fields of defence, security and ground

transportation. Through Thales Communications & Security, Thales is pursuing an ambitious growth

strategy in secure information and communication systems for the global defence, security and ground

transportation markets. In particular, the new company strengthens Thales’s position as a major world

player in cyber security. Thales Communications & Security employs approximately 7,000 people at 10

locations in France, providing an extensive portfolio of solutions to customers on every continent.

Thales Services SAS designs, provides and operates Critical Systems. Thales Services SAS offers a large

array of services: Servers Hosting, Outsourcing, Resources on-demand services, Security management

(Cyber Security Operational Centre), Data Centers engineering, recovery plan and Cloud Computing.

ThereSIS within Thales Services SAS is an applied research Laboratory focusing its activity into a number of

key areas as IT Security, Access Control, Privacy, Cloud Computing and the architectures for Web-based

services. Thales Services SAS employs approximately 3300 people at 15 locations and 4 Data Centers.

ThereSIS is one of the Innovation laboratories of Thales Advance Studies. Its mission consists in ensuring

smooth technological transfers within Thales Services product lines. As such, it has as a main objective to

guarantee that R&D investments of Thales are devoted to cutting-edge technologies that will support

todays and tomorrow’s challenges, while being ready to face the industrial constraints of business entities

and customer expectations.

Thales UK, with 8,500 employees based at 40 locations throughout all regions, is the heart of the UK’s

critical infrastructure, delivering technologies in transport, aerospace, secure transactions and integrated

communications. UK annual revenues are around £1.4 billion, over a third of which comes from exports.

Thales Alenia Space, a third-party of Thales Communications & Security, employs 7,500 people in five

countries worldwide, focusing on Space activities.

Thales solutions are covering the following segments / sub segments:

Security

- Urban security systems

- Critical infrastructure protection systems (airports, energy, sensitive sites, etc.)

- Secure ID systems

- Information technology security

- NRBC systems

Ground transportation

- Rail signaling (mainline and metro)

- Integrated communication and supervision systems

- Fare collection systems

Defence

- Radio products

- Systems



o Strategic and infrastructure networks

o Mobile networks

o Defence protection systems

o Information technology security

o Support and services

Space (Navigation Domain)

- Prime contractor of Galileo Ground Mission Segment (GMS)

- Prime contractor of EGNOS

- Location-Based Solutions (LBS) provider taking benefit of Galileo and EGNOS programmes and

associated expertise.

FIWARE relevance in your current business model

Thales Communications & Security is conducting a number of far-reaching innovation programmes

focused on its key technologies, with particular emphasis on command & control systems and

hypervisors. These programmes are an integral part of a Group-wide R&D strategy designed to maximise

technological synergies between Thales businesses.

In addition, Thales Communications & Security is a major stakeholder in the Group’s policy of open

innovation, working alongside industry partners and academic research institutes in high-tech clusters.

The same strategy of innovation is driving an ambitious investment programme to create global lines of

products and solutions around strategic technologies such as cyber security, tactical software radio and

secure cloud computing.

The involvement of Thales Communications & Security in FIWARE is taking a major place in this strategy,

especially in the cyber security and secure cloud computing areas.

Moreover, Thales has set up a company-wide programme for the transformation to the Cloud, covering a

wide range of business domains. Thales has heavily invested together with Orange and the French state in

CloudWatt, a new European player in the IaaS market where virtualization management technologies for

SMEs, institutions and the general public are being co-developed. Thales is not only an investor in the

company, but also a provider of security.

CloudOMC is a complementary internal product line for critical private IaaS solutions, that is offered both

as a service to key accounts (ministries, banks, hotel chains, etc..) and used for internal projects requiring

elastic resources.

Stepping up to the challenge of data sovereignty in the cloud, Thales has also developed the CYRIS cloud

security solution to protect the data assets of its customers in any type of cloud environment. CYRIS is a

comprehensive offering comprising security technologies and expertise developed specifically to respond

to all kinds of threats targeting the cloud.

Thales UK has focussed its participation in FIWARE to align with its UK Security business. Thales e-Security

has been a global provider of data protection solutions with more than 40 years’ experience securing the

world’s most sensitive information. Thales products and services improve the security of applications that

rely on encryption and digital signatures, while some 80% of the world’s payment transactions are

secured with Thales equipment.

Within FIWARE, Thales UK is exploring how security solutions can be realised in the future Internet.

Specifically, a more mobile, virtualised world present new security challenges. In FIWARE, Thales UK is

advancing its application-level security solution, Content Based Security, which controls access to content

in an information container, not possession of the information container. Such an approach offers novel



security features and in FIWARE, a service oriented approach has been developed based on an Open API

specification.

Thales Alenia Space brings its expertise in Global Navigation Satellite Systems (GNSS) and knowledge of

assisted GNSS technology. Its applicability in FIWARE environment makes perfect sense with the

introduction of Location GE facilitating the location retrieval and GNSS assistance of mobile devices.

In accordance with Thales Group governance principles, defining Thales Research and Technology (R&T)

strategy and governance to develop technological synergies across the Group, the Technical Directorate

through Key Technical Domains (KTD) governs the conduct of R&T in the Group. This includes policies to

promote innovation outcomes exploitation.

Thales Group R&T is characterised and managed in 4 domains, called Key Technical Domains (KTD):

Hardware (KTD HW), Software (KTD SCIS), Processing (KTD PCC), Systems (KTD SYS).

The Group R&T governance comprises definition of R&T strategies for each of the KTDs, and the cascade

of these strategies to the entities undertaking R&T activities. With the objective to improve both the

solution attractiveness and offer competitiveness, these R&T strategies aim at developing technological

assets, and validated technological building blocks, to be inserted into Thales offers.

Figure 24 Thales R&T process Map



Figure 25 Thales R&T Activity flow diagram

Technology life cycle

Thales develops and acquires technologies to support the achievement of market outcomes.

Consequentially, not all technologies will be subject to the entire R&T process. In addition to internal

development from TRL (« Technological Readiness Level ») 1 – 3 (Research Phase) technologies may be

developed externally by third parties or under collaborative arrangements. These technologies may be

candidates for Risk Reduction (TRL 4 – 5) activity and would therefore enter the process through the

Initial Gate Approval.

R&T “Initial Gate” zoom-in

The Initial Gate approval marks a decision to progress development of a technology beyond TRL 3.

If such approval is achieved, the technology will be further developed to TRL 5 and an assessment made

as to whether it will then be included as an element of product roadmaps or other Thales offers. The

development to TRL 5 is referred to as the Risk Reduction Phase.

To achieve Initial Gate approval the KTD Board must first be satisfied that the technology has reached TRL

3. Second, the KTD Board must be satisfied that there is market pull for the technology. This is

demonstrated through at least one Division identifying this technology as a long-term option in their

product roadmaps and policies.

Finally, given that the investment to progress a technology from TRL 4 – 5 is significantly greater than

from TRL 1 – 3, the KTD Board will take account of the anticipated return on investment when deciding to

progress a proposal through the Initial Gate. This decision is supported by a plan for the Risk Reduction

Phase, comprising schedule, budget and expected outcomes.

A technology that achieves Initial Gate approval will be inserted as a long-term option in the product

roadmap. This approval is therefore referred to as an authorization to roadmap.

R&T “Risk Reduction Phase” zoom-in

For each study of the activity plan, this phase consists in carrying out the activity with the intention of

progressing to TRL 5.

This Risk Reduction Phase is aimed at testing the technology against constraints that reflect the conditions

of use that the technology would face if inserted into an operational application of the Group, with a view

to qualifying the technology for insertion in the product policy or other Thales offer. The constraints may

be related to usage -e.g. evaluation of an algorithm developed on a reduced data set with a realistic data

set- or physical -e.g. reduced volume for incorporation in the actual application.

This activity is carried out in close relationship with the operational engineering teams in charge of the

product range that is the target for insertion of the technology. It is highly recommended that operational

teams participate in the work done in this phase.

The FIWARE Testbed allows Use Case projects and third parties to test their Future Internet Applications

based on FIWARE GEs, validating them. In the R&T “Risk Reduction Phase”, the FIWARE Testbed enables

significant economies to deploy conceptual prototypes and to test the technology against constraints that

reflect the conditions of use that the technology would face if inserted into an operational application of

the Group.

R&T “Main Gate” zoom-in

The Main Gate approval marks a decision to insert the technology into a product roadmap or otherwise

include it in a Thales offer. If such approval is achieved, the technology will be further developed beyond

TRL 5 by an operational entity and in accordance with a roadmap approved by a Division.



To achieve Main Gate approval some conditions must first be satisfied:

- The technology has reached TRL 5.

- There is market pull for the technology. This is demonstrated through an operational entity

including the technology in their product roadmaps or otherwise as a component of a Thales

offer.

- Main Gate approval requires the financial commitment of an operational entity supported by a

development plan that includes a schedule, budget, expected outcomes and participating

competence and/or integration centres.

A technology that achieves Main Gate approval will be identified for further development in the product

roadmap. This approval is therefore referred to as an authorization to develop.

FI-LAB , providing Cloud hosting capabilities so Operational entities can run experimental Future Internet

Applications and test them, is an opportunity to successfully pass the Main Gate approval.


Security

- The main outcomes of the WP Security are following:

o Implementation of attack graph integrating new vulnerability scoring capacities;

o Definition and implementation of remediation capacities;

o Definition and implementation of a cloud-connector for security monitoring;

o Consolidation / transfer of the Secure Storage Service;

o Content Based Security, as a Service.

Data/Context Management

- The main outcomes of the WP Data/Context Management are as follows:

o Implementation and integration of Location GE in test bed, including many advanced

features like mobile device tracking and geo-fencing;

o Development of specific simulation tools allowing the demonstration of Location GE

features, as such features are not yet available in core software of commercial handsets

today;

o Creation of a clear roadmap for application development on commercial handsets

(Android) demonstrating the various Location GE features.

Cloud

- The main outcomes of the Cloud WP are as follows:

o implementation and integration of Edgelets GE in test bed, allowing to host lightweight

runtime components on distributed devices

o development and experimentation on the uses and opportunities of such a edge cloud

architecture, close to the users, compared with classical architectures with resources

allocated from a centralized pool

How are you going to exploit the project results in distinct environments?

Thales Communications & Security intends to integrate the FIWARE project outcomes into 2 different

strategic offers:



- The Cybersecurity Packaged Modular Solution (PMS), called CYBELS;

- The Secure Cloud solution.

With respect to this R&T processes, the FIWARE project has been identified as a Key Enabling

Technologies (KET) provider for the “Cyber Security Operational Centre - CYBELS” product line, through

the following KTD innovation segments:

- Attack Graphs;

- Vulnerability analysis & scoring;

- Decision support & Remediation.

Lately FIWARE has contributed to the successful approval of the “Attack Graph” Initial Gate, which allows

us to insert this technology in the CYBELS offer roadmap, aiming now a smooth Main Gate approval.

FIWARE’s outcomes, especially the Configuration Validation and Compliance Assessment & Remediation

components, are already identified to support the ongoing Initial Gate processes for “Vulnerability

analysis & scoring” and “Decision support & Remediation”.

Last but not least we have started to engage with business partner’s dissemination of results and/or

utilization.

This is especially the case of SME Montimage that has chosen to co-develop the FIWARE SecMon GE with

Thales Services in a Virtualized network environment. This joint activity will be supported by in-house

invests (75% for Thales / 50% for Montimage) and a national collaborative project DOCTOR for the French

ANR call for project 2014 (25% for Thales / 50% for Montimage) and will require 2 P.Y during 3 years.

Montimage will provide a Complex Event Processing tool, MMT, and will co-develop with Thales the

Scored Attack paths and the Remediation module benefiting from the novel Network Function

Virtualization capabilities of Software defined networks and virtualized infrastructure more generally.

A direct control mechanism for verifying adoption will consist in the deliverables follow-up of the national

funded project DOCTOR. An indirect control mechanism may consist in Thales customer feedback for the

future Cybels-Scan release encompassing this FIWARE-based Vulnerability management capability.

CYBELs offering details

In a world that is increasingly relying on information networks and web-based communications,

information system security must be more proactive and dynamic in order to detect attacks and provide

effective operational responses at the earliest possible stage.

To answer these needs, Thales has launched CYBELS, a comprehensive approach offering the capabilities

to protect government administrations and businesses' the information and communication systems.

CYBELS also provides police and law enforcement agencies with the solutions they need to combat

cybercrime and cyber terrorism.

CYBELS aims to anticipate and detect cyber threats through permanent hypervision of the most critical

systems in order to provide real-time operational solutions to deal with risks. Thales's offer consists of

equipment and resources allowing the detection, analysis and the reaction to fight all types of current and

potential future cyber attacks (such as virus, disinformation, denial-of-service, destabilization,

destruction, defacement, information/data theft, etc.). Thales CYBELS offer relies on a permanent

operations cyber security centre, which provides 24/7 supervision of the information systems and also

detects and responds to cyber attacks.



Figure 26 – THALES CYBELs Security Operational Center

Context and challenges of Cyber Security

Cyber-security issues are coming from digital information, worldwide networks and applications

interconnection as well as the speeding-up of data dissemination. Going paperless and exchanges

automation are radically changing the economic, social and political environment of nations, making them

more vulnerable.

Figure 27- Thales Cyber Security for Thales

As shown in Figure 27 - Cyber Security for Thales, Cyber-security is the coordinated actions in order to

anticipate, to analyse and to react in case of cyber-attacks. The main goals are to protect in a permanent

way and to provide customer with a timely and relevant measures to deal with the risks targeting the

Information systems.

Cyber Security challenges resides in the followings fields:

- Enhancement of operator confidence in Decision Support Tools;

- Management of massive & heterogeneous security events;

- Comprehensive Visualization of Infra-structure’s situation;



- Smart information gathering, analysis & processing.

We chose to address these topics through the OODA Loop perspective, initially defined for defence

operation process the OODA loop match perfectly the Security event and Crisis management

requirements.

Figure 28– Thales CYBELs Security Operation Centre

FIWARE Contributions to CYBELs

In the following distribution of capacities through the OODA Loop, the bold items refer to functionalities

partially covered by the Security Monitoring GE:

- Observe

o Security watch (early detection of emerging attack)

o Multi-source information (sensors events, vulnerabilities, SCADA inputs) collection and

correlation

- Orient

o Risk analysis

o Role Based visualization

o Predictive Attack Scenario

o Elaborate events correlation & processing

- Decide

o Decision making support tool for prioritization of actions

o Residual Risk analysis through counter measure impact simulation

- Act

o Counter measures recommendation according to regulations and internal security

policy

o Cyber investigations and digital evidences

o Information diffusion to Cyber Security Platforms, partners, CERTs…

The most important is not the vulnerability itself but the magnitude of damage in case of its exploitation

by malicious people. We thus aim at:

- Reducing the impact of attacks, by knowing the paths of vulnerability through our networks,

based on pre-emptive analysis of network vulnerability scan results;

- Identifying the critical assets targeted by the attacker and the best way to defeat him at an early

stage.



The use of Attack graphs supports proactive defence across the whole protect-detect-react life cycle and

helps us:

- Computing key security metrics;

- Guiding the configuration of intrusion detection systems, prioritizing intrusion alarms, and

planning optimal attack responses.

In terms of direct usage of FIWARE results in an application we can quote the Cybels-Scan application that

is part of Thales Consulting services portfolio. This application supports the daily business of Thales

Vulnerability management team who is in charge of the vulnerability assessment and mitigation plan for

the Thales customers. In order to provide an added-value vulnerability analysis it has been planned to

implement a specific SecMon GEi that will fit in the Cybels-Scan current architecture. The Topological

Network Connector, Scored Attack Paths & Remediation modules of the FIWARE Security Monitoring GE

will be added as “to be developed” features by the Cybels-Scan product line in their next answer to

customer project specifications in early 2015.

The detailed architecture of the Cybels-Scan application is confidential material, but we can mention that

the Cybels-Scan application will comply with the interface defined by the FIWARE GE implementation to

allow a deeper vulnerability analysis. Refactoring and/or alternative COTS may be selected during the

product development phase to match license and intellectual property management requirements.

Cybels-Scan application being operated by Thales team, the benefits of this added-value vulnerability

reporting will be automatically available for each Thales customer who has chosen to delegate to Thales

the management of their Information System vulnerability.

Secure Cloud Solution

Concerning the Secure Cloud solution, FIWARE is going to provide a wide range of cloud-ready enablers,

offering possibilities of extension, especially in the scope of cybersecurity (e.g. Security Monitoring, Data

Handling, Privacy …) where the project shall give the opportunity to link the Secure Cloud and CYBELS

solutions (synergy).

The Secure Storage Service GE is studying its merging with the Access Control GE to provide a secure

storage facility for CYBELS solution to provide access to sensitive information (threats, vulnerabilities,…)

to authorized users (security operators,…) or for CYRIS (Cloud Computing) solution to ensure data

protection through new mechanism sharing storage in the Cloud.

Thales UK intends to integrate the FIWARE CBS GE project outcomes into two strategic offers, within the

Thales e-Security business:

• Evolution of our Hardware Security Modules towards security services, using Content Based

Security i.e. CBS as a Service;

• Supplying enterprises with solutions that address their security compliance needs, such as data

protection strategy based on CBS.

Thales already has a significant market position in deploying high assurance security solutions that satisfy

widely established and emerging standards of due care for cryptographic systems and practices, usually

based on hardened, tamper-resistant modules. FIWARE results enable a more service-oriented offering

that complements existing solutions.

As organisations are increasingly required to think beyond the traditional models of securing the

perimeter and locking down specific segments of IT infrastructure, the benefits of protecting at the

application-level are becoming better recognised. Thales foresees opportunities to offer application-level

security solutions, such as the FIWARE CBS, as part of the overall data protection strategy.



Regarding the Location GE solution, FIWARE provides a Location as a Service (LaaS) platform that can be

exposed to third-party applications willing to sell added value services based on the location of mobile

devices provisioned in FIWARE platform.

Mission-critical Cloud-ready applications

Through the project, Thales will complement its Cloud transformation programme by de-risking the

architecture and methodologies for the development of mission-critical Cloud-ready applications, those

that benefit from availability, scalability, cloning, etc. because they were architected to be automatically

provisioned, configured, monitored and managed.

CYRIS

CYRIS is a comprehensive offering comprising security technologies and expertise developed specifically

to respond to all kinds of threats targeting environments in the Cloud. CYRIS products and services

provide effective protection against theft, loss or disclosure of data, intrusions, theft of hard disks from

the cloud computing service supplier’s premises, deletion of incomplete data, etc.

CYRIS is a highly secure solution that protects both virtual data and infrastructures. It incorporates

different security modules for data protection, virtualisation security, access and identity management,

and protection of infrastructures. These modules can be deployed singly or as a package, depending on

the cloud service model employed and the criticality of the applications and data impacted.

With CYRIS, enterprises and organisations retain full ownership, compliance and control of data. Whether

they use a public, private or hybrid cloud, CYRIS is an effective and proven solution designed to meet the

security challenges of cloud computing.

Which customers do we want to serve?

Thales as a global technology leader with a unique capability to provide equipment, systems solutions and

services that meet the most complex security requirements in defense and security, aerospace and

transportation markets serves a broad range of customers.

The main customers of Security Monitoring GE and Access Control GE are the designers, providers and

managers of critical infrastructures and cyber resilient solutions (Administration, Finance, Energy,

Transportation, health, telecommunications..), the Cyber security operational Centers and globally the IT

Security Officers.

The main customers of the Secure Storage Service GE are service providers and users willing to store

securely their data and control its access, especially the Security Operators of Cyber security operational

Centers.

The Content Based Security GE addresses the security needs of its traditional customers in the transport,

defence and aerospace sectors but it also addresses the emerging security needs of an even broader



range of customers in both the public and private sector where sensitive information, such as personal

data, needs to be shared in a responsible manner.

The main customers of the Location GE are:

- Service providers that are willing to retrieve the location of a dedicated fleet of terminals whilst

improving the GNSS performances of the terminal thanks to the GNSS assistance data provided by

the Location GE,

- Or telecommunication operators that needs to manage the location of their subscriber, in order

to exploit it (sales to 3rd party application, emergency call E112, legal interception, proprietary

location based services).

The main customers of the Edgelets GE are any services provider that is willing to offer added-value

services and resources close to the end user, either by owning already existing set-top boxes installed in

user homes (such as ISPs) or having access to such devices (tablets, smartphones, intelligent devices, …)

through specific contracts.

Which channels will be used to reach the various customer segments?

Thales will rely on a number of already existing channels to reach the various customer segments and

promote new offerings leveraging on FIWARE results.

- The Security Monitoring GE and Edgelets GE will be integrated in the CYBELs offer (PMS), Servers

Hosting, Outsourcing and Cloud Computing Thales offer.

- The Secure Storage Service GE will be integrated, after being merged with Access Control GE

functionalities, in the CYBELs offer (PMS) and Cloud Computing Thales offer.

- The Content Based Security GE has already been integrated with the Access Control GE and will

be further integrated into future Thales security service offerings.

- The Location GE will be sold to:

o Telecommunication operators via integrators (like Alcatel Lucent);

� Example of customer: Orange

o Service Provider (direct sales) that need a solution to assist and track specific terminals

with high accuracy, fast time to first fix, high sensitivity and availability. It is then up to the

Service Provider to sell location services to 3rd party customers.

� Example of customer: Telespazio

- The Access Control GE will be integrated in the CYBELS (Cybersecurity Operation Solution) and

CYRIS offer (Cloud Security Solution). At mid-term, it will be integrated in many turnkey systems

delivered by Thales in various civilian and military domains.

Which benefits are the participants going to take to the market thanks to FIWARE?

Security Monitoring GE, Access Control GE and Secure Storage Service GE benefits:

Thales being in charge of Trust, Security & Privacy in FIWARE main benefits are expected there. Results

achieved there will be used also valued in a number of security offerings (e.g. CyberSecurity, Cloud

Security, Application Security …).



The Third parties can evaluate the Security monitoring GE, benefit from partners support, run trial with

real users, test their Future Internet Applications based on Security Monitoring GE and accelerate the

product development..

Content Based Security benefits

The main benefits that the Content Based Security GE offers to the market are an approach to

information security that:

- Is Medium independent - disk, laptop, phone, web site.....

- Is Content Independent - text file, still image, mp3, web page...

- Is Channel Independent - courier, Internet, mpeg stream.....

- Protects information at rest or in flight – on a server, on the wire, over the air.....

- Provides control over access to the information from cradle to grave.

LOC S GE benefits:

The deployment of the Location GE within FIWARE makes it visible to the large number of use case

projects that will promote our solution. The standard being used in Location GE is not yet implemented in

the core software of commercial handsets; the more use cases, the more the standard will be adopted.

The benefit of FIWARE is to show real scenarios and promote this standard towards mobile manufacturers

and fleet operators.

The benefits that our customer (Telco or Service Provider) can get are:

- Network centric architecture, enabling openness to other platform & services

- Access of the location of the handset for 3rd party Service Provider, through standardized

interface

- Strong Marketing benefits towards Service Provider end users

- High reliability infra-structure enabling service continuity even in case of trouble of GPS (thanks to

EGNOS Signal In Space).

- Benefits for the end users (customer of the telco or customers of the service provider) are:

- Usability of any deployed LBS based on A-GPS technology (few seconds to get a position);

- Extended coverage of the service;

- Better accuracy.

How are the benefits going to be sold?

Benefits are going to be sold relying on a number of business models -- including products, service

offerings, etc. All of the above may be applied to the above benefits, depending on the specific

technology and the specific customer needs.

Exploitation of Security Monitoring benefits:

The Security monitoring GE contributes to the promotion of the Thales Security offer and to the

validation process of Cyber resilient solutions developed by Thales.

Exploitation of secure Storage Service GE benefits:

For the Secure Storage Service GE, either it will contribute to the promotion of the Thales Security offer

(CYBELS, CYRIS) or be sold to Security operators to be integrated in their service offering or they will

integrate with FIWARE platform to access its services.



Exploitation of LOC_S GE benefits:

For the Location GE, either our software will be sold to Telco or to Service Provider.

For the Telecommunication Operators, the benefits of the LOC_S GE will be monetized thanks to:

- The use the location of their subscriber by integrating it into in-house Location Based Services

(customized navigation for example);

- The sales of the location of their subscriber to third party commercial application;

- The compliance with future E112 emergency regulation.

- The sales of the location of their subscriber to governmental agencies (legal interception)

For the Service Provider, the benefits of the LOC_S GE will be monetized thanks to:

- The sales of the location of a dedicated fleet to fleet manager (sales as a service);

- The sales of the location of anonymous mobile user to geo-marketing company.

Exploitation of the Access Control GE benefits:

The Access Control GE provides new access control paradigm to answer business needs in a better way

thanks to Attribute-Based Access Control model. The GE will not be sold as a standalone product but it

will be sold internally as a building block for Thales solutions; the first offer integrating the Access Control

GE is the CYRIS solution for data protection in the cloud.

Exploitation of the Edgelets GE benefits:

The Edgelets GE will be used for complementing its Cloud transformation program and de-risking the

architecture and methodologies for the development of mission-critical Cloud-ready applications.

Exploitation of the Content Based Security GE

The principal exploitation route for the CBS GE is as a service (CBS as a Service), integrated with other

Thales security solutions to provide a more complete service offering.

How will the sales process work?

Regular Thales sales process will be followed and Thales sales force will be used.

Globalisation of the exploitation plan - Potential combination with other GEs

Thales works worldwide with customers since will enable and support globalization of the exploitation

plan.

The Access Control GE could be exploited/integrated either with other FIWARE GE (like the Identity

Management GE) or independently.

The LOC_S GE could be exploited/integrated either with other FIWARE GE (like the context broker which

uses the output of the LOC_S, as input contextual data) or independently (for the Telco market for

example).

The CBS GE has already been integrated with the FIWARE Access Control GE and with the FIWARE Identity

Manager (GCP) to provide a more comprehensive management of user identities and rights.

How will you make money from FIWARE Platform?

Thales will offer security products and/or services on commercial terms. Other offerings resulting from

individual versus conjoint use of other FIWARE GEs would also be considered. As such Thales according to

industrial segments of concerns and customer demands will fully explore and release potential of

commercial exploitation of FIWARE platform results.



For the Security Monitoring GE, the first commercial benefit from the FIWARE platform will be to

maintain or increase the Thales market by integrating the Thales Components of the GE into its Cyber

Security solutions. The GE enhances Thales market position as Security operator.

LOC_S GE will be sold as infra-structure to companies that are willing to own the infrastructure. In such

case, the LOC_S customer will have to pay an entry price to acquire the infrastructure, depending of the

configuration (number of users, number of location technologies covered, and type of wireless network,

reliability, monitoring andcontrol...).

For the Access Control GE, the first commercial benefit from the FIWARE platform will be to maintain or

increase the Thales market share on its core business by integrating the GE into its delivered systems.

Thales may consider providing the GE as a standalone offer for external software companies in the future.

Positioning in the market?

TAS-F LOC_S GE position in the market:

Various competitors exist on the market, regarding LOC_S vendors: SIEMENS-NOKIA, ERICSSON, ZTE, NEC,

OPENWAVE, HUAWEI.

The TAS-F Location Server enables:

• Openness to existing infra-structure from other vendors;

• Best in class performances: accuracy, quickness and availability;

• Low maintenance cost.

External availability

Software associated to the LOCS product is usually provided under paid licenses in compliance with

FRAND (Fair Reasonable And Non-Discriminatory) terms. The license price will depend of the requested

configuration (number of users, number of location technologies covered, type of wireless network,

reliability, monitoring&control...). Please contact [email protected] to obtain

further information about pricing of licenses and other commercial use terms and conditions.

However, Thales Alenia Space is open to negotiate bi-lateral commercial agreements with companies

willing to commercialize and/or support the LOCS product, or develop products/services based on it.

Please contact [email protected] to obtain further information about commercial

liaisons.

For the Access Control GE, Thales provides an open source version as part of the FI-Core project. This

version contains the core features of the FIWARE GE.

5. Telecom Italia S.P.A.


The Telecom Italia Group is a major Italian enterprise and a key European strategic ICT player. Driven by

technological innovation and a commitment to service excellence, Group companies (spearheaded by

Telecom Italia, TIM, and Telecom Italia Media) operate in fixed-line and mobile telecommunications,

Internet & Media, Information Technologies.

Telecom Italia Lab is the R&D centre of the Telecom Italia Group. Centre of excellence since 1964 in

networks and services, Telecom Italia Lab took part in the definition and consolidation of the GSM



standard, Mp3 and optical transmission. Today it goes on creating innovation through direct experience in

the planning of fixed and mobile access networks, supporting the evolution of the transport network,

developing platforms and services, prototyping next generation terminals. Within the Company, the

Innovation Function promotes the innovation of applications, products and services for the Company,

identifying the business opportunities they originate, and is directly involved in the evolution of

technologies and applications concerning the future internet and the terminals. Altogether the R&D and

Innovation activities of Telecom Italia involve around 4500 researchers and technicians with an average

investment of 650 M euro per year.

The work carried out by the R&D and Innovation Labs is the outcome of a strategic partnership with the

main manufacturers of telecommunications equipment and systems, and with centres of excellence in

research at the most highly qualified national and international academic institutions. On the

international level Telecom Italia has pledged a substantial commitment to the task of standardisation

and has been involved from the beginning in the European Union Framework Programmes starting with

the first pilot projects of the ESPRIT programme in 1983 and continuing as one the primary European

collaborators in terms of both finance and the number of projects. In the Seventh Framework Programme

Telecom Italia is at present involved in more than 40 Projects.


Telecom Italia owns a considerable know how in the development of innovative service platforms

leveraging enhanced network architectures. Most of such platforms are supporting applications either in

field or in trial phase both for domestic and industrial environments. Telecom Italia brings its expertise to

FIWARE project in various fields: Internet of Things Service Enablement, Data and Context Management,

Applications and Terminals (connected devices). All these are among the most prominent baseline

technologies for the development of new business opportunities to the benefit of the Company.

Telecom Italia is involved in several FIWARE chapters, each specifying and implementing a different set of

Generic Enablers. The following sections identify the main outcomes per chapter.


Telecom Italia, in its innovation department, has a number of Innovation Laboratories that host services

and application platforms to be offered to internal customers. The mediator GEi is the main chapter

output which will be offered to innovation projects and to the company’s Architecture and Engineer

Groups inside TI production projects.

The mediator GE is a centralized platform aimed to expose and manage APIs provided by an

heterogeneous plethora of services in a uniform way. It supports a variety of protocol (http, REST, SOAP,

ftp, tcp) and message payloads (XML, JSON ecc.).

Interface to Networks and Devices

Telecom Italia, as telecom operator, participates to a number of initiatives to standardize the network and

device APIs (it is member and actively contributing to W3C, OMA DM, GSMA and others), fully supporting

their adoption by the manufacturers in the next generation of connected devices, cloud edge/proxies and

network platforms.

In particular, TI is active participant in the activity of smart home architecture, device template models

and APIs for abstraction layer of sensors’ networks in HGI, with liaisons with OSGi Alliance and Broadband

Forum, and links to the ongoing initiative coordinated by the European Commission on “Smart Home

semantics”. Definition of advanced specifications and reference implementations in terms of device and

local and network APIs, device management, as well as advanced gateway (Cloud Proxy) architectures, are



the main outcomes from the “Interfaces to Networks and Devices” activity that Telecom Italia intends to

exploit.

The implementation activity could also be preparatory to the actual deployment of smart home services

at TI customers’ premises, leveraging on the software modularity of the cloud proxy GE.

In future tenders, TI will define requirements for software modularity of home gateways supporting this

enabler according to the project experience; in particular, next generation of advanced access gateways,

planned during 2016, will be equipped with this software architecture; however, while the functional

requirements will be fully coherent to the FIWARE cloud proxy, how the implementation will be actually

close to the FIWARE set up for the cloud proxy will strongly depend on use cases supported and the direct

choice of the box manufacturer).

For what concerns the CDI Generic Enabler implementation, the underlying technology is open source, as

well as the implementations on top of it jointly provided by the Partners working on such

implementation. CDI belongs to a very dynamic sector, i.e. the connected devices, it is therefore expected

that its functionalities will be used by the developer communities to push further the evolution towards

standardized solutions (i.e. html5), in conjunction with other initiatives in the field which the project

partners are getting in contact with, e.g. tizen or Firefox OS (this latter recently for TI).

Internet of Things

Telecom Italia is largely interested in the Future Internet evolution of its own current network both fixed

and mobile. There are large investments on the technological development (e.g. the introduction of

LTE/LTEa in Telecom Italia mobile network, which is currently covering more than 60% of national

population) and also extensive participations to the definition of standards for the IoT related

architectures and protocols. Especially about the latter, Telecom Italia has currently the chairmanship of

the ETSI Technical Committee M2M and is a committed member of the partnership project oneM2M

whose scope is the definition of Protocols/APIs/standard objects based on a service architecture which

allows an interworking ensuring an independent access to end-to-end services (along the lines of the

3GPP standardization body, as the global initiative for M2M standardization).

From the point of view of the Internet of Things applications Telecom Italia has been working for years on

the concepts of Smart Things. Telecom Italia began in 2002 its involvement in the ZigBee Alliance

acquiring the chairmanship of the ZigBee Telecom Services work item. Based on such background the

main outcomes from this chapter will be the contribution, inclusion and adoption of such standardised

solutions as unifying components of IoT based application and services.

In this context TI has developed the Zigbee Protocol Adapter (ZPA) Generic Enabler that implements the

ZigBee specifications: such a standard specifies how the ZigBee world of Things interacts with the IP

world, in particular with a platform through a gateway. Moreover the ZPA is based on a ZigBee Gateway

Device implementation which has been released in open source under the Apache 2 license.

By using ZPA the FIWARE platform is able to communicate with any ZigBee device independent of the

specific application profile used (home automation, smart energy, building automation, health care, etc),

that is in TI’s view an added value brought to FIWARE.

The ZPA code has been contributed to the Jemma initiative (http://ismb.github.io/jemma/) which

promotes development of energy aware systems based among the others on the ZPA module.

Data and Context Management

Many Internet services are currently based on business models that exploit massive data provided by end

users. Such data volumes are exploited e.g. in advertising or offered to 3rd parties so that they can build



innovative applications. FIWARE and its data/context outcomes can enable smarter context-aware

applications and services to be created.

As main outcomes of this chapter Telecom Italia is providing the specifications and implementation of the

Publish/Subscribe Broker and the Semantic Annotation GE. Such elements are key functionalities to

develop applications and services where management, processing and exploitation of context

information, as well as where enriching textual data (tags or text) with meaningful and external content,

is extremely valuable.


The Telecom Italia Group is a major Italian enterprise and a key European strategic ICT player. Telecom

Italia owns a considerable know how in the development of innovative service platforms leveraging

enhanced network architectures. Most of such platforms are supporting applications either in field or in

trial phase both for domestic and industrial environments.

The main customers Telecom Italia expects to reach with the FIWARE developments are companies,

public institutions (e.g. within the framework of the initiatives concerning smart cities) as well as SMEs

and developers, who can be attracted by the technology evolution and become the future customers of

the company.

The participation of Telecom Italia in FIWARE enables the possibility to provide open and standardized

solutions to different markets of interest for the Company. The support to initiatives like Smart Cities and

in the field of M2M are seen as the major vehicle to spread the benefits over a global market and

providing benefits to a wide set of citizens, through services and applications which could be made

available on large scale in the near future.

In order to reach its customers like Large Enterprises, SMEs and Public Institutions, the company works

through the business/commercial units of the Company. Direct contacts are usually managed through the

company's links between the Innovation and the Commercial units, to convey to customers the innovative

solutions that, as first step, can generate a smaller business opportunity through specific field trials. On

success, they usually turn into a larger business opportunity through an industrialization of the trial

solutions developed.

As an example, the involvement of Torino as smart city in FIWARE has been brought to the city’s

representatives in close cooperation with the Commercial functions of the Company who are the usual

contact point with the municipality. The experimental outcomes, based on an FIWARE-Lab application to

manage and expose as open the data concerning security and safety of citizens, have re-enforced the

contacts with the Municipality. The company will provide, through further experimentations which are

currently being planned, its commercial services of ultra-broadband and advanced 4G mobile connectivity

to run innovative, future internet applications.

While the channels of Business and Commercial units are the nominal contact points towards customers,

a further channel to reach potential developers and company’s customers of the future is represented by

the Joint Open Lab initiative launched by the company, which joins the efforts of Telecom Italia



Innovation initiatives with selected main Italian Universities. The JOL allow to reach a wide community of

early developers who will be involved in the development and testing of prototypes or beta services for a

broad range of applications scenarios (eHealth, service robotics, smart cities, energy, etc). The adoption of

FIWARE outcomes in their developments, along with their direct involvement in the FIWARE

developments (e.g. the Cloud Robotics platform group) extends the ways to develop innovative

applications based on project's Generic Enablers, and provide the involved people with a possibility to

value the benefits offered by FIWARE outcomes through the company’s implementations, thus

maximizing the possibility to bias them towards such solutions and enlarge the potential future customers

base.

The success of the FIWARE Acceleration initiative just started in the last months of 2014 is closely

followed by the Innovation group and management, as it provides a further channel through which the

project outcomes can be put at value, both directly (i.e. adoption of developed GEis) and indirectly (i.e.

providing advanced telecommunication capabilities, to support the experimentation of innovative

services and applications that the involved SMEs, start-ups and web entrepreneurs will develop).

From a global FIWARE platform perspective, Telecom Italia is considering too the option of providing a

own commercial version of it. However, there are aspects which need to be investigated beforehand: on

one side, the cloud technology underlying FIWARE is not the one provided by the company in its

commercial proposition (Nuvola Italiana), which means a dedicated deployment is necessary. On the

other hand, a more detailed analysis of the business linked to the exploitation of a whole FIWARE

instance is required. For this reason, the company is extremely interested to support and verify the

outcomes of the wide adoption of the platform, through FIWARE Lab, within the third phase of the FI-PPP

initiative.

While the creation of the internal versions of a FIWARE platform is already on going within the Innovation

group, its provisioning as a commercial offer through the Business/Commercial units will be subject to

further considerations. These will be performed in the FIWARE project follow up during FI-PPP Phase 3.

In any case, the main business perspectives are represented the deployment of a FIWARE platform

suitable for specific application domains, the most mature one being the support to creation of new

services for smart cities, thus involving eGovernment services, intelligent transportation systems, and

sensor-wide infrastructures (including e.g. metering). This kind of platform instance, comprised of the

enablers to manage big data in quantity and the analytics associated to them, will likely happen to be the

most attracting proposal..

To complete this section, a list of more specific exploitations of the various GEIs developed by TI in the

diferent chapters is provided below.

Application Services Ecosystem

For what concerns the Apps outcomes, the support to the integration in company’s Architecture and

Engineer Groups inside TI production projects, including the Cloud offer of Telecom Italia (Nuvola

Italiana), is the main exploitation mean for the Mediator GE implementation. It is therefore expected that

the exploitation of the GEi will not be direct (neither as a service on its own offered by the company, nor

licensing its implementation), but rather it will be embedded in the overall commercial Cloud offer by the

Company. The target of the offer includes the third parties which experimented the Mediator in joint

innovation projects.

Moreover, the Mediator GE is already used as an asset in many projects where TI collaborate with third

parties like Public Administration and Universities. Some of these projects are related to HealthCare,



SmartHome and Utilities Management where the capabilities of the Mediator are successfully used to

speed up development. In those cases the mediator GE is used mainly to centralized APIs and to mediate

Telco capabilities like SMS, Mail, Location, Map and Geofencing services. The overall platform is based on

Open Source projects and tools that have been integrated and customized with code developed internally

in TI’s innovation Labs.

Internet of Things

Telecom Italia has been actively working in the development of Intelligent Solutions focused on the

Internet of Things perspective. This is a natural exploitation field for IoT Service Enablement outcomes,

like the ZigBee Protocol Adapter.

Among others, the development of Energy Management systems both in enterprise and home

environments, Smart Metering solutions for gas and water, Smart Grid applications in collaboration with

Italian utilities and white goods manufactures leverage on the ZigBee technology and the ZPA GEi.

More in detail, Telecom Italia intends to exploit the ZBA in the developments of the Energy@Home

Consortium, a no-profit Association founded on July 2012 by Electrolux, Enel, Indesit Company and

Telecom Italia, that includes today more than 20 member companies. The mission of the Energy@home

Association is developing and promoting technologies and services for energy efficiency in smart homes,

based upon the interaction between user devices and the energy infrastructure. Its goal is to promote the

development and widespread adoption of products and services based on the interoperability and

collaboration of the appliances within the household. The FIWARE outcomes will enrich the

Energy@Home architecture at network platform level, that currently is more focused at domestic

gateway level.

Among the various initiatives of the Energy@Home Association, a network trial for the integrated

multimedia and Smart Home architecture is on-going and will turn into an innovative commercial offer on

the Italian market. Depending on the choice of the Engineering and Business units of the company, the

commercial offer will either use the developed ZPA GEi directly, or it will include an engineered version

based on the specifications of the FIWARE GEi.

Data and Context Management

The Publish/Subscribe Broker (Context Awareness Platform - CAP) and the Semantic Annotation GEis are

already integrated in a set of evolving applications and services prototypes such as TIM Social, Social

Reading, etc. The GEis are also provided to and installed in a number of other research and innovation

projects such as 4CaaSt, and CloudWave.

Interface to Networks an Devices

The I2ND outcomes allow the Company to leverage the enhanced capabilities of the devices in their offer

of commercial components and services to its customers. The competitive advantage is represented by

the advanced knowledge about those capabilities, since the time they are conceived and proposed for

standardisation. All the company’s offers of advanced home gateway, multimedia devices equipment and

mobile terminals will benefit from the outcomes of FIWARE.

In particular the cloud proxy collusion could be implemented on set top box reference designs, waiting for

the availability of hardware platforms for home gateways able to offer processing capabilities optimising

the implementation of the enabler (anyway supported by the current reference designs)

In addition to the plans for future deployment of software modularity and use of the FIWARE experience

to build up the related requirements, a number of lab activities are already ongoing in TI, to check the

actual portability of cloud proxy and other similar solutions (either developed internally or acquired from

specific software companies) on the current hardware platforms; this credibility activity will be



fundamental to fine tune the features of the future modular gateways and has been already useful to

prove the possibility of exploiting the FIWARE solution in near-to-field scenarios.


Working on sensitive data, as it was done with the experimentation performed with the City of Torino

within FIWARE Lab, and transform them into a set of open data is a potential critical aspect to be

investigated. This might imply overcoming potential barriers to manage data not only in the smart city

context, but in all contexts where personal data (even coming from sensors surrounding citizens), are

collected and exposed e.g. through a FIWARE instance.

It is expected that FIWARE and the federation of nodes across European countries, will minimise this

issue, thus ensuring the compliance with national policies and regulations.

6. France Telecom Sa

France Telecom-Orange is the first French Mobile and Internet operator. We operate mobile, fixed and

internet networks in 35 countries in the World, especially in Europe and in Africa with more than 220

millions of customers. Our dedicated entity, Orange Business Solutions provides corporate services in 220

countries with a 24/7 customer support service for data and voice services. Orange Business Services

delivers the same vertical services for its customers: transport, supply chain, health, finance, utilities...

FIWARE business model is relevant for France Telecom-Orange to support the same services in all

countries where we have to support our customers. Based on several competitive environments with

different regulation issues, a common technological foundation which could be use everywhere is a clear

competitive advantage. To be able to deliver a seamless service through all European countries as well as

in emerging countries is a big challenge where FIWARE enablers will be very useful.

In a first step, each Orange country will be able to prioritize some technological challenge to target

dedicated vertical areas and to involve its own ecosystem to speed up open innovation and to imply local

partners.

In a second step, all Orange countries will converge to a common platform to deliver the same and

seamless service for international customers.


From Orange side an ongoing activity is the compatibility of many Open Source license models which are

a clear obstacle to define what could be an optimal platform using FIWARE Generic Enablers.

Because of Orange dedicated work on OpenStack and the strong links with Cloudwatt in France, Orange

interest focus mainly on two technical chapter of FIWARE: Internet of Things and Data and Context

chapter, with a minor interest into Security chapter.

Based on internal dissemination activities which happened in 2014, some Orange countries have now a

good knowledge of FIWARE and the potential competitive advantage that it could provide. The integrated

and standardized approach for many API (FIWARE implementation of OMA NGSI for 11 Generic Enablers)

is a clear positive points especially for Orange countries which do not have the same existingproduct

environment than France.



Orange is not a software company so our commitment behnd FIWARE is more linked to a subset of

Generic Enablers which could provide a comprehensive platform depending of the targeted vertical

market but Orange has a strong interest in all IoT Generic enablers and the dedicated role that the

Gateway could play. The next step is clearly to established a link with the French initiative launch by

Orange, Datavenue19, especially with the adoption of the FIWARE NGSI API.


The following actions will take place in 2015:

- Orange FIWARE node for innovation in Africa

o Orange has already managed some open initiative in Africa (D4D Data for Development20)

to ensure services creation based on open data, some of them brought by Orange. The

improvement expected for Q4 2015 is the implementation of an Orange FIWARE Node

dedicated to several Orange African countries to provide a full platform for service

development and not only Oepn Data.

o Because some of the targeting services are potentially focusing on Smart Agriculture and

could have also further support of international entities like UN or World Bank, one the

the key advantage of FIWARE technology is the Open Source model which is required by

these kind of organization.

o 2015 work will be split into 3 phases: platform architecture definition to select some

Generic Enablers, implementation of the FIWARE node and then integration of the

FIWARE node in the 2015 D4D challenge which could involve also more than one Orange

African country.

- Orange FIWARE node in Poland

o This action is associated to a first step of Orange Smart Cities approach in Poland with a

dedicated FIWARE node instantiated in Warsaw to support the creation of a digital and

innovative ecosystem of smart city services.

o This platform will include a subset of Generic Enablers dedicated to Smart City activities

(first focus on Internet of Things and Big/Open data)

These two initiatives will also take benefits of processes defined in XiFi project to instantiate multiple

FIWARE nodes.

In addition FIWARE NGSI API implementation have been deeply analysed by operational team already

monitoring current Orange IoT platform and the decision has been taken to provide this API on top of this

existing enabler. Again this approach will strongly impact Smart Cities offer in a first step and will

influence Datavenue initiative.

All these activities are now under management of Innovation Marketing Director for Internet of Things

also leading the Datavenue initiative.

19

http://imagine.orange.com/en/datavenuechallenge 20

http://www.d4d.orange.com/fr/Accueil



7. NOKIA SOLUTIONS AND NETWORKS MANAGEMENT GMBH,

NOKIA SOLUTIONS AND NETWORKS KFT


As the world’s specialist in mobile broadband, we help our customers to enable their end users to do

more than ever before with the world’s most efficient mobile networks, the intelligence to maximize their

value and the services to make it all work together. From the first ever call on GSM, to the first call on LTE;

we operate at the forefront of each generation of mobile technology. Our global experts invent the new

capabilities our customers need in their networks. We provide the world’s most efficient mobile

networks, the intelligence to maximize the value of those networks, and the services to make it all work

together seamlessly. With an unswerving focus on quality, efficiency and reliability we help our customers

meet the mobile customers’ demands for universal content and connectivity more efficiently and

effectively. Together, we deliver the innovations in mobile technology that enable people and businesses

everywhere to do more than ever before. Mobile operators face challenges from many sides that put

their mobile network and their business model under extreme pressure. By transforming their mobile

network and business, they will turn their challenges into opportunities. Working closely with them, we

deliver the products and services that will help drive their success - today and tomorrow.


The general aim of NSN’s research departments is to provide applied research; meaning that the overall

focus of the research activities is to provide ideas for new innovative products and solutions. This includes

also innovative enhancements to existing products and solutions. In the context of FIWARE all GEs

contribute as well to the future product portfolio of NSN.

1) Identity Management GE – OneIDM GEi and DigitalSelf GEi

The Identity Management (IdM) GEis provided by NSN are encompassing a number of aspects involved

with users' access to networks, services and applications, including secure and private authentication

from users to devices, networks and services, Authorisation & Trust management, User Profile

management, Single Sign-On (SSO) to service domains and Identity Federation towards applications.

NSN’s GEis are offering the following interfaces:

- SAML (Security Assertion Markup Language)

- OAuth (Open Authorisation Protocol)

- OpenID Connect

- SCIM

- user name / password

During the project NSN has enhanced the already existing GEis by additional features. Some examples are

listed here:

- User self registration

- SCIM protocol

- Frontend for managing employees and roles for organizations

- Two factor authentication



- Integration of verifier and issuer service

More enhancements and as well detailed information on the enhancements are available from the

FIWARE roadmap of the security chapter. The IDM GEis are provided as a software as a service. They are

using physical servers in NSN premises and resources are assigned on request as described in the FIWARE

catalogue.

The additional features where facilitating the usage by the use case projects, external parties and as well

the common demo together with the project partners IBM and SAP (described below). On the other hand

they contribute NSN internally to the enhancement of the research prototypes and pre-product

development.

2) I2ND GE – VNP GEi

As anticipated virtualization became a hot topic for telecom operators and vendors, see the inception of

ETSI NFV ISG and the first deployments of networks based on software defined networking (SDN)

principles by companies like Google, and NTT. Even though NFV can be applied without SDN, the solutions

combining them provide greater value.

Virtual Network Provider (VNP) is a NetIC GE implementation that offers SDN, focusing on on-demand

connectivity provision in the transport network. It provides an abstract view of the underlying physical

network for its users hiding the technical details of networking and additionally grants features like

automatic recovery of connectivity. Using the principles of SDN it can provide a customized network view,

i.e. the virtual network, for each user (or application) and by offering on-demand connectivity it provides

the subset of the NetIC API functions.

The VNP GEi is provided as a software as a service. As it uses a physical network in NSN laboratory,

resources must be assigned for VNP testing, which is done on request as described in the FIWARE

catalogue entry for VNP.

NSN has deployed the VNP implementation in an evolved packet core (EPC) virtualization proof of

concept, which has been presented at the Mobile World Congress 2014. The "SDN in mobile network"

demo shows the extension of the mobile network on-demand: several virtual network functions (SGW,

PGW, MME) are deployed in a data center and additional transport network capacity is reserved (with

QoS guarantees) that connects the newly created network elements to the rest of the mobile operator

infrastructure. The latter functionality is provided by the VNP GEi (note that it is assumed that the mobile

operator as the client of the transport network provider has a service level agreement to receive this

additional transport network capacity, but this capacity can be used by other clients when not reserved by

the mobile operator. When the additional virtual network functions are released, the additional transport

network capacity is released as well.


1. Identity Management GE – OneIDM GEi and DigitalSelf GEi

NSN’s GEis are in use by the use case projects FIcontent, FIcontent2 and FIspace and evaluated by

different other use case projects and external companies in the context of FIWARE. The scenarios where

the GEis are implemented cover the transportation and logistics area as well as the radio and TV

broadcasting environment. For all this environments NSN’s GEis are integrated in the pilot applications by

the use case projects. Thus proving the ease of implementation and the functionality offered by the GEis.

Together with IBM and SAP, NSN implemented a joint demo facilitating the advantages of the 3 GEs,

which are:



- Privacy GE (IBM)

- Data Handling GE (SAP)

- Identity Management GE (NSN)

The demo was already presented at the EEMA conference (the European association for e-identity and

security) in conjunction with the TDL association (Trust in the Digital World).

Furthermore specific services have been developed in order to test the functionality of the GEis from NSN

and to guide developers how to integrate their services with the GEis.

The combined demo, the test services and as well the GEis are accessible from the Internet to illustrated

the features. NSN’s focus is the mobile broadband telecommunication sector where the GEis are offered

to NSN’s customers supporting the end users by easy to handle and personalized service access. Thus the

activity in FIWARE contributes to the service offerings from NSN.

2. I2ND GE – VNP GEi

The VNP GEi can be used by any user/application that requires QoS guaranteed connections (e.g. to

operate properly the application has strict bandwidth and/or latency requirements for data sent over the

network), and these connections are not needed permanently, but only on demand. The on-demand

provision of connectivity is applicable both for transport networks and networks within data centers.

For the latter case the VNP GEi works together with NSN's Cloud Application Manager (CAM) that

manages the data center resources (compute and store resources for users/applications that do not

require QoS ensured network resources). Cloud Application Manager has recently been transferred from

a research project into a product in NSN's Operation Support Systems (OSS) business line. This

cooperation enables the unified management of compute, store, and network resources in the cloud with

VNP GEi and CAM.

On the longer term it is expected that all network elements will be cloud based (telco cloud) and for

flexible deployment flexible connections are needed with the same QoS guarantees as legacy telecom

networks, NSN will use SDN principle and thus VNP in those scenarios.

NSN participates in the standardization work related to SDN and NFV: in the Open Networking Foundation

organization the NorthBound Interface WG plans to define a standard interface, which has a similar role

as the NetIC interface defined in FIWARE, the Architecture WG plans to define SDN architecture, and

Extensibility WG defines the OpenFlow protocol. Colleagues participating in the FIWARE project have

participated in ONF standardization work as well. The VNP GEi development allowed us to have hands-on

experience with the OpenFlow protocol of ONF, and allowed us to propose improvements for the

protocol and provide review comments for the architecture documents.

Additionally NSN participates in the work of other standardization organizations, where virtualization is

also a hot topic. These include (but the list is not complete): ETSI NFV ISG (defines NFV), 3GPP (EPC

virtualization, service chaining), IETF (Interface 2 the Routing System, Service Function Chaining), the

development of VNP GEi as an SDN controller provided us a useful experience for those activities.


I2ND GE – VNP GEi

The standardization of SDN, virtualization, and NFV related features for mobile networks (as the main

focus for NSN) is in early phase, and the timing when the standards will be available may delay the



exploitation of those features (for example 3GPP will start studies on ETSI NFV impact only after the June

2014 plenary).

8. Deutsche Telekom AG


Deutsche Telekom is one of the world's leading integrated telecommunications companies, with

approximately 129 million mobile customers, 36 million fixed-network lines, and more than 16 million

broadband lines. We provide fixed-network/broadband, mobile communications, Internet, and IPTV

products and services for consumers, and information and communication technology (ICT) solutions for

business and corporate customers. We are present in around 50 countries. With a staff of some 236,000

employees throughout the world, we generated revenue of EUR 58.7 billion in the 2011 financial year,

over half of it outside Germany.


- The developments in the framework of “Interfaces to Network and Devices” were used to extend

our knowledge and to help through dissemination activities towards the strategic business to

enrich the technical knowledge and to support the roadmap of the introduction of new

technologies based on 3GPP’s Evolved Packet Core.

- The internal IDM platform “Global Customer Platform” was extended by FIWARE and was

developed in the direction of a product.

Please note: Both outcomes are described deeper in a bi-lateral exploitation plan with the Commission.


- The implementations of “Interfaces to Network and Devices” were used for demonstrations and

to showcase the possibilities of new services on top of the Evolved Packet Core. The knowledge

was transferred to the business units and was used internally for the support and software

development of showcases with the real network environment. “Customer” was the business unit

responsible for network architecture and technology roll-out.

o The results are used in other ongoing R&D projects and testbed projects. Especially, the

Evolved Packet Core implementations will be offered in the XIFI project. The locally

installed Evolved Packet Core is the control plane of the networking site and testbed of

the XIFI Berlin note.

o In parallel the local physical testbed with its implementations will be used as an

evaluation platform for application and service developers of DT.

- The IDM platform “Global customer Platform” included results and became a product by the

beginning of the year. Further information can be checked out:



o

Please note: The Web-page: http://www.customer-platforms.com/ is currently under

construction and includes for the time being only contact informations.


A detailed and revised bi-lateral exploitation plan was provided to the project officer with internal and

confidential information. We have also included additional information such as the depicted leaflet in the

document for the Commission.

9. Technicolor R&D France Snc


With more than 95 years of experience in entertainment innovation, Technicolor (ex-Thomson,

www.technicolor.com) serves an international base of entertainment, software, and gaming customers.

The company is a leading provider of production, postproduction, and distribution services to content

creators and distributors. Technicolor is one of the world‘s largest film processors; one of the largest



independent manufacturers and distributors of DVDs (including Blue-ray Disc). On top of being a

―content-related- company, Technicolor also provides its customers advanced platforms such as

gateways, storage, tablets and set top boxes for home content delivery. These key components are the

obvious extensions of the internet inside the home and the enabler of most home network applications

and services (e.g. e-health, e-learning, entertainment, home automation, and gaming). Technicolor, as a

media and entertainment innovation provider focused on the production, management and delivery of

premium quality content, with customers worldwide, has a unique position in the European IT industry

landscape.

Technicolor declares that maintain its confidential exploitation plan delivered, in a confidencial

mode, in M30

10. Atos SE (Societas Europea)


Atos SE (Societas Europea) is a leader in digital services with 2013 pro forma annual revenue of € 10

billion and 86,000 employees in 66 countries. Serving a global client base, the Group provides Consulting

& Systems Integration services, Managed Services & BPO, Cloud operations, Big Data & Security solutions,

as well as transactional services through Worldline, the European leader in the payments and

transactional services industry. With its deep technology expertise and industry knowledge, the Group

works with clients across different business sectors: Defence, Health, Manufacturing, Media & Utilities,

Public Sector, Retail, Telecommunications, and Transportation.

Atos is focused on business technology that powers progress and helps organizations to create their firm

of the future. The Group is the Worldwide Information Technology Partner for the Olympic & Paralympic

Games and is listed on the Euronext Paris market. Atos operates under the brands Atos, Atos Consulting,

Atos Worldgrid, Bull, Canopy, and Worldline. For more information, visit: atos.net.

With the recent acquisition of Bull[1], Atos strengthened and deepened the portfolio in 3 key areas: Cloud,

Cyber Security and Big Data, leveraging the complementarity of distinctive Bull High Performance

Computing solutions to Atos capabilities in Systems Integration and Analytics.

Also relevant for this assignment is the fact that Bull extends the geographical coverage of Atos,

especially in Africa, with offices in 10 countries of the continent.

Additionally, Atos is backed by strong shareholders, including Siemens, which is also an innovation

partner. Siemens is the second largest shareholder in Atos - retaining a 15% stake for at least five years -

and our largest client, Siemens is also a Global Strategic business Partner. Overall, Siemens is an

important partner to address the sectors: Industry, Energy, Healthcare and Infrastructure & Cities. Within

Atos, a dedicated team - the Siemens Global Partnership team - is set up to promote and facilitate joint

initiatives, leverage all Atos capabilities, and monitor the results of the commercial partnership.

Atos Research & Innovation

[1] http://atos.net/en-us/home/investors/acquisition-of-bull.html



Atos Research & Innovation is the worldwide reference point in research for the whole Atos group. The

vision of the Atos Research & Innovation (ARI) group is mainly focused on applying the latest research

outcomes to real world situations where Atos clients need solutions that go beyond what current

products provide

This division is the research, development and innovation hub of the company and it is a key reference for

the whole Atos group. ARI’s structure includes several labs focusing on social networking, trust, security,

e-identity, knowledge & semantics, media, software engineering and cloud services, geographical

information systems, and smart object technologies.

Exploitation, Technology Transfer and Commercialization capacities, expertise and responsibilities are

often not concentrated in a single department, but rather span various horizontal and vertical units in a

large corporate such as Atos. The figure below shows typical expertise needed for the successful

execution of ETTC activities.

In some cases expertise and capacity exist within the project or within ARI, while in the other cases

assistance is needed from e.g. Global Innovation and Business Strategy (GIBS) department. Thanks to

the long history of execution of EU funded projects, ARI has established a fluid process that integrates all

elements needed for the successful exploitation, from the legal and IPR expertise, to the sale support and

marketing.

On November 18th 2014 Atos CEO Thierry Breton is presenting Atos strategy called “Digital

transformation” at European Commission ICT conference21, strategy that is applicable to all sectors and

also outlined in 2013 report22 where the role of Atos research & innovation has been also mentioned.

Atos is ideal position to lead “digital transformation” of EU sectors. The consulting and systems

integration businesses of Atos are now under one umbrella a unified €3.1bn business C&SI also integrates

Atos research & Innovation (ARI) unit that is leading FIWARE TTC process. In addition, Atos undertook a

major change by focusing its offerings on verticals. In the vast majority of digital transformation projects,

there are components of internet of things, mobility, analytics/big data, cloud, social network, cyber

security, etc. Digital transformation process, therefore, is a mix of consulting, system integration and

vertical known how.

21

http://ec.europa.eu/digit-ict/en/content/programme 22

https://atos.net/content/dam/global/documents/investor-financial-reports/atos-2013-registration-document.pdf




The Internet is changing. It is evolving in order to sustain more connected uses, in real time, and to ensure

quality of service and reliability, both for mobile and low-capacity terminals, as well as the powerful

servers that reside in a major Internet service provider’s data center.

- Atos, as a major online services operator and Cloud solutions provider, is monitoring this

evolution and even anticipates it through its participation in the Future Internet Public Private

Partnership as well as its own research and development (R&D) work on new protocols and

network designs, in order to adapt to this ever evolving environment.

- Atos is developing and investigating Big Data Management as key technology for future

customer requirements. Both internal and global customers will require more and more data.

Stores and the associated processes to manage huge amounts of information. Some projects and

initiatives are focused on HTTS (massive transaction management) and Atos Research &

Innovation, which provides high-value and technical solutions to global key customers. In

addition, Atos believes that emerging fields, like Internet of Things and Context-Aware

Computing, which necessarily involve the ability to manage lots of data, will become key fields in

the near future. The emergence of Big Data Management and new data analytics technologies,

increasing the probability of finding meaningful insights from huge amounts of data generated by

myriad applications and sensors.

For a service company like ours, future service means added-value internet-based service. There are many

platforms already available over the internet, on top of which services can be built and offered. However,

to the extent of our knowledge, no platform offers at once Cloud Computing abilities, Internet of

Services, Big Data, High Tech Media applications and support for the growing “internet of people”

possibilities, which will be a dominating scope in the coming years.

Atos main contributions to FIWARE have to do with four areas of research: Support Services (specifically

data management and storage), SaaS, IoT and Trust and Security solutions. All of them are part of the

Service offering provided by Atos at commercial level, and therefore, we expect that the outcomes of

FIWARE will help us to acquire competitive advantages in our current service portfolio, mainly in the case

of Iot and particularly within our Smart City portfolio.

Additionally, taking into account that FIWARE software components are mainly provided under name

Generic and Specific Enablers, which are basically software elements offering reusable and commonly

shared functions making it easier to develop FI-Apps in multiple sectors and application domains.

- FI-Apps are therefore composed of “software components” and constitute an evolution from

SOA-based systems, exhibiting many commonalities (e.g. service orientation) but also introduce

new and amplify existing aspects (e.g., collaborative development, unprecedented level of

heterogeneous interoperability). These applications and components are further characterized

by the adoption of critical third-party services available over the Internet.

- One of the main constraints for their ETTC is the need to collect and address multi-stakeholder

requirements. In a matter of fact, we expect that the part of our FIWARE generated income will

come from the customization, configuration and the other system integration activities, which on

the other hand constitutes the core business of Atos

In this TTC option, software components (being generic/specific enablers or parts of it) could be

integrated into some of the existing Atos assets or solutions. Another option is their release as the open

source or even multiple adaptations to various platforms. Criteria and review is done per component (see

below). So far, COMPEL component has been integrated into yourBPM solution, while other

components have also been integrated into yourKIM and yourCySEC solutions. Finally we also expect

that SLA management framework, now under development in FICORE, can be later exploited through this

option.



- Semantic app support and UDA: Semantic app support and UDA, contribute to the generation of

a solution in Atos Research and Innovation (yourKIM) which provides automated methods for

knowledge and intelligence processing and management, from data acquisition all the way to the

final application services that include decision support, visualization, etc. yourKIM is based on the

state -of of-the- art technologies, such as an ontology-guided and rule-based information

extraction approach. It also provides interfaces with the most common infrastructures and

ontology that incorporate domain-specific knowledge with concepts, vocabulary, and

relationships. yourKIM has been basis for the recent internal start up that focuses on social

network analysis.

- Security Monitoring contributes to the generation of a solution in Atos Research and Innovation

(Your CYSEC) which provides scalable data acquisition and collection of huge amounts of security

events from diverse and geographically spread nodes. In addition, it performs a distributed and

near real-time aggregation, dissemination and processing of events, which leads to a reaction

ranging from alert generation and incident notification to more automated actions. Scalability

and elasticity of correlations is embedded in the design of your CYSEC, so that integrated and

distributed engine implementation alternatives can be deployed in the cloud and adapted to a

cost effective, on-demand business model.

- YourBPM provides an intuitive environment for lightweight service composition and

consumption, allowing non-experts users to model and design their business process. YourBPM

helps these users to search and select the best service for accomplished the tasks in their

process. The target users are then domain experts (such as civil servants, administrative staff,

financial controllers,) but also software integrators and service providers/developers can be

interested in its commercialization for final customers. In many sectors, such as logistics or

finance, there are financial processes that integrate a growing set of external business services

from third party providers, such as payment services or invoicing, which have to be integrated

with the core functionalities. YourBPM can model a wide variety of internal and external services,

including Financial Services (Cash Clearing, Credit Card Validation and Payment, Order, etc.) or

Retail Services (Order, Upgrade, Trouble Ticketing, etc.).

One of the main channels for ETTC activities in ARI is through packaging of research project results into

ARI solutions and ARI assets. Any form of intangible project results (technical consulting, business

consulting, and system integration capacity) or tangible result (software components, tools, prototypes,

service suite) is a candidate to become an ARI asset. Each asset has assigned asset owner that serves as

the main contact point. The list of assets is reviewed on annual basis.

Tangible project results, such as software components or tools, can also qualify to become ARI solution.

ARI solution is a mature technical asset or set of assets. It can also use external components, either Open

Source or components where we have specific agreements with component owner, in order to

complement ARI asset and provide full end-to-end solution. These “external assets” have to fulfil the

following criteria:

- they are necessary for end-to-end solution,

- there is a written and approved (by Atos legal services) agreement with its owner or they are

open source (therefore no agreement is needed),

- there is no similar asset owned by Atos


Atos relevant presence in FI-PPP projects is due to the extreme importance that the company has given to

the development of this area. Through this presence Atos is looking for a privileged position in the Future

Internet limelight. The projects are providing Atos with a unique expertise in the area. The acquired

knowledge provides the capacity of playing with very innovative roles as FIWARE provider, FIWARE



consultant and it also gives the expertise in relevant domain such as logistic, agriculture, Smart

Awareness, environment, Smart City Services and Smart Energy.

In general, key customer segments are Infrastructure and Cities as well as industrial final users, mainly

within the domains Industry, Energy, Healthcare.

Based on the preliminary FIWARE project value proposition, Atos has segmented the business

opportunities in three main categories:

1) Opportunities for application developers/entrepreneurs: Atos as the application developer

2) Opportunities for platform service providers: Atos as the consultant and system integrator (C&SI)

3) Opportunities to host FIWARE instance on behalf of platform provider: Atos as the managed

service operator

The business model will be very different, as well as the revenue sharing models and support for each of

these roles, although the FIWARE value proposition message so far has been the same (Open service

ecosystem architecture, open APIs, generalized components freely available etc).

In regard to the technology transfer and commercialization (TTC) and Atos solution portfolio, there are

currently two main strategies within Atos:

1) Foster value creation: A customer oriented, consolidated, modular portfolio of global offerings is

the main lever to improve our top-line and to show professionalism to the market

2) Industrialize best practices: Industrialized “production” of high quality offerings, to be sold and

delivered in a repetitive manner will have strong positive impact on bottom line.

As we will see later, FI PPP TTC process is a mix of these two strategies. In this sense the main constraints

and risks identified in TTC are:

1) Research push: No buyers, lack of user involvement

2) Market pull: Risk aversion, lack of innovation

Outcomes of RTD projects that have the potential to become part of Atos portfolio are supported by

TTC units that approach Atos market and sales force, as a first step, in order to promote the adoption of

innovative solutions and emerging technologies. Based on market experts’ feedback, assets can be

moulded and prepared to be presented to Atos customers.

Prerequisite to be able to derive Portfolio from customer needs is to understand customers processes,

trends in certain industries, value adding innovation topics…Outcome is a customer oriented structured

and reusable portfolio of offerings may it be a solution component, a solution or a service.

This process within Atos is depicted in the following figure:



Atos places particular value in understanding customer processes (Process Map) and to define domains

(Domain map) where we think customer needs to spend Consulting or System Integration money to

outperform competition or at least draw level with competition. This needs to be proven in direct

customer involvements in POCs or joint Offering development (Solution Map) with customers. To make

this Offerings really standardized, reusable and fitting to the involved Partner products we need to

underpin it with the respective Architecture (Architecture map).

This process is integrated in the overall lifecycle called Solution Offering Lifecycle Development (SOLD),

a highly standardized and industrialized global process. In the offering definition step, there is now space

to introduce so called Innovative Proposal Plugins (IPP), complementing the existing portfolio with

solutions piloted in RTD projects. These IPP vary from services such as “security assessment” to

components such as “smart mobility API”.

In regard to the technology transfer and commercialization (TTC) of the specific FI PPP project results,

Atos has been considering several options:

1) Solution: TTC based on the domain specific adaptation of the platform for the client

2) Solution components: TTC based on the reuse of a technology platform components inside of

Atos (see previous chapter “identification of main projects outcomes”.

3) Service: TTC based on the consulting, implementation or operation of a FIWARE GE/Instance.

(Initial Smart City Approach)

4) Internal exploitation through internal FIWARE Lab, as well as providing FIWARE Lab to its clients

for the experimentation

In these options different channels and tools can be used, ranging from a participation in foundation to

bilateral and multilateral exploitation or commercialization agreements.



Business value of FIWARE has been already widely addressed in the exploitation reports and here we

just summarize main findings, as well as their measurability and possibility to realize in the “real”

environment.

The four options identified above (integrated FIWARE, loose components, related service and internal

use) can be also traced back to the major roles that have been identified for FI-Apps, and based the FI-

WARE model. This also establishes dependency on FIWARE partners

FIWARE based Smart City Approach

Some municipalities are already including FIWARE as the underlying platform in their Smart City tenders.

In this type of procurement, Atos has a competitive advantage due to its know-how of FIWARE, as well as

already existing applications that use FIWARE generic enablers (e.g. COSMOS, RERUM and other projects).

In the second hypothetical case, when the municipality or the contracting authority does not specify

underlying technology, Atos will offer FIWARE as the preferred option since it dramatically decreases

costs.

We consider consulting activities as a key to the successful ETTC of FIWARE and in this sense we are

investing particularly:

- Awareness and readiness through RECI (Red de Ciudades Inteligentes) and es.internet platform,

as well as other organizations such as Eurocities

- SOA oriented redesign: many of our clients are in phase of “digital transformation” and we are

trying to move their IT modernization trends towards FIWARE-like approaches

- Readiness and feasibility: this is one of the most prominent Atos Consulting services and

introducing FIWARE through this channel to the end client, with cost reduction as the key

argument, is one of the keys for ETTC success

Action Plan

Regular internal cross-department meetings are organized to spread the information about FIWARE

technology. The alignment of the PPP and our interest in FIWARE with the future vision of Atos thanks to

our close collaboration with the Scientific Community (at worldwide level, up to 200 members for all the

countries)



FIWARE Contacts Internal Responsible: Mr. Aljosa Pasic

Role Contacs Date Colaboration

CEO Thierry Breton and

Hubert Tardieu

9-Dec-14 Sherpa meeting between ATOS, TEF and ENG in Madrid within the next 3 weeks.

Big Data PPP: It will not develop a platform by itself, rather use existing

technologies. ATOS can ensure that FIWARE technologies get a fair chance to

compete in the big data and perhaps are even favoured because of the principles

FIWARE stands for (openness, third part innovation, I)

Info-point: ATOS runs the Spanish nodes of the newly selected EIT KIC on

eHealth called InnoLife. An opportunity for a vertical application of FIWARE GEs

and SEs.

Close relation of ATOS and SIEMENS: Further to the meeting of Thierry Breton

and Roland Busch on 19 December 2014, at which FIWARE as on the agenda, IT Challengues Ramon van Knippenberg

and Mike Smith

8-Jan-15 ATOS IT Challenge: from the today selected 15 teams, easily 5-7 could fully build

the project on FIWARE. Atos team to evaluate which, train the coaches and gives

support to the teams.

Smart City Offer

Leader

Alber Scheubers nov-14 Introduce FI WARE into our Smart City Portfolio

Telefonica Account Matteo Sarti jul-14 Support to telefonica in the new solutions based on FIWARE

Spain Public and

Health Market

Leader

Tomas Mallo nov-14 Include FIWARE in the new commercila bids as value added

Spain Solutions

Manager

Keith Alexander dec-14 Exploring new solutions integrating FI WARE and FISPACE components

Spain Solutions

Architecture Leader

Fco Jose Ruiz nov-14 Easy to integrate into the Atos solutions

Looking at the future, all the developments of Atos are fully aligned with the business strategy already

defined by Atos Research & Innovation as contributions to business development activities of the

company (that is what we call Business Assets)

In the first part of this report we have explored the option of TTC of the platform as a whole. This path

has many assumptions and alternatives that can lead to different decision taking. A number of sub-

services can be defined for each phase of platform lifecycle, as depicted below.

At this stage Atos TTC team has already done a number of “Discovery workshops” where internal sales

people are informed about FIWARE a project results.

FIWARE Awareness & Readiness (A&R) Workshop

� Perform “Discovery Workshop”:

• Conduct FIWARE Maturity Assessment

• Evaluate Results

• Identify pain points

• Define A&R goals: People, Opportunity, Actions etc

� Prepare for FIWARE readiness:

• Collect customer Goals and Rules

• Analyze Policy and Compliance issues

• Connect Current IT architecture to Strategic Goals

• Perform FIWARE impact analysis and define initial roadmap

• Analyze ROI

• Establish Governance

• Establish FIWARE competence team

� Collect Requirements

� Determine proof of concept or project scope

We are now preparing a number of A&R workshops (see slide below) for the selected Smart Cities (attach

table).



FIWARE ContactsExternal Responsible: Mr. Aljosa Pasic

Client Collaboration

Smart City Madrid (Spain) COSMOS Project supports the on-going creation of IoT applications which utilize data and services

from many different (heterogeneous) device platforms locations and environments.

New decentralized management mechanisms allow for efficient exploitation of the underlying

devices overcoming the inefficiencies of centralized approaches when dealing with a huge number of

devices.

Tarragona (Spain) RERUM Project Indoor safety: IoT data (temperature, lights etc) is privacy sensitive and needs

protection

Outdoor safety: IoT data (pollution , Co2 level etc) can be manipulated

Chemnitz

(Germany)

Zero Emission communal carpool setup.For supporting a Zero Emission carpool service for

communal use Atos can contribute in the setup for the IT needed to operate such a pool. Depending

on the user group and the intended use of the ZEM there are different layers needed to complete the

full setup for implementing such a pool in communities. As we see ZEM pools as important part of

the intra city transport modalities it is in the main focus of Atos.

Atos is already doing commercial actions with respect to customers that could acquire FIWARE

technologies and we have used the concept of Smart Cities as landscape for initial deployments of the

technology. This will depend on the initial success, but being Atos a multinational company, the results of

the initial trials in Spanish cities, will be immediately used in other Atos markets.


For Atos CEO Thierry Breton, a recurring concern is controlling data flows: there is a strong demand in the

market for ensuring that cloud data flows can be contained to Europe; data should not flow through

territories that don't respect EU legislation and EU policy principles. Mr. Breton proposes the creation a

"Schengen for data", he would recommend that a new agreement enable the protection of European

companies' data by basing it in European data centres, support the economy and create jobs, while giving

users all the freedoms they want from the Internet.

Following that, SAP and Atos, both members of the European Cloud Partnership, are working with the

European Union to bring in new standards for web-based programmes and data storage in an effort to

tackle growing surveillance fears following ongoing NSA revelations. This would address the risk of

inadvertently breaking laws in one EU country where the standards differ. The proposals, which have the

backing of EU Digital Agenda Commissioner Neelie Kroes, are part of a pan-European effort to develop

new cloud standards that cover all participating nations, which will tackle inconsistencies and

incongruities between existing national standards.

A new security labelling system could spur cloud adoption and give European providers like SAP and Atos

a significant advantage.

11. Engineering - Ingegneria Informatica Spa

Organization Profile – E-IIS

Engineering (www.eng.it) is a global player, being one of the top 10 European companies and Italy's

largest IT system integrator. The Engineering Group is leader in the provision of complete integrated

services throughout the software value chain: design, development, outsourcing services, products and

proprietary vertical solutions, IT and strategy consultancy, and recently infrastructure and innovative

outsourcing services through the in-house Cloud Computing infrastructure – these tailored to the

business models of our clients in all markets. E-IIS is present throughout Italy with about 7,000 employees

and 43 branch offices, in addition to a direct commercial presence in Belgium, in Latin America (Brazil and

Argentina) and in the United States (Delaware). The Group has a global production capacity in more than



50 different countries, managing IT initiatives linked to the development of projects in the industrial and

telecommunications sectors. E-IIS’s organisational model is diversified according to various geographical

areas, but each country model shares competencies, synergies and approaches with the parent company,

thus providing a multinational vision to the Group. At present, E-IIS strategy foresees the

internationalisation of its business activities, through partnerships with large Italian and overseas

organisations and through targeted acquisitions in emerging countries with high growth rates, such as

Brazil and Latin America. In the EU, E-IIS is a consolidated supplier of IT services to main EU institutions

with its subsidiary Engineering International Belgium, located in Brussels.

The holding company, Engineering Ingegneria Informatica S.p.A., has been listed on the Milan Stock

Exchange since December 2000 where 67% of the shares are held by company founders. In 2013 the total

operating revenues of the Group was 822.2 million Euros. The group has traditionally grown at a higher-

than-average market rate since 1980, thanks to its dual strategy that rewards the capacity of internal

growth and a policy of acquisitions in emerging business lines and vertical markets. The Engineering

Group (13 companies specialised according to market segment or line of business) has solid vertical

business skills and across the board vision of technology and solutions, operating through business units:

Finance, Public Administration and Healthcare, Industry, Services and Utilities and Telco & Media, and

Training Services. The Group offering is complemented by the following competence centres operating

across all vertical markets: ERP, Enterprise Content Management, Automation and Controls, Business

Intelligence, Open Source, and Big Data. The business units are supported by 250 highly specialized

transversal skills centres, and by its Central Department for Research and Innovation, having a double

objective of promoting the role of software research at international level, as well as, bringing the

innovation to the business units productive cycles. E-IIS is present in the IT outsourcing market with a

network of 6 data centres, all located in Italy, which adopt advanced technologies to ensure high quality

and security services.

Facts supporting the FIWARE exploitation strategy

FIWARE is a core element in the innovation strategy of the company. In fact the E-IIS CEO, Ing. Paolo

Pandozy, not only wants to be kept constantly aware on the initiative progresses, but also provides

continuous strategic inputs for the successful adoption of FIWARE technologies. Together with the CEOs

of AtoS, Orange and Telefonica he is directly involved in the definition and establishment of a legal entity

for the sustainability of the FIWARE initiative after the end of the FI-PPP programme.

E-IIS, accompanied by Mr. Mario Campolargo, met Italian National authorities for the inclusion of FIWARE

in the National Digital Agenda. This activity is still ongoing. Such activity is also on-going with several

Regional authorities where this fits (e.g. the introduction of FIWARE in the regional research and

innovation programmes).

E-IIS is involved in the FI-PPP since its initial planning, i.e. before it was formally launched, as the company

was one of those consulted by the European Commission about the need of such an initiative.

E-IIS is present in the FI-PPP continuously since its Phase 1. Currently the company is participating in 11

running FI-PPP projects which embraces all the project typologies being involved in the core platform, in

some use case projects, in some accelerators, and finally in some supporting actions. The above makes

the organisation more present even if it does not share a large budget. Such large participation is due to

the company strategy to be a player in the definition on how 2020 ICT systems will look like and how they

will be implemented.



FIWARE technologies will be part of the complete re-engineering of the company ICT solutions for the

Health Care sector. It is important to mention here that the company shares about the 80% the Italian

market of the Health care legacy systems.

Since September 2014 E-IIS is running an industrial instance of FIWARE Lab called FIWARE ENG Lab. It is

accessible at fiware.eng.it. Such instance, although not officially launched even if part of several

presentations, is currently in pre-commercial mode and hosts not only trails that E-IIS developed, and is

further enhancing, under the auspices of the FIWARE initiative, but also internal commercial projects.

FIWARE relevance in your current business model

As clear from above, FIWARE plays a relevant role in the E-IIS business strategy. Recalling the main

objective of the project which focuses on “a core platform for the Future Internet by providing a

framework for the development of smart applications” and to make this platform “the reference point for

the development of future internet application.”This offers a leverage point to the E-IIS business in any of

the company concerned vertical markets. All the market sectors where E-IIS is currently involved in are

beginning to understand and appreciate the added value derived from building new and innovative

applications based on Future Internet technologies. In this respect, to keep its current customers and

acquire new ones therefore consolidating in this way the leadership, E-IIS wants to enhance its driving

position of this innovation process and in turn by offering new sets of technologies, expertise and know-

how. In this way, E-IIS is also able to pave the way to raise awareness of actual and future customers on

the added value provided by the Future Internet. Finally, being E-IIS a multinational company, the

possibility to enrich its CV with new competencies as those derived from FIWARE is definitely an added

value to becoming a stronger multinational player.

Given the situation described above, the Generic Enablers Open Specifications, their reference

implementations, the Development Community Environment (especially the myForge, the eLearning

platform – now implementing the FIWARE Academy - and Catalogue, not only for the tools, but also for

the knowledge built during their development and operation) and the Testbed are all assets that, for a

Business Integrator like ENG, are key for many aspects. A not exhaustive list of these aspects is: new

technologies to be used to make company’s solutions more effective and innovative, new competencies

to offer to company’s customers but also internally to improve services and assets for a more efficient

and effective way of working, new ideas and knowledge to investigate potential markets and, last but not

least, a greater competitiveness in the open source market place where E-IIS is particularly active. FIWARE

will not have a one shot impact on E-IIS business as the company offering is mainly consultancies and

know-how. Most of the markets addressed by the company are not accustomed to sudden and radical

innovations (e.g. Public Administrations), this means that one shot all the innovations provided by

FIWARE cannot be offered. E-IIS will perform a smooth yet energetic knowledge transfer from the R&D

Division to the Business Divisions which will use this new knowledge in the new bids according to the

ability of the customers to welcome innovation in their solutions.

Last but not least, worth mentioning, E-IIS is a core partner of the network of EIT Labs

(http://eit.ictlabs.eu) in Trento which “is the EIT’s Knowledge and Innovation Community with a focus on

future Information and Communication Society.” The mission of this Lab is to boost innovation in Europe

and this initiative is another important opportunity E-IIS will use to propose and reuse the FIWARE results.



Identification of main project outcomes of interest

E-IIS is directly involvement in the Applications Services Ecosystem Chapter where it developed the GE

Open Specification for the SLA Management. The aspects concerning the SLA are cross cutting domains

and are more and more recognised as critical. E-IIS intends to propose this as a complete solution for the

SLA Management lifecycle that can be sold in each of its market sectors especially those oriented to the

offering of service based solutions (e.g. Cloud). Any other GE Open Specification will be potentially

exploited in ENG. In this respect, particular attention is paid to the results of the Cloud Chapter as the

company in the last year has been pushing a new offer on cloud (CLOE) and the results coming from Cloud

Chapter could be a means to make this offer innovative and appealing. The main outcome in this respect

will be the realization of deployment patterns that ENG intends to propose as a basic foundation for its

IaaS, PaaS and SaaS solutions. ENG is also involved in the realisation and management of the FIWARE

Testbed, thus allowing the acquiring of a deep knowledge on how to design, build, maintain, and operate

a FIWARE Lab instance. The results coming from this experience, in addition to the exploitation of the

Testbed itself for our internal projects is also something that will be reused in the company Data Centres

Network.

Concerning the Tools Chapters, this is also an important one. The Engineering Group is becoming ever

more a multinational group, thus virtual teams are now the default and it is becoming mandatory to have

more innovative development and collaborative environments and methods enabling more effective and

efficient shared daily work. FI-CoDE (the name of the main Tools Chapter outcome) will be proposed as a

reference development and collaboration environment for the E-IIS development factories spread around

Europe.

How are you going to exploit the project results in distinct environments?

The strategy Engineering will use to stimulate FIWARE’s potential stakeholders will take full advantage of

the position of the company in the Cloud and XaaS market, as well as, in various OS communities.

Primarily, users/developers are within the Group itself, usage and acceptance validation tests will be

performed within the group in order to assess these results as valid and worthy of being offered as

solutions to the market. In this respect, within the Engineering Group, project results will be published in

the Engage community, Engineering’s social network where all the ideas, best practices, innovations are

shared, discussed and improved. Dedicated workshops (f2f and virtual) are organized to present demo

and tutorial on the above mentioned outcomes. For these kind of dissemination aspects, a proper use of

the FIWARE Academy can make the difference in terms of audience reached, training cost reduction and

time optimization. Other important channels Engineering will use to exploit its results and reach potential

users are the Open Source communities where the Group is particularly active, both as provider of the

Business Intelligence Suite Open Source (SpagoBI part of the SpagoWorld suite – www.spagoworld.org)

and as a member; these are: Eclipse and OW2 (here E-IIS is in the governing board). Eclipse and

FusionForge communities already welcomed and accepted the extensions done in FIWARE (FusionForge

Connector for Mylyn) to their existing components.

The way Engineering will transfer the FIWARE results to the market is strictly related to the Engineering

core business and innovation models. The plan is to exploit the GE Open Specifications realised as well as

their reference implementations and instances through the company FIWARE ENG Lab instance. In



particular GE Open Specifications will be used to advance the company offering in terms of new and

innovative architectural solutions and services design to play the role of system integrator able to fully

manage Future Internet technologies. It is also worth to mention that being OS GE implementations could

be suited according to specific customer needs time to time.

In general, E-IIS will adopt an open innovation/technology transfer strategy. According to this, innovation

will not be a closed process within the same organisation, but will benefit from innovation deriving from

other organisation, and will impact at the same time the innovation capacity of other organisations. In the

case of FIWARE, the results of the project will become exploitable assets for the company as a whole, and

also for all the communities Engineering participates to, this resulting in more innovation flow towards

the company itself. This open approach to technology transfer has always been at the heart of the

company capacity to innovate its business, since its first experiments with open source software in the

late 90s.

Which customers do we want to serve?

Primarily, developers within the Group itself: usage and acceptance tests of the specification and

prototyping will be performed within the Group, in order to assess the quality and the validity of results

as solutions ready to the market. In this respect, within the Engineering Group, project results will be

published in the Engage community, being the Engineering Group social network where all the ideas, best

practices, and innovations are shared, discussed and improved.

Which channels will be used to reach the various customer segments?

Dedicated workshops (f2f and virtual) will be organized to present demos and tutorials on main FIWARE

outcomes. This dissemination activity will be complemented by the contents available from the FIWARE

Catalogue and the FIWARE Academy platform. Other important channels Engineering will use to exploit

its results and reach potential users are the Open Source communities where the Group is particularly

active, both as provider of the Business Intelligence Suite Open Source (SpagoBI part of the SpagoWorld

suite – www.spagoworld.org) and as a member (e.g. Eclipse and OW2). In this respect, Eclipse and

FusionForge communities have already been contacted to present the extensions done in FIWARE to their

components and these extensions have been accepted and committed in FusionForge software

repositories and welcomed by Eclipse.

Which benefits are the participants going to take to the market thanks to FIWARE?

The main benefits E-IIS is expecting to bring to the market is the increased capabilities and the reduce

time-to-market thanks to the adoption of the FIWARE core platform and the use of specifications and GEIs

through the FIWARE ENG Lab instance.

How are the benefits going to be sold?

The adoption of a cloud-based platform, as an IT layer for delivering services will improve the efficiency of

the E-IIS Data Centres Network. It has been estimated that reducing the management operation of about



50% (mainly due to savings in personnel effort) the centres will reduce their costs of about 30%. In the

case of Engineering, it is an average of 2M€/year. Aside from this efficiency aspect, the Company is

expected to propose renew of contracts and product development during the next 5 years. In such

renewal phase, new functionalities and new opportunities given by the FIWARE GEIs ecosystem will be

exploited. Innovation in the offer proposition will serve to ensure the maintenance of the current

customers and to increase the market presence by 5 - 15%, being some 40-120M€ based on 2013

revenues.

How will the sales process work?

Early results from the project are continuously released through the agile process in place in FIWARE. In

2014 an internal validation phase is started to ensure the acceptance by technicians (developers and IT

operators) and marketing personnel. This phase is very critical since the social and psychological aspects

of adopting a new, potentially disruptive technology, may hinder its wider adoption in the E-IIS target

market. In 2015, as said in previous sections, through the more finalised versions of the GE specifications

and instances, the company will start to include the new options into its market portfolio.

Globalisation of the exploitation plan

Globalisation of the solution is key for a multinational group such as E-IIS. E-IIS will promote collaboration

and FIWARE adoption also in Middle East, US, and Latin America, with a particular concern to Brazil, to

allow the homogenisation of the portfolio throughout the group.

How will Engineering make money from FIWARE Platform?

E-IIS Business perspectives will leverage on service development and IT operation offering. In this sense,

the main sources of money from FIWARE will be from:

- Internal savings and efficiency of development and operation process, then in ensuring the

maintenance and increase of new innovative services, certainly the main source

- Increase the offering of the company Data Centres Network, from pure hosting to also IaaS and

PaaS offering.

12. Alcatel-Lucent Deutschland AG & Alcatel-Lucent Italia S.P.A.


Alcatel-Lucent is the trusted transformation partner of service providers, enterprises, strategic industries

(such as energy, healthcare, transportation, and defense), and governments worldwide, providing

solutions to deliver voice, data and video communication services to end-users. As a leader in fixed,

mobile and converged broadband networking, IP and optics technologies, applications and services,

Alcatel-Lucent leverages the unrivalled technical and scientific expertise of Bell Labs, one of the largest

innovation powerhouses in the communications industry.



Alcatel-Lucent Optics Division (represented by Alcatel-Lucent Italia S.P.A.) is achieving the transformation

of optical transport from legacy technology to packet, supporting a broad range of services and

applications such as triple play, Gigabit Ethernet connectivity, and mobile backhauling and delivering

products that match customers’ needs in the fixed, mobile, submarine and vertical markets. Commercial

products include transport service switching, WDM transport solutions, optical cross-connects and a

management suite covering transport switching, optical and microwave radio transmission. The optics

division R&D in Italy can leverage the capabilities of a global network infrastructure manufacturer as well,

having a good experience in national and European research frameworks. Recent FP6/FP7 involvement

related to FIWARE includes GEYSERS, ETICS, ECONET and ONELAB2.

Alcatel-Lucent Bell Labs have one of their global research centers in Stuttgart, providing innovative

technologies in the fields of optical networks, wireless systems, networks and networking, as well as

service infrastructures. Bell Labs in Germany can leverage the experience and capabilities of a global

network infrastructure manufacturer, and have a long year experience in national and European research

frameworks. Recent FP7 involvements related to FIWARE include, amongst others, SAIL, 4WARD, and

STRONGEST.


Within the chapter 'Interface to Networks and Devices', Alcatel-Lucent was one of the key drivers for the

definition of the ‘Network Information and Control’ task. The related API mediates the communication

between the higher stratum of the FIWARE platform, like cloud and apps, and the elements of the

underlying networks. To exploit the API capabilities, two NetIC Network functional blocks for Network

Information and for Network Control have been developed which can be used to exemplarily connect

elements of an underlying network with higher layer applications or other FIWARE functions.

More specifically, Bell Labs (ALU-D) research work in FIWARE focused on the design and development of

network information solution for carrier-grade open networking interfaces. The key objective of Bell Labs

in FIWARE was to contribute to the definition and realization of a new, efficient Internet platform being

easily customizable for the needs of e.g. cloud computing or other new and network-demanding services.

To realize this, Bell Labs have developed and provided the Generic Enabler Instantiation “Altoclient”

which allows applications to retrieve network information from an ALTO server. Furthermore, Bell Labs

actively contributed to disseminate the project's scientific results in the research community, and it is also

committed to foster potential commercialization. Corresponding inputs and requirements have been fed

back into the FIWARE project.

Alcatel-Lucent Optics Business Division (represented by Alcatel-Lucent Italia S.P.A.) contributed to the task

'Interface to open networking entities' being part FIWARE chapter 'Interfaces to Networks and Devices'.

Alcatel-Lucent Optics Business Division worked on the integration of a standard telecommunication node

(exemplarily, a commercial optical nodes belonging to Alcatel-Lucent 1850 TSS family was chosen) as a

basis to develop and demonstrate a control interface between a cloud mediation platform and the optical

node. This task showed two results: First, a significant experience was achieved in developing an

adaptation layer between FIWARE cloud framework and the node management system using standard

TL1 interface, which was identified to be very important to start managing virtualized telecommunication

resources. Second, this “proof of concept” can be considered as an actual example how a “legacy

network” can migrate to a virtualized platform, providing an evolutionary path towards the Software

Defined Networking (SDN) approach.

Exploitation of project results by Alcatel-Lucent in distinct environments

Alcatel-Lucent expects synergies with usage areas of FIWARE (vertical projects) concerning the

exploitation of existing vertical private solutions and enablers like Infrastructure as a Service (IaaS), which

so far are mostly used for intranets only, but could be applicable to the Internet as a whole as well. The

position of Alcatel-Lucent in major standardization fora will further help to foster standardization and



industrialization of solutions according to the FIWARE approach and help to bring them faster and more

effectively into the market.

Specifically, ALU expects to use the project‘s results for the validation and then exploitation of

commercial platforms for transport switching and optical transmission. This is complemented by Bell Labs

research that will provide input for the definition of potential new products satisfying upcoming demands

for flexibly configurable networks. Corresponding networking concepts like Software Defined Networking

(SDN) of Network Function Virtualization (NFV) are seen as key for an efficient and flexible Future Internet

platform, enabling cloud computing and other new services.

To enable and further promote interaction of new applications and services with the underlying networks,

Alcatel-Lucent distributes the source code as open source software to interested parties under a BSD type

license (for details see ‘Terms and Conditions’ in FIWARE Catalogue entry of ‘Altoclient’). The source code

and all relevant documentation can be found in the FIWARE catalogue

(http://catalogue.FIWARE.org/enablers/network-information-and-control-altoclient).

Redistribution and use of the ‘Altoclient’ software in source and binary forms, with or without

modification, are permitted provided that the following conditions are met:

- Redistributions of source code must retain the given copyright notice, this list of conditions and

the given disclaimer.

- Redistributions in binary form must reproduce the given copyright notice, this list of conditions

and the given disclaimer in the documentation and/or other materials provided with the

distribution.

- Furthermore to enable management of logical abstract network resources as required by FIWARE

ecosystem irrespective of the underlying actual physical networks, Alcatel-Lucent Optics Business

Division is prepared to provide the source code of its “VNEIC” Generic Enabler Instantiation (GEi)

to interested parties as follows.

- For experimentation and testing within the scope of the FI-PPP, partners can use the “VNEIC” GEi

under the conditions established in the FI-PPP Collaboration Agreement or, if applicable, the

FIWARE Consortium Agreement;

- Partners within FIWARE-LAB (Open Innovation Lab) can do development, testing and

experimentation of “VNEIC” GEi under the conditions established in the "FIWARE Open

Innovation Lab: Use Terms and Conditions”.

- To any other party, the “VNEIC” GEi software will be made available under fair and reasonable

terms, following a written request by the license seeking party to Alcatel Lucent Italia SPA and a

written agreement specifying such fair and reasonable terms, to be agreed between Alcatel

Lucent Italia SPA and the license seeking party.

- For FI-PPP and FIWARE-LAB collaboration partners, the “VNEIC” GEi software is provided through

the FIWARE catalogue and the related Forge file repository; any other interested party may

receive the software directly from Alcatel Lucent Italia SPA subsequent to the conclusion of the

aforementioned license agreement.

The innovations and revolutions on Future Internet are of interest for all types of end users, providers and

over-the-top actors. Taking into account the relevance of the Generic Enablers introduced by FIWARE in

the area of, e.g., IoT, QoS and Cloud, as a first selection in the area of B2B customers, we can identify the

public sector and strategic industries within the smart city sector. These market players are constantly

searching for flexible, secure and reliable Internet based infrastructures. Another promising sector

comprise over-the-top provisioning of HD-multimedia streaming and content, which require flexible and

reliable provision of connectivity with dedicated Quality of Service (QoS).



We will continue to use the existing channels to reach our customers, but emerging new tools and

opportunities provided by the FIWARE platform will be explored accordingly, too. Furthermore, new B2B

models are likely to emerge among existing and new actors.

We expect that the FIWARE dissemination and exploitation shall continue to be global with all interested

partners after the project will have ended. This will strengthen the position of FIWARE proponents and

FIWARE compliant products on the market compared with solutions which have to start from the scratch.

13. Siemens AG


Siemens AG (headquartered in Berlin and Munich) is a global powerhouse in electronics and electrical

engineering. Operating in the fields of industry, energy and healthcare as well as providing infrastructure

solutions, primarily for cities and metropolitan areas, Siemens holds leading market positions in all its

business areas. The company has roughly 362,000 employees – of which 118,000 or 33% are based in

Germany – working to develop and manufacture products, design and install complex systems and

projects, and tailor a wide range of solutions for individual requirements. For almost 170 years, Siemens

stands for technological excellence, innovation, quality, reliability and internationality. In fiscal year 2013,

Siemens had revenue with business in more than 200 countries of €75.9 billion. Innovation is Siemens’

most important growth and productivity driver. In fiscal year 2013, the company invested €4.3 billion –

5.6 percent of its total revenue – in research and development (R&D) to stay at the forefront of

technological progress. Today the company employs some 29,800 researchers and developers at 229 R&D

locations worldwide, who work on innovations that secure existing business and open up new markets.

Around 17,000 of them are software engineers or researchers with a strong expertise in software

development. The degree of innovation and the market success is significantly driven by software, being

an inherent element of most of our products. This makes Siemens one of the world´s largest software

houses. Apart from that Siemens is strongly engaging in sustainable solutions: In fiscal year 2013,

Siemens’ revenue from its Environmental Portfolio represented €32.3 billion and well over 40% of total

revenue comprising products and solutions that contribute directly to environmental protection and

climate change mitigation. Collaborations are an indispensable mean of developing strategically

important technologies. By discussing, sharing, and implementing ideas with scientists from outside the

company, Siemens researchers keep abreast of the latest findings resulting from fundamental and applied

research all over the world.

With over 6,900 employees worldwide, Corporate Technology (CT) plays a key role in R&D at Siemens.

Corporate Technology works closely with the R&D teams in the Siemens´ Sectors and Divisions. Corporate

Technology is networked to facilitate efficient collaboration between its various sites around the world

and with the rest of the Company. Its principal research operations are in close proximity to worldwide

business activities and technology hotspots: Germany, the U.S., Austria, Russia, India, China, Japan and

Singapore are among the most important sites. Establishing own research centers is combined with an

intensive cooperation with top universities. This allows responding quickly and precisely to the demands

of the customers and to provide solutions that meet local needs. The CT organization provides expertise

regarding strategically important areas to ensure the company’s technological future, and to acquire

patent rights that safeguard the company’s business operations. Against the background of megatrends

such as climate change, urbanization, globalization, and demographic change, CT focuses on innovations

that have the potential to change the rules of the game over the long term in business areas that are of

interest to Siemens.




The main project outcome of Siemens in FIWARE are the three Generic Enablers Media-enhanced Query

Broker (MeQB), Compressed Domain Video Analysis CDVA), and Metadata Preprocessing (MDPP) in the

Data/Context Management Chapter. The Query Broker GE is planned to be used for (semantic) search in

medical databases, surveillance archives, and other media storage systems. The Compressed Domain

Video Analysis GE will help to automatically analyze massively parallel media streams or huge storage

systems. Finally, the Metadata Preprocessing GE is planned to be used as a mediator between different,

formerly incompatible, metadata processing devices and systems and as a metadata client prior to

storage.

Furthermore, standardization results were achieved, mainly the liaison of ISO/IEC MPEG and ONVIF on

Surveillance Application Format (SAF), which led to a new ONVIF specification on Export Format.


Major exploitation of FIWARE project results is seen in the surveillance domain. Several FIWARE GEs are

applicable here. Most naturally, the Compressed Domain Video Analysis GE can analyze the video streams

of a large number of cameras in a video surveillance installation. Metadata sent by the cameras often are

proprietary or not in the target format for the storage system. The Metadata Preprocessing GE converts

the different formats, assuring compatibility of the information and interoperability between the systems

and components. Finally, the Query Broker GE offers a unified access for querying surveillance archives

with heterogeneous query formats and search paradigms. Similarly, the Query Broker GE offers unified

querying of heterogeneous databases also in the healthcare domain, where information of different kind

(personal patient data, image data and related annotations, treatment metadata, etc.) is distributed over

several systems but needs to be aggregated and combined to increase the value of the extracted

semantic information.

In addition to the direct usage of Siemens GE implementation, also FIWARE-LAB offers extended

opportunities for exploitation of the project results. A cloud-installation of Siemens’ and also FIWARE

partners’ Generic Enablers allows offering the dedicated functionality as a service. For instance, the

Compressed Domain Video Analysis GE can be used to offer analytics functionality in a “surveillance as a

service” environment. Similarly, the FIWARE-LAB installation of the Metadata Preprocessing GE will allow

offering a cloud service for metadata processing with zero installation effort, and the Media-enhanced

Query Broker GE will enable offering a service to quickly add new application features by integration of

novel data sources into existing search / query including the option to enrich it by linked open data (LOD)

cloud data (e.g., map info).

For external usage by third parties, the functionalities covered by the implementation of Siemens Generic

Enablers are provided “as a Service” through instances in FIWARE-LAB listed in section “External instance”

under the “Instances” tab of the FIWARE Catalogue. The service is provided free of charge but without

support.

In general, key customer segments are industrial final users, mainly within the domains Industry, Energy,

Healthcare as well as Infrastructure and Cities. Direct users are Siemens business units which work in

these domains, e.g., the Building Technology division in the Infrastructure&Cities domain.

Several instruments are used to reach the various stakeholders in Siemens. Regular internal cross-

department meetings ("Future Internet Jour Fix") of key researches are organized to spread the

information about FIWARE technology. Second, half-yearly meetings with key persons in the business

units are organized ("Future Internet Community Meetings"). Third, direct contact to responsible

innovation and product managers is made to discuss the inclusion of FIWARE technology in domain-

specific solutions. For example, innovation management and R&D management of Siemens Building

Technology business unit is involved in the technology development for the Metadata Preprocessing GE

and the Compressed Domain Video Analysis GE.



In order to reach external customers and other interested parties, FIWARE-LAB will serve as a marketing

instrument for promotion and promulgation of the functionality provided by the Generic Enablers. The

direct addressing of external stakeholders is in line with Siemens Open Innovation strategy.

The main benefits from FIWARE for Siemens will be in the area of data and context management. The

respective technology for metadata processing, query management, video analytics, stream processing,

big data processing, etc. will help improve the technology foundation for solutions in this area. The

openness of the solutions (including open interfaces) plays an important role here, which is further

supported by openness of FIWARE-LAB mainly due to the fact that the functionality of many Generic

Enablers (including the Siemens GEs) are offered in FIWARE-LAB with no license fees. Siemens will in

particular benefit from real world feedback provided by the users of the Siemens GEs in the FIWARE-LAB

to further improve the GEs and to identify potential additional market opportunities.

FIWARE results are planned to bring enhancements to Siemens products, solutions, and services.

Potentially, FIWARE technology will allow making new offerings to the customers. Presentations and

demonstrations leveraging practical results from GE usage in the Use Case projects as well as the usage of

the FIWARE Platform in the test bed will be prepared to market FIWARE results to Siemens business units.

Again, the openness of the API will be a key differentiator to proprietary platforms and components.

Sales are planned as a two-tier process. In a first step, FIWARE technology will be transferred from the

Research and Technology Center to Siemens business units, which will in a second step integrate suitable

components in their offerings. As described above, links to relevant business units have been established.

Therefore, Siemens Corporate Technology is actively providing information about FIWARE technology

inside the globally organized Research and Technology Center (RTC) and also is promoting results and

benefits to the researchers and developers in the Business Units all over the world.

The results from FIWARE are planned to be used in Siemens Solutions and Services, especially in the

Infrastructure&Cities as well as the Healthcare sector. Profitable revenue is planned to be made from

products and solutions that are enhanced with FIWARE technology.

For example, it is planned to use the Compressed Domain Video Analysis GE for massively parallel

surveillance installations due to the unprecedented low computational complexity of this component.

Along the same lines, the Metadata Preprocessing GE is planned to be used in such surveillance

installations for integration and preparation of metadata generated by, e.g., smart cameras for

subsequent indexing of video archives.

The persons within the organization responsible for the exploitation of FIWARE results are Dr. Andreas

Hutter (Head of RG Video Analytics Germany) and Peter Amon (Senior Research Scientist).


No specific policy issues and barriers are currently seen.

14. Intel Research an Innovation Ireland Limited




Intel Corporation is the world’s largest semiconductor manufacturer, and develops advanced digital

technology platforms for the computing and communications industries. More than 6,000 researchers

and scientists are engaged in the Intel research and development program, including over 1500

employees within Intel Labs Europe. The Ireland Innovation Open Lab hosts most of the European

Framework research carried out by Intel in Ireland. It is Intel's fourth largest site worldwide, and the

largest outside the United States. The Ireland Innovation Open Lab hosts two labs: a Cloud Services Lab,

and an Energy and Sustainability Lab.

The Cloud Services Lab has helped advanced the state-of-the-art in research through numerous FP5, FP6

and FP7 engagements including MOBILE CLOUD NETWORKING, IOLANES, FIWARE, SLA@SOI, PERSIST,

SOCIETIES, N4C, iSURF, DBE, as well as various joint initiatives with industry (SAP CoLab, Nokia CoLab) and

academia (Innovation Value Institute). It actively engages in international standards initiatives, and its

researchers participate on national ISO sub-committee mirror groups, in European cloud standards

working groups, and in global ISO sub-committees (e.g. ISO SC38 – Cloud Computing). The lab also

occupies a leadership role (co-chair) in OGF’s Open Cloud Computing Interface working group.


For several years now Intel has been promoting a cloud computing vision with three core tenants:

Automation, Federation, and Client-Awareness. The Cloud must not be stifled by closed, proprietary

interfaces. FIWARE is completely aligned with this vision: designing, implementing and promoting open

APIs and technologies for an extensive range of functionality in the Cloud.

Results of FIWARE are now receiving significant visibility within the company as orchestration of the cloud

becomes a key research responsibility for Intel’s Cloud Services Lab. Open Specifications, Open APIs, Open

Standards are all key enablers for cloud orchestration and the progress made by FIWARE partners in

pushing and promoting these are being leveraged and further advanced in important internal research

vehicles such as the Cloud Services Lab Apex Lake project.

The contributions of FIWARE partners to important ground-breaking open-source initiatives are also of

important significance. Intel for its part has been ramping up its support of and contributions to

OpenStack, along with other FIWARE partners such as IBM. Indeed towards the end of 2014 Intel has

become a Platinum member of the OpenStack Foundation. The contributions that are being made to the

OpenStack community by FIWARE are helping to significantly mature this platform.

Finally, the outreach of FIWARE to as wide a community as possible through its extensive FILAB

infrastructure and associated initiatives is recognised as an important way of increasing the awareness

and adoption of open solutions by a much wider audience.


Through FIWARE Intel’s Cloud Services Lab has been able to progress the maturity and adoption of open

standards and APIs to progress the corporate Intel vision in three key areas.

In Cloud Hosting, FIWARE has helped mature OGF’s Open Cloud Computing Interface (OCCI) specification

for cloud infrastructure management, with our reference implementation continuously maintained and

published as open source in step with the regular OpenStack releases. This standard is going from

strength to strength with over 20 implementations now published by the community, and a

comprehensive (but backward compatible) refinement of the standard is nearing completion at the time

of writing.



FIWARE has also helped showcase how SNIA’s Cloud Data Management Interface (CDMI) can be used to

provide an open standardised interface to object storage functionality – through the Object Storage GE

built on top of OpenSwift Swift. This GE has been successfully deployed and is being consumed in FILAB.

Intel’s work within CDI helped to explore the way web based applications can perform native applications

functionality. Via CDI’s collaboration with the FP7 project Webinos, which primarily explored of web

based applications can coordinate in a distribute and diverse compute environment, it has defined the

architecture of some of the Tizen OS functionality.

Through 2014 Intel’s Cloud Services Lab has begun to consolidate and focus its efforts more specifically on

the challenges of orchestration in the Cloud. The progress and results achieved in FIWARE are already

being advanced to the next level, with continuing investment by the lab in OCCI in particular, guided by

the community’s particular interest in this open standard. For example, with the support of EIT, Intel have

just published an extension to OCCI that supports machine readable SLAs. This research, directly

dependant on the advances made by FIWARE in the DCRM Generic Enabler, was identified as one of the

key areas requiring progress in the ETSI Cloud Standards Coordination final report – a report which Intel

contributed FIWARE inputs into.

Under the leadership of Principal Engineer Joe Butler, Intel’s Cloud Services Lab has been positioned

within the company to take leadership for Cloud Orchestration research going forward. To this end it has

constructed a research vehicle we call Apex Lake and is currently developing a roadmap to advance the

capabilities of this cloud orchestration framework. This work, in collaboration with fellow travellers from

industry and academia, is already helping identify contributions to Intel product designs and to Open

Source projects to help the industry and the community take full advantage of the investments that they

make in their computing infrastructure.

Fundamental to the realisation of this roadmap will be a continuing investment in standards for the cloud.

Ongoing enhancements of the OCCI progress in FIWARE is planned to mature this open standard to

support rich infrastructure monitoring – a key prerequisite for intelligent orchestration – as well as the

flexible machine-readable Service Level Agreement support already referred to. Intel will also maintain

their participation in ISO/IEC JTC 1/SC38 – the subcommittee of ISO responsible for standards in cloud

computing.

Whilst the current focus of Intel’s work is on the orchestration of compute resources in the cloud, plans

are being made to address the complete spectrum of software defined infrastructure. As orchestration of

storage, networks and client capabilities are added to the scope of Apex Lake, the relevant progress made

in FIWARE by Intel and other partners in these broader areas will be leveraged where possible.


The open source nature of much of the output of FIWARE is to be commended. It has minimised the

complications and issues for Intel exploiting those results of FIWARE of most relevance to its corporate

interests.

15. Nec Europe Ltd



NEC Organization Profile

NEC Corporation is one of the world’s leading providers of Internet, broadband network and enterprise

business solutions dedicated to meeting the specialized needs of its diverse and global base of customers.

NEC delivers tailored solutions in the key fields of computer, networking and electronic devices, by

integrating its technical strengths in IT and networks. Empowered by innovation, its solutions, products

and services are backed by the leadership and expertise of one of the most successful global companies,

conducting business for more than 100 years. NEC Europe Ltd. established the NEC Laboratories in

Heidelberg, Germany in 1997 as NEC's third research facility in Europe. Research and development

functions are integrated into the same organization to shorten the time to market of cutting-edge

network technologies. The Heidelberg labs focus on software-oriented research and development for the

next generation Internet and for the societal challenges around the globe. New communication

architectures and protocols supporting multimedia and mobility over the Internet, together with

intelligent Future Internet services, are the core of our work. A market research team continuously

analyses market trends and market requirements to ensure that R&D activities address actual market

needs. The laboratories place special emphasis on solutions meeting the needs of NEC's European

customers.

Exploitation of FIWARE by NEC

As a global company, NEC is in general witnessing a move towards data platforms and services reaching

from utlility networks, production networks, to smart city and smart nations. NEC has already promoted

the usage of the FIWARE platform within Europe (in research and in commercial context) as well as in

other countries (Japan, Korea, Singapore, to name a few).

NEC is active in supporting FIWARE inside the FI-PPP and within the follow-up project FI-Core. There are

currently three different ongoing activities within NEC where the FIWARE infrastructure and FIWARE

Generic Enablers are commercially exploited. Firstly, NEC is part of a group of companies that actively

pursue the goal to harmonize FIWARE enablers with the oneM2M standard; thus further extending the

reach of FIWARE. Secondly, NEC Singapore is building upon FIWARE enablers and protocols in a

commercial Public Safety Platform that enables Interagency Collaboration and exchange of IoT data.

Finally, a commercial Smart City Control Center is created by NEC Iberia, using multiple FIWARE enablers

as building blocks, protocols, and data sources.

In all these exploitation activities the results of the FIWARE Internet-of-Things Chapter play the major

role; including the Generic Enablers used and the APIs adopted.

Public Safety Platform: On June 2, 2014, NEC has announced the global launch of MAG1C (Multi AGencies,

1 Concert) solutions for analyzing information from multiple sources, including video, voice, as well as

sensor data from temperature, humidity and scent sensors. The press release can be found on

http://www.nec.com/en/press/201406/global_20140602_01.html.In cooperation with NEC Laboratories

Europe, NEC Singapore currently integrates FIWARE building blocks into their solution. In particular, the

IoT Broker GE and Configuration Management GE from the IoT chapter provide an inter-agency

communication platform to exchange data streams from sensor devices between different agencies.

Every agency can receive controlled access to live sensor data streams and other information from other

agencies. Previous versions of MAG1C have already been sold to governments in the Asia-Pacific area. The

security component from the first MAG1C version is currently being integrated with the IoT Broker GE

thus showing that FIWARE enablers are being integrated with existing products. An enhanced version of

the Configuration Management GE is used together with the “Pervasive Display Network – Control System

(PDN-CS)” to find relevant display on which to show emergency messages. The feature is part of the



MAG1C shared digital signage module. Customers in general are mainly city and region governments. In

case of this exploitation activity, utilization and dissemination is done by NEC in the role of a Public Safety

Platform provider. The key person in charge of this commercial activity is Paul Wang (CTO & Head of

Strategy & Mgmt), NEC Global Safety Division – Public Safety, Singapore.

Smart City Control Center: NEC Iberia is working with city authorities and local SMEs to create a Smart City

Control Center for the city of Santander. A respective press releases can be found here: “NEC helps

Santander sustain the lead as Europe's smartest city”1.

In this project, NEC Iberia has the role of coordinator and system integration, while NEC Laboratories

Europe is providing technology and know-how, including FIWARE results. In particular, enablers from the

FIWARE IoT Backend play a central role in this platform: Availability data is stored in a custom

implementation of the Configuration Management Generic Enabler, and the NEC IoT Broker is used to

retrieve live data from smart cities through the FIWARE NGSI interface. Through an instance of the

Backend Data Handling GE, sensor data from the city of Santander is fed into the platform, and further

cities are planned to be connected with. The first client for this platform is the City of Santander who

wishes to now the operational status of the city and is planning to put more commercial services on the

smart city platform (“NEC and ASCAN to launch pioneering smart waste collection service in Santander”2).

In general city governments are targeted as customers for the operation center. Business partners are

NEC Iberia and the SMEs (Heritas, Conceptual) plus City Service Providers like Ascan, responsible for waste

management. The key person in charge of this activity is Victor Martinez, Manager at NEC Iberia and

responsible product manager. Second collaboration partner is NEC’s Cloud Center of Compentence (Cloud

CoC) in Madrid, Spain. The Cloud CoC will have the technical responsibilities for the final product including

the FIWARE enabler. It should be noted that the FIWARE technology was included in the second release of

the CCOC product. Please use the press release mentioned in the footnote 4 as an official statement for

NEC using the FIWARE platform in their product. FIWARE and generic enablers from FIWARE are

prominently mentioned in the PR.

oneM2M Demonstrator. A concrete exploitation and dissemination activity currently ongoing is the

creation of a demonstrator showing the potential of the oneM2M standard for Smart Cities in connection

with NGSI and FIWARE. In this demonstrator, a Smart City application is deployed on top of oneM2M

enablers. The oneM2M enablers, which are provided by Fraunhofer FOKUS, InterDigital, and KETI, will be

uses as a middleware for bringing data from the City of Santander, collected using FIWARE enablers, to an

application. The demonstrator was shown at the oneM2M Launch Event (December 2014), and it is also

targeted to be ready for the IoT Week taking place in Seoul in early November 2014. During the oneM2M

launch event, the contribution of FIWARE was explained in the presentation “Showcase C: Smart City

Services and Multiple Service Layer Platforms Interworking”3. This activity supports the dissemination of

the NEC Smart City business in particular, and the use of FIWARE in the context of M2M in general. A

respective Press Release had the title “NEC supports smart city scalability with first live deployment of the

new oneM2M standard”4. Further media coverage including FIWARE references resulte from the

oneM2M event 5,6 .The key person in charge of this activity is Ataru Kobayashi, NEC Corporation,

Telecommunication Carriere Business Unit, Japan.

Support of general FIWARE exploitation activities

NEC is supporting the general dissemination and exploitation activities of FIWARE. In particular, we have

contributed to the following group of events:

- FIWARE architects week, 2012, Zürich and Madrid. Here the FIWARE protocols and enablers were

presented to the FIWARE use case projects.



- FIWARE Hackathon and Smart City conference in Santander, Spain, Oct 16-18th, 2013

- FIWARE IoT Demo at ECFI Conference, September 2014, Munich. Here the capabilities of FIWARE

IoT were demonstrated to the public.

- FIWARE Bootcamp, October 2014, Berlin. Here SMEs were instructed about what FIWARE is and

how it can be used in their businesses.

Furthermore, NEC is collaborating with public agencies such as the Irish Civil guard (together with

Waterford Institute, a XIFI node) to verify the use of FIWARE enablers for public safety.

IPR Management

NEC is not only providing the open specification of the IoT Broker Generic Enabler, but has also released

the reference implementation as open source. This is to facilitate the active usage of the APIs and the

enablers, while the business model of NEC in the Smart City and Public Safety sector is to provide

specialized integrated platforms leveraging on FIWARE Generic Enablers and other well-established

components.

1 http://www.nec.com/en/press/201405/global_20140507_01.html


3 Download from here:

https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CC0QFj

AC&url=http%3A%2F%2Fwww.onem2m.org%2Fcomponent%2Frsfiles%2Fdownloadfile%2Ffiles%3Fpath

%3DoneM2M_Showcase%25255CShowcase_C_Interworking_oneM2M_IoTPlatforms.pdf%26Itemid%3D

198&ei=s0KYVJmuF6LNygOH6IKIBg&usg=AFQjCNFpNf558_ENjZhsFLsAVa7K1tywQ&sig2=cC2GYpuLeFVh

cjHIZN1mXA&bvm=bv.82001339,d.bGQ


5 “NEC brings the oneM2M standard to smart cities”,

http://www.telecomtv.com/articles/m2m/nec-brings-the-onem2m-standard-to-smart-cities-12037/

6“NEC supports smart city scalability with first live deployment of the new oneM2M standard”

http://m2mworldnews.com/2014/12/15/79539-nec-supports-smart-city-scalability-with-first-live-

deployment-of-the-new-onem2m-standard/

16. FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER

ANGEWANDTEN FORSCHUNG E.V (Fraunhofer)


The Fraunhofer Institute for Open Communication Systems FOKUS is researching and developing

application-orientated solutions for partners in industry, research and public administration in various ICT

fields including the communication technologies and services and their interoperability, architectures and

protocols of future communication networks and platforms, interactive technologies for individual and

community applications, measuring and testing of distributed telecommunication and software systems.

Fraunhofer FOKUS develops innovative processes from the original concept up to the pre-product in

companies and institutions. With an expertise of more than 20 years, Fraunhofer sees itself as a link

between university research on the one hand and industry and public administration on the other.

Acknowledging the current opportunities and challenges in the mass broadband communication market,

FRAUNHOFER FOKUS through its competence centre for Next Generation Network Infrastructures (NGNI)

has become internationally recognised as the Next Generation Network (NGN) testbed experts,

particularly in the field of converged network infrastructures and virtualisation, including the Open IMS



Core (www.openimscore.org), OpenEPC (www.openepc.net), OpenSDNCore (www.opensdncore.org),

OpenMTC (www.open-mtc.org) and Open5GCore (www.open5Gcore.net) implementation enabling the

fast prototyping, evaluation and dissemination of novel R&D concepts on a realistic comprehensive

integrated testbed infrastructure starting from access networks to service platforms including multimedia

operator services, core networks for 2G/3G/LTE and their evolution towards 5G, dynamic virtualised

service enablement and device management.


- Fraunhofer FOKUS contributed to three GEs with specific functionality: IoT MTC Gateway, I2ND

S3C, I2ND CDI, providing them as part of the Fraunhofer toolkits

- Fraunhofer FOKUS is currently in charge of the XiFi German node and through this has deployed a

large number of FIWARE enablers

- Fraunhofer FOKUS is part of FI-STAR use case project using specific GEs and further adapting them

for the eHealth environment


Own GEs are offered as part of the testbed implementations for different operators, vendors and

academic partners as follows:

- The MTC gateway is a major part of the OpenMTC toolkit (www.open-mtc.org) currently deployed

in more than 10 locations around the world

- The S3C components of Fraunhofer were introduced in November 2014 as part of the OpenMTC

in order to address the needs of M2M deployments in 5G environment.

- The CDI components of Fraunhofer are offered as part of the Open5GCore

(www.open5GCore.net) toolkit launched in November 2014 with already 3 industry customers

and the possibility to further use the results in the 5G ecosystem.

The licensing team is lead by Dr. Marius Corici and is part of the Next Generation Networks Infrastructure

department lead by Prof. Thomas Magedanz. The success metric is based on the sales of licenses towards

the industry as well as on the number of licenses sold. A Fraunhofer FOKUS license is per legal

organization, with no number of instances or time limitations. Fraunhofer FOKUS is committed to

continue the lucrative business model of licensing for testbeds for at least two years including the

developments of FIWARE.

- The MTC Gateway and the S3C components were further extended and adapted for eHealth use

cases as part of the FI-STAR project and currently offered as part of the testbeds enabling

reliability and security advancements within the vertical markets for 5G ecosystem. Fraunhofer

FOKUS is currently in advanced discussions for Industrie 4.0 projects with a large number of

vendors and European Agencies in further development of this research and testbed

development track.

- With the experience accumulated by being part of FILAB, Fraunhofer FOKUS has developed a

successful business for Testbed as a Service, the FUSECO playground having a similar offer to

FILAB addressing the need of running application tests in a realistic environment. For this, along

with the Fraunhofer developments in FIWARE another set of developments in the area of core

networks, IoT and Cloud were considered, introducing the FIWARE GEs as part of the

comprehensive testbed offer.

- With the experience accumulated with the OpenEPC toolkit, Fraunhofer FOKUS launched a spin-

off company: Core Network Dynamics (CND) (www.corenetdynamics.com), specialized into critical

infrastructure deployments. Depending on the specific demand from the CND customers,



Fraunhofer FOKUS is willing to transfer at a fair price the S3C developments to CND in order to

increase the company’s value added services towards applications and to provide the basis for

their own application development.



Glossary

3GPP 3rd Generation Partnership Project

AGPL GNU Affero General Public License

API Application Programme Interface

ASON Automatically Switched Optical Network

B2B Business to Business

B2B VAS B2B value-added services

BAN Building Area Networks

BSD Berkeley Software Distribution

CAGR Compound Annual Growth Rate

CAPEX Capital Expenditure

CDI Connected Devices Interfacing

CDMI Cloud Data Management Interface

CEA composition execution agents

CEP Complex Event Processing

CIP Competitiveness and Innovation Framework Programme

COTS Commercial-Off-the-Shelf

CVSS Common Vulnerability Scoring System

DLNA Digital Living Network Alliance

DNS Domain Name System

E2E End To End

EPC Evolved Packet Core

EPL Eclipse Public License

ERI Extended Remediation Information

ERI-DEF Extended Remediation Data Exchange Format

ETSI European Telecommunications Standards Institute

EPL Eclipse Public License

EU European Union

FIRE Future Internet Research and Experimentation

FSF Free Software Foundation

FTTH Fibre to The Home

ForCES FORwarding and Control ElementS

G.E. Generic Enabler



GMPLS Generalized Multi-Protocol Label Switching

GPL GNU General Public License

GPS Global Position System

GSM Global System for Mobile Communications

HA high availability

HAN Home Area Networks

HGI Home Gateway Initiative

HTML HyperText Mark-up Language

IDMEF Intrusion Detection Message Exchange

I2ND Interface to Networks and Devices

IaaS Infrastructure as a Service

ICT Information and Communication Technology

IDM Identity Management

IETF Internet Engineering Task Force

IMS IP-Multimedia Subsystem

IoC Internet of Cloud

IoS Internet of Services

IoT Internet of Things

IPR Intellectual Property Rights

ISPs Internet Service Providers

IT Information Technology

LGPL Lesser General Public Licence

LDAP Lightweight Directory Access Protocol

LTE Long Term Evolution

LOD Linked Open Data

M2M Machine to Machine

MIT Massachusetts Institute of Technology

MNO Mobile Network Operators

MPL Mozilla Public License

NaaS Network as a Service

NAN Neighbourhood Area Networks

NetIC Network Information & Control

OCCI Open Cloud Computing Interface

OMA Open Mobile Alliance

OMG Object Management Group



OPEX Operating Expenses

OSS Open Source Software

OVAL Open Vulnerability and Assessment Language

P2P Peer to Peer

PaaS Platform as a Service

PPP Public Private Partnership

QoS Quality of Service

RCS Rich Communications Suite

RDF Resource Description Framework

ROI Return on Investment

RPS Remediation Policy Specification

RTL Remediation Tasking Language

RTP Real-Time Transport Protocol

SaaS Software as a service

SDK Software Development Kit

SDNP Software Driven Network Protocol

SES Software Enabling Services

SI industry solutions

SIEM Security Information and Event Management

SIP Session Initiation Protocol

SLA Service Level Agreement

SME Small and Medium-Sized Enterprise

SMS Short Message Service

SOA Service-oriented Architectures

SRM Security Risk Management

SSO Single sign-on

SWOT Strengths, Weaknesses, Opportunities and Threats

TMT Technology, Media, Telecommunications

UC Uses Case

UCP Uses Case Projects

UI User Interface

UPNP Universal Plug and Play

USB Universal Service Bus

USLD Uniform Service Description Language

vApps virtual appliance



VM Virtual Machine

VoIP Voice over Internet Protocol

W3C World Wide Web Consortium

WAC Wholesale Applications Community

WSDL Web Services Description Language

XaaS Everything as a Service

XACML Extensible Access Control Mark-up Language

XLM Extensible Mark-up Language

XSLT XML Stylesheet Language for Transformations



References

[IDC 3rd

Platform

13]

IDC- The 3rd Platform: Enabling Digital Transformation-November 2013, Frank Gens

[CENATIC] Open Smart Cities III: Open Source Platforms, Services and Applications for Smart Cities.

CENATIC. Observatorio Nacional del Software de Fuentes Abiertas

[Asymmetric

Business model]

Vision Mobile Report: Asymmetric Business model. The Secret Weapon of Software Driven

companies. October 2014

[Open Source

Marketplace] Challenges of the Open Source Component Marketplace in the Industry. Claudia Ayala,

Øyvind Hauge1, Reidar Conradi, Xavier Franch, Jingyue Li1,and Ketil Sandanger Velle

[Ballon 07] Ballon, P. (2007) “Business Modelling Revisited: The Configuration of Control and Value”, info:

The Journal of Policy, Regulation and Strategy for Telecommunications, Information and

Media, vol.9, issue 5 (August 2007), 6-19.

[Chesbrough 06] Chesbrough, H. (2006) Open Business Models: How to Thrive in the New Innovation

Landscape. Boston, Massachusetts: Harvard Business School Press

[Mckinsey 13] McKinsey Report: Disruptive technologies: Advances that will transform life, business, and the

global economy. May 2013.

[M2M 14] Machina Research Whitepaper: Rapid Application enablement and extensibility –

competitive advantage in M2M/IoT application platforms. January 2014.

[OpenStack] www.openstack.org

Cloud

[AMAZONAWS] Amazon AWS, http://aws.amazon.com/es/

[Amazon EBS] www.amazon.com, “Amazon Elastic Bean Stalk”, https://aws.amazon.com/elasticbeanstalk/

[Amazon EC2] www.amazon.com, “Amazon EC2”, https://aws.amazon.com/ec2/

[AMAZONOPS] Amazon OpsWorks, http://aws.amazon.com/opsworks/

[AnyCloud] cloudbees.com, AnyCloud, http://www.cloudbees.com/platform/anycloud.cb

[AWS] www.amazon.com, “Application Hosting”, https://aws.amazon.com/application-hosting/

[AWSCF] AWS CloudFormation, http://aws.amazon.com/cloudformation/

[Azure] Windows Azure website home page, http://www.windowsazure.com

[Azure Arch] Hanu Kommalapati, “Windows Azure for Enterprises”, 2010, http://msdn.microsoft.com/en-

us/magazine/ee309870.aspx

[Azure OS] J.D. Meier's Blog, “Windows Azure Platform at a Glance”,

https://blogs.msdn.com/b/jmeier/archive/2010/02/16/windows-azure-platform-at-a-

glance.aspx?Redirected=true

[BEERNAERT2012] Beernaert et al. “Automatic elasticity in OpenStack”. Proceedings of the Workshop on Secure

and Dependable Middleware for Cloud Monitoring and Management. MM '12. York, NY, USA.

[NVF] Wikipedia, Network Functions Virtualization,

http://en.wikipedia.org/wiki/Network_Functions_Virtualization

[OASIS-TOSCA] OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA),

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca

[Object Storage] Thijs Metsch, Object Storage GE Implementation, https://github.com/tmetsch/cdmi

[OCCI] Open Cloud Computing Interface website home page, http://occi-wg.org/

[OF v1.2] The Open Network Foundation, “OpenFlow 1.2”, December 2011,

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-

specifications/openflow/openflow-spec-v1.2.pdf

[OFSWITCH v1.3.1] The Open Network Foundation, “OpenFlow Switch Specification”, September 2012,



https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-

specifications/openflow/openflow-spec-v1.3.1.pdf

[Wiki Amazon] Wikipedia, “Amazon.com”,

https://en.wikipedia.org/wiki/Amazon.com#Computing_services

[Wiki Azure] Wikipedia, “Windows Azure”, http://en.wikipedia.org/wiki/Windows_Azure

[Wiki GAE] Wikipedia, “Google App Engine”,

http://en.wikipedia.org/wiki/Google_App_Engine#Runtimes_and_frameworks

[Wiki Glacier] Wikipedia, “Amazon Glacier”,

https://en.wikipedia.org/wiki/Amazon_Glacier

Data

[AVRO] Apache Software Foundation, The AVRO web site, http://avro.apache.org

[AzureTables] Microsoft Azure Large Table Service web site (2013): http://www.windowsazure.com/en-

us/develop/net/how-to-guides/table-services

[Balaur 2013] Balahur, A., Steinberger, R., Kabadjov, M., Zavarella, V., Van Der Goot, E., Halkia, M., ... &

Belyaeva, J, Sentiment analysis in the news, arXiv preprint arXiv:1309.6202, 2013

[Baldauf 07] Baldauf, M., Dustdar, S. and Rosenberg, F., A survey on context-aware systems., International

Journal of Ad Hoc and Ubiquitous Computing, vol. 2, num. 4, pp. 263-277, 2007. ISSN 1743-

8225., 2007

[Barnaghi 2012] Semantics for the Internet of Things: early progress and back to the future, , .

[Belissent 13] Belissent, J., Getting The Most Out of Open Data, Forrester Report, 2013

[BernersLee 06] Berners-Lee, T. (2006) "Linked Data". International Journal on Semantic Web and Information

Systems, vol. 4, num. 2, 2006. Publisher: W3C. ISSN: 15526283

[Bernstein96] Middleware: a model for distributed system services. Communications of the ACM, pages 86 –

98, 1996.

[BigTable] Fay Chang, Jeffrey Dean, Sanjay Ghemawat, Wilson C. Hsieh, Deborah A. Wallach, Mike

Burrows, Tushar Chandra, Andrew Fikes, and Robert E. Gruber (2006). "Bigtable: A Distributed

Storage System for Structured Data". OSDI'06: Seventh Symposium on Operating System

Design and Implementation, Seattle, WA, November, 2006.

[Bizer 09] Bizer, C., Heath T. and Berners-Lee, T. (2009) "Linked Data – The Story So Far". International

Journal on Semantic Web and Information Systems, vol 5, num. 3, 2009.

[BLUM13] N. Blum, et al., Telecom Applications, APIs and Service Platforms. Evolution of

Telecommunication Services. Springer Berlin Heidelberg, 25-46., 2013

[Hadoop] The Apache Software Foundation (2010) Apache Hadoop web site. http://hadoop.apache.org/

[Haener 13] Haener, Rainer, Joachim Waechter, and Martin Hammitzsch, Management of natural crises

with choreography and orchestration of federated warning-systems., EGU General Assembly

Conference Abstracts. Vol. 15. 2013, 2013

[Hanney 2014] Haney, C, Sentiment Analysis: Providing Categorical Insight into Unstructured Textual Data,

Social Media, Sociality, and Survey Research, 2014

[HBase] The Apache Software Foundation (2010) Apache Hbase web site.

http://hadoop.apache.org/hbase/

[HDFS] The Apache Software Foundation (2010) Apache Hadoop Distributed File System is part of



Apache Hadoop, http://hadoop.apache.org/docs/r1.0.4/hdfs_design.html

[Lefort et al. 2011] Semantic Sensor Network XG Final Report

[Lenzerini, 2002] M. Lenzerini. Data integration: A theoretical perspective. In Proc. of PODS 2002, pages 233–

246, 2002. Retrieved from http://portal.acm.org/citation.cfm?id=543644

[Lenzerini, 2011] M. Lenzerini. Ontology-based data management. In Proc. of CIKM 2011, pages 5–6, 2011

[Logothetis 08] Logothetis, D. and Yocum, K., Wide-Scale Data Stream Management, Tech Report Retrieved

from http://www.usenix.org/event/usenix08/tech/full_papers/logothetis/logothetis_html/,

2008

[LOPEZ13] L. Lopez, et al., Kurento: a media server technology for convergent WWW/mobile real-time

multimedia communications supporting WebRTC., World of Wireless, Mobile and Multimedia

Networks (WoWMoM), 2013 IEEE 14th International Symposium and Workshops on a. IEEE,

2013

[Lucene] The Apache Software Foundation (2010) Apache Lucene web site. http://lucene.apache.org

[M. Arenas, et al,

2012]

M. Arenas, A. Bertails, E. Prud'hommeaux, J. Sequeda, A Direct Mapping of Relational Data to

RDF, W3C Recommendation, 2012

[MAPREDUCE] Map & Reduce, http://research.google.com/archive/mapreduce.html, .

[MapReduce] http://research.google.com/archive/mapreduce.html

[MarkLogic] MarkLogic document store web site (2013). http://www.marklogic.com

Apps

[Amazon DevPay] Amazon DevPay: http://aws.amazon.com/es/devpay

[Amazon WS] Amazon Web Services: http://aws.amazon.com

[Appelquist 10] Daniel Appelquist, A Standards-based, Open and Privacy-aware Social Web, 2010.

[AppStore] Apple App Store (requires iTunes): http://www.itunes.com/appstore/

[Ballon 07] Ballon, P. (2007) “Business Modelling Revisited: The Configuration of Control and Value”, info:

The Journal of Policy, Regulation and Strategy for Telecommunications, Information and

Media, vol.9, issue 5 (August 2007), 6-19.

[BlueVia] BlueVia website: http://www.bluevia.com/

[BPEL] Web Services Business Process Execution Language (WS-BPEL): http://docs.oasis-

open.org/wsbpel/2.0/varprop.

AllegroGraph RDF store, http://www.franz.com/agraph/allegrograph/

[LinkedUSDL] Linked USDL Community Site, http://linked-usdl.org

[Maximilien 07] E.M. Maximilien, A. Ranabahu, and S. Tai, Swashup: situational web applications mashups,

New York, New York, USA: ACM Press, 2007.

[W3CWidgets] W3C Specifications for Widget Packaging and XML Configuration.

http://www.w3.org/2008/webapps/wiki/WidgetSpecs

[WADL] Web Application Description Language: http://www.w3.org/Submission/wadl/

IoT

[6LowPan] IETF Working Group How to use IP for severely constrainted devices



(http://datatracker.ietf.org/wg/6lowpan/)

[Abangar 10] Abangar H, Ghader M, Gluhak A, Tafazolli R. (2010) 'Improving the Performance of Web Services

in Wireless Sensor Networks'. Florence, Italy: Future Network & Mobile Summit 2010

[Aggarwal 07] Data Streams: Models and Algorithms (Springer) Ed. Charu Aggarwal, January 2007. --

Comprehensive survey driven book on Data Stream Research with chapters contributed by

prominent researchers in the field.

[ANSI 11] The ANSI/IEEE N42.42 standard specifies the XML data format that shall be used for both required

and optional data to be made available by radiation measurement instruments.

(http://www.nist.gov/pml/div682/grp04/n42-2011.cfm)

[Anyanwu 03] K. Anyanwu, A. P. Sheth, (2003) “p-Queries: Enabling Querying for Semantic Associations on

theSemantic Web”, In Proceedings of WWW 2003 Conference, pp. 690–699, 2003.

[Atzori 10] L. Atzori, A. Iera, G. Morabito (2010), “The Internet of Things: A survey”, Computer Networks, vol

54, issue 15, pp. 2787-2805, 2010.

[Autonomic] Jeffrey O. Kephart and David M. Chess (2003) "Autonomic Manifesto", IBM Thomas J, Watson

Research Center. Retrieved of http://www.research.ibm.com/autonomic/manifesto

[Barnaghi 09] P. M. Barnaghi, S. Meissner, M. Presser, and K. Moessner (2009) “Sense and Extensible: Semantic

Data Modelling for Sensor Networks”, In Proc. Of the ICT-Mobile Summit, June 2009.

[Barnaghi 10] P. Barnaghi, M. Presser, K. Moessner (2010) "Publishing Linked Sensor Data"', In Proc. of the 3rd

Int. Workshop on Semantic Sensor Networks (SSN), Nov. 2010.

[ZibeeAll] ZigBee Alliance (2010). http:// www.zigbee.org

In2d

[APPCELERATOR] Introducing the Appcelerator Platform. http://www.appcelerator.com/platform/appcelerator-

platform/. Accessed on May 2013

[AQUILA2003] AQUILA-2003 T. Engel et al., “AQUILA: adaptive resource control for QoS using an IP based layered

architecture”, IEEE Communication Magazine, Volume 41, (1), January, 2003

[CISCO2013] Cisco, “Cisco Visual Networking Index: Global Mobile Data”, Traffic Forecast Update, 2012–2017;

[ETICS2010] FP7 ICT Economics and Technologies for Inter-Carrier Services (ETICS), D4.1 End-to-End service

specification template, www.ict-etics.eu, 2010;

[OpenAJAX] About OpenAjax Alliance. http://www.openajax.org/overview.php. Accessed on May 2013

[ONEAPI] GSMA (2010) "GSMA‘s OneAPI Initiative", http://www.gsmworld.com/oneapi/index.html,

Accessed on May 2013

[Openflow] White Paper: http://www.openflow.org/documents/openflow-wp-latest.pdf

[OPENROADS] K. K. Yap, M. Kobayashi, R. Sherwood, N. Handigol, T. Huang, M. Chan, N. McKeown, “OpenRoads:

Empowering Research in Mobile Networks” . In Proceedings of ACM SIGCOMM, Barcelona, Spain,

August 2009;

[OPENROADS2] K. K. Yap, T. Huang, M. Kobayashi, Y. Yiakoumis, N. McKeown, S. Katti and G. Parulkar, “Making Use

of All the Networks Around Us: A Case Study in Android,” in CellNet’12, Helsinki, Finland, August

13, 2012;

[PHONEGAP] PhoneGap: About the Project. http://phonegap.com/about. Accessed on May 2013.

[PKT040113] PacketCable Electronic Surveillance Specification, PKT-SP-ESP-I03-040113, Cable Television

Laboratories Inc., 13 January 2004;

[RHODES] Rhodes Reference. http://docs.rhomobile.com/rhodes/introduction. Accessed on May 2013.

[SDNBUCA] S. Das, G. Parulkar, N. McKeown, “SDN Based Unified Control Architecture”, Photonics Conference

(IPC), 2012 IEEE

[SPARC] MPLS Demonstrator http://www.fp7-sparc.eu/prototyping/mpls-demonstrator/

[TEQUILA2003] TEQUILA-2003 E. Mykoniati et al. “Admission control for providing QoS in DiffServ IP networks: the

TEQUILA approach””, IEEE Communication Magazine, Volume 41, (1), January, 2003;



[TISPAN282003] ETSI (2003) ―Telecommunicahons and Internet converged Services and Protocols for Advanced

Networking (TISPAN), TISPAN ES 282.003. Resource and Admission Control Sub-System (RACS)

Release 3. www.etsi.org;

[UNI] User Network Interface http://www.oiforum.com/public/documents/OIF-UNI-01.0-R2-

Common.pdf Optical Internetworking Forum;

[W3CDAP] Device APIs Working Group. http://www.w3.org/2009/dap/. Accessed on May 2013

[WAC] Wholesale Applications Community

http://en.wikipedia.org/wiki/Wholesale_Applications_Community. Accessed on May 2013;

[WEBINOS] About webinos. http://www.webinos.org/about-webinos/. Accessed on May 2013.

Security

[Aniketos] «FP7 Aniketos,» [En ligne]. Available: http://www.aniketos.eu/.

[ArcSight] http://www.ndm.net/siem/main/arcsight-siem

[Atlas] «Atlas,» [En ligne]. Available: http://atlas.arbor.net/.

[Atz10] L. Atzori, A. Iera et G. Morabito, «The internet of things: A survey,» Computer Networks, 54, 15,

2010.

[Ban09] J. Banghart et C. Johnson, «The Technical Specification for the Security Content Automation

Protocol (SCAP),» NIST Special Publication, 2009.

[Bar11] M. Barrere, G. Betarte et M. Rodriguez, «Towards Machine-assisted Formal Procedures for the

Collection of Digital Evidence,» 9th Annual International Conference on Privacy, Security and Trust,

2011.

[New05] J. Newsome et D. Song, «Dynamic taint analysis for automatic detection, analysis, and

signaturegeneration of exploits on commodity software,» NDSS, 2005.

[NIST] «NIST, National Institute of Standards and Technology,» [En ligne]. Available: http://www.nist.gov/.

[OAuth] «OAuth,» [En ligne]. Available: http://oauth.net/.

[Oeh05] P. Oehlert, «Violating assumptions with fuzzing,» IEEE Security and Privacy, vol. 3, n° %12, 2005.

[PEEM] «Open Mobile Alliance (2009) "Policy Evaluation, Enforcement and Management Architecture

V1.0.",» [En ligne]. Available:

http://www.openmobilealliance.org/Technical/release_program/peem_v1_0.aspx.

[PeerTrust] «PeerTrust,» [En ligne]. Available: http://www.l3s.de/peertrust/.

[PPL] «PrimeLife Policy Language,» [En ligne]. Available:

http://spdp.di.unimi.it/papers/w3c_wsacas_2009_02.pdf.

[Prime] «Privacy and Identity Management for Europe. EU FP6 project,» [En ligne]. Available:

https://www.prime-project.eu/.

[Saw08] R. E. Sawilla et X. Ou, «Identifying Critical Attack Assets in Dependency Attack Graphs,» 2008.

[SecureChange] «FP7 SecureChange,» [En ligne]. Available: http://www.securechange.eu/.

[Serenity] «The Serenity Project,» [En ligne]. Available: http://www.strategiestm.com/EU-Project-SERENITY-s-

Security.html.

[Sha10] A. Shabtai, Y. Fledel, U. Kanonov, Y. Elovici, S. Dolev et C. Glezer, «Google Android: A

Comprehensive Security Assessment,» Security Privacy, IEEE, 8, 2010.

[SIPIPFIX] S. Niccolini, B. Claise, B. Trammell et H. Kaplan, «A Common Log Format for SIP using IPFIX Files,»

IETF 79, 2010.

[SNORT] «SNORT,» [En ligne]. Available: http://www.snort.org. Snort® is an open source network intrusion

prevention and detection system (IDS/IPS

[Sut07] M. Sutton, A. Greene et P. Amini, «Fuzzing: Brute Force Vulnerability Discovery,» 2007.

[SWIFT] «SWIFT (Secure Widespread Identities for Federated Telecommunications), EU IST FP7 project,»

[En ligne]. Available: http://www.ist-swift.org/.



[Sym11] Symantec, «W32.stuxnet dossier,» 2011.

[Sym13] Symantec, «Internet security threat report,» 2013.

[Szo11] P. Szor, «Duqu - threat research and analysis,» Technical report, McAfee, 2011.

[TLS] I. Workgroup, «Transport Layer Security,» [En ligne]. Available: http://www.ietf.org/rfc/rfc2246.txt.

[Tls99] Transport Layer Security (tls) - http://datatracker.ietf.org/wg/tls/charter/ - mailing list:

[email protected] – to Subscribe: https://www.ietf.org/mailman/listinfo/tls

[XACML] «OASIS eXtensible Access Control Markup Language (XACML) TC,» [En ligne]. Available:

http://www.oasis-open.org/committees/xacml.

[XACML] OASIS eXtensible Access Control Markup Language (XACML) - https://www.oasis-

open.org/committees/tc_home.php?wg_abbrev=xacml

[XRay] «X-Ray for Android,» [En ligne]. Available: http://www.xray.io/.

[Yao82] http://www.brics.dk/SMCL/: multi-party computation Language; Secure Multi-party Computation

Using Virtual Parties for Computation on Encrypted Data – Rohit Pathak (Acropolis Inst. Of

Technology & Research) & Satyadhar Joshi (Shri Vaishnav Inst. Of Technology & Science) Indore,

India – rohitpathak,[email protected]

[YuS10] S. Yu, C. Wang, K. Ren et w. Lou, «Achieving secure, scalable, and finegrained data access control in

cloud computing,» 29th IEEE Conference on Computer Communications, 2010.

[ZHA07] T. ZHANG, M.-Z. HU, X.-C. YUN et Y.-Z. ZHANG, «Attack Graph Generation with Implementation in

Network Security,» WESEAS Conference on computers, 2007.

[Zir12] N. Ziring et S. D. Quinn, «Specification for the Extensible Configuration Checklist Description Format

(XCCDF),» 2012.

large-scale integrated project (ip) · private public partnership project (ppp) large-scale...

Documents