IoT

Large-scale integrating project (IP) proposal ICT Call 5 FP7-ICT-2007-5 Title: Internet of Things for All Acronym: IoT4All

www.iot4all.com Date of preparation: 26.10.2009 Participant no.

Participant organisation name

Part. short name

Country

1 (Coordinator)

Atos Origin Sociedad Anonima Espa帽ola

Atos Origin

Spain

2

TXT e-Solutions

TXT

Italy

3

Centro Ricerche FIAT ScpA

CRF

Italy

4

DIAKINISIS S.A

DIAKIN

Greece

5

Fundaci贸n Instituto Gerontol贸gico Matia-INGEMA

INGEMA

Spain

6

CAEN RFID srl

CAEN

Italy

7

Telit Wireless Solutions Ltd

Telit

Israel

8

Informatica per il Sistema degli Enti Locali s.p.a

Insiel

Italy

9

Research and Education Laboratory in Information Technologies

AIT

Greece

10

LISSI/SCTIC

LISSI

France

11

Evidian

Evidian

France

12

Kinamik Data Integrity, S.L.

Kinamik

Spain

13

Institute of Communication and Computer Systems/National Technical University of Athens

ICCS/NTU A

Greece

14

Forschungszentrum Informatik an der Universit盲t Karlsruhe

FZI

Germany

15

Athens University of Economics and Business

AUEB

Greece

16

Sigs Datacom GmbH

SIGS

Germany

17

Fundacion Esade

Esade

Spain

18

BMT Group Ltd.

BMT

United Kingdom

Work programme topics addressed Objective ICT-2007.1.3: Internet of Things and Enterprise environments Name of the Coordinating Person: Santi Ristol E-mail: santi.ristol@atosorigin.com Fax: +34 934860736

Proposal Part B: page 1 of 203

Proposal Abstract Internet of Things is a perspective of the global Future Internet where physical things are enabled to share their Real World knowledge with virtual things living in the Digital World to enable novel Internet based applications in the Socio-economic World.

The IoT4All (Internet of Things for All) IP vision is to go beyond the interoperability among real, digital and socio-economic worlds, where just exchanges of data could occur, but to achieve by 2020 a sympathetic and osmotic IoT Space, where these 3 worlds influence, participate and in some cases cum-penetrate each other. This future IoT Space will finally unleash the potential of the IoT foundational technologies (microsystems, nanotechnologies, wireless sensors, network infrastructure, objects identification, energy saving and harvesting, communication frequencies and protocols) in the meantime developed in different domains, making IoT a resource for all, citizens and companies, governments and enterprises, representing therefore a revolutionary boast towards the society of the future.

The IoT4All mission and main innovation is to study, model and develop the mutual relations among real, digital and socio-economic worlds through an open architecture which will enable novel IoTdriven business applications for the benefits of European citizens and enterprises. As already mentioned above, our concept of the IoT is based on 3 Worlds: 1. A Real World where we imagine a physical heterogeneous, interoperable and evolutionary world of inter-connected computers, inter-connected mobiles, inter-connected people, interconnected sensors/actuators and inter-connected objects.

2. A Digital World where Services are provided & consumed, Events generated & filtered, Actuations inferred & controlled, Knowledge generated & transmitted, Reasoning implemented & explained, by means of an open, secure and privacy-preserving IT infrastructure, enabling the interoperability of Enterprise Collaboration Platforms, Enterprise Applications Clouds, Distributed Manufacturing Facilities and Global Service Delivery Platforms.

3. A Socio-Economic World, not confined to the business-oriented Manufacturing and Product + Service life-cycle, but extended to citizen’s wellbeing and Quality of Life, where the IoT revolution will stimulate the birth of novel business, social and knowledge software applications. In the Business field, making things protagonist of the decisional processes together with humans and computers, beyond collaboration and co-operation; in the Social field, making things able to find friends in both the human and smart objects constituency, to exchange information with them, to arrange dates and meetings, beyond human-oriented social networks, wikis and chats; in the Knowledge field, making things able to share experiences and to become context-aware and intelligent, beyond traditional document management systems and search engines.

The IoT4All IP will be run for 42 months by a consortium of 18 beneficiaries led by ATOS Origin Spain.

Proposal Part B: page 2 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Table of Contents PROPOSAL ABSTRACT....................................................................................................................................... 2 SECTION 1: SCIENTIFIC AND/OR TECHNICAL QUALITY, RELEVANT TO THE TOPICS ADDRESSED BY THE CALL.... 5 1.1 CONCEPT AND OBJECTIVES ................................................................................................................... 5 1.1.1 Background & Motivation .......................................................................................................... 5 1.1.2 Vision & Mission & Concept........................................................................................................ 7 1.1.3 The scientific and technological objectives & expected results..................................................... 9 1.1.4 Relation to the call objectives ................................................................................................... 15 1.2 PROGRESS BEYOND THE STATE OF THE ART ......................................................................................... 19 1.2.1 Future Internet and the IoT....................................................................................................... 19 1.2.2 RFID and WSAN in the IoT ........................................................................................................ 22 1.2.3 Trust, privacy & security in the IOT ........................................................................................... 25 1.2.4 Real World Technologies for the IoT ......................................................................................... 28 1.2.5 Distributed Intelligence and Smart Objects ............................................................................... 29 1.2.6 Smart Spaces and User Interaction in the IOT............................................................................ 32 1.2.7 Real World Management & Governance................................................................................... 33 1.2.8 Socio-economics, Business models & value proposition for the IoT ............................................ 33 1.2.9 Event Driven Platforms in the IoT.............................................................................................. 35 1.2.10 Service & Cloud Platforms for the IoT ................................................................................... 38 1.2.11 Service Front-end & Collaboration Platforms for the IoT ....................................................... 41 1.2.12 Semantic Reasoning in the IoT ............................................................................................. 43 1.3 S/T METHODOLOGY AND ASSOCIATED WORK PLAN .............................................................................. 45 1.3.1 Introduction to the IoT4All Architecture.................................................................................... 45 1.3.2 Description of the overall strategy of the work plan .................................................................. 62 1.3.3 Work package and deliverable time schedule - Gantt chart....................................................... 68 1.3.4 Detailed work description broken into WPs............................................................................... 70 1.3.5 Summary of staff effort .......................................................................................................... 137 1.3.6 Graphical presentation of the components showing their interdependencies........................... 139 1.3.7 Risk Management .................................................................................................................. 139 SECTION 2: IMPLEMENTATION..................................................................................................................... 140 2.1.

MANAGEMENT STRUCTURE AND PROCEDURES .............................................................................. 140 2.1.1. Organization structure and decision making mechanism......................................................... 140 2.1.2. Management bodies .............................................................................................................. 141 2.1.3. Decision procedures and conflict resolution ............................................................................ 143 2.1.4. Management of knowledge, intellectual property and innovation related activities ................ 144 2.1.5. Tools and services for management assistance....................................................................... 144 2.1.6. Management processes and management handbook ............................................................. 145 2.1.7. Reporting, Monitoring, Reviewing: towards EC ....................................................................... 146 2.2.

INDIVIDUAL PARTICIPANTS .......................................................................................................... 152 2.2.1. Atos Origin............................................................................................................................. 152 2.2.2. TXT e-Solutions – ITALY........................................................................................................... 153 2.2.3. Centro Ricerche FIAT .............................................................................................................. 154 2.2.4. Diakinisis................................................................................................................................ 155 2.2.5. Ingema .................................................................................................................................. 156 2.2.6. CAEN RFID Company Profile.................................................................................................... 157 2.2.7. Telit ....................................................................................................................................... 158 2.2.8. Insiel ...................................................................................................................................... 159 2.2.9. AIT ......................................................................................................................................... 160 2.2.10.

LiSSi Laboratory ................................................................................................................. 161 2.2.11.

EVIDIAN............................................................................................................................. 162 2.2.12.

Kinamik Data Integrity....................................................................................................... 163 2.2.13.

Institute of Communication and Computer Systems/National Technical University of Athens (ICCS/NTUA) ........................................................................................................................................ 164

Proposal Part B: page 3 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.14.

FORSCHUNGSZENTRUM INFORMATIK AN DER UNIVERSITÄT KARLSRUHE (FZI) ................... 165 2.2.15.

AUEB-ELTRUN.................................................................................................................... 166 2.2.16.

SIGS DATACOM GMBH....................................................................................................... 167 2.2.17.

ESADE................................................................................................................................ 168 2.2.18.

BMT .................................................................................................................................. 169 2.3.

CONSORTIUM AS A WHOLE ........................................................................................................... 170 2.3.1. Consortium composition leading criteria................................................................................. 170 2.3.1. Partner descriptions and roles ................................................................................................ 171 2.3.2. Subcontracting....................................................................................................................... 176 2.3.3. Other counties........................................................................................................................ 177 2.4.

RESOURCES TO BE COMMITTED .................................................................................................... 177 2.4.1. Allocation over project activities............................................................................................. 177 2.4.2. Allocation over cost categories ............................................................................................... 178 SECTION 3: IMPACT...................................................................................................................................... 181 3.1 EXPECTED IMPACT ........................................................................................................................... 181 3.1.1 NEW CLASSES OF APPLICATIONS OF THE INTERNET OF THINGS ...................................................... 184 3.1.2 A GENERIC AND OPEN ARCHITECTURE .......................................................................................... 186 3.1.3 NEW BUSINESS MODELS ............................................................................................................... 188 3.1.4 USE CASES IN SPECIFIC ECONOMIC SECTORS ................................................................................. 190 3.1.5 SUSTAINABLE LOGISTICS ............................................................................................................. 191 3.2 DISSEMINATION, EXPLOITATION OF PROJECT RESULTS, AND MANAGEMENT OF INTELLECTUAL PROPERTY 192 3.2.1. Creating long term value and exploiting the results of IOT4ALL ............................................... 192 3.2.2. Contribution and use of standards.......................................................................................... 194 3.2.3. Dissemination Activities.......................................................................................................... 195 3.2.4. Managing of knowledge and intellectual property rights ........................................................ 198 SECTION 4: ETHICAL ISSUES.......................................................................................................................... 201 ANNEX A: LETTER OF SUPPORT OF ETSI TO THE IOT4ALL PROJECT. .............................................................. 203

Proposal Part B: page 4 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Section 1: Scientific and/or technical quality, relevant to the topics addressed by the call 1.1Concept and objectives 1.1.1 Background & Motivation There have been several definitions for Internet of Things (IoT) in the recent literature. For instance: 

A physical world where everyday objects, rooms and machines are connected to one another and to the larger digital world;



Things having identities and virtual personalities operating in smart spaces using intelligent interfaces to connect and communicate within social, environmental, and user contexts;



A vision of the Future Internet where connecting physical things, from banknotes to bicycles, through a network will let them take an active part in the Internet, exchanging information about themselves and their surroundings;



A global network infrastructure, linking physical and virtual objects through the exploitation of data capture and communications capabilities. This infrastructure includes existing and evolving Internet and network developments. It will offer specific object-identification, sensor and connection capability as the basis for the development of independent federated services and applications.

These will be characterized by a high degree of autonomous data capture, event transfer, network connectivity and interoperability; or the most recent definition chosen for the CERP IoT Cluster of Research Projects on the Internet of Things: Internet of Things is an integrated part of Future Internet and is defined as a dynamic global network infrastructure with self configuring capabilities based on standard and interoperable communication protocols where physical and virtual “things” having identities, physical attributes, virtual personalities and using intelligent interfaces are seamlessly integrated into the information network.

The definition we would like to propose in this project tries to make a synthesis of them and to comply on the one side on the Future Internet movement, on the other side with the ICT WP20092010 objective 1.3: Internet of Things is a perspective of the global Future Internet where physical things are enabled to share their Real World knowledge with virtual things living in the Digital World to enable novel Internet based applications in the Socio-economic World.

Our IoT4All definition is therefore originally characterized by a twofold motivation: i.

IoT is a perspective of Future Internet (FI) and not an integrated part of it. This means that IoT is the FI and grows and develops together with it, with an original viewpoint which sees everything as a Thing (and not in parallel with it). Most of IoT technologies are the FI technologies and will be developed inside in cooperation with the FI movements, i.e. in European RTD together with the more than 90 projects belonging to the FI Assembly. Our assumption is that it does not make any sense to develop a specific IoT network infrastructure (see objective 1.1 in current and previous ICT workprogramme), a specific IoT federation of service platforms (see objective 1.2), a specific IoT Smart Space for users interaction (see user-centric research in several objectives), a specific IoT Contents & Knowledge Management System (see objective 1.5 and 4.3 in current and previous ICT workprogramme), which then would need to be integrated in the FI. Instead, FI research in IoT has a twofold perspective: a. In close connection with other research communities, including the ETPs (European Technology Platforms EpoSS NESSI NEM ISI eMobility Manufuture) and the European

Proposal Part B: page 5 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Economic Recovery Plan PPPs (Public Private Partnerships Factories of the Future, Energy Efficient Buildings, Green Cars), to provide requirements for their research challenges, to verify & validate their outcomes in FI IoT scenarios; b. To develop in IoT research just those specific technologies, protocols, tools which are not foreseen in the research agendas of the other FI communities, but which are essential for the development of IoT in Europe.

The main IoT4All message is: “A single IoT IP is not able to design and develop all technologies which are necessary to build a global IoT-specific network infrastructure. We must be humble and not unrealistically ambitious, if we want to have the European IoT really in place in 10 years time, together with the Future Internet.” ii. The IoT essential value lies in the way it will revolutionize the life of all European citizens and not in its physical network infrastructure (which will be the FI one and not an independent one, as said above). Is the current Internet a real revolution for all of us (researchers, workers, managers, citizens, patients, disabled, …), because it is made of a network of computers exchanging TCP/IP packets? Moreover, seamless integration is not enough, not even transparent interoperability (much more correct indeed). On the one side, trillions of things require autonomy, flexibility and adaptability and not “integration” which simply destroys heterogeneity by law; on the other side not even interoperability is enough, as smart entities are influencing each other when interact and never remain the same (Heraclitus “you cannot step twice into the same water”). Hence, the key research topics of IoT4All will be: a. An osmosis-like multi-layered architecture which will allow a continuous interaction and mutual influence between real, digital and socio-economic worlds; b. A special attention to the final users of the technology, as current Internet history shows that it was not the best designed systems by researchers and engineers which encountered the best success among people and which made the Internet really grow and revolutionize our lives.

The main IoT4All message is: “The success of a brand new set of technologies, like IoT in the FI, is not just in its clean design and development, but mostly in its capability to improve our lives and to have a real socio-economic impact..”

As a consequence of our IoT definition, we could make some statements: a) Firstly, the architectural model of the IoT is not just confined to the Real World of sensor networks, smart objects and connecting things, but it embraces also the Digital World of events, services, actions and controls (virtual things) and the Socio-economic World of work, entertainment and public utility services. This holistic view (everything is a thing) justifies the assertion that IoT is a perspective of the FI and not just a part of it: human beings, computers, objects, sensors, services, events are things and the main challenge is to discover how this new world of things will influence and affect our daily social life and business. b) Secondly, each World has a native population of entities (physical/virtual objects, middleware/protocol tools, socio/economic bodies) who live in a certain intra-world environmental natural space under certain defined rules, policies and conventions: smart spaces for Real World interaction (humans objects devices), software platforms for Digital World integration (F-O-T federated open trusted platforms), social/business workflows for Socio-economic World co-operation (next generation IoT-based enterprise and social applications). c) A third important aspect of such a vision, with considerable implications to the architectural vision, is the presence of an IoT inter-World *ware system (a middleware, an upperware and

Proposal Part B: page 6 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

a crossware) which is not just defining the interoperability of the three Worlds (i.e. exchange of information and use of the information exchanged), but also is able to model and implement the relations and mutual interactions among them, like a semi-permeable membrane supports continuous osmotic exchanges between liquids. Keywords in this respect are: data, information, knowledge and experience: how do they flow through the membrane and influence our society.

1.1.2 Vision & Mission & Concept The IoT4All vision is to go beyond the interoperability among real, digital and socio-economic worlds, where just exchanges of data could occur, but to achieve by 2020 a sympathetic and osmotic IoT Space, where these 3 worlds influence, participate and in some cases cum-penetrate each other. This future IoT Space will finally unleash the potential of the IoT foundational technologies (microsystems, nanotechnologies, wireless sensors, network infrastructure, objects identification, energy saving and harvesting, communication frequencies and protocols) in the meantime developed in different domains, making IoT a resource for all, citizens and companies, governments and enterprises, representing therefore a revolutionary boast towards the society of the future.

Moreover, the IoT4All mission stems upon two main assumptions:  Research about innovative IoT foundational technologies is so complex and multidisciplinary which cannot be performed seriously and with success in just one single IP. It is however a reasonable and feasible objective of a single IP like IoT4All to specify the requirements for FI technologies, to develop the architecture and the tools to make such research outcomes directly and easily adopted and taken up by the Society. Moreover, most of the architectures and technologies are proprietary, owned by multinational big IT companies, and therefore not suitable to be the open foundations for an IoT available for all, mostly the less advantaged citizens, enterprises and governments. 

The IoT is inserted in a movement of more than 90 European projects, named Future Internet Assembly, aiming at finding new technologies and sustainable business models for the Internet of the Future. It is therefore useless and even counterproductive that all the communities of the FI will design and develop their own network infrastructure and protocols, because just one of them will become the FI and there are several projects already allocated to such a task (mostly in objective 1.1 Future Internet Architectures and Network Technologies, in call 5 Novel Internet architectures and technologies & Flexible and cognitive network management and operation frameworks and in call 4 Spectrum-efficient radio access to Future Networks & Converged infrastructures in support of Future Networks). The IoT4All will therefore use all the innovative FI technologies which will be made available by the FI projects, reserving to foundational technologies just some specific resources which will make our test-cases feasible and demonstrable.

In conclusion: The IoT4All mission and main innovation is to study, model and develop the mutual relations among real, digital and socio-economic worlds through an open architecture which will enable novel IoTdriven business applications for the benefits of European citizens and enterprises.

As already mentioned above, our concept of the IoT is based on 3 Worlds:  A Real World where we imagine a physical heterogeneous, interoperable and evolutionary world of inter-connected computers, inter-connected mobiles, inter-connected people, interconnected sensors/actuators and inter-connected objects. In particular, among these not just intelligent products provided with advanced active identification technologies, but also selforganizing sensor networks able to maximize effectiveness by minimizing energy consumption and data storage needs, as well as smart objects and devices provided with advanced communication and reasoning capabilities (i.e. the intelligent fridge, the intelligent car, the

Proposal Part B: page 7 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

intelligent home), as well as integrated working-entertainment-home environments where humans, provided with smart and wearable devices, could interact with the IoT (Ambient Intelligence). Virtual Worlds are also belonging to this space, as emotional experimental facilities characterized by shifting in time (past reconstructions, future projections) and/or extension in space of our experience. Very challenging is also the mutual influence between RW/VW whenever actions are generated in either of them and effects need to be propagated in both, like commanding a switch-on/off in a domotics VW or in a Mixed Reality Plant Supervisory Control; or reporting back in the VW a RW Machine breakdown in a shopfloor or an as-built change in a new hospital construction.  A Digital World where Services are provided & consumed, Events generated & filtered, Actuations inferred & controlled, Knowledge generated & transmitted, Reasoning implemented & explained, by means of an open, secure and privacy-preserving IT infrastructure, enabling the interoperability of Enterprise Collaboration Platforms, Enterprise Applications Clouds, Distributed Manufacturing Facilities and Global Service Delivery Platforms. Such a federated interoperability will be implemented by a next generation flexible and self-adaptive Business Process Management Systems encompassing services-eventsactions life-cycle management, adhoc-mediated-planned collaboration forms, decisionalinnovation-automation cross-organizational workflows, individual-team-community oriented front-ends and workspaces, deterministic-stochastic-fuzzy behaviours. o in the Knowledge field, making for instance things able to share experiences and to become context-aware and intelligent (e.g. smart block-notes for medicine prescriptions to be able to interrupt the current TV program reminding the patient/watcher of his/her duties; intelligent printed machine maintenance manuals able to update their content/bibliography/hyperlinks by inspecting a case base of past malfunctions and diagnosis recovery actions; smart printed delivery schedule or mission navigator of a logistic operator able to change its plan according to environmental and mobility situations) beyond traditional document management systems and search engines.  A Socio-Economic World, not confined to the business-oriented Manufacturing and Product + Service life-cycle, but extended to citizen’s wellbeing and Quality of Life, where the IoT revolution will stimulate the birth of novel business, social and knowledge software applications. o In the Business field, making for instance things protagonist of the decisional processes together with humans and computers (e.g. smart machines concurring to decide the time for a preventive maintenance stop in a shop-floor, smart shelves concurring to decide the price-promotions policies and the re-assortment levels in a Supermarket, smart monitoring environments concurring to decide the visit schedule of a physician in a home rehabilitation program), beyond collaboration and cooperation. o

In the Social field, making for instance things able to find friends in both the human and smart objects constituency, to exchange information with them, to arrange dates and meetings (e.g. a parcel in a warehouse supposed to be picked up yesterday and not yet considered could share its experience with other parcels in similar conditions and propose a solution to the human and computer expert; a car not feeling good with its brakes could ask other cars for past similar experience and report back to the board computer for warnings and alarms; a smart environment experimenting a fall of an ageing patient could get in touch with a specialized centre, send a short movie of the fall and synthesize a convenient voice message to re-

Proposal Part B: page 8 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

assure the unlucky elderly), beyond human-oriented social networks, wikis and chats; The “3 Worlds” Interoperability architecture will be implemented by:  A Business-IT upperware (i.e. the connection between socio-economic and digital worlds) to allow IoT- derived knowledge to influence the innovative social-knowledge-business applications;  An IT-Reality middleware (i.e. the connection between digital and real worlds) to allow relevant field events to be considered and to address commands to the relevant field actuators;  A Business-Reality crossware (i.e. the direct connection between socio-economic and real worlds) which in some cases is able to seamlessly cross the digital world and directly connect the IoT with the Enterprise Environments, i.e. to immediately report serious events to the decision makers and to instantaneously actuate urgent commands from the decision makers to the real world.

A pictorial view of the 3 interconnected World is given here below:

1.1.3 The scientific and technological objectives & expected results The above considerations led us identify 4 Grand Challenges for our project proposal (which will find their development in our main 4 research SubProjects):

Proposal Part B: page 9 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

•

The perception of the Real World is different because of two reasons: every observer has a different sensing capability (Viewpoint, sensors, elaboration, attitude, interpretation make our experience of reality personal and unique. Antoine de Saint-Exupery said “The meaning of things lies not in the things themselves, but in our attitude towards them”) and the observed reality is continuously changing and evolving (Heraclitus said “We exist in a field or continuum in which everything is constantly in flux or process, Πάντα ῥεῖ). In addition, such an interaction between observer and observed is now possible not just in the Real World, but also in the Virtual World or in a mix of the two, when for instance you buy a good in Second Life and you start a set of subsequent physical-digital-economical processes. Another consideration is that in the future IoT, the boundaries between active observer and passive observed thing is blurring, where every entity could be observer and observed thing at the same time, provide-consume services, accept-generate commands, sense-actuate the environment. GC#1: Modelling, Representing & Governing the Observers, the Observed and the Communicating Things in the Real World.

•

Nobody could say that the reality is only one, but we could just share experiences taken from Communicating Things, compare them and extract common knowledge from them. IoT implies that information and experiences flowing between the 3 Worlds (Real-Digital-Social) middlewares are processed and transformed into services, events, actions. For doing that we need a co-operation of different digital platforms: service delivery platforms, event driven platforms, actuation control platforms, knowledge management platforms, context-driven intelligent reasoning platforms, human-things interaction platforms. All of them need to be F-O-T platforms: Federated (not just interoperable, but collaborative), Open (respecting standards and offering open interfaces) and Trusted (where security and privacy issues are managed transparently according to agreed policies) GC#2: Analyzing, Extracting & Managing Knowledge & Experiences via federated platforms in the Digital World.

•

Information extracted from the Real World and transformed into knowledge in the Digital World is then ready to be contextualized in innovative Socio-economic IoT-based applications, by using it for everyday life experience and/or business decisions. We identified three kinds of applications: Realtime sensing applications (e.g. monitoring, diagnosis, filtering, in several domains like plant maintenance, environmental protection, energy management, healthcare) where the major challenge is to support RT critical decisions; Distributed intelligence applications (i.e. planning, scheduling, optimization in several domains like collaborative supply chain management, transportation, logistics), where the major challenge is to solve complex problems by the coordination of several different knowledge and intelligence sources; Smart Ambient applications (i.e. human-computer multi-modal & multi-device interaction, virtual reality, location based services in several domains like e-inclusion, tourism, new product design and development), where the major challenge is to support an easy and effective interaction among things and between things and humans. GC#3: Developing highly innovative networked applications, based on the IoT experience, knowledge and context in the Socio-economic World.

•

Every experience modifies both the observer and the observed reality in a mutual sympathy and reciprocal influence, like a semi-permeable membrane defines the interaction among two liquids or gases. This also applies to our three worlds which are neither to be merged, seamlessly integrated together, nor totally separated and stand-alone, but they are continuously and mutually influencing each other, keeping their independence and autonomy. An example is an event generated at the Real World level and synthesized and contextualized at the Digital World level which is influencing human Socio-economic decisions or a schedule generated by a human decision maker which is able tor each the physical shop-floor of a factory through synthesis of actuations and commands. GC#4:

Proposal Part B: page 10 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Modelling and implementing the information-knowledge-decision osmotic relations among Worlds.

The IoT4All Integrated Project objectives are: i. Design, develop and prototype an open architecture based on open protocols to enable European society at ALL levels to easily adopt and deploy the new technologies at the basis of the Internet of Things. The open architecture will enable a seamless, trustworthy and pervasive infrastructure to bridge the conceptual, applicative and technological gaps between the societal, the information and the physical spaces in enterprise environments.

The technical experience gained from previous FP6-FP7 RTD projects in IoT-related domains (e.g. sensor networks, ambient intelligence, product identification, intelligent objects, smart personal spaces) will drive such an activity. ii. Identify & introduce innovative IoT Technologies into the Real World. Such technologies (in the classes of self-organizing sensors networks, distributed objects intelligence and smart interaction environments) will populate our three test environments (realtime sensing in transportation, distributed intelligence in logistics, smart ambient in assistive technologies) and innovate the Digital and the Societal worlds; iii. Develop & integrate a federation of F-O-T platforms in the Digital World. In particular, we will consider service-oriented cloud platforms to support massive amounts of information, event-driven intelligent platforms to analyse data streams and infer relevant events, personalized and semantic service front-ends to allow human users to easily access the wealth of knowledge generated by the lower level; iv. Design & prototype innovative business- and citizen-centric applications founded on the IoT in the Socio-economic World. In particular, we will take the existing software applications driving the 3 IoT4All scenarios and improve them in the sense of IoT. For the cars realtime remote diagnosis application we will add the dynamic and self-configuring sensors networks in a community of cars; for the supply chain management application we will add the distribution of intelligence in a heterogeneous collaborative decision making process, made of humans and smart containers, warehouses, pallets and items; for the ambient assistive living application we will add the capability of location-based and context-driven services as well as an easy and multimodal human-computer interaction; v. Model and implement the relations and mutual interactions among the three Worlds identified in an open, standard-based *ware system. The real-digital world relations are managed by a middleware which will enable the software platforms to access the wealth of information produced by the things (services, events, actions); the digital-social world relations are managed by a upperware which will enable the three software applications to integrate the F-O-T platforms and run their business processes (e.g. diagnosis, planning, monitoring business processes); the direct social-real worlds relations are managed by a crossware which will enable the innovative software applications to interact in a safe and secure way directly with the things via commands and actions (e.g. switch on/off a sensor, configure remotely a smart container, send a warning message to a disabled or elderly under assistance); vi. Build & deploy realistic things-centred test-cases in business- and social-oriented PPP business ecosystems. The real value of the IoT technologies and, as interpreted in IoT4All project, will be fully unleashed just when they will be able to influence and change our daily life, as citizens, employees, civil servants. Things are entering with their own identities and personalities in our life as full users of our innovative IoT-based applications. Imagine a mixed community of mechanical engineers, car drivers, maintenance operators and cars, all users of the same real-time monitoring application and collaboratively engaged to solve a diagnosis problem; or imagine a community of production managers, logistic operators, containers and parcels, all users of the same outbound inventory management and

Proposal Part B: page 11 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

distribution planning system, to find the best payloads and stock levels for an optimized service; or imagine physicians, assistance operators, caretakers, patients and smart rooms which all collaborate for a better quality of life of disabled and elderly. vii. Measure & demonstrate tangible/intangible Benefits for the EU society sectors derived from the IoT take-up in the three above test-cases. For instance, improve the safety of our cars, diminish cars accidents and failures, offer a better information system to car drivers; eliminate out of stocks at the points of sales, reduce environmental impact of our goods distribution networks, offer more customised and fresh goods to consumers; reduce the hospitalization times and the costs for the community of not-patients assistance, improve the capability of disabled to interact with peers and the society, prolong the life expectancy of elderly. viii. Diffuse & disseminate the project’s Outcomes to the international scientific, standards and industrial communities. Our dissemination strategy will consist of several distinct but interoperable dissemination channels. For instance, as far as the standardisation bodies are concerned, ETSI (see ANNEX A) will support our project and will be part of the Industrial Advisory Board. As far as the International scientific community, ATOS Origin, thanks to its International presence, will design and execute a detailed dissemination strategy determining the appropriate use of the various dissemination possibilities, such as flyers, the support and organization of conferences on the topics and Web-based dissemination of project results such as implemented tools and prototypes. ix. Exploit & impact the Society by demonstrating IoT Best Practices and stimulating their adoption worldwide. We believe that anticipations of the real IoT could take place also in the presence of our beloved current Internet infrastructure, perhaps not in a full global and totally scalable manner. IoT4All will put in place several Training and Exploitation measures in order to impact the society with the outcomes of our project such as specific measures related to the exploitation of project results: While user-centric activities represent the customer perspective, takes concrete steps towards successful exploitation from the point of view of the R&D partners. There are two major factors which determine the impact and thus the exploitation potential of an IP: cost and benefit. Key to exploitation is the project visibility – making prospective users and the potential community in general aware of the project benefits. Within IoT4All we lower the cost of adopting IoT4All technologies by aligning project outcomes with relevant standardization activities.

Proposal Part B: page 12 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

In conclusion, we could put in the following table the S/T objectives of our project.

OBJECTIVES

M24

M36

2 3 5

4 5 8

1 1 3

2 2 5

8 2

4 4

1 1 1 1

3 3 3 3

2 2 3

4 3 4

i. Open Architecture Open standards adopted Open protocols adopted Open Platforms integrated ii. Real World Technologies Innovative hardware technologies Innovative communication protocols Number of User Interaction Devices integrated iii. Digital World Platforms Number of Platforms studied for Integration Number of Platforms integrated Semantic Reasoning Ontologies iv. Socio-economic World Applications Innovative plug-ins for car diagnosis Innovative plug-ins for logistics management Innovative plug-ins for Emergency Management Innovative plug-ins for AAL v. *Ware System Number of standards used in Middleware Number of standards used in Upperware Number of standards used in Crossware vi. + vii Things-centred Test-cases Number of car-diagnosis Smart Things Number of logistics Smart Things Number of AAL Smart Things Number of Emergency Management Smart Things viii Dissemination IoT4All events Number of Delegates IoT4All articles in Journals, papers in Conferences IoT4All newsletter circulation

2 2 4 2

5 4 6 4

50 10 200

200 100 500

ix Impact External Multipliers ETP Addressed Future Internet Working Groups

10 2 1

40 4 3

Table 1.1. S/T Objectives

Proposal Part B: page 13 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

In the following table we also put the Business-Social tangible and intangible benefits derived directly from the adoption of IoT4All solutions: BENEFITS Self-repairing Car Maximise safety, availability and reliability of vehicle, for professional or leisure usage Minimise customer operational costs of maintenance and insurance Minimise company costs for contractual maintenance, assistance and logistics of spare part Sustainable Logistics Monitoring the environmental impact of products- processes on the environment Environmental-friendly supply chain and distribution processes Stimulation of greener consumer demand Ambient Assistive Living Improving quality of life of patients Reduction of accidents Improving the caretaking process Homeland Security RealTime Monitoring & Control of Devices More timely Warning and Alarm Channelling Distributed reasoning and decision making Table 1.2. Benefits Table

Thanks to its first class constituency, the IOT4All consortium is also able to generalize the business objectives depicted above for our 4 test cases to other additional sectors and domains which are in the core industrial business and/or in the primary research priorities of our beneficiaries: Retail, Banks, Public Transportation, Manufacturing, Energy are just some examples of generalization.

Proposal Part B: page 14 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.1.4 Relation to the call objectives The call for Objective 1.3 bullet a) outlines four objectives of which three are relevant for IoT4All. We repeat the three relevant objectives here for convenience alongside their relationship to the project.

Component of ICT Call 5

How the proposed project contributes

Challenge 1: Pervasive and Trusted IoT4All compliance Network and Service Infrastructures 1.

Need to rethink architectures such 1. The IoT4All Real World vision is that of an open that performance bottlenecks are federation of independent, heterogeneous platforms, overcome, a wider variety of service one of them is the IoT. On the basis of the decennial types can be supported, novel types experience in Enterprise Interoperability research (the of edge networks such as wireless Socio-Economic World) of some of its beneficiaries, the sensor networks may be integrated, concept IoT4All would like to study and explore is that a and constraints imposed by new close integration among them is too hard and almost types of media applications such as impossible to achieve. We propose a workflow- and 3D virtual environments can be process- based smooth interoperability paradigm with supported the IoT4All Osmotic Middlewares as mediators in charge of hiding the heterogeneity of the Real World.

Interoperable vs. integrated approach.

2.

These network infrastructures need to support an Internet of dynamically combined services with worldwide service delivery platforms and …..

3.

Flexibly enable the creation of opportunities for new market entrant. The 'third party generated service' is emerging as a trend supporting the move towards usercentric services, as shown by the advances in Service-OrientedArchitectures and in service frontends as the interface to users and communities

Objective 1.3: Bullet a) 4.

Architectures and technologies

5.

Using open protocols,

6.

which enable novel Internet-based applications including – but not restricted to – business/enterprise scenarios.

2. The IoT4All Digital World is addressing the IoServices challenge of the FI, where Global Service Delivery Platforms will play a central role. Global in the sense of ubiquitously accessible by anyone, Service Platforms in the sense that the unifying model will be Service-based (Things seen as Services); Delivery in a more extended sense including also design and development environments 3. The IoT4All Socio-Economic World is addressing the Business challenge of the FI, where new opportunities will be given to the most innovative service providers, those who can interpret the new exigencies of users and communities indeed. New market entrants and SMEs in particular with very specialized niche solutions will be entitled to join the big important IoT projects for enterprises and organizations, thanks to the open and federated approach, which will guarantee unprecedented levels of democracy and equal opportunities for all.

IoT4All compliance 4. IoT4All main objective is to develop an architecture to interoperate the 3 Worlds each characterized by its own technologies..

5. Openness and respect of open standard is at the basis of Iot4All. That’s why we also focus on beneficiaries which could be credible in this respect and in practice.

6. This is key in IoT4All. In order for IoT to be really

Proposal Part B: page 15 of 203

FP7-ICT-2009-5 26/10/09 v1.0 7.

8.

They should use information generated at the periphery of the network from the virtual and physical worlds with aggregation of those, and allow action on the physical world.

Physical world event information are generated by tags, sensors, actuators and wireless devices.

Related processes and applications may be object- or location-centric and cover management capabilities of various classes of events, such as real world events (sensor based), behavioural/people events, or business events.

9.

For business scenarios, traceability networks correlated with logistics and order or billing flows are of particular importance

10.

Optimised technologies covering distribution of intelligence between the edge network and the more centralised business/process information system.

11.

This includes service discovery systems as well as scalable, secure, open middleware necessary to put real world data into the context of various Internet applications with event processing, separation and filtering.

12.

Of particular importance are the integration and interoperability with the mainstream business/process management platforms and tools and the necessary management of varying data ownership across the edge device/object life cycle.

13.

Architectural models enabling an open governance scheme of the Internet of Things, without centralised gatekeeper lock-in of critical business/process functionalities.

14.

If third country partnership is felt

Proposal Part B: page 16 of 203

IP proposal IoT4All

disruptive in our society we need to develop new Smart FI-based Applications. This is also the key message of the FI DG INFSO PPP task force.

7. This bi-directional mode (not just data capture, but also context capture and use of semantics) is one of the key aspects of our Osmotic Middleware. In IoT4All we decided not to address the Virtual Worlds, intended as “out-of-reality� worlds (SecondLife and the like), but the world of Virtual Organizations, Virtual Communities and Virtual Factory is in our DNA indeed.

8. Particular attention in IoT4All is given to the proper interoperability between SOA and EDA orient. This is key for any FI infrastructure and project. In IoT4All we have real fully European leaders in both SOA (ATOS NTUA) and EDA (FZI TXT). Moreover, user- and context-centric behavioral approaches are of fundamental importance in the Smart Spaces interaction (AIT LISSI) and in the Service Front Ends collaborative approaches (TXT)

9. IoT4All Logistics scenario is in place to address traceability challenges. It is worth saying that this scenarios does not come uniquely from the RFID constituency but from one on-going Integrating Project in ICT for Transport about Smart Containers (led by INSIEL EURIDICE)and two IPs in DG TREN (led by BMT) .

This will make the case even more interesting and challenging. In any case, Logistics is one of the four scenarios.

10.Proper distribution of intelligence is not achieved through merging and fusion of the different Worlds (too rigid), not even through just interoperability (where there is exchange and not sharing and cum-penetration).

Osmotic membranes middlewares is IoT4All answer.

11.IoT4All digital World includes several service platforms, each devoted to a specific task. Among the peculiar contributions of NTUA we have a semantic service discovery engine, while among the peculiar contributions of FZI we have a dynamic Complex Event Processing platform.

12.The attention of IoT4All to Business needs and Business Processes is total. ATOS and TXT provide commercial solutions for BP Management and have been recently involved in several research projects on BPM (e.g. COIN ECOLEAD SUPER). Regarding data ownership policies and privacy-preserving middlewares, there is also a solid competency in ATOS and TXT to this respect (e.g.

TRUSTCOM MASTER GEMOM projects in DG INFSO D3 &

FP7-ICT-2009-5 26/10/09 v1.0

relevant by proponents, priority should be for those third countries having established links with the EU in this field and providing mutual benefits, including the U.S., Japan, Korea, China, and India.

IP proposal IoT4All

F5) 13. Several different models will be research, and will take into account the work done until now by ONS, and other standarisation bodies, and propose either a new one or a combination of the above.

14.The International impact of the IoT4All project is guaranteed by ATOS Origin, while the letter of adhesion from ETSI representative Patrick Guillemin will cover the aspects regarding standardization and the relation with previous (CE-RFID GRIFS CASAGRAS) and on-going projects (RACE).

The FI Assembly

How the proposed project contributes

DG INFSO FI Task Force

IoT4All compliance

15.

In the future Internet-based Society, we expect that digital services will become increasingly interlinked with physical environments of individuals, communities, and businesses

16.

European industry and high-level research and education must play their role in preserving and strengthening our competitiveness and our shared European values such as privacy, common history, cultural diversity or social “acquis�

Proposal Part B: page 17 of 203

15.

The IoT4All Service Platforms typologies embed digital services, real world environments, people and communities, content and knowledge in a federated interoperable environment. Moreover, the business motivation is at the basis of all our research and new business models will also be described and experimented in SMEs

16.

It is our internal conviction that an European way towards the FI is possible and that such an European way, in a STEEP sense (social, technological, environmental, economical and political) needs to be implemented by SMEs which are the engine of our economy.

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The CERP IoT SRA was recently officially presented in October in London. The following table shows how IoT4All complies with its technological challenges. It is worth saying that IoT4All is an open-tocollaboration project, in the sense that it is our conviction that a single IP, although important and huge, cannot cover alone all the challenges posed by the IoT. Regarding instead the definition of IoT with all its implications, IoT4All has already expressed its opinion in the previous section 1.1.

Component of CERP IoT SRA

How the proposed project contributes

Chapter 3: Technological Challenges

IoT4All compliance

1.

Identification Technology

1.

IoT4All WP2.1 and WP2.4

2.

Internet of Things Architecture Technology

2.

IoT4All A1, all WPs

3.

IoT4All WP2.2

4.

In collaboration with 1.1 projects (Trilogy Eiffel Sensei 4Ward)

5.

In collaboration with 1.1 projects (Trilogy Eiffel Sensei 4Ward)

6.

IoT4All A1 A2 A3 A4

7.

IoT4All WP2.1 and external collaborations

8.

IoT4All WP 1.2

9.

IoT4All WP 4.2

10.

In collaboration with 1.1 projects (Trilogy Eiffel Sensei 4Ward)

11.

IoT4All WP2.1 and external collaborations

12.

IoT4All WP 1.3

13.

IOT4All WP 6.2 an external collaborations (ETSI)

3.

Communication Technology

4.

Network Technology

5.

Network Discovery

6.

Software and algorithms

7.

Hardware

8.

Data and Signal Processing Technology

9.

Discovery and Search Engine Technologies

10.

Relationship Network Management Technologies

11.

Power and Energy Storage Technologies

12.

Security and Privacy Technologies

13.

Standardisation

Proposal Part B: page 18 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.2Progress beyond the state of the art As a new coined term IoT in the context of the future internet assembly and following the RWI working work, we propose to go beyond the state of the art facilitating a non existing architecture reference.

1.2.1 Future Internet and the IoT State of the Art The IoT4All state of the art regarding the IoT architecture is strictly linked to the FIA (Future Internet Assembly) movement and its more recent achievements.

In the FIA event in Madrid (December 2008), the cross-ETP vision of the FI was presented by the director of Eurescom John Kennedy, who used the metaphor of a Greek temple to explain his vision of the FI. A Future Network Infrastructure (the floor of the temple) will provide the basis for 4 main pillars (Internet by and for People, Internet of Contents and Knowledge, Internet of Things and Internet of Services) on top of which the Future Networked Society (the roof of the temple) will be enabled by innovative, next generation applications.

More recently, the DG INFSO task force on Future Internet, presented at FI Assembly in Prague (Spring 2009), elaborated a Recommendation Report on "Interdisciplinary Research Challenges relating to the Future Internet", where one of the most important concepts is represented by F-O-T Platforms (Federated Open Trusted), which are the basis on which to develop next generation, smart complex systems and applications.

To position Europe as a leader in the Future Internet, we suggest that initiatives in Europe should be centred on the development of Future Internet Federated, Open, and Trusted (shortly, F-O-T) Platforms. A multitude of such F-O-T platforms could constitute the fundamental enablers and the ecosystems of the Future Internet on which existing and new “smart� applications could be built upon. Many different types of F-O-T platforms will be available, allowing specific applications to use the capabilities of one or more platforms depending on their needs1 This statement (see picture below) specifies that the four vertical pillars and the horizontal infrastructure should be F-O-T platforms and that on top of it it is need to develop highly innovative Internet applications for a Smart European Society.

1

Recommendation Report on "Interdisciplinary Research Challenges relating to the Future Internet", DG INFSO 2009

Proposal Part B: page 19 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

FI art Sm i n g Liv

art Sm l t h a He

art Sm rgy e En

FI

FI

Federated – Open – Trusted Platforms

art Sm sport n Tra

FI FI

art e Sm ersiv s m Im pace s

FI

art s S m prise ter En

FI

FI art Sm stics gi Lo

art Sm ?

Another interesting metaphor for the FI was shown by Jesus Villasante and Arian Zwegers (DG INFSO D3) during one 2008 objective 1.2 concertation meeting. The Buddhism vision of an elephant and of a set of observers who try to interpret what they are seeing, in a holistic way, but owing to their partial sensing capabilities they come to very different and divergent conclusions. So, in our case, for IoT researchers people-content-services are all real-digital-virtual things (see the CERP IoT SRA); for IoS researchers people-content-things are all services; for IoC researchers everything is finally a piece of content.

Innovation The basic dilemma is: Temple or Elephant? Zeus or Buddha? Which means: is IoT an independent part of the FI (one of its 4 pillars) or is it a perspective of FI (a viewpoint to the elephant)? The consequences of such a decision are not trivial for a research project. If it is a pillar in the temple, it will share with the other pillars the foundations (i.e. the Network Infrastructure), but it will develop quite autonomously its architectures, technologies and models. An integration point is then foreseen above the pillars, at the level of the lintel of the temple, probably under the form of a generic, common, multi-platform Business Process / Workflow Management environment which will be able to feed the innovative FI smart applications in the roof with Internet by and for People, Internet of Content and Knowledge, Internet of Services and Internet of Things functionalities. If it is a viewpoint of the elephant, such an autonomy of research for IoT is impossible or counter-productive and all the

Proposal Part B: page 20 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

architectures, technologies, models would need to be shared with the other perspectives of the FI (i.e. people, content and services indeed).

IoT4All is not taking a definite position about it, but it will try to be compatible with either paradigm will finally win and be adopted for the FI. However, the reference metaphor will be the temple, but with some corrections.

For sure, we will not invade heavily the Network Infrastructure foundations, but we will provide them with IoT real-world requirements and very specific user-driven technological developments.

We foresee indeed a strict liaison with D1 FI projects like 4Ward, Trilogy, Sensei, Chianti, Eiffel, Socrates (and those that will be funded in call5 1.1) and we already started such a process.

We will then climb the IoT pillar towards the roof, through Real World, Digital World and SocioEconomic World and their respective osmotic middlewares, but not in a full independent way from the other pillars. For instance, in our Digital World, we will have the presence of Smart Spaces and advanced Human-Computer Interaction facilities (Internet by and for People), the presence of Ontologies and Semantic reasoning engines (Internet of Content and Knowledge) and the presence of Service/Cloud computing platforms (Internet of Services).

We will also build the lintel through an original combination of SOA and EDA in user-driven CEP (Complex Event Processing) scenarios.

Finally, we will show at the top of the roof the socio-economic benefits for all the European society, derived from a 360° full adoption in real-life test cases of the IoT as a whole and not just of its technologies and protocols.

Our Motto is:  Wake-up from the basement’s floor!  Climb the temple’s pillar!  Reach the roof’s summit!

Impact The impact onto the European society of the IoT4All architectural choices will be evident in our 4 application cases related to “safer cars”, “sustainable logistics”, “assistive inclusion” and

Proposal Part B: page 21 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

“environmental risk management” and a preliminary estimation of such an impact is already depicted in section 1.1. Moreover, we also aim at generalizing such results to other domains and sectors which are in the core business of our industrial partners and in the first priority agenda of our research institutes (i.e. manufacturing, retail, healthcare, transportation, energy management, etc).

1.2.2 RFID and WSAN in the IoT IoT4All will research and provide a middleware solution for IoT, with a view to facilitating the development and integration of IoT applications. Among the key innovations of the IoT4All middleware solution, will be its ability to support the business, social and technical aspects of IoT applications in a global scale i.e. beyond monolithic scenarios and specific enterprises. Specifically, the IoT4All middleware solution will provide the means for connecting business semantics with lowlevel information stemming from the things, while at the same time enabling business models to drive the configuration of the underlying “things”.

IoT4All will take into account existing middleware solutions for RFID and WSAN (Wireless Sensors and Actuator Networks), These solutions will be extended in order to handle additional devices comprising the IoT4All applications, as well as their business semantics/context. In the sequel we outline the state-of-the are in RFID and WSAN middleware and related tools, while also developing a vision for extending them radically in the scope of the project.

1.2.2.1 RFID Middleware Implementations and Related Tools Several RFID middleware middleware frameworks are nowadays providing functionality for RFID data collection, filtering, event generation, as well as translation of RFID stream into their business semantics. These frameworks have been developed as part of both research initiatives and vendor products. For example, the research-oriented RFIDStack and WinRFID [RFID1], [RFID2] systems deal with the low-level tasks of capturing and filtering RFID events in a scalable fashion. In the industrial world, vendors (e.g., Oracle - Oracle Sensor Edge Server, BEA - BEA Weblogic RFID Enterprise Server [RFID3], Sun Java RFID System [RFID4], [RFID5]), have released middleware platforms, which provide RFID middleware for collecting, filtering and managing RFID data. In addition to commercial RFID middleware products, several open-source RFID frameworks have emerged, such as the RadioActive Foundation (http://www.radioactivehq.org/), Singularity (http://singularity.i-konect.com/), Mobitec (http://mobitec.ie.cuhk.edu.hk/rfid/middleware/), AspireRfid (http://wiki.aspire.ow2.org/), as well as the fosstrak project (http://www.fosstrak.org) [RFID6], which provide royalty-free implementations of RFID middleware stacks. Most of these implementations emphasize on middleware standards specified by the EPCglobal in the scope of the EPCglobal architecture [RFID7] (as outlined in Table 1.3. S/T Objectives: OSS Middleware Implementations of EPC Standards below).

RFID EPCglobal Standards Implementatio ONS ns Fosstrak Rifidi Singularity RadioActive X Mobitec Logicalloy

EPCIS

ALE

RM

LLRP

RP

TP

X

X X X * X X X X X X X X X X X X X X Table 1.3. S/T Objectives: OSS Middleware Implementations of EPC Standards

Along with middleware implementations several projects have also focused on the implementation of tools that facilitate RFID development, deployment and integration. For example the EU ASPIRE

Proposal Part B: page 22 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Integrated Project (www.fp7-aspire.eu), deals with open-source tools for programmable RFID development and end-to-end management of the RFID infrastructure [RFID8]. Also, the Rifidi project (http://www.rifidi.org) provides an open source IDE for RFID. Rifidi lets one develop an RFID system entirely with Software Components and removes the dependency on hardware and infrastructure that RFID typically demands. Moreover, Sun’s JCAPS (Java Composite Application Platform) for RFID (https://jcaps-rfid.dev.java.net) provides tools for facilitating RFID development, though they have not achieved wide adoption.

References: [RFID1]. UCLA WinRFID Middleware. http://www.wireless.ucla.edu/rfid/winrfid/.

[RFID2]. S. Prabhu, Xiaoyong Su, Harish Ramamurthy, Chi-Cheng Chu, Rajit Gadh, “WinRFID –A Middleware for the enablement of Radio Frequency Identification (RFID) based Applications”, Invited chapter in Mobile, Wireless and Sensor Networks: Technology, Applications and Future Directions, Rajeev Shorey, Chan Mun Choon, Ooi Wei Tsang, A. Ananda (eds.), John Wiley (to appear), available at: http://www.wireless.ucla.edu/rfid/winrfid/.

[RFID3]. BEAWebLogic RFID Enterprise Server™, “Understanding the Event, Master Data, and Data Exchange Services”, Version 2.0, Revised: October 12, 2006.

[RFID4]. Gupta and M. Srivastava, ‘Developing Auto-ID Solutions using Sun Java System RFID Software’, http://java.sun.com.

[RFID5]. S. Microsystems, “Java System RFID Software 3.0 Developer Guide,” www.sun.com, Feb. 2006.

[RFID6]. Christian Floerkemeier, Christof Roduner, and Matthias Lampe, ‘RFID Application Development with the Accada Middleware Platform’, IEEE Systems Journal, Vol. 1, Issue 2, pp.82-94, December 2007.

[RFID7]. Architecture Review Committee, “The EPCglobal Architecture Framework,” EPCglobal, July 2005, available at: http://www.epcglobalinc.org.

[RFID8]. John Soldatos, “AspireRfid Can Lower Deployment Costs”, RFID Journal, March 16th, 2009.

1.2.2.2 Middleware for Wireless Sensor Networks The proliferation of WSN (Wireless Sensor Networks) has led to the emergence of middleware platforms, tools and techniques for programming and deploying WSN applications. The diversity of WSN has led to several variations in related middleware platforms. Overall, typical functionality of WSN middleware includes:  Support for services and resource abstractions, which handle internal details of the WSN.  Provision of utilities for developing, programming, deploying, maintaining, and executing/operating WSN applications.

Note that some middleware platforms address only the level of the sensor network, whereas other deal also with devices and networks connected to the WSN (e.g., [WSN-11], [WSN-12]. Some middleware platforms are characterised as sensor databases, other as virtual machines, whereas there are also publish-subscribe [WSN-8], tuple-based, and agent-based approaches.

Systems such as Moteview [WSN-10] and ScatterViewer [WSN-1] are examples of WSN development and monitoring systems, which however provide limited extensibility (tightly coupled approach).

Other environments such as Hourglass [WSN-2], SenseWeb [WSN-3], jWebDust [WSN-9] and GSN [WSN-4], provide more complete development and/or programming environments for WSN applications. Between the bounds/extremes of high flexibility approaches and tightly coupled, there are several other approaches such as TinyDB [WSN-5], Hood [WSN-6] and SNACK [WSN-7], Kairos [WSN-14].

The above list of WSN middleware is representative, yet not exhaustive.

For a complete presentation

Proposal Part B: page 23 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

References: [WSN1]. The Scatterweb wireless sensor network platform, http://www.scatterweb.de.

[WSN2]. J. Shneidman, P. Pietzuch, J. Ledlie, M. Roussopoulos, M. Seltzer, and M. Welsh, Hourglass: An infrastructure for connecting sensor networks and applications, Tech. report, Harvard TR21-04, 2004.

[WSN3]. A. Santanche, S. Nath, J. Liu, B. Priyantha, and F. Zhao, SenseWeb: Browsing the physical world in real time, Demo Abstract, ACM/IEEE IPSN06, Nashville, TN, 2006 [WSN4]. K. Aberer, M. Hauswirth, and A. Salehi, The global sensor networks middleware for efficient and flexible deployment and interconnection of sensor networks, Tech. report, Ecole Polytechnique Federale de Lausanne (EPFL), 2006, Technical Report.

[WSN5]. S. Madden, M. Franklin, J. Hellerstein, and W. Hong, “TinyDB: An Acquisitional Query Processing System for Sensor Networks”, Journal of ACM TODS 30 (2005), 122–173.

[WSN6]. C. Sharp, E. Brewer, and D. Culler, “Hood: A neighbourhood abstraction for sensor networks”, In the Proc. of MobiSYS’04, 2004.

[WSN7]. B. Greenstein, E. Kohler, and D. Estrin, “A Sensor Network Application Construction Kit (SNACK)”, In the Proc. of the 2nd International Conference on Embedded Networked Sensor Systems (SenSys 2004), 2004, pp. 69–80.

[WSN8]. E. Souto et al., Mires, “A publish/subscribe middleware for sensor networks”, In the Journal of Personal and Ubiquitous Computing 10 (2005).

[WSN9]. I. Chatzigiannakis, G. Mylonas, and S. Nikoletseas, “jWebDust : A java-based generic application environment for wireless sensor networks”, In the proceedings of the first International Conference on Distributed Computing in Sensor Systems (DCOSS ’05), 2005, pp.

376–386.

[WSN10]. Moteworks software platform, http://www.xbow.com [WSN11]. C. Curino, M. Giani, M. Giorgetta, A. Giusti, A. Murphy, and G. Picco, TinyLIME: Bridging Mobile and Sensor Networks through Middleware, Third IEEE International Conference on Pervasive Computing and Communications, PerCom 2005, 2005, pp. 61–72.

[WSN12]. S. Eisenman, N. Lane, E. Miluzzo, R. Peterson, G. Ahn, and A. Campbell, MetroSense project: People-centric sensing at scale, In Workshop on World-Sensor-Web (WSW 2006), Boulder, October 31, 2006.

[WSN13]. Chatzigiannakis, I. Mylonas, G. Nikoletseas, S., “50 ways to build your application: A survey of middleware and systems for Wireless Sensor Networks” in the Proc. of IEEE Conference on Emerging Technologies and Factory Automation, 2007. ETFA. [WSN14]. R. Gummadi, O. Gnawali, and R. Govindan, “Macro-programming wireless sensor networks using Kairos”, In the Proc. of the International Conference on Distributed Computing in Sensor Systems (DCOSS’05), Springer, 2005, pp. 126–140.

Beyond the State of the Art IoT4ALL addresses a “things” saturated environment, along with its social and business aspects. To this end, it has to extends state-of-the-art RFID and WSN middleware platforms in order to deal:  With a wide range of sensors, devices, tags, actuators and other “things” of the IoT environments. Current platforms are usually restricted to few homogeneous sets of sensors, while IoT comprises wider range of heterogeneous devices. To this end, additional abstraction and virtualization of resources will be needed.  With business semantics associated with social and business aspects of the IoT. Current middleware platforms deal hardly with business semantics. The business semantics handled for example by RFID middleware such as AspireRfid are limited to specific business domains (such as logistics) and do not capture the people, business and societal dimensions. IOT4ALL will have to specify ontologies beyond the low-level sensor details and accordingly bridge them to the underlying sensor data and middleware.

Proposal Part B: page 24 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.2.3 Trust, privacy & security in the IOT 1.2.3.1

Data Integrity

State of the Art The more people who have access to a document or file, the less you can trust its integrity.

Something I release as being the truth, even digitally signed with my own certificate, can be changed, re-signed, and re-released, apparently as my own faithful document.

Much is made of the use of PKI and digital signatures for increasing security. If I am in an organization and using my certificates for creating digital signatures, and one of my signatures reveals that a document has been changed, I don’t know where the document was tampered. Digital signatures work at a data group level, and are usually applied after a specific time interval from the moment of the file creation.

Time stamping services can only guarantee that a specific file has been irrefutably stamped at a specific trusted time and day. This means that an audit file cannot be time stamped before it has been finished, leaving an unsecured time gap from the moment the file has been created and it is time stamped.

Log management solutions excel in collecting events in real time, in parsing and normalizing information and analyzing the collected information for producing alerts in real time. However, this does not relate to provide integrity protection in any way.

Write-once Read Only Solutions (WORM) devices work very well avoiding that the information that has been written in them is not altered after its addition. Since they treat files as objects and they need to hash them before adding them in the system, continuously appending files such as logs must be "closed" (i.e. finished) before being processed.

One-way hashing is a technology rather than a product. It has a lower computational cost and is fast to apply. However, if the file integrity is infringed, the file as a whole has to be considered tampered.

Innovation and Impact Kinamik’s technology will apply a “digital fingerprint” in real-time, just as events are being generated and registered. This eliminates the unsecured time gap making it virtually non-existent. Furthermore, securing the file down to the event/record level means that if any tampering is detected, only the affected records should be discarded.

1.2.3.2 Access control to information State of the Art In standardization efforts as well as in existing deployments, the focus effort is put on identification and authentication (RFID, biometry, strong authentication with digital certificates).

As a corollary function, the association of secondary authentications after the primary authentication provides the single sign-on capability.

When multi-domain is involved, it’s essentially for identity federation, with architectures and protocols like Liberty Alliance, Shibboleth, SAML 2 as the convergence standard, and WS-Federation.

These standards only apply to authentication and single sign-on.

For what concerns authorization, standardization is still poor. As the most relevant element, XACML is a standard to express security policy rules, associated to SAML 2 as a mean to convey them. WSPolicy is a standard used to convey some security requirements for exchanges with the service provider, but not to describe a policy, and doesn’t provide any solution for the negotiation of the security policy of for its interpretation. Nothing exists to describe what the policy for accessing information means, what its objectives are, or how it can/must be understood by each party.

Proposal Part B: page 25 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Authentication and authorization: the essentials of the security mechanisms

Authentication Authentication

2’ 2

Contrôle Contrôle Contrôle D’accès Access D’accès D’accès control

Service consumer 1

Service Service Service provider provider provider 4

3

Authorization Authorization

In the contrary of authentication, authorization is not enough standardized, not enough understood in multi-domain environments, where all domain are administered independently, and are enforcing a different security policy. As for PKI difficulties outside one unique organization, it is far from being applicable in real-life deployments.

What are the situations were the multi-domain question applies? Enterprises are continuously extending their business processes outside their traditional boundaries to conduct electronic business with partners and suppliers. However, a single organization cannot effectively manage or control a global e-business process end to end, especially when multiple organizations are involved.

Even within the enterprise, different business units often manage distinct sets of users and resources. The deployment of SOA’s or the composition of Web Services are other typical scenarios: the different services can pertain to different companies or entities, with different policies for enforcing the security of each service and the access to the requested information.

Innovation and Impact The expected authorization behaviour in a multi-domain environment

security domain A

Trust

security domain B

Identity Provider

SAML

access control Service Providers

user attributes

Service consumer

Authentication

Authorization

The proof of authentication of a user in a domain, as well as attributes that define his/her profile, are moved to another domain. Based on a trust relationship between domains, the second domain uses the attributes to determine the user access rights to systems and applications. This principle allows each domain to keep the responsibility for administering its users, as well as its security policy The project will implement a complete authorization chain, applicable and specialized for securely retrieving information.

Proposal Part B: page 26 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The access control chain at the core of the project

Policy Policy administration administration point point

Security policy

Decision Decision Decision points points points 2

1

Service consumer SAML AutN + attr

SAML AutZ req / resp

Enforcement Enforcement Enforcement points Enforcement points points points

3

Service provider

The Policy Decision Point is an authorization server. This component uses the well-established standards SAML 2 and XACML. SAML 2 is used for authentication, and to transfer requests between access control building blocks. XACML is used to express security policy statements inside SAML requests, and is at the core of the authorization server.

The Policy Administration Point is the repository of the security policy. The policy model is based on the NIST RBAC standard, extended with the new features, and improved to solve critical deployment issues. The policy server is implemented using web services and an expert system kernel, and administered using a powerful user interface, based on an efficient technology, such as AJAX. Every component of this access control chain is interoperable with standards, and therefore can be replaced by any other conformant ad hoc module, if necessary. This approach allows to create the modularity of the components constituting the chain to control the access to information.

Proposal Part B: page 27 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.2.4 Real World Technologies for the IoT State of the Art Research on IoT components and network technologies is driven by two main goals2: (i) increasing the degree of “embedded intelligence” to be incorporated into physical objects; (ii) allow for ubiquitous networking of embedded intelligence. Several important developments are on course that, in the long term, will make these goals achievable: - New materials, hardware and power technologies will deliver devices (including sensors and actuators) that are as small, cost- and power-effective as required to make embedded intelligence truly pervasive and inexpensive.

- Advances in communication technologies are going to widen the protocol spectrum for both near-field and long range communications, aiming at unified seamless management of shortto wide-range protocols3.

- Networks will evolve into self-organizing and self-repairing architectures, allowing for secure sharing of communication resources, as well as context- and location-based interaction with sensors and actuators.

While research and technological development progress steadily in each field, a reference framework is still missing where the different components and platforms are integrated to support the IoT vision of distributed and networked intelligence. Microsystems research focuses on producing smarter, cheaper and better interoperable devices4, whereas protocols convergence and new wireless platforms aim at supporting ubiquitous and granular device connectivity5.

There is no doubt that parallel development and final convergence of these new technologies will make networks of intelligent objects commonplace. Nevertheless we believe that times are mature to start looking at convergence scenarios, and at how distributed intelligence will change, and be affected by, real world processes.

Innovation In our vision, even if the ultimate technology required for embedded and networked intelligence is not yet there, the main user needs for it must be there. Surely IoT will address or even induce new needs and forge new user communities, that our socio-economic research in WP3.5 will help to identify. But, for the large majority of users, the basic needs will remain the same and IoT will offer newer, easier and more effective ways to address these needs. Cars will still experience failures and containers will still be stopped at terminals: IoT will allow cars to self-repair and containers to selfhandle clearance operations.

Hence IoT4All will evaluate the current status of device, communication and network technologies in terms of their applicability to real-world user scenarios, and will select and integrate key technological components into a framework aimed at embedding intelligence into objects and making them always and everywhere connected.

The Figure below shows how the IoT4All Real-World physical framework will have three main levels, corresponding to three main technological elements: - Devices and microsystems allowing cost- and energy-efficient data and event capture from Real-World things, embedded computation as well as enactment of changes. The aim of our research will be to bring intelligence as closer as possible to the things themselves, by 2

Internet of Things Strategic Research Roadmap, September 2009, CERP-IoT, EC DG INFSO-D4.

E.g., short/medium range: ZigBee, Bluetooth, wide range: GSM/GPRS, UMTS, WiMAX, Satellite.

4 Internet of Things in 2020 - A Roadmap For The Future, European Commission (Infso D.4, Infso G.2 in cooperation with EPOSS), 05 September, 2008.

5 Among others, the DG INFSO Integrated Project SENSEI is addressing these issues, see: “A Framework for the Management of Wireless Network Islands through Dynamic Network Reconfiguration”, www.ict-sensei.org.

3

Proposal Part B: page 28 of 203

FP7-ICT-2009-5 26/10/09 v1.0

-

-

IP proposal IoT4All

integrating low-power chips with smart energy-harvesting solutions in relation to actual demands in computing power, communication and sensing capabilities.

Capillary networks, i.e., self-configuring networks of local devices and sensors connected and remotely controlled via M2M (Machine to Machine) gateways6. The aim is to add scalability to the “every thing is smart” concept by, allowing nearby objects to share their information, join computational resources and optimize their long-range communications.

Platforms, i.e., global communication, positioning and service infrastructures allowing connectivity of devices and capillary networks with remote users and other open and trusted platforms of the Future Internet. In this field, we aim at seamless interoperability across multiple protocols and platforms to make every object, wherever positioned, able to access and provide context-based services through existing (e.g., UMTS, GNNS) and Future Internet F-O-T platforms.

Impact The IoT4All RW Framework will be a key component in all four pilot applications, that are expected to demonstrate significant socio-economic and environmental impact at the European level. Besides, our research on the RW Framework is expected to impact on the ICT industry itself and on the development of related standards. This will be pursued in two ways: (i) by providing user requirements and feed-back from pilot applications to researchers and standardization bodies, both on individual components performances and on overall framework convergence; (ii) by disseminating pilot applications concepts and reuslts since the early stages of development; this should trigger a “snowball effect”, boosting industry investments on key technologies and standards.

1.2.5 Distributed Intelligence and Smart Objects Since the very beginning, the Internet of Things was presented by the International Telecommunication Union7 as the shift from conventional computer networks towards a more pervasive, ubiquitous and intelligent computing and communications infrastructure, enabling things to exchange information in real time, handle requests and react intelligently to changes in the surrounding environment. In other terms, a trend of progressive distribution of autonomy and intelligence towards the edges of the network was identified as result of a close-at-hand technological revolution, pushed inevitably by technology developments:

6

M2M architecture by ETSI TC M2M ad-hoc group.

“UN predicts 'internet of things'”, BBC News 17 November 2005 (ref. to ITU Internet Reports 2005: “The Internet of Things”) 7

Proposal Part B: page 29 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

-

Radio-Frequency Identification (RFID) and related standards, progressing rapidly to become the universal, cost effective means for objects identification and close-range data collection.

- Advanced sensor technologies and wireless networks, providing the ability to detect and handle events in real-time like, e.g., object and environment status changes.

- Embedded intelligence, i.e., computing capabilities inserted into physical objects to give them autonomous behavior and to distribute processing power across the network.

- Miniaturization and nanotechnologies, aiming at progressive reduction in size, price and power consumption, thus increasing the number of connected objects and making the network ever more pervasive and unobtrusive.

This should have changed the computing paradigm by delegating ever more intelligence to the things themselves and by supporting real-time knowledge gathering and conveyance at the point of use.

Experience in both research an industrial pilots has shown that availability of physical components and infrastructures, alone, does not make networks of distributed intelligent objects happen. Smart tags pilot applications have so far been circumscribed to very specific sectors and needs like, e.g., temperature monitoring in perishable goods supply chains (like, e.g., the active RFID technology developed by CAEN in the frame of the BRIDGE integrated project8). “Intelligent” devices are so far synonym of gprs-enabled sensors used, e.g., in toll collection or metering systems, to transmit data to central repositories. Examples include Advanced Metering Infrastructures (AMI) for the energy sector, currently implemented as proprietary platforms with research attempts to make them open and interoperable9.

Innovation Compared to state-of-the-art applications, a paradigm shift is required to achieve true Distributed Intelligence. This implies profound changes that are summarised in the Table below: Current paradigm

Distributed Intelligence

Data origin

User or system generated

Thing/sensor –generated

Interaction paradigm

Organization-to-organization

Thing-to-thing

Information services

Centralized, proprietary platforms

Ad-hoc combination of local (thingcentred), proprietary and global services

Knowledge semantics

Mutually agreed with each partner or between trade community members

Globally established, for any-to-any ad hoc relationships

Event processing

Centralized at organization level

Distributed, may start at object level Event-triggered, localized and (partially) automated decisions

Decisions making

Top-down, centralized decision making, based on periodic data revision

IoT4All has clearly the ambition to support the shift from the current approach, based on centralized platforms with remote sensors, to a world of truly intelligent, interacting and cooperating objects.

The Figure below shows how this requires to work on all dimensions of the IoT hypercube, to achieve two (conceptually) sequential stages in objects’ capabilities: (i) Making the objects smart, by enabling them to: 8 9

BRIDGE Integrated Project, October 2008 Newsletter.

See, for example, the OPEN METER project recently approved in FP7’s ENERGY theme.

Proposal Part B: page 30 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

o

(ii)

Self-identify through global IDs provided by public domain services, allowing seamless and consistent linkage across multiple domain spaces; e.g., a container identified by its serial number, an EPC-compliant RFID code, the IPv6 address of the GPRS/GPS device attached to the container itself. o Interconnect via physical and logical links between related things; e.g., loading operation automatically links container ID with GTIN10 number of the shipped goods. o Provide access to services to authorised users and systems, combining multiple information sources and different viewpoints on the same object; e.g., container positioning service is combined with GTIN information from the supplier to address local Customs request on the contained goods.

Making the objects intelligent, by enabling them to: o Use knowledge, structured into federated and open ontologies, to capture contextual information, mediate across user and business domains and reason on the impact of events and decisions. o Understand their context, in terms of status, location, interacting entities and users, relevant events; e.g., the container locates itself at the destination port, subject to certain customs procedures and under the responsibility of a given terminal operator. o Apply reasoning methods to interpret the context, foresee consequences and act accordingly; e.g., a container uses terminal ambient information to detect risks for its perishable content, and suggests recovery measures.

Digital Dimension

cio mi c So no o Ec

Impact Distributed intelligence will be a key component in all four pilot applications, and will contribute to the expected socio-economic and environmental impact at the European level. Besides, our research in this specific field will contribute to and influence the ongoing efforts of ICT research and industry in some key areas: (i) agent technologies11; the adoption of multi-agent systems is expected to be facilitated by the possibility to associate agents to physical smart objects; (i) new, distributed services platforms, such as EPCIS12, that rely on on-field services access and provisioning by smart objects.

10

Global Trade Item Number Jeffrey M. Bradshaw (1997), Software Agents, The MIT Press 12 EPC Information Services (EPCIS) from GS1.

11

Proposal Part B: page 31 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.2.6 Smart Spaces and User Interaction in the IOT State of the Art Our vision of IoT Smart Spaces originates from the Ambient Intelligence paradigm. Ambient Intelligence refers to electronic and computing environments that are sensitive and responsive to the presence of people. In an Ambient Intelligence world, devices and services interact in a seamless fashion to create a digital ecosystem that supports people in carrying out their everyday life activities. The support is provided in a transparent and natural way, leveraging on information and knowledge that is pervasively distributed in the network connecting these devices and services. The Ambient Intelligence paradigm stems from ubiquitous computing, profiling practices and humancentric computer interaction design and is characterized by systems and technologies that are: 1) embedded: many networked devices and services are integrated into the environment; 2) context aware: these devices and services can recognize individual users and their situational context; 3) personalized: the services can be tailored to users’ needs 4) adaptive: the services can change in response to the context 5) anticipatory: the services can anticipate users’ desires without conscious mediation.

Ambient intelligence is closely related to the long term vision of a Smart Space in which technologies are able to automate a platform embedding the required devices for powering context aware, personalized, adaptive and anticipatory services.

User Interaction is also a core element of a Smart Space. Parallel to the development of the Graphical User Interface technology, natural language processing, computer vision, 3-D sound, and gesture recognition have made significant progress. In addition recent interaction paradigms such as perceptual User Interface (UI), tangible UI and embodied UI open a vast world of possibilities for interaction modalities including modalities based on the manipulation of everyday physical objects such as a bottle and modalities based on the manipulation of a PDA and so on. Moreover the focus of multimodal user interfaces has been extended from purely active modalities, where the user directly and explicitly interacts with the computer, to a mixture of passive and active ones. Passive modalities involve indirect and implicit interaction, in that the computer interprets these as input user behaviour that is not explicitly or primarily directed towards it, for example by using the location of a person walking to work as a cue to update a map on that person’s smart phone. Driven by progress in machine perception and signal processing, information capture via multiple passive modalities now has a strong impact both on the modalities used for system output and on the robust interpretation of multimodal inputs.

Innovation In a smart space devices and services shall adapt to the change in the available resources as well as to the users’ preferences and profiles over time and the physical environments. Obviously, context awareness is central to ambient intelligent media that aims at delivering applications to end-users in a dynamically optimal way, with the best quality possible. Context-awareness is usually implemented by context management and the follow-on context-based adaptation. However, existing approaches to context management: 1) are weak in supporting dynamic context capture at the deep level and in multimodal manners that ambient intelligent media needs; 2) lack effective automatic matching between context and media/service specifications; 3) lack commonality, such as a generic context model, which is needed for context remembrance across applications; 4) have no consideration for new context types, such as social context.

To support the user interaction in Smart Spaces the project will develop a model of multimodal interaction services from an Ambient Intelligence perspective. Various pure or combined interaction

Proposal Part B: page 32 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

modalities for physical objects and mobile setting will be considered, ranging from active (i.e., tangible objects as tools for interaction) to passive (e.g., localisation) modalities. This includes recent interaction paradigms such as augmented reality and tangible user interfaces.

We intend to leverage on the FP6 project OpenInterface (www.openinterface.org), which produced an open source platform for multimodal interaction prototyping and bridged the gap between academic and industrial research. We foresee to extend the OpenInterface platform by integrating Ambient Intelligent services that will implement dynamic selection and combination of modalities to fit and support the ongoing context of use.

Impact Ambient Intelligence is a widely supported and shared vision of the future of computing, telecommunications and consumer electronics for the time frame 2010–2020. The key contribution of the project is to establish middleware for network aware and efficient devices and services that dynamically and adaptively reacts to multimodal context-based user interactions. These development will make significant contributions at European level competitiveness as it aims at 1) becoming a reference framework fostering standardisation and interoperability, and 2) providing a set of primitives and components that allow rapid prototyping of applications in Smart Spaces with Multimodal Interfaces, thusly reducing development costs.

1.2.7 Real World Management & Governance We will have contacts with EPC Global that is leading the development of industry-driven standards for the Electronic Product Code™ (EPC) to support the use of Radio Frequency Identification (RFID) in today’s fast-moving, information rich, trading networks. Verisign, and ETSI. 1.2.8 Socio-economics, Business models & value proposition for the IoT Business Model is a concept that captures how value is created and captured in an organization through a value proposition presented to customers (Chesbrough, 2006). However, academics and practitioners alike often loosely refer to it as “the way a company operates”, for example, Magretta (2002) refers to business models as “stories that explain how enterprises work”. However its first formulation can be traced back to Porter (1985).

Even if other types of business models beyond simply selling products or buying services had been present in markets since long (the razor-blade is probably the most common example). Was the introduction of IT and particularly the Internet, what opened new opportunities. The paradigmatic case has been the one of Google who managed to leverage Google’s success and profit from traffic generated by search. Google practically re-invented the field creating a lot of expectation around it.

Google’s success has been more dramatic because of its ability of not only subsidizing its product, but being able to provide it for free.

This accomplishment spurred the imagination of business from all sectors resulting in new ideas and practices that had and are transforming not only entire sectors of the economy, but also our conception of value.

This is why Business models are nowadays, are also a source of competitive advantage and a way to compete in the market. Therefore, business models evolve and develop inside the firm. Chesbrough (2006) developed a framework that considers six types of business models relating them to how innovation is managed in the firm.

Proposal Part B: page 33 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Business Model

Innovation Process

IP Management

Type 1

Undifferentiated

None

None

Type 2

Differentiated

Ad hoc

Reactive

Type 3

Segmented

Planned

Defensive

Type 4

Externally aware

Externally supportive

Enabling asset

Type 5

Integrated

Connected to the business model

Financial asset

Type 6

Adaptative

Identifies new business models

Strategic asset

Table 1.4. Business Models types (Chesbrough, 2006).

IC technologies played an important role in the development of Business Models because of three important reasons.

1. First, because of their capacity of lowering transaction costs, making possible aggregations that otherwise will not be feasible to address (Teece, 1986).

2. Secondly, because of its ability to organize coordination, effectively substituting layers of managerial structures and allowing the coordination of a large number of participants and contributors at a negligible cost (Shirky, 2008).

3. Thirdly, because of its capacity of transforming rival goods (goods whose stock is depleted when consumed) into non-rival. This is the case of information, books that are rival, once digitalized become non-rival because they can be reproduced at cost zero and instantly.

We have seen the impact of these three transformations in software and in the Internet, allowing new business models and shaping the industry. We argue that the same will be valid in the case of the Internet of Things.

Automatic interaction and identification of customers could allow for the development of scenarios that are simply too costly without it. Such is the case of the introduction and management of flat rates, bonus for attention in shopping malls, customized pricing and discounts, on-the-fly promotions or direct vendor intervention in price fixation.

A good example of how coordination has been substituted in the Internet, is the case of ads, where agencies have lost their privileged situation as intermediaries and click rate has substituted other indirect elements of measurement. Internet of Things can provide similar elements in the real world using, as in the virtual, the capacity of automatic identification of customers and ads.

Also the introduction of these capabilities could lead to personalized information on products and services to customers and professionals in a diversity of environments, from shopping malls to hospitals. That has the potential to change not only the interaction but also the whole supply chain and the role of the intermediaries in it.

All these opportunities, of which we have mentioned some examples, have the potential to change economic and social interactions in the real world in a similar way that we have witnessed in the virtual world because of Internet.

Proposal Part B: page 34 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Exploring and assessing the potential changes, and its magnitude feasibility, while providing clues to industry participants on how to take better advantage of them are the objectives of this area of work. Objectives that will have an impact not only in terms of research in business models and service science but also have the potential to produce a significant contribution in the real world.

1.2.9 Event Driven Platforms in the IoT State of the Art In order to capture relevant changes in a system and respond to those changes adequately, a number of formal reactive frameworks have been proposed. Work on modeling behavioral aspects of an application (using various forms of reactive rules) started in the Active Database community a long time ago. Different aspects have been studied extensively, ranging from modeling and execution of rules to discussing architectural issues [PD99]. However, what is clearly missing in this work is a clean integration of active behavior with pure deductive and temporal capabilities.

A lot of work [MZ95] [LLM98] [PKB07] [BE07] in the area of rule-based Complex Event Processing (CEP) has been carried out, proposing various kinds of logic rule-based approaches to process complex events. As pointed out in [BE07], rules can be effectively used for describing event patterns.

There exist a number of other reasons to use rules: Rules serve as an abstraction mechanism and offer a higher-level event description. Also, rules allow for an easy extraction of different views of the same reactive system. Rules are suitable to mediate between the same events differently represented in various interacting reactive systems. Finally, rules can be used for reasoning about causal relationships between events.

A big portion of related work in the area of rule-based CEP is grounded on the Rete algorithm [For82]. Rete is an efficient pattern matching algorithm, and it has been the basis for many production rule systems (CLIPS13, TIBCO BusinessEvents14, Jess15, Drools16, BizTalk Rules Engine17 etc.). The algorithm creates a decision tree that combines the patterns in all the rules of the knowledge base. Rete was intended to improve the speed of forward chained production rule systems at the cost of space for storing intermediate results. The left hand side of a production rule can be utilized to form a complex event pattern, in which case Rete is used for CEP. Thanks to forward chaining of rules, Rete is also event-driven (data-driven).

Complex Events are specified using event patterns. Event patterns consist of event templates and event operators [LuSc08a]. For this purpose different pattern languages were proposed in the past.

The following paragraphs discuss several event pattern languages and their operators.

An early active database system offering Complex Event Processing is HiPAC [McC89]. It is an objectoriented database with transaction support. HiPAC can detect events only within a single transaction.

Global event detectors are proposed which detect complex events across transaction boundaries and over longer intervals, but no further details are given.

The first event specification language which specified formal semantics is Snoop [CKAK94] and its successor SnoopIB. Snoop provides the well known operators And, Or, as well as Sequence. The remaining operators are: Not, Any, A, A*, P, P* and Plus.

Selection and consumption of events define which occurrences participate in a complex event. Both terms are an integral part of the semantics of an event definition. Selection defines the choice of events if there are more than one event of a required type that have not yet been consumed.

13

CLIPS: http://clipsrules.sourceforge.net/ TIBCO BusinessEvents: http://www.tibco.com/software/complex-event-processing/businessevents/ businessevents.jsp 15 Jess: http://jessrules.com/ 16 Drools: http://jboss.org/drools/ 17 BizTalk Rules Engine: http://msdn.microsoft.com/en-us/library/dd879260%28BTS.10%29.aspx 14

Proposal Part B: page 35 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Consumption is concerned with the deletion of events when they cannot be part of further complex events.

Other approaches to event pattern languages include statements reminiscent of SQL. Two examples are StreamSQL [Stre04] and Continuous Computation Language CCL [Cor08]. Queries in these languages match patterns in streams instead of database tables which is the case for SQL. Queries here are long-running and produce incremental results in contrast to SQL queries. In streaming languages all operators can only be applied to bounded windows of events. Complex events have to adhere to SQL schemata which prohibits nested sets, for example, an events that includes a previously unknown number of constituents. Although the well known syntax of SQL might help with the adoption of these languages, e.g. a seamless integration of an action part seems hard to accomplish.

Innovation Event-condition-action (ECA) rules are considered as an appropriate form of reactive rules. However their use as reactive rules may be very unpredictable with respect to their intended semantics [Kif2006]. In general case, execution of an event may trigger other events, and these events may trigger even more events. There is neither guarantee that, such a chain of events will terminate, nor that states (through which a reactive system passes) are valid.

Further on, two reactive rules with the same execution priority may lead the system to two different states of the whole system. The system cannot be in two states at the same time. Therefore a rule base needs to be confluent (i.e., two rules triggered in an initial state lead the system, not to two, but to a single final state, regardless of the order which any subsequent simultaneously triggered rules are selected for firing). The next issue is the rule ordering (i.e., two rules may produce different effects if the first rule is scheduled before the second and vice versa). Confluence, ordering, and similar issues have been recognised and extensively discussed in the area of Active Databases [Pat1999]. Many different policies are proposed there for solving the issues (e.g., policies for termination, priority and ordering, policies for resolving conflicts etc.).

We believe that semantics of complex relationship inside of an ECA rule, and between rules, should be described formally. In this way, we would establish control mechanism in an ECA system by means of logic rather than by many policies. Instead of a policy interpreter we would use reasoners to keep control in reactive systems.

Instead of logic that may be used for reasoning in some particular state, rather we propose a logic that offers reasoning over all states (which the system goes through). The purpose of such a mechanism is to control state-changing actions, keeping the system always in a consistent state. By executing a set of complex ECA rules, the system changes its states. In this transition, every state in which the system enters, needs to be a legal state. However if the inference engine, searching for a possible execution path, enters to an illegal state such a state-transition should be rolled back. In this way, automated execution of reactive systems should be also controlled in an automated manner.

Therefore we see logic as a viable mechanism to implement such next generation reactive systems.

Further on, our approach is completely put in a logical framework where the same formalism is used for all the three part (event, condition and action). This is very important property since we can reason not only about actions (as in [Beh2006]) or only about events (as in [Bry2007]), but about all three parts of an ECA rule as well as over the whole rule set. This will further allow for discovering new relationship between events, condition and actions. For instance, we will be able to define a composite event with respect to, not only atomic events, but atomic events and actions (e.g., eventA triggers if eventB happens just after actionC or in the middle of a complex actionD).

Therefore, this approach will enable more intelligent processing of event streams, that will support detection of more complicated situations, like detection of unusual situation, or proactive alerting about “interesting� situations that will happen in the near future.

Proposal Part B: page 36 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Impact The overall vision for event processing in IoT4ALL is very ambitious: to support more efficient management of event driven applications, by taking into account that some very strong research results (especially from Active database) are achieved and the industry already started with the adoption of event driven applications. However, in Iot4ALL we challenge several of the premises that these results are based on: 1) ECA (event-condition-action, such as it is) model is too simple presentation of the (intelligent) event processing nature, since it does not correspond directly to the way people are reacting on events: Observe SITUATION, Orient in CONTEXT, decide about ACTIONS, Do (actions); 2) Context plays an important role in even driven applications and the role of an efficient context detection process is inevitable for the efficient event processing; 3) A unified mechanism for formal representing all phases in the reaction cycle is needed for efficient event processing.

All these issues are missing in the scientific literature, which ensure, if planed results are achieved, a significant impact on the research community. IoT4ALL provides excellent research solutions (methods and tools) for them, based on a novel conceptual model for events and conditions (i.e. situation and context), which is well founded in transactional logic that has a scalable implementation. In fact, we can go a step further and say that by using a richer conceptual model for describing reactions on events, we are not any more talking about simple processing of events, but rather about the management of a very valuable knowledge asset of every company (system), i.e. knowledge how to react (make decisions) in event-driven situations.

Finally, we are aiming to the new generation of the event processing platforms which will not just process, but reason about event streams, which is of the paramount importance for the Internet of Things applications, since they will be not only passive processors but intelligent actors in the Future Internet. Additionally, we will consider existing and ongoing standardization efforts for rule interchange on the Web, such as the Rule Markup Language (RuleML, www/ruleml.org) and Rule Interchange Format (RIF, www.w3.org/2005/rules).

References [Ada06] Raman Adaikkalavan and Sharma Chakravarthy. SnoopIB: Interval-Based Event Specification and Detection for Active Databases . Data Knowl. Eng., 59(1):139-165, 2006.

[Beh2006] Behrends E., Fritzen O., May W. Schenk F. Combining ECA Rules with Process Algebras for the Semantic Web. RuleML, 2006.

[BE07] Franรงois Bry and Michael Eckert. Rule-based composite event queries: The language xchangeeq and its semantics. In RR. Springer, 2007.

[Bry2007] Bry F., Eckert M. Towards Formal Foundations of Event Queries and Rules. Second Int. Workshop on Event-Driven Architecture, Processing and Systems EDA-PS, 2007.

[CKAK94] S Chakravarthy, V Krishnaprasad, E Anwar, and S Kim. Composite events for active databases: Semantics, contexts and detection. In VLDB, 1994.

[Cor08] Coral8 CCL Reference, Version 5.2, Online Resource http://www.coral8.com/system/files/assets/pdf/5.2.0/Coral8CclReference.pdf [For82] Charles L. Forgy. Rete: a fast algorithm for the many pattern/many object pattern match problem. Artifcial Intelligence, 19:17-37, 1982.

[Gal02] Antony Galton and Juan Carlos Augusto. Two Approaches to Event Definition . In DEXA '02: Proceedings of the 13th International Conference on Database and Expert Systems Applications, pages 547-556, London, UK, 2002. Springer-Verlag.

[Kif2006] Kifer M., Bernstein A., Lewis P. Database Systems - An Application-Oriented Approach.

Addison-Wesley Longman Publishing Co., Inc., 2006.

Proposal Part B: page 37 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

[LLM98] Georg Lausen, Bertram Ludäscher, and Wolfgang May. On active deductive databases: The statelog approach. In ILPS’97, 1998.

[LuSc08a] David C. Luckham and Roy Schulte. Event Processing Glossary - Version 1.1. Online Resource. http://complexevents.com/2008/08/31/event-processing-glossary-version-11/, July 2008. Last visited: October 2009 [McC89] Dennis McCarthy and Umeshwar Dayal. The architecture of an active database management system . In SIGMOD '89: Proceedings of the 1989 ACM SIGMOD international conference on Management of data, pages 215-224, New York, NY, USA, 1989. ACM. [MZ95] Iakovos Motakis and Carlo Zaniolo. Composite temporal events in active database rules: A logic-oriented approach. In Deductive and Object-Oriented Databases. Springer-Verlag, 1995.

[Pat1999] Paton N. W., Díaz O. Active database systems. ACM Comput. Surv. ACM, 1999.

[PD99] Norman W. Paton and Oscar Díaz. Active database systems. In ACM Comput. Surv. ACM, 1999.

[PKB07] A. Paschke, A. Kozlenkov, and H. Boley. A homogenous reaction rules language for complex event processing. In International Workshop on Event Drive Architecture for Complex Event Process. ACM, 2007.

[Stre04] StreamSQL Guide. Online Resource http://streambase.com/developers/ docs/latest/streamsql/index.html 1.2.10Service & Cloud Platforms for the IoT State of the Art Cloud computing has evolved from a futuristic technology into a commercially viable alternative for companies in search of a cost-effective storage and server solution. It comprises an emerging infrastructural model through which users can gain access to their applications from anywhere, through any connected device. What it aims at is allowing for the efficient and effective management of large numbers of highly virtualized resources as one single resource. In order to achieve this, numerous techniques, technologies and methods are incorporated including resource management, trust enabling, data management, among others.

In the case of IoT4all, the main objective for introducing cloud computing is to enhance the IoT infrastructure with computing and storage capabilities by providing access to a cloud of resources that will facilitate the IoT framework to boost its computing and storage capacity as well as address non-functional requirements such as scalability, robustness and quality of service.

As has been mentioned before, instead of developing and implementing a brand new set of and tools from scratch, IoT4All aims to focus on the convergence and improvement of existing technologies and platforms in order to provide a federated IT infrastructure that will constitute a powerful framework for IoT. In the case of Cloud platforms, rather than developing a new Cloud platform in order support the computing and storage requirements of IoT, existing platforms will be evaluated and weighed against the functional and non-functional requirements of IoT technology as a whole as well as the specific demands of the pilot applications.

These platforms currently incorporate various techniques and technologies for offering dynamically scalable and often virtualised resources as a service over the Internet, including resource management, discovery and scheduling mechanisms, Service Level Agreement (SLA) management, security, data management, portals, among others. Service Level Agreements (SLA) are bilateral contracts between the consumer and the provider of a service setting out the terms and conditions the two parties have agreed upon and, optionally, specifies how the usage of the service is priced. In Cloud environments, SLA contracts comprise a powerful mechanism that Service Providers (SP) may use to offer strong Quality of Service (QoS) guarantees to potential customers and are generally considered to be one of the most vital factors for commercial Cloud applications.

As a result most Cloud platforms have provision for the whole lifecycle of Service Level Agreements [BON07] [ROS09]. This includes negotiation of the agreement between the two parties [HAS07],

Proposal Part B: page 38 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

monitoring of the resources in order to ensure conformance to the terms [SAH03], evaluation of the monitoring results and corrective actions in case of violation [KAR09]. In some cases, SLAs can be used for charging customers for resource usage [HAS07] or for imposing penalties [KOS08] to the provider for not delivering the promised level of service. Thus, SLA management comprises a complex task as it needs to take into account and consequently depends on several factors such as network reliability and availability, system behaviour, external dependencies and even unexpected events.

The dynamic, collaborative and complex nature of IoT poses even stricter requirements for the provision of the requested functionalities through combined services. Service discovery comprises one of the key building blocks of Cloud computing platforms. Its complexity lies on the fact that during this process not only the services that offer the requested functionalities need to be discovered, but also the underlying resources – resource discovery – on which these services are running need to be taken into account based on the agreed-upon SLA and the requested QoS. With service composition climbing high on the hierarchy of required mechanisms for facilitating the IoT requirements, service discovery needs to be built upon highly expressive service and resource querying mechanisms encapsulating and aiming at requested QoS and resource usage optimisation at the same time. Current resource discovery and management mechanisms require further advancements before being able to meet the high IoT demands. The Monitoring and Discovery Service (MDS) from Globus Toolkit [MDS09] is a set of web services for monitoring and discovering distributed resources. Nevertheless, MDS does not offer the flexibility and functionality offered by UDDI [UDDI09] for service discovery. Still, UDDI lacks the required flexibility for registering and managing stateful resources. In general, current solutions are far from being mature enough to provide the basis for the IoT due to the dynamic nature and status of resources which in these approaches are dealt with as static entities, technical constraints and geographical limitations such as autonomous, heterogeneous resources, geographical dispersion of resources, large number of users and large distributed networks, availability status of resources and different technology policies.

Innovation In IoT4All, SLAs will be used in order to establish a level of trust between the owners of the cooperating platforms by setting out the terms upon which the cooperation between the involved parties will be based. The expectations of all parties in terms of performance guarantees and implications in case of non-conformance to the agreement will be investigated and balanced in order to choose the most suitable SLA Management framework. What is more, the SLA Management mechanisms will be adapted to the special requirements of the IoT context. Both the general framework of IoT as well as the particular requirements for the pilot applications will be taken into account in order to define the QoS parameters that make sense in that particular context. Within this context, research will focus on dynamic negotiation (through re-negotiation) based on context and aiming at keeping the optimal balance between meeting the requested QoS and achieving resource usage optimisation. Moreover, QoS and QoE within the IoT will be further analysed in order to provide enriched SLA templates. Given the complexity of the IoT and the variability in the underlying resources, services, applications, systems, and things, special focus will be given on end-to-end SLA monitoring and the development of corrective mechanisms based on well-specified policies, whereas existing billing policies will be adapted in order to encompass QoS, QoE, penalties and satisfy the commercial aspects of IoT. Reputation management will also be considered as another approach for trust establishment and management. Different perspectives of reputation can be met. Sabater and Sierra [SAB05] note that reputation can only be based on what the other agents say about the agent’s behaviour, whereas Abdul-Rahman and Hailes [ABR00] mention that reputation can be viewed as an expectation about the behaviour of an agent based on information about it or observations of its past behaviour.

Within this context, reputation management will be investigated at various levels within the IoT,

Proposal Part B: page 39 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

including computational and data resources, services, systems and things and will form an indirect means of trust establishment and management.

In order to meet the dynamic and demanding nature of continuously evolving applications, work within IoT4All will also focus on introducing innovative resource discovery and management techniques. One of the main challenges within IoT4ALL will be to treat resources as dynamic entities which are able to adapt on the applications’ requirements. Thus, based on pre-defined policies and the application-specific requirements, resources (including data, services, things) will be able to selforganise and self-manage in order to serve the demands of the application. Moreover, research on resource discovery will focus on advanced multiple resource discovery at different contexts.

Resource discovery and management will be tightly bound to the objective of achieving resource utilization optimisation and meeting QoS expectations. For this reason, advanced resource monitoring techniques will be applied which will monitor resources and services. These techniques will monitor resource usage, overall function and will retrieve information on energy consumption.

This information will be fed to advanced models which will describe the “behaviour” of the resources and the services and will further enhance the resource discovery and resource self-management processes.

Impact The IoT4ALL Service and Cloud Platform is expected to offer a key set of mechanisms which will facilitate the IoT computational, communication and storage needs. By incorporating efficient SLAdriven QoS-aware service discovery, composition and management and resource utilization optimisation mechanisms and by enabling end-to-end SLA monitoring, trust aggregation and reputation management as an indirect means for trust establishment, the proposed platform aims at comprising a dynamic, scalable, robust and trusted infrastructure able to support the dynamic, collaborative and complex nature of IoT and the delivery of customisable high added value services.

Given the clear focus for facilitating business solutions, provision for the whole SLA lifecycle with special focus on SLA evaluation and billing policies will further boost the adoption of IoT in the business world through a more robust trust establishment and management approach. It should be noted that the proposed platform will also facilitate the sustainability awareness perspective of the IoT4All platform, by monitoring the available resources’ energy consumption and by incorporating the latter into the multi-parametric resource usage optimisation mechanism.

References [BON07] Boniface, M. J., Phillips, S. C., Sánchez-Mácian, A., Surridge, M., Dynamic Service Provisioning Using GRIA SLAs. ICSOC Workshops 2007: 56-67.

[ROS09] Rosenberg, I., Juan, A. Integrating an SLA architecture based on components, BEinGRID White Paper, 2009.

[HAS07] Hasselmeyer, P., Koller, B., Kotsiopoulos, I., Kuo, D., Parkin, M., Negotiating SLAs with Dynamic Pricing Policies, Service Oriented Computing: a look at the Inside, SOC@Inside'07, 2007.

[SAH03] Sahai, A. Graupner, S. Machiraju, V. van Moorsel, A., Specifying and Monitoring Guarantees in Commercial Grids through SLA, Proceedings of the 3rd IEEE/ACM International Symposium on Cluster Computing and the Grid, CCGrid’03: 292-299.

[KAR09] Kardara, M., Konstanteli, K., Aisopos, F., Andronikou, V., & Varvarigou, T. (2009). A Subscription and Notification Mechanism for Dynamic SLA Evaluation in GRIA. E-Challenges 2009.

[KOS08] Kosinski, J., Radziszowski, D., Zielinski, K., Zielinski, S., Przybylski, G., Niedziela, P., "Definition and Evaluation of Penalty Functions in SLA Management Framework," Fourth International Conference on Networking and Services (icns 2008), pp.176-181, 2008 [MDS09] MDS, http://www.globus.org/toolkit/docs/4.0/info/key-index.html [UDDI09] UDDI, http://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.220041019.htm

Proposal Part B: page 40 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

[ABR00] Abdul-Rahman A., Hailes., S., Supporting trust in virtual communities. In HICSS ’00: Proceedings of the 33rd Hawaii International Conference on System Sciences, IEEE Computer Society, (6): 6007, Washington, DC, USA, 2000.

[SAB05] Sabater, J., Sierra, C. Review on computational trust and reputation models. Artificial Intelligence Rev., 24(1): 33–60, 2005.

1.2.11Service Front-end & Collaboration Platforms for the IoT State of the Art According to the European Commission18 “the software technologies that will be developed for the Future Internet put the user at the centre of attention. The projects classified in "Service Front Ends" share the aim of empowering users to do things which they can’t currently do with software technology” In FP6 the above issues have been mainly addressed by the “Collaborative Working Environments” projects, whose main goal was “to develop next generation collaborative working environments, thereby increasing creativity and boosting innovation and productivity. These environments should provide collaboration services to make possible the development of worker-centric, flexible, scalable and adaptable tools and applications. This will enable seamless and natural collaboration amongst a diversity of agents (humans, machines, etc) within distributed, knowledge-rich and virtualized working environments. Professional virtual communities and nomadic personal access to knowledge should be supported”. One of the major initiatives undertaken by CWE projects was the establishment of an “Open Collaboration Architecture”19 (OCA) Working Group, whose mission is to define the foundational architecture to enable a world-wide interoperable collaboration infrastructure, supported by Collaboration@Rural, CoSpaces, EcoSpace, Laboranova, NEPOMUK, WearIT@Work projects.

Current FP7 Service Front Ends (SFE) projects can be classified into three major categories: 1. Creation of services by the end-user (projects “FAST” and “M:Ciudad”) - Web 2.0 is the trend in the use of internet technology that aims to facilitate creativity, information sharing, and, most notably, collaboration among users. Going beyond this, research into "Service Front Ends" aims to enable users to adapt, customise and control services according to their needs 2. Supporting users that are on the move (projects “Persist”, “OPEN”) - Users are increasingly mobile and require wire-free and nomadic access via a growing number of diversified communications devices and appliances 3. Methodology for developing user interfaces for service oriented applications (project “ServFace”) – Focusing on the software developers, the goal is to provide them with a methodology and tools to develop consistent user interfaces for applications developed in a service oriented manner.

More recently a SFE Open Alliance has been founded by a group of industries and research centers.

The objective of the “Open Alliance on Service Front Ends”20 is to set up an open global alliance aimed to effectively deliver:  a common vision on the technologies and architecture associated to Service Front Ends in the future Internet of Services  open specifications and, potentially, open source reference implementations of components in the envisioned architecture

18

http://cordis.europa.eu/fp7/ict/ssai/service-front-ends_en.html http://www.oca-wg.org/ 20 http://sfe.morfeo-project.org/ 19

Proposal Part B: page 41 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Current members include large companies (Telefonica, SAP, Telecom Italia), Universities (Politecnica de Madrid, TU Wien, etc...) and Research Centers (FhG ISST, ISTI, etc..)

According to their vision, Internet users are expecting that the Web will support their daily life becoming the front-end through which they will get access and mix services (either application services, content/data delivery services) which are truly useful for them, matching their needs at any moment, in a context/knowledge-aware manner.

In their “manifesto”21, the SFE Open Alliance highlight the following current problems: 1. users do not have tools that facilitate the integration of available services into applications that effectively support their daily processes.

2. supporting full context-awareness is still an undelivered promise.

3. users do not have tools that enable them to share the processes they have implemented with other users 4. trying to evolve towards a Service Oriented Economy will need a necessary paradigm shift from selling products to offering services.

The SFE Open Alliance thus identifies the following “principles” for future SFE projects to go beyond State of the Art: 1. End-users have to be fully empowered, so they are able to setup their own web access point to content and application services by means of picking and assembling web resources (e.g. gadgets) available on the Internet ("LEGO" philosophy).

2. Active participation in the future Internet has to be enabled by allowing the end users to create the applications as well as gadgets they want to provide. Sharing and exchanging knowledge, gadgets and applications with others is seen as an accelerator to the adoption of innovations, 3. Interaction must be seamlessly adapted and relevant to context at any time, giving the term "context" the widest possible meaning, 4. Access to sustainable business marketplace of services must be supported 5. Trust and reputation mechanism must be supported Their vision is represented by the following picture:

Innovation In IOT4All we will innovate SOTA in the following areas:  The extension of the SFE concept to the IoT: an IoT-oriented SFE needs to provide users with special services for Real World events and actions, such requirements are not taken into account while working with “classical” digital services. Current SFE solutions risk to fail making the wealth of knowledge generated by Things available for users, especially nomadic and mobile users 21

http://sfe.morfeo-project.org/wp-content/uploads/2009/05/sfe-open-alliance-manifesto-v2-09-05-12-final.pdf

Proposal Part B: page 42 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

 By enabling the concept of Thing-to-Thing collaboration, thanks to the generation of workspaces for Things and not just for human users. In fact, the IoT will pose additional challenges for Things to be enabled to work with other Things, i.e. to be able to generate their workspace, mostly made of services and not of Human-Computer Interface primitives Such innovation will be made possible thanks to the development of an Open Collaboration Architecture, leveraging on the previous work of the OCA working group22, and thanks to the development of innovative IoT Open Collaboration Services, which will enable the current socialknowledge-business collaboration paradigms accessible by Things Impact Thanks to the new concept of SFE for Things and Thing-to-Thing collaboration, the Internet of Service will be dramatically extended and expanded by the presence of trillions of things. Humans will be able to collaborate with Smart Objects and Sensors Networks to find a solution of a diagnosis problem or to find the optimal itinerary for some perishable goods or to take the best decisions in an assistive or emergency management scenario.

Moreover, the proposed solution will enable Things to communicate and to access needed services: for example, what services could be accessed at a certain instant by the Intelligent Car to find diagnosis hints and solutions? Or what services could be accessed by the Smart Container to report an anomaly in the itinerary or to double check some policies and rules?

For instance, services which would allow the creation and govern of a virtual community of cars (social); services which would allow the representation and sharing of multimedia material among Things (knowledge); services which would allow the set-up of a virtual organization of Things, humans, companies to face business opportunities (business).

1.2.12Semantic Reasoning in the IoT Semantic Knowledge Management using Production rules is looking for mechanisms and models to formalize and reason with domain knowledge using logic and logical inference. Production rules reasoning system makes use of an “inference engine in which the ”condition” part of the rules are unified with the facts proper to the system. The production rules paradigm conforms to the classic “if/then” rule format. If the unification is successful, the corresponding rule “fires” and new knowledge (inference) is derived by executing the operations proper to “action” part (the consequent) of the rule. It is then obvious that the inference engine plays a central role in any system that makes use of business rules according to the production rules paradigm. Moreover, we can note that – independently from the specific business rules applications – “rules” and “production rules” play a fundamental role in many other scientific/technical domains.

In these last years, we observe an explicit adhesion from researchers to the semantic web community projects (ontology research field and reasoning on the web), and the standardization efforts (R2ML, OWL). For example, interoperability is one of the primary goals of the Semantic Web research and the work on rules and on their standardization represents a key move towards the realization of that goal, eg it is used for the discovery and the composition of web services using the CLIPS rule engine. Discovery is realized through the matching between semantic search queries and OWL-S descriptions of Web services, and composition algorithm is based on the rules which are considered as composite services or template where the premise part of a rule contains a set of conditions.

22

http://www.oca-wg.org/

Proposal Part B: page 43 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

But, the weak support tools for the development of rule bases requires seriously to find new ways to standardize and enhance rule languages that allows to cope with IoT semantic knowledge management and reasoning issues. For example, the lack of the notion of ‘variable’ in OWL makes it very difficult to rely on the W3C languages in their ‘native’ form to build up ‘real’ inference engines for rule processing. For practical applications, especially in the IOT industrial context, a solution to the problem of finding an efficient ‘rule engine’ for executing the so-called ‘business rules’ consists then in making use of ‘expert systems’ tools like JESS. However, the situation in the Semantic Web rule domain is still particularly moving, in spite of the emergence of several “ reasoner” like RACER, Pellet, Fact++, KAON, JENA, Hoolet and so on that, all based on the weak “inference by inheritance” reasoning paradigm, can only solve, in practice, the most common classification (“subsumption”) problems. We can also note that, in a strict W3C languages OWL, RDF(S) context, building up ‘true’ rule systems is a really complex task given that i) on the one hand, the lack of the notion of ‘variable’ in OWL makes it impossible to rely on this language in its ‘native’ form to build up ‘real’ inference engines for rule processing, and ii) on the other hand, no support for rules and rule processing has been introduced in the standard descriptions of these languages at the time of their conception. The consequence is that the whole Semantic Web rule domain seems to be in an early stage of development. Languages like the Semantic Web Rule Language (SWRL) – all based, roughly, on extensions of the inferential properties of Horn clauses and (Unary/Binary Datalog) to deal with OWL-like data structures appear to be, for the time being, as quite limited with respect to the range of their possible applications and particularly complicated to be used in practice. In this paper we propose a rule language along with a knowledge representation model called Semantic Micro Concept, to write business rules for the management of objects in a closed and industrial environment. Our proposition is motivated by the fact that we need to recover to some issues related, for example, to the efficient handling of syntactic/semantic structures in business rules, handling properties with multiple values; interoperability between heterogeneous management systems, etc.

The first ambitious RTD objective concerns the proposition of reasoning templates that allows the existence of Intelligent and smart things with reasoning capabilities and decision making processes, which makes call to production rules in order to derive high level and complex facts or react by launching a task concerning the semantic of a particular situation. The reasoning system will makes use of semantic knowledge modelling capabilities and matching mechanisms regarding production rules and the description of IOT things. The innovation behind semantic web is the use of AI based reasoning mechanisms to support uncertainty of collected facts and to optimize the composition and matchmaking processes.

The second ambitious, RTD objective of Iot4all in the reasoning part, consists in trying to build a complex events inference framework where it is possible edit complex rules written in a (sort of controlled) business oriented natural language that can bed converted on the shelf into an executable format like that proper to R2ML, DROOLS or JESS. This is the option chosen, e.g., by Graham Witt who is actually publishing a series of articles about “A Practical Method of Developing Natural Language Rule Statements” in the “Business Rules Community” journal. It is also the option that we will propose some concrete solutions in the “NL Business Rules” domain.

Proposal Part B: page 44 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3S/T methodology and associated work plan 1.3.1 Introduction to the IoT4All Architecture The 4 dimensions23 of the IoT hypercube are the Real World Dimension (RWD), the Digital World Dimension (DWD) and the Socio-Economic World Dimension (SEWD), and last but not least the sectors and targets that this hypercube is targeted to, thus the spherical dimension surrounding the hypercube is what we call the fourth dimension.

23

"An attempt at visualizing the Fourth Dimension: Take a point, stretch it into a line, curl it into a circle, twist it into a sphere, and punch through the sphere." — Albert Einstein

Proposal Part B: page 45 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.1.1 The Real World Dimension Motto: Every Thing is Smart From IoT Technologies to IoT Space: the foundational technologies for the IoT (wireless sensor networks, microchips, active RFID, communication protocols) should be available for all and not the subject of self-referencing research. In the Smart Spaces, enabled by the IOT4ALL architecture and middleware’s, human users are immersed in the real & virtual world and enabled to interact with it.

The Real World Dimension exhibits a real heterogeneous, interoperable and evolutionary world of inter-connected computers, inter-connected mobiles, inter-connected people, inter-connected sensors/actuators and inter-connected objects with identities.

In particular, among these not just smart products/systems provided with advanced active identification technologies, but also self-organizing sensor networks able to maximize effectiveness by minimizing energy consumption and data storage needs, as well as smart objects and devices provided with advanced communication and reasoning capabilities (i.e. the intelligent fridge, the intelligent car, the intelligent home), as well as integrated working-entertainment-home environments where humans, provided with smart and wearable devices, could interact with the IoT (Ambient Intelligence).

Virtual Worlds are also belonging to this space, as emotional experimental facilities characterized by shifting in time (past reconstructions, future projections) and/or extension in space of our experience.

Proposal Part B: page 46 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.1.2 The Digital World dimension Motto: Every Thing as a Service From Software Platforms to Knowledge/Experience : federated, open and trusted (F-O-T) platforms are the basis for the Future Internet. In the IoT, particular importance is given to service/cloud platforms, event-driven platforms and service front-ends platforms. The IOT4ALL architecture and middleware’s will be able to transform the data and information sensed and gathered from the real world into knowledge and experience useful for all, and for the innovative socio-economic applications in particular.

Knowledge

Architecture & MDW’s

Events & Services

Eventdriven platform Service and Cloud Platform

Digital Dimension

FrontEnd Platform

The Digital World Dimension contains the two main blocks of services and events where services are established & provided, events generated & filtered, actuations inferred & controlled, knowledge generated & transmitted, Reasoning implemented & explained, by means of an open, secure and privacy-preserving IT infrastructure, enabling the interoperability of Enterprise Collaboration Platforms, Enterprise Applications Clouds, Distributed Manufacturing Facilities and Global Service Delivery Platforms. Such a federated interoperability will be implemented by a next generation flexible and self-adaptive Business Process Management Systems encompassing services-eventsactions life-cycle management, adhoc-mediated-planned collaboration forms, decisional-innovationautomation cross-organizational workflows, individual-team-community oriented front-ends and workspaces, deterministic-stochastic-fuzzy behaviours.

Proposal Part B: page 47 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.1.3 The Socio-economic World dimension Motto: Every Thing is a User From Innovative Applications to Democratic Governance: the IoT revolution should impact the socio-economic world; otherwise it is just a useless exercise by few experts. The major innovation in this respect is the fact that things must become protagonists of our life and in particular become users of our daily software applications. Cars could by themselves take part in the diagnosis and maintenance programs; parcels and containers could self-plan and schedule their shipment and distribution along the supply chain; home appliances in smart spaces could detect anomalous events and help physicians in the assistive and recovery tasks in the presence of elderly or disabled. The risk of such an invasion by things into our socio-economic world is some kind of anarchy. We need new business models and governance rules, which on the one side will give order to this potentially chaotic environment, on the other side will preserve the inherent democratic and participative attitude embedded in the IoT concept.

Availability ubiquity and simplicity Energetic and economic sustainability Security privacy and Trust

Business & Social

Architecture & Conceptual

Governance

SocioEconomic

The Socio-Economic World Dimension, not confined to the business-oriented manufacturing and product + service life-cycle, but extended to citizen’s wellbeing and quality of life, where the IoT revolution will stimulate the birth of novel business, social and knowledge software applications.

Next generation Enterprise Applications will have on the one side direct real time connections with the real world, assuring a prompt and adaptive reaction to events and safe and secure actuations; on the other side they will implement their workflows as loosely coupled orchestrations of services provided by F-O-T platforms. The Socio-Economic dimension will also address the challenges of provisioning, management and governance of these next generation applications, guaranteeing the proper levels of data protection, privacy and AAA security.

Proposal Part B: page 48 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.1.4 The Architecture & Middlewares block Motto: Every Thing is Experience At the center of this IoT Hypercube it is the architecture and the middleware’s that provide the glue/interoperability between the edges of the cube. Consequently, the not yet established, implemented and standardized architecture of the Internet of Things is at the heart of this project.

The interoperability of the three dimensions will be guaranteed through an appropriate architecture addressing: The IoT architecture enables that information and experiences (e.g. sensor data) are processed and transformed into services, events and actions. For doing that we need a co-operation of different digital platforms: service delivery platforms, event driven platforms, actuation control platforms, knowledge management platforms, context-driven intelligent reasoning platforms, human-things interaction platforms. All of them need to be FOT platforms: Federated (not just interoperable, but collaborative), Open (respecting standards and offering open interfaces) and Trusted (where security and privacy issues are managed transparently according to agreed policies).

In particular there is the need for a Business-IT upper-ware (i.e. the connection between socioeconomic and digital worlds) to allow IoT- derived knowledge to influence the innovative socialknowledge-business applications;

There is the need for an IT-Reality middleware (i.e. the connection between digital and real worlds) to allow relevant field events to be considered and to address commands to the relevant field actuators.

And there is the need for a Business-Reality cross-ware (i.e. the direct connection between socioeconomic and real worlds) which in some cases is able to seamlessly cross the digital world and directly connect the IoT with the Enterprise Environments, i.e. to immediately report serious events to the decision makers and to instantaneously actuate urgent commands from the decision makers to the real world.

Ultimately information extracted from the Real World and transformed into knowledge in the Digital World is then ready to be contextualized in innovative Socio-economic IoT-based applications, to be used for everyday life experience and/or business decisions.

Proposal Part B: page 49 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.1.5 The fourth dimension Scenarios This spherical dimension surrounding the converging architectures is the application to real sectors and domains. For that purpose we are trying to cover a full range of applications that could potentially cover all the aspects of the business and society range of sectors. In particular, we are going to develop:

1) Storyboard of self-repairing car scenario FIAT will apply the IoT4all architecture to the Automotive Application, enabling the collaboration between on-board systems, neighbouring objects to the vehicle and remote external services. It is based on web-services and integrates elaborated mechanisms to support recovery processes.

The flexible process management system is based on adaptive and self-healing web-service composition mechanisms, to support recovery execution when basic on-board recovery cannot proceed correctly. It is based on cause-action mechanisms, identifying faulty or degraded services, and adjusting the process execution through dynamic planning mechanisms in order to reach the repair process goals. Such flexibility allows managing many types of exceptions in processes and raises demanding research questions since web services have both permanent and transient faults.

A service-based gateway towards the electronic control units (ECU) of the car will be created, and a high-level repair management system based on processes composed of web services will be provided, coordinating the collaboration and interaction between: 

On-board OEM devices, such as ECUs,



On-board specific diagnostics and maintenance systems



On-board/ off-board objects, in the neighbouring cloud to the vehicle, with different level of intelligence, sensing, memory and communication capabilities, such as infrastructure equipment (e.g. sensors embedded in the road), RFID tags (e.g. attached to the vehicle components), incoming vehicles providing additional data (related e.g. to traffic, road status, environmental conditions), professional or customer devices (e.g. PDAs, smart phones providing further data to understand context and causes)



The driver of the vehicle equipped with human-machine interface, to provide additional input and support for interaction;



External services.

Such high-level recovery processes will assist the car and the driver on the road to recover from situations which might be annoying for the driver, such as continuous alarms for minor faults while driving, or blocking the car even when failures are not critical for safety. They will provide interaction with repair shops, remote assistance, advanced diagnosis, and software upgrades.

Proposal Part B: page 50 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The goal is to prevent specifying handlers for all possible exceptions in the processes, through a flexible on-board execution mechanism of such processes with a self-healing and adaptive behaviour.

The following paragraph describe the likely story of a professional user of the IoT4all industrial platform: The Automotive application settings is the usage phase of the lifecycle of Smart Products. In this scenario, Smart vehicles are equipped with Blue&MeŠ, a on-board telematics platform able to interact with the driver through vocal and textual channels, with neighbouring objects and services through wireless channels and remotely with external service providers.

Michael is a deliveryman for a florist. He usually uses a brand new IVECO Daily (still under warranty).

For planning and optimising his deliveries, he needs a constant availability of the vehicle and would appreciate to be warned of any incoming failure.

When receiving the vehicle, Michael has asked for a constant monitoring of the vehicle status, consumption and use over the complete life of the vehicle. As a counterpart for driving data to be recorded, he has access to different services, in particular the online diagnostics and recovery.

Figure 1. The IoT4all Smart Vehicle (IVECO Daily) Today Michael begins around 9.00 his daily delivery tour of Piedmont: he is delivering in an area North-East of Turin, up to 150 kms from Turin. Entering the vehicle Michael is automatically identified: with his ID and rights, he has access to all functionalities of the vehicle, which becomes an extension of his office.

As Michael turns on the key, the vehicle welcomes him and the body computer performs the usual check-up of the vehicle and components health, interacting through the vehicle wired networks with on-board electronic control unit (ECU). Major pieces of information are resident in the vehicle or available in central databases[1]: Vehicle identity (VIN), Updated structure of the vehicle (BOM), Maintenance history (planned/ unplanned interventions, components substitution, date and place‌), Version of software for ECUs. Through the Blue&Me, added critical information is retrieved wirelessly: the pressure of tyres using dedicated sensors; the availability of spare wheels using embedded smart tags; the destination list from the PND; the type of goods in the vehicle.

While travelling, the Blue&Me gets access to information coming from other vehicles or from the infrastructure and embedded in tags and systems along the road. In this case, an RFID located inside a road sign warns of road works for the next 500 m. The vehicle proactively initiates a recording of some driving parameters and in particular the vibrations in the engine compartment[2]. Shortly after the road works, the vehicle registers a series of error on the dashboard display and in the electric network. The Blue&Me interacts vocally with the driver to evaluate if he had noticed a problem related to the display. In fact Michael had noticed the on-going blinking of the headlights warning light. As the Blue&Me, in collaboration with the body computer do not spot any other major dysfunction, they advise Michael to go on.

While Michael continues his journey, the Blue&Me interacts with the remote servers and other vehicles to understand if the problem has occurred in the same context for similar vehicles.  Smart Product (Blue&Me): ok, we see the problem: most probably a parking sensor is loose, probably caused by the vibrations and the bad road conditions. No actions should be taken for now, as it does not create any safety problem but mention the problem tonight to your fleet maintenance operator. I will do it as well on my side, so that they book one hour and check of they have a spare sensor.

[1] [2]

using the VIN. and also in the trailer.

Proposal Part B: page 51 of 203

FP7-ICT-2009-5 26/10/09 v1.0



IP proposal IoT4All

Michael: ok, thanks. I’ll do that.

Halfway back to Turin, around 17.00, the dashboard lights twinkle and then switch off. Michael stops at the nearest emergency area and activates the Blue&Me for diagnosis.  Smart Product (Blue&Me): we’ll try together to recover from here. But just in case I have prealerted the nearest workshop with your model of dashboard. They also have somebody to work on it tonight. If they stick to the official timing for maintenance it should not take more than 90 minutes for substitution. 

Michael: thanks, proceed with the onboard recovery.



Smart Product (Blue&Me) (after the operations): together with the IVECO central server for remote update, we have managed to recover the lights. You can safely proceed to the workshop we had mentioned. Costs will be charged on IVECO.



Michael: super. I’ll do that.

Finally Michael arrives at the selected workshop. The Blue&Me identifies it and proactively transfers via WI-FI the ID of the vehicle, the relevant data for diagnosis, both pre- and post-failure, the history of maintenance and repair and other contextual data.

Registration is reduced to handing over the keys and signing the approval for maintenance. Actually the vehicle has not yet stopped in the workshop and the staff at the garage is already, from remote, 1) analysing the diagnostics data and 2) afterwards connecting to the vehicle networks.

After a long day, continuously supported by the vehicle, Michael can safely return home.

Technical challenges to be addressed Today web services for cars are in their infancy and are basically oriented to infotainment applications. Some of these services exist already, such as MapPoint .Net, which allows users to access maps in their dashboard displays. Microsoft partners are working on other possibilities, such as services that will allow users to check traffic, weather, gas prices and restaurant menus from the privacy of their own vehicles while for example in Japan, there's even demand for in-car karaoke systems. Today web services for cars are oriented to provide information to the drivers, tomorrow web services will be oriented towards the car itself and to its components, a revolutionary approach that will be undertaken step by step by this project. At the vehicle level, the main challenge is to beyond the physical networks already level (CAN-busses) and create an architecture enabling discovery of objects and services, to sustain the proactive collaboration between different level of intelligent objects, and to create, enrich and distribute knowledge between these objects.

The approach is based on the original idea of providing adaptation and self-healing mechanisms based not only on context knowledge, but also on diagnostic techniques to provide explanations of the possible causes of events, therefore giving an interpretation of the environment in which the services are being executed. This interpretation allows both an improved reaction to failures (since repairing does not only focus on the failure but on its causes and consequences) and also the possibility of adapting the service compositions by exploiting the augmented knowledge about the execution environment. The application will apply model-based distributed diagnostic algorithms for supporting diagnosis in processes where services cooperate in an open world assumption, and in which limited knowledge is available about the internal structure of external services. A model-based approach is also proposed for obtaining a lively service behaviour based on knowledge of causes of failures or possible failures in a set of cooperating services. The focus will be on establishing cooperation methods compatible with an autonomous behaviour of each service. Open source web service technology will be augmented with self-management functionality which allows the control of repair actions, adaptation actions, and testing and monitoring services. In particular, the problems posed by services being executed in micro-environments, in which computational resources can be limited, will be studied. Service execution in real time environments and web services as support for

Proposal Part B: page 52 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

embedded systems will be investigated, in particular in the chosen test-bed in the automotive domain. In fact, the interaction of internal devices in a car with external services in more powerful computational environments and with other service providers (e.g. for maintenance) appears particularly promising. Research to provide self-managing services in small devices will be performed to make the environment applicable also in composed services where services in small devices and in traditional environments cooperate.

This application will build innovative and resilient services for the Self-Repairing Car, and in particular:  Apply methodologies to create, maintain, improve and communicate knowledge;  Aggregate, analyse, display and refine knowledge coming from different sources (things, people) and through different means (wireless/ wired, vocal/ textual…)  Fuse and resolve conflict between data coming from different internal and external sources;  Refine and adapt strategies according to the context of use;  Provide a resilient, safe and efficient services framework, also in case of network failure e.g. by distributing and sharing information between objects in the Internet of Things (smart phones, ECUs, tags, etc).  Use the IoT4all platform for discovery and integration of new objects, interaction and collaboration of different levels of intelligent objects Scenario/prototype typology This application will provide a unique opportunity to consolidate and bring to maturity the ideas underlying cause-based service management. The application of the approach is very wide, integrating on-board systems, the cloud of objects surrounding the vehicle in the Internet of Things and web services on external servers. The achievement of the goals is enabled by expertises in multidisciplinary areas that indeed require a European dimension.

The application will need new techniques which have high impact, but high risk, since these techniques imply a complexity which needs further fundamental research (both on the modelling side and on scalability). The application will test the innovative IoT4all technologies with a wide applicability and cost effectiveness, since it will reduce both design efforts and trial-and-error repair and adaptation, while current approaches focus more on symptoms than causes.

A robust environment for adaptive web service execution, based on adaptation and self-healing functionalities will have several important impacts in e-service technologies for the next decades.

Quality of service, together with service reliability and availability (guaranteed by design for selfhealability and by monitoring and recovery in case of failures) will impact significantly the use of internet and the web at various levels.

This will be demonstrated in the automotive domain in which many malfunctions of a vehicle (due to the increase of electronic and firmware on board) can be often caused by software problems and can be repaired by software actions.

Impact in either society or industry The integration of objects in the Internet of Thing inside the well-known processes of tele-diagnosis and workshop tele-support opens new areas of businesses of a magnitude still to be assessed. On an industrial perspective the impact of such a project can be very high in future reducing of more than 50% costs related to car stops and dysfunctions. They include advantages for the customer and for the company:

Proposal Part B: page 53 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All



Safety and availability of vehicle will be increased. The latter is of paramount importance for professional users, where a day at the garage can cost up to thousands of Euros;



Operational costs will be reduced: in 50% of the cases, vehicle stops will be avoided, vehicle maintenance will be shifted from garage to vehicle, insurance fees will be reduced;



Company costs will be minimised: a more efficient management of the operational contractual maintenance (in the first years of the vehicle lifecycle) will decrease vehicle towing to the workshop, time dedicated to fault finding procedures and eventual errors in these procedures, use of courtesy cars to the customer and will even enable to optimise the logistics of spare parts by reducing the number of circulating[3] items and the stocks in the dealers network and OEM warehouses.

Furthermore, the OEM expects to increment CSI (customer satisfaction index) related to service providing and quality perception by up to 80%, from values shadowed by car stops and high intervention time.

Other examples of the applications that will be impacted are in the domains of the railway industry, as well as e-commerce, e-government and e-inclusions services, services providing assistance to users, etc. The proposed techniques have the potential to significantly enhance the competitive advantage of the European industry in these domains and to considerably improve the satisfaction for customers.

2) Storyboard of the ambient assistive living scenario Storyboard

Scenarios for IoT4All: In general, AAL environments are more useful for people without cognitive impairment or for caregivers of those with dementia than for people with dementia themselves, since they would have problems even to understand the input provided for the system for them. They can be passive subjects of AAL systems, but interactions patient-system should be avoided if they are not closely controlled by a caregiver and based on a previously well-known interface (TV, etc).

Scenario 1: At the Day Care Center.

One common problem that is found there is that of the management of medication. Each patient has its own medication schedule, usually complex since multi-medication is common within elderly people, and it increases in those suffering from dementia. To make the problem more complex, users of Day Centers have their own General Practitioner that takes care of their medication changes, and the family has to inform the Day Center staff of each change that occurs in the medication schedule of the patient. Thus, for the formal caregivers at the Day Center would be of great help to have an updated information of the medication that has to be given to each patient at each time, the dose, if it has to be administered with/without food, etc, all this information should be changed and updated automatically and offered to the formal caregiver (staff) in a private manner. Also, the management of the medication stock (new drugs needed, drugs that are running out of stock, drugs that are near to expire, drugs that are not needed any more) could be of great help for the staff since it is extremely time consuming. The whole system will help to save costs (staff hours, medication budget) and also to decrease medication errors, that are common in health environments.

[3]

Electronic devices are usually controled after substitution, both for quality control and for maintenance operations control, before being eventually reintegrated into the network as second hand devices.

Proposal Part B: page 54 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Scenario 2: At home.

It is very common in the healthy elderly people that they have daily memory problems. These memory problems are associated with the normal process of aging and are not the first phase of dementia, since in most cases they stay stable. But, for the elderly people, these forgetfulness of daily acts is one of their main complains when talking about their concerns about their cognitive functioning. Also, these actions that they usually forget, are a threat to their self-esteem, since they feel they are getting older and dependent. Common things that are forgotten are: where common things have been left (keys, glasses, purse), common words that do not want to come to the mouth when are needed (the “tip-of-the-tongue” phenomenon), forgetting if some actions have been done (did I switch off the lights/gas?, did I close the door?), forgetting names of known people, forgetting what were you supposed to do in a room (“What was I going to do here?”). All these actions and forgetfulness are common in all ages, but they become a problem when you get older since they are really frequent and they compromise the independent living.

Scenario 3: My mother has mild dementia.

Imagine a caregiver of a person with mild dementia. The most common profile of caregiver is a daughter of 50 years old. Her mother has mild dementia but still lives in her own apartment. The caregiver does not want to send her mother to a nursing home still, because she can still live alone but with a high degree of supervision that has been increasing in the last months. The caregiver would like to have some control of what is happening at her mother´s home when she is there alone.

For instance, is she in the bed during the night? , does she tries to open the door?, does she use cook, washing machine, etc?, does she spend time in front of TV?, does she open /close windows?.

Having this information of activities that compromise the security of her mother would be of great help to the caregiver, and will also help to register and track the types of activities that the patient is able to do or is not able to do anymore.

Technical challenges to be addressed Today, a lot of co-existing standards have been developed for dealing with the Internet of Things concept; at a lower level (especially hardware-, network layer-, and frequency-related) they are very different.

For instance, the Electronic Product Code (EPC) is a global numbering scheme to uniquely identify any object in the world, and it is primarily concerned with tracking an object through the Supply chain. Besides, we all know at this stage RFID (Radio-frequency identification), an automatic identification method, relying on storing and remotely retrieving data using devices called RFID tags or transponders. There are generally two types of RFID tags: active RFID tags, more interesting, which contain a battery, and passive RFID tags, which have no battery.

Now if we think of how can – not someone, but something – extract information from all these RFIDenabled things, one of the logical options is using Near Field Communication or NFC, which is a shortrange high frequency wireless communication technology which enables the exchange of data between devices over about a 10-cm distance. Payments, ticketing, smart posters to download more information about an object, etc are common applications of NFC. The NFC forum24 define support for 4 tag-types that maps to Topaz, MIFARE UltraLight, FeliCa, and MIFARE DESFire types of RFID tags. Ultimately, the idea of NFC is to map support for all these existing (and new) RFID tags into one single NFC implementation. For integration into phones, this NFC 24

Please visit www.nfc-forum.org/ and http://www.nfc-forum.org/specs/

Proposal Part B: page 55 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

implementation should also integrate into SIM. There also exist technologies for the User interface’s client side which can access NFC. For Java, it is JSR-257 (contact-less comm API) and JSR-177 (SATSA API); the SCWS (Smart Card Web Server) is yet another possibility.

What IoT4ALL intends to do is achieving a realization for an open and global architecture that can support these above mentioned technologies, and glue them together in an integral assistive environment for the elder or the impaired. In this regard, we need to: Create a common web service encapsulation for all user commands, sensor inputs, and other static knowledge inside or outside the house that act as input providers for the middleware blocks. These inputs could become known via push or pull mechanisms, depending on each application. One very good example of a novel approach for this can be found at http://community.pachube.com/ Create a middleware first block able to receive and process this low level information (low level state changes, such as “temperature dropped to 21ºC”, “five Imipramine capsules left” or “it is Monday 12h00 and the main entrance door has not been opened yet”), and turn it into a set of semantically contextualized high level events (high level state changes, such as “temperature room is too low for Mr. yyyyyy”, “almost ran out of Imipramine” or “It is late and Mr. yyyyy’s daughter has not come visit him yet || Mr. yyyyy is still home”). We will call this block the Event Composer (EC).

Create a middleware second block, which we will name as the Goal Composer (GC), able to receive and process user requests on one side, and the EC events on the other side, and combine them with known model-based templates for desirable target states, for creating a set of high level goals, or abstract requests, such as “heat the living room”, “Call Mr. yyyyyy’s daughter”, “Check Mr. yyyyy’s assistant’s distance to the nearest pharmacy with Imipramine stock”.

Create a middleware third and last block able to turn these high level goals into specific web service calls to each device/component, for instance a call to the AC system actuator, or a more complex action such as inspecting RFID-enabled Imipramine stocks in the area while getting the location of Mr. yyyyyy’s assistant’s smartphone via HTTP requests to the selected devices. We will call this the Service Composer (SC).

A semantic description of the contextualized states and properties must be designed for this threeblock middleware to act with coherence; this means we have to create an ontology-based model of the context the users and devices are living in, on top of which the rest of the architecture is built on.

Also, the sensors and actuators (low-level input generators and low-level service providers) mentioned here do not limit the scope of interest of IoT4LL-AAL as a whole. In this regard, elements of such interest can also include (as input generators) items like smoke sensors, health monitors, humidity sensors, RFID-equipped goods of any kind, intelligent fridges, smartphones and (as service providers) speech synthesizers, digital TV, or SMS servers.

Scenario/prototype typology RWD: Real World Dimension

The Real World Dimension of this specific scenario exhibits a heterogeneous, interoperable and evolving environment of inter-connected systems and devices, from clocks to sensors to smartphones, and inter-connected people (not only the elderly or impaired people, but everyone who interacts with her/him: neighbours, social carers, relatives, etc).

Proposal Part B: page 56 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

This is a Real World application including the aforementioned “self-organizing sensor networks able to maximize effectiveness by minimizing energy consumption and data storage needs, and smart objects and devices provided with communication and reasoning capabilities”; but even Virtual Worlds, which also belong to this space, could have an example here if we finally counted on a Gym Digital Video Trainer Avatar or other forms of virtual interaction for the elder/impaired. In all, the IoT4ALL-AAL scenario is a virtually endless community of users and devices.

DWD: Digital World Dimension The Digital World Dimension contains the two main blocks of services and events where, by means of an open, secure and privacy-preserving IT infrastructure: Services are established & provided, such as performing an emergency call.

Knowledge

Events generated & filtered, such as generating the event (change of state) of “no stock of a given key medicine” or filtering a temperature change that is irrelevant for Mr. yyyyyy.

Architecture & Conceptual

Knowledge is generated & transmitted, Reasoning is implemented & explained, and Actuations are inferred & controlled, such as the process of acquiring low level data from a door sensor, redirecting it to the ECGC blocks where reasoning is performed and controlling a small Javabased SMS server application to warn Mr. yyyyyy’s neighbour with a text message.

Digital Dimension

Events & Services

SED: Socio-Economic Dimension.

Business

Architecture & Conceptual

Governance

cio So omic on Ec

Proposal Part B: page 57 of 203

The Socio-Economic Dimension of the IoT4ALL-AAL scenario’s potential is of the highest order. Not only a huge amount of public finance savings and business opportunities is on the table but, what is more important, the well-being, self-confidence, independence, social bonds preservation and augmentation, welfare and happiness of – in a few years - more than half of the EU citizens is in our hands.

From a governance perspective, long-term care expenses will be relieved, along with public pensions

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

and healthcare, both of the physic and the psychic kind. This we will see in the next chapter: Impact.

Besides, new rules – and opportunities – will need to be created in order to maintain coherence and enough privacy when everybody gets interconnected with everything.

But also from a business point of view, this aspect of the Internet of Things can stimulate the creation of novel markets, including those in the frameworks of social inclusion software, remote eHealth, sensors, hardware design and supply, wearable devices, digital TV, console hardware and software, and future generation household appliances.

Impact in either society or industry It is widely known that a very steep population ageing rate is happening all over the world, and especially in the EU. The ratio of pensioners to working-age people is projected to increase, from 25% today in 2008 to 53% in 2060. That translates into only two people of working age for every person aged 65 or more in 2060, compared with four to one today25. Critic cases will be those of the UK, Ireland, or Spain, where the children-per-woman ratio will sink by 2020 while the life expectancy will be of 77.7 and 83.8 years for men and women, respectively26.

Thus, the impact – and what is more important from a societal perspective – the need for assistive environments in a very near future is going to be of the highest degree.

Assisting elderly and impaired people, not only at home, but also in a controlled environment that can go from public places such as governmental buildings, hospital facilities or subway stations, all the way to wi-fi enabled restaurants and supermarkets, can mean an important boost for their wellbeing, independence, and productivity, and at the same time a tremendous relieve for public finances all over the EU. Big savings (from the public finance perspective) and big market opportunities (from the private vendors, but also from a wider audience perspective - if progresses in interoperability and standards are able to keep their pace) are expected if a joint venture of IoT + AAL becomes possible in a way that more and more older people are able to stay active in society, connected to reality, healthy, and independent, in such a way like this IoT4ALL scenario does show. Namely, the following sectors will be greatly benefited27: Public pensions: The largest and most obvious expense item in Europe related to ageing is the pensions paid out to people who have retired from the workforce. The IoT + AAL quest is the quest for maintaining people active in society.

Healthcare: Even if older Europeans are leading healthier lives, they still tend to require more healthcare – such as routine checkups and constant monitoring for age-related diseases – than their younger compatriots. In addition, older people carry more of the disease burden. This will undoubtedly push up public health budgets. If IoT + AAL is able to incorporate live checks at home, mobile monitoring for medication reminders, and Digital TV for personalised attention, among other possible solutions, the path for relieving healthcare expenses will be set.

Long-term care: Although many older Europeans are leading largely independent lives, there are many whose health challenges compel them to require the care of others, and following the previous rationale, there will be more in this case in few years. This has and will have serious public finance implications, particularly in northern Europe, where long-term care is more institutionalised than in the more family-based model favoured in the south. Again, enabling a higher rate of independence among elderly and impaired people will enable better confidence and quality of life not only for them

25

Source: Eurostat, 2008 Schroots, J. J. F.; Rocío Fernández Ballesteros, Georg Rudinger (1999). Aging in Europe. pp. 107-108.

27 Inspired by the EC article at http://ec.europa.eu/economy_finance/een/004/article_4298_en.htm 26

Proposal Part B: page 58 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

but also for the ones who take care of them, along with substantial savings on dependency financial aids throughout the continent.

Unemployment benefits: Given that the labour force will shrink and employment will rise, the amount spent on unemployment benefit looks likely to fall. However, the drop in education and unemployment expenditure is unlikely to offset the growth in other age-related expenses. This is interrelated with the first point, and again IoT + AAL must be one of the pillars that can balance this situation to a certain extent.

4) Storyboard of the Crisis Management scenario ATOS proposes a scenario in the Emergency management and civil protection domain, implementing a flexible architecture and a series of adaptive web-services in mobile devices such as PDA and mobile telephones used by civil protection and local authorities to receive alert messages from an emergency Decision Support System (DSS). The DSS operates like an early warning centre and includes the following features:  a multi-sensor monitoring platform with real-time processing of data streams  enhanced modelling and forecasting capabilities to analyse the sensor data and classify a bestfitting pre-calculated simulation contained in the database.  access to a multi channel warning dissemination infrastructure to deliver trusted warnings and forecasts of imminent crisis events (natural and technological disasters) to authorities and emergency management forces of different areas (at national, regional or local level).

The early delivery of warning messages to the local ‘emergency devices’ in the area affected by the risk is critical to undertake effective actions therefore saving numerous human lives.

So far this process has allowed movement of information in one direction only, i.e., from the warning centre to the local mobile devices. In case that one of these mobile devices fails or gets partially disabled an area will be exposed to major hazards.

The proposed scenario will provide the mobile devices with self-healing web-services that will let the warning centre operator know the device has failed, the nature of the failure, etc…, therefore having the opportunity to take timely and compensatory measures. These measures include the activation of additional devices in the affected area, or the delivery of warnings to close areas regarding this failure.

Technical challenges to be addressed The Crisis Management scenario entails important technical challenges: -

Identification and development of new services for autonomous mobile devices to support the crisis response management.

-

Design of software able to be embedded and run on small devices.

-

Enhanced computing power and battery autonomy

-

Capability to communicate between mobile devices themselves.

-

The need to integrate all services and components in an effective Distributed Decision Making tool for crisis management.

Proposal Part B: page 59 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Impact in either society or industry IoT4ALL will support the last link of the emergency management chain, reinforcing the capability of civil protection and emergency managers to respond towards extreme natural and man-made disasters. Those extreme events occasionally cut all communications between the mobile units and the control centre. At that point the emergency managers will have enhanced services and the best information available to act in coordination with other units.

IoT4ALL will minimize the consequences of failure in the communication infrastructure, thus increasing the autonomy and effectiveness of the emergency units.

IoT4ALL will support the following EU legislation and related texts: -

COM(2008)130 Communication on Reinforcing the Union's Disaster Response Capacity28

-

Commission Staff Working Document SEC(2007) 1721, Towards Better Protecting Citizens against Disaster Risks: Strengthening Early Warning Systems in Europe29

-

Council Conclusions on the development and establishment of Early Warning Systems in the EU30

-

Council Conclusions on enhancing the coordination capacity of the monitoring and information centre (MIC) within the community civil protection mechanism31

-

Council Conclusions on preparedness for decontamination of casualties following chemical, biological, radiological and nuclear -incidents32

-

Declaration of the European Parliament on early warning for citizens in major emergencies33

-

European Parliament resolution of 4 September 2007 on this summer's natural disasters34

5) Storyboard of the sustainable logistics scenario Storyboard Climate change has undoubtedly become one of the most critical problems that humanity needs to address in the years to come. The consequences of global warming have already started to become apparent and the scientific forecasts for the future are not encouraging. In addition to this, energy and clean water resources are becoming sparser every day, showing the first signs of a global future energy and water shortage. Under this threat, scientists are stressing the imperative need for action and the need to focus on the most contributing parts and on processes where improvements are feasible in order to achieve energy efficiency and minimize the environmental impact of products from “cradle to gate�. A study undertaken in 2006 on behalf of the European Commission35 showed that the supply chains for food, drink and transportation products (i.e. cars etc) are responsible for about 70% of the total environmental burden caused by consumer products.

Under this perspective the aim of the sustainable logistics scenario will be to support firms in the supply chain to measure, manage and ultimately improve the energy efficiency and the general environmental profile of their operations by utilizing the IOT4ALL architecture.

28

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2008:0130:FIN:EN:PDF http://ec.europa.eu/environment/civil/prote/pdfdocs/sec_1721_2007.pdf 30 http://ec.europa.eu/environment/civil/prote/pdfdocs/2007council_conclusions_ews.pdf 31 http://www.consilium.europa.eu/ueDocs/cms_Data/docs/pressData/en/jha/94607.pdf 32 http://www.consilium.europa.eu/ueDocs/cms_Data/docs/pressData/en/jha/94604.pdf 33 http://www.europarl.europa.eu/sides/getDoc.do?pubRef=-//EP//TEXT+TA+P6-TA-20080088+0+DOC+XML+V0//EN&language=EN 34 http://www.europarl.europa.eu/sides/getDoc.do?pubRef=-//EP//TEXT+TA+P6-TA-20070362+0+DOC+XML+V0//EN&language=EN 35 ENVIRONMENTAL IMPACT OF PRODUCTS (EIPRO), ec.europa.eu/environment/ipp/pdf/eipro_report.pdf 29

Proposal Part B: page 60 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Especially companies offering logistics services and third-party logistics providers would like to enhance their service offering with: a) information regarding the environmental impact of their processes; b) management tools that enable their customers (mostly product suppliers) to monitor and manage their product’s movement and environmental performance across the supply chain; c) efficient inventory management and distribution processes that exploit the full capacity of resources (e.g. full truck loads) and minimize environmental impact. In addition, this information should be made available to consumers who become all the more environmentally conscious and ultimately drive green consumer demand.

What IoT4ALL intends to do is achieving a realization for an open and global architecture that can support the integration of data coming from various data sources and objects (e.g. sensor data monitoring environmental conditions, RFID data uniquely identifying items/cases/pallets, process data etc.) and enable the above service scenarios by bridging the physical, digital and socio-economic dimensions. Furthermore, IoT4ALL wishes to e Technical challenges to be addressed The sustainable logistics scenario presents significant scientific and technical challenges related to the Internet of Things and addressed by IOT4ALL, such as: a) the need to manage and integrate multiple object identification schemes and automatic data capture technologies in order to gather and associate data coming from various data sources; b) the requirement to associate sensor data with unique product instances and processes in order to provide reliable and timely information e.g. on energy consumption or gas emissions related to products and processes; c) the need to support object traceability, discovery and information sharing across the supply chain, in order to monitor a product’s environmental footprint, following a scalable and secure approach; d) the requirement for efficient object-customer interaction in order to support dynamic productinformation services related to a product’s environmental profile (eco-label) and drive green consumer demand; Scenario/prototype typology The sustainable logistics scenario will be tested in a real-world setting with the participation of a Third-Party-Logistics provider (3PL), DIAKINISIS, who handles distribution and logistics processes of fast moving consumer goods (FMCG). More specifically, DIAKINISIS is the largest 3PL company in its market and handles a great range of products such as: foodstuffs, waters, beverages, spirits, confectionery, pet food, personal hygiene, cosmetics, household cleaning, professional/industrial cleaning, machinery, spare parts & accessories, stationery, books, toys, plastics/polymer raw materials, clothing & footwear, athletics & gymnastics, electrical appliances, electronics, promotional materials, and so on.

The company has already invested in RFID technology to monitor incoming and outgoing processes, in order to efficiently manage the large volumes of products (over 50.000.000 shipping cases a year) and orders (over 550.000 orders to a total of 40.000 delivery points across the entire country).

IOT4ALL will give the company the possibility to monitor the environmental profile of things (such as products, vehicles, pallets etc.), associate the physical to the digital world and further make this information available to the company’s customers (product suppliers) but also consumers.

Impact in either society or industry Supply chain control has so far had operational effectiveness and efficiency as its only objective, disregarding the implications that operational characteristics and decisions have on energy use and sustainability. Only recently did environmental performance start to be taken into account as an important parameter when managing supply chains; even when environmental parameters are part

Proposal Part B: page 61 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

of the control process, this happens on an ad-hoc or posterior basis, without being truly integrated with the operational dimension of supply chain control.

The aformentioned scenario, as supported by the IOT4ALL architecture, aims to enhance existing supply chain management practices by incorporating energy efficiency and environmental parameters into current systems. This will integrate supply chain control with environmental performance management. More specifically, IOT4ALL will bring: • Improved operational and environmental performance control • Efficient reporting of environmental KPIs for processes and products • Efficient environmental data sharing Furthermore, the project aims to stimulate greener customer demand by making the information regarding the environmental profile of products available to consumers. The availability of credible and comparable environmental performance information through the use of the IOT4ALL platform will give the opportunity to deliver selected representative metrics for each product to the final consumer, for example in the form of an eco-label or through other channels. This will stimulate environmental consciousness throughout the market, fostering competition for greener and energyefficient products.

This section provides a detailed work plan, broken down into work packages (WPs) which follow the logical phases of the implementation of the project, and include consortium management and an assessment of progress and results.36 Any significant risk is identified and contingency plans are described.

1.3.2 Description of the overall strategy of the work plan This section is organised in the following way: 

Section 1.3.2.1 describes the project methodology,



Section 1.3.2.2 provides the general work plan and milestones of the project,



Section 1.3.2.3 describes the activities in detail,



Section 1.3.2.4 provides a more detailed description of the work packages,

1.3.2.1 Project methodology The IoT4All project methodology balances two general outcomes of the project: 

Research and development that extend the boundaries of knowledge benefiting scientific excellence in Europe



Case Studies, Dissemination and Exploitation that push the state of the art benefiting industry and the wider European community

Our ambitious goal of enabling trillions of things to exist in a highly dynamic fashion creates a specific burden – our technologies need to be highly usable, have validity in the real world, and must be extremely scalable. It is therefore imperative that all IoTAll activities are cohesive. In particular, case studies and R&D activities must be highly interconnected.

36

Please note that our overall approach to management will be described later, in Section 2.

Proposal Part B: page 62 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Figure 1.1- IoT4All research organization: spiral approach To this end we have organized the IoT4All activities to tightly couple the use case implementations, research and development activities and all other project activities. The overall project work will be organized according to seven main activities which are structured within a spiral life cycle shown in the figure above and a strategy for the alignment of the activities is defined.

Through its iterative structure our spiral approach minimizes the risks associated with lack of communication or overall project coherence. From the very start of IoT4All we will deploy combinations of existing technologies, available off-the-shelf or based on previous EU projects, within our industrial case studies.

The lessons learned from initial deployment will be used to derive early specifications for the core IoTAll technologies. Exploitation and dissemination activities will use early project results to raise awareness within the academic and industrial communities. Our virtuous circle will be completed as integration activities ensure that early prototypes are turned into robust systems of industrial and social strength.

1.3.2.2 General work plan and milestones The IoT4ALL general work plan is an implementation that backs our spiral model for research organizations. All activities are subject to semi-ordered sequences and govern the work breakdown structure in all work packages. While work packages can still customize the timing to address their specific needs, general milestones are established by the three phases within each iteration, namely: (1) elaboration phase, (2) construction phase and (3) transition phase.

Proposal Part B: page 63 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Figure 1.2 - Project work plan 1. Elaboration Phase The elaboration analyses the problem domain in depth and makes key architectural choices that are aligned between the different work packages. Key outcomes of the elaboration phase are: 

Develop and refine scientific approaches.



A use-case model in which the case studies and the actors have been identified and the core components of the case study are developed.



A description of the software architecture for all R&D work packages.



Exploitation, dissemination and training plans to anticipate real world impact.

Construction Phase In this phase the main focus switches to the development of components and other features of the overall IoTAll solution. This is the phase when the bulk of the coding work takes place to bring the research to life. This phase also produces demonstrable prototypes that form the basis for case study deployment.

Transition Phase In the transition phase, the R&D results move into case studies and are evaluated with end users.

At the same time, dissemination activities will peak. The outcome of the first iteration is evaluated and forms the input for the elaboration phase of the next iteration.

Proposal Part B: page 64 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

In conjunction with the phases above we define a set of four major milestones in IoTAll. The milestones are control points at which decisions are made based on the results achieved thus far in the project. The milestones are: Milestone 1 - Initialized – Month 6: In the first 6 months of the project an initialization process will be performed. Best candidate methodologies, techniques and tools are identified at this milestone. Furthermore initial conceptual work and simple prototypes are also available.

Milestone 2 - Established – Month 18: At this milestone we will achieve in breadth a development of the platform by providing initial versions of all components and of the platform itself. Having an established platform in the end of Month 18 is one of the most crucial milestones in the project.

Milestone 3 - Refined – Month 33: Once the IoT4ALL platform is fully established, the focus will gradually shift towards a more substantial realization. At this stage of the project, IoT4ALL components are refinements of those available at the previous milestone. Thus this milestone is an updated version of the previous one in terms of more coherent and refined results.

After the above milestone all research and the majority of the technical work will be finalized. The remaining period of the project will concentration on maturing the technology, standardization, training, dissemination, exploitation.

Milestone 4 - Matured – Month 42: This milestone is the final check point where we can verify that we have attained what we set out to accomplish.

1.3.2.3 Activities To achieve a better control over the different WPs associated to the project, we foresee a grouping methodology into Activities. Those activities have a common guideline and main research selling point. We present the list of activities and the description of all of them.

The scope of the IoT4All Integrated Project is ambitious bringing together three complex and powerful concepts addressing not only scientific and technical challenges but also addressing the impact of the project on business (and society). In defining the project structure, the challenge is to develop a structure, which can address the scientific, technical and business drivers behind the creation of the intelligent business related environment following the hypercube vision.

Within this concept, 7 major Activities have been identified. These activities are: 

Activity 0 Project Coordination & Management: This activity covers all necessary project management and coordination activities.



Activity 1 IoT Architecture & Middleware’s: This activity is intended to create the convergent architecture in the IoT hypercube centre, is the main activity of IoT4All that will produce the implementation of the IoT4All framework



Activity 2 Real World IoT Technologies & Systems: This activity will address its effort to the achievement and iterative improvement of a suitable way of interconnection between systems represented by devices and people involved with their usage.



Activity 3 Business/Social World Novel IOT-based Applications: This activity will be addressed to guarantee the benefits of IoT approaches into our socio-economic world represented by different business industries: automotive, logistics, etc.

Proposal Part B: page 65 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All



Activity 4 Digital/Virtual World IoT Service Platforms: The Digital/Virtual World IoT Service Platforms activity aims at providing a robust, open, secure and trusted IT infrastructure allowing for the analysis, extraction & management of Knowledge & Experiences of Communicating Things via federated platforms; Cloud and Service platforms, Service Frontend and Collaboration Platforms, Event Driven Platforms, Semantic Reasoning Platforms.

Within this IT infrastructure, services will be provided and consumed, events will be triggered, generated and processed, knowledge will be analysed, processed, generated and communicated, reasoning will be deduced and analysed taking advantage of innovative resource discovery and management mechanisms offering efficient resource allocation and optimal resource usage, trust and reputation management mechanisms and QoS provision.



Activity 5 Requirements, Pilots & Test Cases: It will be refer to a demonstration stage of the project by performing and deploying architecture and functional approaches into a realworld scenario.



Activity 6 Impact Creation: This activity will analyze and measure the impact of the usage of IoT4ALL approaches by defining a dissemination and deployment further the project perspective.

Additionally the activity and work package structure was chosen to support the following tasks: 

To drive the technical and scientific innovation;



To ensure the impact of the project on the wider scientific, industrial and legislative environment;



To ensure the consistency between the project and the evolving scientific, industrial and legislative external environment; and



To set the objectives of the project and their mapping to work packages;

Proposal Part B: page 66 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The figure below illustrates how these seven activities relate to project work packages.

Activity 0 Project Management WP0.1 General Coordination, Project Management and Impact assessment Activity 1 IoT Architecture & Middleware’s

Activity 2 Real World IoT Technologies & Systems

WP1.1 Architectural Design and Dimensions Coordination

WP2.1 Smart IOT Microsystems and Wireless Sensor Networks

WP1.2 Semi-permeable osmotic *wares (AIT)

WP2.2 Distributed Intelligence and Smart Objects

WP1.3 Trust, privacy & security

WP2.3 Smart Spaces and User Interaction

WP1.4 Integration, Verification/Validation

Testing,

WP2.4 Real Governance

World

Management

&

Activity 3 Business/Social World Novel IOTbased Applications

Activity 4 Digital/Virtual World IoT Service Platforms

WP3.1 Novel Applications

IoT

WP4.1 Event Driven Platforms

WP3.2 Novel Applications

IoT

Cars SCM

Diagnosis &

Logistics

WP3.3 Novel IoT AAL Applications WP3.4 Novel Applications

IoT

Homeland

WP4.2 Service & Cloud Platforms WP4.3 Service Front-end & Collaboration Platforms

Security

WP3.5 Socio-economics, Business models & value proposition Activity5

Prototypes, Pilots & Test Cases

Activity 6 Impact Creation

WP5.1 Pilots & Take-ups Methodology

WP6.1

Dissemination & Training

WP5.2 Pilot 1. i.e. Self-repairing car

WP6.2 Standardization, International Cooperation

WP5.3 Pilot 2. i.e. Sustainable Logistics WP5.4 Pilot 3. i.e. Ambient Assistive Living WP5.5 Pilot 4 i.e. Homeland security Table 1.4 Overview of clustered work packages

Proposal Part B: page 67 of 203

Exploitation

&

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.3 Work package and deliverable time schedule - Gantt chart The following Gantt shows the time plan of the project per activities and work packages, taking into account in the bottom the spiral approach described in previous sections with three iterations, and three phases within each iteration.

Proposal Part B: page 68 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

A0 Project Coordination & Management WP0.1 General Coordination A1 IoT Architecture & Middlewares WP1.1 Architectural Design and Dimensions Coordination WP1.2 Semi-permeable osmotic *wares WP1.3 Trust & Privacy and Security WP1.4 Integration, Testing, Verification/Validation A2 Real World IoT Technologies & Systems WP2.1 Smart IoT Microsystems WP2.3 Distributed Intelligence and Smart Objects WP2.4 Smart Spaces and User Interaction WP2.5 Real World Management & Governance A3 Business/Social World Novel IOT-based Applications WP3.1 Novel IoT Cars Diagnosis Applications WP3.2 Novel IoT SCM and Logistics Applications WP3.3 Novel IoT AAL Applications WP3.4 Novel IoT Homeland Security Applications WP3.5 Socio-economics, Business models and value proposition A4 Digital/Virtual World IoT Service Platforms WP4.1 Event Driven Platforms WP4.2 Service & Cloud Platforms WP4.3 Service Front-end and Collaboration Platforms A5 Requirements, Pilots & Test Cases WP5.1 User requirements specification WP5.x Pilots & Take-ups Methodology WP5.2 Pilot 1. i.e. Self-repairing car WP5.3 Pilot 2. i.e. Sustainable Logistics WP5.4 Pilot 3. i.e. Ambient Assistive Living WP5.5 Pilot 4 i.e. Homeland Security A6 Impact Creation WP6.1 Dissemination & Training WP6.2 Standardization WP6.3 Exploitation & International Cooperation

Leader ATOS ATOS TXT

1

2

3

4

5

6

TXT AIT BULL ATOS INSIEL CAEN INSIEL TXT AUEB BMT CRF TXT INGEMA BMT ESADE NTUA FZI NTUA TXT

CRF ATOS ATOS CRF AUEB INGEMA ATOS

ATOS SIGS ATOS ATOS

Iteration I Elaboration Construction Transition

Iteration II Elaboration Construction Transition

Iteration III Elaboration Construction Transition

Project Checkpoints Project Milesotnes

Proposal Part B: page 69 of 203

7

8

9

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.4 Detailed work description broken into WPs 1.3.4.1 WP No37

Work Packages List Work title

package Type of Lead activity38 partic no.39

0.1

General Coordination (ATOS)

1.1

Architectural Design and Dimensions RTD Coordination (TXT)

2

Semi-permeable RTD osmotic *wares (AIT)

9

Trust, privacy & RTD security (BULL)

11

Integration, Testing, Verification/Valid ation (ATOS)

1

1.2

1.3

1.4

2.1

2.2

2.3

2.4

37 38

39 40 41

MGMT

1

Lead partic. short name

Personmonths40

ATOS ORIGIN

81

Start month41

End month 41

TXT

80

AIT

48

EVIDIAN

66

1

42

1

32

4

33

4

33

4

33

4

33

4

33

4

33

4

33

RTD ATOS ORIGIN

Smart IOT RTD Microsystems and Wireless Sensor Networks (TELIT)

7

Distributed RTD Intelligence and Smart Objects

8

Smart Spaces and RTD User Interaction (TXT)

2

Real World RTD Management & Governance (AUEB)

15

93

96 TELIT

INSIEL

TXT

AUEBELTRUN

57

55

34

Workpackage number: WP 1 – WP n Please indicate one activity per work package: RTD = Research and technological development; DEM = Demonstration; MGT = Management of the consortium Number of the participant leading the work in this work package The total number of person-months allocated to each work package Measured in months from the project start date (month 1)

FP7-ICT-2009-5 26/10/09 v1.0

3.1

3.2

3.3

3.4

3.5

4.1 4.2 4.3

5.1

5.2

5.3

5.4

5.5

6.1

IP proposal IoT4All

Novel IoT Cars RTD Diagnosis Applications (CRF)

3

Novel IoT SCM & RTD Logistics Applications (TXT)

2

Novel IoT AAL RTD Applications (ATOS)

1

Novel Homeland Security Applications (BMT)

18

IoT RTD

CRF

TXT ATOS ORIGIN

BMT

Socio-economics, RTD Business models & value proposition (ESADE)

17

Event Driven RTD Platforms (FZI)

14

Service & Cloud RTD Platforms (NTUA)

13

Service Front-end RTD & Collaboration Platforms (TXT)

2

Pilots & Take-ups RTD Methodology (ATOS)

1

Pilot 1. i.e. Self- RTD repairing car (CRF)

3

Pilot 2. i.e. RTD Sustainable Logistics (AUEB)

15

Pilot 3. i.e. RTD Ambient Assistive Living (INGEMA)

5

Pilot 4 i.e. RTD Homeland security (ATOS)

1

Dissemination & OTH Training (SIGS DATACOM)

16

Proposal Part B: Page 71 of 203

AUEBELTRUN

INGEMA ATOS ORIGIN SIGSDATACOM

4

33

4

33

4

33

4

33

4

33

4

33

8

42

8

42

8

42

8

42

8

42

8

42

34

FZI

CRF

33

34

69

ATOS ORIGIN

4 30

52

TXT

33

32

ESADE

NTUA

4

56

39

29

45

68

89

67 89

FP7-ICT-2009-5 26/10/09 v1.0

6.2

IP proposal IoT4All

Standardization, RTD Exploitation & International Cooperation (ATOS)

1

8

ATOS ORIGIN

42

30,0

TOTAL

1428 Table 1.6. Work packages list

1.3.4.2

Deliverables list

Del. no. 42

Deliverable name

WP no.

Nature 43

Dissemination level 44

Delivery date45 (proj. month)

D0.1.1

Quality assurance manual

WP 0.1

R

PU

M3

D0.1.2

Annual Project Management

WP 0.1

R

PU

M12

D0.1.3

Quality report

WP 0.1

R

PU

M12

WP 0.1

R

PU

M12

WP 0.1

R

PU

M24

WP 0.1

R

PU

M24

WP 0.1

R

PU

M24

WP 0.1

R

PU

M42

WP 0.1

R

PU

M42

WP 1.1

R

PU

M8

46D0.1.2

Report on liaison with other initiatives Annual Project Management

47D0.1.3

Quality report

D0.1.4

D0.1.4 48D0.1.2

Report on liaison with other initiatives Annual Project Management

D1.1.1.

Report on liaison with other initiatives Architecture design initial

D1.1.2.

Architecture design final

WP 1.1

R

PU

M18

D1.1.3.

Dimension holistic view

WP 1.1

R

PU

M18

D0.1.4

42

Deliverable numbers in order of delivery dates. Please use the numbering convention <WP number>.<number of deliverable within that WP>. For example, deliverable 4.2 would be the second deliverable from workpackage 4 43 Please indicate the nature of the deliverable using one of the following codes: R = Report, P = Prototype, D = Demonstrator, O = Other 44 Please indicate the dissemination level using one of the following codes: PU = Public PP = Restricted to other programme participants (including the Commission Services) RE = Restricted to a group specified by the consortium (including the Commission Services) CO = Confidential, only for members of the consortium (including the Commission Services) 45 Measured in months from the project start date (month 1)

Proposal Part B: Page 72 of 203

FP7-ICT-2009-5 26/10/09 v1.0

Del. no. 42

Deliverable name

IP proposal IoT4All

WP no.

Nature 43

Dissemination level 44

49D1.2.1.

D1.2.2.

D1.2.2.

D1.2.3.

D1.3.1.

D1.3.2.

D1.3.3.

D1.3.4.

D1.3.5.

D1.3.6.

D1.3.7.

D1.3.8.

D1.3.9.

D1.4.1.

Ontologies, Semantics and Business Workflows for IOT4ALL applications IoT Middleware Solution Initial prototype IoT Middleware final prototype Solution Specification of Crossware Interactions Security analysis and requirements document for the immutable audit log Global security architecture document and Risk assessment Specifications document of the immutable audit log Authorization chain software modules Extensions software modules for interoperation with the project ecosystem Sensor software module for access management Sensors software modules with semantic capabilities Immutable audit log software modules Rules framework software module and Hypervisor software module Rapid prototype

Delivery date45 (proj. month)

WP 1.2

P

PU

M8

WP 1.2

P

PU

M18

WP 1.2

P

PU

M30

WP 1.2

R

PU

M36

WP 1.3

R

PU

M8

WP 1.3

R

PU

M8

WP 1.3

R

PU

M8

WP 1.3

R

PU

M12

WP 1.3

P

PU

M18

WP 1.3

P

PU

M12

WP 1.3

P

PU

M12

WP 1.3

R

PU

M12

WP 1.3

R

PU

M18

WP 1.4

P

PU

M8

WP 1.4

P

PU

M18

WP 1.4

D

PU

M18

WP 2.1

R

PU

M8

WP 2.1

P

PU

M15

D2.1.2

Testing environment deployed and ready to use Final verification of the end-to end architecture Survey of technologies for the IoT Real-World Framework Smart Devices Components

D2.1.4

Capillary Network Specification

WP 2.1

R

PU

M15

D2.1.3

Integrated Smart Devices

WP 2.1

P

PU

M30

D2.1.4

Integrated Platform

WP 2.1

P

PU

M36

D2.2.1

Smart object networks specifications

WP 2.2

R

PU

M8

D1.4.2.

D1.4.3.

D2.1.1

Proposal Part B: Page 73 of 203

FP7-ICT-2009-5 26/10/09 v1.0

Del. no. 42

Deliverable name

IP proposal IoT4All

WP no.

Nature 43

Dissemination level 44

Delivery date45 (proj. month)

D2.2.2

Semantic framework specifications

WP 2.2

R

PU

M8

D2.2.3

Object intelligence specifications

WP 2.2

R

PU

M8

D2.2.4

Context model

WP 2.2

R

PU

M18

WP 2.2

R

PU

M24

WP 2.2

P

PU

M24

WP 2.2

P

PU

M30

WP 2.3

R

PU

M18

WP 2.3

R

PU

M18

WP 2.3

R

PU

M18

WP 2.3

R

PU

M18

WP 2.3

R

PU

M24

WP 2.3

R

PU

M30

WP 2.3

R

PU

M24

WP 2.3

R

PU

M30

WP 2.4

R

PU

M18

WP 2.4

R

PU

M18

WP 2.4

R

PU

M30

WP 2.4

R

PU

M30

WP 2.4

R

PU

M30

WP 3.1

R

PU

M8

WP 3.1

R

PU

M18

WP 3.1

R

PU

M20

WP 3.1

P

PU

M33

WP 3.2

R

PU

M12

D2.2.6

Smart objects identification and interoperability Context-detection prototype

D2.2.7

Object intelligence prototype

D2.2.5

D2.3.1a D2.3.2a D2.3.3a D2.3.4a D2.3.1b D2.3.2b D2.3.3b D2.3.4b D2.4.1a D2.4.2a D2.4.1b D2.4.2b D2.4.3b D3.1.1.

D3.1.2.

D3.1.3.

D3.1.4.

D3.2.1a

Design of the Physical Smart Spaces of the IOT4ALL Real World The Physical Smart Spaces of the IOT4ALL Real World Design of the Human Smart Spaces of the IOT4ALL Real World The Human Smart Spaces of the IOT4ALL Real World Design of the Physical Smart Spaces of the IOT4ALL Real World The Physical Smart Spaces of the IOT4ALL Real World Design of the Human Smart Spaces of the IOT4ALL Real World The Human Smart Spaces of the IOT4ALL Real World Real World Management and Governance Requirements for IOT Evaluation of Alterantive IOT Governace Schemes Real World Management and Governance Requirements for IOT Evaluation of Alterantive IOT Governace Schemes IOT Real World Management and Governance Recommendations Scenarios for the “Novel IoT Cars Diagnosis Applications“ Requirements for the “Novel IoT Cars Diagnosis Applications“ System Design for the “Novel IoT Cars Diagnosis Applications“ Implementation of components for the “Novel IoT Cars Diagnosis Applications“ Design of the Supply Chain Planning services and plug-ins

Proposal Part B: Page 74 of 203

FP7-ICT-2009-5 26/10/09 v1.0

Del. no. 42

Deliverable name

IP proposal IoT4All

WP no.

Nature 43

Dissemination level 44

D3.2.2a D3.2.3a D3.2.4a D3.2.1b D3.2.2b D3.2.3b D3.2.4b D3.2.5a D3.2.5b D3.3.1.

D3.3.2.

D3.3.3.

D3.3.4.

D3.4.1 D3.4.2 D3.4.3 D3.5.1 D3.5.2 D3.5.3 D3.5.4 D4.1.1 D4.1.2 D4.1.3

The Supply Chain Planning services of IOT4ALL Socio-Economic World Design of the Logistics services and plug-ins The Logistics Mgmt services of the IOT4ALL Socio-Economic World Design of the Supply Chain Planning services and plug-ins The Supply Chain Planning services of IOT4ALL Socio-Economic World Design of the Logistics services and plug-ins The Logistics Mgmt services of the IOT4ALL Socio-Economic World Integrated Supply Chain Planning and Logistics Mgmt Applications Integrated Supply Chain Planning and Logistics Mgmt Applications Scenarios for the “Novel IoT AAL Applications“ Requirements for the “Novel IoT AAL Applications“ System Design for the “Novel IoT AAL Applications“ Implementation of components for the “Novel IoT AAL Applications“ Report on the current state of affairs in homeland security Report on the novel implementation within homeland security Report on State of improvements Internet of Things: Business Models Opportunities Internet of Things: Potential Business Models and Value Propositions Report on Experimentation on Business Models Internet of Things: The SocioEconomic Impact – A Business Model Perspective Conceptual Model of the Event Driven Platform EDP Methodology for managing complex event patterns EDP tools and adaptors

Proposal Part B: Page 75 of 203

Delivery date45 (proj. month)

WP 3.2

R

PU

M18

WP 3.2

R

PU

M12

WP 3.2

R

PU

M18

WP 3.2

R

PU

M24

WP 3.2

R

PU

M30

WP 3.2

R

PU

M24

WP 3.2

R

PU

M30

WP 3.2

RR

PU

M24

WP 3.2

R

PU

M36

WP 3.3

R

PU

M8

WP 3.3

R

PU

M18

WP 3.3

R

PU

M30

WP 3.3

P

PU

M33

WP 3.4

R

PU

M8

WP 3.4

R

PU

M30

WP 3.4

R

PU

M36

WP 3.5

R

PU

M8

WP 3.5

R

PU

M18

WP 3.5

R

PU

M30

WP 3.5

R

PU

M40

WP 4.1

R

PU

M8

WP 4.1

R

PU

M12

WP 4.1

R

PU

M18

FP7-ICT-2009-5 26/10/09 v1.0

Del. no. 42

Deliverable name

IP proposal IoT4All

WP no.

Nature 43

Dissemination level 44

D4.1.4

EDP Service (integrated and tested)

D 5.1.1:

Service and Cloud Platforms IoTspecific Requirements Analysis and Specifications Initial Service and Cloud Platform design and Components Specifications Final Service and Cloud Platform and Specifications Design of an IoT-oriented Service Front End platform The SFE innovative services for the IoT Model generated workspaces for Things Design of the Things Collaboration framework The Innovative IoT-oriented KSB Collaboration services Integrated Requirements definition

D 5.1.2:

Pilot Performing Methodology

D4.2.1.

D4.2.2.

D4.2.3.

D4.3.1a D4.3.2a D4.3.3a D4.3.4a D4.3.5a

D 5.1.3: D5.2.1.

D5.2.2.

D5.2.3.

D 5.3.1.

D 5.3.2

Pilot Performing Integrated Iterated Results Pilot Implementation of the “SelfRepairing Car” Application Test and Evaluation Report of the “Self-Repairing Car” Application Roadmap for Industry Level Implementation incl. Analysis of Critical Issues and Barriers Sustainable Logistics Pilot Requirements Sustainable Logistics Demonstrator

D5.5.1.

Sustainable Logistics Pilot Assessment and Business Validation Pilot Implementation of the “AAL” Application Test and Evaluation Report of the “AAL” Application Roadmap for Industry Level Implementation incl. Analysis of Critical Issues and Barriers Integrated Pilot Implementation

D5.5.2.

Test and Evaluation Report

D 5.3.3.

D5.4.1.

D5.4.2.

D5.4.3.

Proposal Part B: Page 76 of 203

Delivery date45 (proj. month)

WP 4.1

R

PU

M30

WP 4.2

R

PU

M8

WP 4.2

R

PU

M12

WP 4.2

R

PU

M30

WP 4.3

R

PU

M12

WP 4.3

R

PU

M18

WP 4.3

R

PU

M18

WP 4.3

R

PU

M12

WP 4.3

R

PU

M18

WP 5.1

R

PU

M8

WP 5.1

R

PU

M18

WP 5.1

R

PU

M20

WP 5.2

R

PU

M40

WP 5.2

R

PU

M42

WP 5.2

P

PU

M42

WP 5.3

R

PU

M8

WP 5.3

P

PU

M30

WP 5.3

P

PU

M42

WP 5.4

P

PU

M40

WP 5.4

P

PU

M42

WP 5.4

D

PU

M42

WP 5.5

D

PU

M40

WP 5.5

R

PU

M42

FP7-ICT-2009-5 26/10/09 v1.0

Del. no. 42

IP proposal IoT4All

Deliverable name

WP no.

Nature 43

Dissemination level 44

Delivery date45 (proj. month)

D6.1

Roadmap for EU wide Implementation Dissemination Strategy

D6.1.1a

Dissemination Plan

WP 6.1

R

PU

M6

D6.1.2a

Training material version 1

WP 6.1

R

PU

M8

D6.1.1b

Dissemination Plan

WP 6.1

R

PU

M18

D6.1.2b

Training material version 1

WP 6.1

R

PU

M18

D6.1.3

Internal training sessions for IoT4All

WP 6.1

R

PU

M14

WP 6.1

R

PU

M30

WP 6.1

R

PU

M42

WP 6.2

R

PU

M12

WP 6.2

R

PU

M12

WP 6.2

R

PU

M24

WP 6.2

R

PU

M30

WP 6.2

R

PU

M30

WP 6.2

R

PU

M24

WP 6.2

R

PU

M42

WP 6.2

R

PU

M42

WP 6.2

R

PU

M36

D5.5.3.

External training sessions on the use of IoT4All results Dissemination Report

D6.1.4 D6.1.5

Business requirements, Market Sizing and critical success factors Annually Industrial advisory board will be organized Consolidated Market Analysis

D6.2.1 D6.2.5a D6.2.2

Detailed product definition and positioning Individual exploitation plans

D6.2.3a D6.2.4a

Annually Industrial advisory board will be organized Detailed product definition and positioning Individual exploitation plans

D6.2.5b D6.2.3b D6.2.4b

Annually Industrial advisory board will be organized

D6.2.5c

WP 5.5

D

PU

M42

WP 6.1

R

PU

M6

Table 1.7. Deliverables list

1.3.4.3

Milestones list

Milestone number M1

Milestone name Initialized

50

WP

Expected date Means 50 verification51 8

of

Before M8 all the Deliverables should be in the EC, revised

Measured in months from the project start date (month 1) Show how both the participants and the Commission can check that the milestone has been attained. Refer to indicators if appropriate 51

Proposal Part B: Page 77 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

and quality proved.

M2

M3

M4

Milestone 2: Established

Milestone 3: Refined

Milestone 4: Matured Table 1.8. Milestones list

Proposal Part B: Page 78 of 203

18

Before M18 all the Deliverables should be in the EC, revised and quality proved.

30

Before M30 all the Deliverables should be in the EC, revised and quality proved.

42

Before M42 all the Deliverables should be in the EC, revised and quality proved.

FP7-ICT-2009-5 26/10/09 v1.0

1.3.4.4

IP proposal IoT4All

Work package descriptions

Work package number

0.1

Start date or starting event:

Work package title

General Coordination

Activity type

MGT

Participant number

1

2

3

TXT

CRF

Personmonths per 63 participant

10

2

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Participant short name

ATOS

4 TR-SLO

5

M1 – M42

ING

6 CAEN

7 TELIT

8

9

INS

AIT

2

Personmonths per participant

2

2

Objectives:  To manage the scientific, technological and impact background of the project.  Continuous evaluation and monitoring of the technical/impact content of the project.  Assessment of project achievement against project objectives.  Organisation of internal assessment of all project results and deliverables.  Definition of mechanism and principles for reaching the specified objectives Promote collaboration with other FP7 initiatives Description of work T0.1.1: Definition of monitoring and assessment methodology. (M1 – M3) The principles and concept for appropriate project results assessment, monitoring and control are established. The process for technical quality control and cross workpackages assessment procedure will be established. An internal peer review process for project results will be established. A quality assurance manual will be issued. The review teams will be defined.

Task leader: TXT. Members: ATOS

Proposal Part B: Page 79 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

T0.1.2: Organisation of project continuous assessment and evaluation (M1 – M48) The task involves the practical organisation and management of the principles and concept for project results monitoring and control as defined in Task 0.2.1. The task involves a continuous evaluation and monitoring of the technical/impact content of the project achievement against project objectives. Recommendation for corrective actions will be issues for conflict situations if need. A yearly recommendation for revision project objectives will be issued, taking into account achievements and general trends and development outside the project. Quality reports will be produced by the project coordination committee.

T0.1.3 Liaison with other initiatives The task involves an actives organisation and participation in activities for cross project scientific and technology dissention. The IOT4ALL project will have a central role in the European CERP IOT research community. IOT4ALL will participate and take a lead role in clustering and others activities organised by the Commission as well as other research communities worldwide.

Deliverables Milestone 1: Initialized (8)  D0.1.1 Quality assurance manual (M3) Milestone 2: Established (18)  D0.1.2 Annual Project Management (M12)  D0.1.3 Quality report (M12)  D0.1.4 Report on liaison with other initiatives (M12) Milestone 3: Refined (30)  D0.1.2 Annual Project Management (M24)  D0.1.3 Quality report (M24)  D0.1.4 Report on liaison with other initiatives (M24) Milestone 4: Matured (42)  D0.1.2 Annual Project Management (M42)  D0.1.4 Report on liaison with other initiatives ( M42)

Proposal Part B: Page 80 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

1.1

Work package title

Architectural Design and Dimensions Coordination

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M1 – M18

6 CAEN

7 TELIT

8

9

INS

AIT

7

7

Personmonths per 10 participant

15

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

10

7

7

10

Personmonths per 7 participant

Objectives:  To design the IOT4ALL functional and modular architecture in its first and final releases  To select the enabling technologies, tools, services, standards and languages  To develop technical guidelines to be adopted in the subsequent IOT4ALL developments  To constantly monitor, control and coordinate the technical developments in the different IOT4ALL world dimensions  To continuously manage technical risk and find the proper corrective measures Description of work T1.1.1: First design of the IOT4ALL Architecture (TXT). (M1 – M6) The IOT4ALL functional and modular architecture will be designed and developed in this task in its first release. This will include the 3 dimensions and the coordinating middleware among them. The implementation technologies (hw and sw) will be identified and acquired, with specific emphasis on openness and respect of standards. Technical guidelines will be also issued for all the development WPs. T1.1.2: Final design of the IOT4ALL Architecture (TXT) (M13 – M18) After the first development cycle, the choices made at the very beginning of the project in T1.1.1. will be critically revised on the basis of the feedback of the development team and of the requirements

Proposal Part B: Page 81 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

coming from our use cases. This will lead to the final release of the IOT4ALL architectural document.

T1.1.3 IOT4ALL Dimensions Coordination (ATOS) (M1 – M18) In an IP it is always very important to coordinate the activities which are developed in the several different technical work packages. This task will constantly monitor the evolution of the technical project, in order to prevent problems for the subsequent integration and piloting phases. Possible problems will be then reported to WP0 for decision making. The project coordinator will be in charge of this activity to clearly separate the functions of controller and controlled.

Deliverables Milestone 1: Initialized (8) 

D1.1.1. Architecture design initial (M8): This deliverable will structure the full architecture of the project.

Milestone 2: Established (18)  D1.1.2. Architecture design final (M18): This deliverable will deliver the final release of the architecture of the project.  D1.1.3. Dimension holistic view (M18) : This deliverable will deliver a holistic approach to the IoT to disseminate the results of the project.

Proposal Part B: Page 82 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

1.2

Work package title

Semi-permeable osmotic *wares

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M4 – M33

6 CAEN

7 TELIT

7

8

9

INS

AIT

7

15

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

9

10

Personmonths per participant

Objectives: This work package boosts IOT4ALL objective towards developing a platform that can capture the business, IT and social perspectives of IoT. In particular it will research middleware, tools and techniques for supporting the business, technical/technological and socioeconomic perspectives of the IoT applications to be developed in the project. To this end, the work package sets the following objectives: 

To research and provide an IoT middleware solution enabling filtering, collection and processing of information stemming from “things”, while also supporting the configuration of “things”. We conveniently call this middleware solution “IT-world” middleware.



To research IoT oriented business modeling with emphasis on business and societal issues of the applications to be developed in the project (such as the self-repairing car, the next generation AAL application etc.). This modeling with enable the blending of applications into the IoT hardware and software infrastructure. We conveniently call these models and related operations “Society-IT-upper ware”.

To provide models and tools for bridging diverse IoT enabled business and societal domains, with a view to enabling global IoT applications, beyond specific domains and semantics. We conveniently call these models and related operations “World-Society crossware”.

Description of work This workpackage consists of the following tasks:

Proposal Part B: Page 83 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

T1.2.1 Society-IT upperware (TXT) This task will deal with the modelling of societal and business aspects of IoT applications, including people, applications, business concepts, objects, semantics comprising the IoT applications. Along with the models, this task will develop methods for instantiating, populating and managing the models. Furthermore, services and workflows corresponding to these models will be specified. In technical terms business modelling and related operations will be specified in the form of ontologies, as well as a set of rules, reasoning and inferencing mechanisms over the ontologies. Moreover, workflows will be specified as collections of services over the above mentioned models. The above models/ontologies, services and reasoning mechanisms are characterized as “upperware” since they comprise very high level semantics associated with the business and socio-economical aspects of the IoT applications.

T1.2.2 IT-World middleware (AIT) This task will deal with the technical implementation of a middleware solution enabling interfacing with “things”, filtering of sensor and “things”-related information, as well as actuating services over “things”. The middleware solution for “IT-World” middleware will be based on existing middleware solutions for RFID (e.g., through the AspireRfid project (http://wiki.aspire.ow2.org/)) and WSN networks (e.g., through the Global Sensor Networks (GSN) project (http://apps.sourceforge.net/trac/gsn/)). These middleware platforms will be extended in order to cover the additional sensors, devices, actuators, filtering and fusion algorithms as required by the IoT validating applications. The task will also deal with the bridging of the IT-World middleware with the Society IT-upperware, through adding business context to the information acquired by the “things”.

To this end, this task will develop middleware for connecting low-level sensor/”things” semantics with the higher level business/socio-economical semantics.

T1.2.3 World-Society crossware (ATOS) This task will provide mechanisms for inter-connecting IoT systems and application spanning different business domains i.e. based on a different set business semantics. In principles the task will deal with the challenging activity of mapping semantics across different domains. This is a requirement towards implementing global IoT applications spanning multiple business domains and applications. In addition to the mapping the “crossware” should configure the middleware bridges between business semantics and IT-world middleware in order to support the cross-domain interactions. The task will research algorithms for the autonomic/automated interaction between diverse heterogeneous IoT systems.

Deliverables Milestone 1: Initialized (8)  D1.2.1 Ontologies, Semantics and Business Workflows for IOT4ALL applications (M8): specification (report) of all the business modelling entities of the IOT4ALL applications.

A

Milestone 2: Established (18)  D1.2.2 IoT Middleware Solution Initial prototype (M18): An IoT middleware solution (prototype), which will be implemented on top of existing middleware libraries for RFID and WSN (Wireless Sensor Networks). The middleware will be delivered in two successive releases in the scope of an iterative development approach.

Milestone 3: Refined (30)

Proposal Part B: Page 84 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

ď&#x201A;ˇ D1.2.2 IoT Middleware final prototype Solution (M30): An IoT middleware solution (prototype), which will be implemented on top of existing middleware libraries for RFID and WSN (Wireless Sensor Networks). The middleware will be delivered in two successive releases in the scope of an iterative development approach.

Milestone 4: Matured (42) ď&#x201A;ˇ D1.2.3 Specification of Crossware Interactions (M36): A detailed specification automated/autonomic interactions across the IoT systems to be developed in the project.

Proposal Part B: Page 85 of 203

of

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

1.3

Work package title

Trust, privacy & security

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M4 – M33

6 CAEN

7 TELIT

8

9

INS

AIT

Personmonths per participant

7

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

30

12

7

Personmonths per 10 participant

Objectives: In the Internet of Things cloud, more and more “Things” such as web services, smart phones, laptops, servers, printers, etc are exposed over the network and linked in different manners, such as groups, communities, federations. As a result, one Thing can be part of one or several security domains or sub domains. This means that the security management of these Things needs adaptive policies and rules, when Things move and evolve over the time. In term of management, these policies must be relevant and flexible to catch environment and Things contexts.

Security management in Internet of Thing brings several issues such as interoperability, rules interpretation and data representation, data privacy, access control, monitoring automation. The goal of this work-package is to design and implement the security and security management modules in conformance with this vision. The architecture will ensure strong security with access control and data protection, and will make privacy and trust reliable in real-life deployments.

Description of work: Task 1.3.1: Architecture for Security, Trust and Privacy management This task will deliver the specification of the security management infrastructure. It will design a policy-based architecture that integrates services, managed things and a policy semantic interpreter by means of an event bus. The task will take into account the fact that the integrated monitoring components need to adapt autonomously to changes in context, activity, failures, loss of resources.

Proposal Part B: Page 86 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The LISSI lab and Evidian will deliver a global architecture document that will prepare the implementation and further deployment of security, Trust and Privacy management in the project eco-system.

Task 1.3.2: Risk assessment and Security requirements analysis The goal of this task is to provide a risk and vulnerability analysis for the M2M business scenarios supported by the project. It includes the following activities: 

Threat identification and threat models for M2M network, at component, network, system levels,



Risk and vulnerability assessment for the business scenarios addressed in the project.

As much as possible, a classification of risk and vulnerabilities will be established, taking into account either their generality or their application-specific character. From the analysis, this task will elaborate the security and possibly privacy requirements that the M2M business scenarios defined in the project should support. Existing security analysis methodologies will be reused as much as possible, but customized to the specific context of M2M. The activities in this task will consist in: 

choosing a suitable security framework,



defining generic security and trust requirements templates in the context of IoT, relevant for the project business scenarios,



elaborating the specific requirements for scenarios.

The LISSI lab will deliver a risk assessment and security requirements analysis document on these issues.

Task 1.3.3: Security Management architecture The goal of this task is to derive generic secure reference architecture models regarding the different scenarios and use cases. The approach will consist both in the design of common security principles but also in developing all system-level software that will enable to perform an efficient management of security. After, the task will design and implement a policy-based architecture that integrates services, managed things and a rules interpreter by means of an event bus. The integrated monitoring components need to adapt autonomously to changes in context, activity, failures, loss of resources.

This task will use software components developed in the event messaging bus implementation task.

The role of the message bus is to provide connectivity to the different parts of the architecture. This can require providing different options such as synchronous and asynchronous communication. A complete model of such middleware is described in the event processing work package.

Evidian will deliver an authorization chain, made of a Policy Administration Point and a Policy Decision Point. Evidian and the LISSI lab will deliver extensions for synchronous and asynchronous communications for interoperation with the project eco-system.

Task 1.3.4: Distributed Sensors and interpreters of Security and Trust Contexts In order to improve the knowledge about internet of things context and services states, it is essential to discover the relevant sensors/services that can provide such knowledge. In a non-centralized system, this is best left to each component to potentially advertise itself, let things or services register one to another, let them also semantically discover the available ones. This task is based on outcomes from the reasoning work package.

Evidian will provide sensors for a security audit database, targeting access management. The LISSI lab will deliver sensors with semantic capabilities for analyzing security management information.

Task 1.3.5: Business Rules based Hypervisor

Proposal Part B: Page 87 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

This task will design and implement a rules framework, to design software modules capable to perform supervision of internet of things, starting from the business description of their supervision task. This framework will be composed of business rules, a test editor and a rule engine wrapper, which will orchestrate the firing of rules using the available rules engines such Drools, Jess, etc.

The LISSI lab will deliver the rules framework. Evidian will provide a monitoring application dedicated to security information, based on the rules framework. The Evidian monitoring offer OpenMaster will server as the starting point for this hypervisor.

Task 1.3.6: Immutable audit log Moving services to the cloud and virtualized environments implies that security auditing and logging of all the activity is mandatory. As a result, anyone will be accountable of his actions, bringing transparency to the system and enabling trust. This is definitely a key requirement to support privacy and access control to information in the addressed independent multi-domain environments.

It’s not just important that the applications, devices, systems and the infrastructure itself generate this audit information, but also that there is no chance to alter it without producing associated electronic evidence. Independently of privileged users like system administrators or super users, who may alter the original information and modify the associated trace, an original audit data will be processed in real time, and stored preserving it by using the corresponding cryptographic techniques that will avoid this security gap. This will be done in a way that information is treated at the finest level of granularity, with the digital seal applied at the event level, e.g. a line in a text file, or a record in a database.

The objectives of this task are the analysis, design, specification, implementation and testing of an immutable audit log platform that becomes a state-of-the-art development environment for audit data coming from the several services and use cases provided in the project.

The Kinamik’s Secure Audit Vault technology here serves as a starting point. Additional functional and non-functional features will be added according to the requirements of the use cases.

Kinamik will provide a reference implementation of the immutable audit log environment, corresponding development tools, plus all the needed specifications for alternative implementations.

Deliverables The deliverables will be produced in an iterative way, in line with the two cycles of the project.

Milestone 1: Initialized (8)  D1.3.1 Security analysis and requirements document for the immutable audit log (M8)  D1.3.2 Global security architecture document and Risk assessment (M8)  D1.3.3 Specifications document of the immutable audit log (M8) Milestone 2: Established (18)  D1.3.4 Authorization chain software modules (M12)  D1.3.5 Extensions software modules for interoperation with the project eco-system (M18)  D1.3.6 Sensor software module for access management (M12)  D1.3.7 Sensors software modules with semantic capabilities(M12)  D1.3.8 Immutable audit log software modules(M12)

Proposal Part B: Page 88 of 203

FP7-ICT-2009-5 26/10/09 v1.0

ď&#x201A;ˇ D1.3.9 Rules framework software module and Hypervisor software module (M18)

Proposal Part B: Page 89 of 203

IP proposal IoT4All

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

1.4

Work package title

Integration, Testing, Verification/Validation

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M4 – M33

6 CAEN

7 TELIT

8

9

INS

AIT

Personmonths per 25 participant

12

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

10

9

12

10

Personmonths per 7 participant

8

Objectives: The purpose of this WP is give a coherence to the WP1.1 WP1.2. WP 1.3 and see that the interfaces are well defined, that there are not inconsistencies among the developments, and that effectively the final result of the architecture that is going to be released is therefore prepared to be used in the test beds.

For that purpose Atos will use Rational RequisitePro is an easy to use requirements management tool that lets a team:  Author and share their requirements using familiar document-based methods while leveraging database-enabled capabilities such as requirements traceability and impact analysis.  Apply requirements management using the Use Case technique which should help the IoT4All project to manage individual requirement artifacts and fit requirements within the Rational Unified Process (RUP).  Make customizations to the requirements process specific to the IoT4All project and work with guidelines and techniques for capturing functional and system requirements.  Use traceability and tools to automate time-consuming processes . Specify, validate and manage evolving requirements.

At the end, Use Cases provide the basis for the whole object-oriented, software life cycle including architecture, design (including GUI design) and development. At the same time Use cases help testing efforts by facilitating the creation of test cases. All tests must contain a sequence of events, which will be followed to test a particular area of the IoT4All system.

Proposal Part B: Page 90 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Description of work Task 1.4.1. Interfaces definition and rapid prototyping The objective of this task is twofold, first to check that the interface are well defined, and can be accessed in an ubiquitous way, and secondly to verify that there are not inconsistencies. A final rapid prototype will be the outcome of this task in terms of definition of the architecture.

Task 1.4.2 End to end communication testing environment.

To develop this task is mandatory to have a full deployment of the components, to have a full round trip communication among them, and a deployment place allocated beforehand.

Task 1.4.3. Verification and Validation of the expected results.

Define a serial of test that will check that the expected results are ready to be used by the test beds, to avoid the integration task to the scenarios.

Deliverables Milestone 1: Initialized (8)  D1.4.1 Rapid prototype (M8): Proof of concept that everything work together.

Milestone 2: Established (18) 

D1.4.2. Testing environment deployed and ready to use.(M18): A physical environment to deploy the applications in line with the architecture



D1.4.3. Final verification of the end-to end architecture.(M18): Final verification o f the prototype of the architecture.

Proposal Part B: Page 91 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

2.1

Work package title

Smart IOT Microsystems and Wireless Sensor Networks

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

Personmonths per participant

M4 â&#x20AC;&#x201C; M33

6

7

8

9 AIT

CAEN

TELIT

INS

38

35

14

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

Objectives: Workpackage WP2.1 aims at design and implementation of the IOT4ALL Real-World Framework, by achieving the following objectives: -

-

-

-

Evaluate the user needs and application demands in relation to available device technology, gateways and platforms for embedded and networked intelligence, also taking into account ongoing developments that may impact IoT research.

Select, configure and integrate device technologies according to user requested features, e.g.: RFID, properties sensing, actuation, range, computational capabilities, power needs. The purpose is to deliver smart sensorized solutions that are more pervasive and transparent.

Design and implement capillary network gateways, based on M2M standards and Short Range Wireless (SRW) technologies as ZigBee and Wi-Fi to enable M2M connectivity over a limited, localized area.

Provide the means for wireless connectivity between capillary networks and selected platforms for communication, data interchange, positioning and other services, addressing such issues as: self-configuring and secure connection, delay tolerance location- and contextaware network management.

Description of work This workpackage consists of the following tasks: T2.1.1 Technology and requirements survey (Insiel) Under this task, an evaluation of relevant technology components and standards will be conducted,

Proposal Part B: Page 92 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

in terms of e.g. level of specifications, available implementations, degree of maturity and standardization. The survey will involve industry sources, standardization bodies and other EU-funded projects in related areas and will be driven by the user requirements collected from the IoT4All pilot Workpackages, as well as from the IoT4All industrial partners business and market knowledge. Close collaboration with ongoing initiatives in the different technological areas, e.g., projects in DG Infso G2 unit, ETSI M2M standardization group, is planned to broaden and increase the impact of this activity.

T2.1.2 Smart devices and microcomponents (CAEN) This task will deal with the specification, technical implementation and integration of the key technological components required by future IoT smart devices. Based on available technologies selected in T2.1.1, the task will research solutions matching the main embedded intelligence requirements: energy consumption, by looking, e.g., at printed batteries and energy harvesting; ultralow power processors and related memory solutions (e.g., EEPROM52 or polymer memories); integration of chips and antennas into the objects themselves (e.g., with SiP53 technology); device interoperability, RFID standards like EPC54 and new protocols like IPv6. All these activities will be focused on pervasiveness and transparency of device technology aimed at concrete applications like, e.g., product state monitoring and expiry date prediction.

T2.1.3 Capillary Networks (Telit) This task will provide an architecture and solutions to establish connections between all fixed and particularly all mobile nodes of the IoT, down to local constellations of micro-devices and sensors.

The task objective is not only to integrate the selected set of wireless connections into the IoT4All RW Framework, but also to investigate upcoming wireless connectivity approaches, in particular through new M2M architectures55. The research work will focus on two main areas where further developments are expected: (i) advanced communication devices implementing multiple protocols, that permit to interface seamlessly with different kind of tags, e.g., long-range active HF and mediumrange passive UHF, and are capable to drive different types of antenna in order to be suitable for different wireless protocols (e.g., ZigBee, Wi-Fi); (ii) Dedicated Short Range Communication (DSRC) technology to extended communication opportunities between members of a capillary network and provide the means for fall back solutions through cooperative devices and sensors.

T2.1.4 Platform integration (Telit) This task deals with connectivity and integration of IoT capillary networks into global communication and service platforms. The approach will be based on localized M2M gateways, integrating cellular technologies such as GSM and CDMA to provide M2M connectivity over wide area distances, paired with Short-Range Wireless (SRW) technologies to extend cellular M2M connectivity â&#x20AC;&#x153;deeperâ&#x20AC;? into a localized area. This will allow for more efficient and cost-effective connectivity than would otherwise be possible if every locally connected node contained its own cellular M2M modem. Furthermore, the Task will deal with integration of IoT objects into basic communication and services networks, like GPRS\UMTS and GNSS, along with Future Internet F-O-T platforms.

Deliverables Milestone 1: Initialized (8)

52

Electrically Erasable Programmable Read-Only Memory.

System-in-Package.

54 Electronic Product Code, EPC Global / GS1 55 M2M architecture by ETSI TC M2M ad-hoc group.

53

Proposal Part B: Page 93 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

 D2.1.1 Survey of technologies for the IoT Real-World Framework (M8): The report lists and describes the available technologies and ongoing initiatives that are relevant to the implementation of the IoT4All vision of embedded and distributed intelligence.

Milestone 2: Established (18) 

D2.1.2 Smart Devices Components (M15): The report contains the design and integration specifications of the set of communication, computing, sensing and actuating components required for IoT4All smart devices.



D2.1.4 Capillary Network Specification (M15): The report contains the design of IoT4All capillary networks, in terms of communication protocols, device requirements and M2M gateway configurations.

Milestone 3: Refined (30)  D2.1.3 Integrated Smart Devices (M30): The specifications and prototype of the final integrated device providing “smart object” functionalities to things in the IoT4All framework.  D2.1.4 Integrated Platform (M36): The final integrated IoT4All Real-World platform, including smart devices, capillary network gateways and integration into global communication and services platforms.

Proposal Part B: Page 94 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

2.2

Work package title

Distributed Intelligence and Smart Objects

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

Personmonths per participant

M4 â&#x20AC;&#x201C; M33

6 CAEN

7 TELIT

8

8

9

INS

AIT

30

7

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per 12 participant

Objectives: Workpackage WP2.2 aims at making real-world things intelligent actors in the IoT and the Future Internet, by achieving the following objectives: -

-

-

-

Implement smart objects networks where intelligent functions can be deployed anywhere at any object level, exploiting technologies and platforms provided by Workpackage WP2.1 to make things able to recognize each other, sense their environment, connect and share computing and communication resources.

Provide a semantic framework enabling things to exchange knowledge and data with other things, users and systems connected via the F-O-T platforms, by making common definitions (ontologies) and semantic mediation services accessible at object level.

Implement context determination and context awareness, i.e., (i) the ability to interpret in real-time the flow of thing-related data gathered in the real world to contextualize events, services access and interactions, and (ii) the ability of things to adapt to their context in terms of location of use, the nearby services, people, hosts, and accessible devices and resources, as well as to changes to such things over time.

Support event-triggered, decentralized decision-making, where local and remote users, including the things themselves, are immediately alerted of exceptions, informed of the likely consequences on different time horizons, and presented with the available exceptionresolution options.

Proposal Part B: Page 95 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Description of work This workpackage consists of the following tasks: T2.2.1 Smart objects networks (Insiel): This task will provide for the objects’ ability to recognize each other, interact and access F-O-T service networks. The work on smart objects, enabled by devices and communication platforms provided by WP2.1, will focus on: (i) objects identification, targeting self-identifying objects, through coexistence of global IDs (e.g., EPC) with local and application-related identities; (ii) interoperability at object level, aimed at exchange of information, computing and communication resources among constellations of objects; (iii) object-centered services, aiming at SOA approaches where the things themselves are seen as service providers and consumers.

T2.2.2 Semantic framework (Insiel): This task will deal with the specification and technical implementation of an object-centred semantic framework to support the things ability to detect their context, to mediate information across multiple domains, and to apply reasoning methods. To this purpose, the Task will identify the needed knowledge repositories, modelling methodologies and semantic tools, considering existing ontologybased solutions and emerging standards (e.g. ontology based on OWL, RDF, KIF, conceptual graphs (CGIF), decision support rules, etc.), appropriately enhancing the state-of-the-art where needed to bring in the required object-centric approach.

T2.2.3 Context detection (Insiel): This Task will provide for context-awareness of objects in the future IoT, through the definition of a model describing the contextual information of the things in different application domains. The context model will map and relate entities of four main types - Process, Service, Rule and Information - according to the domain and layer of relevance: (a) the Info entities represent information aspects of the thing in relation to a certain domain, (b) the Process entities refer to the actions performed by or on the thing; (c) the Rule entities represent international standards, regulations, recommendations, guidelines, legislation, policies, applying to the thing, and (d) the Service entities represent the F-O-T platform services applying to the thing. The Task will provide the means to define the things contextual space and to understand the thing context, in its various aspects, from its current position along the Real-, Digital- and Socio-economic world dimensions.

T2.2.4 Object intelligence (Insiel): This task will integrate advanced knowledge and context technologies to provide extensive analytics and reasoning both in the local object domain, enabling the object to reason on ambient information and enact changes, and in the global domain, i.e., the environment that influences (remote users, business, policies) and is being influenced by the thing. The main advance expected in respect to other “Intelligence services” is contextualization of information. Context models that will be developed in T2.1.3 will form the needed background for deep reasoning, adaptation and personalisation of services. The main services that will be developed are: distributed data analysis, for offline and real-time decisions support Deliverables Milestone 1: Initialized (8)  D2.2.1 Smart object networks specifications (M8): The report contains the design specifications of identification, interoperability and services access features required for IoT4All smart objects.  D2.2.2 Semantic framework specifications (M8): The report contains the design specifications

Proposal Part B: Page 96 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

of the semantic framework components and tools required to define and use things-centered knowledge bases.  D2.2.3 Object intelligence specifications (M8): The report contains the design specifications of the distributed data analysis, knowledge discovery and anomaly detection services associated to IoT4All smart objects.

Milestone 2: Established (18)  D2.2.4 Context model (M18): The report specifies the structure and content of the IoT4All formalized context model.

Milestone 3: Refined (30)  D2.2.5 Smart objects identification and interoperability (M24): The final integrated prototype of the IoT4All smart objects platform, including identification, interoperability and SOA integration.  D2.2.6 Context-detection prototype (M24): The prototype IoT4All context-detection service, allowing local and global context understanding based on real, digital and socio-economic world contextual data.  D2.2.7 Object intelligence prototype (M30): The prototype IoT4All object intelligence services as designed in D2.2.3.

Proposal Part B: Page 97 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

2.3

Work package title

Smart Spaces and User Interaction

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

15

M4 – M33

6 CAEN

7 TELIT

10

8

9

INS

AIT

10

10

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per 10 participant

Objectives:  To design and develop Real World physical smart spaces for IOT4ALL pilots  To design and develop the mobile-wireless-wearable side of the Smart Space  To design and develop the modality of interaction between things and humans (HTI)  To design and develop innovative multi-modal interaction features.

Description of work T2.3.1: Design and development of Physical Smart Spaces (M7 – M36) The IOT technologies require some Smart Spaces to really show all its potentials. Existing mock-ups of such smart spaces do already exist in our test cases (a mock-up of an IoT car, of an IoT assistive room, of an IoT container, of an IoT homeland security. This task will analyse the requirements of the new IOT4ALL scenarios and use cases and design and develop the new physical smart spaces.

T2.3.2: Design and development of Human Smart Spaces (M7 – M36) A Smart Space also includes the human side which is usually represented by wireless or even wearable devices. From an analysis of the pilots scenarios and of their use cases, the proper wireless / wearable devices, operating systems and development environments will be selected and possibly extended.

Proposal Part B: Page 98 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

T2.3.3 Design and development of Human Things Interaction primitives (M7 – M36) This task will design and develop the modality, primitives, protocols and payloads messages which will characterize the interaction in the Real World of the Things with the human uses. We will analyze different Things (e.g. sensors, objects, appliances), different Users (e.g. professionals, IT-illiterates, citizens) in different Contexts (e.g. work, entertainment, usual life). A HTI conceptual and implementation framework will be developed.

T2.3.4 Design and development of Multimodal Human Things Interaction platform (M7 – M36) In some situations (e.g. hand jobs, disability, wearable) the usual HCU interaction modality is not viable. In this task we will analyse the users scenarios and use cases in order to identify the needs for not conventional user interaction, like speech, touch, iconic, gestural interaction.

Deliverables Milestone 2: Established (18)  D2.3.1a Design of the Physical Smart Spaces of the IOT4ALL Real World (M18)  D2.3.2a The Physical Smart Spaces of the IOT4ALL Real World (M18)  D2.3.3a Design of the Human Smart Spaces of the IOT4ALL Real World (M18)  D2.3.4a The Human Smart Spaces of the IOT4ALL Real World (M18) Milestone 3: Refined (30)  D2.3.1b Design of the Physical Smart Spaces of the IOT4ALL Real World (M24)  D2.3.2b The Physical Smart Spaces of the IOT4ALL Real World (M30)  D2.3.3b Design of the Human Smart Spaces of the IOT4ALL Real World (M24)  D2.3.4b The Human Smart Spaces of the IOT4ALL Real World (M30)

Proposal Part B: Page 99 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

2.4

Work package title

Real World Management & Governance

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

Personmonths per participant

M4 â&#x20AC;&#x201C; M33

6 CAEN

7 TELIT

12

8

9

INS

AIT

7

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

15

Objectives: The objective of this Work Package is to deal with the management and governance issues related to the Internet of Things by identifying the synergies, similarities and differences between the Internet of Things, the current Internet and the Future Internet. Internet governance is the development and application by governments, the private sector and civil society, in their respective roles, of shared principles, norms, rules, decision making procedures, and programmes that shape the evolution and the use of the Internet or, in our case, of the Internet of Things. This includes several issues, more than names and addresses, such as critical resources, the security and safety, and developmental aspects and issues pertaining to the use of the Internet of things.

Description of work Task 2.4.1. Define the Real World Management and Governance requirements for IOT [Leading partner AUEB, All other partners involved, M1 â&#x20AC;&#x201C; M24] During this task an extensive review of existing Internet governance practices will be made and a good examination of the relevant work performed by other projects and initiaves on FI and IOT will be sought. Through this compilation and building on the work of the other IOT4ALL work packages, the various governance and real-world management issues of IOT will be identified and a comparison will be made between existing and emerging issues. Issues of legislation will undoubtedly arise with

Proposal Part B: Page 100 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

respect to the Internet of Things, particularly where concerns arise that are of a privacy and security nature. With respect to RFID concerns have been expressed over openness and neutrality of database structure that are used to hold unique identifiers. This is also of direct relevance to the Internet of Things and global coding. Ethical and secure systems management is required with processes that are interoperable and non-discriminatory. These considerations provide lessons for considering the governance requirements for the Internet of Things.

Task 2.4.2. Study and evaluation of alterantive governace schemes [Leading partner AUEB, All other partners involved, M6 – M30] Based on the work performed during the previous task, alternative governance schemes will be identified, which will vary in the degree of synergies achieved between existing Internet, IOT and FI, centralization or decentraliation, distribution of power, control structures etc. These alternative governance schemes will be evaluated, based on the perspective of different stakeholders and taking into account both economic/financial and policy criteria as well as the degree to which the various governance requirements are met. Focus groups with experts, interviews with various stakeholders, value-chain analysis, financial assessments etc. are indicative instrucments that will be employed to perform this task.

Task 2.4.3. Development of governance recommendations [Leading partner AUEB, All other partners involved, M18 – M30] Following the previous two tasks, a range of issues will need to be addressed in developing the governance recommendations for IOT. The European Commission consultation process on RFID revealed that 86% of respondents supported the need for a “governance model that is built on transparent, fair and non-discriminatory international principles, free of commercial interest”. In view of the latent requirement for integrating the Internet of Things with that of the Internet it is important that proposals for governance and other issues are considered in cooperation with relevant authorities and organisations involved with parallel developments of the Internet. Within Europe the European Future Internet Assembly is an example of such an organisation in which one of its aims is to develop the tools and approaches harnessing the potential of the Internet of Things.

Indicative recommendations refer, for example, to the need for a registration authority for identifiers, included within a global scheme for resolving identifiers, recommendations regarding revenue and registration schemes that will be needed and the political framework that will be necessary to facilitate appropriate international collaboration, the establishment of a top level Internet domain as a platform for supporting a federated development of the Internet of Things structure, applications, services and governance etc.

Deliverables Milestone 2: Established (18)  D 2.4.1a Real World Management and Governance Requirements for IOT (Μ18)  D 2.4.2a Evaluation of Alterantive IOT Governace Schemes (M18) and Milestone 3: Refined (30)  D 2.4.1b Real World Management and Governance Requirements for IOT (Μ30)  D 2.4.2b Evaluation of Alterantive IOT Governace Schemes (M30)  D 2.4.3b IOT Real World Management and Governance Recommendations (M30)

Proposal Part B: Page 101 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

3.1

Work package title

Novel IoT Cars Diagnosis Applications

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

M4 – M33

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

7

25

7

8

9

TELIT

INS

AIT

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

Objectives: This activity aims at investigating the scenarios for the “Novel IoT Cars Diagnosis Applications”. The overall goal is to develop the methodologies, on-board and off-board technologies, interaction and service architecture to enable the proactive and autonomous collaboration between different classes of objects towards diagnosing and solving on-board failures of the vehicle functionalities: “the SelfRepairing Car”.

The detailed objectives of the application are to create, maintain and manage the knowledge acquired between different objects; to use fusion and conflict resolution in case of data acquired by different internal and external sources; to build innovative services and a resilient services architecture in the usage phase of the product lifecycle

The objective of this application is, in collaboration with research Activities 1, 2 and 4, to develop the suitable scenarios adapted to the IoT4all vision and to identify, prioritise and share the requirements for the technologies developed in Activities 1, 2 and 4. The application will also contribute to the development of methods in these technical work-packages, on an iterative basis.

The process to be evaluated in the first phase of the analysis regards essentially the usage of the vehicle and in particular the diagnostics, troubleshooting and recovery of the vehicle functionalities.

For each of these phases it is expected to assess in details how products will be able to collaborate within the Internet of Things with people, machines, tools and all level of intelligent objects in order to fulfil the common goal.

Proposal Part B: Page 102 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

In this work—package we address the following issues: 

Identify, specify and model activities in which the Internet of Things can be applied to the Self-Repairing Car;



Identify persons, activities and contexts, to enhance the interaction and experience of people with the Self-Repairing Car;



Provide and refine data for technical development;



Define requirements for technical development;



Adapt and develop application-specific modules;



Implement the design on selected activities;



Refine design, specifications and scope of the application.

These activities will be performed on an iterative basis, to take into account the evolution of techniques, business and clients perspectives.

Description of work To support the activities listed above, the planning of activities in the work-package include the following tasks: Task 3.1.1: Scenario Definition [Leading partner CRF, All other partners involved, M4 – M9].

The goal is to identify the specific critical requirements and to determine if IoT4all technologies and methodologies will meet them on the defined application. Some preliminary data collection is required and it helps to understand the importance of the current state process and how the current states impact on the critical issues.

The activities to be performed in this task are: 

Define the scope of the application and the activities identified



Understand the current state and measure it in diagrams, drawings, documents, etc. to present the uniqueness of the problem



Study the application in order to identify the data that are necessary for the IoT4all purposes; this activity will be performed in conjunction with associated research activities 1, 2 an 4: sample data will be provided, such as processes description, BOMs, drawings, product characteristics and specifications, context information;



Illustrate the relationship between the critical issues and the current state and the potential impact of IoT4all on the activities;



Documentation of the current state vs. issues.

Activities of this task will produce contributions to deliverable D3.1.1, due in month 9 and be connected to the activities 1, 2 and 4. Continuous interaction with them will ensure the coherence with the overall scope and strategy of IoT4All. Task 3.1.2: Requirements elicitation and analysis

Proposal Part B: Page 103 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

[Leading partner CRF, All other partners involved, M6 – M12].

Based on the previous task, and following the generic guidelines for requirements elicitation, this task will deliver the application-specific requirements, which will be generalised in activities 1, 2 and 4.

Requirements will be linked to these activities and prioritised for the scope of the successive pilots.

Task 3.1.3 Design and implementation [Leading partner CRF, All other partners involved, M13 – M33].

Taking into account the conclusions of the previous task, and the results of the research activities 1, 2 and 4, this task will: 1) develop the detailed design of the Demonstrator on “Novel IoT Cars Diagnosis Applications” and 2) implement the components of the demonstrator based on the IoT4all platform, designing and developing the application-specific modules, on an iterative basis.

The design shall also include the analysis of the data needed and the eventual tools to be developed to enhance field data and / or manage product data and knowledge for this specific application. The activities to be performed in this task are:  Modeling of the selected activities and demonstrator specification  Design of the demonstrator  Description and documentation of the demonstrator  Detailed data regarding the selected activities  Survey and selection of applicable technologies/modules  Implementation of application-specific modules  Customisation of generic IoT4all modules

Deliverables Milestone 1: Initialized (8)  D3.1.1. Scenarios for the “Novel IoT Cars Diagnosis Applications“ (M8) Milestone 2: Established (18)  D3.1.2. Requirements for the “Novel IoT Cars Diagnosis Applications“ (M18) Milestone 3: Refined (30)  D3.1.3. System Design for the “Novel IoT Cars Diagnosis Applications“ (M20) Milestone 3: Refined (30)  D3.1.4 Implementation of components for the “Novel IoT Cars Diagnosis Applications“ (M33)

Proposal Part B: Page 104 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

3.2

Work package title

Novel IoT SCM & Logistics Applications

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M4 – M33

6 CAEN

7 TELIT

15

8

9

INS

AIT

8

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

7

Objectives:  To design and develop services and plug-ins for IoT-oriented Supply Chain Planning  To design and develop services and plug-ins for IoT-oriented Logistics Management  To integrate them into existing SCM/Logistics market and research applications Description of work T3.2.1: Design and development of IoT SC Planning services and plug-ins (M7 – M30) The IoT will pose unprecedented challenges to SC Planning. Firstly, the availability of multiple and huge data sources coming from the trillions of Things requires the development of distributed intelligence planning systems also using autonomous computing and Multi Agent Systems. Secondly, Things become active users of SC Planning and not just passive resources to be allocated. Beyond single, group and community human users of current planning, IoT-oriented SC Planning systems will provide the possibility to negotiate and interact with things. Finally, IoT SC Planning systems will be Realtime distributed systems always-on and in connection with the Real World through a proper layer of middleware and platforms. This means to allow things to arise exceptions and warnings about the real world execution of a plan,.

T3.2.2: Design and development of IoT Logistics Mgmt services and plug-ins (M7 – M30) IoT will allow not just sophisticated and precise location-based services for transported goods (just

Proposal Part B: Page 105 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

RFID based indeed), but also to design and develop new logistics systems like intelligent containers, trucks, cargos, warehouses which could not just capture data from the environment but also preserve and govern ambient conditions by means of proper actuators.

T3.2.3 Integration of the innovative services / plug-in into existing Applications (M13 – M36) On the basis of user requirements, scenarios and use cases, his task will design and develop the integration between IoT oriented innovative services and plug-ins into existing supply chain and logistics applications. Both commercial and research platforms will be considered, integrated and customized for the test cases. Openness and respect of standard will be taken in due account, also in the presence of proprietary applications and value added services.

Deliverables Milestone 2: Established (18)  D3.2.1a Design of the Supply Chain Planning services and plug-ins (M12 )  D3.2.2a The Supply Chain Planning services of IOT4ALL Socio-Economic World (M18 )  D3.2.3a Design of the Logistics services and plug-ins (M12 )  D3.2.4a The Logistics Mgmt services of the IOT4ALL Socio-Economic World (M18 ) Milestone 3: Refined (30)  D3.2.1b Design of the Supply Chain Planning services and plug-ins (M24)  D3.2.2b The Supply Chain Planning services of IOT4ALL Socio-Economic World (M30)  D3.2.3b Design of the Logistics services and plug-ins (M24)  D3.2.4b The Logistics Mgmt services of the IOT4ALL Socio-Economic World (M30)  D3.2.5a Integrated Supply Chain Planning and Logistics Mgmt Applications (M24) Milestone 4: Matured (42)  D3.2.5b Integrated Supply Chain Planning and Logistics Mgmt Applications (M36)

Proposal Part B: Page 106 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

3.3

Work package title

Novel IoT AAL Applications

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M4 – M33

6 CAEN

7 TELIT

8

9

INS

AIT

Personmonths per 7 participant

20

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per 7 participant

Objectives: This activity aims at investigating the scenarios for the “Novel IoT AAL Applications”. The overall goal is to develop the methodologies, interaction and service architecture to enable the proactive and autonomous collaboration between different classes of objects towards diagnosing and solving reallife situations within the context of Ambient Assisted Living as those mentioned in chapter 1.3.1.5.

The detailed objectives of the application are to create, maintain and manage the knowledge acquired between different objects and devices; to use fusion and conflict resolution in case of data acquired by different internal and external sources; to build innovative services and a resilient services architecture in the usage phase of the product lifecycle The objective of this application is, in collaboration with research Activities 1, 2 and 4, to develop the suitable scenarios for AAL situations adapted to the IoT4all vision and to identify, prioritise and share the requirements for the technologies developed in Activities 1, 2 and 4. The application will also contribute to the development of methods in these technical work-packages, on an iterative basis.

In this work package, the following will be addressed: 

Identify, specify and model activities in which the Internet of Things can be applied to real-life AAL scenarios;



Identify persons, activities, devices, technologies, and contexts to enhance the possibilities of interaction and experience of people in the given AAL cases;

Proposal Part B: Page 107 of 203

FP7-ICT-2009-5 26/10/09 v1.0



Provide and refine data for technical development;



Define requirements for technical development;



Adapt and develop application-specific modules;



Implement the design on selected activities;



Refine design, specifications and scope of the application.

IP proposal IoT4All

These activities will be performed on an iterative basis, taking into account the evolution of techniques, business and clients perspectives.

Description of work To support the activities listed above, the planning of activities in the work-package include the following tasks: Task 3.3.1: Scenario Definition The goal is to identify the specific critical requirements and to determine if IoT4all technologies and methodologies will meet them on the defined application. Some preliminary data collection will be required.

The activities to be performed in this task are: 

Define the scope of the application and the activities identified. Define the basic interactions among the cared person, other people, the environment, and devices. Define the basic goals in a real-life context.



Understand the current state and measure accordingly. Study the application in order to identify the data that are necessary for the IoT4all purposes; this activity will be performed in conjunction with associated research activities 1, 2 an 4: sample data will be provided, such as processes description, BOMs, drawings, product characteristics and specifications, context information;



Illustrate the relationship between the critical issues and the current state and the potential impact of IoT4all on the activities. Documentation of the current state vs. issues.

Activities of this task will produce contributions to deliverable D3.3.1, will be connected to the activities 1, 2 and 4. Continuous interaction with them will ensure the coherence with the overall scope and strategy of IoT4All. Task 3.3.2: Requirements elicitation and analysis Based on the previous task, and following the generic guidelines for requirements elicitation, this task will deliver the application-specific requirements, which will be generalised in activities 1, 2 and 4.

Requirements will be linked to these activities and prioritised for the scope of the successive pilots.

Task 3.3.3 Design and implementation

Proposal Part B: Page 108 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Taking into account the conclusions of the previous task, and the results of the research activities 1, 2 and 4, this task will: 1) Develop the detailed design of the Demonstrator on “Novel IoT AAL Applications” and 2) Implement the components of the demonstrator based on the IoT4all platform, designing and developing the application-specific modules, on an iterative basis.

The design shall also include the analysis of the data needed and the eventual tools to be developed to enhance field data and / or manage product data and knowledge for this specific application. The activities to be performed in this task are:  Modelling of the selected activities and demonstrator specification  Design of the demonstrator  Description and documentation of the demonstrator  Detailed data regarding the selected activities  Survey and selection of applicable technologies/modules  Implementation of application-specific modules Customisation of generic IoT4all modules Deliverables Milestone 1: Initialized (8)  D3.3.1. Scenarios for the “Novel IoT AAL Applications“ (M8) Milestone 2: Established (18)   D3.3.2. Requirements for the “Novel IoT AAL Applications“ (M18) Milestone 3: Refined (30)  D3.3.3. System Design for the “Novel IoT AAL Applications“ (M30) Milestone 4: Matured (42)  D3.3.4. Implementation of components for the “Novel IoT AAL Applications“ (M33)

Proposal Part B: Page 109 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

3.4

Start date or starting event:

Work package title

Novel IoT Homeland Security Applications

Activity type

RTD

Participant number

1

M4 – M33

2

3

4

5

ATOS

TXT

CRF

DKR

ING

CAEN

Participant number

10

11

12

13

14

Participant short name

LISSI

EVID

KIN

NTUA

FZI

7

7

Participant short name

6

7

8

9

TELIT

INS

AIT

15

16

17

18

AUEB

SIGS

ESD

BMT

Personmonths per participant

Personmonths per participant

20

Objectives: This scenario will deal respectively with a ‘civilian’ homeland security application (protection of highly secured buildings). It concern a ‘homeland security application”, in the ‘civilian’ meaning of these words. More precisely, it will concern an integrated smart surveillance system able to ensure optimal monitoring and control against threats or malicious attacks of highly secured building such as critical infrastructures and utilities having very restricted access and high availability/security requirements.

The main idea is to take a step forward in the integration of security subsystems through the use of a centralized command and control system that creates building situation awareness picture. This is achieved by collecting all information provided by the security subsystems – token/smart cards, vision (tracking, abnormal behaviour), voice recognition, Indoor-Location Based-Systems (ILS), monitoring & control and also rule-based systems for decision making – and correlating by inference, at the conceptual level and after the ‘recognition/categorization’ phase, information coming from these different sources to establish a snapshot of what is the real situation in a building at a specific moment. We can note, in fact, that technologies will provide inputs individually but this information may not be sufficient to make up a decision on what is going on. It is the correlation of all the technologies, implemented thanks to the RWEs paradigm, which will provide more complete information to be used to improve the decision on what is happening.

Description of work This workpackage consists of the following tasks: T3.4.1 Survey of current Homeland security techniques:

Proposal Part B: Page 110 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

To begin with, we will commence a full investigation of current IT-based applications to homeland security. All technology used in the field at present needs to be catalogued and understood in order to get a clear representation of the present methodology for dealing with these threats. This database can be used to better understand the potential niches for an internet of things application to homeland security.

T3.4.2 Implementation of novel homeland security techniques: Implementation of an internet of things approach to one or more aspect of homeland security. These will be identified from the first task. BMT and partners will work towards a solution pertaining to an aspect of homeland security. This could be hardware, software or possibly merely a theoretical solution. The application will provide an interconnectedness that will enable faster propagation of data or services. This will result in a better experience for all users of the service.

T3.4.3 Linking novel homeland security technique to other areas within the project: This task will involve looking at the potential impact of the changes that are to be made in task 2. An attempt will be made to quantify the full usefulness of the output of task 2 and determine the potential applicability to other sections of this project. Links will be forged with the other tasks, so this task should begin at a low level early on in the project.

Deliverables Milestone 1: Initialized (8) ď&#x201A;ˇ D3.4.1 Report on the current state of affairs in homeland security (M8): This will be a thorough review of all current homeland security measures that are currently undertaken.

Milestone 3: Refined (30) ď&#x201A;ˇ D3.4.2 Report on the novel implementation within homeland security (M30): A report on the new homeland security measure(s) that is(are) developed in this task.

Milestone 4: Matured (42) ď&#x201A;ˇ D3.4.3 Report on State of improvements (M36): A report on how the new measure(s) impact upon the rest of the project and integrate with the remainder of the project.

Proposal Part B: Page 111 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

3.5

Work package title

Socio-economics, Business models & value proposition

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

M4 – M33

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

7

8

9

TELIT

INS

AIT

Personmonths per 10 participant

7

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

7

28

Objectives: The impact of innovative Business Models in the development of the Internet in general and web 2.0 applications in particular could not be underestimated. They were not only the enablers of many of this projects but also played a key role in the adoption process that diffuse these practices and by doing that allowed new innovation to appear.

The so called “Internet of Things”, presents an scenario that is not totally different. There, we also find this effortless capacity of aggregation and accessing information, however, this time in the real world.

In this area, many times we have found quite an intense exploration of possible scenarios of new services, products and ways of interaction but a limited one regarding business models. These scenarios appealed to the imagination of the technical side of equation but fall short when regarded from the point of view of the market, because even if the value proposition to the customer is clearly expressed, it is not clear how it can be sustained and value captured. There has been, indeed, very little work and exploration in this area and almost none in real life experimentation.

Therefore, exploring the business model part of the proposition could have as much impact in its development and potential adoption as the development of the product itself. This constitutes the objective of this workpackage.

Description of work This is an ambitious workpackage that aims to provide at least some insights on future business models that will be enabled by the Internet of Things. And aims to do so, not only by theorizing what

Proposal Part B: Page 112 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

these business models could be, but with real experimentation in trials when possible and when not in ad-hoc settings.

Based on this knowledge, the workpackage will develop proposals for both value propositions and business models that could address the emerging opportunities that the Internet of Things will bring.

Finally the workpackage will develop scenarios that could portray the possible socio-economic impact of the adoption of the Internet of Things with the proposed business models and with them it will attempt to asses the resulting business landscape.

Task 3.5.1. Internet of Things: Assessing the Opportunity in terms of Business Models This task aims to asses the opportunity of Internet of Things in terms of business models by means of a) collecting the best practices from current RFID pilots or implementations, be) capturing the insights and the lessons learned from existing projects and c) tapping into the knowledge and the understanding developed by the experts on the subject.

Task 3.5.2. Development of Value Propositions and potential Business Models This task builds on the previous one, developing potential business models and value propositions that could be used in pilots, prototypes and for wider market adoption. For achieving this result the task will use Design Thinking and Living Labs type of methodologies depending on the type of the project.

Task 3.5.3. Experimentation on Business Models Business models developed in task 2 will be validated depending on the possibilities of the trial, in real life environments. Therefore we could have from validations at prototype level to full scale ones, depending on the objectives of the organization sponsoring the trial and its desired outcomes.

Task 3.5.4. Internet of Thinks, Socio-Economic Impact All this work on business models, will certainly provide a privilege situation for assessing what could be the real impact of the technologies developed in socio-economic terms, and what could be its rate of adoption. Both aspects have a tremendous importance not only at social level but for the development of the technology itself, because the next prototype can only be built on the basis of the success of the previous one.

Deliverables Milestone 1: Initialized (8)  D 3.5.1 Internet of Things: Business Models Opportunities (M8) Milestone 2: Established (18)  D 3.5.2 Internet of Things: Potential Business Models and Value Propositions (M18) Milestone 3: Refined (30)  D 3.5.3 Report on Experimentation on Business Models (M30) Milestone 4: Matured (42)  D 3.5.4 Internet of Things: The Socio-Economic Impact – A Business Model Perspective (M40)

Proposal Part B: Page 113 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

4.1

Start date or starting event:

Work package title

Event Driven Platforms

Activity type

RTD

Participant number

1

M4 – M33

2

3

4

5

ATOS

TXT

CRF

DKR

ING

CAEN

Participant number

10

11

12

13

14

Participant short name

LISSI

EVID

KIN

NTUA

FZI

7

40

Participant short name

6

7

8

9

TELIT

INS

AIT

15

16

17

18

AUEB

SIGS

ESD

BMT

Personmonths per participant

Personmonths per 7 participant

15

Objectives: Development of an intelligent, efficient and scalable Event Driven Platform (EDP), encompassing:  Well-founded models for representing events, complex events and situations  Methodologies for managing life-cycle of complex events  Algorithms for advanced complex event detection and visualisation and  Corresponding tools and adaptors with the goal of analysis and interpretation of atomic and complex events in order to identify meaningful information for decision making and managing corresponding actions.

Efficient integration of the platform in the rest of the architecture Description of work Task 4.1.1 Requirement analyses The state of the research and practice in the areas of event processing will be examined, documented, and discussed with the Consortium in order to find out its suitability to meet the requirements of the pilot applications. Special emphasis will be laid upon specific knowledge representation and reasoning requirements. The As-Is situation of the pilots will be analysed in order to identify specific requirements for each of them.

Special focus will be given to the following trends: a) Data streams in IoT have become extremely complex and heterogenous, b) Business real time (for processing) has become much shorter and c)

Proposal Part B: Page 114 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The requirements for non-trivial (intelligent) analyses are ever increasing Task 4.1.2 EDP Model and methodology The goal of this task is to provide a formal foundation for event processing in the large (language, syntax, semantics), including corresponding methodologies and algorithms for reasoning on largescale event-based systems and streams. The work will be focused on the development of a) a wellfounded model for representing events, complex events and situations, that will ensure validation and enable interoperability between complex events, b) a comprehensive methodology for managing the life-cycle of complex event patterns, from their creation through their evolution.

The Validation property is related to the elimination of any kind of unreliability in sensing by considering the semantic (formal) model of events, e.g. a wrongly calibrated sensor can be detected by comparing values of (semantically) related sensors.

The Integration property is related to the on-the-fly aggregation of events coming from heterogeneous sensors, by keeping their original semantics, e.g. integrating signals from different cameras (on the street) in a unique data stream.

The methodology will cope also with the problem of Discovering new complex event patterns by mining existing data repositories.

Task 4.1.3 Intelligent complex event detection The role of the intelligent (advanced) complex event processing will be researched and algorithms for advanced complex event detection will be developed. We envision three main areas for IoT applications: a) Unknown complex event detection, b) Incomplete complex event detection and c) Unusual complex event detection. The methods will be supported by discovering â&#x20AC;&#x17E;moreâ&#x20AC;&#x153; information about the complex event detection process in real time, called reasoning about the complex event detection processes.

This will enable better interpreting of complex situations by predicting important information in real time and detecting anomalies on the fly.

The ways of propagating reliability information within detection process will be researched as well.

The primary non-functional criteria will be the scalability of algorithms and near real-time processing of information from very large amounts of IoT artefacts.

Task 4.1.4 Complex Event Processing tools On the basis of the previous two tasks, a platform (EDP Service) for complex event processing in IoT applications will be developed. It will consist of: a Management tool (editing, validating, verifying, evolving models) for Event Processing and CEP a Detection tool (advance processing). Two important sub-elements of the Management tool are the Discovery tool and Vizualisation tool.

The software will be developed in two iterations, first and second prototype of the platform.

Task 4.1.5 Testing and integration The developed tools will be tested and thereafter integrated into the rest of the IoT system, as a service.

Special adaptors and interoperability tools will be developed.

Deliverables Milestone 1: Initialized (8)

Proposal Part B: Page 115 of 203

FP7-ICT-2009-5 26/10/09 v1.0

 D4.1.1 Conceptual Model of the Event Driven Platform (M8) Milestone 2: Established (18)  D4.1.2 EDP Methodology for managing complex event patterns (M12)  D4.1.3 EDP tools and adaptors (M18) Milestone 3: Refined (30)  D4.1.4 EDP Service (integrated and tested) (M30)

Proposal Part B: Page 116 of 203

IP proposal IoT4All

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

4.2

Work package title

Service and Cloud Platforms

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

M4 – M33

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

7

8

9

TELIT

INS

AIT

Personmonths per 7 participant

7

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

7

35

Personmonths per participant

Objectives: The main objectives of this work package include:  Analysis of the functional and non-functional requirements related to Service and Cloud Platforms so that are able to support the computing and storage requirements of IoT and provide the necessary levels of reliability, trust, usability and Quality of Service (QoS) as well as interoperability with the rest of the IoT infrastructure;  Evaluation of existing Cloud Platforms based on the identified functional and non-functional requirements of IoT and selection of mechanisms, components and functionalities that need to be included or enhanced;  Design and implementation of the selected components and mechanisms with particular focus on resource discovery, management, orchestration and resource usage optimisation with a cornerstone of our approach being the treatment of the resources as dynamic entities, trust and reputation management, efficient service discovery and composition and QoS provision;  Integration of the developed components into the Service and Cloud Platform followed by exhaustive testing and validation against the identified functional and non-functional

Proposal Part B: Page 117 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

requirements in order to provide a Service and Cloud Platform which will be able to support IoT as a whole as well as the pilot applications that will be developed in IoT4All Activity 5. It should be noted that based on the overall IoT4All plan, an iterative process (including three cycles) in the design and implementation tasks will be followed that will incrementally result in improved versions of the Service and Cloud platform to allow for better control on the anticipated progress versus achieved progress, for incremental evaluation of the platform and for the application of corrective measures through incremental user evaluation and repeated platform adjustment and refinement.

Description of Work Task 4.2.1 Service and Cloud Platforms : Requirements Analysis and Specifications The general requirements for the IoT and well as specific requirements of each pilot case will be analysed in order to come up with a set of specifications that will be used in order to decide on the most appropriate cloud platform for IoT. More specifically we will examine and evaluate the pilot cases as well as the IoT infrastructure as a whole in terms of both computing and storage requirements and non functional requirements such as QoS guarantees, resource management and discovery, trust and security. The outcome of this task will be a full set of specifications that will be fed as input to Task 4.2.2 in order to define the cloud platform that will meet the particular needs of the IoT infrastructure.

Task 4.2.2 Definition of an appropriate Service and Cloud Platform Based on the specifications defined by Task 4.2.1, existing cloud platforms will be examined and evaluated in terms of functional and non-functional requirements (NFRs). In addition to the NFRs set out by Task 4.2.1 special focus will be given to interoperability issues with the IoT middleware infrastructure as well as scalability. The objective of this task is to decide which platform is the most appropriate for the IoT4All scope and what changes need to be made (features added or modified, security enhanced, stronger QoS guarantees, more efficient resource discovery and management, etc) in order to fully meet the IoT requirements.

Task 4.2.3 Platform re-design and implementation The objective of this task is to install and re-design the selected Service and Cloud Platform according to the guidelines set out by 4.2.2. The first outcome of this task will be a technical design document outlining the new architecture of the platform that includes the enhanced features and modifications that have been defined by 4.2.2. Based on this document, the necessary developments will be carried out in order to create an enhanced cloud computing platform tailored to the functional and non functional needs of the IoT. Task 4.2.4 Testing and evaluation The platform produced by Task 4.2.3 will be tested both and integrated with the rest of the infrastructure in order to evaluate both its functionality as well as interoperability among the various platforms and components.

Deliverables Milestone 1: Initialized (8) ď&#x201A;ˇ D4.2.1. Service and Cloud Platforms IoT-specific Requirements Analysis and Specifications (M8)

Proposal Part B: Page 118 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Milestone 2: Established (18) ď&#x201A;ˇ D4.2.2. Initial Service and Cloud Platform design and Components Specifications (M12) Milestone 3: Refined (30) ď&#x201A;ˇ D4.2.3. Final Service and Cloud Platform and Specifications (M30)

Proposal Part B: Page 119 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

4.3

Work package title

Service Front-end & Collaboration Platforms

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

M4 – M33

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

7

8

9

TELIT

INS

AIT

Personmonths per 7 participant

15

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

10

7

Objectives:  Design and develop an open architecture for users to easily access the IoT services  Design and develop an open Platform for IoT Service Front Ends  Design and develop innovative thing-to-thing collaboration/communication services  Design and develop IoT semantic desktop and workspaces Description of work T4.3.1: Design and development of an IoT-oriented Service Front End platform (M7 – M30) The F-O-T platforms federation in the IOT4ALL Digital World also includes the extension to the IoT of an existing SFE platform. The IoS will be dramatically extended and expanded by the presence of trillions of things, hence current SFE solutions risk to fail making such a wealth of knowledge available for users, especially nomadic and mobile users. An IoT-oriented SFE needs to be developed in order to provide users with special services for Real World events and actions.

T4.3.2: Design and development of model-generated workspaces for Things (M7 – M36) This task address the problem of generating workspaces for Things and not just for human users.

Semantic technologies have been so far applied to generate highly customized workspaces for knowledge workers, including personalized search and documents classification. The IoT will pose additional challenges for Things to be enabled to work with other Things, i.e. to be able to generate

Proposal Part B: Page 120 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

their workspace, mostly made of services and not of HCI primitives. What services could be accessed at a certain instant by the Intelligent Car to find diagnosis hints and solutions? Or what services could be accessed by the Smart Container to report an anomaly in the itinerary or to double check some policies and rules?

T4.3.3 Design and development of an open Collaboration Architecture (M7 – M30) OCA (Open Collaboration Architecture) is a reference architecture for CWE (Collaborative Working Environments) in the Internet of Services. It provides a conceptual framework and specifications for designing and developing service-oriented collaborations, through mash-up and light compositions of elementary service components (named CoCos). The advent of IoT will increase not just the number but the typology of users in ad-hoc and planned collaboration projects. Humans could collaborate with Smart Objects and Sensors Networks to find a solution of a diagnosis problem or to find the optimal itinerary for some perishable goods or to take the best decisions in an assistive or emergency management scenario.

T4.3.4 Design and development of IoT open Collaboration services (M7 – M36) Innovative collaboration services need to be developed for the IoT. The ECOLEAD and COIN integrated projects already developed several KSB (Knowledge Service Business) collaboration services in the IoS. The next challenge is to make social-knowledge-business collaboration accessible

by Things, through a set of new services. For instance, services which would allow the creation and govern of a virtual community of cars (social); services which would allow the representation and sharing of multimedia material among Things (knowledge); services which would allow the set-up of a virtual organization of Things, humans, companies to face business opportunities (business).

Deliverables Milestone 2: Established (18  D4.3.1a Design of an IoT-oriented Service Front End platform (M12)  D4.3.2a The SFE innovative services for the IoT (M18)  D4.3.3a Model generated workspaces for Things (M18)  D4.3.4a Design of the Things Collaboration framework (M12)  D4.3.5a The Innovative IoT-oriented KSB Collaboration services (M18) Milestone 3: Refined (30)  D4.3.1b Design of an IoT-oriented Service Front End platform (M24)  D4.3.2b The SFE innovative services for the IoT (M30)  D4.3.3b Model generated workspaces for Things (M30)  D4.3.4b Design of the Things Collaboration framework (M24)  D4.3.5b The Innovative IoT-oriented KSB Collaboration services (M30)

Proposal Part B: Page 121 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

5.1

Work package title

Pilots & Take-ups Methodology

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

M8 – M42

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

7

8

9

TELIT

INS

AIT

Personmonths per 15 participant

6

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

8

Objectives: The first and important step in order to manage a test-cases performance achieving successful results (which implies proper demonstrations about IoT challenges into real cases) is to define a certain methodology which is going to lead the development process of such test-cases. Thus, objectives of this work package are defined as follows:  To establish the same demonstrations concerns focused to apply IoT4ALL approaches to different pilots (with different end-user domains).  To identify phases and iteration in order to perform pilots focused in the same general objective To define guidance and templates in order to be used for obtaining the same expected results from different domains Description of work T5.1.1: General concerns and requirements definition First step is to define general concerns in order to focus test-cases demonstration to the same target based in IoT4ALL challenges. Requirements will be defined by classifying between non-functional and functional requirements. Non-functional requirements will be based in the IoT infrastructure environments defined in priors work packages related to IoT4ALL architecture. Thus, architecture approaches will be adapted through methodology templates.

Proposal Part B: Page 122 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

T5.1.2: Phases and Iterations definition Once requirements has been defined, similarities and differences along all proposed study cases should have been clarified in order to define a methodology which adapts its task process to develop each test-case as an isolated activity but also making them capable to integrate their results for leading the implementation towards at the same monitoring process. It will ease the control of the addressing of researching results oriented to IoT4ALL objectives defined since the very beginning.

Phases will be defined by taking into account features about different domains to be implemented and bases in a base development process opened to be tailored in different industrial environments.

Thus, OpenUP (Open Unified Process) might be an interesting solution as a open source development process which have the basics tools to produce and adapted methodology. Iteration will come as a product after analyzing the complex process which every domain is involved.

T5.1.3: Process Monitoring and Iterative Adaptation Monitoring test-cases implementation performances is going to be based in methodology defined during T5.1.2. This task will be addressed to modify methodology by adapting achieved results from each performed iteration. Milestones are needed to be defined in order to identify a finished iteration and analyze properly the results from this one.

Deliverables Milestone 1: Initialized (8) ď&#x201A;ˇ D 5.1.1: Integrated Requirements definition (M8) Milestone 2: Established (18) ď&#x201A;ˇ D 5.1.2: Pilot Performing Methodology (M18) Milestone 3: Refined (30) ď&#x201A;ˇ D 5.1.3: Pilot Performing Integrated Iterated Results (M20)

Proposal Part B: Page 123 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

5.2

Work package title

Pilot 1. i.e. Self-repairing car

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

M8 – M42

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

6

33

7

8

9

TELIT

INS

AIT

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

Personmonths per participant

6

Objectives: This activity aims at integrating and testing the IoT4all technologies in the “Self-Repairing Car” pilot, building on the technologies and components developed in research activities 1, 2, 3 and 4.

In concrete, in this work-package we integrate and test IoT4all techniques and tools to: 

Build innovative services in the usage phase of the smart product lifecycle;



Interact proactively with other objects in order to create, maintain, improve and communicate knowledge;



Aggregate, analyse, display and refine information coming from different sources (things, people) and through different means (wireless/ wired, vocal/ textual…)



Fuse and resolve conflict between data coming from different internal and external sources;



Refine and adapt strategies according to the context of use;



Provide a resilient, safe and efficient services framework, also in case of network failure e.g. by distributing and sharing information between objects in the Internet of Things (smart phones, ECUs, tags, etc).

The products rely on the telematics and communication devices on-board to interact with neighbouring objects (other vehicles, road or garage infrastructure, electronic devices and other components taken on-board, external objects such as the garage tools) and remote services providers.

Description of work

Proposal Part B: Page 124 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Task 5.2.1: Integration and pilot tests [Leading partner CRF, All other partners involved, M8 – M40].

The application will provide a real-world problem, on which testing activities will be performed, in order to provide useful feed-back on the technology development work-packages based on real tests and to enable to proceed with the spiral implementation. The activities will be to: 

Define the users, tasks and context of use



Set up the objectives of the demonstrator



Achieve the application-specific system integration and customisation

Task 5.2.2: Pilot Evaluation [Leading partner CRF, All other partners involved, M28 – M42].

The major tasks of the evaluation and validation plan are to: 

Set up the validation, analyse data and results



Verify if goals were achieved



Archive information for re-use, reference and values.

The task will also identify the technical risks for implementation at the industry level.

Task 5.2.3: Critical Issues and Barriers (Business) [Leading partner CRF, All other partners involved, M28 – M42].

This task will address the critical issues and barriers for implementation, and develop a roadmap for implementation at the industry level, taking into account the technical and business risks.

For this purpose, the task comprises the following activities: 

Define roles, activities, and documentation templates



Model reference processes based on the results and experiences of work-packages 3.2 and previous tasks

 Identify and formulate performance indicators for controlling these processes Develop a roadmap for implementation on an industry level including analysis of current barriers and risks.

Deliverables Milestone 4: Matured (42)  D5.2.1. Pilot Implementation of the “Self-Repairing Car” Application (M40)  D5.2.2. Test and Evaluation Report of the “Self-Repairing Car” Application (M42)  D5.2.3. Roadmap for Industry Level Implementation incl. Analysis of Critical Issues and Barriers (M42)

Proposal Part B: Page 125 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

5.3

Work package title

Pilot 2. i.e. Sustainable Logistics

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

6

10

M8 – M42

6 CAEN

7 TELIT

6

8

9

INS

AIT

15

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

6

15

Personmonths per participant

20

Objectives: The aim of this WP is to support the Sustainable Logistics pilot, deploying the IOT4ALL architecture in industrial settings and assessing its overall performance and the delivered value. WP 5.3 has the following objectives: • To elicitate the requirements for the sustainable logistics scenario • To design and develop the specific sustainable logistics services, building on the IOT4ALL architecture • To run a field trial and monitor the performance of individual modules as well as the performance of the system as a whole • To evaluate the trial’s results against the project objectives • To explore how the system can be used to raise the consumers’ environmental consciousness Description of work Task 5.3.1. Sustainable Logistics Scenario Requirements Analysis The aim of this task is to capture the user requirements through a set of interviews with the participating user company (DIAKINISIS) as well as involving other user companies and selected product suppliers from the FMCG sector. The user requirements shall indicate the desired functionality of the system. The necessary energy, environmental and operational data that the system should capture and manage, indicating linkage with existing systems, will be defined.

Proposal Part B: Page 126 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Furthermore this task will include modelling of existing processes, automatic data-capturing requirements and requirements related to the overall IOT4ALL architecture.

Task 5.3.2 Sustainable Logistics Services Design and Development This task will design and develop (making the appropriate customisation) the prototype modules supporting the sustainable logistics services to facilitate the monitoring of environmental profile of products and processes in all relevant aspects (carbon, energy, other parameters). This task will build on the Novel IoT SCM and Logistics applications developed in WP3.2 and on the overall IOT4ALL underlying architecture. Testing and integration with the rest of the IOT4ALL architecture and the user company’s ERP system is also included in this task.

Task 5.3.3 Field Trial Preparation This task will make all necessary preparations for the field trial to start. The involved partners shall initially identify the required infrastructure regarding hardware, software, human resources, possible operational reconfiguration and any other asset/resource that needs to be in place for the trial. The task’s aim will be to ensure that the complete system infrastructure, including all required peripheral resources, is deployed and are fully operational before the start of the trial. Any problems shall be promptly identified and resolved within the task’s scope.

Task 5.3.4. Field Trial This task will carry out the actual field trial, during which the proposed infrastructure will be tested in real industrial settings. The involved partners will train the end users and analyze the system’s aims and functionality in order to ensure a smooth system adoption. The system’s performance shall be closely monitored and the maximum possible availability shall be targeted. The trial shall be evaluated against the initial project objectives and user requirements. Any special issues resulting from the use of the system (e.g. operational, political etc) shall be explicitly reported.

Task 5.3.5. Overall Assessment and Business Validation The aim of this task will be to evaluate the system’s effectiveness and assess its impact on business operations. The system will be evaluated with regard to its availability, scalability, responsiveness, security and any other aspects that will be defined as critical. In addition to that, the business impact that the system had will be assessed, especially the extent to which the system contributed towards greener operations and strategies, better use of energy and resources as well as stimulating the firms’ environmental activities in general. Finally, the task shall assess the value of the system’s individual building blocks as seen through the trial, suggesting ways for enhancing them and disseminating their use across the industry.

Deliverables Milestone 1: Initialized (8)  D 5.3.1. Sustainable Logistics Pilot Requirements (M8) Milestone 3: Refined (30)  D 5.3.2 Sustainable Logistics Demonstrator (M30) Milestone 4: Matured (42)  D 5.3.3. Sustainable Logistics Pilot Assessment and Business Validation (M42)

Proposal Part B: Page 127 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

5.4

Work package title

Pilot 3. i.e. Ambient Assistive Living

Activity type

RTD

Participant number

1

Participant short name

ATOS

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

M8 – M42

6 CAEN

7 TELIT

8

9

INS

AIT

Personmonths per 15 participant

6

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUE

SIGS

ESD

BMT

30

22

Personmonths per 10 participant

6

Objectives: This activity aims at integrating and testing the IoT4all technologies in the Ambient Assisted Living pilot, building on the technologies and components developed in research activities 1, 2, 3 and 4.

More concretely, in this work-package, IoT4all techniques and tools will be integrated and tested to: 

Build innovative services in the usage phase of the smart product lifecycle;



Interact proactively with other objects (at home and/or not) in order to create, maintain, improve and communicate knowledge;



Aggregate, analyse, display and refine information coming from different sources (devices that could include householod appliances, PDAs, smartphones, GPS systems, sensors, RFIDequipped hardware) and through different means (wireless/ wired, vocal/ textual…)



Fuse and resolve conflict between data coming from different internal and external sources;



Refine and adapt strategies according to the context of use;



Provide a resilient, safe and efficient services framework, also in case of network failure e.g. by distributing and sharing information between objects in the Internet of Things (smartphones, ECUs, tags, etc).

The products rely on the telematics and communication devices at home to interact with both inhouse equipment and neighbouring objects/people (outside environment infrastructure, relatives’ devices, etc) and remote services providers.

Proposal Part B: Page 128 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Description of work Task 5.4.1: Integration and pilot tests The application will provide a real-world problem, on which testing activities will be performed, in order to provide useful feed-back on the technology development work-packages based on real tests and to enable to proceed with the spiral implementation. The activities will be to: 

Define the main user (cared person), other users, tasks and context of use



Set up the objectives and goals of the demonstrator



Achieve the application-specific system integration and customisation

Task 5.4.2: Pilot Evaluation The major tasks of the evaluation and validation plan are to: 

Set up the validation, analyse data and results



Verify if goals were achieved



Archive information for re-use, reference and values.

The task will also identify the technical risks for implementation at the industry level.

Task 5.4.3: Critical Issues and Barriers (Business) This task will address the critical issues and barriers for implementation, and develop a roadmap for implementation at the industry level, taking into account the technical and business risks.

For this purpose, the task comprises the following activities: 

Define roles, activities, and documentation templates



Model reference processes based on the results and experiences of previous work-packages



Identify and formulate performance indicators for controlling these processes

Develop a roadmap for implementation on an industry level including analysis of current barriers and risks.

Deliverables Milestone 4: Matured (42)  D5.4.1. Pilot Implementation of the “AAL” Application (M40)  D5.4.2. Test and Evaluation Report of the “AAL” Application (M42)  D5.4.3. Roadmap for Industry Level Implementation incl. Analysis of Critical Issues and Barriers (M42)

Proposal Part B: Page 129 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

5.5

Work package title

Pilot 4 i.e. Homeland security

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

2

3

4

5

TXT

CRF

DKR

ING

6

M8 – M42

6 CAEN

7

8

9

TELIT

INS

AIT

6

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

15

6

6

8

Personmonths per 10 participant

10

Description of work Task 5.5.1: System integration [Leading partner EVID, All other partners involved, M8 – M40].

A real-world problem will be selected amongst those the partners work with in their day to day.

These include port security, airport security and health crisis management. The criteria for selection will include the ease with which the problems can be brought into the framework of IoT4All, the benefits to be obtained, the availability of the necessary hardware and the commitment of end-users.

We will then set up the objectives of the demonstrator in detail, define the specific technical requirements, map out the work to be carried out, create the application and integrate it with all necessary ancillary components.

Task 5.5.2: Test and Evaluation [Leading partner BMT, All other partners involved, M28 – M42].

Test and evaluation plans will be created. Whereas test will be concerned mostly with ensuring the system satisfies the technical requirements, evaluation will focus on determining if the system satisfies the overall end-user objectives and brings in the expected social and economic benefits.

Testing will be carried out by the system developers whilst evaluation will be the preserve of the system end-users. Detailed test and evaluation reports will be written for future reference. These will also cover the risks for implementation at a wide EU level. This will feed into the work of Task 5.5.3.

Task 5.5.3: Road Map

Proposal Part B: Page 130 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

[Leading partner EVID, All other partners involved, M28 – M42].

This task will devise a road map for implementation at a wide level. This will be done interactively with the outside community, particularly with the end-user community of the selected pilot. Tasks 5.5.1 and 5.5.2 will enable us to have the demonstration and documentation which will convince outside end-users of both the feasibility and the advantages of the approach. A set of demonstration workshops conducted with a wide participation of outside end-users will elicit the critical issues and barriers to wide implementation as well as the possible approaches to circumventing these obstacles.

The final road map will cover these points extensively and be the basis for actual dissemination and implementation of the results in the wider user group in this domain.

Deliverables Milestone 4: Matured (42)

 D5.5.1. Integrated Pilot Implementation (M40)  D5.5.2. Test and Evaluation Report (M42)  D5.5.3. Roadmap for EU wide Implementation (M42)

Proposal Part B: Page 131 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Work package number

6.1

Work package title

Dissemination & Training

Activity type

RTD

Participant number

1

Participant short name

ATOS

Personmonths per participant

Start date or starting event:

M8 â&#x20AC;&#x201C; M42

2

3

4

5

6

TXT

CRF

DKR

ING

CAEN

6

2

2

3

7 TELIT

8

9

INS

AIT

2

6

Participant number

10

11

12

13

14

15

16

17

18

Participant short name

LISSI

EVID

KIN

NTUA

FZI

AUEB

SIGS

ESD

BMT

4

6

5

2

3

42

2

2

Personmonths per 2 participant

Objectives: The dissemination activities will inform the scientific and technical community about the progress of the project. It will ensure timely impact creation based on IOT4ALL project results with high industry and academic visibility, through raising awareness of project goals, transmitting results and issuing announcements regarding developments.

All dissemination activities have the objective to build and to enlarge the IOT4ALL community.

The members of the IOT4ALL community will become a major driving force of developing and offering an open architecture based on open protocols, in particular to SME`s.

Training Training activities will produce a set of training and demonstration materials and courses and participate in and create in training modules for courses in universities and engineers schools. This will allow the IoT4All partners to develop specialities in other areas of the project and will increase the uptake of IoT4All results in the community.

Description of work T6.1.1 - Dissemination Strategy SIGS will develop a high level strategy for the dissemination of results and project objectives and developments. An inital strategy will be developed early in the project and refined periodically

Proposal Part B: Page 132 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

according to developments in the market and in the project. The strategy defines WHO the stakeholders are (ie target groups for dissemination activity) and WHAT the core messaging and branding of the project is.

T6.1.2 - Dissemination Plan SIGS will coordinate all dissemination activities of the IOT4ALL project. This will be driven by a specific dissemination plan that sets out HOW, WHEN and WHERE dissemination actions will occur. This plan will ensure that activities such as press releases, journal articles and event attendance are timed to coincide with important developments inthe project such as the release of results, and that they are coordinated between partners.

Such actions include, but are not limited to: press releases, blog posts and content seeding, branding, Wikipedia, whitepapers, newsletters, peer-reviewed journals, conferences and demonstration events, flyers, merchandising, interviews, videos, webcasts, tutorials, workshops and webinars. The dissemination plan also considers the role of social media (eg. YouTube, Linkedin, Sharethis, Digg, etc) for dissemination means. It is clear that not all these tools will be appropriate all the time. The merits of each must be evaluated regarding the intended audience, the message to deliver and our ability to apply them.

Nonetheless we have already identified that the project web page will be an important focal point of the strategy. Not only is it an indispensible way for the public to contact us, but through the application of web marketing techniques, it become well known within a very short period of time within the European software engineering community as well as the financial services and e-tourism community. This gives us a very powerful tool to drive uptake of results. We also are committed to the use of scientific journals and conferences which are an established method of recording and present findings and opening debate on them.

The plan will be renewed on a 12 month basis reflecting to the evolution of the project and the market.

It is important to recognise the resources of that the dissemination manager SIGS DATACOM has agreed to commit, which will be leveraged extensively: Journals - OBJEKTspektrum, JavaSPEKTRUM and BI Spektrum (BI Business Intelligence have a print run of 15.000 copies each and are published each six times a year. They would reserve half a page in each issue to report about the progress of the IOT4ALL project.

Contact database - The SIGS database contains aprox. 75.000 email addresses including addresses from Germany Switzerland, Austria, UK, Scandinavia, Benelux, Italy, Spain etc which all have an Opt in. Advertisements and banners in our monthly Newsletters are addressed to 44.000 recipients. In addition they have another 12.000 addresses in the area of Data Warehousing and Business Intelligence. This would be exploited for mail shots (2 p.a.), newsletters (3 p.a) and surveys (1 p.a.)

SIGS DATACOM Knowledge Library - an important new feature of the website is the “Knowledge Library” which guarantees that significant traffic is taking place on the website and where IoT4All content can be placed. All relevant menu points of the SIGS DATACOM website will be linked to the IOT4ALL website. In addition, a special section on the SIGS DATACOM website will be dedicated to the IoT4All project. Within this section we will promote all the latest information regarding the IOT4ALL project. Traffic will be monitored and report back to the organizers on a monthly basis.

Events – The leading European software conference, OOP, www.oop2010.de, is organized by SIGS DATACOM. We propose to hold as of 2012 an IOT4ALL user conference during this event. Moreover, as of 2011 IOT4ALL will get a booth, free of charge, during the OOP conference. In the OOP programm the project results of IOT4ALL will be communicated to the European software community and in addition TDWI ( The Data Warehouse Institute) will offer a both free of charge, as of 2011, during the annual European TDWI conference.

Proposal Part B: Page 133 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

More details of this can be found in section 3.

T6.1.3 – Recording and evaluating dissemination activities This task compiles a record of all dissemination activities to have occurred and will analyse feedback received on them. The conclusions from this analysis will guide future activities. It is an annual task.

T6.1.4 – Training This task consists of:  Development of training and demonstration material. This will include general presentation of the objectives and the contents of the IoT4All project and introductory tutorials on IoT technologies.  Internal Training Sessions. Organization of specific training sessions for the IoT4All community  External training sessions. Such sessions address a large spectrum of potential users : industry and Service companies involved in the different sectors represented by specific areas of IoT4All. We will emphasize on SMEs and service sectors. All this activity will be performed in strong coordination with the core dissemination activity to maximise impact.

Deliverables Milestone 1: Initialized (8)  D6.1 - Dissemination Strategy (M6)  D6.1.1a Dissemination Plan (M6)  D6.1.2a Training material version 1 (M8) Milestone 2: Established (18)  D6.1.1b Dissemination Plan (M18)  D6.1.2b Training material version 1 (M18)  D6.1.3 Internal training sessions for IoT4All (M14) Milestone 3: Refined (30)  D6.1.4 External training sessions on the use of IoT4All results (M30) Milestone 4: Matured (42)  D6.1.5 – Dissemination Report (M42)

Proposal Part B: Page 134 of 203

FP7-ICT-2009-5 26/10/09 v1.0

Work package number Work package title Activity type Participant number Participant short name Personmonths per participant Participant number Participant short name Personmonths per participant

IP proposal IoT4All

6.2

Start date or starting event:

M6 – M42

Exploitation & International Cooperation OTH 1

2

3

4

ATOS

TXT

CRF

24

6

3

10

11

12

13

LISSI

EVID

KIN

11

8

TR-SLO

5 ING

6

7

8

9

CAEN

TELIT

INS

AIT

3

70

2

2

14

15

16

17

18

NTUA

FZI

AUE

SIGS

ESD

BMT

4

7

2

7

5

Objectives: The objectives of this work package are to ensure the long-term sustainability of the results. This will be done though 1) comprehension of the market and conditions for success, 2) appreciation of our capabilities and delivering a well defined product that builds upon our core capabilities and is competitive in the marketplace 3) a detailed and methodical approach to product positioning (pricing and marketing) and 4) a disciplined and committed interaction between these activities and the release of information through the dissemination work package. This will be broken down in to the following objectives: 

Collect the requirements from the business viewpoint and provide this as input for the architecture and development activities.



Quantify the potential market for results and the critical success factors for their adoption.



Derive and validate a value chain for the sector, identifying points of conflict between roles and understanding the capacities and limitations of the consortium.



Investigate the competitive landscape in terms of direct competitors and substitutes, the bargaining power of buyers and suppliers, the threat of new entrants and internal rivalry.



Define the product at an early stage and refine it as more data regarding market conditions and salient technical innovations are identified.



Develop a positioning strategy and related marketing plan.

In addition, technical results can be exploited on a result by result basis when a secondary application is identified that does not require the entire IoT4All results. The objectives here are: 

Identify the major innovations of the technical results and find strategies within each partner to exploit them.

Proposal Part B: Page 135 of 203

FP7-ICT-2009-5 26/10/09 v1.0



IP proposal IoT4All

Facilitate the establishment of potential joint exploitation activities where appropriate (not necessarily consortium wide).



Establish a dialogue with identified stakeholders to raise awareness and anticipation of results and to identify their requirements (through the dissemination work package).

We foresee in this work package the organisation of 3 industrial international (INCO) advisory board.

Description of work Task 6.2.1: Business requirements, Market Sizing and critical success factors (M1-12) This task provides an initial description of what the IoT4All product is and investigates the requirements that business users will have of it. This can cover a broad range of topics: security, compatibility, usability, cost, requirements, learning curve and so on. It also segments the market according to suitable criteria: customer type, geographic region, end use, economic sector, customer size. Early in this analysis, appropriate grounds for segmentation must be defined. Subsequently analysis will quantify the size of each of these market segments and calculate the RAM (realistically available market) and ascertain the critical success factors for serving that market segment. Here we will use analyst reports, interviews, telephone surveys, guesstimates and internet research to produce the data.

Task 6.2.2: Consolidated Market Analysis (M12-24) This task takes the above market analysis and consolidates with a study of existing competitors, likely competitors and substitutes to understand the industry landscape. We will derive a value chain for the sector so that we can follow the creation and capture of value and how each actor interacts. Is the industry growing?, shrinking?, prone to fluctuations? We will recognise potential conflict and understand profitability drivers. We will use a Porter’s five forces model to model how power lies in the industry: are buyer’s all powerful? This can drive down profitability. Is the threat from new entrants high? This is initially good for us, but how can we protect our position once achieved? The results of this analysis can have implications such as the role that switching costs play in profitability and whether lock in is something we should encourage or discourage in product development.

Task 6.2.3: Detailed product definition and positioning (M24-42) This task takes a look at the technical achievements in the project and defines the offering we can make to the market. We must start to take decisions regarding which segments we will serve. Are we following a niche strategy or a differentiated one? Are we to be low-cost or open source? We must accept the consequences this may have for the technical work. New imperatives may emerge if we decide to be generic or target specific segments. This will be evolved over the last 18 months of the project and the business team must liaise increasingly tightly with the dissemination team to ensure that promotion is addressing the right targets and is ‘on message’.

Task 6.2.4: Individual Exploitation plans (M24-42) As mentioned above, there is another side to exploitation which does not consider the conjunct of project results as a single entity. Alternative applications for components and knowledge are common and each partner will attempt to recognise these alternative applications and how they can take advantage of them. This involves a self-analysis by each partner to recognise target areas and an analysis of available components. Each partner will produce two iterations of an individual exploitation plan, where these will be reported. They can be confidential upon request.

Task 6.2.5: International Cooperation (M12-42) Will foster the organisation of the Industrial advisory board, inviting attendees of the Asiatic countries as well as American.

Proposal Part B: Page 136 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Deliverables Milestone 2: Established (18)  D6.2.1 - Business requirements, Market Sizing and critical success factors (M12)  D6.2.5a – Annually Industrial advisory board will be organized (M12) Milestone 3: Refined (30)  D6.2.2 - Consolidated Market Analysis (M24)  D6.2.3a – Detailed product definition and positioning (M30)  D6.2.4a – Individual exploitation plans (M30)  D6.2.5b – Annually Industrial advisory board will be organized (M24) Milestone 4: Matured (42)  D6.2.3b – Detailed product definition and positioning (M42)  D6.2.4b – Individual exploitation plans (M42)  D6.2.5c – Annually Industrial advisory board will be organized (M36)

1.3.5 Summary of staff effort A summary of the staff effort is useful for the evaluators. We identify the work-package leader for each WP by showing the relevant person-month figure in bold.

Proposal Part B: Page 137 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

PartnerNumber Partner Name Country Type of Organisation Funding

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

ATOS ORIGIN

TXT

CRF

Diakrinisis

INGEMA

CAEN

TELIT

INSIEL

AIT

LISSI Paris 12

Evidian

Kinamik

NTUA

FZI

AUEBELTRUN

SIGSDATACOM

ESADE

BMT

Spain

Italy

Italy

Greece

Spain

Italy

Israel

Italy

Greece

France

France

Spain

Greece

Germany

Greece

Germany

Spain

UK

LE

LE

LE

LE

ACA

SME

LE

LE

ACA

ACA

LE

SME

Research

ACA

SME

ACA

LE

50%

50%

50%

75%

75%

50%

50%

75%

75%

50%

75%

75%

75%

75%

75%

75%

50%

2,00

0,00

0,00

0,00

0,00

0,00

0,00

2,00

ACA

Workpackage Title

WP Lead Contractor

WP0.1 General Coordination

ATOS

MGT

81,00

63,00

10,00

2,00

0,00

0,00

0,00

0,00

2,00

0,00

WP1.1 Architectural Design and Dimensions Coordination

TXT

RTD

80,00

10,00

15,00

7,00

7,00

7,00

10,00

7,00

7,00

10,00

WP1.2 Semi-permeable osmotic *wares

AIT

RTD

48,00

7,00

7,00

15,00

9,00

10,00

WP1.3 Trust, privacy & security

EVIDIAN

RTD

66,00

15,00

30,00

7,00

7,00

WP1.4 Integration, Testing, Verification/Validation

ATOS

RTD

93,00

8,00

7,00

10,00

9,00

12,00

WP2.1 Smart IOT Microsystems and Wireless Sensor Networks

TELIT

RTD

96,00

14,00

9,00

WP2.2 Distributed Intelligence and Smart Objects

INSIEL

RTD

57,00

WP2.3 Smart Spaces and User Interaction

TXT

RTD

55,00

WP2.4 Real World Management & Governance

AUEB

RTD

34,00

WP3.1 Novel IoT Cars Diagnosis Applications

CRF

RTD

32,00

WP3.2 Novel IoT SCM Applications

TXT

RTD

35,00

WP3.3 Novel IoT AAL Applications

ATOS

RTD

34,00

WP3.4 Novel IoT Homeland Security Applications

BMT

RTD

34,00

WP3.5 Socio-economics, Business models and value proposition

ESADE

RTD

54,00

WP4.1 Event Driven Platforms

FZI

RTD

69,00

WP4.2 Service & Cloud Platforms

NTUA

RTD

WP4.3 Service Front-end and collaboration Platforms

TXT

RTD

WP4.4 Semantic Reasoning Platform

LISSI

RTD

WP5.1 Pilots & Take-ups Methodology

ATOS

WP5.2 Pilot 1. i.e. Self-repairing car

CRF

WP5.3 Pilot 2. i.e. Sustainable Logistics

Type of Activity

TOTAL 0,00

7,00 25,00

12,00 38,00

15,00

7,00

35,00

8,00

30,00

7,00

12,00

10,00

10,00

10,00

10,00

12,00

7,00

15,00

25,00

15,00

5,00

8,00

7,00 20,00

7,00

7,00 7,00

10,00

7,00

56,00

7,00

7,00

39,00

7,00

15,00

RTD

29,00

15,00

6,00

RTD

45,00

6,00

AUEB

RTD

78,00

6,00

WP5.4 Pilot 3. i.e. Ambient Assistive Living

INGEMA

RTD

89,00

WP5.5 Pilot 4 i.e. Homeland security

EVIDIAN SIGS DATACOM

RTD

67,00

6,00

WP6.1 Dissemination & Training

OTH

89,00

6,00

2,00

WP6.2 Standardization, Exploitation & International Cooperation

ATOS

RTD

154,00

24,00

6,00

3,00

TOTAL

1514,00

183,00

152,00

65,00

20,00

7,00

2,00

7,00 7,00

15,00

10,00

15,00

7,00 7,00

28,00

40,00

35,00 10,00

7,00

8,00 33,00

6,00 10,00

6,00

6,00

20,00

15,00

30,00

22,00 6,00

2,00

17,00

32,00

3,00

2,00

6,00

3,00

70,00

2,00

2,00

86,00

105,00

112,00

96,00

6,00

10,00 10,00

15,00

6,00

2,00

4,00

6,00

5,00

2,00

3,00

11,00

8,00

4,00

7,00

2,00

102,00

57,00

98,00

89,00

61,00

96,00

15,00

6,00 10,00 42,00

42,00

6,00

8,00

2,00

2,00

7,00

5,00

69,00

52,00

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

1.3.6 Graphical presentation of the components showing their interdependencies

Activity 0

Activity 2

Activity 3

Activity 4

Activity 1

Activity 5

Activity 6

1.3.7 Risk Management A simple but state-of-the art risk management plan will be developed and implemented as a project deliverable within the first six months. The plan will address: 

Identify the risks (of any nature) which might occur in the project.



Assess the likely severity of each risk and its potential impact on the project.



Assess the potential probability of the risk.



Identify the measures which may be necessary, if relevant, to offset or prevent the occurrence of the risk



Identify the measures that may be necessary, if relevant, to minimize the impact of the associated event should it nevertheless occur

Detailed risk management procedures and related contingency plans are described in Section 2.1.8.

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Section 2: Implementation 2.1.

Management structure and procedures

2.1.1. Organization structure and decision making mechanism The management of complex constructs like an Integrated Project requires a very efficient and wellstructured project organization. Of particular importance are the distribution of responsibilities and the flow of information, both for controlling and reporting. A clear conflict management is required to ensure fast and acceptable conflict resolution, while reducing the risks of escalations of disputes. A thorough assessment and analysis of potential risks is also important to prepare cover-up actions if required.

The overall IoT4ALL management structure is shown in the figure below:

EUROPEAN COMISSION

A0 - Project Coordination & Management External International Advisory Committee (EAC)

IPR Audit Committee (IAC) General Assembly

Business Advisory Committee

IP Co-ordination Committee (IPCC)

Reports, directions...

IP Co-ordination (IPC)

IP Manager (IPM)

IP Secretariat (Administrative, financial, legal support)

Executive IP Management (EPM)

Controlling path Reporting path (admin)

Activity 1 Leader

Activity 2 Leader

Activity 3 Leader

Activity 4 Leader

Activity 5 Leader

Activity 6 Leader

Activity 1

Activity 2

Activity 3

Activity 4

Activity 5

Activity 6

Figure 2.1 IoT4All Management Structure procedures

Proposal Part B: Page 140 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.1.2. Management bodies Detailed rules for the composition of the IP management bodies and their decision-making procedures will be described in the IOT4ALL Consortium Agreement.

General Assembly (GA) The General Assembly (GA) is the highest body of the IP. All partners of the Consortium are represented in the GA. Upon recommendations from the Executive IP Management (EPM) and/or the IP Co-ordination Committee (IPCC), the GA takes final decisions on the overall-policy of the Consortium, on modifications or extensions of the Consortium Agreement, or of the objectives of the IP. The IPCC and the EPM will keep the GA informed about the progress and achievements.

The GA shall solve conflicts within the Consortium that could not be resolved by the EPM or the IPCC. Members of the GA shall have differentiated voting power, which is based on their company’s overall contribution to the IP. To reflect in the voting power a mix of money and person-power committed to the project, each partner represented in the GA will have one vote for each 100.000 € share of the total project budget, plus one vote for each person-year provided within the project (parts will be rounded up). Each partner has at least one vote. If the project shares change, the number of votes will be adjusted accordingly.

Decisions on budget (re-) allocation, release of joint funds, replacement of officers, launch of work packages, change of work packages between partners, new Consortium partners, alterations of the Consortium Agreement, or of the contract need a 75% majority as well as a quorum of 2/3 of all parties. For any other decision a majority of the votes and a majority of the parties are required.

The GA meets regularly twice a year, and if more than 20% of the GA members require it. It can take decisions by correspondence. The IP Coordinator will chair the GA. The IP Manager and the Commission IP officer are ex officio members of the GA. External Advisory Committee (EAC) The External Advisory Committee (EAC) advises the IP on its scientific direction. It reviews on a yearly basis the progress made and gives advises on the scientific aspects of the IP (e.g. new academic or technological achievements the IP should consider, new important trends, new societal developments the IP should take into account, etc.). The EAC is also invited to propose ideas on generating new business and exploiting project results further.

High profile industry and academia representatives of related areas constitute the EAC. Every Consortium partner can propose EAC members. The GA, with the consent of the Commission, selects and nominates the members of the EAC. The EAC should have not more than 7 members. The EAC meets once a year or upon specific request by the GA. The IP Coordinator shall chair the EAC. The IP Manager, the Commission IP Officer and the Work Package Leaders shall be represented at the meetings. Suggestions from the EAC are sent to the IPCC and may be forwarded to the GA. The GA decides on acceptance or consideration of EAC proposals forwarded to them, or may leave the decision to the IPCC.(Patrick GUILLEMIN – ETSI Cluster of European Research Projects on IoT Coordinator will be part of the IPCC.) IPR Audit Committee (IAC) The IPR Audit Committee is a small group, which shall meet once a year or upon request by the GA. The IPR Audit Committee will assess all IPR relevant information that was brought in the project or was developed within the project. Based on the ownership of IPR, access rights and use of results shall be determined and regulated. The IPR Audit Committee gives recommendations to the GA on the handling of the assessed IPR issues. The IPR Audit Committee shall consist of not more than three experts with IPR background recruited from the Consortium partners.

Proposal Part B: Page 141 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Business Advisory Committee (BAC) The Business Advisory Committee (BAC) shall be composed of high profile business managers recruited from the Consortium partners. It is expected that about 3 experts should come from large corporations and 1 from SMEs (these numbers are only indicative). The BAC shall develop concrete proposals how new business may be generated and how exploitation should be organised from the project results. Any GA or IPCC member can propose BAC members. The GA decides on the composition of the BAC. The IP Coordinator will chair it. The IP Manager is an ex-officio member of the BAC. IP Co-ordination Committee (IPCC) The IP Co-ordination Committee is responsible for the technical overall management of the IP and the co-ordination between the different work packages. This includes assessment of progress reports, maintenance of work plans, resource re-allocation (if required) and first level conflict resolution. The IPCC meets regularly monthly and works continuously between the meetings by email and audio/video conferences. The IPCC consists of the IP Coordinator, the IP Manager, and leaders of activities.

The IP Manager (supported by the IP Secretariat) is responsible for calling the meeting, preparing the agenda, chairing the meeting, and for the minutes. Decisions in the IPCC shall be taken by consensus.

If a consensus cannot be reached, decisions shall be taken by simple majority of all attending representatives, provided more than 50% of all IPCC members are present. In cases of budget and resource (re-) allocation, determining a defaulting party, procedures for the management of knowledge, decisions on technical roadmaps, deciding on press releases and joint publications, a majority of 75% of the votes is necessary. All IPCC members shall have the same voting power. In cases, where no final decisions can be reached, the issue has to be brought to the attention of the GA for conclusion.

Executive IP Management (EPM) The EPM is the intermediary between the Commission and the Consortium. The EPM is responsible for the day-by-day project management of the whole IP. It consists of the following entities:  IP Coordinator (IPC) (including coordinator project manager)  IP Manager (IPM)  IP Secretariat The EPM is the interface between the GA and the IP Execution (Project), and is overall responsible for the success and smooth running of the project.

The EPM will also be personally involved in resolving conflicts and attending all meetings and events where they are needed. The EPM will ensure availability and take measures to be able to respond within 24 hours during working days.

Decisions of the EPM are binding and can only be overturned by a concrete alternative decision of the GA. The EPM should consult the IPCC on important issues and aim at achieving consensus, but the IPCC cannot overrule decisions of the EPM on day-to-day issues. However, the IPCC may initiate a change of the EPM members via the GA in case of problems.

The EPM will organise all overall project reports and metrics, ensure smooth operation and timely financial transactions and organise audits by the Commission.

In IOT4ALL the main management responsibilities are split into: The administrative and financial part, which is managed by the IP Co-ordinator, and The technical part, which is managed by the IP Manager

Proposal Part B: Page 142 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

This approach has many advantages, such as a better distribution of the management tasks according to the required skills and experiences, a stronger (because team-based) decision process, an enhanced availability and responsiveness because the IPC and the IPM act as deputies for each other, a less-biased decision making, and a faster management, because parallel work is possible.

Since the management of a big activity like an IP requires a team anyhow, there is no overhead created by splitting the administrative/financial and the technical parts properly.

IP Coordinator (IPC) The IPC is nominated by the IP Consortium and indicated in the contract and Consortium Agreement.

The IPC is responsible for the IP project controlling, in particular for the administrative and financial reporting, project time controlling, co-ordination issues and overall IP activities (e.g. training, dissemination). He/she is also responsible for the correct application of all EU rules, particularly concerning handling the payments and keeping the accounts. The IPC acts as a deputy of the IPM. IP Manager (IPM) The IP Manager (IPM) is nominated by the IP Consortium and indicated in the Consortium Agreement. The IPM is responsible for the overall technical management and technical co-ordination within and between work packages. The IPM is the direct contact point to the Activity Leaders (ALs).

The ALs send all technical progress reports to the IPM. The IPM reports to the IPC and the IPCC. In case of conflicts that cannot be solved by the IPM and IPC, the IPCC or, if this is not possible, the GA shall be contacted. The IPM acts as a deputy of the IPC. IP Secretariat The IP Secretariat provides secretarial, administrative, financial and legal support to IPM and IPC. The IP Secretariat shall have a permanent contact person that also supports project participants, ALs, and IPCC members. At least one person should be permanently available.

Activity Leader (AL) The Activity Leader (AL) is responsible for the technical management of the Activity (A) that has been assigned to him/her. The AL may be supported by a number of WP Leaders of the same Activity. They report to the AL on a regular basis. For all technical co-ordination the AL reports to the IPM. For progress reporting (e.g. quarterly reports, financial reporting, etc.) the AL reports directly to the IPC (always keeping the IPM informed).

Activity Committee (AC) For the main technical activities (A1 to A5) the Activity Leader, all WP Leaders of that activity, and one representative of the parties involved in the activity form an Activity Committee (AC). Each party represented in the AC has one vote only. To be able to decide the AC needs two thirds of the parties participating in the related activity.

The AC is in charge of the co-ordination of the work within the activity, and discusses solutions in case of conflicts. The AC shall meet preferably in connection with technical activity meetings to reduce overhead. Alternatively it can meet by audio-conference or correspondence.

A0 and A6 do not have ACs, because of their special nature as management, co-ordination, dissemination control, training and demonstration activities.

2.1.3. Decision procedures and conflict resolution In general, it is expected that the instructions of overall coordinating WPs (such as WP0.1), or the ones included in technical Activities, mainly Activity 3 and Activity 4 on requirements and architecture) will be followed by the concerned activities, or that conflicting views will be solved bilaterally. In the exceptional case that conflicts cannot be solved on Activity level, the EPM may be called by the respective Activity Leader and asked to solve the conflict.

Proposal Part B: Page 143 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

It is expected that the coordinating tasks will seriously consult the concerned Activities before making any decision and especially ensure that no heavyweight overhead is generated. The goal and thus the metric for the coordinating tasks is always to improve the overall functioning of the IP as a joint project and to improve the quality, consistency and impact of the project results.

If the EPM cannot solve a conflict it must be brought forward to the IPCC for decision. If the IPCC is unable to provide an acceptable decision, the case must be brought to the GA. The GA will make a final decision, if necessary, by weighted voting. This decision is then binding to all management bodies. The EPM will be in charge to ensure that all pending conflicts will be resolved within reasonable time frames. The EPM shall make a decision within 10 working days. If the IPCC needs to be involved, there are another 10 working days until the case is brought to a first decision. If the GA needs to be involved, they shall make a first decision within 20 working days.

2.1.4. Management of knowledge, intellectual property and innovation related activities The management of knowledge, intellectual property and innovation related activities, including exploitation of results and business creation, are handled by the two separate management bodies, the IPR Audit Committee and the Business Advisory Committee. High-level experts recruited from Consortium partners shall staff both bodies. The handling of IPR issues and the management of knowledge shall follow the established guidelines and processes provided in an IP Management Handbook (IP-MHB). The IPR Audit Committee continuously verifies these processes and provides recommendations to improve the processes or to solve problems. It also shall provide recommendations on concrete IPR problems, e.g. use of knowledge, IPR and access rights.

Each partner, who brings an IPR into the project or has developed some IPR within the project, shall give a statement on this IPR on an electronic form provided by the IP Coordinator. Such statement shall include any special requirement for the use of this IPR in addition to or deviating from the standard IPR-rules of the Consortium Agreement. Within one month the other partners may raise objections against such a statement. If no objections have been raised within this month, the statement shall be considered as accepted. Any objections have to be dealt with by the IPR Audit Committee without undue delay.

The Business Advisory Committee has the mandate to work out proposals on exploiting the results in the best way. Also possibilities for creating new business from the project results shall be investigated and possible actions shall be worked out and recommended to the IPCC and General Assembly.

2.1.5. Tools and services for management assistance A number of efficient and proven tools will be made available to all Consortium partners in order to build a management information services and to allow efficient work in distributed work groups.

Tools already in place are: 

Project ‘Paddock’ Server that provides FTP and Web services including e-mail and mailing list servers. These services can manage their own security environment and can be designed according to individual needs of the IP and activities.



GroupWare and knowledge management tools like BSCW, inter-/intranet portals, NetMeeting-type applications.



Online reporting tool for project reporting and collaboration: Project Portal 2.0.

Conference bridges for audio and video conferences

Proposal Part B: Page 144 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.1.6. Management processes and management handbook The overall IP management shall be covered by a number of management processes that shall provide reference rules for all relevant management tasks. These processes are building on current coordinator internal processes that are all ISO 9002 certified and fully documented in the IP Management Handbook (IP-MHB). The IP-MHB has been aligned to rules and procedures requested by the Commission. The following processes are explained in details in the IP-MHB: 

Future directions and maintenance of the constituency This process describes how to define and maintain a vision and targets for the work to be performed by the IP and its work packages. A further objective will be to organise calls for proposals to maintain the constituency and assess submitted proposals according to rules to be decided with the Commission.



Set-up, integration and kick-off of activities This process describes how a most efficient project team should be built and how a welldefined project description should be produced. It also includes rules concerning external liaisons, reviewers, dissemination of results, training, etc.



Management of the IP and/or its activities This process provides guidelines to efficiently manage the IP, activities and WPs and tasks, to control timing and progress of expected results and to assist in case of difficulties.



Reporting and work progress This process describes rules to timely report on progress, achievements and budget consumption. The reporting processes are based on available electronic online reporting tools and a management information database. A number of rules are related to Commission requirements.



Quality assurance and audits This process describes how to obtain external to the project evaluations of the quality of the project work and the results. This process deals also with audits requested by the Commission.



Dissemination and exploitation of results This process describes how dissemination of results should be organised, which media should be chosen and how workshop or training activities should be organised.



Closure of the IP and/or its activities The objectives of this process are to finalise the IP and/or its work packages in a controlled manner and to ensure that all invoices are paid and liabilities are concluded. The conclusion of administrative work is concluded when the Commission has accepted all deliverables, all invoices have been paid and all liabilities concluded.



Operational accounting of the IP and/or its activities The objectives of this process are to ensure an efficient and effective registration of work performed at partners, their invoicing and payment according to rules and procedures set out in the model contract and otherwise specified by the Commission.

Proposal Part B: Page 145 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.1.7. Reporting, Monitoring, Reviewing: towards EC According to Article II.7, periodic activity reports shall be submitted to the Commission Project Officer by the Project Manager every twelve months covering one year of the project, normally followed by a formal review by the Commission supported by an external team of reviewers.

Review or progress meetings may take place at the Commission, at the premises of one of the partners, or by videoconference (progress meetings only), as appropriate and agreed by all parties.

Prior to sending the periodic activity report or progress reports to the Commission, the reports are agreed with all partners. In case of conflicts between partners on what and how is reported, the different positions are recorded in the report.

As self standing documents that give a complete snapshot of the status, achievements and plans of the project, progress reports and periodic activity reports are the primary basis for the monitoring and reviewing of the project by the Commission and the review panel. Progress reports and periodic activity reports shall contain as sections the exploitation and use report and plan as well as the dissemination report and plan. If considered more appropriate, these documents may be separate documents. In this case they will however be attached as an appendix to the respective progress report or periodic activity report. Executive summaries of the deliverables shall not report administratively what has been done, but shall describe in summary the content of the deliverable, e.g. the functionality and status of a prototype, an overview of the architecture of the system to be developed, etc.

In detail, progress reports and periodic activity reports shall follow the same template and shall include: 

objectives and strategic aspects



status, achievements, delays, milestones



key events during the reporting period



list of deliverables



progress and performance per work package in general and per partner



progress versus plan, deviations, corrective actions



work planned for the next period/remainder of the project



proposals for revisions of the work plan or the Description of Work



exploitation/use/technology implementation report and plan



dissemination report and plan



management and co-ordination



effort consumption and other expenditures



executive summaries of deliverables



annexed publications

2.1.8. Management of risks In large, complex and relatively long projects where many partners are involved it is unavoidable that problems occur from time to time. It is of paramount importance that potential risks are clearly identified and assessed, and that the project prepares for repair actions if required.

Potential risks can be classified into one of the following groups: 

Partner problems (e.g. a partner is underperforming or a key partner leaves the project).

Proposal Part B: Page 146 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All



Expertise risks (e.g. a key person with specific expertise leaves the project).



Project execution risks (e.g. key milestones or critical deliverables are delayed).



Agreement risks (e.g. consortium partners cannot agree because of different interests).



Technological risks (e.g. key technologies or components are not available at the expected time).



Dissemination risks (e.g. no major customers for project results are found).



Market and user related risks (e.g. the market environment or the user views change and makes the results obsolete).



Competition risks (e.g. a competing solution comes up and makes the results less valuable).

Several of these potential risks can be assessed from the perspective of their probability and level of (negative) impact. Risks with a high probability and a severe impact are handled with particular caution during the project. The following measures are foreseen to meet these risks: Risk

Risk State of the environment relevance

type

Cause

Effect

art External lost

Rise of new, superior Failure of the project, technologies make expected goals cannot be semantic business met, lack of sustainability process management obsolete

Project objectives lost External relevance

Breakthrough in Failure of the project, Semantic and Business expected goals cannot be Process Technology by met, lack of sustainability another project or an industrial player

Lack of consensus Strategic between Consortium and EU commission with respect to changes to the Implementation plan

Economic or legal Failure of the project misunderstandings, different opinions about state of the art

Management / Operational, organisational overhead Financial higher than anticipated due to unforeseen events

E.g. higher Budget cannot be met communication efforts deadlines cannot be met

Partner consortium

leaves Operational

Change in partner’s Recalculation of the budget strategic goals, partner necessary, search for a disagrees with project substitute development

Operational

Lack of expertise, Deadlines could not be met, economic difficulties, quality of project results are management problems lower than expected of individual partner

Unacceptable performance individual partners

by

Proposal Part B: Page 147 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Staffing and recruitment Operational problems

Lack of qualified staff Quality of project results is available, salary lower than expected expectations can not be met

Key staff illness during Operational critical project phase

External

Deadlines are not met by Operational consortium

Lack of project Time delays, revision of work management, plan unexpected problems with new technologies

Time for development is Operational underestimated

Lack of project Time delays, deadlines cannot management, be met unexpected problems with new technologies

Negative domino-effects Operational due to interdependence of output

Work packages depend Schedule of the project is at on results of their risk predecessors

Budget or Person Month Operational, for additional key skills Financial needed

Unexpected problems Budget cannot be met with new technologies

Integration of individual Operational, WP results not achieved Strategic to form a coherent project

Conceptual weaknesses of the project plan, assumptions of the work plan wrong

Revision of work plan Strategic puts stability of project to a risk

Diverse expectations Time delays, deadlines cannot within the consortium, be met project environment has changed

Use cases representative

Wrong assumptions

not Operational

Deadlines cannot be met

Quality of project results are lower than expected, the fulfilment of all milestones is at risk

Quality of project results are lower than expected, deadlines cannot be met

Potential users / Operational customers fail to understand the usability

Unclear user expectations; misunderstandings by project team, unproven method to capture user requirements

Conceptual failure architecture

Project environment has Total failure of the project, changed, planning expected goals cannot be phase was too short, met, lack of sustainability important aspects were neglected

of Strategic

Software components Operational fail or have limited functionality

Proposal Part B: Page 148 of 203

Quality of project results are lower than expected.

Time delays, deadlines cannot be met

Lack of experience with Quality of project results is certain software lower than expected components, unexpected problems

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

with new technologies Development based on Operational new and unproved technology fails

Unexpected problems Total failure of the project, with new technologies, expected goals cannot be project environment met, lack of sustainability has changed

Decision in favour of External standards with no promising future

Project environment has Total failure of the project, changed, lack of/wrong expected goals cannot be industry partners met; lack of sustainability

Technology require redesign

Project environment has Budget cannot be met, changed deadlines cannot be met

changes External significant

Tools cannot be used or Operational integrated Difficulties accommodate partner consortium

Unexpected problems Quality of project results are with new technologies, lower than expected, lack of planning deadlines cannot be met

to Operational and Management overhead, Time delays, revision of work new Strategic partner integration plan joining difficulties Table 2.1 â&#x20AC;&#x201C; Analysis of potential risks

The risks are classified. For risks with a medium to high probability and severe impact countermeasures and contingency plans are described, and they will be flagged throughout the execution of the project as â&#x20AC;&#x153;risk itemsâ&#x20AC;?. This ensures that all levels of the project special care is taken for those items. For risks with low probability or low impact, and for risks which cannot be foreseen at this stage, the Project Management Team will ensure that these are identified as early as possible, and that necessary countermeasures are taken.

While risk response planning determines the options available to risk response, risk monitoring and control determines contingency strategies and keeps track of the identified, residual, and new risks.

The contingency strategies also ensure the execution of risk response plans, and evaluates their effectiveness.

The contingency plan contains a set of well-defined actions to be taken if a risk related event actually occurs. For every risk we define a contingency strategy which can be executed when necessary. The following list provides an overview of the contingency plans: Risk

Contingency Strategy

State of the art environment Advisory Board continuously observes the technical progress of loses relevance competing technologies addressing the same problems. Guidance by neutral outside experts. AB changes the work plan, if necessary.

Project relevance

objectives

loses Advisory Board periodically reviews the progress in the field of semantic Web, business process management and Web services and changes the work plan, if necessary.

Lack of consensus between EBMP continuously observes the communication with the EU Consortium and EU commission commission and tries to achieve a balance of interest between the with respect to changes to the consortium and EU commission Implementation plan

Proposal Part B: Page 149 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Management/organisational Project board organization and checkpoints will monitor in order overhead higher than anticipated to detect problems early and take corrective action. due to unforeseen events Partner leaves consortium

Consortium is of sufficient strength and diversity for partners to replace if required.

Unacceptable performance by Based on the Bi-monthly Reports and the deliverables the individual partners performance of each partner will be monitored and if necessary corrective actions will be taken.

Staffing problems

and

recruitment IoT4ALL has a split partner concept which can be seen as risk balancing to avoid critical dependencies. Every partner is responsible for their staffing and recruiting.

Key staff illness during critical Critical parts of project will be carried out by more than one project phase partner Deadlines are consortium

not

met

by Project checkpoints will monitor, detect problems early and take corrective action.

Time for development underestimated

is Project checkpoints will monitor, detect problems early and take corrective action.

Case studies can be re-scheduled and re-scoped to mitigate against the delayed delivery of software.

Negative domino-effects due to Project checkpoints will monitor, detect problems early and take interdependence of output corrective action.

Budget or Person Month for A budget shift between the affected partners takes place. additional key skills needed Integration of individual WP Project checkpoints will monitor, detect problems early and take results to form a coherent whole corrective action. not achieved Revision of work plan puts Project board organization and checkpoints will monitor, detect stability of project to a risk problems early and take corrective action Use cases not representative

Close co-operation with industrial partners, case studies can be rescheduled and re-scoped to mitigate against the delayed delivery of software.

Potential users/customers fail to Significant effort will be invested to set up or define a market understand the project benefits driven exploitation and deployment strategy. These activities will be informed by ongoing market and technology watch initiatives.

Conceptual architecture

failure

of The software engineering process is an integral part of the development, architecture will be chosen in a way so that we can react to changes; several fallback variants of the architecture will be taken in account

Software components fail or The architecture provides a balanced design between existing have limited functionality tools and components to be developed, functionalities will be ranked by priority

Proposal Part B: Page 150 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Development based on a new Architecture is sufficiently flexible to react to change, particularly and unproved technology fails with respect to the following key components: ontology, Web services, and business process management. Technology watch is a key project activity.

Decision of standards with no Acceptance by the Industry will be closely monitored, close copromising future operation with industrial partners, a person responsible for managing and watching standards will be nominated Technology changes significant redesign

Tools cannot integrated

be

require Architecture is flexible enough to react to changes, particularly with respect to the following key components: Ontology, Web Services, and Business Process Management. Technology watch is a key project activity. used

or Interoperability and architecture work package will be set up with specific responsibility in this area.

Difficulties to accommodate a Consortium partners demonstrate sufficient flexibility to new partner joining consortium accommodate new partners, PMO ready for additional organisational overhead Table 2.2 â&#x20AC;&#x201C; Risks and contingency plans

The project management approach proposed for IoT4ALL provides mechanisms to identify and resolve potential risks. The Project Management Team will continuously monitor the project plan with its milestones and critical paths. In addition the project has a monthly reporting schedule, which ensures that the management is aware of potential problems on a monthly basis, and can initiate countermeasures long before a problem becomes extreme. The tight control both at work package level (via a WP leader) and at IP management level (Project Management Team and Executive Board) ensures that solutions will be available in time.

As an additional measure the project management will maintain an â&#x20AC;&#x153;issueâ&#x20AC;? database, which will keep track of any issues, and describe the solutions and lessons learned.

2.1.9. Management of resources and payment rules on performed work In the Consortium Agreement the conditions for payment procedures and for resource re-allocation, in case these becomes necessary, are laid out.

As a basic rule all partners receive an initial advance of 40% (of the EU advance payment) according to their assigned budget of the first year. During the following semesters the IP Co-ordinator will control the payment of the remaining budget according to reported work and invoices. Work reporting and payment of performed work will be carried out on a semester basis. Payments will only be carried out if the committed work has been performed. In the negative case payments may be delayed until the work has been delivered. If a partner is not able to deliver the work, the Project Coordinator may re-allocate the assigned tasks to other partners who offer to complete the work.

This procedure, which complies with well-established and proven methods, ensures a high degree of security and flexibility, and will help to assure that work will be delivered according to plan even if a partner may fail to perform the assigned work.

Proposal Part B: Page 151 of 203

FP7-ICT-2009-5 26/10/09 v1.0

2.2.

IP proposal IoT4All

Individual participants

2.2.1. Atos Origin General Information Atos Origin is an international information technology services company. Its business is turning client vision into results through the application of consulting, systems integration and managed operations. The company’s annual revenues are more than EUR 5 billion and it employs over 46,000 people in 40 countries. Atos Origin is the Worldwide Information Technology Partner for the Olympic Games and has a client base of international blue-chip companies across sectors including CPG/Retail, Discrete Manufacturing, Financial Services, Process Industries, the Public Sector, Telecom, Utilities and Media. See www.atosorigin.com.

Atos Origin sae is the Spanish branch of Atos Origin. Atos Origin sae is a founding member of the European Technology Platform NESSI (Networked European Software and Services Initiative) officially launched in September 2005 as industry’s commitment to cooperate in research and innovation, and define a strategic research agenda for the sector. At national level, Atos Origin sae also participates in other technology platforms like INÉS for software and services, eMOV for mobility, eSEC for security, and PROMETEO for embedded systems Atos Research & Innovation (ARI), R&D node of Atos Origin in Spain, is a point of world reference in innovation for the whole Atos Origin group. It is focused on project accomplishment, which combines advanced technological developments and the economic exploitation of results in R&D. Our aim is to leverage our knowledge and experience acquired to concrete projects with clients. ARI consists of 5 technology areas organised into 12 research units: Services (Service Oriented Middleware & Infrastructures, Semantic & Services Engineering, Innovation, Open Source & Software Engineering); Nature (Biotechnologies & Healthcare, Space & Satellite Communications, GIS); Systems; Society (elearning, Social Applications, e-collaboration in Industrial and Rural Environments);and Information Management (Innovative Government, Security); See: www.atosresearch.eu Key People Santi Ristol: Degree in Telecommunication Engineering high degree in 1992 at the Polytechnic University of Catalonia in Barcelona. Master in e-commerce by the Universitat Ramon Llull in 2000.

He has been working in ATOS ORIGIN Spain since 1992 and in R&D Projects for the European Commission since 1994. Currently, he is responsible of all R+D+i Projects related to GRID technologies, Software & Services and Innovation. He is responsible for defining the exploitation strategy of the company related to these technologies.

Josep Martrat: Degree in Telecommunication engineering in 1999 at the Polytechnic University of Catalonia. He is currently responsible for GRID area in the Applied Innovation Department.

His research activities concern the study of GRID technologies and their application in business world. He is Project Manager for GRASP FP5 project and he is also participating in AKOGRIMO project (IP FP6). Experience in collaborating in international R&D projects for the EC in FP5 like GENESIS and ASAP. Ignacio Soler: High degree in Computer Engineering in 2000, at the University Autonomous of Barcelona (UAB) in Barcelona. He is working in ATOS ORIGIN Spain since 2003, belonging to Research & Innovation department in International Public Sector division.

He has been working in several projects for the Core Banking division for the Stock Options in Barcelona, as well as working in R&D for Nokia Networks Barcelona in Cap Gemini Ernst & Young.

Proposal Part B: Page 152 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.2. TXT e-Solutions – ITALY General Information TXT e-Solutions is a private, mid-sized software vendor and system integration company, with its headquarters in Milan and growing branch offices in Genoa, Turin, Bari, Rome, Perugia, Vicenza, Paris and Lyon (F), Barcelona (E), Chemnitz and Halle (D), London (UK), Bussum (N) and New York (US). Thanks to a highly qualified and motivated staff of about 600 people, 90% of which are graduated, the 2008 turnover exceeds 57 million Euro. TXT e-solutions acts on the market through three business areas: 

TXT PERFORM: suite of proprietary software solutions for Supply Chain Management specialized in Fashion & Luxury, Specialty Retail, Consumer Goods, Discrete Manufacturing sectors.



TXT Polymedia: products and services for Media & Channel Integration for broadcasters, media and telco operators.



TXT Next: advanced software systems for Aerospace & Defence, Banking & Finance and High Tech Manufacturing.

The CRS TXT Division (Corporate Research and Innovation) is in charge of medium-to-long term research activities and is / has recently been active in several collaboration projects at Regional, National and European level concerning six strategic research pillars: Enterprise Interoperability (national project SFIDA-PMI, European projects COIN IP, ATHENA IP, INTEROP NoE, ABILITIES STREP, SEEMP STREP), Enterprise Collaboration (national project PROBO, European projects ECOLEAD IP, ECOSPACE IP, E4 STREP, eCoSpace, WearIt@Work, Collabs, MyTreasury STREP), SOA and GRID Computing (national project SFIDA-PMI, European projects SOA4ALL IP, BEINGRID IP, SORMA STREP, CHEMOMENTUM STREP), Software and Service Engineering (European projects MOMOCS and TEAM), Extended Products Identification and Tracking, Internet of Things, Privacy & Security (European projects iSURF, GEMOM; SHIELDS, OpenGarment, TIPPS, NMP K-FLOW, CONCLORE STREP, LEAPFROG CA/IP. Key People Sergio Gusmeroli: born in Sondrio (Italy) in 1961, he worked for CISE Tecnologie Innovative (19871989), for FIAR SpA Space Division (1989-1991), for FIAR Group (1992-1995). In July 1995 he joined TXT Ingegneria Informatica, where he has been since then Project Manager in a number of commercial and R&D Projects. He is author of more than 30 publications in Italian and International magazines and conferences. Since June 2000, he is head of the Corporate Research Unit and operating manager of TXT EU funded projects in the ICT domain. His main areas of competence and experience include E-Commerce, Internet and Intranets and Workflow technologies.

Matteo Villa: born in 1973 and graduated in 1998 at the Politecnico di Milano in IT Engineering. After working for 3M Spa as software engineer, he joined TXT e-Solutions in 2000, where currently he works as project leader in European research projects in the areas of SOA and Grid-based architectures for SMEs supply networks (SOA4All IP, SFIDA-PMI, IST Be-in-Grid IP, IST SORMA), Collaborative Working Environments (ECOSPACE IP), Environmental Risk Management (IST GIMMI), and Cultural Heritage: he has been project coordinator of the EU IST AGAMEMNON project and project leader for take-up on Cutural Heritage in WearIT@Work IP project.

Alex Conconi: Born in Milan (Italy) in 1973, he obtained a M.Sc. (2000) and a Ph.D. (2004) in Computer Science from the University of Milan, where he also served as Research Assistant for three years. He joined TXT in 2004 as a Project Manager, and he has been project coordinator and site manager of several FP6 and FP7 STREPs and IPs. He has published several referred papers in international journals and conferences proceedings. His scientific background is in the field of machine learning, with a particular focus on text mining and search engines technology. He was involved as Technical Manager in research projects about Networked Media, Multimodal Interfaces, Mobile and Wireless Applications, On-line communities and Content and Knowledge management.

Proposal Part B: Page 153 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.3. Centro Ricerche FIAT General Information Centro Ricerche FIAT (CRF) was established in 1976 to enable the innovation, research and development needs of the FIAT Group to be satisfied. The main site of CRF is located near Torino (Orbassano) in North-West Italy with three branches in Trento, Bari and Foggia. Moreover, advanced R&D related to lighting and the welding of plastics is conducted at a satellite facility in the Friuli Region of North-East Italy.

With a full-time workforce of more than 850 highly trained professionals, CRF offers a wide range of technical competencies and is equipped with state-of-the-art laboratories for the testing of power trains, electro-magnetic compatibility, experimental noise and vibration analysis, driving simulationand virtual reality, in addition to facilities for the development of new materials and manufacturing processes, opto-electronics and micro-technologies.

CRF uses innovation as strategic lever and attributes value to its results by promoting, developing and transferring innovation in order to enhance product competitiveness and distinctiveness.

Furthermore, the development of effective, creative and competitive solutions is matched by direct technology transfer, which also includes â&#x20AC;&#x153;on the jobâ&#x20AC;? training of specialised personnel in the different areas.

In this way, CRF provides vital technological support for growth to Fiat Group, its partners and different regions by conducting research and development activities, frequently related to improving the efficiency and safety of mobility and transportation by focusing on the development of vehicles with new architectures and power trains, innovative materials and advanced solutions for telematics and communications, mechatronics and optics.

Centro Ricerche FIAT will provide the points of view of the end-users (Fiat, IVECO), providing requirements, process models, and data as well as the points of view of the technological experts in the area of electronics and telematics applied to the product lifecycle, from development to production, use, maintenance and disposal of a vehicle.

Key People Dr Julien Mascolo: is a project manager in the Infomobility Business Line of CRF. His areas of work in FIAT include the optimisation of industrial processes (Manufacturing, Logistics, Product Development Process). In the framework of joint research project with IVECO, CNH and FIAT Group Automobiles he is also involved in the development of mobility and productivity services based on telematics. He coordinated several European research projects and was involved in many others in the area of Product Lifecycle Management, including the FP6 IP PROMISE (Product Lifecycle Management and Information Tracking using Smart Embedded Systems) and the FP7 IP Smart Products (Proactive Knowledge for Smart Products).

Dr Marina Giordanino: Academic background: Laurea degree in Computer Science (Turin, Italy), 1990. Current Organisation: Project manager at Infomobility Department.

Expertise: includes research and development of methodologies and tools to support knowledge management in automotive product development processes. Since 1993 involvement in several European project most related to KM. In this area, last activities carried out are: Coordination of Application and Testing Area, case study definition, user requirements management and design of a knowledge management system able to extract and sharing knowledge from multimedia sources (XMEDIA); user requirements survey, testing and evaluation of an integrated platforms for the development of web services based applications (SeCSE); contribution to realization of data model and ontology for the management of information to support vehicle repair (MyCarevent); coordination of user requirements management, testing and evaluation of a KM system for the automatic classification of document (Peking).

Proposal Part B: Page 154 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.4. Diakinisis General Information “DIAKINISIS S.A.” was founded in 1977 as the first company to offer integrated logistics services in Greece. As of July 2007 the company was acquired by LSH (Logistics Services Hellas) subsidiary of ELGEKA S.A. group of companies (www.elgeka.gr), present in Athens stock Market.

Today, after 31 years of continuous and successful presence, our company has achieved a leading position in the sector of 3PL (third-party logistics) service providers in our country, with the largest market share (notably 18,5% according to the 3PL sector Study of ICAP dated May 2005), offering pure logistics services and supply chain management solutions.

We may assert a unique know-how, state-of-the-art infrastructure in buildings and mechanical equipment, amplified capabilities for the warehousing, handling and distribution of goods, fully computerized, flexible timetable from 06.00 to 22.00 daily for all working days of the year, as well as an experienced and highly-skilled manpower.

Geographically, our premises are situated in locations of strategic value. Aspropyrgos is known to be a superb location, not only because of its vicinity to the Athens metropolitan area (where more than 50% of the total consumption is concentrated), but also in terms of the easy access to the major motorway networks (Athens-Corinth-Patras Motorway, Athens Ring Road), ports (Piraeus, Eleusis) and railways (New Thriasio Rail Cargo Intermodality Station). Similarly, our Salonica branch in Kalochori is also ideally situated to tap the Salonica metropolitan area, as well as a cross-docking hub for Northern Greece since it is just off the Athens-Salonica Motorway. Finally, our Patras branch in Western Greece enhances further our potential for a prompt coverage of the markets on a panHellenic scale. Also aour company working with two cross docking on Larisa for Thessalia area and the second in Ioannina for Epirus area.

The range of products we handle are: foodstuffs, waters, beverages, spirits, confectionery, pet food, personal hygiene, cosmetics, household cleaning, professional/industrial cleaning, machinery, spare parts & accessories, stationery, books, toys, plastics/polymer raw materials, clothing & footwear, athletics & gymnastics, electrical appliances, electronics, promotional materials, POS, stands and so on.

Our total surface capacity of covered buildings (warehousing and office space) exceeds 175.000 m2, of which 70.000 m3 concern depots for the storage of goods at controlled temperature and humidity.

The total number of SKUs of our clients that we dealt with during the year surpassed 330.000 SKUs through our systems, and the order collection (picking activity, micro-picking, picked layered) reached 7.000.000 invoice lines.

Our sales turnover for 2008 is estimated to 53,0 million euros from pure logistics services, and we are a thirty years profitable company earnings before tax (EBT) around 3,0 million euros.

We have been selected as the only designated company/user from 3PLs to participate in a research program of the Athens University of Economics & Business (A.S.O.E.E.) and the Aegean University sponsored by the Ministry of Development (General Secretariat of Research & Technology G.G.E.T.) concerning the pilot application of track-and-trace “telematics” in vehicle tracking and on dynamic re-routing optimization software development.

Key People Maria Katsika was born in Athens on July 1963. In August 1982 she entered ELGEKA S.A. Group Of Companies, during her studies in Law University of Athens. Through her long presence within the company, she undertook several posts such as: Credit Control Manager, Customer Service Manager, Operation Manager and National Supply Chain Manager, whereas, as of the 01.07.2009 she undertook the position of the Project Development Coordinator of Elgeka S.A.

Proposal Part B: Page 155 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.5. Ingema General Information Ingema Foundation is Spain’s leading private research institute on ageing and disability, supported by one hundred and twenty-one years experience of Matia Foundation hospitals and day care centres.

With headquarters in Saint Sebastian and facilities in Madrid, Ingema currently employs more than twenty researchers coming from different countries and from multidisciplinary backgrounds such as psychology, medicine, chemistry, biology, sociology, nutrition, statistics or economics.

Founded in 2002 to conduct state-of-the-art research, Ingema has grown from a local-focused institute to become an internationally known centre with a solid project portfolio in Spain and Europe, as well as an active partner to universities and institutes in North and South America.

Presently, more than fifty projects have been or are being carried out within one of Ingema’s four main research lines: (a) The promotion of active ageing and the prevention of dependence (b) Rehabilitation and compensation of fragility and dependency (c) Quality of life and quality of attention (d) Gerotechnology Ingema’s takes part in basic research initiatives and also in international multi-partner R&D projects aiming to target the world’s transformation towards an ageing society with inclusive policies for all ages and all people, regardless of their disabilities. For instance, Ingema actively plays a key role in projects funded by the European Commission under FP6 and FP7 such as Hebe, Soprano, Iward, Vital, CompanionAble, i2home, Hermes or Tecforlife, as well as AAL-funded undertakings including AmiE or Bedmond.

At the national level, Ingema is officially linked as “Joint Unit” to the Spanish National Research Council (CSIC in Spanish) and the first of its kind in the field of ageing to accomplish this official category.

Key People Cristina Buiza Bueno: Ms. Cristina Buiza Bueno holds a Bachelor’s degree in Psychology from Universidad Complutense de Madrid and a Master’s degree in Clinical Gerontology and in Neuropsychology from the Universidad Autonoma de Barcelona. She has also achieved the Spanish Advanced Studies Diploma by the Universidad Autonoma de Madrid, in order to write her doctoral dissertation on Severe Cognitive Impairment. Ms Buiza has been working for a long time in a number of facilities with older adults (nursing homes, day care centres, etc. and has performed clinical assessments and interventions to neuropsychologically-impaired patients. She is currently Senior Researcher at Ingema and also takes part in the Matia Foundation Memory and Alzheimer Unit. As well as her colleagues at Ingema, she has been awarded the IMSERSO* Award 2008 to Social Research and Studies, the Obra Social Caja Madrid** 2005 Award to the Best Social Study and the Princess Christina Award 2008 to Studies on Ageing and Disability.

Mari Feli Gonzalez: Ms Mari Feli Gonzalez holds a Bachelor’s degree in Psychology and a Master’s Degree in Neuro-psychology from the University of Barcelona. She has gotten the Spanish Advanced Studies Diploma in 2007 in order to start the writing process of her doctoral dissertation on Parkinson´s Disease. She joined Ingema as a researcher in 2005 and has been actively working in more than twenty-five projects at the European, national and local level. She is also a member of the Spanish Society of Gerontology and Geriatrics and is co-author to more than 20 publications (papers, articles, etc). In 2005, Ms González and her colleagues received an award for study Donostia Longitudinal Study of Non Pharmacological Interventions, a pioneer research in Spain in the field of neurorehabilitation with older adults and Alzheimer´s Disease.

Proposal Part B: Page 156 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.6. CAEN RFID Company Profile General Information CAEN RFID is a privately owned Italian company, leading supplier of UHF RFID readers and tags. The company was born recently as a spin-off of CAEN S.p.A. (Costruzioni Apparecchiature Elettroniche Nucleari), a world-leading company with 27 years of experience in electronics for particle and nuclear physics. The longstanding experience acquired with Physics and Aerospace experiments has been the substrate on which the new developments on Radio Frequency systems have begun. A totally internal expertise and know-how on Radio Frequency electronics and related Software has allowed CAEN RFID to become rapidly a leading European company in manufacturing and supplying UHF systems.

CAEN mission is to provide Customers with the best UHF readers and tags which meet standards and protocol requirements, providing our best support for their integration. Our RFID UHF readers are the state-of-the-art for all vertical applications, are fully compliant with the ETSI and FCC rules and EPC Gen2 protocol, are able to cover distances of 5-6m with on-metal passive tags. As an active participant of ETSI and EPCGlobal working groups, CAEN RFID is committed to provide customers with readers and tags that meet ISO/EPC standards and ETSI/FCC requirements. Thanks to our R&D skills, we can also design specific equipment on a custom basis, thus providing RFID readers and tags for special applications on demand.

CAEN RFID is developing three new business units and in the next future it will focus its effort in: Cold Chain control for Pharmaceutical and Food Industries, Embedded Reader for OEM Applications and Assets and Vehicles Tracking.

Key People Adriano Bigongiari: Graduated in Electronic Engineering at the University of Pisa (Italy). He has been working in CAEN since 1984 with different roles. Since 2006 he has been covering the charge of President of CAEN RFID. Regarding his experience in the management of European Project he has been involved, since 1994, in the coordination of different European co-founded projects in Third (MEPI, I-SMILE), Fourth (MAGIC), Fifth (CARDIS I and II), Sixth (EURI-TRACK) and Seventh Framework Programme (EURIDICE) as well as Italian research programme (Imaging Mammografico Integrato and LogOn).

Stefano Coluccini: Has been involved in the development of firmware and software for the CAEN product integration in customer installations. Today he is responsible for firmware and software design for RFID products. He also designs RFID application scenarios for technology demonstration labs and for RFID pilot installations to the end user. Thanks to his experience in RFID applications, he is now involved in the EPCglobal SAG reader protocol group. He is a graduate of Computing Science from the University of Pisa and joined CAEN in 1997, following industry experience as a software developer. In the IoT4All project he will lead CAEN technical activities of the project, designing and implementing the technical solutions coming from the project constraints.

Fabrizio Bertuccelli: He is involved in RFID applications for anti-counterfeiting on government documents, warehouse logistics and asset management (civil and military), public transportation vehicles tracking (buses, trains, ships), containers tracking and sealing, bicycle identification on sports events, vaccine and drugs temperature monitoring and identification: He is an Electronic Engineering graduate from the University of Pisa (Italy). In past years he dealt in the test set-up for various CAEN projects (LAP, CASA2, CAS-TORE, CASTA). In the IoT4All project he will be in charge of the test activities related with CAEN RFID involvement in the project.

Giovanni Grieco: He is the CAEN RFID Marketing Director. He is Physics graduated at the University of Pisa (Italy) in the field of Particle Physics and has ten-years experience in the Sales & Marketing division of CAEN SpA. In IoT4All project he will act as a bridge point with the real RFID world, offering a continuous view on applications and opportunities.

Proposal Part B: Page 157 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.7. Telit General Information Telit Wireless Solutions Ltd is a Company based in Israel that belongs to Telit Group.

Its business segment is R&D applied to machine to machine M2M technology, and cooperates strictly with R&D labs of Telit Communications SpA in Trieste, Italy.

Telit activities is Israel are focused in leading the sales in M2M market adopting the notion is supplying R&D services to the customer’s, schematics and layout design ,debug and precertification consulting , among other things Telit Israel also developed applications to sale using Telit Modules inside as the cellular engine Telit Israel has laboratories which enable develop applications running with Telit M2M engine equipped with high sophisticated equipment for RF pre certifications such as base station simulators , spectrum analyzer , scopes..

Telit is an internationally leading specialist in wireless machine-to-machine (M2M) technology and is the only company worldwide to offer communications modules for all of the various wireless technologies: it develops produces and markets modules for GSM/GPRS, UMTS/HSDPA, CDMA/1xRTT and Short-Range RF applications. M2M applications rationalize business processes by enabling machines, equipment and vehicles to communicate with each other via mobile networks.

Telit products are used all over the world and marketed via Telit’s offices in Brazil, China, Denmark, France, Germany, Israel, Italy, Korea, Spain, the Republic of South Africa, Taiwan, Turkey, the UK and the USA. Telit’s global distributor network comprises of specialists in wireless technologies and enhances the customer experience in over 56 countries worldwide. Telit Communications PLC is listed on AIM Key People Ariel Aharonovitz: (B.SC + MBA) Ariel Aharonovitz is a R&D Tech manager based in Israel, Tel Aviv, and his experience is on digital/analog hardware. He develops all aspects of board design, such as PCB Design, PCB Layout Supervisor (guides, cross-checking and Customer design development -layout ,schematics and RF-) and project control from development to manufacturing at all stages including working in-house and manufacturing factories abroad. His main task is to implement all design aspects addressed to identify the best architectural implementation in order to provide solutions based on Telit M2M technology. He has an M.B.A (Business. Management) – Beer Sheva University Israel, and a B.S.C.T.E (Electrical Engineering) – Tel Aviv University Israel, graduated with Excellence.

Past experience is as HW manager – Telit Italy, HW team Leader in Motorola Communication Israel, and Project Manager -Cell Data company Haim Rozen: (collage) Haim Rosen has a lot of experience with infrastructure of cellular was responsible on building base stations for cellular nets in Africa for Motorola. This knowledge is enabling to understand the process and signalization between the end-unit and the base station to solve any issue. Haim worked for many years in Motorola supporting the cellular engines also for SW commands perspectives a work which is doing also for Telit Israel. Haim is a electronics collage bachelor

Proposal Part B: Page 158 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.8. Insiel General Information Insiel is one of most important ICT companies in Italy’s public sector. Although Insiel is entirely owned by the Regional Government of Friuli Venzia Giulia, its software solutions successfully compete on the open market with private companies across the entire nation. Its suite of government management applications are a point of reference in Italy and used by large and small public bodies across Italy.

Originally established in 1974 to build and manage the Information System for the Regional government of Friuli Venezia Giulia, Insiel, is today one of the most important companies in the Italian IT services sector for local government, healthcare and services for SMEs. Insiel is well established and respected in Northern Italy and has a growing preence on the international marketplace.

Its clients include regional governments like Friuli-Venezia Giulia, Toscana, Puglia and Calabria, or cities such as Trieste, Udine, Venice and Bari, as well as over 1,500 local authorities. Insiel’s growing area of logistics has been chosen for border terminals and ports across Italy and the newest logistics services for SMEs is winning success with large players like HP, and Oracle but moreover to a number of SMEs in the Industrial clusters prevalent in northern Italy. Insiel also offers numerous training modules for its clients including, dedicated courses, individual o group training schemes, personalized training courses for specific professional roles pertaining to our products, but also generic courses on IT literacy and Public Administration and healthcare concepts.

Key People Paolo Paganelli graduated in Electronic Engineering at the University of Bologna in 1991. He was a research assistant at the University of Modena from 1992-1994, involved in design and development of innovative tools to support advanced production planning in SMEs. From 1994 to 1997 he worked at Democenter, in the Research and Development department. In 1997 he joined Gruppo Formula, as senior analyst involved in the design of Formula’s next generation ERP software. He has been Project Manager of the EU projects PLENT, FLUENT and WHALES. He became product manager of Formula’s supply chain management solutions where application development is focused on the integration of platforms and systems. He is now Insiel’s head of Logistics Solutions, where he has the responsibility of the business line dealing with advanced ICT systems for logistics in the private, public and healthcare markets. Paolo is Coordinator of the EURIDICE Integrated Project, the EU lighthouse project on Intelligent Cargo.

Margherita Forcolin qualified IT Project Manager with more than ten years of experience in International collaborative projects, now in charge of the European Research Projects office at Insiel.

Following graduation from the University of Trieste in 1984 she began working with INSIEL as an analyst expert in Object Oriented methodologies. Since 2002 is a project manager leading company team implementing horizontal software components for the interoperability framework to be used in e-governmental infrastructure (national co-financed projects IESS and SIRV-INTEROP). Since 2006 she was general project manger and coordinator of several large collaborative EU funded Research Projects, being technical coordinator in FP6 IST project TOOLEAST, team developing coordinator in FP6 IST project GENESIS. Currently Forcolin coordinates the integration and development activities in FP7 IST project EURIDICE. Valentina Boschian graduated in Management and Logistics Engineering at University of Trieste in 2008. She is a phd student at the University of Trieste and her research activities regard logistics topics. She is working on the EURIDICE project collaborating with Insiel Spa.

Proposal Part B: Page 159 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.9. AIT General Information The Athens Information Technology (AIT) has been recently founded with the vision of becoming a world class education and research centre. As a first step AIT signed an agreement with the Carnegie Mellon University (CMU) and the Information Networking Institute (INI) of Carnegie Mellon to set up and operate a joint Carnegie Mellon-AIT Master in Information Networking (MSIN) Program. AIT has strong relationships with the global IT and networking industry, as well as with the major IT and telecom industries in Greece. AIT is closely collaborating with the largest Greek IT and telecom industry (INTRACOM S.A), towards exploiting and disseminating research results.

AIT participates in SPIN through its Autonomic and Grid Computing Group. The Autonomic and Grid Computing Group (AGCG) of the AIT aspires to achieve secure, pervasive, human- cantered, highperformance computing through a combination of user, network and systems technologies. The group has more than 15 members (possessing MSc and Phds) and a rich track record of FP6/FP7 projects including the CHIL FP6 project (FP6-506909), the HERMES (FP7-216709) project on ICT and ageing well, the ASPIRE (FP7-215417) project on RFID Middleware, the SpeechTV project on speech enabled devices, as well as the PRIAMOS project (funded from the Greek General Secretarial of Research and Technology) which emphasizes on programmable middleware for situation identification and sophisticated context-awareness.

During the last couple of years the AGCG group has developed the following prototype systems: a fully fledged Open Source RFID middleware system http://wiki.aspire.objectweb.org/ ), a face detection system, a face recognition system, a 2D person tracking system, a 3D person tracking system, an audio source localization and tracking system, a Grid middleware scheduling system based on dynamic resource predictions, as well as autonomic middleware components significantly accelerating the development of human centric applications in smart spaces.

Key People Prof. John Soldatos, PhD, (born in Athens, Greece in 1973) is with Athens Information Technology (AIT) since March 2003, where he is currently an Associate Professor. Dr. Soldatos has had an active role (wp-leader, technical manager, project manager) in more than 20 EC co-funded research projects in the scope of the ACTS, ESPRIT, FP5-IST, FP6-ICT and FP7-ICT frameworks. Dr. Soldatos has also considerable experience (senior developer, IT systems architect, team leader, technical project manager) in several enterprise IT projects, where he worked for leading Greek enterprises (INTRACOM S.A, IBM Hellas S.A, PEGASUS S.A, OTE S.A, TEMAGON S.A). Dr. Soldatos was (in 2000) the technical manager for the software development of the portal http://www.e-go.gr. He is also the co-founder, technical manager and contributor of the AspireRfid Open Source project (http://wiki.aspire.objectweb.org/). His current research interests are in Pervasive, Grid and Autonomic Computing, as well as broadband networking. Dr. Soldatos serves as a reviewer in major journals (e.g., IEEE), as an evaluator for EU projects/proposals and business plans, while he has also served as organizing chair, tutorial chair, and TPC member in numerous conferences.

Prof. Aristodemos Pnevmatikakis, PhD is an associate professor at Athens Information Technology, instructing or co-instructing signal processing and communications courses. He is supervising various theses and independent studies in the area of computer vision and speech processing for smart room applications. His research interests include DSP for pattern recognition and communications, the physical layer of communication systems (with emphasis on RF system level design) and data converters (with emphasis on Sigma-Delta modulators) and their interface to the digital and analogue sections of systems. He is co-author of the book Delta-Sigma Modulators, Modelling, Design and Applications, (Imperial College Press, London, UK, 2003). He received his BSc in Physics from University of Patras, Greece in 1993 and his MSc and PhD from Imperial College, University of London in 1995 and 1999 respectively.

Proposal Part B: Page 160 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.10. LiSSi Laboratory General Information LISSI/SCTIC research Lab is associated to the Institute of Technology and Faculty of Sciences and Technology of Paris 12 University (25000 students and 1800 staff members). LISSI was created to develop methods and algorithms for modelling, analysis and control of networked complex and smart ubiquitous systems. Application fields are large ubiquitous robots and web services, pervasive and distributed enterprise systems, (wired and wireless networks, autonomic and soft computing). Currently, the LISSI Lab counts around 62 members (including 6 professors, 20 Assistant professors, and 6 research assistant). LISSI/SCTIC department has research activities in semantic web based pervasive computing, Multi agent systems, Workflows, Network QoS MAC and QoS routing algorithms in wired and wireless networks. Research activities in software engineering (service based architectures, context-aware agent middleware, Intelligent Agents Platform for dynamic workflow and context-aware applications) are also developed. This research has resulted in several publications in international journals or conference proceedings. LISSI/SCTIC has conducted several R&D projects mainly funded by national and regional R&D programs (ACI Blanche/MATEO, ANR RNRT/RADIC SF, ARITT). The staff continuously collaborates with industrial and academic partners directly in EU labeled projects (Multipol, Sembysem, SEISMIC, MDI project IST, LEONARDO DA VINCI program SICINE project) and indirectly through Phd Programs collaboration with industrial invloved in several projects (IST c@r, Expeshare, etc).

Key People Yacine Amirat was awarded an MsC and PhD in Computer Science from the University of Paris-Orsay (Paris XI), France. After having spent couple of years as an Associate Professor, M Amirat got an HDR and Full Professor position at Paris XII university, where he found the LIIA Laboratory with J-P Ponteneau. In 2009 he become the head of LISSI laboratory in Paris XII University Gian Piero Zarri was awarded an MSc in Electronic Engineering from the University of Bologna, Italy, and then a PhD in Computer Science from the University of Paris-Orsay (Paris XI), France. After having spent the essential of his career at CNRS, the French "National Centre for Scientific Research" as Research director, he is now a member of the LiSSi (Laboratoire Images, Signaux et Systèmes Intelligents) Laboratory of the University Paris12/Paris-Est in a position roughly corresponding to that of an ‘Honorary Professor’. Zarri is known internationally for combining methods from knowledgebased systems and NL processing as well as databases and information retrieval systems. Among other activities, he defined and developed NKRL ("Narrative Knowledge Representation Language"), the knowledge representation language and computer environment used in several EC-funded projects like NOMOS (Esprit P5330), COBALT (LRE P61011) CONCERTO (Esprit P29159), EUFORBIA (IAP P26505), PARMENIDES (IST-2001-39023) and VIRTHUALIS (a Priority-3 NMP project). G.P. Zarri was also the general coordinator and Scientific Responsible for the EUFORBIA project.

Abdelghani CHIBANI has been awarded a PhD in Computer Science from Paris XII University and an MSc in Computer Science from EDITE joint doctoral school between Paris 6 University and SupTelecom Paris School “École Nationale Supérieure des Télécommunications (ENST) ». After 9 years as research engineer and senior consultant in SOA, identity and access management systems at Atos Origin, CityPassenger and BULL/Evidian, he is now an associate Professor “Maître de conferences” at the Paris XII/Paris-Est University. Since 6 years, Abdelghani research interests in Computer Science concern the use of Ontology Knowledge Engineering and Modelling techniques to build a semantic middleware for context aware and secure Ubiquitous computing (ubicomp) systems. Actually, Abdelghani is focusing his research work on semantic management of services and users, in particular tackling to issues related to identity and access management across multi domain ubicomp environments.

Proposal Part B: Page 161 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.11. EVIDIAN General Information Evidian, a subsidiary of Groupe Bull established in July 2000, is a security and service management software company that enables customers to successfully deploy secure e-business and telecommunications strategies.

Evidian has 150 employees, more than 600 customers and 70 partners. The Evidian solutions enable corporations to increase productivity, security and effectiveness of e-business :  Identity and Access Management: Evidian enterprise and Internet innovative security management solutions leverage a comprehensive access control policy for both web and legacy environments, to secure user access across the Internet, Intranets and Extranets. The IAM solution suite includes Identity Management, Provisioning, Role and Policy Management, Enterprise Single Sign-On, Web Access Control, Access Control for SOA’s. With Evidian software, all B2E and B2B users (employees, partners and customers) benefit from universal single sign-on and personalised access to applications. This provides organisations with a single point of administration, enabling customers to streamline the deployment of security policy and consistently enforce it while dramatically decreasing security management costs and increasing user convenience.  Service Management Intelligence: Evidian telecom and application service assurance solutions deliver enhanced business process and service level management capabilities for telecom players and enterprises, with a single-console management view of business applications and their underlying network resources.

In addition, Evidian provides a software solution that provides automatic load balancing, fail-over and file replication for Internet and enterprise applications.

Evidian also provides customers with a full range of complementary product-related support and professional services to help ensure the success of any enterprise security or management project.

Specific services include security and management consulting, implementation, education, and training.

Evidian's outstanding technology has been recognised by numerous awards, including the "Best of the Best" software products by InternetWeek, "Best Security Software Tool" by Computergram, the Yphyse award for "Best Security Single Sign-On Solution", "Hot Product" award from Data Communications and several "Best Access Control Software" awards by SC Magazine.

Key People Thierry WINTER has a high degree in Telecommunication engineering at the French Ecole Nationale Supérieure des Télécommunications in 1990. He started his career within the software department of the Bull Group, by carrying out several development projects for the OpenMaster software suite for network and applications management. In 2000, he took the lead of the security R&D of the Evidian company, with a focus on Identity and Access Management. As part of his duties as Evidian CTO since 2006, he’s driving the Research and Development activities for the different Evidian product lines.

Francis JEANDEL has a high degree in Computer Engineering at the French Institut National des Sciences Appliquées in Lyon in 1973. He started his career within the Bull company, by contributing to the design and development of several communication software products, based on the ISO model. In 1990, he joined the Bull security division for distributed systems, as an architect for security technologies applied to distributed systems, with a focus on Kerberos and DCE. He drove several projects related to GSSAPI and web single sign-on. Since 2000, he’s a senior architect in the Evidian product group, for all security products involving new security technologies, such as Identity Federation, SAML, multi-domain authorization, SOA security, semantics. He’s contributing to several European R&D projects.

Proposal Part B: Page 162 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.12. Kinamik Data Integrity General Information Kinamik Data Integrity is a software company focused on data integrity. Born in late 2005, Kinamik started its activities after recognizing the growing risk of unwanted manipulation of records, and the inexistence of specific solutions for providing data integrity. Kinamik developed a distinctive solution for addressing this incipient market need, and along the way- six different patents have been filled. Kinamikâ&#x20AC;&#x2122;s product and vision has also been awarded several times with prestigious international technology prizes.

Our mission is to provide an easy answer to a tough question: how do I know the digital records I am looking at are correct? . Our objective is to protect existing information environments and to create opportunities for trust-based new businesses.

Requirements for trustworthy sources of information are being driven by regulatory compliance, corporate governance, privacy violations, insider threats and demand for more transparency in virtual environments.

Increased complexity and more varied sources of data create greater vulnerability and a growing potential for unwanted manipulation of data. Transparency can now be offered by an independent solution that can relentlessly watch information as it is being created, used and stored in an immutable and tamper-evident way.

Our solutions should be implemented at any business that require high level of traceability and verifiability of its sensitive information such as public administrations, financial, credit cards, telecommunication, medical, insurance, law-enforcement, surveillance or e-commerce industries as well as any sensitive Information Sharing Environments.

Key People Christophe Primault: Master of Finance degree from the University of Paris IX Dauphine. Christophe has fifteen years of experience in the IT industry where he has held senior international positions in blue-chip companies. He has spent most of his career serving the financial transactions industry where he reached the positions of Vice President of world-wide Marketing and Vice President of Software and Security Solutions for the Financial Division of NCR Corp. More recently he was Managing Director at Fluiditi Ltd a UK based international company specializing in innovative security solutions for the banking and Cash in Transit industries.

Nadeem Bukhari: He is a graduate in Information Technology Security from the University of Westminster, a CISSP and CISM. Nadeem has more than 12 years of exclusive experience within the Information Security Industry 8 of which were spent within the management consulting firms of Ernst and Young and Deloitte. Subsequently he has held a senior position within a software start-up company providing technology direction to penetrate the Information Security Industry and has also provided strategic risk management consultancy to global blue chip organisations including Research in Motion, Bank of Montreal and Fidelity Investments.

Carlos Saona: He holds a PhD in Computer Science from the Technical University of Catalonia. Carlos has more than ten years of experience in software development. He started his career as a researcher in CAD algorithms. He then moved to the healthcare industry, where he spent most of his professional career as software architect in scalable and distributed applications for the CH-Werfen group. He has worked in projects for several markets, including Italy, Spain, France, UK and the USA. Joan Marc GarcĂ­a: He holds a degree as Computer Engineer by the Universitat PolitĂŠcnica de Catalunya (Barcelona), and an MBA at ESADE Business School. Has developed his career in a multinational company specialized in security, monitoring, high availability and data replication.

Worked as support manager, consultant, project manager and presales (local and international markets), through direct channels and business partners.

Proposal Part B: Page 163 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.13. Institute of Communication and Computer Systems/National Technical University of Athens (ICCS/NTUA) General Information The National Technical University of Athens-NTUA (www.ntua.gr) is the oldest and most prestigious technical university in Greece. It was founded in 1837 and has since been contributing to the progress of the engineering science in Greece, through the education of young engineers and its multi-faceted research and development activities. The University comprises nine departments, each one covering a different aspect of the engineering field. The School of Electrical and Computer Engineering of the National Technical University of Athens is well known in Greece and abroad for the research achievements of its faculty members and the good reputation of its students and alumni. The Institute of Communication and Computer Systems-ICCS (www.iccs.ntua.gr) is a research organisation associated with the School of ECE and has about 40 laboratories and research units presently active which are established by the implementation of several structural programmes such as Mediterranean Integrated Programme on Informatics of European Community (MIP-Informatics), Public Investment and Special Development Programmes of the Ministry of Education as well as European Programs as TIDE, AIM, RACE, STRIDE, Telematics, ESPRIT, eTEN, ICT, etc. Our Distributed, Knowledge and Media Systems Group-DKMS (www.grid.ece.ntua.gr), administratively falls under the Telecom Lab of ICCS and its research activities focus mainly on: i) Advanced Distributed Computing, dealing with topics such as Service Oriented Architectures, Cloud Computing and ii) Internet of Things and Knowledge, Media & Digital Art, dealing with topics such as Knowledge Representation and Domain Modelling, Artificial Intelligence and Decision Support Systems.

Key People Prof. Theodora A. Varvarigou: She is received the B. Tech degree from the National Technical University of Athens, Athens, Greece in 1988, the MS degrees in Electrical Engineering (1989) and in Computer Science (1991) from Stanford University, Stanford, California in 1989 and the Ph.D. degree from Stanford University as well in 1991. She worked at AT&T Bell Labs, Holmdel, New Jersey between 1991 and 1995. Between 1995 and 1997 she worked as an Assistant Professor at the Technical University of Crete, Chania, Greece. Since 1997 she was elected as an Assistant Professor while since 2007 she is a Professor at the National Technical University of Athens, and Director of the Postgraduate Course “Engineering Economics Systems”.

Dr. Dimosthenis Kyriazis received the diploma from the Dept. of Electrical and Computer Engineering of the National Technical University of Athens, Athens, Greece in 2001, the MS degree in TechnoEconomic Systems (MBA) co-organized by the Electrical and Computer Engineering Dept - NTUA, Economic Sciences Dept - National Kapodistrian University of Athens, Industrial Management Dept University of Piraeus and his Ph.D. from the Electrical and Computer Engineering Department of the National Technical University of Athens in 2007.

Dr Konstantinos Tserpes: He is a Senior Research Engineer in the Distributed, Knowledge and Media Systems Lab (DKMS) of the Institute of Communication and Computer Systems (ICCS) and the National Technical University of Athens (NTUA). He graduated from the Computer Engineering and Informatics department, University of Patras, Greece in 2003. In 2005 he received his master’s degree in Information Systems Management from National Technical University of Athens (NTUA). In 2008, he acquired his PhD in the area of Service Oriented Architectures with a focus on quality aspects from the school of Electrical and Computer Engineers of ICCS-NTUA. Dr Vassiliki Andronikou: He is received her diploma from the Electrical and Computer Engineering Department of the National Technical University of Athens in 2004. She has worked in the National Bank of Greece and the Organization of Telecommunications of Greece, while since 2004 she has been a research associate and PhD candidate in the Telecommunications Laboratory of the NTUA.

Proposal Part B: Page 164 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.14. FORSCHUNGSZENTRUM INFORMATIK AN DER UNIVERSITÄT KARLSRUHE (FZI) General Information FZI is a non-profit research and technology transfer center comprising 14 R&D teams – each of them directed by a Professor also holding a chair for Computer Science, Electrical or Mechanical Engineering, or Business Administration at the Univer¬si¬ty of Karlsruhe – Germany’s oldest and one of its most successful Technical Univer¬si¬ties. FZI helps its partners and customers in applying novel information technologies for realizing new and better pro¬ducts, ser¬vices, and business processes. FZI is a member of the World Wide Web Con¬sortium (W3C), mem¬ber of the Object Management Group (OMG), member of NESSI, it participates in the IBM Cen¬ter for Advanced Studies (CAS) pro¬gramme, it established together with Microsoft a .NETbased center for Innovative Soft¬ware Concepts, and it won several contracts from the European HPMT Programme to act as a Marie-Curie Training Center.

FZI was founded in 1985, currently employs ca. 110 researchers plus additional student assis¬tants, and had a turnover of ca. 6.3 MEURO in 2005. It has outstanding experience in scientific re¬search and industrial development projects in regional, national and inter¬national co¬operations, as well as in providing technology consulting services, for instance feasibility studies, tech¬nology scouting, market studies, prototype de¬ve¬lop¬ment, etc. Through its multidisciplinary, close-to-theUniversity approach and its close collaboration in manifold networks (with its University sister institutes, several spin-off companies, partners in European Networks of Excellence, etc) it can en¬sure on one hand that newest methods are applied and further developed and the highest level of ICT research excellence can be reached, and on the other hand that research results can widely be spread into the scientific community.

The IPE department: FZI is represented in the IoT4ALL Consortium through its IPE depart¬ment (Information Process Engineering) which encompasses the R&D teams headed by: •

Prof. Studer (knowledge management & semantic technologies),

•

Prof. Stucky (business and process engineering, collaboration processes, VO),

•

Prof. Lockemann (middleware, context management, cross-organizational workflow)

•

Prof. Wein¬hardt (information engineering and management).

Key People Dr. Nenad Stojanovic is project leader in IPE. He received the MSc in computer science from the University of Nis / Serbia and the PhD degree from the University of Karlsruhe (thesis on OntologyBased Information Retrieval). He worked in and had the technical management of several FP5/6 STREPs as well as BMBF projects (national German funding) in the area of applying semantic technologies for knowledge management. In this area, he also participates in industry consulting projects. He published more than 70 technical papers in international journals, conferences, and workshops in the areas of applications of complex event processing and ontologies. He has served as technical coordinator in many research projects. He is currently the coordinator of the EU eParticipation project VIDI. In the IoT4ALL project, Dr Stojanovic will coordinate the work done in FZI. Roland Stuehmer is research scientist in IPE. He received his diploma (MSc) in informatics from the University of Karlsruhe (thesis on complex event processing on the Web). He works in FP7 SYNERGYSTREP as well as an industry collaboration of FZI providing consulting in event processing. In the past, Roland was employed as a student at SAP Research Karlsruhe to test his Event Processing engine in the evaluation of an e-government portal for the EU project FIT. His current research interest are in the field of distributed Complex Event Processing (CEP) for large scale deployments of CEP capability, e.g. on the internet.

Proposal Part B: Page 165 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.15. AUEB-ELTRUN General Information The Athens University of Economics and Business (AUEB) (www.aueb.gr, www.rc.aueb.gr) is an institution which provides education both at the undergraduate and postgraduate level mainly in the fields of Economics, European and International Economics, Business Administration, Marketing, Accounting and Finance, Management, Technology, Informatics, Statistics, Decision Science. AUEB is a distinguished public learning institution which is known for the excellence of its faculty, students and academic programmes. ELTRUN (www.eltrun.aueb.gr) is the E-Business Research Center of the Athens University of Economics and Business. It was founded in 1992 with the objective to establish a European center of excellence in research and development in E-Business. ELTRUN currently consists of more than 20 researchers, including 4 members of the academic staff of Athens University of Economics and Business, while there is close cooperation with academic staff of other Institutions.

Through the years, ELTRUN has successfully managed to produce state-of-the-art research and to complete more than 40 international research projects some of them funded by the Information Society and Technologies Program of the European Commission. The center is also actively involved in national research programs, in various activities that are intended to increase awareness in the fields of E-Business. ELTRUN is organized in four research groups: SCORE (Supply Chain and Demand Management, Collaboration and Electronic Services), IMES (Interactive Marketing & Electronic Services), CUBE (Center of Studies on Business Intelligence and Database), IML (Intelligent Media Lab).

Key People Dr. Katerina Pramatari is Assistant Professor at the Department of Management Science and Technology of the Athens University of Economics and Business (AUEB) and scientific coordinator of the ELTRUN-SCORE research group operated at the ELTRUN Research Center at AUEB. Her research and teaching areas are supply and demand chain collaboration, traceability and RFID, e-procurement, e-business integration and electronic commerce. She holds a PhD from Athens University of Economics & Business (AUEB) and a Masters in Information Systems from the same University. She has worked as a systems analyst for Procter & Gamble European Headquarters for two years, on the development of global Category Management applications, and another year in the Marketing Department of Procter & Gamble Greece.

Dr. Dimitris Papakyriakopoulos holds a B.Sc. in Informatics and M.Sc. in Information Systems from AUEB, and a Ph.D. in Information Systems and Artificial Intelligence also from AUEB. He is senior research officer at the ELTRUN Research Center at AUEB and has extensive research experience, having been involved in various research projects for the last 10 years.

Dr. Aris Theotokis is a post-doctoral researcher at the ELTRUN Research Center at the department of Management Science and Technology of the Athens University of Economics and Business. He has a BSc in Industrial Management and Technology, an MSc in Operational Research from University of Edinburgh and a PhD from AUEB. His research interests are in the areas of consumer acceptance of technology, consumer behaviour in retailing and services marketing.

Cleopatra Bardaki is PhD candidate at the Athens University of Economics and Business (AUEB), Department of Management Science and Technology. She holds a BSc (with honors) in Informatics and Telecommunications from the University of Athens (UoA) and an MSc in Information Systems from AUEB. She has worked as research officer at the Network Operations Center of UoA and as Informatics educator at Computer Learning Centers and at the private Secondary Education. She is awarded a nationally offered Bodossaki Foundation scholarship (2006-07, 2005-06) for her PhD studies. She was also awarded one out of 6 nationally offered PriceWaterhouseCoopers scholarships (2003-04) for her MSc studies (ranked first among 177 candidates).

Proposal Part B: Page 166 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.16. SIGS DATACOM GMBH General Information SIGS DATACOM with several established brands like OOP, OBJEKTspektrum, JavaSPEKTRUM, OMG Information Days, TDWI, etc. is a competent, reliable partner for the IoT4ALL Project.

Our operational business is the organization of user-oriented events (i.e. conferences and Seminars) for practitioners and managers of software-oriented companies and we are publishers of the Software Magazines OBJEKTspektrum, JavaSPEKTRUM. For SIGS DATACOM`s perspective it is important to communicate the business approach within our transfer of professional information to software architects, IT-project managers and advanced programmers/developers.

SIGS DATACOM is an international and independent company for professional education in the sector of information technology. Wir are one of the leading providers of IT-Seminars of professional education and conferences e.g. the OOP in Munich, the SET in Zurich and the TDWI-Conferences in Munich and Amsterdam. Our company is the official partner of TDWI (The Data Warehousing Institute) and also of the OMG (Object Management Group, USA), which is responsible for all its conferences and Information Days in Germany, Switzerland and Austria. We publish also the ITjournals OBJEKTspektrum, JavaSPEKTRUM and BI-SPEKTRUM. SIGS DATACOM was founded through the merger of SIGS Conferences GmbH and the DATACOM Akademie GmbH at the beginning of 2001.

The OOP is one of the biggest and most well respected software events in Europe. This event is very well established, with a remarkable 18 year old history of always being at the cutting edge of software technology. It has a proven track record on satisfying the information needs of attendees from both software and business perspective. The technical content covers the whole spectrum of modern software engineering and provides the essence of the important trends and techniques in this area combined with a strong business focus. The next year (January!) the business focus is especially strong and thus the motto â&#x20AC;&#x17E;Productivity: People, Process, and Technology". The technical focus includes the topics BPM, Requirements and Testing, SOA, Architecture, Open Source, collaborating services Java Agile & Lean, and cloud computing.

SIGS DATACOM was the first company in Europe offering the UML 2.0 certification during OOP 2004.

Richard Soley (OMG) handed out the first certificates UML 2.0 to the participants. In 2010 we do gladly with OMG the OCEB certification during OOP 2010.

Key People GĂźnter FUHRMEISTER: Managing Director of SIGS DATACOM has a working experience of 30 years plus in the area of publishing, conferences and seminars. He has worked for the US publishing companies Addison Wesley and International Thomson Publishing, establishing a number of local publishing operations on in Germany, the Netherlands, France, Spain, Italy and South Africa.

Currently he is actively involved as Senior Project Manager to organize and mange the main European software conference on Software engineering, OOP which will take place for the 19th year in Munich in 2010. Other projects are in the area of IT-journals, related to the magazines Objektspektrum, Javaspektrum and BI-Spektrum.

Viktor PALAND: Co-Managing Director of SIGS DATACOM has a working experience of 20 years plus, primarily in the banking sector. He has been working for 19 years for Deutsche Bank in Frankfurt, Nuernberg and Cologne. In particular he has been responsible regarding the supervision of the operational financial management of approx. 40 middle-sized companies in the area of NortherRhine Westfalia. Within European R&D projects he has been the SIGS DATACOM Senior Project Manager for the project MOMOCOS. Currently he is involved as Senior Project Manager in the major / software conference, Software Engineering Today which takes place in Zurich in May 2010.

Proposal Part B: Page 167 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.17. ESADE General Information ESADE is one of the world's most prestigious academic institutions. Its main richness stems from faculty and staff whose reflection, dialogue, projects and initiatives contribute to excellent training, relevant investigation and research.

Furthermore, these professionals make valuable contributions to public debate and social transformation. The institution's main objective is to train individuals to be highly competent professionals, fully conscious of their social responsibility. To do this, ESADE promotes education and research within its university programs and business school by fomenting a strong commitment to intellectual rigor, critical thinking and academic excellence.

ESADE programs, which cover the entire professional cycle (from recent graduate to experienced professional) concentrate on two major areas: the ESADE Business School and the ESADE University Faculties. The ESADE University Faculties consist of two centers: the ESADE School of Management and the Law School, both of which are affiliated with the Ramon Llull University. The Ramon Llull University (URL) was founded on the 1st of March 1990 and proclaimed by unanimous vote by the Parlament de Catalunya (Catalan Regional Parliament) on the 10th of May 1991. It is a private, non profit-making university providing a public service.

ESADE's international network has always been and continues to be an integral part of the institution. ESADE has agreements and collaborations with over 100 universities and business schools on five continents and is currently the European business school with the most extensive student exchange network in Latin America. The institution is a founding member of the Community of European Management Schools (CEMS), the most prestigious European network on the university level. ESADE was one of the first business schools to obtain the three most recognized awards in the sector: International AACSB, EQUIS y AMBA. ESADE ranks among the top ten business schools in Europe in the most important international MBA, Executive Education and university program polls.

The business management research that ESADE carries out is internationally renowned. ESADE offers doctoral and PhD level courses in Management Studies that rely upon various academicians, institutions and research centers, and groups, who focus on entrepreneurship, innovation, leadership and governance, management, skills and knowledge, business social responsibility, economic law, branding, etc.

Key People Jonathan D. Wareham, Ph.D.: Jonathan Wareham is an Associate Professor of Information Systems at ESADE. His research focuses on the intersection of information technology, economics and strategy. He teaches graduate and executive MBA courses in economics, computer programming and technology architecture, and is a frequent speaker at national and international conferences for both academic and professional audiences on these subjects. Dr. Warehamâ&#x20AC;&#x2122;s research has been published or forthcoming in such journals and proceedings as MIS Quarterly, IEEE Transactions on Engineering Management, IEEE Transactions on Professional Communication, IEEE Computer, Communications of the ACM, etc.

Esteve Almirall: Esteve Almirall holds an MSCIS and MSc in Artificial Intelligence, a DEA in AI (UPC) and a MRes and a DEA in Management Sciences (ESADE). Currently he is working in his Ph.D. in AI and in Business Sciences. Most of his career has been devoted to Information Technologies, especially in consulting, banking and finances where he worked for more than 20 years in executive and board level positions in IS, Organization and Marketing. Moreover, Esteve holds an MBA, a PDD from IESE and a Diploma in Marketing from UC Berkeley. Currently he serves as associated professor at ESADE and UPC (part time) and his interests focus on Open Innovation, Innovation Dynamics and AI tools that could foster innovation in collaborative systems.

Proposal Part B: Page 168 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.2.18. BMT General Information BMT Group Ltd. is an international contract research and technology organisation created in 1985 through the merging of the National Maritime Institute (NMI) and the British Ship Research Association (BSRA). When it was formed, BMT inherited a long and distinguished history of development and transfer to industry for the marine, aeronautical and civil engineering industries. One of BMT's aims has been to continue the work of its predecessors by serving the academic world and commerce within a very wide are of activity that encompasses not only the international maritime and civil engineering communities which its predecessors served but, increasingly, the defence and manufacturing worlds, particularly process industry. BMT's independence of Government and all outside financial interests, enables it to invest the profits it achieves in new facilities and research to ensure the retention and enhancement of its technology lead.

BMT's most important asset is its people. Over 80% of all staff are qualified to at least first degree standard. To ensure all work is relevant, BMT encourages its people to play an active part in the industries they serve and to participate fully in their professional institutes. As a result many members of the staff regularly publish professional papers. BMT's outstanding ability in computer technology and system integration and its extensive network of computer facilities has become a key feature in its development and the reason why BMT today is well-known internationally as an established Software House, registered under AQAP 1 and 13, BS5750 and ISO9000. In addition, BMT has extensive physical facilities, including model water tank testing. BMT is a leading participant in multi-million euro European projects and inaugurates joint industry collaborative projects.

BMT has a long experience of coordinating EU projects. In particular, BMT is coordinating FREIGHTWISE. BMT has also been working in ontologies for a long time, for example in the research projects WISPER and FLAGSHIP. FLAGSHIP also concerns itself extensively with KPIs to assess the benefits of the development.

Key People Rory Doyle B.A., B.A.I., MSc., PhD, CEng is a chartered computer engineer. His primary degrees are in Computer Engineering and Mathematics (Trinity college Dublin), his MSc is in vision control of robotics, (Trinity College Dublin) and his PhD in multi-sensor data fusion for helicopter obstacle avoidance (University of Southampton). He has been employed in Research & Development for over 15 years, starting off with virtual reality work in the early 1990's (Trinity College Dublin), and moving on to intelligent control in the mid 1990's (University of Southampton). Since 1996 he has been employed in BMT managing and providing technical consultancy on major intelligent systems projects.. Rory has been the coordinator of SPAN, SEA-AHED, Safetow and EC-DOCK. Dr. Gary Randall has a PhD in Cognitive Psychology, an MSc (Distinction) in Cognitive Science (both University of Birmingham UK), a BSc (Hons) in Artificial Intelligence. He has a unique blend of IT and theoretical skills relating to Cognitive Science, built up over 15 years, and are an experienced programmer in many languages. Gary is a Senior Research Scientist at BMT and Project Manager of EC projects. His post-doctoral experience as Research Fellow at Harvard Medical School was related to implementing and extending the influential machine vision model Guided Search. Prior to this, Garyâ&#x20AC;&#x2122;s research concentrated on building dynamic neural systems to predict common visual behaviours.

Jenny Gyngell joined BMT in 1999 after a career in the Navy. Since then she has become the Project Manager of a large number of EU-funded research projects. In particular she was the Project Manager of FIRE EXIT. She also managed AVATARS, SAFETOW and the large Integrated Project FREIGHWISE.

Proposal Part B: Page 169 of 203

FP7-ICT-2009-5 26/10/09 v1.0

2.3.

IP proposal IoT4All

Consortium as a whole

The IoT4ALL project has followed a purposeful, multidisciplinary approach in establishing the Consortium.

2.3.1. Consortium composition leading criteria The IoT4All consortium has been established in order to conform to the following criteria: • Adequate level of manageability.

• Balanced consortium between industry, academia and SMEs with organisations able to act as multipliers.

• Trans-national approach.

2.3.1.1. Adequate level of manageability The first criterion is satisfied:  By choosing a Coordinator with comprehensive experience in managing large industrial research projects and by defining a suitable management strategy, as described in section 2.1.  By bringing together partners that know each other and have already collaborated in the past.  By defining three levels of responsibilities for all involved partners: Management, Executive Board, and General Assembly (described in detail in section 2.1).

ATOS ORIGIN has applied its methodology for large project management during its long history as a European leader in system integration, consulting and facilities management. The capacity to steer efficiently from the smallest internet Web page to the whole software system of the Olympic Games is reflected in every single project in which ATOS ORIGIN has been involved. This ability has transformed this company into the European leader and the world key player that it is today. Some examples of large projects coordinated by ATOS ORIGIN are:  EU projects with more than 15 partners => SOA4ALL. ELEGI, TRUSTCOM, ORCHESTRA, PROMINENCE.  The largest EU project in FP6 IST with 97 partners => BEinGRID  Olympic Games, a complex mix of process, people, and technology with huge number of partners and suppliers.

“Information Technology is the hidden power behind the Olympic Games.

Atos Origin is the company that makes the Games work” Philippe Verveer, International Olympic Committee, Technology Director

2.3.1.2.

Balanced consortium The consortium has the right balance of skills and industrial scope, essential to this project; its composition has been carefully designed to enable the smooth handling of three dimensions throughout the project:  Academia and research.  Industrial partners => Large industries acting either as researchers and as end-users  SMEs => Providing another perspective from industry, acting either as researchers or as end-users.

Proposal Part B: Page 170 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

INDUSTRIAL PARTNERS Atos Origin TXT e-Solutions Centro Ricerche FIAT Telit Wireless Solutions Insiel Evidian BMT SME Diakrinisis CAEN Kinamik SIGS-DATACOM

ACADEMIAN/RESEARCH Ingema AIT LISSI NTUA FZI AUEB-ELTRUN ESADE

Figure 2.2 - Skills and scope of the consortium 2.3.1.3.

Trans-nationality

IoT4ALL includes partners from 7 European countries (see map), balanced between partners from North, Middle, Southern and Eastern Europe, a mix that will guarantee an optimal match of the constructed solutions to the different management styles related to the different cultures.

Figure 2.3 - Geographical location of the partners 2.3.1. Partner descriptions and roles This criterion has lead to the composition of a consortium with 16 partners from 9 countries. For each partner we provide some relevant information, while in section 2.2 a detailed description for each organisation including key personnel short CVs are provided.

Proposal Part B: Page 171 of 203

FP7-ICT-2009-5 26/10/09 v1.0

# 1

Partner (short name) ATOS ORIGIN

IP proposal IoT4All

Type (Expertise)56

Partner (full name) Main contributions to the project57

Spain

Industry (IT Service Provider)

Industry (IT Service Provider) Industry (IT Service Provider)

ATOS ORIGIN SAE Project Coordinator (experience managing large projects; including IPs such as BEinGRID, TRUSTCOM, ELEGI, and ORCHESTRA).

Technical expertise in SOA architectures (integration capabilities and ESB solutions) and the dynamic composition of Web services. Extensive customer base for exploitation purposes and tools at the disposal of the project (e.g. the collaborative space Project Portal). ATOS will coordinate the project being responsible for the administrative, financial and day-to-day monitoring of the project as well as taking an active participation in the service Web infrastructure and service construction RTD areas.

ATOS will be one of the technical partners of the Homeland Security case study and will actively participate in the exploitation elements of the project.

Scientifical coordinator of the project.

Country

2

TXT

Italy

3

CRF

Italy

4

DIAKINISIS

Greece

56

CRF is the research centre of the Fiat Group. CRF has a long-standing experience in private and publicfunded projects regarding mobility, transportation, telematics, wireless networks, multimedia and HMI systems. The business line involved in the project has current and synergetic projects in the areas that the project is addressing. Centro Ricerche FIAT will provide the points of view of the end-users (Fiat, IVECO), providing requirements, process models, and data as well as the points of view of the technological experts in the area of electronics and telematics applied.

University

Partners are classified according to the type of organisation (Industry, SME, Academia, Research Centre, Government) and a concrete expertise is also provided for all of them 57 Management For each participant is specified only the main role. In many cases the participants have expertises in other areas this will facilitate the communication with other participant involved in related activities and obviously will allow to contribute partially to the research activities.

Proposal Part B: Page 172 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

5

Partner (short name) INGEMA

6

CAEN

Italy

SME

7

Telit

Israel

8

Insiel

Italy

Industry (IT Service Provider) University

9

AIT

Greece

University

#

Type (Expertise)56

Partner (full name) Main contributions to the project57

Spain

Industry (IT Service Provider)

INGEMA will play the role of user partner taking care of the AAL scenario. INGEMA has a wide expertise in usability and user tests with elderly and disabled people and a huge knowledge in this field form its more than 25 proffesionals coming from the health and social sciences. INGEMA has several facilities (nursing homes, day centers) and also can perform tests in its own lab and on real homes from elderly people.

CAEN RFID is a spin-off of CAEN SpA. The CAEN network has been involved in co-funded european projects since the Third Framework Program. The role of CAEN RFID in the consortium is mainly related to the UHF RFID world. Our prior focuses are in the RFID sensor based tags, integrated readers and antennas. CAEN RFID is actually member of EPC Global consortium and LPRA (Low Power Radio Association) and can play an important role in the standardization support.

WP leader

Country

Proposal Part B: Page 173 of 203

WP leader The role of AIT in IOT4ALL will be two-fold. First, it will act as a main IoT middleware developer for the project based on its expertise on RFID middleware in general and more specifically its leading role in the Open Source Project AspireRfid (http://wiki.aspire.objectweb.org/)).

AIT will establish and provide the required liaison with the AspireRfid OSS platform. In the scope of IOT4ALL, AIT will use RFID middleware as a baseline in order to develop middleware libraries for addressing, discovery, filtering and business eventing for the broader range of IoT applications. AITâ&#x20AC;&#x2122;s second responsibility in the project, will be the development, integration and validation of a novel added-value realistic AAL application in the scope of INGEMA lab (Matia hospital, San Sebastian Spain).

AIT has been a main technical contributor in setting up the smart lab at the Matia hospital and will contribute its experience in developing/integrating AAL applications in sensor-saturated environments comprising multiple things. Note that AIT will be also the primary integrator of visual and acoustic sensors (A/V) in the envisaged IoT systems of the project.

FP7-ICT-2009-5 26/10/09 v1.0

10

Partner (short name) LISSI

11

Evidian

#

12

Kinamik

IP proposal IoT4All

Country

Type (Expertise)56

Partner (full name) Main contributions to the project57

France

University

Use case leader.

France

SME

Evidian is leading or is participating to several running European R&D projects. In IoT4All, Evidian will leverage the outcomes from ITEA SODA and ITEA2 MULTIPOL, by adapting the authorization server from SODA and the authorization chain from MULTIPOL, as a basis for the IoT4All innovative mechanisms dedicated to control the access to resources and to information, as well as the intelligent management of security events and security information.

Spain

Proposal Part B: Page 174 of 203

SME

In addition to other actions made by IoT4All partners, Evidian will disseminate the IoT4All activities and results though US and European analysts briefings, such as Gartner, Burton Group, Kuppinger Cole, which are organized periodically during the year, and through analyst conferences where Evidian is present as an exhibitor or a speaker, such as Gartner IAM Summit, Burton Group Catalyst.

These services that will be implemented, will require to log certain activity, and to convert into trustworthy all the information that is sensitive enough to assure that it has integrity. To assure that it really is the data that is meant to be. The key aspect in this case is to accomplish this in a flexible, scalable and technology agnostic way to provide it in the data level: act at an event level, in real time, and linking data between it, so chronology also forms part of the process. Kinamik relies in his collaborations with a set of organizations and profiles for this purpose: auditors, forensics, legal entities, private customers, universities and technology centers, government agencies, security experts and different associations, such as the Cloud Security Alliance.

FP7-ICT-2009-5 26/10/09 v1.0

13

Partner (short name) ICCS/NTUA

14

FZI

#

IP proposal IoT4All

Country

Type (Expertise)56

Partner (full name) Main contributions to the project57

Greece

University

ICCS comprises a research organisation with great experience in Service Oriented Architectures, data management in distributed systems, QoS provision, resource and execution management through SLAs and dynamic workflow management among others.

Within IoT4All, ICCS will undertake the Activity 4 management related to the Digital/Virtual World IoT Service Platforms and will also lead WP4.2 on Service and Cloud Platforms and consequently provide valuable support within the integration efforts. Based on their expertise in semantic reasoning, event correlation and service front-ends, ICCS will participate in all Activity 4 tasks. They will also actively participate in the research and development efforts for the semi-permeable osmotic *-wares and the trust and security tasks, offering their great expertise in middleware development and interoperability issues as well as in SLA management and trust establishment respectively. Given their experience in SOA and SOI design, they will provide valuable input during the IoT4All architecture design. ICCS will disseminate IoT4All innovative research and results through the submission of related papers to international journals and the presentation of the IoT4All findings to international conferences and workshops among others.

German y

University

IPE department which represents FZI participation is active in EP-TS, the Event Processing Technical Society, to create standards and promote and advance Event Processing from a research and a user-centric perspective.

IPE participates in several European projects â&#x20AC;&#x201C; the most relevant for the work on IoT4ALL are from three areas: Semantic & Knowledge Management (FP6 FIT-STREP, FP6 TEAM-STREP, FP6 FUSIONSTREP, FP6 SAKE-STREP, FP7 SYNERGY-STREP, FP6 SOPRANO-IP, FP7 MATURE-IP), Collective Intelligence (FP6 Nepomuk-IP).

Proposal Part B: Page 175 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

15

Partner (short name) AUEB

16

SIGS

German y

17

Esade

Spain

18

BMT

United Kingdom

#

Country

Type (Expertise)56

Partner (full name) Main contributions to the project57

Greece

University

Industry (IT Service Provider) Industry (IT Service Provider) Industry (IT Service Provider)

Role and tasks in IoT4ALL: AUEB will contribute its expertise in the elicitation of the system requirements, the design and pilot test of the “Sustainable Logistics” case and innovative supplychain applications. AUEB will also lead the WP regarding “Real World Management & Governance”. AUEB will further contribute through its experience in the socio-economic impact assessment of the project’s results as well as in the design of the IoT4ALL services based on the principles of the Service-Science discipline. Finally AUEB will disseminate the project results through journal publications and presentations in international academic and industrial Conferences.

Dissemination Leader.

In charge of the Business Models WP 3.5.

Use case leader.

Table 2.3 – Roles of the partners

2.3.2. Subcontracting i. Subcontracting to CRF (50.000 Euros) CRF is planning to subcontract a part of the integration and adaptation of technology developed in the research clusters into the Blue&Me platform and modifications to the platform itself. The subcontractors will be selected taking into account the application specific requirements and previous expertise. They include Actia and Magneti-Marelli. Magneti-Marelli is the developer and system integrator of the telematics platform (Blue&Me) and its future evolutions. Actia is the supplier for the FIAT Group diagnostics platform. The resources estimated for this task amount to 50k€.

3) Certificates on financial statements (84.100 Euros) All partners have been assigned subcontracting budget in the Management category to subcontract the certification of their financial statements.

The budget has been calculated according to the new rule introduced in FP7 about the need of a certificate only when there has been an accumulated funding claim of 375.000 Euros, and the costs of these certificates:  Two average costs of these certificates depending on the partners (number of certificates budgeted indicated per each partner): - 4000 Euros per certificate: Atos Origin (1), CRF (2), CAEN (1), Evidian (2) - 2000 Euros per certificate: Atos Origin (1), TXT (1), CAEN (1), Evidian (1), FZI (1), ESADE (3),

Proposal Part B: Page 176 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.3.3. Other counties Not applicable in IoT4All. 2.4. Resources to be committed The total budget of IoT4All project is 14.368.468,11 €. Of this amount, the requested EC contribution is 9.515.023,87 € (66,22%). The overall costs are elaborated below.

2.4.1. Allocation over project activities The allocation of the project resources per activities is provided below. The budget pending to be allocated in the competitive call has been categorised as RTD activity.

Activity

Effort (person x month)

RTD

%

1344,0

88,77%

Management

81,0

5,35%

Other Activities

89,0

5,88%

1514,0

100,00%

Total

Table 2.4 Effort distribution (per type of activity)

Project Activity

Effort (person x month)

A0 Management A1 IoT Architecture & Middlewares A2 Real World IoT Technologies & Systems A3 Business/Social World Novel IOT-based Applications A4 Digital/Virtual World IoT Service Platforms A5 Prototypes, Pilots & Test Cases A6 Impact Creation Total

%

81,0

5,4%

287,0

19,0%

242,0

16,0%

189,0

12,5%

164,0

10,8%

308,0

20,3%

243,0

16,1%

1.514,0

100,0%

Table 2.5 – Effort distribution (per project activity)

Activity

Budget (Keuro)

RTD

%

Funding (Keuro)

%

12.844.193,26

89,39%

7.990.749,02

83,98%

Management

708.570,92

4,93%

708.570,92

7,45%

Other Activities

815.703,93

5,68%

815.703,93

8,57%

14.368.468,11

100,00%

9.515.023,87

100.00

Total

Table 2.6 – Budget and funding distribution (per type of activity)

Proposal Part B: Page 177 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

2.4.2. Allocation over cost categories The project’s administrative allocation of resources is shown below.

Cost Category

Budget (Keuro)

%

Personel

8.710.472,96

60,62%

Overhead on personel

4.633.435,15

32,25%

110.500,00

0,77%

84.000,00

0,58%

147.000,00 420.000,00

1,02% 2,92%

Subcontracts

50.000,00

0,35%

Other costs

20.000,00

0,14%

193.060,00

1,34%

14.368.468,11

100.00

Consumables Audit Certificates Equipment Travels

Overhead on non personel expenses Total

Table 2.7 – Budget distribution (per cost category)

The major cost item in the project resources is the personnel costs. All partners have committed appropriate personnel resources from existing staff as well as additional staff to be recruited to undertake the project. Travel and subsistence costs are included by all partners to ensure that the project results are effectively disseminated in major international forums to have maximal impact.

The travel and subsistence costs will also facilitate travel to project meetings and workshops as well as meetings with the EC and standardisation bodies. We will attempt to minimise travel by making use of innovative online communication tools as well as telephone conferences. However, physical plenary meetings will take place at regular intervals to monitor the progress of the project and workpackage teams will meet physically in working meetings to undertake technical work as appropriate.

2.4.2.1. Consumables Consumable costs (110.500,00 €) which is going to be spread in different aspects to guarantee the proper performance and an efficient development along the project. In such terms consumables are going to be represented by:  Marketing material including project flyers, brochures, posters, mailings, and other consumables required for dissemination purposes  Supplying the pilot phases with RFID readers, tags and antennas for the implementation.  Any other logistics resources such as software licenses, for books and page charges, printing, toner and telephone, etc

2.4.2.2. Equipment Equipment costs amount of 147.000,00 € is being spread in the following resources:  Servers to : o Host the website project o Host the webcasts of the tutorials for training o Host public demonstrators for IoT4ALL o Deploy the service web architecture

Proposal Part B: Page 178 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

 Laptops and workstations for partners’ teams.  Additional hardware which compose the infrastructure of proposed solution (networks resources, additional devices, etc.)

2.4.2.3. Travel Travel costs in the project are 420,000 €. They have been based on the basis of a specific number of travels per partner and a base cost of 1,000 Euros per travel:  Executive Board: 12 travels per year (42 travels in the project) → 48,000 €  Other partners: 8 travels per year (28 travels in the project) → 32,000€ 2.4.2.4. Other costs  CAEN: to buy some parts or components to be necessary in developing some prototypes during the RTD phase.  EVIDIAN: to cover expenses that may arise for supporting the pilot such as transfer of infrastructure, expenses for RFID tags and/or sensors, demonstration expenses etc.  Diakrinisis: to cover expenses that may arise for supporting the pilot such as transfer of infrastructure, expenses for RFID tags and/or sensors, demonstration expenses etc.

2.4.2.5. Subcontracting Subcontracting issues are described in section 2.3.2.

2.4.2.6. Allocation per countries The IoT4ALL consortium is well balanced according to budget and funding distribution between countries.

Country

Budget

%

Funding

Spain

3.039.842,96

21,16%

2.195.996,32

23,08%

Greece

2.479.681,60

17,26%

1.867.940,80

19,63%

Italy

3.813.708,54

26,54%

2.202.345,50

23,15%

France

2.349.152,00

16,35%

1.437.028,00

15,10%

Germany

1.390.183,00

9,68%

1.142.863,25

12,01%

UK

573.400,00

3,99%

307.600,00

3,23%

Israel

722.500,00

5,03%

361.250,00

3,80%

14.368.468,11

100,00%

9.515.023,87

100,00%

TOTAL

Table 2.8 – Budget distribution (per country)

Proposal Part B: Page 179 of 203

%

FP7-ICT-2009-5 26/10/09 v1.0

Proposal Part B: Page 180 of 203

IP proposal IoT4All

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Section 3: Impact 3.1Expected impact The European Commission has already recognised the economic, commercial and social potential of the Internet of Things. In a Commission Staff Working Document entitled Early Challenges regarding the “Internet of Things”, which accompanied a Communication on Future networks and the internet, a vision of the future Internet is presented where connecting physical things, from banknotes to bicycles, through a network will let them take an active part in the Internet, exchanging information about themselves and their surroundings. This will give immediate access to information about the physical world and the objects in it – leading to innovative services and gains in efficiency and productivity. The productivity and efficiency improvements rendered possible by this Internet of Things and the services it will convey will definitely contribute to improvements in European living standards. So citizens and society will benefit.

The document notes that the next jump in the growth of the Internet will come from seamlessly integrating physical things into information networks, and the overall infrastructure that will support this networking of physical objects can be termed the Internet of Things.

Moreover, developments in several technologies, for example identification technologies like RFID, wireless sensor technologies, robotics and wearable computing, nanotechnology and energy scavenging technologies, are bringing closer the realisation of the Internet of Things.

As a result of this convergence, the working document predicts that new opportunities will be created and new needs will be met, bringing about potentially disruptive business models, and new societal services that will improve the quality of life. The Internet – or the future network into which it will one day evolve – will have to deal with an increase in traffic as today's off-line objects are brought online to make industrial processes more efficient with higher degrees of productivity.

More generally, as the technologies needed for the Internet of Things become available, a wide range of applications will be developed. These can support policy in areas including transportation, environment, energy efficiency and health. Huge benefits will come not only from faster productivity growth, but also in many other ways: increasing efficiency in material handling and general logistics, efficiency in warehousing, product tracking, efficiency in data management, reducing production and handling costs, speeding the flow of assets, anti-theft and quicker recovery of stolen items, addressing counterfeiting, reducing mistakes in manufacture, immediate recall of defective products, more efficient recycling and waste management, achieving CO² reductions, energy efficiency, improved security of prescription medicine, and improved food safety and quality.

In fact, the commercial potential of the Internet of Things was recognised as long ago as 2005, by (among others) the International Telecommunications Union, in a report which was produced by the ITU Strategy and Policy Unit (SPU) for the World Summit on the Information Society held in Tunis, 1618 November 2005 (ITU Internet Report: The Internet of Things, International Telecommunication Union (ITU), Geneva, 2005). This gave an in-depth introduction to the Internet of Things and its effect on businesses and individuals around the world.

This report noted that “The technologies of the Internet of Things offer immense potential to consumers, manufacturers and firms. However, for these ground-breaking innovations to grow from idea to specific product or application for the mass market, a difficult process of commercialization is required, involving a wide array of players including standard development organizations, national research centres, service providers, network operators, and lead users”. However, to date, it cannot be said that this potential has been realised, and for that reason the European Commission has recognised what it describes as the “research challenge” related to the 'Internet of Things' (IoT).

Proposal Part B: Page 181 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Specifically, in Objective ICT-2009.1.3, of the Seventh Framework Programme, which covers the Internet of Things and Enterprise environments, it is seeking to promote development of Architectures and technologies using open protocols, which enable novel Internet-based applications including – but not restricted to – business/enterprise scenarios, as well as Architectural models enabling an open governance scheme of the Internet of Things.

A particular feature of the approach proposed by IoT4All is its recognition that the IoT is a perspective of the Future Internet (FI) and not an integrated part of it. Consequently, IoT4All believes that it does not make any sense to develop a specific IoT network infrastructure, nor a specific IoT federation of service platforms, nor a specific IoT Smart Space for users interaction, nor a specific IoT Contents & Knowledge Management System. Instead, it proposes collaboration with other research communities, including European Technology Platforms etc, to provide requirements for their research challenges, to verify & validate their outcomes in FI IoT scenarios; it also aims to develop in IoT research just those specific technologies, protocols, tools which are not foreseen in the research agendas of the other FI communities, but which are essential for the development of IoT in Europe.

In so doing, it will help to offset the tendency (otherwise a potential risk) for a de facto monopoly to arise from a centralised architecture. As the Commission document cited above warned, it is necessary to avoid architectural approaches that: • Favour a de facto monopolistic operation of one single system world-wide; • Lead to a multiplicity of incompatible systems, with 'RFID islands' developing, probably structured across economic/application sectors; • Lead to closed proprietary standards with high IPR access costs., Despite the lack of progress to date, commercial interest in the Internet of Things remains strong, and the concept was included by ReadWriteWeb as one of the 5 biggest Web trends of 2009, and it was reported that in 2009, this trend has ramped up and is adding a significant amount of new data to the Web. For example, IBM announced a deal at the end of June with Danish transportation company Container Centralen. By February 2010, Container Centralen has undertaken to use IBM sensor technology "to allow participants in the horticultural supply chain to track the progress of shipments as they move from growers to wholesalers and retailers across 40 countries in Europe."

Specifically this refers to transportation of things like flowers and pot plants, which are very sensitive to the environment they travel in. Having sensors as part of the entire travel chain will allow participants to monitor conditions and climate during travel. Essentially it makes the travel process very transparent.

As well as the new types of functionalities it will enable, such as health monitoring by Internet fridges, the sheer amount of new data about an object should lead to better quality goods and better decision-making by consumers For this reason, IoT4All therefore has a clear focus on the commercial potential of the Internet of Things. Although IoT4All has attempted to present its own definition of the term "Internet of Things", it also embraces the accepted view that this term has come to describe a number of technologies and research disciplines that enable the Internet to reach out into the real world of physical objects.

Technologies like RFID, short-range wireless communications, real-time localization and sensor networks are now becoming increasingly common, bringing the Internet of Things into commercial use. The significance of this is the close interlinking between the physical world and cyberspace - a development that is not only relevant to researchers, but to corporations and individuals alike.

The following table explicitly lays out a series of results that IOT4ALL will deliver to contribute to the expected impact of this objective.

Proposal Part B: Page 182 of 203

FP7-ICT-2009-5 26/10/09 v1.0

ICT-2009-1.3 expected impact

IP proposal IoT4All

IOT4ALL will deliver

Strengthened competitiveness of European 1. The IoT4All Consortium is exclusively formed businesses…

by Europe-centric organizations. Some of them have also an important International dimension to guarantee that research outcomes could be disseminated also outside Europe. Both IoT4All coordinators are industrial business companies, that guarantees a special attention to business competitiveness and exploitation of results …in all sectors of the economy…

2. It is one of the major aspects of our proposal to focus on how IoT is impacting the several sectors of European socio-economical life.

We focus on two industrial sectors (automotive and logistics) but we also have one test case in e-inclusion and one test case in homeland security. The generalization and transfer of IoT4All results to other sectors is guaranteed by the variety of the application domains in which Iot4All partners are involved in business.

… through more automated processes,…

3. This is of course in the main focus of the Logistics test case. However, Iot4All focus is not just on time-cost-optimizations and automation of business processes, but above all on improving IoT impact into the European society as a whole.

… new classes of applications, …

4. New IoT-based applications will be designed and developed in our Activity A3. The selfrepairing car, the environmentally friendly logistics, the socially friendly elderly assistance and the realtime environmental protection and homeland security are just some examples of these.

… and more generic and open architectures,…

5. This is the real core of IoT4All impact: an IoT architecture linking the Real, the Digital and the Socio-economic Worlds according to generic and open standards. In our project we will re-use as far as possible architectures, protocols, technologies which are already in use in other FI research streams, like the Network of the Future or the Internet of Services. Our IoT architecture is not IoTspecific but could be applied to the whole FI pillars.

… and through the support to standards …

6. WP6.2. will ensure the alignment within the standardisation bodies like ETSI.

Proposal Part B: Page 183 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

…as well as dynamic and composite business 7. Our WP3.5 is fully devoted to study IoTmodels… oriented new business models. These will be dynamic and composite, in the sense that according to the specific case, we could compose, as in service orchestrations, different BM blocks to form a final composite one. E.g. we could mash-up the social networks business models with SaaS, both interpreted in the IoT sense for the delivery of customisable high added 8. IoT4All will develop innovative IoT-based value products or services services with great impact on European socio-economics.

European leadership in the integrated business solutions…

supply

of 9. IoT4All is not just formally Europe-centric. All its organizations, although some of them present worldwide, are born in EU and see the application of EU-funded research outcomes in EU.

… exploiting the fast development of RFIDs 10.IoT4All will follow with attention the RFID and and smart tags… smart tags developments in collaboration with the other initiatives which are focussing on them, like the ICT PSP Thematic Network on RFID or the GRIFS and CASAGRAS FP7 projects … and taking advantage of fusion between the 11.IoT4All is not considering a fusion between real world and the virtual web-based world.

Real and Digital Worlds, but an osmotic semipermeable membrane between them which allows selectively, but under controlled rules and laws, some particles to be transferred from one world to the adjacent one. Virtual Worlds in the sense of Second Life are instead not in the focus of IoT4All. The IoT4All project will deliver this impact through the release of several major result groupings: New classes of applications of the Internet of Things; a generic and open architecture; new business models; use cases in specific economic sectors with subsequent generic result release and dissemination in a broader spectrum of sectors. Furthermore, successful completion of the project accompanied by long term and sustainable exploitation of results will result in strengthened competiveness in Europe through discovered knowledge and developed skills within the partners and communicated to industry and this will lead to European leadership in this growing field.

3.1.1 New classes of applications of the Internet of Things The application software industry, once very project- and vendor-centric, has been evolving rapidly under the impact of three main driving forces: commoditization of basic functionality, software as a service (SaaS) delivery models and, most recently, availability of service components for userdesigned applications.

The impact of these trends is already visible on the market, where large Independent Software Vendors (ISVs) are withdrawing from direct delivery and customized projects, to focus more on standardized solutions, especially in the lower, broadest portion of the market (e.g., SMEs). In the

Proposal Part B: Page 184 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

same arena, they have started to feel the competition of SaaS providers who, for customers to whom standard functionality is good enough, propose the additional values of null installation and maintenance costs.

The traditional delivery model still seems to resist in the area of specialized applications, e.g. highend ERP implementations, supply chain or vertical systems like traffic management or healthcare.

However, this is the area where the third, most recent trend is going to have an impact. When truly reliable service components become available along with the means to combine them into complex applications, small vendors or even the users themselves will be given the means to deliver and customize sophisticated vertical functionality. Many small software houses have already exploited mapping services from Google or eCommerce services from Amazon to deliver custom applications that, only few years ago, demanded ISV involvement in million-euro projects.

It is our opinion that the IoT will further accelerate these trends, and will make it possible for the market to evolve towards entirely new application classes as well as new delivery and customization models. In particular, the following impacts are expected on the applications market ecosystem (see Table below): -

IoT will make things an active part in the process of delivering and customizing software applications. Producers will deliver application functionality along with their products, as services associated to intelligent “things”. For example, customer support or maintenance functionality will be provided as a service directly by the product itself (e.g., an appliance or a piece of machinery).

-

Service platforms centered on things will appear, providing as publicly available SaaS functionality that was once realized through vertical implementations. For example, track&trace functionality will cease to be a “software project” for each different organization; as cargo will be incorporated into the IoT, track&trace and other logistic functions will be easy to standardize and offer as public services58.

-

Thing-centred services and dedicated public platforms will reduce the need to design specialized functionality from scratch. The process will be rather one of assembling the right combination of services in relation to the things to be managed. For example, an healthcare management system will combine services from medical equipment, prostheses and pharmaceutical products, intelligent patient records and so on. This process will involve ever more the final users and specific functionality providers, and will involve ever less the system integrators and vendors of packaged solutions.

-

As a final step, individual users themselves will be able to deliver their own personalized functionality, by composing services from things they own in the frame of public authoring platforms where users and things can publish and share their services.

58

See for example the DG Infso ICT for Transport project EURIDICE, and the related ORPHEUS service platform: “EURIDICE Project White Paper”, www.euridice-project.eu.

Proposal Part B: Page 185 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

-

< 2000

2010

IoT age

Standard ISV product + delivery and ISV package Previous specialized functionality customization project. or Software-as-a-Service functionalities (thingsor Open source package facing ones) will become standard, boosting the SaaS market.

Specialized Ad hoc development, Specialized vendor + Specialized vendors will or sectorial either in-house or from delivery and customization become SaaS providers of functionality System Integrator. project by System thing-related services.

Integrator.

End-users will gradually replace System Integrators.

User custom Ad hoc development. functionality

Ad hoc development (may Users able to combine and involve publicly available publish new services web services). through public platforms.

Thing -functionality

--

Things will become providers and consumers of services.

To achieve this impact, it is important that IoT platforms are specified not in isolation but, as IoT4All proposes, in a coordinated effort with the other initiatives aiming at the Future Internet, like the Internet of Services and Cloud Computing. For this reason, since the early stages of the project we will establish links with the other active projects pursuing a similar vision of the future applications market. The cooperation will be both on the technical side, to ensure that parallel developments in different areas will not lead to incompatible platforms, and on the impact creation side, to achieve higher visibility and convey a common message to end users and market operators.

Exploitation planning will have to ensure that, after the completion of the project, the software vendors in the IoT4All consortium will invest appropriate resources and marketing efforts to bring forward the changes highlighted in the above Table. To this purpose, the industrial partners will exploit the connections and partnerships they have with leading ICT companies at the international level.

3.1.2 A generic and open architecture Introduction-Overview IOT4ALL will introduce a generic and open architecture of IoT applications, which will cover the business, social and technology dimensions of the IoT revolution. At the technical/technological level the IOT4ALL architecture will boost modularity, extensibility and technological longevity. Note that this is particularly important given the magnitude of technologies that comprise the IoT infrastructures and applications. These technologies span many areas including communication, energy, intelligence, integration, interoperability and more. While IOT4ALL will develop a wide range of IoT technologies it can not (due to budget, resource and timing constraints) cover the full range of technological developments that underpin IoT. To overcome this limitation, IOT4ALL will provide an

Proposal Part B: Page 186 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

open and generic architecture specifying the structuring principles of IoT applications, beyond the specific technologies to be developed in the project. This open and generic architecture will serve as a vehicle for the gradual evolution of IoT. Indeed, we expect it to act as a breadboard for new technological components to be developed in the project.

Impact to technological developer and business communities Along with above lines, the impact of the IOT4ALL open and generic architecture, will boost the project’s impacts on both the business and technical development communities. On the one hand, technical developers will be offered with a backbone infrastructure enabling them the direct exploitation and use of their developments (e.g., new hardware devices, new middleware components) within wider IoT applications and deployments. On the other hand, the IOT4ALL open architecture could generate new business opportunities and revenue streams for various stakeholders within the IoT value-chain. Specifically: 

Application developers and integrators will be offered with a set of standardized principles and building blocks for integrating sophisticated IoT systems and applications. In this respect the IOT4ALL architecture will act an architectural blueprint for deploying non-trivial applications.



Independent Software Vendors (ISVs) will have the opportunity to develop new added-value application modules and/or middleware components, with a view to augmenting the capabilities of the IOT4ALL platform. ISVs will then have opportunities to sell licenses of these components.

The availability of an open and generic architecture will certainly boost such exploitation activities, through providing a clear and well define way for integrating new modules into IoT applications.



Hardware vendors (e.g., RFID reader vendors, sensor manufacturers, device/gateway vendors) will be offered with a standardized architecture for using their products within IoT applications.

Hence, they will have the opportunity to optimize their products for IoT applications, through making them compatible and interoperable with the IOT4ALL architecture.



Business consultants, will be provided with an architectural environment that hides the underlying technological peculiarities, and in this way they will be able to concentrate on the definition and planning of new IoT based revenue generating services.



Academic institutes and universities will be offered with a standardized architectural model for IoT applications, which will facilitate the task of disseminating, teaching and training based on IoT. In this respect the IOT4ALL open and generic architecture will act as a reference model (similar to what the ISO networking layers are for the networking world).

Assumptions and external factors Based on the above opportunities for both the business and developer communities, IOT4ALL has the potential to make significant impact at both the economic, social and technological levels (fully inline with the project’s objectives). However, there are always external factors and/or contingencies that could limit this potential or minimize the impact. These relate to: 

The general adoption of the IoT paradigm by the enterprise world. The IoT concept, though fantastic is associated with increased complexity and sometimes high costs (for specific business scenarios). The future of IoT will heavily depend on the engagement of the business community and associated private investments. If these investments will not be high the corresponding impact could be limited.



The emergence of competing IoT architectures, which will fragment the efforts towards a globally accepted architectural blueprint.

Proposal Part B: Page 187 of 203

FP7-ICT-2009-5 26/10/09 v1.0

ď&#x201A;ˇ

IP proposal IoT4All

The parallel evolution of royalty free standards and open source solutions, which could boost wide adoption of the IOT4ALL open and generic architecture. The wide adoption based on open source and royalty free standards will have to combat the emergence of proprietary architectures by giant vendors like Oracle and SAP.

3.1.3 New business models Business Impact â&#x20AC;&#x201C; Implications for the Business Community We can summarize the impact of business modelling activities the IoT4ALL proposal on the basis of three distinctive contributions: 1) Understanding the contribution of the Internet of Things in the context of current Business Models.

The contribution of the Internet of Things in current Business Models is realized in two main directions: a) its capacity of lowering transaction costs and b) the increase in precision.

However, we lack frameworks that allow us a clear identification, quantification and analysis of these contributions in actual sectors and companies.

This is therefore the first step that the BM workpackage will cover.

2) Understanding the Opportunities that the Internet of Things offers in terms of Business Models.

The Internet of Things offers a broad range of opportunities for evolving and creating new business models building on the same principles as the ones created in the Internet but on the real world.

However, these opportunities will face barriers and difficulties to be pursued if they are not well understood and their potential impact quantified.

3) Offering concrete propositions for new Business Models.

Although general opportunities add some clarification allowing the evaluation of its potential impact, they lack the power of concrete proposals that can be validated in real world environments.

IoT4ALL, aims for building a set of concrete, exemplary proposals for business models and validate the in real world environments. The results of this work could have a clear impact in the sectors addressed, in terms of concrete results and validation exercises that could serve as reference cases.

Technical Impact â&#x20AC;&#x201C; Implications for the Technical Community Technical exploration in companies is driven in many occasions by the likelihood of transforming science & technologies into innovations that add to the bottom line. This is a process where uncertainty plays a major role and often prevents it. A better understanding of the potential impact of technology in the business can clarify directions and clear the path for further investments.

IoT4All aims to contribute to that direction again at three different levels.

1) Understanding the contribution of the Internet of Things in the context of current Business Models.

Proposal Part B: Page 188 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Having frameworks that could allow to assess the potential contribution of IoT to actual business models could clear the path for technological investments and developments geared to either new products or services or to endow actual products and services with these capabilities.

2) Understanding the Opportunities that the Internet of Things offers in terms of Business Models.

Understanding the opportunities could help in taking decisions around which technical possibilities to pursue, how much to invest in them and what needs to be accomplished to have valid solutions.

3) Offering concrete propositions for new Business Models.

Concrete propositions could draw ideas and proposals into the territory of realities, providing a glimpse of what the actual difficulties, costs and acceptance could be, allowing to take better informed decisions on technological investments.

Steps for delivering the Impact - Milestones Milestone

Business Implications

Technical Implications

Contribution of IoT to actual Business Models

- Better understanding of contributions.

- Better informed investments in R&D

- Clear directions.

- Clear investments.

- Business framework for Technical proposals.

Opportunities for New Business Models

- Possible lines of action.

- Informing strategic partnerships.

- Informing long and medium term R&D investments.

Proposals for New Business Models

- Examples for formulating business proposals.

- Actual business proposals.

- Partnerships and strategy.

Concrete Proposals Explored

- Lessons learned.

- Business cases.

- Market potential.

- Clear lines of investments.

- Clear lines of research.

- Driving absorptive capacity and outside exploration for ideas and technologies.

- Real world testing of technologies.

- Difficulties in adoption and scalability.

- Unmet needs.

- Assessing social fit.

- Assessing BM fit.

- Real world difficulties exemplified.

Risk Analysis Risk can be assessed in two directions. First, quantifying the potential exactitude of the hypothesis and predictions. And secondly, taking into account the associated uncertainty.

Proposal Part B: Page 189 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

In this case only when we try to understand the impact of IoT in actual Business Models, we have enough data and cases where to draw on. On the other phases the project is situated in more exploratory areas with high uncertainty.

Therefore this first phase is the only one where we can attempt to quantify risk, while in the others we have to assume a exploratory exercise characterized with a high level of uncertainty.

3.1.4 Use cases in specific economic sectors The impact on the European society of the IoT4All architectural choices will be evident in the four planned application cases related to “safer cars”, “sustainable logistics”, “assistive inclusion” and “environmental risk management” and a preliminary estimation of such an impact is already depicted in section 1.1. Moreover, the results from these four scenarios should also be applicable to other domains and sectors, such as the key working areas of our industrial partners and the foremost concerns of our research institutes (i.e. manufacturing, retail, healthcare, transportation, energy management, etc.).

As well as the socio-economic and environmental impact that will be seen in the four scenarios the framework will have an additional impact in the whole field of ICT. The feedback and dissemination activities that will be undertaken in the pursuit of this framework will have a major effect on the development of standards within the industry. It should also lead to further investment in key technologies.

Another major area of impact for this project is in distributed intelligence. It is anticipated that the project will have a major influence in some important research areas in the ICT industry: the areas of agent technologies and distributed service platforms. These efforts could have an important impact over the whole European area.

IoT4ALL will also have an impact on the field of ambient intelligence, an import aim in the ICT industry over the next ten years or so. The project will make it possible for devices to be aware of the network and user requirements in context and react accordingly. Europe is also aiming to become a leader in the development and standardisation of this technology.

Another major impact is the event driven nature of the applications. Much research has already been done in this field and industry is beginning to take tentative steps in the technology, but IoT4ALL will be able to extend this research significantly and make it an essential for every process. The conceptual model of events and conditions will ultimately provide knowledge to all companies about how to manage such a system and react to such a situation. The final result will be able to reason through a problem providing customers with an application worthy of the future internet.

To focus specifically on the scenarios considered, we can briefly state some particular impacts associated with them.

Self repairing car A self-repairing car would have a massive impact on people’s use of the motor industry. There is much more facility for people to learn that their car will fail long before it actually does. This has the obvious benefit for the customer that they do not end up broken down at the side of the road.

Additionally, identifying a failing component can prevent a breakage of one component that results in the cascade failure of many other components. This saves the user time and money and can save the car from being completely written off.

It does not impact merely when the car breaks down. The car may also have minor problems that affect its fuel efficiency, tyre wear etc. and this application would be able to identify this problem and recommend a solution. This would impact on the performance of the car and would have a large environmental impact. If we assume that most cars probably have some small fault causing lower fuel efficiency (even under-inflated tyres), then it would be possible to get an immense environmental benefit simply from this effect of the application.

If the car can tell the owner how to fix it, then, in some cases, the costs of hiring a mechanic can be eliminated as the owner may be able to fix the car themselves.

Proposal Part B: Page 190 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

All these applications have financial benefits for the owner of the car and a decent environmental benefit. The system could be upgraded in the future to include the whole system of intelligent cars that no longer need driving. In this case, each car would be a thing and they would seamlessly interact on the roads using contextual, intelligent reasoning. e-Inclusion of the Elderly and Disabled Given the rising elderly population and increasing life expectancy within Europe, inclusion of this demographic in the future is clearly an extremely important factor. The productive inclusion of the disabled will enhance the competitiveness of all of Europe globally. Making life as easy as possible for people with these disadvantages and allowing them to live as normally as possible will enhance their well-being and those of all around them.

There is a financial aspect to all of this. As the population of retirees rises over the coming years the tax burden on those still working will rise. Inclusion of the elderly, allowing these citizens to live in their own homes for as long as possible, without having to go into long-term care, will reduce the financial burden that these citizens place upon the rest of the population. Inclusion of the physically and mentally impaired will have an equal effect. Any application that allows them to live as normal a life as possible will reduce the burden on the state to support them and increase their overall happiness as they are fully included in society.

Environmental Crisis Management With the advent of climate change, the world nations must begin to take measures to adapt to the potential disaster situations that may befall them. Crises of this sort will become more frequent and more severe in nature. An IoT application to this scenario has the advantage of a contextual approach that will be more adaptable to sudden changes.

The prediction of potential disasters will be effected by continual monitoring of many different data streams. Once an event is forecast, the application will warn all local services in the area of the imminent danger and help to coordinate the response based on its up to date information. The advantage of a coordinated rapid response is self-evident. People must be evacuated as soon as possible and counter-measures must be put in place. This system would be able to monitor the whole of this process while continually feeding back to coordinators with recommendations as to how resources can be allocated.

3.1.5 Sustainable logistics The environmental impact of freight is measured in millions of tonnes of carbon released every year.

To make freight more efficient and quantifiably reduce the emissions is a worthy aim. An IoT approach to this goal will allow an increased communication. All traffic and packages will be able to communicate with each other at all times. This may allow packages to intelligently link up with packages going in the same direction, which would lead to a reduction in the number of partially full containers. This should mean more full containers and therefore less containers in total number.

Even the choice of transport medium can be influenced in this mechanism. The choices range all the way from air through rail and road to sea. It is often possible to send something by a slower means and reduce its impact. This is only possible in non-urgent cases.

Summary of IOT4ALL impact The aim of the integrated project IOT4ALL as a whole is to state and build up the basis for an interoperable world of things and services in a changing environment and with this respect, the citizens and the enterprises will be able to adopt not only the technology but the social aspects that come though.

The European Union is in the perfect position to play a leading role on the development of the IoT architecture. As we are still in early stages, early designers of the IoT will have an innovation lead and European companies should use this freedom in order to propose their advanced concepts. Similar to

Proposal Part B: Page 191 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

the UMTS success story, the early adoption and development of IoT architectures and protocol suites could jump start the success of European industry in this area.

The aim of the project as a whole is to state and build up the basis for an interoperable world of things and services in a changing environment and with this respect, the citizens and the enterprises will be able to adopt not only the technology but the social aspects that come though. While business analysts may have divergent opinions, it is a recognised fact that the huge increase in the number of communicating objects creates huge market prospects, and a worldwide harmonised standardisation will be one of the key factors of the success of IoT concepts. The IoT definition will be positive not only for the benefit, but also and mainly for the positive effects on the EU economy as well as on the environment, and will enhance quality of life and comfort for the EU population.

3.2Dissemination, exploitation of project results, and management of intellectual property 3.2.1. Creating long term value and exploiting the results of IOT4ALL The IoT4All project will develop long term value and exploit results on two levels: Firstly will strive for a sustainable result on a project level, and secondly we will facilitate each partner to recognise individual project results that can be of use to them and help them develop plans for their commercialisation or incorporation into the organisation.

On a project level: The project aims at producing a complete business plan, which will address the following main issues at different times along the project duration: 1. IPR and Consortium Agreement: Intellectual Property Rights on project results will be discussed during the project and the agreement formalised in a Consortium Agreement, whose signature is planned to take place before starting the project.

2. Initial product Definition, Customer Identification and Market Characteristics Initial product definition; customer/market requirements it meets; value it brings; strength/weaknesses vs. customer/market needs Who are the customerâ&#x20AC;&#x2122;s? How can they be segmented? What is their absolute number? What is the value of each segment? What is the purchase process?

What is the RAM (realistically available market)? how many, where, growth rate; market structure: market segmentation, needs, purchase process, potential market vs accessible market; state of development). Months 7 to 12.

3. Industry Landscape and Competitor analysis Mapping the value chain and identifying where value is created, how and by whom. Is it growing?, shrinking? Prone to fluctuations? Where is the bargaining power? What is the threat of new entrants? Porterâ&#x20AC;&#x2122;s five forces analysis. Who are the competitors? What do they offer? What are their relative strengths and weaknesses? What is their market share?

What is their business model? What implications has this for project direction? Does it challenge any of our assumptions? Is there a key area we have neglected? Month 13-24 4. Product Positioning, Marketing & Sales Strategy, Implementation: structure of the product offer; pricing policy; definition of the sales process; development and targeting of sales messages; definition of specific targets and priorities for each company; definition of the product management responsibilities, of the necessary internal marketing/sales

Proposal Part B: Page 192 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

infrastructure/resources, of the internal technical support infrastructure/resources. Months 24-42 A Quantified Business Plan (forecasts of costs: marketing, advertising, sales, technical support, product engineering, ongoing maintenance, etc.; forecasts of sales; forecasts of break-even point and ROI; commercial risks analysis): by Month 42.

IPR By Month 0 and Consortium Agreement

Months 1- 6 Product Definition

Months 19-24

Months 25-36

Marketing and Sales Strategy Sales and Technical Organisation

Months 7- 12 Cusatomer Identification and Market Charact.

Months 13-18 Analysis of Competitors and Prod. Positioning

By Month 48 Quantified Business Plan

Figure 1 â&#x20AC;&#x201C; IPR Management Plan On an individual level: Each project partner will follow the following process to recognise and exploit sources of value. With industry partners this takes a commercial route, while academic partners will follow a knowledge and expertise route.

1. Recognition of individual project results and their potential (M12-36) (what components, knowledge, skills etc. has the project produced?)

2. Identification of partner requirements and focal areas (M12-24) (What does the organisation do? What products, services, lines of activity require the types of results produced?)

3. Consolidation of partner needs with project results (M12-36) (Which organisations are interested in which results and why?)

4. Investigation of commercialisation or exploitation strategies (M24-36) (How can these results be best used to create value? How would they be applied to problems faced? How can they be incorporated into the organisation or product portfolio?)

5. Development of specific plans to realise that exploitation (M30-42) (What steps are required? Over what timescale? What further development is required? What is the potential market? Who are the competitors? What is the business case for this plan?)

Proposal Part B: Page 193 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All Project results and market context (M1-12)

Recognition of individual project results and their potential (M12-36)

Identification of partner requirements and focal areas (M12-24)

Consolidation of partner needs with project results (M12-36)

Investigation of commercialisation or exploitation strategies (M24-30)

Development of specific plans to realise that exploitation (M30-42)

A first key component of both the exploitation of the whole project output and of individual results is the comprehension of the potential for value creation. This involves detailed analysis into the market conditions. How big is the market? How does it work – what is its value chain? Where are the sources of value creation? What are the critical success factors? What competitors and substitutes exist?

What business models do they employ? What is the strength and stability of the industry? Which role in the value chain has the bargaining power? What is the potential for new entrants and how can IoT4All protect itself from existing players or subsequent copies?

These questions will be addressed on a project level between months seven and eighteen through steps (3) “Customer Identification and Market Characteristics” and (4) “Analysis of Competitors and Product Positioning” This will serve as input of individual exploitation plans, which will need to go further if their identified markets differ from those of IoT4All in general.

The second key of both is the realisation of the value creation, answering such questions as: What is my value proposition? What are my unique selling points? How will I deliver the good or service?

What legal, environmental or other considerations must I consider? What further development is required, if any? What third parties do I need (suppliers, sales, etc.)? How will I charge for the good or service? How will I market the product? What time scale is required? Where will I start?

This second component will be developed between months 1 and 42, starting with the product definition (M1-6) and culminating with the business plan (M42). In the case of individual exploitation plans, this will be developed between months 24 and 42.

A number of tools can be used to realise these analyses and decision making, including, but not limited to: PESTLE analysis; SWOT analysis; Critical success factor analysis; Porters 5 force modelling; the marketing mix, critical success factor analysis, decision making matrices, etc.

3.2.2. Contribution and use of standards The development of standards for IOT would be beneficial to all European stakeholders and in particular those who are closest to these technologies and service dimensions. Standards are vital to European competitiveness as they will provide a level playing field for industry, enabling companies

Proposal Part B: Page 194 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

and service providers to compete in European and global markets. IOT4ALL project will study the standard bodies, which include communication layers, functionality and interfaces for Internet of Things devices, data formats and information codes, naming, addressing and identification issues, middleware aspects and interoperability needs meeting the requirements of the global market place.

Interoperability is a particularly crucial dimension in that it contributes to the provisioning of affordable end-to-end solutions while reducing the costs of application integration. For example, EPCglobal leads the development of industry-driven standards for the Electronic Product Code (EPC) to support the use of Radio Frequency Identification (RFID) in todayâ&#x20AC;&#x2122;s fast-moving, information rich, trading networks. Current EPCGlobal vision and concepts as somehow "limited" in its willingness and capacity to address every kind of actors in any situation (too much standardization, too many deterministic views, etc.). XMPP standard looks neat and largely propagated by the wide adoption of Google Talk. This protocol could become a standard for future Internet of Things (IoC). This requires close cooperation with regional standards bodies, supported by policy debates and international dialogues with other world regions. Standardisation must not be limited to technical matters, but also take into account socio-economic and political aspects.

Standards Bodies that will be analyzed and investigated. We will work with them to refine and reuse their standards as appropriate.

Full Name International Organization for Standardization ISO/IEC Joint Technical Committee 1 Electronic Product Code European Telecommunications Standards Institute International Telecommunications Union â&#x20AC;&#x201C; Telecommunications Sector International Electrotechnical Commission European Committee for Standardization European Committee for Electrotechnical Standardization Institute of Electrical and Electronics Engineers Internet Engineering Task Force

Acronym ISO ISO/IEC JTC1 EPCglobal ETSI ITU-T IEC CEN CENELEC IEEE IETF

3.2.3. Dissemination Activities A successful dissemination strategy will be due to the mix of ongoing marketing activities in the areas of events, trainings, journals, newsletters and the website. The information must be of the highest quality delivered in an ongoing fashion to the target group.

SIGS DATACOM will take charge of coordinating communication to the European software community. They will ensure that communication and dissemination efforts follow a strategy regarding what will be communicated and to whom. As the project passes through its project lifecycle, the nature of the core messaging will change: from initially informing the stakeholders of the project objectives and activities, to later building anticipation for concrete results that are expected, and later proliferating awareness and use of those results. Consequently the appropriate communication channels will change and different tools must be employed: press releases are good for targeting a diffuse audience with general objectives; conferences are useful for engaging in debate about initial results and involving the research community; peer-reviewed journals invite scrutiny and debate on conclusions and demonstrations and tutorials are good for encouraging commercial take up of results.

Proposal Part B: Page 195 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

The project will define a dissemination strategy that will be revised periodically by project management and use this to define a dissemination plan covering the following 12 month period. At the end of each period this will be revised according to perceived successes and failures, feedback, changes in market conditions and the overall evolution of the project. This will incorporate the results of a periodic Internet-based survey in order to get direct feedback from selected previously identified contacts of the SIGS DATACOM database, which will provide invaluable input for the next phases of the project. At the same time it is our goal that participants of these surveys/market analysis results will become, going forward, users and in the long run customers of the Internet of Things project.

The first step towards defining the dissemination strategy is based on the preliminary identification of target groups. This will be refined during the project. Our identification of target groups will initially come from the existing SIGS DATACOM database. The database contains approx. 75.000 email addresses including addresses from Germany, Switzerland, Austria, UK, Scandinavia, Benelux, Italy, France and Spain, etc. which all have an Opt in. In addition we have another 12.000 addresses in the area of Data Warehousing and Business Intelligence.

The target groups of software architects, IT project leaders, programmers, developers and to a lesser degree, CIO´s of the leading European IT software companies are of vital importance. SIGS DATACOM will motivate these well known contacts to become an active part of in the (IoT) project.

For almost 20 years SIGS DATACOM has formed part of the European IT software community. The brand name is a reliable, well known factor.

The following communication channels are initially considered:        

Events (conferences, seminars) Journals (articles, technical updates, interviews in OBJEKTspektrum, JavaSPEKTRUM) New Services (E-mail Shots via SIGS DATACOM database, advertisements in Email-newsletters) Press releases Whitepapers Demonstrations, tutorials, workshops and video presentations Extensive Coverage on the SIGS DATACOM websites with related links Realizing a separate IoT4ALL homepage (e.g. www.IoT4ALL.eu) This domain name has already been purchased.

The IoT4ALL project is fortunate to have dissemination manager partner that currently organises a large number of well known, user-oriented events for practitioners and managers in software intensive organisations. For the last 18 years, SIGS DATACOM has organised a major annual event called the “OOP Conference –Software meets business– Practical software technology decisions”.

Furthermore, they organize more than 100 other events addressing this target group or parts of this target group in 2009 reaching more than 3000 paying professionals and approx. 2000 visitors. This is an excellent resource for IoT4ALL to exploit.

Furthermore through the dissemination manager we have access to the journals OBJEKTspektrum and JavaSPEKTRUM that have a print run of 15-16000 copies each. Each journal is published 6 times a year. Both journals have a paying subscriber base of approx. 4-5000. The journals are a very good medium to report about the IoT4ALL Project, publishing interviews with leading individuals, dealing with the latest technical developments and standardization issues.

SIGS DATACOM will actively provide the organisers of IoT4ALL conference with:  a list of potential exhibitors/sponsors  a list of potential speakers  3 newsletter advertisements (per newsletter 44.000 recipients)

Proposal Part B: Page 196 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

 1 stand-alone newsletter (80.000 recipients) in order to generate delegate bookings  Possibility to select qualified prospects out of our database of 80.000 IT-professionals throughout Europe. For conference organizer the addresses are free of charge.  Postage costs are the responsibility of event organizer.  Print advertising in JavaSPEKTRUM and OBJEKTspektrum (to be finalized with event organizer)  Provide personal support if required for operational items  We will create a special section on the SIGS DATACOM website dedicated to the IoT4ALL Project. On this section we will promote conference, user forum and local end-user events.

We will monitor the traffic and report back to the organizers on a monthly basis.  Once the organiser for the IoT4ALL user forum is known to SIGS DATACOM. SIGS DATACOM will actively support for 36-42 months to organize via Email newsletters, postmailings, distribution of forum brochures at SIGS-DATACOM events, print advertising activities, presence of event on SIGS DATACOM website in order to attract delegates to the User Forum.  If required SIGS DATACOM does offer support to develop the Forum program, suggest speakers, logistics (venue, catering, registration, catering) as well.  If IoT4ALL partners are interested to hold during the project period local end-user events SIGSDATACOM will be separately contracted by the local partner. We will offer our services to organize a complete blueprint in order to hold a local event form the beginning, i.e. the planning till holding the actual local event with SIGS DATACOM and the respective IoT4ALL partner.

A significant part of the available SIGS DATACOM Email database is already part of the IoT4ALL community. Attractive newsletters with state-of-the-art, hands-on information regarding the project IoT4ALL with further information on current results achieved, dates of lectures, talks and trainings available product reviews and demos will be very attractive for the current recipients of SIGS DATACOM`s Email-newsletters. In addition we are very confident to enhance with further marketing activities the IoT4ALL community over the next four years significantly.

Currently we have the following Email-addresses as opt-ins for circulation available: Germany, Switzerland, Austria 44.000 Italy: 2.600 France: 1.600 UK 20.600 Benelux 3.100 Scandinavia 3.400 Spain 600 Hungary 400 Czech Republic 100

Overall, the dissemination strategy will reach (min.): Events: Paying delegates 3.700 per year Visitors of exhibition  2.000 per year Journals: OS, JS, BIS  34.000 per year Newsletter contacts  636.000 per year Total (min)  676.700 per year

Proposal Part B: Page 197 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

3.2.4. Managing of knowledge and intellectual property rights Due to the innovative aspects of IOT4ALL, it is expected that partners will generate Intellectual Property that has to be protected through appropriate means, yet made available for other partners for their own work in the project, and exploited outside the project by appropriate licensing.

Most of the partners have substantial prior experience in EC RTD collaborative projects: all have therefore agreed to the general principles on which IPR will be managed and allocated, considering that the projects handing of IPR is completely in-line with Annex II of the Model Contract and, in general, with the expected contracts covering the provision of EU support.

Moreover, all Parties have already reviewed and agreed a first draft of IOT4ALL Memorandum of Understanding, that will be signed before the starting of negotiations, in case of successful evaluation. The partners, before the start of the project, will enter into a binding Consortium Agreement, whose main aspects are likely to arise are listed below: 1. Ownership and transfer of ownership of Foreground Foreground shall be the property of the contractor carrying out the work leading to that Foreground.

Where several contractors have jointly carried out work generating the Foreground and where their respective share of the work cannot be ascertained, they shall have joint ownership of such Foreground.

2. Protection of Foreground Where Foreground is capable of industrial or commercial application, its owner shall provide for its adequate and effective protection, in conformity with relevant legal provisions, including the Model Contract and any Consortium Agreement, and having due regard to the legitimate interests of the contractors concerned. Details of any such protection sought or obtained will be included in the Exploitation and Dissemination Plans 3. Access rights to Foreground, Background and Sideground The general principles relating to access rights are the following: a) Access rights shall be granted to any of the other contractors upon written request.

The granting of access rights may be made conditional on the conclusion of specific agreements aimed at ensuring that they are used only for the intended purpose, and of appropriate undertakings as to confidentiality. Contractors may also conclude agreements with the purpose of granting additional or more favourable access rights, including access rights to third parties, in particular to enterprises associated with the contractor(s), or specifying the requirements applicable to access rights, but not restricting the latter. b) Access rights to Background and to Sideground shall be granted provided that the contractor concerned i Access rights for execution of the project are the following: ď&#x201A;ˇ

Contractors shall enjoy access rights to the Foreground, to the Background and Sideground, if that Foreground, Background and/or Sideground is needed to carry out their own work under the project. Access rights to Foreground shall be granted on a royalty-free basis. Access rights to Background and to Sideground shall be granted on a royalty-free basis, unless otherwise agreed before signature of the contract.

ď&#x201A;ˇ

Subject to its legitimate interests, the termination of the participation of a contractor shall in no way affect its obligation to grant access rights to the other contractors pursuant to the previous paragraph until the end of the project.

Access rights for use of Foreground are the following: a) Contractors shall enjoy access rights to Foreground, Background and Sideground, if that Foreground, Background and/or Sideground is needed to use their own Foreground. Access rights to Foreground shall be granted on a royalty-free basis, unless otherwise agreed before

Proposal Part B: Page 198 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

signature of the contract. Access rights to Background and to Sideground shall be granted under fair and non-discriminatory conditions to be agreed.

It is envisaged also that the Parties, again before the start of the Project, will arrange a positive list of Background needed for the purpose of the project, excluding specific Background where appropriate: this list will be attached to the Consortium Agreement.

The protection and management of Intellectual Property and access rights for Foreground generated within the project, being it for further research or for commercial use and exploitation, is an essential issue, to which this Consortium is going to devote great attention aiming at clearly identify and address all the relevant concerns, such as ownership and suitable protection mechanisms to be applied to the IOT4ALL results.

3.2.4.1. IPR Advisor Considering such relevance of IPR issues, it is envisaged that the consortium will: o Appoint an IPR Advisor o Develop the IPR Exploitation Initial Roadmap (containing an IPR Repository), the Intermediate and the Final IPR Repository Updates and the IPR Deployment Agreement o Record the Laboratory Workbooks As regards the IPR Advisor, this figure will be appointed soon after the start of the project and will be an expert in the management of Foreground and IPR. He will advice the Project Management Board on the protection, management and exploitation of Foreground and Intellectual Property generated by the Project, so that to better face matters such as possible licensing, formation of spin-out companies and joint ventures and to provide business support services.

In this way, it will be possible to adequately market new technologies, that may be developed by the project. The IPR Advisor will seek input from all Consortium members on a regular basis (as part of the management meeting agendas) on any new Foreground and IPR generated during reporting periods and, acting on behalf of the Consortium, will advice on exploitation routes for such Foreground and IPR, particularly dwelling upon inputs from the Consortium industrial partners, in order to support the Project Management Board in making appropriate decisions on exploitation roadmaps. Of course, this doesnâ&#x20AC;&#x2122;t exclude a Consortium partner from exploiting its Foreground and IPR within the framework of the Consortium Agreement.

The IPR Advisor will have a key-role also in the development of the IPR exploitation initial roadmap, of the IPR repository update and of the IPR deployment agreement. ď&#x201A;ˇ The IPR Exploitation Initial Roadmap will be developed during the first quarter of IOT4ALL activities and will aim at facilitating planning and execution of a controlled path in order to achieve a set of defined objectives upon IPR issues, described within an outline vision. It will also define a strategy for future actions and will explicitly incorporate a development plan concerning Intellectual Property management. The targets of the roadmap are first of all the Parties, but also, in an indirect way, the European Commission.

The roadmap will be validated in a consensus-building process among the Parties themselves, with the main aims of contributing to the definition of emerging barriers, needs and requirements on IPR matters in the project, of identifying proper strategies, of providing a common approach to IPR agreements and of achieving a common understanding of concepts and consensual dialogue, able to concretely support the enrichment and validation of IOT4ALL results.

The same document will contain also the proper standard for the Laboratory Workbooks and the updated version of the list concerning Background and Sideground. In fact, Intellectual property that is brought into the project or an asset will be recorded, uniquely identified and linked together: in other terms, a clear IPR Repository will be created. The information captured will include the provenance, permitted usage/user/price matrix and the terms of any current agreements for the contributions.

Proposal Part B: Page 199 of 203

FP7-ICT-2009-5 26/10/09 v1.0

ď&#x201A;ˇ

IP proposal IoT4All

The IPR Repository Updates will respectively be made, on the one hand, at the beginning of the development of the IPR exploitation initial roadmap, containing the list of Background and Sideground pertaining to the various Parties, and, on the other hand, before the end of project activities: in the update versions the Repository will be enriched also with the Foreground developed in the meanwhile.

ď&#x201A;ˇ

Finally, the IPR Advisor will seek for a suitable IPR Deployment Agreement among the Parties that will have contributed to the development of the Foreground concerned, in particular of the joint ownership IOT4ALL results. In such agreement allocation and terms of exercising the ownership of knowledge will be clearly defined, in a more detailed way that in the Consortium Agreement, so that to specify all governing management issues, taking also into account the different national joint ownership regimes to avoid their potential pitfalls.

It may be established, for instance, that patent applications will be filed and maintained by only one of them, subject to proper licensing clauses or other provisions. In case the share of revenue has not been previously defined, a clear provision about this aspect will be contained in this Agreement. Provisions pertaining to the sharing of the costs arising from legal protection procedures, such as patent filing and examination fees, renewal fees, prior state of the art searches and so on, will be addressed in the above mentioned document.

It may be preferred, instead of developing only one agreement, to prepare a template of IPR Deployment Agreement, including different choices for the most significant clauses, so that to meet all the possible needs and requirements of the Parties involved in the generation of the several project results.

Due to the fact that ownership is usually one of the basic mechanism to determine royalties and revenue shares, it is envisaged that all contractors will maintain Laboratory Workbooks, in accordance with proper standard that will be identified in the IPR exploitation initial roadmap, so that it will be possible to prove ownership, as well as the conception date of any invention.

The Consortium will address IPR topics with an approach aiming at linking them with exploitation concerns (besides taking into in-depth consideration the chosen dissemination strategy): in fact, the procedures of IPR assessment will help to clarify any Background right already existing and to define clear rules of ownership for a successful common future exploitation approach, which could be able to assure the effective protection and use of Foreground and Joint ownership of results deriving from the project.

The Parties ensure that the rights "any" personnel (employees, scholars, collaborators, etc.) may claim to the results by virtue of national law or agreement will not prejudice the obligations assumed by the grant agreement and/or by the Consortium Agreement or other arrangements between the Parties themselves.

In any case, it will be strongly emphasized that IOT4ALL results have been achieved thanks to EC financial support: in any publication or other dissemination activity, patent applications filed and patents issued on the results there will be a clear statement specifying that the Foreground in question was made with assistance of financial support from the European Community.

In a few words and aiming at summarizing, the Parties activities on IPR issues may be divided into three main areas: 1. Activities to be undertaken before the signature of the expected EC grant agreement: Memorandum of Understanding Consortium Agreement, with an Annex containing the list of Background 2. Activities to be undertaken during IOT4ALL development Appointment of an IPR Advisor IPR Exploitation Initial Roadmap (containing the IPR Repository) Intermediate and Final IPR Repository Update IPR Deployment Agreement or template Record of the Laboratory Workbooks

Proposal Part B: Page 200 of 203

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

3. Activities to be undertaken after the termination of the Project Possible signature of IPR Deployment Agreements based on the template Legal protection of Intellectual Property and maintenance of it.

Section 4: Ethical Issues ETHICAL ISSUES TABLE YES Informed Consent Does the proposal involve children?

Does the proposal involve patients or persons not able to give consent?

Does the proposal involve adult healthy volunteers?

Does the proposal involve Human Genetic Material?

Does the proposal involve Human biological samples?

Does the proposal involve Human data collection?

Research on Human embryo/foetus Does the proposal involve Human Embryos?

Does the proposal involve Human Foetal Tissue / Cells?

Does the proposal involve Human Embryonic Stem Cells?

Privacy Does the proposal involve processing of genetic information or personal data (eg. health, sexual lifestyle, ethnicity, political opinion, religious or philosophical conviction) Does the proposal involve tracking the location or observation of people?

Research on Animals Does the proposal involve research on animals?

Are those animals transgenic small laboratory animals?

Are those animals transgenic farm animals?

Are those animals cloned farm animals?

Are those animals non-human primates?

Research Involving Developing Countries Use of local resources (genetic, animal, plant etc) Impact on local community Dual Use

Proposal Part B: Page 201 of 203

PAGE

FP7-ICT-2009-5 26/10/09 v1.0

IP proposal IoT4All

Research having direct military application Research having the potential for terrorist abuse ICT Implants Does the proposal involve clinical trials of ICT implants?

I CONFIRM THAT NONE OF THE ABOVE ISSUES APPLY TO MY PROPOSAL

Proposal Part B: Page 202 of 203

x

FP7-ICT-2009-5 26/10/09 v1.0

ANNEX A: Letter of Support of ETSI to the IoT4ALL project.

Proposal Part B: Page 203 of 203

IP proposal IoT4All